Re: How to handle project dependencies?
I'm also new here - but possibly facing similar problems (C#). I'm not sure how exactly you expect the dependencies to be handled, but I thought I would post my opinion. I am going for your option B one job for each project? My current plan is to add build other project post build tasks to jobs that are depended upon. If I understand correctly, by doing this I can Block build when upstream project is building, and Block build when downstream project is building. Since I want immediate feedback, regardless of what is happening elsewhere, I'm NOT going to use these. Maybe you want to... I will also use the Copy artifacts plugin for projects that have dependencies to use the last successfull build from the upstream project. Below is a sample setup with some possible problems. Job A (triggered by a code checkin to repo somerepo/A,with with post build task to to run Job B) Job B (triggered by a code checkin to repo someotherrepo/B AND has a dependency on Job A) Problem 1 Scenario A Two different developers check in changes simultanuously to the two different repo's. Since the changes do not depend on one another, both jobs should be allowed to run simultanuously (job B can use the last successful build of job A's artefacts). When Job A is done, the post build task will run Job B a second time. Scenario B A single developer checks in changes to both repos at the same time - the changes depend on each other. The jobs will be run as described in Scenario A - which causes Job B to fail. The second run of Job B should fix this. I think scenario B will not happen often - and I can accept a failed build in this case. Is this the type of handling you are asking about?
Re: How to handle project dependencies?
Another problem caused by not using the Block build when upstream project is building or Block build when downstream project is building in my post setup is that Job A and Job B could end up running on the same slave. This would be problematic (for me at least) since the artefacts of Job A would replace the dependency of Job B. To get around this I have to ensure that a slave can only run one job at a time. I think this is the number of executors of a slave. I don't think this is a big problem, slaves are pret
Re: How to handle project dependencies?
*pretty cheap
Jenkins open or close issue
How can I implement to Jenkins open or close a issue ticket? I can use Redmine, Trac, Mantis, Bugzilla, whatever. It`s possible to jenkins open a Issue ticket on some of this projects? If possible I would like open a Issue ticket (some of these softwares) and jenkins closse the issue depending of the status of the build Thanks for you attention
Re: Jenkins open or close issue
You could probably use the groovy post build action plugin and make a script to send a request using whatever API your ticket system uses. Sent from my iPhone On 2012-11-17, at 3:31 PM, Gustavo Lira e Silva guga.li...@gmail.com wrote: How can I implement to Jenkins open or close a issue ticket? I can use Redmine, Trac, Mantis, Bugzilla, whatever. It`s possible to jenkins open a Issue ticket on some of this projects? If possible I would like open a Issue ticket (some of these softwares) and jenkins closse the issue depending of the status of the build Thanks for you attention
Re: Jenkins open or close issue
This may sound heretical, but it seems like that is too much process for a compilation failure or a test failure. If the code fails to compile, don't you most want to fix the failed compilation? Why make the person who is fixing the failed compilation also spend time updating another database / bug tracker to show that they fixed the failed compile. Likewise for a test failure. If a test fails, it seems to me that the real value is in the analysis which decides if the test failed because the test is wrong, or if the test failed because the code being tested is wrong. Can you explain further why you want to track Jenkins detectable issues somewhere other than in Jenkins? Now, having expressed my skepticism of how you would open an issue ticket from Jenkins, you might look at: https://wiki.jenkins-ci.org/display/JENKINS/Trac+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Redmine+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Bugzilla+Plugin Thanks, Mark Waite From: Gustavo Lira e Silva guga.li...@gmail.com To: jenkinsci-users@googlegroups.com Sent: Saturday, November 17, 2012 1:31 PM Subject: Jenkins open or close issue How can I implement to Jenkins open or close a issue ticket? I can use Redmine, Trac, Mantis, Bugzilla, whatever. It`s possible to jenkins open a Issue ticket on some of this projects? If possible I would like open a Issue ticket (some of these softwares) and jenkins closse the issue depending of the status of the build Thanks for you attention
Re: Jenkins open or close issue
Mark, History. At this time, I report outward so that we can determine which tests are flaky. That's the engineering reason. We all know the MGMT reason... Metrics , Metrics, Metrics Total result trendlines are useful. I just wish I could click on a specific test and see its history. Jenkins has all the info. Rodney On Sat, Nov 17, 2012 at 12:49 PM, Mark Waite markwa...@yahoo.com wrote: This may sound heretical, but it seems like that is too much process for a compilation failure or a test failure. If the code fails to compile, don't you most want to fix the failed compilation? Why make the person who is fixing the failed compilation also spend time updating another database / bug tracker to show that they fixed the failed compile. Likewise for a test failure. If a test fails, it seems to me that the real value is in the analysis which decides if the test failed because the test is wrong, or if the test failed because the code being tested is wrong. Can you explain further why you want to track Jenkins detectable issues somewhere other than in Jenkins? Now, having expressed my skepticism of how you would open an issue ticket from Jenkins, you might look at: https://wiki.jenkins-ci.org/display/JENKINS/Trac+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Redmine+Plugin https://wiki.jenkins-ci.org/display/JENKINS/Bugzilla+Plugin Thanks, Mark Waite -- *From:* Gustavo Lira e Silva guga.li...@gmail.com *To:* jenkinsci-users@googlegroups.com *Sent:* Saturday, November 17, 2012 1:31 PM *Subject:* Jenkins open or close issue How can I implement to Jenkins open or close a issue ticket? I can use Redmine, Trac, Mantis, Bugzilla, whatever. It`s possible to jenkins open a Issue ticket on some of this projects? If possible I would like open a Issue ticket (some of these softwares) and jenkins closse the issue depending of the status of the build Thanks for you attention
Re: How to handle project dependencies?
I also think using the fingerprint plugin (https://wiki.jenkins-ci.org/display/JENKINS/Fingerprint) will be very useful to track dependencies - i.e. this build failed because these dependencies are not compatible...
Re: How to use the environment variables set by a parameterized build?
Hey,
Checkout the environmental variable here:
https://wiki.jenkins-ci.org/display/JENKINS/Building+a+software+project
Short answer:
echo ${JOB_NAME}
echo ${BUILD_NUMBER}
On Friday, November 16, 2012 3:39:26 PM UTC-5, Martin Lichtin wrote:
Hi
For a parameterized build with one run parameter (let's name it X),
Jenkins set three environment variables.
X
X.jobName
X.number
How can the latter two be used in a pre-step shell script?
Bash cannot handle environment variables containing a dot, it seems.
$ echo ${X.jobName}
bash: ${X.jobName}: bad substitution
Re: a lot of jobs
It does not suite my needs, it just allows to organize multiple jobs which are supposed to all be triggered by the same event, am I correct? My jobs are pretty similar to each other - ex. build jobs have the same configuration except svn url, downstream jobs list and maybe some details (like email notification triggers), all other properties are equal. But they are triggered at different times as they relate to different projects. What I'm looking for is more like configuration inheritance, where I'd need to change job configuration property once, in only one place (in the 'base' job) instead of per each job (plus possibility to override at job level). Maybe there is possibility to use configuration slicing plugin without admin permissions? That would partially work Thanks Marcin On Nov 15, 5:48 pm, Marek Gimza marekgi...@gmail.com wrote: Marcin, Do you know about the MultiJob plugin? https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin Regards, Mgimza On Wed, Nov 14, 2012 at 7:39 PM, Marcin Biegan marcin.bie...@gmail.comwrote: Hi, I wanted to ask how do you handle configuring multiple jobs. We have about 10 maven projects to build in at least 2 versions (trunk/ branch), which makes 20 jobs, some more for additional tests, releases, maybe deployment, verification, etc. Manually adding permissions and adjusting configuration of jobs is cumbersome. Is there a working plugin which would allow to set some 'parent' job which would define default configuration? (Template Project Plugin is not enough, because it 'works' only at job creation). I know also about Configuration Slicing Plugin, but this will not work in my case as it requires admin permissions. Thanks Marcin Biegan
