Support synchronization of a single Build
Description
Environment
Activity

Mark Rekveld July 11, 2018 at 2:02 PM
I added a story to handle the case where the build number is not provided or in the case its the hourly sync operation, see JJI-487.

Paul Holden July 11, 2018 at 12:35 PM
That would be great We have disabled the hourly synchronization, so just rely on the build completed notification - this presumably contains the build number, so it would be nice if just that build was synchronized, especially for projects with hundreds of builds

Mark Rekveld July 6, 2018 at 9:41 AM
I have not fully flushed out the design for this, but my thinking is to handle synchronization in the following ways.
in case the Jenkins add-on notifies of a build completion
if the notification contains a build number, the only synchronize this build
otherwise, keep with current behaviour and synchronize all builds, new and old.
in case of hourly synchronization, behaviour should be unchanged and continue to synchronize all builds available on Jenkins
I'm also thinking of a better way to handle builds that have been synchronized already, but have not yet found a way for this.

Paul Holden July 6, 2018 at 9:21 AM
Will this resolve the current behaviour, where the plugin re-requests build data for every build in a project when a single build completes (even those that it already knows about)?
Details
Details
Assignee
Reporter

Adding support to synchronize a single build when it completes on Jenkins.