One of the more popular concepts on automated build servers are the concept of build pipelines. The concept is also one of the corner stones in continuous delivery which these days is a must know and do in agile software development. Yet it seems that none of the very popular Jenkins CI build server plugin really support the concept to full extend and in a flexible manner. Inspired by, or extending, the existing plugins for Jenkins we need to solve this challenge once for all. By taking on this project you will be introduced to some of the most modern software development concepts that every one talks about. You will be developing in Java, contributing to the largest CI build server community - the Jenkins CI community - and you will gain a lot of community respect from a working solution. User scenarioWhen setting up a build pipeline on Jenkins the following process, workflow or features are needed. Some of these are already supported by one or several of existing plugins, but no one have them all and work around must be deployed. Our scenarios for a pragmatic build pipeline include:
Design proposalWe suggest to start with a research of the current solution, and that we give an introduction to the current limitions. A technical investigation of the current plugin might the be done to find out if a new plugin is needed or current solution can be brought to work. EstimateWe estimate that students that are unfamiliar with continuous delivery concept and Jenkins CI plugin development would spend 4-600 hrs on an assignment like this. A professional implementation done by Praqma is estimated to 100 hrsReferences
ContactCall Lars on +45 20 87 25 30 or mail to him on lak@praqma.net if you are interested in this Blue Print. |
Blue Prints >