That instance does not build the plugin for release, it just runs the tests
for visibility on Pull Requests.
When releasing, I have always just run that locally, following the
instructions here:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Releasingtojenkinsci.org
Hello,
Thanks for accepting me.
How can I have access to the Jenkins instance which builds the plugin
https://jenkins.ci.cloudbees.com/job/plugins/job/gitlab-plugin/ ?
joi, 5 ianuarie 2017, 00:15:28 UTC+2, Owen B. Mehegan a scris:
>
> Thanks for your interest! I have given you commit access.
Managed to fix it.
A project dependency was requiring guava 18.0, but jenkis-core was fetching
11.0.1. To fix it I had to exclude guava from jenkins-core:
org.jenkins-ci.main
jenkins-core
com.google.guava
guava
Hello Martin,
I have final year student of computer science
background. I have worked at certain giants and have majorly performed on
Java Technologies & have used Jenkins as a user alot during software
development cycle. I found myself to be able to contribute to jenkins as
Hello, I am looking forward to participate in GSOC'17 & am new to open
source development. I know JAVA well and want to contribute to
Jenkins. Please give me some idea about some issues in which i can start
contributing
--
You received this message because you are subscribed to the Google
Seems to be resolved now.
The new version is available in the update center.
Von: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] Im
Auftrag von Pönisch, Christian
Gesendet: Montag, 9. Januar 2017 09:30
An: jenkinsci-dev@googlegroups.com
Betreff: AW: new version not in
