Re: Saving infra resources

Anil Belur


With the `trigger-parameterized-builds` macro/plugin does not have a switch which will automagically trigger jobs only if there are none in the queue. The way around this to use the manual way (without the plugin) to trigger builds and build some logic over checking if the jobs are in the queue before triggering. However, once a job is already in the queue (it already been triggered to start with some data from the older AR builds, which is probably outdated), and therefore should remove existing int/dist job from the queue before trigger adds a new int/dist job.  

I'd think this should be fixed in AR/parent job that is triggering these int/dist jobs every day. The question that needs to be answered is if we do need to build AR (and int/dist jobs) every day even if there are no new changes to the project participating in the AR repos

If there is scope for some improvements, I think we should be fix this in both places. 


On Fri, Jan 18, 2019 at 4:36 AM Luis Gomez <ecelgp@...> wrote:

I have observed this a few times now (see attached pic):

The distribution test jobs pile up in Jenkins queue and every one of these takes a lot of infra resources (full distribution CSIT verification). Is there a way for Jenkins to only keep 1 job of this type in the queue? like a new job will remove an old one if this exists in the queue?

integration-dev mailing list

Join { to automatically receive all group messages.