Re: Release Button or best practice
We have a similar design challenge. I was thinking about creating dependent builds and then chaining them, but the more I look at it the more I am convinced that Jenkins is just an awkward fit for CD. On Monday, August 21, 2017 at 8:31:28 AM UTC-7, Steven Foster wrote: > > I do like this solution and it seems really flexible but unfortunately it > has one big problem for us. The build is not technically *done* until this > input step is answered. Sometimes we will want to release over a week > later. We release at any time really. If we timeout then we can't answer > the input step, but if we don't timeout then the build does not finish. It > would be lovely if we could specify an input step between two different > jobs, or split it in some way so we can have builds completing and later > decide to continue some builds to the deploy stage. > > On Monday, August 21, 2017 at 10:54:46 AM UTC+1, Ludovic SMADJA wrote: >> >> Actually we are using a input step without a timeout fixed to one day (in >> order to deploy the version which was deployed during the last night on >> pre-prodcution server). >> >> If you catch the timeout exception without any error, This tricks do the >> job. >> >> -- >> >> Ludovic SMADJA >> R engineer - build process and development JALIOS SA >> http://www.jalios.com >> >> -- 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/1ef94f3a-67cb-43f9-b4bf-24b97aefd742%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Release Button or best practice
I do like this solution and it seems really flexible but unfortunately it has one big problem for us. The build is not technically *done* until this input step is answered. Sometimes we will want to release over a week later. We release at any time really. If we timeout then we can't answer the input step, but if we don't timeout then the build does not finish. It would be lovely if we could specify an input step between two different jobs, or split it in some way so we can have builds completing and later decide to continue some builds to the deploy stage. On Monday, August 21, 2017 at 10:54:46 AM UTC+1, Ludovic SMADJA wrote: > > Actually we are using a input step without a timeout fixed to one day (in > order to deploy the version which was deployed during the last night on > pre-prodcution server). > > If you catch the timeout exception without any error, This tricks do the > job. > > -- > > Ludovic SMADJA > R engineer - build process and development JALIOS SA > http://www.jalios.com > > -- 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/93818a64-f2c0-4c76-9ba7-ffe71ce08c63%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Release Button or best practice
Actually we are using a input step without a timeout fixed to one day (in order to deploy the version which was deployed during the last night on pre-prodcution server). If you catch the timeout exception without any error, This tricks do the job. Le mercredi 16 août 2017 à 02:22 -0700, Steven Foster a écrit : > On Tuesday, August 15, 2017 at 6:09:04 PM UTC+1, Simon Richter wrote: > > You are looking for the "Promoted Builds" plugin. > > > > > > > > Ah, I did come across this but unfortunately we are using pipeline builds and > it seems this isn't compatible > > > > > -- > > 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+unsubscribe@googleg > roups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/4e285cf7-ba96-40a7-bcd2-d18 > 3cd72e472%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > -- Ludovic SMADJAR engineer - build process and development JALIOS SA http://www.jalios.com -- 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/1503309267.8119.5.camel%40jalios.com. For more options, visit https://groups.google.com/d/optout.
Re: Release Button or best practice
On Tuesday, August 15, 2017 at 6:09:04 PM UTC+1, Simon Richter wrote: > > > You are looking for the "Promoted Builds" plugin. > > Ah, I did come across this but unfortunately we are using pipeline builds and it seems this isn't compatible -- 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/4e285cf7-ba96-40a7-bcd2-d183cd72e472%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Release Button or best practice
Hi, On 15.08.2017 18:25, Steven Foster wrote: > Does anyone know of any techniques or plugins for triggering a release > after a build? You are looking for the "Promoted Builds" plugin. Simon -- 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/0d98c982-dcdd-4ac2-dc93-9d849c3c9f31%40hogyros.de. For more options, visit https://groups.google.com/d/optout. signature.asc Description: OpenPGP digital signature
Release Button or best practice
Hello, Does anyone know of any techniques or plugins for triggering a release after a build? I'd like to be able to decide to release any previous build and have that process traceable. Input steps don't suit because it holds back the build feedback. Sometimes it will be a few days after a build when the decision is made to release it. For some projects it's often an arbitrary, human decision so it's hard to come up with some logic to automate this. I've seen examples of hacking in HTML to a build description to trigger another job, but I'm hoping there's a better way. -- 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/270cd0db-c057-44aa-af0f-a925de73fea9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
