Ah, sorry for my confusion.
On Tue, Jul 10, 2018 at 4:59 PM Łukasz Gajowy <lukasz.gaj...@gmail.com>
> I didn't edit the "Standalone Seed job", only the "SeedJob". Now every
> time someone tries to run the seed job ("Run seed job") it results in an
> error even despite prior running the standalone job from master branch the
> way you described.
> śr., 11 lip 2018 o 01:25 Lukasz Cwik <lc...@google.com> napisał(a):
>> job_seed_standalone should only be edited when we know that the regular
>> seed job is in a healthy state.
>> Note, that you can always recover back to what is checked in master by:
>> 1) Creating an empty PR
>> 2) Using the standalone seed job trigger phrase: "Run Standalone Seed Job"
>> I kicked one off right now:
>> On Tue, Jul 10, 2018 at 4:17 PM Łukasz Gajowy <lukasz.gaj...@gmail.com>
>>> while working on Jenkins' seed job, some changes I introduced didn't get
>>> reverted even after running the seed job again from the master branch. This
>>> is why seed job is now failing. More details here  and here .
>>> Since I can operate only with jobs phrase-triggered from GitHub's PR, I
>>> think there's nothing more I can do than I already tried. In my
>>> opinion, fixing this issue requires an aid of a person with some greater
>>> access to Jenkins. Can someone help with that?
>>> Sorry for the inconvenience - I didn't expect that such situation can
>>> occur. "job_seed_standalone" works fine and it can be used instead
>>> (until the issue is fixed).
>>>  https://github.com/apache/beam/pull/5915
>>> Best regards,