[
https://issues.apache.org/jira/browse/BEAM-6250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16724373#comment-16724373
]
Scott Wegner commented on BEAM-6250:
------------------------------------
I believe the easiest path forward will be to manually delete the jobs with old
names.
Going forward, I believe having multiple Seed Job definitions generating the
same set of jobs is problematic. My hypothesis is that each job tracks the
history of jobs it previously created separately, which can end up in weird
interactions like this. [This stackoverflow
post|https://stackoverflow.com/a/33880814/33791] provides some details:
bq. Each instance of the Job Dsl plugin tracks what jobs (and views) it
creates. When it is run again, you can configure what it does to jobs (and
views) that were present the previous time this instance was run, but are not
present this time.
> [beam_SeedJob] Failing with "beam_PostCommit_Go already exists"
> ---------------------------------------------------------------
>
> Key: BEAM-6250
> URL: https://issues.apache.org/jira/browse/BEAM-6250
> Project: Beam
> Issue Type: Bug
> Components: test-failures, testing
> Reporter: Scott Wegner
> Assignee: Scott Wegner
> Priority: Major
> Labels: currently-failing
>
> _Use this form to file an issue for test failure:_
> * [Jenkins
> Job|https://builds.apache.org/blue/organizations/jenkins/beam_SeedJob/detail/beam_SeedJob/3151/changes/]
> * [Test source
> code|https://github.com/apache/beam/blob/67d0f787b82aa065c2dc1f67608833e9e3e2215c/.test-infra/jenkins/job_PostCommit_Go.groovy#L27]
> Initial investigation:
> The job started failing on the first scheduled run after
> [PR#7286|https://github.com/apache/beam/pull/7286] went in.
> The failure message is:
> {{...}}
> {{Processing DSL script job_PostCommit_Go.groovy}}
> {{java.lang.IllegalArgumentException: beam_PostCommit_Go already exists}}
> The job succeeded on the [test run from the
> PR|https://builds.apache.org/job/beam_SeedJob/3150/], which shows the new job
> with migratedname (beam_PostCommit_Go). The
> [log|https://builds.apache.org/job/beam_SeedJob/3150/console] lists the old
> job name (beam_PostCommit_Go_GradleBuild) under 'Unreferenced items', and I
> can see that the [job still exists and has recent
> runs|https://builds.apache.org/job/beam_PostCommit_Go_GradleBuild/]
> It seems that the old jobs were [not properly disabled which is the intended
> behavior|https://github.com/apache/beam/blob/67d0f787b82aa065c2dc1f67608833e9e3e2215c/.test-infra/jenkins/job_00_seed.groovy#L110].
> ----
> _After you've filled out the above details, please [assign the issue to an
> individual|https://beam.apache.org/contribute/postcommits-guides/index.html#find_specialist].
> Assignee should [treat test failures as
> high-priority|https://beam.apache.org/contribute/postcommits-policies/#assigned-failing-test],
> helping to fix the issue or find a more appropriate owner. See [Apache Beam
> Post-Commit
> Policies|https://beam.apache.org/contribute/postcommits-policies]._
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
