I was more thinking of saving resources, and unnecessary emails, rebuilding a project that has not changed (for weeks) is just an unnecessary overhead. Doing a SCM pole is much less.
Cheers Greg. On 23 January 2015 at 10:32, Glen Mazza <glen.ma...@gmail.com> wrote: > I'm unsure what the other projects do but I think the status quo is OK. > We only get a message that everything is OK after a failure, and sometimes > it's good to get failures because they point to problems outside of the > code but in the Jenkins process. We may go another three weeks with no > emails due to consecutive success builds. > > Glen > > On 01/23/2015 03:59 AM, Greg Huber wrote: > >> Can we not poll the SCM and if there are changes do the build, rather than >> running it every day regardless of changes? >> >> Cheers Greg. >> >> >> ---------- Forwarded message ---------- >> From: Apache Jenkins Server <jenk...@builds.apache.org> >> Date: 23 January 2015 at 08:55 >> Subject: Jenkins build is back to normal : Roller #1498 >> To: dev@roller.apache.org, glen.ma...@gmail.com >> >> >> See <https://builds.apache.org/job/Roller/1498/> >> >> >
