Re: Request for commit access

On 2017-08-19 1:02 PM, Oleg Nenashev wrote: > I have granted the access and changed the default assignee in JIRA. > > Welcome onboard! And sorry for the delay. Many thanks! -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe

Re: Request for commit access

Cristoph was in Cc starting from Aug 4. So the 2 week response timeout is reached even if there was no confirmation. Don't get me wrong, I believe there was a response from him. I have granted the access and changed the default assignee in JIRA. Welcome onboard! And sorry for the delay. BR, Ol

Re: Request for commit access

On 2017-08-16 9:15 PM, Oleg Nenashev wrote: > I am fine with that. There are several maintainers, who do not work in the > Jenkins project for sure. Not sure if it fits the current governance docs > and CoC. How do we proceed? -- You received this message because you are subscribed to the Goog

Re: Request for commit access

> > Can we just tick this over into the "unresponsive maintainer" category > of adoption requests? I am fine with that. There are several maintainers, who do not work in the Jenkins project for sure. Not sure if it fits the current governance docs and CoC. BR, Oleg 2017-08-16 21:05 GMT+02:00

Re: Request for commit access

On 2017-08-14 1:19 PM, Daniel Beck wrote: > Christoph, could you resubscribe and respond to this thread, or email > one of us directly so we can forward your response? Can we just tick this over into the "unresponsive maintainer" category of adoption requests? 3 weeks has passed since the initial

Re: Request for commit access

> On 8. Aug 2017, at 14:40, Baptiste Mathus wrote: > > I believe they're not supposed to be rejected, simply queued up for > moderation isn't it? Indeed I had checked it and never found/saw any email > from Christoph there If you're not subscribed, you get a response saying that your email wa

Re: Request for commit access

Added Tyler to Cc. Maybe he has enough superpowers to check the moderator log in the ML. So far I do not see confirmation unfortunately вторник, 8 августа 2017 г., 14:40:07 UTC+2 пользователь Baptiste Mathus написал: > > I believe they're not supposed to be rejected, simply queued up for > mode

Re: Request for commit access

I believe they're not supposed to be rejected, simply queued up for moderation isn't it? Indeed I had checked it and never found/saw any email from Christoph there. And I guess the moderators wouldn't have deleted it... Another weird case of Google groups (Is there any audit log for this in al

Re: Request for commit access

> On 7. Aug 2017, at 14:59, Drew DeVault wrote: > > Odd, he copied jenkinsci-dev Maybe not subscribed anymore? Those emails get rejected. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

Re: Re: Request for commit access

On 2017-08-04 1:41 AM, Oleg Nenashev wrote: > Hi Drew, > > I can transfer the ownership, but I also need a Jira ID My Jira ID is sircmpwn. > I also do not see the response from Cristoph in this thread. Seems it got > lost in Re:Re:s Odd, he copied jenkinsci-dev. It was an HTML email though, m

Re: Re: Request for commit access

Hi Drew, I can transfer the ownership, but I also need a Jira ID I also do not see the response from Cristoph in this thread. Seems it got lost in Re:Re:s среда, 2 августа 2017 г., 15:57:25 UTC+2 пользователь Drew DeVault написал: > > Thanks Christoph - are you able to do the transfer or does s

Re: Re: Request for commit access

Thanks Christoph - are you able to do the transfer or does someone else have to be invoved? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+u

Re: Request for commit access

Thanks for the advice. Happy to take over maintainership, just providing context for why I came around. Current maintainer is cc'd now. Context: > Hey, can I get commit access to this repository? > > https://github.com/jenkinsci/ircbot-plugin > > My GitHub username is SirCmpwn. I'd like to merge

Re: Request for commit access

Hello, please follow the process https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-IknowwhichpluginIwanttohelpwith,whatshouldIdonow ? Especially hence the part where we ask you to do a best effort to put the last/current known maintainers in CC of an email to do that here. Also,

Re: Request for commit access

Bump. On Tuesday, July 25, 2017 at 9:43:23 AM UTC-4, Drew DeVault wrote: > > Hey, can I get commit access to this repository? > > https://github.com/jenkinsci/ircbot-plugin > > My GitHub username is SirCmpwn. I'd like to merge this PR: > > https://github.com/jenkinsci/ircbot-plugin/pull/18 > >

Request for commit access

Hey, can I get commit access to this repository? https://github.com/jenkinsci/ircbot-plugin My GitHub username is SirCmpwn. I'd like to merge this PR: https://github.com/jenkinsci/ircbot-plugin/pull/18 Thanks! -- Drew DeVault -- You received this message because you are subscribed to the Goo

Re: Request for commit access to slack plugin

> On 05.12.2016, at 23:21, Matt Sheehan wrote: > > I would like to request commit access to the slack plugin so I can get this > merged: https://github.com/jenkinsci/slack-plugin/pull/236. Have you tried to contact the existing maintainers? -- You received this message because you are subscr

Request for commit access to slack plugin

I would like to request commit access to the slack plugin so I can get this merged: https://github.com/jenkinsci/slack-plugin/pull/236. Thanks, Matt -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop

Re: accurev-plugin, request for commit access

o/ Done, you should have received a GitHub invitation for that repo. Please think about removing the adopt-this-plugin label on the wiki page. Thank you and welcome on board! 2016-08-24 15:56 GMT+02:00 Joseph P : > Hi > > > > I would like to be a maintainer for the accurev plugin. > > https://

accurev-plugin, request for commit access

Hi I would like to be a maintainer for the accurev plugin. https://wiki.jenkins-ci.org/display/JENKINS/AccuRev+Plugin Would also appreciate a code review on https://github.com/jenkinsci/accurev-plugin/pull/25 GitHub id: casz Jenkins id: casz Best regards Joseph -- You receiv

Re: Request for commit access for testdroid-run-in-cloud-plugin

Could someone help me? On Thursday, 21 April 2016 08:08:26 UTC+2, Damian Sniezek wrote: > > Hi All, > > I am trying to release version 1.0.11-SNAPSHOT of > testdroid-run-in-cloud-plugin > > My origin points to: > > origin g...@github.com:jenkinsci/testdroid-run-in-cloud-plugin.git (fetch) > > ori

Re: Request for commit access

m>> Cc: "michael.dono...@gmail.com<mailto:michael.dono...@gmail.com>" mailto:michael.dono...@gmail.com>> Subject: Re: Request for commit access Nope, just wait /some/ time by respect also for the past work of the current maintainer(s). Your PR is 14 days just today. We generally

Re: Request for commit access

o wait for one of the current maintainers to respond? > > > Best, > > Jeff > > From: Jeff Bischoff > Date: Friday, April 22, 2016 at 11:36 AM > > To: "jenkinsci-dev@googlegroups.com" > Cc: "michael.dono...@gmail.com" > Subject: Re: Request

Re: Request for commit access

googlegroups.com<mailto:jenkinsci-dev@googlegroups.com>" mailto:jenkinsci-dev@googlegroups.com>> Cc: "michael.dono...@gmail.com<mailto:michael.dono...@gmail.com>" mailto:michael.dono...@gmail.com>> Subject: Re: Request for commit access I see that Configurat

Re: Request for commit access

2:33 PM To: "jenkinsci-dev@googlegroups.com<mailto:jenkinsci-dev@googlegroups.com>" mailto:jenkinsci-dev@googlegroups.com>> Cc: "michael.dono...@gmail.com<mailto:michael.dono...@gmail.com>" mailto:michael.dono...@gmail.com>> Subject: Re: Request for commit access

Re: Request for commit access

t;" mailto:michael.dono...@gmail.com>> Subject: Re: Request for commit access Hi, FWICT, looking at last commits, actually Michael Donohue seems pretty active on this one (in CC). And last release in only 1.5 month old. And one week old is still not that long for a PR. @Michael: d

Request for commit access for testdroid-run-in-cloud-plugin

Hi All, I am trying to release version 1.0.11-SNAPSHOT of testdroid-run-in-cloud-plugin My origin points to: origin g...@github.com:jenkinsci/testdroid-run-in-cloud-plugin.git (fetch) origin g...@github.com:jenkinsci/testdroid-run-in-cloud-plugin.git (push) I have set username and password in

Re: Request for commit access

Hi, FWICT, looking at last commits, actually Michael Donohue seems pretty active on this one (in CC). And last release in only 1.5 month old. And one week old is still not that long for a PR. @Michael: do you still work on that plugin as a maintainer? If so, please confirm here. And also, would b

Request for commit access

Hi all, I recently created a pull request for the configurationslicing-plugin of jenkinsci. I believe the changes are very straightforward. After more than a week, I have not received any response to the pull request or the associated JIRA ticket. I am aware that this plugin is lightly-maintain

Re: Request for commit access to Jenkinsci/gitlab plugin

Hi, I was on vacation for the last 3 weeks so I'm just catching up on gitlab-plugin stuff. I'm happy to merge your PRs and get a new release out in the next week or so. I'll respond to your email to my personal account re: commit access, etc. Thanks for offering to help! On Thursday, January

Request for commit access to Jenkinsci/gitlab plugin

Hello folks, as the maintainer group of the *jenkinsci/gitlab plugin* is asking for helpers (see issue #115 <(https://github.com/jenkinsci/gitlab-plugin/issues/115>) and I have a pending pull request for a new feature resolving issues #

Request for commit access to Jenkinsci/gitlab plugin

Hello folks, as the maintainer group of the *jenkinsci/gitlab plugin* is asking for helpers (see issue #115 <(https://github.com/jenkinsci/gitlab-plugin/issues/115>) and I have a pending pull request for a new feature resolving issues #

Request for commit access to Jenkinsci/gitlab plugin

Hello folks, as the maintainer group of the *jenkinsci/gitlab plugin* is asking for helpers (see issue #115 <(https://github.com/jenkinsci/gitlab-plugin/issues/115>) and I have a pending pull request resolving issues #142

Re: Request for commit access to notification-plugin

Sure I’m happy to take over maintenance of the plugin – the issue has been around for the past year so I’m not sure waiting for the patch to be applied is viable anymore. I’ve sent an email off to the three people currently listed as maintainers. Cheers, Adrian. > On 12 Nov 2015, at 10:11 AM,

Re: Request for commit access to notification-plugin

Hi Adrian, Trying to reflect the current process here: If you wish to become a maintainer on the plugin, then great! In this case, please say so and somebody will be able to grand you the permissions. That means you're ready to work on the plugin and handle it for sometimes (and handle JIRA issue

Request for commit access to notification-plugin

Hi, The notification-plugin appears to be unmaintained. There's an outstanding pull-request from Rich Kang to fix an issue that's been causing us issues for quite some time that I'd like to merge. Issue: https://issues.jenkins-ci.org/browse/JENKINS-26162?jql=project%20%3D%20JENKINS%20AND%20statu

Re: Request for Commit access[jigomerge-plugin]

Thanks Christopher! > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visi

Re: Request for Commit access[jigomerge-plugin]

Done. You should probably get an email from GitHub inviting you to the repo. -Chris On 06/08/15 16:27, Smruti Mohapatra wrote: > Hi, > > I made a pull request for the jigomerge-plugin and have not seen any > response in more than a week now. Would it be possible to grant me the > commit access

Re: Request for Commit access[jigomerge-plugin]

Anybody ? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://gr

Request for Commit access[jigomerge-plugin]

Hi, I made a pull request for the jigomerge-plugin and have not seen any response in more than a week now. Would it be possible to grant me the commit access ? The fix is pretty straightforward and I already have the fix working for me on our jenkins instance. My github account name is "smrutimo"

Re: Request for commit access to Jenkins Notification Plugin

Forwarding the response I got from hagzag to the list: > Just saw this now - I merged the change + looking at other 2 pull requests > before we release a new version. On 07.07.2015, at 23:14, Daniel Beck wrote: > CC hagzag, who appears to be the current maintainer of the plugin. > > On 07.07.

Re: Request for commit access to Jenkins Notification Plugin

CC hagzag, who appears to be the current maintainer of the plugin. On 07.07.2015, at 23:06, Ryan Plauche wrote: > Hi, > > I submitted a pull request for the Jenkins notification plugin about a month > ago and so far no one has responded. I would like to request commit access to > the repo for

Request for commit access to Jenkins Notification Plugin

Hi, I submitted a pull request for the Jenkins notification plugin about a month ago and so far no one has responded. I would like to request commit access to the repo for that plugin so I can merge in the request myself. The github repo is https://github.com/jenkinsci/notification-plugin and m

RE: Request for Commit Access to SSH-Plugin

k > To: jenkinsci-dev@googlegroups.com > Subject: Re: Request for Commit Access to SSH-Plugin > > I believe I replied to you a couple of times on IRC, but I guess we > missed each other. > > You should now have access. > > Regards, > Chris > > > On 27/05/15

Re: Request for commit access to Rally plugin repository (and code review)

Thanks for the response! That sounds perfectly reasonable. Everything is ready to go at this point (in terms of new plugin functionality), I'm just waiting on permission. I released something last night as a fork-of-a-fork thing that I'm not too proud of, but my organization needed something co

Re: Request for Commit Access to SSH-Plugin

: jenkinsci-dev@googlegroups.com Subject: RE: Request for Commit Access to SSH-Plugin Date: Wed, 20 May 2015 22:44:30 -0400 I hate to bump this, but I did not want to start a new thread. I have tried getting onto IRC, but I think I am missing the peak times as I have not managed to get a response yet. Can

Re: Request for commit access to Rally plugin repository (and code review)

It sounds like it would be best if you became another maintainer of the plugin if the current maintainer doesn't have time at the moment. If the maintainer was ok with that, we can give you commit access now. In any case, from a user's point of view, it's better to have one plugin than multipl

RE: Request for Commit Access to SSH-Plugin

way from its use. From: john.ta...@live.com To: jenkinsci-dev@googlegroups.com Subject: RE: Request for Commit Access to SSH-Plugin Date: Wed, 20 May 2015 22:44:30 -0400 I hate to bump this, but I did not want to start a new thread. I have tried getting onto IRC, but I think I am missing the

Re: Request for commit access to Rally plugin repository (and code review)

I did finally get in contact with the maintainer of the Rally plugin. However, given the recent goings-on in his life and the amount that I've been throwing at him, I'm wondering if it would be in both of our interests to fork and have two separate plugins. Mine focuses more on the SCM integrat

RE: Request for Commit Access to SSH-Plugin

bears no responsibility for any loss and/or damage arising in any way from its use. From: john.ta...@live.com To: jenkinsci-dev@googlegroups.com Subject: Request for Commit Access to SSH-Plugin Date: Sat, 16 May 2015 13:51:55 -0400 May I have commit access for the SSH-Plugin, specifically

Request for commit access to Rally plugin repository (and code review)

Hello, I would like commit access to the Rally plugin repository ( https://github.com/jenkinsci/rally-plugin) and potentially leadership of that plugin. My team is using Rally on a fairly large project (alongside several other teams) and I'm seeing a few areas where minor improvements would yi

Request for Commit Access to SSH-Plugin

May I have commit access for the SSH-Plugin, specifically https://github.com/jenkinsci/ssh-plugin? My GitHub user ID is johnny-b-goode. I have tried reaching out to the maintainer indicated on the wiki, Edmund Wagner, but have not received a response. His last commit was about nine months ago.

Re: Request for commit access to git-plugin

Hi, it was about https://github.com/jenkinsci/git-plugin/pull/315, but I saw that you found the PR in the meantime and it is already merged. Thanks for reviewing and merging. Br Christian On Monday, April 27, 2015 at 11:22:44 AM UTC+2, nicolas de loof wrote: > > Which PR is this about ? > > 20

Re: Request for commit access to git-plugin

Which PR is this about ? 2015-04-25 13:15 GMT+02:00 Christian Galsterer : > Thanks for looking into the PR. > > On Saturday, April 25, 2015 at 1:03:03 PM UTC+2, nicolas de loof wrote: >> >> I've been on vacation for 2 weeks, will review your PR asap. Please note >> 1 week for such a popular plugi

Re: Request for commit access to git-plugin

Git plugin has design issues, that's why single fixes that resolve only one small part of issue and adding other problems not merged. On Saturday, April 25, 2015 at 2:15:18 PM UTC+3, Christian Galsterer wrote: > > Thanks for looking into the PR. > > On Saturday, April 25, 2015 at 1:03:03 PM UTC+2

Re: Request for commit access to git-plugin

Thanks for looking into the PR. On Saturday, April 25, 2015 at 1:03:03 PM UTC+2, nicolas de loof wrote: > > I've been on vacation for 2 weeks, will review your PR asap. Please note 1 > week for such a popular plugin is not a long delay to wait for > review/feedback. > > Le sam. 25 avr. 2015 12:2

Re: Request for commit access to git-plugin

I've been on vacation for 2 weeks, will review your PR asap. Please note 1 week for such a popular plugin is not a long delay to wait for review/feedback. Le sam. 25 avr. 2015 12:28, Christian Galsterer a écrit : > Hi, > > you are right. I updated the code already a week ago, but I didn't left a

Re: Request for commit access to git-plugin

Hi, you are right. I updated the code already a week ago, but I didn't left a reply on the review comment. I left a comment now. Br Christian On Saturday, April 25, 2015 at 10:59:47 AM UTC+2, Daniel Beck wrote: > > > On 25.04.2015, at 07:21, Christian Galsterer > wrote: > > > without feedback

Re: Request for commit access to git-plugin

Hi, you are right. I updated the code already a week ago, but I didn't left a reply on the review comment. Br Christian On Saturday, April 25, 2015 at 10:59:47 AM UTC+2, Daniel Beck wrote: > > > On 25.04.2015, at 07:21, Christian Galsterer > wrote: > > > without feedback > > What about the r

Re: Request for commit access to git-plugin

On 25.04.2015, at 07:21, Christian Galsterer wrote: > without feedback What about the review comment you got? Note that there's no notification when a pull request is updated, so a simple 'I addressed your review comment' would be helpful. -- You received this message because you are subscr

Request for commit access to git-plugin

Hi, I would like to ask for commit access for the git-plugin as my pull request is pending for more then 2 weeks without feedback any I also didn't get response for my request for review of the PR here in the group. My GitHub account: christiangalsterer Repository: https://github.com/jenkinsci/

Request for Commit access for New Plugin DiskCheck& Recycle

Hi, I have written a plugin to add a Disk check before a project is started, Problem Statement : Disk run out of space while running a build , We do use Disk Usage plugin , but it checks for disk usage every hour also mark the slave offline without any notification which is not appropriate So

Re: Request for commit access to Embeddable Build Status Plugin

t no response so far. As there are some other PRs pending it > seems to be that the plugin is currently not under active maintenance. Hence > this request for commit access. My github id is "christiangalsterer". > > Thanks in advance. > > Br > Christian > >

Request for commit access to Embeddable Build Status Plugin

maintenance. Hence this request for commit access. My github id is "christiangalsterer". Thanks in advance. Br Christian -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

request for commit access to https://github.com/jenkinsci/awseb-deployment-plugin

Hello, Can I be granted access to commit to this plugin? There are some features I would like add, but it appears there has been no dev activity here since February. githubid: DavidTanner Thanks, David Tanner -- You received this message because you are subscribed to the Google Groups "Jen

request for commit access to https://github.com/jenkinsci/ghprb-plugin

Hello, Can I be granted access to commit to this plugin? There are some features I would like add, but it appears there has been no dev activity here for over a month. githubid: DavidTanner Thanks, David Tanner -- You received this message because you are subscribed to the Google Groups "J

Re: New Jenkins Cors Plugin - request for commit access

Hi Jochen, Your plugin has been forked into the jenkinsci organisation: https://github.com/jenkinsci/cors-plugin You can use this repo now to make a release :) Regards, Chris On 26/04/13 10:07, Jochen Hinrichsen wrote: Dear Ulli, you can find the cors plugin here: https://github.com/jhinric

openid-plugin fix for users with proxy servers / request for commit access to the plugin repo

I have recently reported JENKINS-22368 - Discovery fails when Jenkins is behind a proxy and have delivered a fix as a pull request in Github. As per the Pull Request to Repositories wiki en

Re: new jira-rest-plugin: request for commit access

+1 on migrating from SOAP to REST in the existing plugin and all +1 on moving to the credentials plugin support. Rather the doing some hacky username/password converting from the old way to the new, you could also use the AdministrativeMonitor ExtensionPoint to inform the admin about the incompl

Re: new jira-rest-plugin: request for commit access

@DanielBeck: I like that option as it will allow me to drop the soap-related stuff while still reusing the existing code. I'd like to migrate to jenkins credentials at the same time and drop the input fields for user/pass. Or maybe there is a recommended way of migrating plugins from user/pass inp

Re: new jira-rest-plugin: request for commit access

On 28.03.2014, at 22:48, Stefan Thurnherr wrote: > feels like quite a big change, which I believe makes it justifiable to create > a new plugin If necessary (no additional option 'Use SOAP'/'Use REST' feasible) you could keep as much as possible from the existing plugin, and make this a Jira

Re: new jira-rest-plugin: request for commit access

+1 for adding this to the existing plugin. Probably would make migration to JIRA 7 much less painless for users of the existing plugin Am 28.03.2014 22:42, schrieb Slide: Is there any reason you couldn't add the capability to the existing plugin instead of writing a new plugin? slide On Fr

Re: new jira-rest-plugin: request for commit access

I wouldn't change from SOAP to REST, I would refactor to support both somehow. slide On Fri, Mar 28, 2014 at 2:48 PM, Stefan Thurnherr < stefan.thurnh...@gmail.com> wrote: > Yeah I considered that. However changing from soap/rpc to rest feels like > quite a big change, which I believe makes it

Re: new jira-rest-plugin: request for commit access

Yeah I considered that. However changing from soap/rpc to rest feels like quite a big change, which I believe makes it justifiable to create a new plugin. Code also becomes more maintainable if it doesn't include any soap stuff. And the plugin does not persist much information (user/pass, url,

Re: new jira-rest-plugin: request for commit access

Is there any reason you couldn't add the capability to the existing plugin instead of writing a new plugin? slide On Fri, Mar 28, 2014 at 2:37 PM, Stefan Thurnherr < stefan.thurnh...@gmail.com> wrote: > Hi all > > I'm working on a new jira plugin that will use the rest api available in > jira.

new jira-rest-plugin: request for commit access

Hi all I'm working on a new jira plugin that will use the rest api available in jira. The existing jira plugin uses the soap/rpc api which will probably be deprecated with JIRA 7 - see https://issues.jenkins-ci.org/browse/JENKINS-18166. I'm currently working on the new jira-rest-plugin in my p

Re: Request for commit access to Cppcheck plugin

Done. Am 22.02.2014 um 12:26 schrieb Michal Turek : > Hi, > > I would like to ask for a commit access to the repository of Cppcheck plugin. > I plan to fix its issues and implement requested features similarly as I > recently did in SLOCCount plugin. My first pull request is not processed for

Re: Request for commit access to Cppcheck plugin

Anyone? On Sat, Feb 22, 2014 at 12:26 PM, Michal Turek wrote: > Hi, > > I would like to ask for a commit access to the repository of Cppcheck > plugin. I plan to fix its issues and implement requested features similarly > as I recently did in SLOCCount plugin. My first pull request is not > proc

Request for commit access to Cppcheck plugin

Hi, I would like to ask for a commit access to the repository of Cppcheck plugin. I plan to fix its issues and implement requested features similarly as I recently did in SLOCCount plugin. My first pull request is not processed for about two weeks and it seems nobody maintains the plugin at the mo

Re: request for commit access to https://github.com/jenkinsci/rundeck-plugin/

Done, welcome aboard! Ulli Am 24.01.2014 um 17:18 schrieb greg : > Hi, can I be granted commit access to > https://github.com/jenkinsci/rundeck-plugin/ ? > > I am the lead developer of Rundeck, and the rundeck-plugin has been without > an update for a while. I have a pull request to upda

request for commit access to https://github.com/jenkinsci/rundeck-plugin/

Hi, can I be granted commit access to https://github.com/jenkinsci/rundeck-plugin/ ? I am the lead developer of Rundeck, and the rundeck-plugin has been without an update for a while. I have a pull request to update it https://github.com/jenkinsci/rundeck-plugin/pull/3 github id: gschue

Re: Request for Commit access for new SBuild plugin

Thanks. Tobias Am Dienstag, 3. Dezember 2013 13:19:13 UTC+1 schrieb Ullrich Hafner: > > Created https://github.com/jenkinsci/sbuild-plugin > > Welcome aboard! > > Ulli > > Am 02.12.2013 um 12:20 schrieb Tobias Roeser > >: > > Hello, > > I'm wrote the SBuild plugin, which enabled Jenkins to direc

Re: Request for Commit access for new SBuild plugin

Created https://github.com/jenkinsci/sbuild-plugin Welcome aboard! Ulli Am 02.12.2013 um 12:20 schrieb Tobias Roeser : > Hello, > > I'm wrote the SBuild plugin, which enabled Jenkins to directly execute SBuild > targets. > > My github ID is: https://github.com/lefou > > The plugin is alread

Request for Commit access for new SBuild plugin

Hello, I'm wrote the SBuild plugin, which enabled Jenkins to directly execute SBuild targets. My github ID is: https://github.com/lefou The plugin is already hosted on Github, so feel free to fork: https://github.com/lefou/jenkins-sbuild Best regards, Tobias Roeser -- You received this mess

Re: Request for commit access to greenballs-plugin

Done. Welcome aboard! Ulli Am 23.09.2013 um 16:08 schrieb Nikolas Falco : > I've submitted a PR some time ago for the greenballs-plugin > (https://github.com/jenkinsci/greenballs-plugin). > > I didn't get any response. I got an e-mail that incite me request commit > access. > > The reposito

Request for commit access to greenballs-plugin

I've submitted a PR some time ago for the greenballs-plugin (https://github.com/jenkinsci/greenballs-plugin). I didn't get any response. I got an e-mail that incite me request commit access. The repository: https://github.com/jenkinsci/greenballs-plugin My github username: nfalco79 Relevant PR:

Re: Request for commit access to leiningen-plugin

Done. Welcome aboard! Ulli Am 22.09.2013 um 19:57 schrieb Auke van Leeuwen : > I've submitted a PR some time ago for the leiningen-plugin > (https://github.com/jenkinsci/leiningen-plugin). > > I didn't get any response, except for the automated ones. Today I got an > e-mail saying I could re

Request for commit access to leiningen-plugin

I've submitted a PR some time ago for the leiningen-plugin (https://github.com/jenkinsci/leiningen-plugin). I didn't get any response, except for the automated ones. Today I got an e-mail saying I could request commit access via this list (based on https://wiki.jenkins-ci.org/display/JENKINS/Pu

Re: Request for commit access to crowd2-plugin to merge patch

Hi Paul, Sorry I had a look at the plugin one week ago and did not see your PR I stopped to follow github notifications that are unmanageable when you are subscribing to various organisations with many repo/activities :( About the plugin itself I upgraded on my own fork the version of the c

Re: Request for commit access to crowd2-plugin to merge patch

Hello Ulli, On Wed, 4 Sep 2013 14:00:06 +0200 Ulli Hafner wrote: > Hi Paul, > > sorry for the delay. I added you as a committer of the crowd2 plug-in. > > Welcome aboard! Thanks much, I merged the pull request, and will be studying docs to learn what making a new release means. > > Ulli >

Re: Request for commit access to crowd2-plugin to merge patch

ys that it's possible to > request commits access via dev list, that it's not considered spamming > to actually be trying to get it. > > Thanks in advance! > > > Begin forwarded message: > > Date: Tue, 27 Aug 2013 15:29:15 +0300 > From: Paul Sokolovsky > To

Fw: Request for commit access to crowd2-plugin to merge patch

age: Date: Tue, 27 Aug 2013 15:29:15 +0300 From: Paul Sokolovsky To: jenkinsci-dev@googlegroups.com Subject: Request for commit access to crowd2-plugin to merge patch Hello, I submitted a pull request https://github.com/jenkinsci/crowd2-plugin/pull/4 almost 2 weeks ago, and as there was no repl

Request for commit access to crowd2-plugin to merge patch

Hello, I submitted a pull request https://github.com/jenkinsci/crowd2-plugin/pull/4 almost 2 weeks ago, and as there was no reply, I would like to follow suggestions given in the pull request welcome message (http://jenkins-ci.org/pull-request-greeting) and apply for commit access to merge it myse

Re: Jenkins Redmine Plugin - request for commit access

Regarding https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories I'm ready to co-maintain Redmine Plugin. Side questions: - are jenkins developers prefer spaces over tabs? how many spaces? - which option regarding git line endings should I user in jenkins repos as I'm workin

Re: Jenkins Redmine Plugin - request for commit access

Hi, I've made another PR to redmine-plugin which introduces some rework of plugin internals. My initial PR was sent about a month ago but with no response; I've sent also email to Akiko Asami (id: gaooh), but with same result. Could someone else review my PR in terms of idea and code? I know t

Re: request for commit access

mit access working? Thanks, Harald > From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] > On Behalf > Of Harald Albers > Sent: den 3 april 2013 23:54 > To: jenkinsci-dev@googlegroups.com > Subject: Re: request for commit access > On 3 Apr 2013 at

Re: New Jenkins Cors Plugin - request for commit access

Dear Ulli, you can find the cors plugin here: https://github.com/jhinrichsen/cors-plugin On Friday, 5 April 2013 09:44:31 UTC+2, Ullrich Hafner wrote: > > Typically we grant you access for your own plug-in only. Did you already > push your plugin to your github account already? Then we can fork

Re: Jenkins Redmine Plugin - request for commit access

Sorry, I did not. Just send an email to gaooh. W dniu piątek, 5 kwietnia 2013 09:45:45 UTC+2 użytkownik Ullrich Hafner napisał: > > Did you already get in contact with the current maintainer Akiko Asami > (id: gaooh)? > > Ulli > > Am 04.04.2013 um 19:44 schrieb ljad...@gmail.com : > > Hi, > > I

Re: Jenkins Redmine Plugin - request for commit access

Did you already get in contact with the current maintainer Akiko Asami (id: gaooh)? Ulli Am 04.04.2013 um 19:44 schrieb ljader...@gmail.com: > Hi, > > I'm interested in fixing/extending Jenkins Redmine Plugin. I've made simple > Pull Request on https://github.com/jenkinsci/redmine-plugin but

Re: New Jenkins Cors Plugin - request for commit access

Typically we grant you access for your own plug-in only. Did you already push your plugin to your github account already? Then we can fork it to our organization? Or what should be the exact name of your plug-in that will be used as git repository? Ulli Am 04.04.2013 um 20:28 schrieb Jochen Hi

  1   2   >