-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins 2.89.4
BuildMaster 5.8.3
Jenkins BuildMaster plugin - 1.6
Somehow at the end of a build run the plugin will query BuildMaster. It first queries to get the applications, then it queries the app for it's releases and deployables.
It does this over and over and over. For the same app, same deployable. At the point in the Job where this runs the plugin is not being used, it had already been ran earlier in the job.
This doesn't happen all the time it seems to only occur if the job's configuration is changed and that change doesn't involve changing anything to do with BuildMaster plugin.
Since we have a lot of apps on BuildMaster this causes a build run to take a lot of extra time.
[JENKINS-50976] At end of build plugin is querying BuildMaster for apps deployable info
Jon Starbird
created issue -
Jon Starbird
made changes -
| Summary | Original: At end of build plugin is querying BuildMaster for every apps deployable info | New: At end of build plugin is querying BuildMaster for apps deployable info |
Jon Starbird
made changes -
| Description |
Original:
Somehow at the end of a build run the plugin will query BuildMaster. It first queries to get all the applications, then it queries each app for it's releases and deployables. It does this for Every app on BuildMaster even though this job is configured for only 1 app. This doesn't happen all the time it seems to only occur if the job's configuration is changed and that change doesn't involve changing anything to do with BuildMaster plugin. Since we have a lot of apps on BuildMaster this causes a build run to take a lot of extra time. |
New:
Somehow at the end of a build run the plugin will query BuildMaster. It first queries to get the applications, then it queries the app for it's releases and deployables. It does this over and over and over. For the same app, same deployable. This doesn't happen all the time it seems to only occur if the job's configuration is changed and that change doesn't involve changing anything to do with BuildMaster plugin. Since we have a lot of apps on BuildMaster this causes a build run to take a lot of extra time. |
Jon Starbird
made changes -
| Description |
Original:
Somehow at the end of a build run the plugin will query BuildMaster. It first queries to get the applications, then it queries the app for it's releases and deployables. It does this over and over and over. For the same app, same deployable. This doesn't happen all the time it seems to only occur if the job's configuration is changed and that change doesn't involve changing anything to do with BuildMaster plugin. Since we have a lot of apps on BuildMaster this causes a build run to take a lot of extra time. |
New:
Somehow at the end of a build run the plugin will query BuildMaster. It first queries to get the applications, then it queries the app for it's releases and deployables. It does this over and over and over. For the same app, same deployable. At the point in the Job where this runs the plugin is not being used, it had already been ran earlier in the job. This doesn't happen all the time it seems to only occur if the job's configuration is changed and that change doesn't involve changing anything to do with BuildMaster plugin. Since we have a lot of apps on BuildMaster this causes a build run to take a lot of extra time. |
Andrew Sumner
added a comment - Is this still happening or can the issue be closed? Jon Starbird
added a comment - I haven't seen it recently but It wasn't happening all the time. Go ahead and close this out, I think, if you want, and if it happens again I can submit a new one.
Jon Starbird
added a comment - I haven't seen it recently but It wasn't happening all the time. Go ahead and close this out, I think, if you want, and if it happens again I can submit a new one. Andrew Sumner
made changes -
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Andrew Sumner
made changes -
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
Andrew Sumner
made changes -
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
I cannot say why this might be happening - hopefully it goes away with this new version of the application but I make no promises... If it still remains an issue we can look into this further.