It didn't. After running the standalone job (even multiple times before I
started this thread) I still couldn't run the seed job from master branch
because it was expecting changes from my branch.
I created an issue for this to document this better:
https://issues.apache.org/jira/browse/BEAM-4770.
The outage likely fixed it.
I would have expected running the standalone job with the trigger phrase
should have fixed it. Did it not?
On Wed, Jul 11, 2018 at 8:45 AM Lukasz Cwik wrote:
> I believe there was an outage a few hours ago.
>
> On Wed, Jul 11, 2018 at 8:36 AM Łukasz Gajowy
> wrote:
>
I believe there was an outage a few hours ago.
On Wed, Jul 11, 2018 at 8:36 AM Łukasz Gajowy
wrote:
> It's totally fine. The problem is now gone even though I have taken no
> action to fix it. I suppose Jenkins was restarted?
>
> BTW: Is it restarted only on demand by those who have access, or i
It's totally fine. The problem is now gone even though I have taken no
action to fix it. I suppose Jenkins was restarted?
BTW: Is it restarted only on demand by those who have access, or it's done
once in a while (periodically)?
śr., 11 lip 2018 o 17:07 Lukasz Cwik napisał(a):
> Ah, sorry for m
Ah, sorry for my confusion.
On Tue, Jul 10, 2018 at 4:59 PM Łukasz Gajowy
wrote:
> 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 b
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 napisał(a):
> job_s
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
Hi,
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
thin
