Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
None
Description
We have more and more Jenkins jobs and we need to make them easier to manage. Also the idea is to have one job per maven project (instead of coarse-grained jobs as we have now, i.e. for example one job for the platform modules) so that we can benefit from all our distributed agents.
I've started exploring http://evgeny-goldin.com/wiki/Maven-jenkins-plugin
Current issues we need to work around:
- Doesn't support some parameters we use. For example <blockBuildWhenUpstreamBuilding>. See http://evgeny-goldin.org/youtrack/issue/pl-588
- I still need to check if "Build whenever a snapshot dep is built" and "Build when a change is pushed to GitHub" are handled
- The plugin doesn't push the generated config.xml file through the REST API (see http://evgeny-goldin.org/youtrack/issue/pl-190?projectKey=pl&query=REST). Right now this means we need to ssh the config.xml files to the remote server and perform a refresh on the jenkins instance so that they are taken into account.
- We need an automated way to remove jobs too when we stop supporting a given branch
Note that this feature is also related for supporting the Functional tests in platform, see http://markmail.org/thread/uorjcsq5axkjk47t