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

Update pom.xml #7

Merged
merged 1 commit into from
Jan 20, 2016
Merged

Update pom.xml #7

merged 1 commit into from
Jan 20, 2016

Conversation

jglazner
Copy link
Contributor

Update to version 1.72 of the github-api project that was released on the 10th of Dec 2015.

Update to latest version of the github-api project that was released on the 10th of Dec 2015.
@jenkinsadmin
Copy link
Member

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

@jglazner
Copy link
Contributor Author

@KostyaSha is there anything else that needs to be done here to get this merged and released?

@KostyaSha
Copy link
Member

Please fill jira issue and note why it required.

@jglazner
Copy link
Contributor Author

@KostyaSha this repo doesn't have an issue tracker. I previously filed an issue in the github-api repo which has been resolved (see hub4j/github-api#234). However, I need this bundle to be released with the new version of the github-api so I can use the change in my own jenkins plugin that will depend on this plugin :)

KostyaSha added a commit that referenced this pull request Jan 20, 2016
@KostyaSha KostyaSha merged commit febb760 into jenkinsci:master Jan 20, 2016
@jglazner
Copy link
Contributor Author

@KostyaSha The jenkins build failed due to a dependency download failure because the backend servers were at capacity - can you trigger the build again?

https://jenkins.ci.cloudbees.com/job/plugins/job/github-api-plugin/41/

Relevent Error:
[ERROR] Failed to execute goal on project github-api: Could not resolve dependencies for project org.jenkins-ci.plugins:github-api:hpi:1.72-SNAPSHOT: Failed to collect dependencies at org.jenkins-ci.main:jenkins-core:jar:1.424 -> org.kohsuke.stapler:stapler-adjunct-timeline:jar:1.3 -> org.kohsuke.stapler:stapler:jar:1.214 -> org.kohsuke.stapler:json-lib:jar:2.4-jenkins-2: Failed to read artifact descriptor for org.kohsuke.stapler:json-lib:jar:2.4-jenkins-2: Could not transfer artifact org.kohsuke.stapler:json-lib:pom:2.4-jenkins-2 from/to repo.jenkins-ci.org (http://repo.jenkins-ci.org/public/): Failed to transfer file: http://repo.jenkins-ci.org/public/org/kohsuke/stapler/json-lib/2.4-jenkins-2/json-lib-2.4-jenkins-2.pom. Return code is: 503 , ReasonPhrase:Service Unavailable: Back-end server is at capacity. -> [Help 1]

@KostyaSha
Copy link
Member

i didn't trigger any builds and there is no any snapshots for plugins.

@jglazner
Copy link
Contributor Author

right the maven release plugin should handle all of that, but when you merged the PR it triggered a build which failed due 503's downloading a dependency from repo.jenkins-ci.org. If you can't help, who do i contact to get the plugin released?

@KostyaSha
Copy link
Member

Will do release on weekend.

@jglazner
Copy link
Contributor Author

awesome! Thank you so much!

@KostyaSha
Copy link
Member

Released

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.

3 participants