[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Broken seed job

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.gajowy@xxxxxxxxx> wrote:

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 [1] and here [2].

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). 

[1] https://github.com/apache/beam/pull/5915
[2] https://builds.apache.org/view/A-D/view/Beam/job/beam_SeedJob/2190/console  

Best regards,