Re: Request access to JenkinsCI organization

2016-03-29 Thread Michael Neale
Hi Oscar - I have added them as a committer as per the https://wiki.jenkins-ci.org/display/JENKINS/IRC+Bot I assume they have a https://jenkins-ci.org/account set up with the same user name - then that should be all that is needed. If they want to release the plugin they will need to use

Re: Plugin dependencies automatically installed

2016-03-29 Thread Michael Neale
Right - generally I like in hpi:run land until I want it in a "real" jenkins, which would be done via an update center or already likely has the required dependencies installed (this is why this doesn't come up too much I think). On Wednesday, March 30, 2016 at 5:29:46 AM UTC+11, Jesse Glick

Need write access to EASE plugin as a new maintainer

2016-03-29 Thread Kevin Wilson
Repo: - https://github.com/jenkinsci/ease-plugin Github ID: - kwilson6744 Jenkins-CI ID: - kwilson6744 The original developer of this plugin added me as a maintainer 2 months ago but it appears I still do not have write access.

CPS transforming at compile time?

2016-03-29 Thread Andrew Bayer
I'm doing all kinds of weird stuff with Pipeline scripts delivered by plugins, and I'm beginning to get annoyed at having to have the actual Pipeline script (which is being served similar to a GlobalVariable) in src/main/resources rather than src/main/groovy. I'm assuming the root reason for this

Re: svn.jenkins-ci.org will be SHUT DOWN on March 31

2016-03-29 Thread R. Tyler Croy
(replies inline) On Tue, 29 Mar 2016, Michael O'Cleirigh wrote: > Hello, > > I identified the tags for each of the svn.jenkins-ci.org plugins and > started doing comparisons with what is in the live svn repo. > >

Re: Plugin dependencies automatically installed

2016-03-29 Thread Jesse Glick
On Wed, Mar 23, 2016 at 8:50 PM, Slide wrote: > The automatic dependency stuff only works if installing via the update > center I believe. Or from `mvn hpi:run` when testing. -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: Switching plugin build from Maven to Gradle breaks Jenkins CI builds

2016-03-29 Thread Jesse Glick
On Tue, Mar 29, 2016 at 12:27 PM, Jochen Hinrichsen wrote: > What's the procedure for changing the template as soon as the PR is > accepted? Ask here. > Am i missing some permissions to see the magic "Config" button? Yes. :-) -- You received this message

Re: svn.jenkins-ci.org will be SHUT DOWN on March 31

2016-03-29 Thread Michael O'Cleirigh
Hello, I identified the tags for each of the svn.jenkins-ci.org plugins and started doing comparisons with what is in the live svn repo. https://docs.google.com/document/d/1MnYEIVPkNFDWOjXqUYGx-Ic6uYrvpZvTByM8GNiIhMM/edit?usp=docslist_api Aside from some file permissions the git converted trunk

Switching plugin build from Maven to Gradle breaks Jenkins CI builds

2016-03-29 Thread Jochen Hinrichsen
Dear all, i just sent a PR to switch the build tool for the Gradle Plugin from Maven to Gradle. This change will break the continuous build job, which expects a maven pom: https://jenkins.ci.cloudbees.com/job/plugins/job/gradle-plugin/ What's the procedure for changing the template as soon as

Request access to JenkinsCI organization

2016-03-29 Thread Oscar Serna
Hi mates! I'm Oscar Serna and my github id is oserna3. I'm one of the actual owners of elasticbox-plugin repository. It would be very nice that Guillermo Sanchez would be a member of the jenkinsci organization and ElasticBox-plugin developer team. I've already added him as a repo

Re: Display Git changelog as a list of Atlassian Stash (Bitbucket Server) pull requests

2016-03-29 Thread Tomas Bjerre
You may want to have a look at https://wiki.jenkins-ci.org/display/JENKINS/Git+Changelog+Plugin Den tisdag 22 mars 2016 kl. 16:00:40 UTC+1 skrev Nickolay Rumyantsev: > > Hi, > > In my company we use Atlassian Stash (now Bitbucket Server) to serve our > sources. We use pull requests to merge our

Re: connecting jenkins to artifactory

2016-03-29 Thread domi
I do something similar and I have the best result with combination of these two plugins (not using artifactory, but an other maven repo server): https://wiki.jenkins-ci.org/display/JENKINS/Maven+Metadata+Plugin —> get a parameter dropdown with all the artefact versions in the maven repository