Skip to content

[FIXED JENKINS-23995] Set context for GH status#50

Merged
oleg-nenashev merged 1 commit intojenkinsci:masterfrom
KostyaSha:JENKINS-23995
Feb 25, 2015
Merged

[FIXED JENKINS-23995] Set context for GH status#50
oleg-nenashev merged 1 commit intojenkinsci:masterfrom
KostyaSha:JENKINS-23995

Conversation

@KostyaSha
Copy link
Member

supersede #47

@KostyaSha
Copy link
Member Author

@janpapenbrock please test this hpi (press green checkbox and then click on "module builds")

@janpapenbrock
Copy link

Thanks very much for your effort. Still have a similar result, but the names have changed: https://raw.githubusercontent.com/janpapenbrock/github-plugin-test/master/3-notifications.png

While we are at it, I have a probem with getting the SHA1 to be set correctly in downstream builds - I have to clone it again although it was cloned upstream. This is probably a different issue, but its quite near in the code I guess. Should be this https://github.com/KostyaSha/github-plugin/blob/JENKINS-23995/src/main/java/com/cloudbees/jenkins/GitHubCommitNotifier.java#L102

Maybe this is related to the problem seen here?!?

@KostyaSha
Copy link
Member Author

@janpapenbrock have you added new commit to branch where you testing statuses?

@janpapenbrock
Copy link

Yes, I did.

@janpapenbrock
Copy link

The Github API documentation says at https://developer.github.com/v3/repos/statuses/#create-a-status:

context string A string label to differentiate this status from the status of other systems. Default: "default"

So maybe this issue is related to the API implementation?

@KostyaSha
Copy link
Member Author

@janpapenbrock stop guessing ;)
Status is set multiple times, i trusted initial PR code. Now should work right. Wait PR build results and test new hpi.

@janpapenbrock
Copy link

Great thanks ;)

@KostyaSha KostyaSha closed this Feb 20, 2015
@KostyaSha KostyaSha reopened this Feb 20, 2015
@KostyaSha
Copy link
Member Author

PR builds fixed, new hpi is available

@jenkinsadmin
Copy link
Member

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

@janpapenbrock
Copy link

@KostyaSha
Copy link
Member Author

Cool, need +1 from some other dev and will merge.

@KostyaSha KostyaSha added this to the github-1.11 milestone Feb 21, 2015
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any reasons to change the DisplayName to the project's full name. In such cases the status info will lose the information about the build.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, where this info displayed?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed and tested, result is here KostyaSha/test-repo#20

@KostyaSha
Copy link
Member Author

@kohsuke @oleg-nenashev i will merge and release this state if i will get no replies in the next day.

oleg-nenashev added a commit that referenced this pull request Feb 25, 2015
[FIXED JENKINS-23995] Set context for GH status
@oleg-nenashev oleg-nenashev merged commit 598565c into jenkinsci:master Feb 25, 2015
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

Successfully merging this pull request may close these issues.

4 participants

Comments