Re: commit access lost to blueocean-plugin

FTR I resolved both issues. -- 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

Re: commit access lost to blueocean-plugin

On Wed, 2 Aug 2023 at 12:39, Mark Waite wrote: > > The lockout on repo.jenkins-ci.org has happened to several of us. An > Artifactory admin will need to toggle a setting on your account on > repo.jenkins-ci.org ok no worries. I will wait this to get for others as well. > > I don't understand

Re: commit access lost to blueocean-plugin

The lockout on repo.jenkins-ci.org has happened to several of us. An Artifactory admin will need to toggle a setting on your account on repo.jenkins-ci.org I don't understand the block on GitHub/ Have you tried ssh access rather than https? On Tuesday, August 1, 2023 at 7:47:24 PM UTC-6

Re: commit access lost to blueocean-plugin

and my account seems to be locked on https://repo.jenkins-ci.org/ while I can still log in to issues.j.o definitely not a good day :) On Wed, 2 Aug 2023 at 10:53, Olivier Lamy wrote: > > Hi, > Until yesterday, I was able to push to blueocean-plugin repo but this > morning (2 Aug) this does

commit access lost to blueocean-plugin

Hi, Until yesterday, I was able to push to blueocean-plugin repo but this morning (2 Aug) this does not work anymore olamy@pop-os:~/dev/sources/jenkins/blueocean-plugin$ git push origin snakeyaml-2.0 remote: Permission to jenkinsci/blueocean-plugin.git denied to olamy. fatal: unable to access

Re: Commit access request

Hi Nikita, Welcome back! All the listed repositories have been moved from SVN to Git in 2011, and there was no updates since that. I have granted you permissions in these repositories, you should have received an invitation to the GitHub organization in your inbox. You will need to accept the

Commit access request

Hello, I am the creator of the following Jenkins plugins: https://plugins.jenkins.io/copy-data-to-workspace-plugin/ https://plugins.jenkins.io/selection-tasks-plugin/ https://plugins.jenkins.io/seleniumrc-plugin/ https://plugins.jenkins.io/storable-configs-plugin/ Recently I was asked to approve

Re: Requesting commit access for bitbucket-plugin

Hello, I just gave you admin access to the repository. Notice that I am not sure if it makes sense to continue maintaining this plugin since the Bitbucket Push and Pull request plugin might do what you are looking for * https://github.com/jenkinsci/bitbucket-push-and-pull-request-plugin Let

Re: Requesting commit access for bitbucket-plugin

FTR I have reached out to Felix to get his response in this thread. Best regards, Oleg On Monday, July 20, 2020 at 4:42:06 PM UTC+2, tzach@gmail.com wrote: > > Hi All, > > Could someone please check my request? > > Thanks, > Tzach > > On Saturday, 4 July 2020 at 23:12:10 UTC+3

Re: Requesting commit access for bitbucket-plugin

Hi All, Could someone please check my request? Thanks, Tzach On Saturday, 4 July 2020 at 23:12:10 UTC+3 tzach@gmail.com wrote: > Hello, > > I would like to help maintain the plugin BitBucket. > > My request details are as follows: > >- Plugin I want to maintain:

Requesting commit access for bitbucket-plugin

Hello, I would like to help maintain the plugin BitBucket. My request details are as follows: - Plugin I want to maintain: https://plugins.jenkins.io/bitbucket/ - Pull request: https://github.com/jenkinsci/bitbucket-plugin/pull/74 - My GitHub profile is: https://github.com/tzachs -

Re: Adopt parameterized-trigger-plugin commit access

Hi Olivier, I am +1 for that as a former plugin maintainer, thanks a lot for standing up! I have granted you permissions in the repository. Please let me know if you want to be a default assignee in Jira. Best regards, Oleg On Friday, June 12, 2020 at 8:24:28 AM UTC+2, Olivier Lamy wrote: >

Adopt parameterized-trigger-plugin commit access

Hi As it's in "adopt me" mode, I'd like to make some changes in this plugin https://github.com/jenkinsci/parameterized-trigger-plugin It's essentially some dependencies upgrade and some cleanup github id: olamy. Jenkins infra id: olamy Thanks Regards -- Olivier Lamy -- You received this message

Re: Commit access request (File operations plugin)

thread, if there’s no response we normally wait 2 >>> weeks from cc and then grant access >>> >>>> On Sun, 23 Feb 2020 at 18:23, Ramzi El-Yafi wrote: >>>> Hi, >>>> >>>> As per the adopt a plugin guidelines, I would like to request co

Re: Commit access request (File operations plugin)

Sun, 23 Feb 2020 at 18:23, Ramzi El-Yafi > > wrote: >> >>> Hi, >>> >>> As per the adopt a plugin guidelines, I would like to request commit >>> access to the file operations plugin: >>> >>> *Plugin Repo: *https://github.com/jenkin

Re: Commit access request (File operations plugin)

mb wrote: > >  > Please cc him in this thread, if there’s no response we normally wait 2 > weeks from cc and then grant access > > On Sun, 23 Feb 2020 at 18:23, Ramzi El-Yafi > wrote: > >> Hi, >> >> As per the adopt a plugin guidelines, I would like to req

Re: Commit access request (File operations plugin)

Just an update - my PR has now been merged by the plugin owner (thanks Suresh), so I no longer need commit access. Please disregard this conversation. On Sunday, 23 February 2020 22:15:29 UTC, Ramzi El-Yafi wrote: > > Ok - CC’ing as requested. > > On 23 Feb 2020, at 20:00, Tim J

Re: Commit access request (File operations plugin)

t;> >> As per the adopt a plugin guidelines, I would like to request commit access >> to the file operations plugin: >> >> Plugin Repo: https://github.com/jenkinsci/file-operations-plugin >> PR I would like to deliver: >> https://github.com/jenkinsci/file-operatio

Re: Commit access request (File operations plugin)

Please cc him in this thread, if there’s no response we normally wait 2 weeks from cc and then grant access On Sun, 23 Feb 2020 at 18:23, Ramzi El-Yafi wrote: > Hi, > > As per the adopt a plugin guidelines, I would like to request commit > access to the file operations plugin: >

Commit access request (File operations plugin)

Hi, As per the adopt a plugin guidelines, I would like to request commit access to the file operations plugin: *Plugin Repo: *https://github.com/jenkinsci/file-operations-plugin *PR I would like to deliver: * https://github.com/jenkinsci/file-operations-plugin/pull/9 *GitHub Id:* relyafi

Re: [gitlab-oauth-plugin] Request commit access

Maybe try creating the permission-updater PR, and tagging them incase they have some sort of email filtering going on. On Tue, Nov 12, 2019 at 10:41 AM Björn Kasteleiner wrote: > Hello, > > thanks to Gavin and Oleg for replying to my mails. > It was a good idea to try another way to contact the

Re: [gitlab-oauth-plugin] Request commit access

Hello, thanks to Gavin and Oleg for replying to my mails. It was a good idea to try another way to contact the current maintainer. The situation is kind of weird and I'm not sure if I should continue the adoption process. Two hours after my email on the 7th the current maintainer merged the

Re: [gitlab-oauth-plugin] Request commit access

Yes, we usually CC folks in the email to the dev list. It is what Bjoern did in the original email, and the email in the profile was used. +1 for a PR to Repository Permission updater and the final CC, but I believe that 2-week timeout is over. We can do the transfer this week On Thursday,

Re: [gitlab-oauth-plugin] Request commit access

I reached out on twitter - https://twitter.com/halkeye/status/1192334639844577280, just in case https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin doesn't give explicit steps I think since this has the time elapsed, the best thing is to make an INFRA ticket on jira to get write access to

Re: [gitlab-oauth-plugin] Request commit access

Hello, I would like to adopt the gitlab-oauth plugin, since the current maintainer isn't responding anymore. What do I have to do to become maintainer of the plugin? Thanks a lot. Cheers Bjoern Am 21.10.19 um 06:47 schrieb Björn Kasteleiner: Hello, I would like to adopt the

[gitlab-oauth-plugin] Request commit access

Hello, I would like to adopt the gitlab-oauth-pugin, to take care of the current issues of the plugin. Gitlab-User-Id: bjkastel Jenkins-User-Id: bjkastel I've already tried to contact the current maintainer at the beginning of September, unfortunately he hasn't answered yet. I've added him

Re: Commit access to plugin office-365-connector-plugin

Not sure who is that Nishant you are talking about, can't find a reference in that thread apart from yours. I think we can move forward though. Last commit in April 2018. As Joseph said, also, following the process helps everyone :). Just had to look up your GH username, and that almost made me

Re: Commit access to plugin office-365-connector-plugin

Hi, So as I said, I've provided information which was requested by Nishant but then the communication has died. I was trying to get the feedback or status two times during last week but without any success :( Damian > I've provided information requested by Nishant Garg who sent me > private

Re: Commit access to plugin office-365-connector-plugin

I've provided information requested by Nishant Garg who sent me private email. Damian >> On 21. Feb 2019, at 08:29, Joseph P wrote: >> >> We have to wait for 2 weeks  > Please also try to contact the original maintainer. -- You received this message because you are subscribed to the

Re: Commit access to plugin office-365-connector-plugin

> On 21. Feb 2019, at 08:29, Joseph P wrote: > > We have to wait for 2 weeks  Please also try to contact the original maintainer. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

Re: Commit access to plugin office-365-connector-plugin

The procedure is pretty clear: https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess We have to wait for 2 weeks  On Thursday, February 21, 2019 at 12:31:41 AM UTC+1, Tyler Smith wrote: > > With the rise in popularity of MS Teams, this plugin needs an active

Re: Commit access to plugin office-365-connector-plugin

With the rise in popularity of MS Teams, this plugin needs an active maintainer or two. There are many bug fixes and features waiting for a maintainer to merge and released. I think the original author is `outconn` and he hasn't been very active in GitHub in the last year, how can we go over

Re: Commit access to plugin office-365-connector-plugin

Title: Re: Commit access to plugin office-365-connector-plugin I don't know who is the original author but I see you have merged recent commits then I believe your opinion matters. Also added second maintainer to CC. Damian You should cc the original authors. On Monday, February 18, 2019

Re: Commit access to plugin office-365-connector-plugin

You should cc the original authors. On Monday, February 18, 2019 at 12:27:53 AM UTC+1, damian.pu...@gmail.com wrote: > > Hi, > > As active user and contributor of the office-365-connector-plugin > I'd > > like to

Commit access to plugin office-365-connector-plugin

Hi, As active user and contributor of the office-365-connector-plugin I'd like to have permission to merge and publish new versions. There are a few reasons for that: - plugin is currently unmaintainable by

Re: Request commit access for lockable-resources-plugin

hanges done last November? > > Am Montag, 19. November 2018 13:12:19 UTC+1 schrieb Antonio Muñiz: >> >> Hello, >> >> I just commented in the PR. >> >> On Fri, 9 Nov 2018 at 15:51, Heiko Bennewitz >> wrote: >> >>> Hello, >>> >&

Re: Request commit access for lockable-resources-plugin

Hello, do you have any time left to look at the changes done last November? Am Montag, 19. November 2018 13:12:19 UTC+1 schrieb Antonio Muñiz: > > Hello, > > I just commented in the PR. > > On Fri, 9 Nov 2018 at 15:51, Heiko Bennewitz > wrote: > >> Hello, >>

Fwd: Request commit access for lockable-resources-plugin

://github.com/jenkinsci/lockable-resources-plugin Me on github: haithir Me on Jenkins.io: haithir Thank you, Heiko Bennewitz Am Freitag, 9. November 2018 15:51:40 UTC+1 schrieb Heiko Bennewitz: > > Hello, > > I’d like to request commit access for > https://github.com/jenkinsci/lockable-r

Re: [Slack plugin] Request commit access

ke over this plugin? >> >> I've tagged on github: >> >> On Wed, 14 Nov 2018 at 20:27, Tim Jacomb wrote: >> >>> CC maintainers >>> >>> On Wed, 14 Nov 2018 at 20:25, Tim Jacomb wrote: >>> >>>> Hi >>>> >>

Re: [Slack plugin] Request commit access

plugin? > > I've tagged on github: > > On Wed, 14 Nov 2018 at 20:27, Tim Jacomb > > wrote: > >> CC maintainers >> >> On Wed, 14 Nov 2018 at 20:25, Tim Jacomb > > wrote: >> >>> Hi >>> >>> I would like to request commit acce

Re: [Slack plugin] Request commit access

2018 at 20:27, Tim Jacomb wrote: > >> CC maintainers >> >> On Wed, 14 Nov 2018 at 20:25, Tim Jacomb wrote: >> >>> Hi >>> >>> I would like to request commit access for the slack plugin >>> It has been discussed briefly here: >>

Re: [Slack plugin] Request commit access

: > >> Hi >> >> I would like to request commit access for the slack plugin >> It has been discussed briefly here: >> https://github.com/jenkinsci/slack-plugin/issues/402 >> >> Github: timja >> Jenkins infra: timja >> >> Thanks >> Tim

Re: Request commit access for lockable-resources-plugin

Hello, I just commented in the PR. On Fri, 9 Nov 2018 at 15:51, Heiko Bennewitz wrote: > Hello, > > I’d like to request commit access for > https://github.com/jenkinsci/lockable-resources-plugin. > > As suggested I waited one week for answer on my pull request. > > &

Re: [Build failure analyzer] Request commit access

; > Den tis 13 nov. 2018 kl 21:36 skrev Tim Jacomb : > >> CC maintainers >> >> On Tue, 13 Nov 2018 at 20:31, Tim Jacomb wrote: >> >>> Hi >>> >>> I would like to request commit access for the build failure analyzer >>> plugin >>

Re: [Build failure analyzer] Request commit access

mb wrote: > >> Hi >> >> I would like to request commit access for the build failure analyzer >> plugin >> >> I would like to clean it up and do some more development on it >> >> Github: timja >> Jenkins infra: timja >> >>

Re: [Slack plugin] Request commit access

CC maintainers On Wed, 14 Nov 2018 at 20:25, Tim Jacomb wrote: > Hi > > I would like to request commit access for the slack plugin > It has been discussed briefly here: > https://github.com/jenkinsci/slack-plugin/issues/402 > > Github: timja > Jenkins infra: timja >

[Slack plugin] Request commit access

Hi I would like to request commit access for the slack plugin It has been discussed briefly here: https://github.com/jenkinsci/slack-plugin/issues/402 Github: timja Jenkins infra: timja Thanks Tim -- You received this message because you are subscribed to the Google Groups "Je

[Slack plugin] Request commit access

Hi I would like to request commit access for the slack plugin It has been discussed briefly here: https://github.com/jenkinsci/slack-plugin/issues/402 Github: timja Jenkins infra: timja Thanks Tim -- You received this message because you are subscribed to the Google Groups "Je

Re: [Build failure analyzer] Request commit access

CC maintainers On Tue, 13 Nov 2018 at 20:31, Tim Jacomb wrote: > Hi > > I would like to request commit access for the build failure analyzer plugin > > I would like to clean it up and do some more development on it > > Github: timja > Jenkins infra: timja > > Than

[Build failure analyzer] Request commit access

Hi I would like to request commit access for the build failure analyzer plugin I would like to clean it up and do some more development on it Github: timja Jenkins infra: timja Thanks Tim -- You received this message because you are subscribed to the Google Groups "Jenkins Developers&q

Request commit access for lockable-resources-plugin

Hello, I’d like to request commit access for https://github.com/jenkinsci/lockable-resources-plugin. As suggested I waited one week for answer on my pull request. Me on github: haithir Me on Jenkins.io: haithir Thank you, Heiko Bennewitz Heiko Bennewitz *SENIOR SOFTWARE ENGINEER

Re: Commit access for ease-plugin

> On 8. Nov 2018, at 12:26, Baptiste Mathus wrote: > > Just redid it a few seconds now, you *have* to accept the invitation before > permissions are enabled. > This, by the way, is the reason. -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: Commit access for ease-plugin

gt; Cheers >>> >>> Le jeu. 4 oct. 2018 à 21:01, Robert Friedman a >>> écrit : >>> >>>> I have submitted the PR to the permissions repo, and I am not sure what >>>> type of approval you need from the previous maintainers. A comment in the >

Re: Commit access for ease-plugin

>>> type of approval you need from the previous maintainers. A comment in the >>> permissions PR? >>> >>> In case it helps, I did a PR to the plugin repo and got one of the >>> previous maintainers to merge that. Is that sufficient? >>> >>> T

Re: Commit access for ease-plugin

iners to merge that. Is that sufficient? >> >> Thanks! >> >> >> On Tuesday, September 25, 2018 at 5:19:53 PM UTC-4, Robert Friedman wrote: >>> >>> Hello, I would like to get commit access to the plugin >>> https://plugins.jenkins.io/

Re: Commit access for ease-plugin

repo and got one of the > previous maintainers to merge that. Is that sufficient? > > Thanks! > > > On Tuesday, September 25, 2018 at 5:19:53 PM UTC-4, Robert Friedman wrote: >> >> Hello, I would like to get commit access to the plugin >> https://plugins.jenkins.io/e

Re: Commit access for ease-plugin

! On Tuesday, September 25, 2018 at 5:19:53 PM UTC-4, Robert Friedman wrote: > > Hello, I would like to get commit access to the plugin > https://plugins.jenkins.io/ease-plugin. My company developed it > originally but the 2 maintainers are no longer involved. We are planning

Re: Commit access for ease-plugin

Hello, please file a PR in the permissions repository, and get approval from at least one of the previous maintainers. Thanks Le mar. 25 sept. 2018 à 23:19, Robert Friedman a écrit : > Hello, I would like to get commit access to the plugin > https://plugins.jenkins.io/ease-plugin. My c

Commit access for ease-plugin

Hello, I would like to get commit access to the plugin https://plugins.jenkins.io/ease-plugin. My company developed it originally but the 2 maintainers are no longer involved. We are planning to update it within the next few weeks with a new version. Github ID: rufriedman Jenkins.io: rfriedman

Re: Commit access for plugin usage plugin and PR that adds version information

Timeout expired indeed, just made you committer on this plugin. To be able to release you need to file a PR on https://github.com/jenkins-infra/repository-permissions-updater/ Welcome aboard and thanks a lot for stepping up! 2018-03-01 16:49 GMT+01:00 Michał Laskowski

Re: Commit access for plugin usage plugin and PR that adds version information

that state I can become one : https://wiki.jenkins.io/disp >>> lay/JENKINS/Pull+Request+to+Repositories >>> While Java is not my first language, this plugin is fairly simple and I >>> would like to ask for commit access. >>> >>> Of course I will release

Re: Commit access for plugin usage plugin and PR that adds version information

one : >> https://wiki.jenkins.io/display/JENKINS/Pull+Request+to+Repositories >> While Java is not my first language, this plugin is fairly simple and I >> would like to ask for commit access. >> >> Of course I will release a new version was the PR is merged. >>

Re: Commit access for plugin usage plugin and PR that adds version information

gt; the rules that state I can become one : https://wiki.jenkins.io/disp > lay/JENKINS/Pull+Request+to+Repositories > While Java is not my first language, this plugin is fairly simple and I > would like to ask for commit access. > > Of course I will release a new version was t

Commit access for plugin usage plugin and PR that adds version information

://wiki.jenkins.io/display/JENKINS/Pull+Request+to+Repositories While Java is not my first language, this plugin is fairly simple and I would like to ask for commit access. Of course I will release a new version was the PR is merged. My GitHub username: michallaskowski Thanks, Michal -- You received

Not sure how to request commit access to the GitHub repo

: Bergquist, Brett; Mention Subject: Re: [jenkins-infra/repository-permissions-updater] Added Brett Bergquist (bbergquist) as a committer for the project (#504) @bbergquist0930<https://github.com/bbergquist0930> Please let me know if you still need commit access to the GitHub repo.

Re: Commit access to vstestrunner-plugin

or a > shorter timeline. > > > > Of course I can wait for whatever length of time seems best. If this > simply has to be tabled until 17 or 18 October that’s fine. Let me know > what you think. > > > > Erik, > > I granted you commit access. > > Ideally y

Re: Commit access to vstestrunner-plugin

tivity might have allowed for a shorter > timeline. > > Of course I can wait for whatever length of time seems best. If this simply > has to be tabled until 17 or 18 October that’s fine. Let me know what you > think. > Erik, I granted you commit access. Ideally you'll take over m

vstestrunner-plugin: Requesting Commit access

Requesting commit access to vstestrunner-plugin. JIRA id: egoughnour GitHub id: egoughnour [Wiki id: egoughnour] Refer to https://jenkins.io/project/governance/#plugin-committers and http://wiki.jenkins.io/display/JENKINS/Pull+Request+to+Repositories I have asked and waited, following all

Re: Commit access to vstestrunner-plugin

Requesting commit access. By anyone’s count this has now been a sufficient wait. On Tuesday, October 17, 2017, Erik Goughnour <e.goughn...@gmail.com> wrote: > Picking this back up again. Would it still be premature to request commit > access? > > On Thursday, October 5, 20

Re: Commit access to vstestrunner-plugin

Picking this back up again. Would it still be premature to request commit access? On Thursday, October 5, 2017, Erik Goughnour <e.goughn...@gmail.com> wrote: > I did read the link. I had actually read it (along with quite a bit of > the rest of the documentation) before I cr

Re: Commit access to vstestrunner-plugin

10-05 16:17 GMT+02:00 Erik Goughnour <e.goughn...@gmail.com > <javascript:_e(%7B%7D,'cvml','e.goughn...@gmail.com');>>: > >> Requesting commit access again. >> >> Surely the touchstones are all giving favorable indications by now. >> >> Elapse

Re: Commit access to vstestrunner-plugin

Well, technically if you read the link I provided, we would usually wait again ~13 days, given IIUC you've CCed Yasu yesterday (?). 2017-10-05 16:17 GMT+02:00 Erik Goughnour <e.goughn...@gmail.com>: > Requesting commit access again. > > Surely the touchstones are all giving favora

Re: Commit access to vstestrunner-plugin

Requesting commit access again. Surely the touchstones are all giving favorable indications by now. Elapsed time, respect, courtesy, required information, multiple attempts to contact—was there anything else? Thanks, Erik On Wednesday, October 4, 2017, Erik Goughnour <e.goughn...@gmail.

Re: Commit access to vstestrunner-plugin

斎藤ヤスユキ様 始めまして。ところでお名前の漢字はどう書きますか？これ突然のメールで申し訳ないです。そしてほんとうに宜しく御願いします。 御返事を待ちしております。 Erik Goughnour On Tuesday, October 3, 2017, Erik Goughnour wrote: > Yasu is CC’d now. The user email listed in GitHub matches the last git >

Re: Commit access to vstestrunner-plugin

Yasu is CC’d now. The user email listed in GitHub matches the last git log entry’s email. On Tuesday, October 3, 2017, Baptiste Mathus wrote: > Hello, > > Basically we require a best effort to contact previous maintainer. Please > follow

Re: Commit access to vstestrunner-plugin

Hello, Basically we require a best effort to contact previous maintainer. Please follow https://wiki.jenkins.io/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-Requestcommitaccess Try to ping the maintainer by adding her/him in CC of this very thread (hint: emails are generally attached to commit

Re: Commit access to vstestrunner-plugin

I forwarded this thread to Yasu as of a few days ago. [I have to pause here and admit I am not incredibly familiar with Google Groups.] Is there a better way to solicit a response? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Commit access to vstestrunner-plugin

That would be @yasu-s. On Monday, September 25, 2017 at 12:30:28 AM UTC-5, Daniel Beck wrote: > > > > On 25. Sep 2017, at 01:39, Erik Goughnour > wrote: > > > > Can I get access to vstestrunner-plugin? > > Please make sure to include the current/previous maintainers in

Re: Commit access to vstestrunner-plugin

> On 25. Sep 2017, at 01:39, Erik Goughnour wrote: > > Can I get access to vstestrunner-plugin? Please make sure to include the current/previous maintainers in this request to give them a chance to respond, if they're still around. It doesn't look like there's a lot

Commit access to vstestrunner-plugin

Hello All, Can I get access to vstestrunner-plugin? I have submitted two issues and opened a pull request to fix them. I do have an interest in making sure the plugin works. I set up Jenkins jobs pretty frequently and it's difficult to run and track .NET tests without it. Thanks, Erik --

Re: Request commit access to a CppCheck plugin

+1 вторник, 29 августа 2017 г., 15:05:50 UTC-7 пользователь Marcin Kolny написал: > > Hi, > I'd like to ask for commit access to a CppCheck plugin ( > https://github.com/jenkinsci/cppcheck-plugin/) > Based on the discussion: > https://github.com/jenkinsci/cppcheck-plugin/pu

Request commit access to a CppCheck plugin

Hi, I'd like to ask for commit access to a CppCheck plugin ( https://github.com/jenkinsci/cppcheck-plugin/) Based on the discussion: https://github.com/jenkinsci/cppcheck-plugin/pull/36#issuecomment-323684872 current maintainer is no longer interested in this project, so I'd like to take

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,

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

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

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

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

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 >

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

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

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,

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

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

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'

Re: Request for commit access

rew 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 >

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/jenkins

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

Re: commit access to scm-sync-configuration-plugin

Adding owner and last active maintainer. Guys, may I have commit access to the repo https://github.com/jenkinsci/scm-sync-configuration-plugin please? So I could help with maintenance. Thanks! P.S. my github id: mavlyutov jenkins user id: mavlyutov On Fri, Dec 9, 2016 at 12:53 PM, Baptiste

Re: commit access to scm-sync-configuration-plugin

Hello, that's cool, thanks for considering that! Please follow the process https://wiki.jenkins-ci.org/display/JENKINS/Adopt+a+Plugin#AdoptaPlugin-IknowwhichpluginIwanttohelpwith%2CwhatshouldIdonow%3F especially the "Request commit access" part Thanks! 2016-12-08 13:16 GMT+01:00 Iv

  1   2   3   4   5   6   >