Re: Broken seed job
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. I left it unassigned -
feel free to take this.
Thanks,
Łukasz
śr., 11 lip 2018 o 20:25 Alan Myrvold napisał(a):
> 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:
>>
>>> 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 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 branch the
> way you described.
>
>
>
> śr., 11 lip 2018 o 01:25 Lukasz Cwik 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:
>>
>> https://builds.apache.org/view/A-D/view/Beam/job/beam_SeedJob_Standalone/1289/
>>
>> On Tue, Jul 10, 2018 at 4:17 PM Łukasz Gajowy <
>> lukasz.gaj...@gmail.com> wrote:
>>
>>> 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 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,
>>> Łukasz
>>>
>>
Re: Broken seed job
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:
>
>> 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 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 branch the
way you described.
śr., 11 lip 2018 o 01:25 Lukasz Cwik 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:
>
> https://builds.apache.org/view/A-D/view/Beam/job/beam_SeedJob_Standalone/1289/
>
> On Tue, Jul 10, 2018 at 4:17 PM Łukasz Gajowy
> wrote:
>
>> 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 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,
>> Łukasz
>>
>
Re: Broken seed job
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 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 branch the
>> way you described.
>>
>>
>>
>> śr., 11 lip 2018 o 01:25 Lukasz Cwik 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:
>>>
>>> https://builds.apache.org/view/A-D/view/Beam/job/beam_SeedJob_Standalone/1289/
>>>
>>> On Tue, Jul 10, 2018 at 4:17 PM Łukasz Gajowy
>>> wrote:
>>>
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 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,
Łukasz
>>>
Re: Broken seed job
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 branch the
> way you described.
>
>
>
> śr., 11 lip 2018 o 01:25 Lukasz Cwik 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:
>>
>> https://builds.apache.org/view/A-D/view/Beam/job/beam_SeedJob_Standalone/1289/
>>
>> On Tue, Jul 10, 2018 at 4:17 PM Łukasz Gajowy
>> wrote:
>>
>>> 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
>>> 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,
>>> Łukasz
>>>
>>
Re: Broken seed job
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_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:
>
> https://builds.apache.org/view/A-D/view/Beam/job/beam_SeedJob_Standalone/1289/
>
> On Tue, Jul 10, 2018 at 4:17 PM Łukasz Gajowy
> wrote:
>
>> 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
>> 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,
>> Łukasz
>>
>
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: https://builds.apache.org/view/A-D/view/Beam/job/beam_SeedJob_Standalone/1289/ On Tue, Jul 10, 2018 at 4:17 PM Łukasz Gajowy wrote: > 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 > 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, > Łukasz >
Broken seed job
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 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, Łukasz
