On 2 August 2017 at 13:28, Guillaume Smet wrote:
> On Wed, Aug 2, 2017 at 1:21 PM, Sanne Grinovero wrote:
>>
>> This might work for HV but please don't do this generally?
>> Concurrently running builds will fail because of conflicting resource
>> usage,
>> and we had plenty of cases in which some
On Wed, Aug 2, 2017 at 1:21 PM, Sanne Grinovero wrote:
> This might work for HV but please don't do this generally?
> Concurrently running builds will fail because of conflicting resource
> usage,
> and we had plenty of cases in which some ports are needd which you
> didn't even know about.
>
At
On 2 August 2017 at 12:13, Guillaume Smet wrote:
> The website jobs are not the only ones that need to be prioritized: the
> release jobs should also be prioritized.
Good point.
>
> When you do a release, it's really a pain to wait for all the other jobs to
> finish.
>
> Currently, I set a weigh
The website jobs are not the only ones that need to be prioritized: the
release jobs should also be prioritized.
When you do a release, it's really a pain to wait for all the other jobs to
finish.
Currently, I set a weight of 2 for the BV/HV release jobs so that they can
also be prioritized.
No
Thank for the IRC logs. To comment on the Jenkins vs 5 Executors "trick":
if it's too limiting +1 to remove this but please always allow a
website release to allow "right now", sometimes it's really urgent and
even waiting a couple of fast jobs is very stressful.
A simple solution - and actually
