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

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.

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)?

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