You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beam.apache.org by Alexey Romanenko <ar...@gmail.com> on 2020/06/08 12:22:27 UTC
Difficulties with triggering PRs Jenkins jobs
Hello,
I think we have an issue, that seems to happen from time to time, to trigger the Jenkins jobs from PRs.
For me, usually, I need to type and enter 2 or even more times the same command as a PR comment (like ‘retest this please’ or at least 'Run Java PreCommit’) to see that it finally started. Sometimes it doesn’t start at all .
Does anyone know what cause this and what we can do to fix/improve it?
Re: Difficulties with triggering PRs Jenkins jobs
Posted by Alexey Romanenko <ar...@gmail.com>.
Tyson, Brian - thanks for details!
> On 8 Jun 2020, at 18:55, Brian Hulette <bh...@google.com> wrote:
>
> Sometimes triggering with a key sentence starts a job based on an earlier commit in the PR branch, and repeatedly trying to trigger can start several jobs validating that same incorrect commit. You can see a yellow circle next to the old commit ID when this happens. On the day of 2.22.0 cut Pablo and I ran into this at the same time on a couple of PRs and blew up the jenkins job queue.
>
> Hopefully the effort Tyson mentioned will resolve that, but in the meantime we should all double-check that we're not creating junk jobs on other commits when furiously attempting to "retest this please".
>
> Brian
>
> On Mon, Jun 8, 2020 at 9:40 AM Tyson Hamilton <tysonjh@google.com <ma...@google.com>> wrote:
> There is an active effort in coordination with the Apache Infrastructure team to move Beam to a new dedicated Jenkins cluster. This will resolve the issues described and add some new functionality as well within the next month.
>
> On Mon, Jun 8, 2020 at 6:29 AM Alexey Romanenko <aromanenko.dev@gmail.com <ma...@gmail.com>> wrote:
> Yes, the key sentences still work. The problem that it triggers jobs in non deterministic way. Sometimes, to run a job, I need to type the same command twice or more times.
>
>> On 8 Jun 2020, at 14:25, Jean-Baptiste Onofre <jb@nanthrax.net <ma...@nanthrax.net>> wrote:
>>
>> Hi,
>>
>>
>> Actually, it’s because of the PR plugin we are using on Jenkins.
>>
>> We have the choice between two plugins:
>> - the "old/deprecated" one that allow key sentence like "retest this please". I’m still using it on projects like Karaf just for that ;)
>> - the "new" plugin just trigger build when the PR is created or updated (push forced), but it doesn’t support (yet) key sentence
>>
>> Regards
>> JB
>>
>>> Le 8 juin 2020 à 14:22, Alexey Romanenko <aromanenko.dev@gmail.com <ma...@gmail.com>> a écrit :
>>>
>>> Hello,
>>>
>>> I think we have an issue, that seems to happen from time to time, to trigger the Jenkins jobs from PRs.
>>>
>>> For me, usually, I need to type and enter 2 or even more times the same command as a PR comment (like ‘retest this please’ or at least 'Run Java PreCommit’) to see that it finally started. Sometimes it doesn’t start at all .
>>>
>>> Does anyone know what cause this and what we can do to fix/improve it?
>>
>
Re: Difficulties with triggering PRs Jenkins jobs
Posted by Brian Hulette <bh...@google.com>.
Sometimes triggering with a key sentence starts a job based on an earlier
commit in the PR branch, and repeatedly trying to trigger can start several
jobs validating that same incorrect commit. You can see a yellow circle
next to the old commit ID when this happens. On the day of 2.22.0 cut Pablo
and I ran into this at the same time on a couple of PRs and blew up the
jenkins job queue.
Hopefully the effort Tyson mentioned will resolve that, but in the meantime
we should all double-check that we're not creating junk jobs on other
commits when furiously attempting to "retest this please".
Brian
On Mon, Jun 8, 2020 at 9:40 AM Tyson Hamilton <ty...@google.com> wrote:
> There is an active effort in coordination with the Apache Infrastructure
> team to move Beam to a new dedicated Jenkins cluster. This will resolve the
> issues described and add some new functionality as well within the next
> month.
>
> On Mon, Jun 8, 2020 at 6:29 AM Alexey Romanenko <ar...@gmail.com>
> wrote:
>
>> Yes, the key sentences still work. The problem that it triggers jobs in
>> non deterministic way. Sometimes, to run a job, I need to type the same
>> command twice or more times.
>>
>> On 8 Jun 2020, at 14:25, Jean-Baptiste Onofre <jb...@nanthrax.net> wrote:
>>
>> Hi,
>>
>>
>> Actually, it’s because of the PR plugin we are using on Jenkins.
>>
>> We have the choice between two plugins:
>> - the "old/deprecated" one that allow key sentence like "retest this
>> please". I’m still using it on projects like Karaf just for that ;)
>> - the "new" plugin just trigger build when the PR is created or updated
>> (push forced), but it doesn’t support (yet) key sentence
>>
>> Regards
>> JB
>>
>> Le 8 juin 2020 à 14:22, Alexey Romanenko <ar...@gmail.com> a
>> écrit :
>>
>> Hello,
>>
>> I think we have an issue, that seems to happen from time to time, to
>> trigger the Jenkins jobs from PRs.
>>
>> For me, usually, I need to type and enter 2 or even more times the same
>> command as a PR comment (like ‘retest this please’ or at least 'Run Java
>> PreCommit’) to see that it finally started. Sometimes it doesn’t start
>> at all .
>>
>> Does anyone know what cause this and what we can do to fix/improve it?
>>
>>
>>
>>
Re: Difficulties with triggering PRs Jenkins jobs
Posted by Tyson Hamilton <ty...@google.com>.
There is an active effort in coordination with the Apache Infrastructure
team to move Beam to a new dedicated Jenkins cluster. This will resolve the
issues described and add some new functionality as well within the next
month.
On Mon, Jun 8, 2020 at 6:29 AM Alexey Romanenko <ar...@gmail.com>
wrote:
> Yes, the key sentences still work. The problem that it triggers jobs in
> non deterministic way. Sometimes, to run a job, I need to type the same
> command twice or more times.
>
> On 8 Jun 2020, at 14:25, Jean-Baptiste Onofre <jb...@nanthrax.net> wrote:
>
> Hi,
>
>
> Actually, it’s because of the PR plugin we are using on Jenkins.
>
> We have the choice between two plugins:
> - the "old/deprecated" one that allow key sentence like "retest this
> please". I’m still using it on projects like Karaf just for that ;)
> - the "new" plugin just trigger build when the PR is created or updated
> (push forced), but it doesn’t support (yet) key sentence
>
> Regards
> JB
>
> Le 8 juin 2020 à 14:22, Alexey Romanenko <ar...@gmail.com> a
> écrit :
>
> Hello,
>
> I think we have an issue, that seems to happen from time to time, to
> trigger the Jenkins jobs from PRs.
>
> For me, usually, I need to type and enter 2 or even more times the same
> command as a PR comment (like ‘retest this please’ or at least 'Run Java
> PreCommit’) to see that it finally started. Sometimes it doesn’t start at
> all .
>
> Does anyone know what cause this and what we can do to fix/improve it?
>
>
>
>
Re: Difficulties with triggering PRs Jenkins jobs
Posted by Alexey Romanenko <ar...@gmail.com>.
Yes, the key sentences still work. The problem that it triggers jobs in non deterministic way. Sometimes, to run a job, I need to type the same command twice or more times.
> On 8 Jun 2020, at 14:25, Jean-Baptiste Onofre <jb...@nanthrax.net> wrote:
>
> Hi,
>
>
> Actually, it’s because of the PR plugin we are using on Jenkins.
>
> We have the choice between two plugins:
> - the "old/deprecated" one that allow key sentence like "retest this please". I’m still using it on projects like Karaf just for that ;)
> - the "new" plugin just trigger build when the PR is created or updated (push forced), but it doesn’t support (yet) key sentence
>
> Regards
> JB
>
>> Le 8 juin 2020 à 14:22, Alexey Romanenko <aromanenko.dev@gmail.com <ma...@gmail.com>> a écrit :
>>
>> Hello,
>>
>> I think we have an issue, that seems to happen from time to time, to trigger the Jenkins jobs from PRs.
>>
>> For me, usually, I need to type and enter 2 or even more times the same command as a PR comment (like ‘retest this please’ or at least 'Run Java PreCommit’) to see that it finally started. Sometimes it doesn’t start at all .
>>
>> Does anyone know what cause this and what we can do to fix/improve it?
>
Re: Difficulties with triggering PRs Jenkins jobs
Posted by Jean-Baptiste Onofre <jb...@nanthrax.net>.
Hi,
Actually, it’s because of the PR plugin we are using on Jenkins.
We have the choice between two plugins:
- the "old/deprecated" one that allow key sentence like "retest this please". I’m still using it on projects like Karaf just for that ;)
- the "new" plugin just trigger build when the PR is created or updated (push forced), but it doesn’t support (yet) key sentence
Regards
JB
> Le 8 juin 2020 à 14:22, Alexey Romanenko <ar...@gmail.com> a écrit :
>
> Hello,
>
> I think we have an issue, that seems to happen from time to time, to trigger the Jenkins jobs from PRs.
>
> For me, usually, I need to type and enter 2 or even more times the same command as a PR comment (like ‘retest this please’ or at least 'Run Java PreCommit’) to see that it finally started. Sometimes it doesn’t start at all .
>
> Does anyone know what cause this and what we can do to fix/improve it?