• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • p4-plugin
    • None

      I experiencing the same problem regarding double (or even multiple) display of "Label This Build" as it is described inside JENKINS-30425 (see p4plugin-changelog-missing-3.png).

      Since this old issue has solved the other reported problem this new issue shall track the "Label This Build" problem.

      Inside the the folder for that build /var/lib/jenkins/jobs/.../builds/2 I see two changelog files:

      • changelog0.xml
      • changelog1.xml

      They are identical (verified using diff).

      That might also be the reason why I also see duplicate change entries?

          [JENKINS-39096] duplicate display of "Label This Build"

          Ilya Gorban added a comment - - edited

          Hi!
          I had the same issue - when building in parallel (pipeline + parallel step), after sync via:

          checkout $class: 'PerforceScm', ...
          

          I'm getting duplicate set of changelists + duplicate display of 'label this build'.
          Thank you,
          Ilya

          Ilya Gorban added a comment - - edited Hi! I had the same issue - when building in parallel (pipeline + parallel step), after sync via: checkout $class: 'PerforceScm' , ... I'm getting duplicate set of changelists + duplicate display of 'label this build'. Thank you, Ilya

          Phil McArdle added a comment -

          I also see duplicate displays of 'Label This Build' when using Perforce in parallel jobs, although in my case they're slightly more justified.

          In my scenario, I fetch a shared library from Git, and run Perforce on 3 different workspaces in parallel (although, against the same path and CL). So I now have 4 links to 'Label This Build', however all 4 of them only target the Git repository, and none of them are for Perforce.

          I'm not really sure against which component to report the latter bug though.

          Phil McArdle added a comment - I also see duplicate displays of 'Label This Build' when using Perforce in parallel jobs, although in my case they're slightly more justified. In my scenario, I fetch a shared library from Git, and run Perforce on 3 different workspaces in parallel (although, against the same path and CL). So I now have 4 links to 'Label This Build', however all 4 of them only target the Git repository, and none of them are for Perforce. I'm not really sure against which component to report the latter bug though.

          Jay Spang added a comment -

          I'm seeing this same issue. My hypothesis is that the plugin shows a "Label this build" link for every changelog.xml find found (despite all links doing exactly the same thing). In my case, my job actually pulls several things from Perforce:

          1. The Jenkinsfile itself comes from Perforce
          2. I use a shared Library which also comes from Perforce
          3. lastly, the job's source code itself comes from Perforce

          The result is that each build contains 4 identical "Label this build" links (I think the last one might come from polling)?

          Jay Spang added a comment - I'm seeing this same issue. My hypothesis is that the plugin shows a "Label this build" link for every changelog.xml find found (despite all links doing exactly the same thing). In my case, my job actually pulls several things from Perforce: The Jenkinsfile itself comes from Perforce I use a shared Library which also comes from Perforce lastly, the job's source code itself comes from Perforce The result is that each build contains 4 identical "Label this build" links (I think the last one might come from polling)?

          Simon Watts added a comment -

          Seeing the same as jayspang – except one project now has eight (8) changelog*.xml and same number of 'Label This Build' links.  The changelog*.xml files come in three (3) different contents (1,2,5), and the 'Label This Build' links appear in groups of 1,2, and 5 amongst the sidebar links (not all in one block).  ...so there are multiple correlations.

          We also pull a Jenkinsfile and common library from Perforce, but also build on two different platforms.  Other stages may use additional agents, although there should only be the Jenkins master and one slave in use.

          The Jenkinsfile is declarative, and we don't explicitly checkout anything from Perforce ourselves.

           

          • Jenkins version 2.89.2
          • P4 Plugin version 1.8.4

          Simon Watts added a comment - Seeing the same as jayspang – except one project now has eight (8) changelog*.xml and same number of 'Label This Build' links.  The  changelog*.xml files come in three (3) different contents (1,2,5), and the 'Label This Build' links appear in groups of 1,2, and 5 amongst the sidebar links (not all in one block).  ...so there are multiple correlations. We also pull a Jenkinsfile and common library from Perforce, but also build on two different platforms.  Other stages may use additional agents, although there should only be the Jenkins master and one slave in use. The Jenkinsfile is declarative, and we don't explicitly checkout anything from Perforce ourselves.   Jenkins version 2.89.2 P4 Plugin version 1.8.4

            Unassigned Unassigned
            heiko_nardmann Heiko Nardmann
            Votes:
            7 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: