Push job synchronization causes blank builds to be saved.
Description
Environment
None
Activity
Show:

Mark Rekveld
changed the StatusMarch 29, 2021 at 3:04 PMIn Progress
Done

Mark Rekveld
updated the Fix versionsMarch 29, 2021 at 3:04 PMNone
server-next

Mark Rekveld
updated the ResolutionMarch 29, 2021 at 3:04 PMNone
Fixed

Mark Rekveld
updated the Fix versionsMarch 29, 2021 at 3:04 PMNone
lite-next

Mark Rekveld
updated the Fix versionsMarch 29, 2021 at 3:04 PMNone
cloud-next

Mark Rekveld
updated the LinkMarch 29, 2021 at 12:52 PMNone
This issue blocks MS-292

Mark Rekveld
updated the RankMarch 29, 2021 at 12:51 PMNone
Ranked higher

Mark Rekveld
changed the AssigneeMarch 29, 2021 at 12:51 PMUnassigned

Mark Rekveld

Mark Rekveld
changed the StatusMarch 29, 2021 at 12:51 PMTo Do
In Progress

Mark Rekveld
updated the RankMarch 29, 2021 at 12:51 PMNone
Ranked higher

Mark Rekveld
updated the RankMarch 29, 2021 at 12:51 PMNone
Ranked higher

Mark Rekveld
changed the StatusMarch 29, 2021 at 12:51 PMBacklog
To Do

Mark Rekveld
created the IssueMarch 29, 2021 at 12:51 PMFixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Mark Rekveld
Mark RekveldReporter
Mark Rekveld
Mark RekveldComponents
Fix versions
Affects versions
Priority
Zoom
Open Zoom
Created March 29, 2021 at 12:51 PM
Updated March 29, 2021 at 3:04 PM
Resolved March 29, 2021 at 3:04 PM
Zoom
When the Jenkins plugin is installed, it will push data to Jira when a job configuration is changed or a description is updated.
As part of the Job synchronization it will also trigger the synchronization of builds available for the job. This can cause blank builds to be synchronized when the job change trigger comes from a private Jenkins site. The data from the job change push only contains the build numbers but on of the other data that is needed.