Re: New git repo for jenkins

----- Original Message ----- Let me try to explain. Currently the status is all job logic is written inside the job itself, this is bad practise, for a few reasons: 1. no code review (job configuration is also only viewable and accessible to jenkins power-users/admins, not very "open source" approach) 2. difficult to include usage of files (answer file for example for automating engine-setup) 3. backup of code and revisions (sure there is the job config-history but that's really for troubleshooting the restoring jobs) 4. writing long complex code in bash/python inside a textbox is error prone and not convenient. I have experience from the past 2 years of writing code for jenkins jobs that got complex and longer as the product evolved. today i use even more than one repository for running jobs in jenkins. the proposed change is to keep all code inside a git repo instead just inside jenkins jobs. it doesn't mean that every job that has 2-3 lines of code should go into the git, it means we have a choice, if the code gets too complex (like running engine-setup + engine-upgrade) then we can use git as the source for the code. I intend to add some of the existing jobs that runs complex code into it, but not all of them. that's up to the job maintainer to decide. the way to use it in a job is by using the 'multiple scm plugin' which allows you to listen to more than one git repo for a job. you can see an example in the new setup+upgrade job knesenso is building now http://jenkins.ovirt.org/job/ovirt_engine_upgrade_stable_32_to_latest_32/... as i mentioned, this plugin is good mainly for keeping track on who made change