Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow customisation of 'Details' destination in Github status #79

Closed
Igorshp opened this issue Apr 23, 2015 · 4 comments
Closed

Allow customisation of 'Details' destination in Github status #79

Igorshp opened this issue Apr 23, 2015 · 4 comments

Comments

@Igorshp
Copy link

Igorshp commented Apr 23, 2015

Currently the plugin updates the PullRequest status with link to the specific job (the 'Details' button on the right).
githubstatus
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

@KostyaSha
Copy link
Member

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.

@Igorshp
Copy link
Author

Igorshp commented Apr 23, 2015

@KostyaSha any chance you could link to some examples of configurations/plugins/setups/best_practices on setting up the buildpage

@KostyaSha
Copy link
Member

You can wrote jenkins users maillist.
Also changing link between steps may confuse users in jenkins navigation.

@Memphiz
Copy link
Contributor

Memphiz commented May 8, 2015

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants