Hi Rachel, Thanks for your answer. No that's not it. I'm running a pipeline but it could be manual execution as well and basically I want the ability the say my shell script is conditional and should only run if there was a change in the source. Regardless of how the build was triggered.
Thanks, Peter Get Outlook for Android<https://aka.ms/ghei36> On Tue, Oct 18, 2016 at 8:28 PM +0100, "Rachel" <raquel.moreno.carm...@gmail.com<mailto:raquel.moreno.carm...@gmail.com>> wrote: Hi Teichner, I don't know if I've understood you correctly, but I usually configure my jobs with: * Build Triggers > Poll SCM With this option you specify when you want to check your SCM (e.g. hourly, every 2 hours, ...) and a new build is executed only if changes are detected from the last build. Is that you're looking for? Best regards, Rachel El martes, 18 de octubre de 2016, 11:22:35 (UTC+2), Teichner Peter escribió: I’m trying to find the right solution for using a conditional multiple build step depending if there was a code change. I have seen a solution by checking ROOT_BUILD_CAUSE but that might be unreliable as the execution could be manually triggered but there could still be code change. I need this so I wont build the software unless there was an actual change in the code change. Thanks in advance. -- 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/631E36F203287D68.4e80c18c-c88a-4951-8451-671343570ed6%40mail.outlook.com. For more options, visit https://groups.google.com/d/optout.
