You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2022/01/12 03:50:07 UTC

[jira] [Updated] (BEAM-4770) Standalone seed job didn't revert Jenkins seed job changes introduced by a PR

     [ https://issues.apache.org/jira/browse/BEAM-4770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-4770:
----------------------------------

This Jira ticket has a pull request attached to it, but is still open. Did the pull request resolve the issue? If so, could you please mark it resolved? This will help the project have a clear view of its open issues.

> Standalone seed job didn't revert Jenkins seed job changes introduced by a PR
> -----------------------------------------------------------------------------
>
>                 Key: BEAM-4770
>                 URL: https://issues.apache.org/jira/browse/BEAM-4770
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: Lukasz Gajowy
>            Priority: P3
>
> +What was the setup?+
> I created Pull Request (let's call it "A") of a branch with some changes in job__00_seed.groovy. Those changes involved adding a new glob pattern to detect files not only with job_*.groovy naming pattern but also with /**/*Job.groovy.
> I created another PR (let's call it "B") which was "empty" - no changes added to the codebase. I used such PR to run job_seed_standalone (or job_00_seed) from master branch to revert changes introduced by A.
> So:
>  - to introduce change I ran: "Run seed job" in pr A's comment
>  - to revert changes I ran: "Run seed job" / "Run seed job standalone" in pr B's comment. 
>  
> +What did I expect?+
> I expected every change introduced in the seed job by A reverted by B's standalone seed job. I even expected that B's seed job will revert the changes.
> +What actually happened?+
> After running standalone seed job from "B" some changes were not reverted. Jenkins was still expecting files with *Job. glob pattern when I was running the seed job afterwards. It couldn't find them on master so it resulted in the following error: 
> {code:java}
> Resetting working tree
>  > git reset --hard # timeout=10
>  > git clean -fdx # timeout=10
> ERROR: no Job DSL script(s) found at .test-infra/jenkins/**/*Job.groovy
> Not sending mail to unregistered user cclauss@bluewin.ch
> Sending e-mails to: dev@beam.apache.org pabloem@google.com
> Setting status of 4715449665ae235f96c7a67ce5f80b774d5474e5 to FAILURE with url https://builds.apache.org/job/beam_SeedJob/2191/ and message: 'FAILURE
>  '
> Using context: Jenkins: Seed Job
> Finished: FAILURE
> {code}
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)