Maven says it can't find MasterToSlaveFileCallable

[Adam Chevalier]

I'm working on getting this plugin 
 ready for hosting and 
I've had some problems after updating the parent pom version to 2.6

The first two rounds of compilation errors were resolved by updating some 
dependencies, but then I had to replace a use of FileCallable in the 
plugin. I determined that MasterToSlaveFileCallable was the best fit for 
the intent. However, maven is telling me it can't find that class. This 
doesn't make sense to me, since it's in the core Jenkins package, which I 
have listed as a dependency.

Thanks!

-- 
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://groups.google.com/d/msgid/jenkinsci-dev/ec41a2f1-1634-4cd4-890a-a8fe3fad5e03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem during plugin release

[Jesse Glick]

On Sun, Nov 27, 2016 at 2:43 AM, Thomas Fürer  wrote:
> What about using our own infrastructure at
> https://jenkins.ci.cloudbees.com or https://ci.jenkins-ci.org to release
> the plugins?

Long been on our wishlist; no proposal yet for how to do an
authentication check.

-- 
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://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr15iH%2BH2kbK%3DAPUtROyLG%2Bi8h73e1hUD-Tx8H8iiBkkjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Develop a custom step that would make pipeline wait for a webhook

[Jesse Glick]

On Fri, Nov 25, 2016 at 4:14 AM, Julien HENRY
 wrote:
> I found this ticket https://issues.jenkins-ci.org/browse/JENKINS-27127 that
> is really close to what we need.

Yes, sounds like it. The issue needs to be “defuzzed” somewhat:
concrete proposals written up, possibly broken into multiple features.

> Is there any progress on that topic?

Not currently.

> Waiting for this generic step, do you think it would be possible to
> implement the feature with a custom step?

Sure, there is nothing stopping you from writing a limited version of
this feature tailored to your needs.

https://github.com/jenkinsci/workflow-step-api-plugin/#creating-an-asynchronous-step

plus probably an `UnprotectedRootAction` (take care to consider
malicious payloads).

-- 
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://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0eoqDrV_sMtvN7XR3aPExECjwki4Ckzqg8O93HLKL08A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Credentials Provider

[Kanstantsin Shautsou]

I think you don't need CredentialsProvider, but you need firstly choose 
some `Credentials` type (if there is no suitable, then create own), then 
limit your code to work with it and store only String credentials ID. 
Better look into some existing plugin, i.e. github-plugin (or any other). 

CredentialsProvider is a source (via search/list methods) of Credentials 
that may be (or not) contained in some `CredentialsStore`.


On Monday, November 28, 2016 at 11:27:49 PM UTC+3, Stephen Connolly wrote:
>
> I am planning on working on some guides for integrating with the 
> credentials API in the near future. Responding to this thread is also on my 
> todo list
>
> On Mon 21 Nov 2016 at 22:36, Fritz Elfert  > wrote:
>
>> Somehow your screenshots are cut off - I cant see any Test-Connection
>> Button?!
>>
>> Anyway, implementing a test-connection is actually quite easy using a
>> validateButton element. It works like this:
>>
>> supposed, in your .jelly form you have the input-fields named "user",
>> "url" and "key", then you can write in your jelly:
>>
>> > method="testConnection" with="user,url,key"/>
>>
>> In your corresponding DescriptorImpl you then simply put a method that
>> gets the parameters specified in the with="..." attribute like this:
>>
>> public FormValidation doTestConnection(@QueryParameter String user,
>> @QueryParameter String url, @QueryParameter String key) throws 
>> IOException {
>> ...
>> }
>>
>> you get the idea ...
>>  -Fritz
>>
>> On 21.11.2016 22:11, iwarapter wrote:
>> > Hi,
>> >
>> > I'm currently in the process of creating a new credentials provider and
>> > looking for feedback on the based where to implement its authentication
>> > with the backend.
>> >
>> > I have two ways i can probably go with this one is provide the
>> > authentication through credentials similar to the kubernetes plugin for
>> > example:
>> >
>> > <
>> https://lh3.googleusercontent.com/-hXbsw3-YWd4/WDNgjt84AHI/ACg/tWrThothLN0yJchUEJT7b3l26jJNsHMaQCLcB/s1600/Screen%2BShot%2B2016-11-21%2Bat%2B20.59.05.png
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > The alternative is i provide it directly using something similar to the
>> > private key source
>> > <
>> https://github.com/jenkinsci/ssh-credentials-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPrivateKey.java#L270
>> >
>> > mechanic used in the ssh-credentials plugin:
>> >
>> > <
>> https://lh3.googleusercontent.com/-AOC4CXYnZsc/WDNhde8cBQI/ACo/uUVEYKp22Wct31TJ8AmPbSo0y1CG8PNcQCLcB/s1600/Screen%2BShot%2B2016-11-21%2Bat%2B20.56.38.png
>> >
>> >
>> >
>> > The problem with the second option is providing a 'Test Connection'
>> > style button is very hard (i have no idea if Jelly could even do it).
>> > Whilst providing that feature with the first option is easy, however it
>> > seems a little silly using the original credentials provider as i would
>> > have to implement a new credential impl (for tokens). Am i over thinking
>> > this? I'm aware poor choices early on have the potential to cause alot
>> > of pain later down the line.
>> >
>> > Happy for feedback!
>> >
>> > --
>> > 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-de...@googlegroups.com 
>> > .
>> > To view this discussion on the web visit
>> > 
>> https://groups.google.com/d/msgid/jenkinsci-dev/6366b390-4a7b-4880-b35b-e661cc73d645%40googlegroups.com
>> > <
>> https://groups.google.com/d/msgid/jenkinsci-dev/6366b390-4a7b-4880-b35b-e661cc73d645%40googlegroups.com?utm_medium=email&utm_source=footer
>> >.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
>> 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-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/b1b6122a-7357-1b9d-1f5b-39c16cf729fc%40fritz-elfert.de
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> Sent from my phone
>

-- 
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://groups.google.com/d/msgid/jenkinsci-dev/ae918297-a25d-44c4-9972-ded8ce312a3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Credentials Provider

[Stephen Connolly]

I am planning on working on some guides for integrating with the
credentials API in the near future. Responding to this thread is also on my
todo list

On Mon 21 Nov 2016 at 22:36, Fritz Elfert  wrote:

> Somehow your screenshots are cut off - I cant see any Test-Connection
> Button?!
>
> Anyway, implementing a test-connection is actually quite easy using a
> validateButton element. It works like this:
>
> supposed, in your .jelly form you have the input-fields named "user",
> "url" and "key", then you can write in your jelly:
>
>  method="testConnection" with="user,url,key"/>
>
> In your corresponding DescriptorImpl you then simply put a method that
> gets the parameters specified in the with="..." attribute like this:
>
> public FormValidation doTestConnection(@QueryParameter String user,
> @QueryParameter String url, @QueryParameter String key) throws IOException
> {
> ...
> }
>
> you get the idea ...
>  -Fritz
>
> On 21.11.2016 22:11, iwarapter wrote:
> > Hi,
> >
> > I'm currently in the process of creating a new credentials provider and
> > looking for feedback on the based where to implement its authentication
> > with the backend.
> >
> > I have two ways i can probably go with this one is provide the
> > authentication through credentials similar to the kubernetes plugin for
> > example:
> >
> > <
> https://lh3.googleusercontent.com/-hXbsw3-YWd4/WDNgjt84AHI/ACg/tWrThothLN0yJchUEJT7b3l26jJNsHMaQCLcB/s1600/Screen%2BShot%2B2016-11-21%2Bat%2B20.59.05.png
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > The alternative is i provide it directly using something similar to the
> > private key source
> > <
> https://github.com/jenkinsci/ssh-credentials-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPrivateKey.java#L270
> >
> > mechanic used in the ssh-credentials plugin:
> >
> > <
> https://lh3.googleusercontent.com/-AOC4CXYnZsc/WDNhde8cBQI/ACo/uUVEYKp22Wct31TJ8AmPbSo0y1CG8PNcQCLcB/s1600/Screen%2BShot%2B2016-11-21%2Bat%2B20.56.38.png
> >
> >
> >
> > The problem with the second option is providing a 'Test Connection'
> > style button is very hard (i have no idea if Jelly could even do it).
> > Whilst providing that feature with the first option is easy, however it
> > seems a little silly using the original credentials provider as i would
> > have to implement a new credential impl (for tokens). Am i over thinking
> > this? I'm aware poor choices early on have the potential to cause alot
> > of pain later down the line.
> >
> > Happy for feedback!
> >
> > --
> > 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://groups.google.com/d/msgid/jenkinsci-dev/6366b390-4a7b-4880-b35b-e661cc73d645%40googlegroups.com
> > <
> https://groups.google.com/d/msgid/jenkinsci-dev/6366b390-4a7b-4880-b35b-e661cc73d645%40googlegroups.com?utm_medium=email&utm_source=footer
> >.
> > For more options, visit https://groups.google.com/d/optout.
>
>
> --
> 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://groups.google.com/d/msgid/jenkinsci-dev/b1b6122a-7357-1b9d-1f5b-39c16cf729fc%40fritz-elfert.de
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Sent from my phone

-- 
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://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMx1RxGqV2p-xw2wfGW2hVWKCgzvVJKJVoM2rVAK%2BXEGjA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[Jacob Larfors]

Hi Oleg,

Awesome, and thanks Daniel & Gregory.

See you tomorrow.

Best Regards,
Jacob

> On 28 Nov 2016, at 17.35, Oleg Nenashev  wrote:
> 
> Hi,
> 
> Just FYI, we have got a reply from Gregory in the separate thread. Now you 
> have an authorization 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  >:
> Hi Oleg,
> 
> That's great - I saw the meeting summary so thanks for bringing this to 
> light. I spoke with our plugin developer on Friday and we will get the plugin 
> updated and ready for release whilst we wait for a reply from gboissinot and 
> prepare a branch on the jenkinsci project ready for a pull request.
> 
> Hopefully see you at the CoDe Conf tomorrow so we can talk about this a bit 
> more.
> 
> Safe travels with Lufthansa.
> 
> Best Regards,
> Jacob
> 
> 
> On Saturday, 26 November 2016 07:58:30 UTC+1, Oleg Nenashev wrote:
> Hi Jacob,
> 
> On Wednesday we agreed with the proposed plan. Here is the meeting summary: 
> http://meetings.jenkins-ci.org/jenkins-meeting/2016/jenkins-meeting.2016-11-23-18.00.html
>  
> 
> 
> We agreed that I and Daniel will make the last attempt to reach out the 
> original plugin maintainers with a final 2-week timeout. If we do not get a 
> response, we will grant you the release permissions, no need in plugin 
> renaming, etc.
> 
> I have granted you push permissions to 
> https://github.com/jenkinsci/klocwork-plugin 
> , hence you can start 
> integrating changes there. I kindly recommend to consider using Pull requests 
> and CCing 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 г., 11:19:27 UTC+3 пользователь Jacob Larfors написал:
> Many thanks for helping so much with this. The plan sounds good to me.
> 
> My Jenkinsci account is: jlarfors
> 
> Thanks again,
> Jacob
> 
> On Tuesday, 22 November 2016 18:05:20 UTC+1, Oleg Nenashev wrote:
> I have added the the topic to the agenda of the tomorrow's governance 
> meeting: 
> https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Nov23meeting
>  
> 
> 
> Jacob, could you please provide your Jenkinsci account?
> 
> Thanks in advance,
> Oleg
> 
> вторник, 22 ноября 2016 г., 17:44:02 UTC+1 пользователь Oleg Nenashev написал:
> In addition to this thread, I have tried to reach out Gregory directly 
> without success. Since he has left his original company as well as his 
> companion from citools org, it is a low chance we can proceed in the common 
> way.
> 
> I had an f2f discussion with Jacob at Embedded Conference Scandinavia. We 
> discussed the current state and agreed on the following:
> Oleg will grant him an access to the klocwork repository within the jenkinsci 
> organization (an existing repo)
> Jacob will push the current changes in citools org and then proceed with 
> preparing the release in pull requests (he can use jenkinsci/code-reviewers 
> in order to get help with onboarding)
> Oleg will try to reach out Thales directly on behalf of the Jenkins core team 
> (in order to propose the ownership handover)
> If we do not get a response from Thales, we will submit a topic to the 
> Governance meeting with 2 options:
> Fork of a plugin with renaming/package name changes
> Just a takeover of the plugin by the Jenkins community (with temporary 
> revokation of upload permissions for original maintainers to avoid mess if 
> they come back and do not notice this thread)
> WDYT?
> 
> 
> 
> Best regards,
> 
> Oleg
> 
> 
> 
> среда, 16 ноября 2016 г., 16:11:58 UTC+1 пользователь Oleg Nenashev написал:
> Any revival of this plugin will be appreciated.
> 
> Unfortunately, we cannot just fork the repository and start releasing from 
> it. It may be considered as a highjacking of the plugin. Plugin maintainers 
> commonly do not sign Jenkins CLA, hence we have no formal permission to do so.
> 
> I think we should fork the plugin to jenkinsci and start preparing it to the 
> 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 the proper migration code.
> 
> I've added Gregory Boissinot to Cc. Maybe he could suggest the proper contact.
> 
> BR, Oleg
> 
> 
> вторник, 15 ноября 2016 г., 14:13:29 UTC+1 пользователь Jacob Larfors написал:
> Ok I tried contacti

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

[Oleg Nenashev]

Hi,

Just FYI, we have got a reply from Gregory in the separate thread. Now you
have an authorization 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 :

> Hi Oleg,
>
> That's great - I saw the meeting summary so thanks for bringing this to
> light. I spoke with our plugin developer on Friday and we will get the
> plugin updated and ready for release whilst we wait for a reply from
> gboissinot and prepare a branch on the jenkinsci project ready for a pull
> request.
>
> Hopefully see you at the CoDe Conf tomorrow so we can talk about this a
> bit more.
>
> Safe travels with Lufthansa.
>
> Best Regards,
> Jacob
>
>
> On Saturday, 26 November 2016 07:58:30 UTC+1, Oleg Nenashev wrote:
>>
>> Hi Jacob,
>>
>> On Wednesday we agreed with the proposed plan. Here is the meeting
>> summary: http://meetings.jenkins-ci.org/jenkins-meeting/2016/jenkins-
>> meeting.2016-11-23-18.00.html
>>
>> We agreed that I and Daniel will make the last attempt to reach out the
>> original plugin maintainers with a final 2-week timeout. If we do not get a
>> response, we will grant you the release permissions, no need in plugin
>> renaming, etc.
>>
>> I have granted you push permissions to https://github.com/jenkinsci/k
>> locwork-plugin, hence you can start integrating changes there. I kindly
>> recommend to consider using Pull requests and CCing
>> 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 г., 11:19:27 UTC+3 пользователь Jacob Larfors
>> написал:
>>>
>>> Many thanks for helping so much with this. The plan sounds good to me.
>>>
>>> My Jenkinsci account is: jlarfors
>>>
>>> Thanks again,
>>> Jacob
>>>
>>> On Tuesday, 22 November 2016 18:05:20 UTC+1, Oleg Nenashev wrote:

 I have added the the topic to the agenda of the tomorrow's governance
 meeting: https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeti
 ng+Agenda#GovernanceMeetingAgenda-Nov23meeting

 Jacob, could you please provide your Jenkinsci account?

 Thanks in advance,
 Oleg

 вторник, 22 ноября 2016 г., 17:44:02 UTC+1 пользователь Oleg Nenashev
 написал:
>
> In addition to this thread, I have tried to reach out Gregory directly
> without success. Since he has left his original company as well as his
> companion from citools org, it is a low chance we can proceed in the 
> common
> way.
>
> I had an f2f discussion with Jacob at Embedded Conference Scandinavia.
> We discussed the current state and agreed on the following:
>
>1. Oleg will grant him an access to the klocwork repository within
>the jenkinsci organization (an existing repo)
>2. Jacob will push the current changes in citools org and then
>proceed with preparing the release in pull requests (he can use
>jenkinsci/code-reviewers in order to get help with onboarding)
>3. Oleg will try to reach out Thales directly on behalf of the
>Jenkins core team (in order to propose the ownership handover)
>4. If we do not get a response from Thales, we will submit a topic
>to the Governance meeting with 2 options:
>   - Fork of a plugin with renaming/package name changes
>   - Just a takeover of the plugin by the Jenkins community (with
>   temporary revokation of upload permissions for original maintainers 
> to
>   avoid mess if they come back and do not notice this thread)
>
> WDYT?
>
>
> Best regards,
>
> Oleg
>
>
> среда, 16 ноября 2016 г., 16:11:58 UTC+1 пользователь Oleg Nenashev
> написал:
>>
>> Any revival of this plugin will be appreciated.
>>
>> Unfortunately, we cannot just fork the repository and start releasing
>> from it. It may be considered as a highjacking of the plugin. Plugin
>> maintainers commonly do not sign Jenkins CLA, hence we have no formal
>> permission to do so.
>>
>> I think we should fork the plugin to jenkinsci and start preparing it
>> to the 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 the proper migration code.
>>
>> I've added Gregory Boissinot to Cc. Maybe he could suggest the proper
>> contact.
>>
>> BR, Oleg
>>
>> вторник, 15 ноября 2016 г., 14:13:29 UTC+1 пользователь Jacob Larfors
>> написал:
>>>
>>> Ok I tried contacting the other maintainer/user at cittools and his
>>> email address for Thales doe

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

[Jacob Larfors]

Hi Oleg,

That's great - I saw the meeting summary so thanks for bringing this to 
light. I spoke with our plugin developer on Friday and we will get the 
plugin updated and ready for release whilst we wait for a reply from 
gboissinot and prepare a branch on the jenkinsci project ready for a pull 
request.

Hopefully see you at the CoDe Conf tomorrow so we can talk about this a bit 
more.

Safe travels with Lufthansa.

Best Regards,
Jacob

On Saturday, 26 November 2016 07:58:30 UTC+1, Oleg Nenashev wrote:
>
> Hi Jacob,
>
> On Wednesday we agreed with the proposed plan. Here is the meeting 
> summary: 
> http://meetings.jenkins-ci.org/jenkins-meeting/2016/jenkins-meeting.2016-11-23-18.00.html
>
> We agreed that I and Daniel will make the last attempt to reach out the 
> original plugin maintainers with a final 2-week timeout. If we do not get a 
> response, we will grant you the release permissions, no need in plugin 
> renaming, etc.
>
> I have granted you push permissions to 
> https://github.com/jenkinsci/klocwork-plugin, hence you can start 
> integrating changes there. I kindly recommend to consider using Pull 
> requests and CCing 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 г., 11:19:27 UTC+3 пользователь Jacob Larfors 
> написал:
>>
>> Many thanks for helping so much with this. The plan sounds good to me.
>>
>> My Jenkinsci account is: jlarfors
>>
>> Thanks again,
>> Jacob
>>
>> On Tuesday, 22 November 2016 18:05:20 UTC+1, Oleg Nenashev wrote:
>>>
>>> I have added the the topic to the agenda of the tomorrow's governance 
>>> meeting: 
>>> https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Nov23meeting
>>>
>>> Jacob, could you please provide your Jenkinsci account?
>>>
>>> Thanks in advance,
>>> Oleg
>>>
>>> вторник, 22 ноября 2016 г., 17:44:02 UTC+1 пользователь Oleg Nenashev 
>>> написал:

 In addition to this thread, I have tried to reach out Gregory directly 
 without success. Since he has left his original company as well as his 
 companion from citools org, it is a low chance we can proceed in the 
 common 
 way.

 I had an f2f discussion with Jacob at Embedded Conference Scandinavia. 
 We discussed the current state and agreed on the following:

1. Oleg will grant him an access to the klocwork repository within 
the jenkinsci organization (an existing repo)
2. Jacob will push the current changes in citools org and then 
proceed with preparing the release in pull requests (he can use 
jenkinsci/code-reviewers in order to get help with onboarding)
3. Oleg will try to reach out Thales directly on behalf of the 
Jenkins core team (in order to propose the ownership handover)
4. If we do not get a response from Thales, we will submit a topic 
to the Governance meeting with 2 options:
   - Fork of a plugin with renaming/package name changes
   - Just a takeover of the plugin by the Jenkins community (with 
   temporary revokation of upload permissions for original maintainers 
 to 
   avoid mess if they come back and do not notice this thread)
   
 WDYT?


 Best regards,

 Oleg


 среда, 16 ноября 2016 г., 16:11:58 UTC+1 пользователь Oleg Nenashev 
 написал:
>
> Any revival of this plugin will be appreciated.
>
> Unfortunately, we cannot just fork the repository and start releasing 
> from it. It may be considered as a highjacking of the plugin. Plugin 
> maintainers commonly do not sign Jenkins CLA, hence we have no formal 
> permission to do so.
>
> I think we should fork the plugin to jenkinsci and start preparing it 
> to the 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 the proper migration code.
>
> I've added Gregory Boissinot to Cc. Maybe he could suggest the proper 
> contact.
>
> BR, Oleg
>
> вторник, 15 ноября 2016 г., 14:13:29 UTC+1 пользователь Jacob Larfors 
> написал:
>>
>> Ok I tried contacting the other maintainer/user at cittools and his 
>> email address for Thales does not work, so I suspect he has left Thales. 
>> As 
>> there has also been an outstanding pull request since July, and our 
>> attempts to contact the people at cittools has failed, I would assume 
>> this 
>> repository is no longer taken care of...
>>
>> What options do we have? Can we make the jenkinsci repository the 
>> "main"