Well done, thanks a lot.
On Fri, Jan 12, 2018 at 8:12 AM, Yoann Rodiere wrote:
> Quick update: the priority plugin seems to be working fine, and I disabled
> the Heavy Job plugin. It turns out the Heavy Job plugin was preventing the
> Amazon EC2 plugin to spin up new
Quick update: the priority plugin seems to be working fine, and I disabled
the Heavy Job plugin. It turns out the Heavy Job plugin was preventing the
Amazon EC2 plugin to spin up new slaves, probably because the Amazon EC2
plugin only saw two empty slots on an existing slave and couldn't
I know ;)
Anyway I do agree that any release jobs should be given the highest
priority in the job queue
On Wed, Jan 10, 2018, 10:29 AM Guillaume Smet
wrote:
> On Wed, Jan 10, 2018 at 5:00 PM, Steve Ebersole
> wrote:
>
>> And in advance I say I
On Wed, Jan 10, 2018 at 5:00 PM, Steve Ebersole wrote:
> And in advance I say I would not be cool with you killing my jobs for your
> job to run
>
Yeah, that was my understanding.
I don't expect anyone to be cool with it.
___
And in advance I say I would not be cool with you killing my jobs for your
job to run
On Wed, Jan 10, 2018 at 9:52 AM Sanne Grinovero wrote:
> On 10 January 2018 at 11:33, Guillaume Smet
> wrote:
> > On Wed, Jan 10, 2018 at 12:08 PM, Sanne
On 10 January 2018 at 11:33, Guillaume Smet wrote:
> On Wed, Jan 10, 2018 at 12:08 PM, Sanne Grinovero
> wrote:
>>
>> Some of our test suites used to take 2 hours to run (even 5 days some
>> years ago); now you say waiting 20 minutes is not good
On Wed, Jan 10, 2018 at 12:08 PM, Sanne Grinovero
wrote:
> Some of our test suites used to take 2 hours to run (even 5 days some
> years ago); now you say waiting 20 minutes is not good enough? You'll
> have to optimise our code better :P
>
What I'm saying is that in the
> Let's not forget that many Apache projects take a week or two to
> perform a release, we all know of other projects needing months, so by
> the law of diminishing returns I don't think we should invest much
> more of out time to shave on the 10 minutes.. just spin up some extra
> nodes :)
+1
On 10 January 2018 at 10:25, Guillaume Smet wrote:
> Hi,
>
> On Wed, Jan 10, 2018 at 11:06 AM, Yoann Rodiere wrote:
>>
>> I hope we will be able to use this priority feature instead of the Heavy
>> Job plugin (which allows to assign weights to
Hi,
On Wed, Jan 10, 2018 at 11:06 AM, Yoann Rodiere wrote:
>
> I hope we will be able to use this priority feature instead of the Heavy
> Job plugin (which allows to assign weights to jobs), and avoid concurrent
> builds completely. With the current setup, someone releasing
Hello,
TL;DR: I installed a plugin to prioritize Jenkins jobs, please let me know
if you notice anything wrong. Also, I will remove the Heavy Job plugin
soon, let me know if you're not okay with that.
I recently raised the issue on HipChat that some Jenkins builds are
triggered in batch,
11 matches
Mail list logo