Re: Request ownership/action for a plugin (klocwork)

e release with patches (including stuff like CI, parent POM update, >>> etc.). If the maintainer does not respond, likely the only valid option >>> will be to rename plugin and to change packages to avoid data conflicts. >>> But it will require much work to implement

Re: Request ownership/action for a plugin (klocwork)

Cing jenkinsci/code-reviewers at the first steps (just to get > some knowledge transfer). It is also recommended to update Jenkins core > dependency to something newer and to use the new parent POM. > > Best regards, > Oleg Nenashev > > > > среда, 23 ноября 2016

Re: Request ownership/action for a plugin (klocwork)

horization from the original maintainer, hence you can proceed > with the release once you are ready. > > See you tomorrow! > > Best regards, > Oleg > > 2016-11-28 16:20 GMT+01:00 Jacob Larfors <ja...@larfors.com > <mailto:ja...@larfors.com>>: > Hi Oleg

Re: Request ownership/action for a plugin (klocwork)

nt > clusterfuck thanks to maintainers maintaining elsewhere. > > I recommend you contact cittools and coordinate what to do with them. I > can then transfer the repo as needed, and delete the one in jenkinsci that > appears to have never been used. > > > On 15.11.

Re: Request ownership/action for a plugin (klocwork)

n and have been shipping hpi files for the past few years to avoid this mess and bottleneck of waiting for cittools. Thanks for the help. Jacob On Tuesday, 15 November 2016 14:59:06 UTC+2, Jacob Larfors wrote: > > Hi Daniel, appreciate the quick feedback and thanks for the info - that &g

Request ownership/action for a plugin (klocwork)

Hi guys, Maybe someone can help me out, but a few weeks back I posted about commit access to the Klocwork plugin, following a pull request for a colleague, and neither have been answered... We really want to push some great features out there but our hands our tied :) If anyone knows how who

Klocwork Plugin commit access

Hello, myself and a colleague have a pull request for the Klocwork Jenkins plugin that has not been responded to. We have tried contacting the owner but cannot get hold of him. Repository: https://github.com/jenkinsci/klocwork-plugin Requesting commit access to this repository as we actively

Re: [Experiment] Reviewers Team

Nice, and thanks for the information. I was recommended to add jenkinsci code-reviewers but perhaps this is not necessary for the low scale plugins I am working on as things have been working fine up until now. PS - I accepted the invitation now to join jenkinsci (email got lost) On Thursday,

Re: Request ownership/action for a plugin (klocwork)

iel Beck <m...@beckweb.net> wrote: > > >> On 01.12.2016, at 12:13, Jacob Larfors <ja...@larfors.com> wrote: >> >> Awesome - looks good. Can I also have commit access to this one, or how do >> we plan to do this? >> >> My plan was to

Re: Request ownership/action for a plugin (klocwork)

Great, I acknowledge and sounds like a good idea - so please go ahead. Thanks, Jacob On Wednesday, 30 November 2016 21:03:00 UTC+2, Daniel Beck wrote: > > > > On 28.11.2016, at 17:44, Jacob Larfors <ja...@larfors.com > > wrote: > > > > Awesome, and than

Re: Request ownership/action for a plugin (klocwork)

All good to delete the jenkinsci/klocwork-plugin-fork repo as it was never used. On Thursday, 1 December 2016 12:32:59 UTC+2, Daniel Beck wrote: > > > > On 01.12.2016, at 11:17, Jacob Larfors <ja...@larfors.com > > wrote: > > > > Great, I acknowledge and so

Re: Request ownership/action for a plugin (klocwork)

iPhone > On 1 Dec 2016, at 13.02, Daniel Beck <m...@beckweb.net> wrote: > > >> On 01.12.2016, at 11:34, Jacob Larfors <ja...@larfors.com> wrote: >> >> All good to delete the jenkinsci/klocwork-plugin-fork repo as it was never >> used. > >

Re: [Experiment] Reviewers Team

Hello, just checking that the @jenkinsci/code-reviewers group is still around? Doesnt seem to exist in GitHub anymore... at least I get a 404 error not found https://github.com/orgs/jenkinsci/teams/code-reviewers I was hoping to get