You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On our installation we see an interesting effect: some jobs do not get out of "running" state. This is what gets logged:
App 3347 stdout: Building job 'MyProject'
App 3347 stdout: Obtaining the current build number of 'MyProject'
App 3347 stdout: Job queued for MyProject, will wait up to 30 seconds for build to start...
App 3347 stdout: Obtaining the details of task with ID '684'
App 3347 stdout: Obtaining the details of task with ID '684'
App 3347 stdout: Obtaining the details of task with ID '684'
App 3347 stdout: Obtaining the details of task with ID '684'
App 3347 stdout: Obtaining the details of task with ID '684'
Plugin defintely gets information it waits for. When I click on one of those tasks to see console output I get:
Hello.
On our installation we see an interesting effect: some jobs do not get out of "running" state. This is what gets logged:
Plugin defintely gets information it waits for. When I click on one of those tasks to see console output I get:
So the plugin should know job's done, but it leaves state as "Running".
If you need more details I'll be glad to update this report.
The text was updated successfully, but these errors were encountered: