You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Kenneth Knowles <kl...@google.com.INVALID> on 2016/12/01 07:57:52 UTC
Jenkins precommit worker affinity
It appears that the new job beam_PreCommit_Java_MavenInstall has an
affinity for Jenkins worker beam3 while workers beam1 and beam2 sit idle.
Is this intentional? There seems to be a backlog of half a dozen builds.
Re: Jenkins precommit worker affinity
Posted by Jason Kuster <ja...@google.com.INVALID>.
Will do.
On Thu, Dec 1, 2016 at 12:06 AM, Davor Bonaci <da...@apache.org> wrote:
> Configuration fixed. The problem was job parallelism, not affinity.
>
> Jason, can you fix this in your pending PR?
>
> On Wed, Nov 30, 2016 at 11:57 PM, Kenneth Knowles <kl...@google.com.invalid>
> wrote:
>
>> It appears that the new job beam_PreCommit_Java_MavenInstall has an
>> affinity for Jenkins worker beam3 while workers beam1 and beam2 sit idle.
>> Is this intentional? There seems to be a backlog of half a dozen builds.
>>
>
>
--
-------
Jason Kuster
Apache Beam (Incubating) / Google Cloud Dataflow
Re: Jenkins precommit worker affinity
Posted by Davor Bonaci <da...@apache.org>.
Configuration fixed. The problem was job parallelism, not affinity.
Jason, can you fix this in your pending PR?
On Wed, Nov 30, 2016 at 11:57 PM, Kenneth Knowles <kl...@google.com.invalid>
wrote:
> It appears that the new job beam_PreCommit_Java_MavenInstall has an
> affinity for Jenkins worker beam3 while workers beam1 and beam2 sit idle.
> Is this intentional? There seems to be a backlog of half a dozen builds.
>