[HAP-454] Artifactory plugin adds arguments when editing a job configuration while the job is building Created: 24/Oct/13  Updated: 14/Nov/17

Status: Reopened
Project: Jenkins Artifactory Plug-in
Component/s: None
Affects Version/s: 2.1.8
Fix Version/s: 2.2.5

Type: Improvement Priority: Normal
Reporter: Walter Kacynski Assignee: Eyal Ben Moshe (Inactive)
Resolution: Unresolved Votes: 0
Labels: None

Attachments: PNG File HAP-454-arguments-still-show-up-when-editing.png    


Jenkins Core 1.509.4

We use the artifactory plugin and have ant ANT build step defined with a target of [build.all]

When the job is building and we want to change the configuration, the build step will be reflected with targets of [build.all -lib "E:/Jenkins/workspace/artifactory-plugin/2.0.5" -listener org.jfrog.build.extractor.listener.ArtifactoryBuildListener ]

It seems that this information is dynamically entered during build time, however if we click save on a job configuration this information will be persisted. If this happens multiple times, then the job target will contains duplicate copies of this information.


Comment by Jeffrey Johnson [ 07/Jan/15 ]

Adding a Shell build step with a sleep command demonstrates how the extra arguments still show up when editing a job that is running

Comment by Jeffrey Johnson [ 07/Jan/15 ]

This bug is not fixed. I installed the 2.2.5 plugin and created a job and added a "sleep 30" shell build step. Ran the job, waited a few seconds, and edited it. The configuration information was still there. The fix for commit 2947c6c468f48eafde70a5734815d6f3137cceec only prevents the Artifactory listener arguments being added multiple times.

Generated at Fri Feb 28 12:39:06 UTC 2020 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.