Ok, I did have the jobs set to "Build periodically" and I switched it to "Poll SCM" and used the same schedule, however, it does not seem to have made a difference. The shell code is still being executed, even though there has been no change to than branch since the last event. Any ideas why, as from what has been said, if the poll returned that the commits were the same, nothing else should happen, or am I missing something obvious here?
On Thursday, February 27, 2014 3:59:32 PM UTC-5, LesMikesell wrote: > > On Thu, Feb 27, 2014 at 2:52 PM, Mark Warren > <[email protected]<javascript:>> > wrote: > > Hello all, > > I have quite a few jobs set to run at a specific time, e.g.; once a day, > as > > we only want daily builds for those jobs (other jobs are set to pick up > > changes as commits are made). > > The job will get changes from our git repo, it then executes a shell > script > > with builds the project. > > > > Is there a way to set something, perhaps via a plugin, to not execute > the > > shell script if the last commit hash is the same as the one currently > being > > checked, and thus not do anything. > > > > The script currently has code to check the last commit it built > successfully > > agains the current commit, and if they match, fail the job (issues an > "exit > > 1" command), but that obviously leads to a build failure in the Build > > History and I don't really want that as technically the build has not > > failed, the commit is just the same so it does not need to build it. > > > > Any suggestions or help is greatly appreciated. > > > > Can't you just poll the repository on your schedule instead of > building periodically? If there are no new commits the build won't > run. > > -- > Les Mikesell > [email protected] <javascript:> > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
