Re: How to force an upstream job to be green
hi, thx for suggestion. I have it running, but the only issue i run into
is that if it actually fail, it is not triggerring a post action. like if
it fail i want it to trigger parameterized build on other project. but its
not doing this.
out.println params[browser]
out.println params[baseUrl]
parallel (
retry ( 2 ) { build( test1 , param1: params[browser] , param2:
params[baseUrl] ) },
retry ( 2 ) { build( test2 , param1: params[browser] , param2:
params[baseUrl] ) },
)
I have a post build after this. Any suggestion? thx
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/9cca7b61-e750-4513-bf01-20f24629eadf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: How to force an upstream job to be green
NM, there's an issue with build flow.
https://issues.jenkins-ci.org/browse/JENKINS-22779
On Monday, January 12, 2015 at 3:00:22 PM UTC-8, Lam Le wrote:
hi, thx for suggestion. I have it running, but the only issue i run into
is that if it actually fail, it is not triggerring a post action. like if
it fail i want it to trigger parameterized build on other project. but its
not doing this.
out.println params[browser]
out.println params[baseUrl]
parallel (
retry ( 2 ) { build( test1 , param1: params[browser] , param2:
params[baseUrl] ) },
retry ( 2 ) { build( test2 , param1: params[browser] , param2:
params[baseUrl] ) },
)
I have a post build after this. Any suggestion? thx
--
You received this message because you are subscribed to the Google Groups
Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/47084c18-9b5b-4295-9017-951c8b438a5e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: How to force an upstream job to be green
If I understand your requirements correctly, I would use the build flow plugin: https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin Make the controller job a build flow job which calls the other 3 jobs in a guard-rescue block each and let them re-run once if they fail in the rescue block. Other alternatives might be the workflow plugin https://github.com/jenkinsci/workflow-plugin or the build pipeline plugin https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin but I don't have much experience with them. HTH Christoph Am 10.01.2015 um 00:05 schrieb Lam Le: I have a job which act as a controller. It call subsequent job using the 'Trigger/call builds on other projects' plugin. The controller call 3 other jobs, if any of these job fail, then it will rerun itself. Controller: J#1 - Pass J#2 - Pass J#3 - Fail, retry and Pass In this case, the controller job will be marked as Failed on the history. How do I force this to become green/successful? I am currently using the promote plugin which only put a green star next to failure in the history. The issue with this is in the upper view level, it still show the controller as a RED/Fail unless someone click into it to view the history. I want it to truly be green in the upper level view. Thanks. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com mailto:jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d723225c-4039-40fd-a51b-a78f30b7dfa4%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/d723225c-4039-40fd-a51b-a78f30b7dfa4%40googlegroups.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/54B0FBA9.8000805%40gmx.de. For more options, visit https://groups.google.com/d/optout.
Re: How to force an upstream job to be green
Much better of course to use the retry statement of the build-flow plugin:
retry ( 3 ) {
build( this_job_may_fail )
}
Am 10.01.2015 um 11:15 schrieb Christoph Kutzinski:
If I understand your requirements correctly, I would use the build flow
plugin: https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin
Make the controller job a build flow job which calls the other 3 jobs in
a guard-rescue block each and let them re-run once if they fail in the
rescue block.
Other alternatives might be the workflow plugin
https://github.com/jenkinsci/workflow-plugin
or the build pipeline plugin
https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin
but I don't have much experience with them.
HTH
Christoph
Am 10.01.2015 um 00:05 schrieb Lam Le:
I have a job which act as a controller. It call subsequent job using
the 'Trigger/call builds on other projects' plugin. The controller call
3 other jobs, if any of these job fail, then it will rerun itself.
Controller:
J#1 - Pass
J#2 - Pass
J#3 - Fail, retry and Pass
In this case, the controller job will be marked as Failed on the
history. How do I force this to become green/successful? I am
currently using the promote plugin which only put a green star next to
failure in the history. The issue with this is in the upper view level,
it still show the controller as a RED/Fail unless someone click into it
to view the history. I want it to truly be green in the upper level view.
Thanks.
--
You received this message because you are subscribed to the Google
Groups Jenkins Users group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-users+unsubscr...@googlegroups.com
mailto:jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/d723225c-4039-40fd-a51b-a78f30b7dfa4%40googlegroups.com
https://groups.google.com/d/msgid/jenkinsci-users/d723225c-4039-40fd-a51b-a78f30b7dfa4%40googlegroups.com?utm_medium=emailutm_source=footer.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups Jenkins
Users group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/54B0FC1F.40804%40gmx.de.
For more options, visit https://groups.google.com/d/optout.
How to force an upstream job to be green
I have a job which act as a controller. It call subsequent job using the 'Trigger/call builds on other projects' plugin. The controller call 3 other jobs, if any of these job fail, then it will rerun itself. Controller: J#1 - Pass J#2 - Pass J#3 - Fail, retry and Pass In this case, the controller job will be marked as Failed on the history. How do I force this to become green/successful? I am currently using the promote plugin which only put a green star next to failure in the history. The issue with this is in the upper view level, it still show the controller as a RED/Fail unless someone click into it to view the history. I want it to truly be green in the upper level view. Thanks. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/d723225c-4039-40fd-a51b-a78f30b7dfa4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
