Re: Inconsistent jenkins workers

Sounds good, thanks for the update. And thanks especially to Pablo for pushing https://github.com/apache/beam/pull/5149 through in the meantime. On Mon, Apr 16, 2018 at 4:38 PM Yifan Zou wrote: > Thanks Jason for explanation. I am working on Jenkins containerization and trying to figure out a way

Re: Inconsistent jenkins workers

Thanks Jason for explanation. I am working on Jenkins containerization and trying to figure out a way to smoothly update OS and build consistent Jenkins environment. On Mon, Apr 16, 2018 at 4:23 PM Jason Kuster wrote: > To provide slightly more context here, we do have some ability to change >

Re: Inconsistent jenkins workers

To provide slightly more context here, we do have some ability to change what's on the build machines (they're puppetized and the configurations are available at https://github.com/apache/infrastructure-puppet), but the image that they're running is Ubuntu 14.04, and some latest versions of things

Re: Inconsistent jenkins workers

Hi all, So does it make sense to send out a change to make PreCommits run in beam[1-3] only for now? Since this is likely blocking python work right now. Or is there a way to manually select the jenkins machine to run on? Best -P. On Mon, Apr 16, 2018 at 4:02 PM Yifan Zou wrote: > Those machine

Re: Inconsistent jenkins workers

Those machines are managed by apache-infra, that we are not able to install/update tools on them. We plan to have a new instance group for beam Jenkins since we are required to update OS to the latest Ubuntu. With fresh, supportive dependencies installed on new machines could also get rid of restri

Re: Inconsistent jenkins workers

Thanks. In the short term, I could try to limit precommits to these two machines following that example, but presumably that would mean longer queues. Who owns these machines? Could we just wipe them and install fresh, modern, consistent OS/environments on them? (The container story seems like a g

Re: Inconsistent jenkins workers

The Jenkins worker configurations is a pain point of beam build and tests, and it is indeed difficult to debug. Originally, python tests such as beam_PostCommit_Python_Verify only run on one worker due to BEAM-1817 . We