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
Currently the plugin updates the PullRequest status with link to the specific job (the 'Details' button on the right).
Most of the time, when a job fails, the user will want to go to console to find out the reason and with current setup that requires 2 clicks, 2 page loads.
I believe the workflow can be simplified by allowing the endpoint destination to be changed in global config depending on job result status.
for example:
job created - link to job
job succeeded - link to job
job failed - link to console
The text was updated successfully, but these errors were encountered:
Good configured jobs and builds provides all needed info (failed tests, static analysing, etc) on the build page. Navigation to console is your single use case.
Consider matrix jobs or multijobs ... there is no single console output to jump to. Please don't change current behavior of this link. Jumping to the buildpage is the right thing to do.
Currently the plugin updates the PullRequest status with link to the specific job (the 'Details' button on the right).
Most of the time, when a job fails, the user will want to go to console to find out the reason and with current setup that requires 2 clicks, 2 page loads.
I believe the workflow can be simplified by allowing the endpoint destination to be changed in global config depending on job result status.
for example:
job created - link to job
job succeeded - link to job
job failed - link to console
The text was updated successfully, but these errors were encountered: