Maintenance help needed on ghprb-plugin

Hi folks - I've been maintaining this for a year or so, and it's been a good ride. However, I no longer feel I can be an effective maintainer for various reasons including time commitments. Looking for volunteers. If you've developed on this plugin before please feel free to answer on

Re: Someone to take over GHPRB

Hi Jeremy - I maintain the plugin but I'd love to share that duty. I see an e-mail from you in my work account; I'll write you back there.  Ben On Tue, May 23, 2017 at 1:23 PM, wrote: > Hi David, > I realize it's 2017, but my company (The Linux Foundation) has a

Re: Fwd: Re: Maintainer request for ghprb

Re-sending so we include the Jenkins dev thread Hi Nitin I'm the maintainer. Why don't you send me a message with your plans? Honza - sorry you don't care about the plugin these days but your legacy lives on! Ben On Dec 15, 2016 7:58 AM, "Ben Patterson" On Dec 15, 2016 7:49

Re: Someone to take over GHPRB

Good point; I'll do that as well Daniel. ty On Tue, Nov 15, 2016 at 8:24 AM, Daniel Beck <m...@beckweb.net> wrote: > > > On 15.11.2016, at 14:19, Ben Patterson <patterson@gmail.com> wrote: > > > > If anyone has keen interest, please let me/this-line know

Re: Someone to take over GHPRB

2.0, etc. If anyone has keen interest, please let me/this-line know and let's get you collaborator or maintainer status. On Tue, Sep 27, 2016 at 4:57 PM, Ben Patterson <patterson@gmail.com> wrote: > Well, my two cents is indeed to do things by the book in GitHub-land for >

Re: How to make the Jenkins build output as downloadable from Jenkins server machine itself?

I realize this is not as pretty as was what you were looking for, but you can always tee your build scripts to a log file, and archive that. (I thought I'd answer in case there's not an easier way; but if there is, hopefully someone can suggest something more Jenkins-y. --cheers) On Monday,

Re: Someone to take over GHPRB

net> wrote: > > > On 27.09.2016, at 22:09, Ben Patterson <patterson@gmail.com> wrote: > > > > It sounds good to me. FWIW I had submitted an issue to the 'current' > parent repo; I assume GH would only make the switch if all parties agree. > > Breaking the

Re: Someone to take over GHPRB

.2016, at 23:04, Ben Patterson <patterson@gmail.com> wrote: > > > > Yeah breaking the fork link would be under the control of the other repo > fwiw so I couldn't promise that. > > I can ask GitHub support to do that if that's the consensus. > > -- > You received

Re: Someone to take over GHPRB

icial to users to not have 2 or 3 places to look at to look for and > file issues on that plugin :-/. > > Thanks! > > 2016-09-26 22:24 GMT+02:00 Ben Patterson <patterson@gmail.com>: > >> James - Since the plugin is maintained on jenkinsci and not janinko, is >>

Re: Someone to take over GHPRB

ership. > > On Sunday, September 25, 2016 at 5:59:45 AM UTC+10, Ben Patterson wrote: >> >> Och I should have mentioned my github id: benpatterson >> >> sent via Android >> >> On Sep 24, 2016 12:56 PM, "Ben Patterson" <patter...@gmail.com> wrote

Re: Someone to take over GHPRB

; Thanks > > Le 24 sept. 2016 9:59 PM, "Ben Patterson" <patterson@gmail.com> a > écrit : > >> Och I should have mentioned my github id: benpatterson >> >> sent via Android >> >> On Sep 24, 2016 12:56 PM, "Ben Patterson" <p

Re: Someone to take over GHPRB

Och I should have mentioned my github id: benpatterson sent via Android On Sep 24, 2016 12:56 PM, "Ben Patterson" <patterson@gmail.com> wrote: > Hi Daniel and David - > > I can help out with this plugin if you'd like someone to guide home the > pull requests

Re: Someone to take over GHPRB

Hi Daniel and David - I can help out with this plugin if you'd like someone to guide home the pull requests and such. I have some cycles. Care to give me contributor access? Ben On Friday, September 16, 2016 at 9:01:47 PM UTC-4, Daniel Beck wrote: > > I marked the plugin as 'up for adoption'

Re: Modifying a job via a post build step

Phil, have you looked at the Job DSL plugin? It sounds to me like that might be useful for you here. https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin, and https://github.com/jenkinsci/job-dsl-plugin/wiki On Friday, June 12, 2015 at 1:05:48 AM UTC-4, Phil C wrote: Hi, I'd like to

Re: Modifying a job via a post build step

something? In any case, if I do end up implementing job modification functionality, I will look into adding this functionality to the Job DSL plugin, rather than creating an entirely new plugin. Phil On Friday, June 12, 2015 at 5:50:05 AM UTC-7, Ben Patterson wrote: Phil, have you looked

Re: how to add many jobs in jenkins for all projects at once

Have you looked at the Job DSL plugin https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin? That might get you what you need. On Wednesday, April 15, 2015 at 7:00:29 AM UTC-6, Mahdaoui Charifa wrote: Hi , please we have at the moment a lot of projects to add in jenkins, i ask if

Re: Plugin that generates Jobs based on a template

Karthik - have you looked at the Job DSL Plugin https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin? That is a decent option for your use case. It can both create the parent job (or template), and it can also create child jobs based on a template. As you look at it, I'd suggest looking

Re: Commit access request for jenkinsci / job-dsl-plugin

That plugin is actively maintained. You should submit pull request(s) on github. They'll get looks there. It's likewise worth your while to look at the existing pull requests to see if someone has already done work you were planning to do. On Thursday, February 27, 2014 5:20:31 AM UTC-5,

Re: deploy build artifacts to nexus

For more info, you can take a look here: https://support.sonatype.com/entries/21283268-Configure-Maven-to-Deploy-to-Nexus You tie the deployment to the Maven deploy build phase, so whenever you call 'mvn deploy', it will publish the artifact to the repo you've configured. (Calling mvn build or

Requesting commit access to dormant plugin [shelve project plugin] - to address [Jenkins-11023] and beyond

Hi - It looks like this plugin has been dormant; I realized when I submitted a pull request https://github.com/jenkinsci/shelve-project-plugin-plugin/pull/2that there was already a pull request for a different feature https://github.com/jenkinsci/shelve-project-plugin-plugin/pull/1. I'd love