Re: Maintainer for Log Parser Plugin

okay, thanks. Done ;) On Tue, Jul 2, 2019 at 3:36 PM Daniel Beck wrote: > > > > On 2. Jul 2019, at 14:18, Martin Reinhardt > wrote: > > > > sorry, my vault. my account (mreinhardt in jenkins-ci.org) is not > allowed to publish: > > > > [ERROR] Failed to execute goal >

Re: Maintainer for Log Parser Plugin

> On 2. Jul 2019, at 14:18, Martin Reinhardt wrote: > > sorry, my vault. my account (mreinhardt in jenkins-ci.org) is not allowed to > publish: > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on > project log-parser: Failed

Re: Maintainer for Log Parser Plugin

BTW: On Github my account (hypery2k) can also not access the settings tab of the repo -- 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: Maintainer for Log Parser Plugin

sorry, my vault. my account (mreinhardt in jenkins-ci.org) is not allowed to publish: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project log-parser: Failed to deploy artifacts: Could not transfer artifact

Re: Maintainer for Log Parser Plugin

I'm surprised to see that you seem to have decided to not release to Jenkins update sites.[1][2] Could you explain this? Should we suspend distribution of previous log-parser plugin releases, as its newest releases are no longer distributed via update sites? 1:

Re: Maintainer for Log Parser Plugin

thanks Am Mittwoch, 26. Juni 2019 08:35:34 UTC+2 schrieb Oleg Nenashev: > > Hi Martin, > > I have updated the permissions. You should have access now > > P.S: It looks like nobody is actively looking (e.g. every day) at the dev > list for such requests after I stepped down in December. > We

Re: Maintainer for Log Parser Plugin

Hi Martin, I have updated the permissions. You should have access now P.S: It looks like nobody is actively looking (e.g. every day) at the dev list for such requests after I stepped down in December. We should probably move it to HOSTING in JIRA so that we could get a dashboard (or maybe

Re: Maintainer for Log Parser Plugin

Any update on this? What did I need to do? -- 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

Re: Maintainer for Log Parser Plugin

Any progress on that? More than two weeks were passed :D Am Mittwoch, 12. Juni 2019 11:46:57 UTC+2 schrieb Martin Reinhardt: > > looking forward to friday ;) > > Am Mittwoch, 12. Juni 2019 09:28:57 UTC+2 schrieb Jon Brohauge: >> >> Hi Martin >> >> Thank you for stepping up to be a maintainer of

Re: Maintainer for Log Parser Plugin

looking forward to friday ;) Am Mittwoch, 12. Juni 2019 09:28:57 UTC+2 schrieb Jon Brohauge: > > Hi Martin > > Thank you for stepping up to be a maintainer of this plugin. Can't wait > for the PR's to roll onto master ;-) > > regards > Jon > > On Sunday, June 2, 2019 at 7:33:45 PM UTC+2, Martin

Re: Maintainer for Log Parser Plugin

Hi Martin Thank you for stepping up to be a maintainer of this plugin. Can't wait for the PR's to roll onto master ;-) regards Jon On Sunday, June 2, 2019 at 7:33:45 PM UTC+2, Martin Reinhardt wrote: > > Hi Mike, > > thanks for assisting here. > > My GitHub username is hypery2k > > And me

Re: Maintainer for Log Parser Plugin

Hi Mike, thanks for assisting here. My GitHub username is hypery2k And me Jenkins Account ID is mreinhardt -- Martin Reinhardt Sent with Airmail Am 2. Juni 2019 um 03:43:43, Mark Waite (mark.earl.wa...@gmail.com) schrieb: Thanks in advance for adopting the plugin! I've copied the most

Re: Maintainer for Log Parser Plugin

Thanks in advance for adopting the plugin! I've copied the most recent committers to the plugin on this e-mail to assure that they are OK with your adopting the plugin. If no response is received from them in 2 weeks, or if they respond that they are willing to add you as a maintainer, then the

Re: Maintainer for Log Parser Plugin

The Adopt a Plugin page suggests: Email the Jenkins Developers mailing list and request to be made a maintainer (which usually means commit access to the plugin repository and being made default

Maintainer for Log Parser Plugin

Hi there, i want to step in for the Log Parser Plugin: https://github.com/jenkinsci/lo= g-parser-plugin A already maintain the RocketChat Plugin. Looking forward Regards Martin -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To