Re: New Plugin hosting request: Splunk plugin for Jenkins

[Daniel Beck]

Hi Ted,

Hosting requests are regularly reviewed by our team, but it can take a few days 
as it's done by volunteers.

Daniel

> On 27.09.2016, at 14:06, Ted Xiao  wrote:
> 
> I would like to request hosting the Splunk plugin 
> https://wiki.jenkins-ci.org/display/JENKINS/Splunk+plugin+for+Jenkins
> Git repo: https://github.com/splunk/splunkforjenkins
> Jira ticket: https://issues.jenkins-ci.org/browse/HOSTING-201
> License: MIT
> 
> Thanks,
> Ted
> 
> -- 
> 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/f43592d9-ead9-46cb-85b3-34d9b0c677a5%40googlegroups.com.
> 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/7E5370E2-FFEF-4A4C-BC83-7A99B3BF05F2%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin hosting request

[Baptiste Mathus]

Hi Sanketh,

I've made a committer on this plugin and the lead of the JIRA component.
Please review your inbox, you should have received an invitation.
Leonardo is still committer.

So, please start progressively, ideally by filing PR instead of directly
pushing, and asking for review from your co-maintainer, and feel free to
merge it if you don't hear from him under a few days.
Over time, it'll be up to you to choose that strategy.

Thanks for your help.

2016-03-20 10:50 GMT+00:00 Sanketh P B :

> It's a long wait by now. Could you please let me know the next steps?
>
> On Thursday, December 24, 2015 at 3:55:20 AM UTC+5:30, Daniel Beck wrote:
>>
>> Given that it's the end of the year I'd prefer to wait a bit longer to
>> give Leonardo time to respond even if on vacation.
>>
>> > On 23.12.2015, at 19:09, Sanketh P B  wrote:
>> >
>> > Dear Team,
>> >
>> > There is no update from the plugin developer/maintainer, please let me
>> know how to proceed here.
>> >
>> > Thanks,
>> > Sanketh
>> >
>> > On Tuesday, December 15, 2015 at 9:38:27 PM UTC+5:30, Sanketh P B
>> wrote:
>> > Sure, I agree with you. We could enhance the existing plugin.
>> > @Leonardo Kobus: Please provide your inputs on how to proceed.
>> >
>> > Thanks,
>> > Sanketh
>> >
>> > On Monday, December 14, 2015 at 1:32:22 PM UTC+5:30, Oleg Nenashev
>> wrote:
>> > In general we try to avoid creation of new plugins wherever it is
>> possible. IMHO it makes sense to consider integrating the functionality
>> into a single plugin^ because they are very close. I agree that the
>> existing plugin does not cover all your case, but it could be solved by the
>> plugin extension and renaming.
>> >
>> > I've added Leonardo Kobus (maintainer of
>> change-assembly-version-plugin) to Cc.
>> >
>> > воскресенье, 13 декабря 2015 г., 16:46:14 UTC+3 пользователь Sanketh P
>> B написал:
>> > Dear Oleg Nenashev,
>> >
>> > This plugin offers support for frequently performed operations (change
>> in product version, file version and copyright info) on .Net, managed .Net
>> and C++ assembly information in a easy way. The other concentrates on .Net
>> only and for updating versions. Kindly suggest your thoughts, I feel this
>> could be separate plugins.
>> >
>> > Best Regards,
>> > Sanketh
>> >
>> > On Sunday, December 13, 2015 at 2:42:07 AM UTC+5:30, Oleg Nenashev
>> wrote:
>> > Hi Sanketh,
>> >
>> > How the plugin differs from
>> https://github.com/jenkinsci/change-assembly-version-plugin ?
>> > From what I see it would be better to update that plugin instead of
>> creating the new one
>> >
>> > Best regards,
>> > Oleg Nenashev
>> >
>> > пятница, 11 декабря 2015 г., 18:29:12 UTC+3 пользователь Sanketh P B
>> написал:
>> > Dear All,
>> > Any updates here? Is this pending due to any changes required?
>> >
>> > Thanks,
>> > Sanketh
>> >
>> >
>> >
>> > --
>> > 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/57fb76aa-0c69-4053-89ee-66642cc78ce5%40googlegroups.com.
>>
>> > 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/6ddeb357-83ee-4ef0-a16f-03c222131bec%40googlegroups.com
> 
> .
>
> 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/CANWgJS7dWL942EiMLUYhPfKG%3D6%3DsMWDYfkT5ZeET_JXMD-sE0w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin hosting request

[Sanketh P B]

It's a long wait by now. Could you please let me know the next steps?

On Thursday, December 24, 2015 at 3:55:20 AM UTC+5:30, Daniel Beck wrote:
>
> Given that it's the end of the year I'd prefer to wait a bit longer to 
> give Leonardo time to respond even if on vacation. 
>
> > On 23.12.2015, at 19:09, Sanketh P B  
> wrote: 
> > 
> > Dear Team, 
> > 
> > There is no update from the plugin developer/maintainer, please let me 
> know how to proceed here. 
> > 
> > Thanks, 
> > Sanketh 
> > 
> > On Tuesday, December 15, 2015 at 9:38:27 PM UTC+5:30, Sanketh P B wrote: 
> > Sure, I agree with you. We could enhance the existing plugin. 
> > @Leonardo Kobus: Please provide your inputs on how to proceed. 
> > 
> > Thanks, 
> > Sanketh 
> > 
> > On Monday, December 14, 2015 at 1:32:22 PM UTC+5:30, Oleg Nenashev 
> wrote: 
> > In general we try to avoid creation of new plugins wherever it is 
> possible. IMHO it makes sense to consider integrating the functionality 
> into a single plugin^ because they are very close. I agree that the 
> existing plugin does not cover all your case, but it could be solved by the 
> plugin extension and renaming. 
> > 
> > I've added Leonardo Kobus (maintainer of change-assembly-version-plugin) 
> to Cc. 
> > 
> > воскресенье, 13 декабря 2015 г., 16:46:14 UTC+3 пользователь Sanketh P B 
> написал: 
> > Dear Oleg Nenashev, 
> > 
> > This plugin offers support for frequently performed operations (change 
> in product version, file version and copyright info) on .Net, managed .Net 
> and C++ assembly information in a easy way. The other concentrates on .Net 
> only and for updating versions. Kindly suggest your thoughts, I feel this 
> could be separate plugins. 
> > 
> > Best Regards, 
> > Sanketh 
> > 
> > On Sunday, December 13, 2015 at 2:42:07 AM UTC+5:30, Oleg Nenashev 
> wrote: 
> > Hi Sanketh, 
> > 
> > How the plugin differs from 
> https://github.com/jenkinsci/change-assembly-version-plugin ? 
> > From what I see it would be better to update that plugin instead of 
> creating the new one 
> > 
> > Best regards, 
> > Oleg Nenashev 
> > 
> > пятница, 11 декабря 2015 г., 18:29:12 UTC+3 пользователь Sanketh P B 
> написал: 
> > Dear All, 
> > Any updates here? Is this pending due to any changes required? 
> > 
> > Thanks, 
> > Sanketh 
> > 
> > 
> > 
> > -- 
> > 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/57fb76aa-0c69-4053-89ee-66642cc78ce5%40googlegroups.com.
>  
>
> > 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/6ddeb357-83ee-4ef0-a16f-03c222131bec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin hosting request

[Sanketh P B]

Dear Team,

There is no update from the plugin developer/maintainer, please let me know 
how to proceed here.

Thanks,
Sanketh

On Tuesday, December 15, 2015 at 9:38:27 PM UTC+5:30, Sanketh P B wrote:
>
> Sure, I agree with you. We could enhance the existing plugin. 
> @Leonardo Kobus: Please provide your inputs on how to proceed.
>
> Thanks,
> Sanketh
>
> On Monday, December 14, 2015 at 1:32:22 PM UTC+5:30, Oleg Nenashev wrote:
>>
>> In general we try to avoid creation of new plugins wherever it is 
>> possible. IMHO it makes sense to consider integrating the functionality 
>> into a single plugin^ because they are very close. I agree that the 
>> existing plugin does not cover all your case, but it could be solved by the 
>> plugin extension and renaming.
>>
>> I've added Leonardo Kobus (maintainer of change-assembly-version-plugin) 
>> to Cc.
>>
>> воскресенье, 13 декабря 2015 г., 16:46:14 UTC+3 пользователь Sanketh P B 
>> написал:
>>>
>>> Dear Oleg Nenashev,
>>>
>>> This plugin offers support for frequently performed operations (change 
>>> in product version, file version and copyright info) on .Net, managed .Net 
>>> and C++ assembly information in a easy way. The other concentrates on .Net 
>>> only and for updating versions. Kindly suggest your thoughts, I feel this 
>>> could be separate plugins.
>>>
>>> Best Regards,
>>> Sanketh
>>>
>>> On Sunday, December 13, 2015 at 2:42:07 AM UTC+5:30, Oleg Nenashev wrote:

 Hi Sanketh,

 How the plugin differs from 
 https://github.com/jenkinsci/change-assembly-version-plugin ?
 From what I see it would be better to update that plugin instead of 
 creating the new one

 Best regards,
 Oleg Nenashev

 пятница, 11 декабря 2015 г., 18:29:12 UTC+3 пользователь Sanketh P B 
 написал:
>
> Dear All,
>
> Any updates here? Is this pending due to any changes required?
>
> Thanks,
> Sanketh
>
>

-- 
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/57fb76aa-0c69-4053-89ee-66642cc78ce5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin hosting request

[Daniel Beck]

Given that it's the end of the year I'd prefer to wait a bit longer to give 
Leonardo time to respond even if on vacation.

> On 23.12.2015, at 19:09, Sanketh P B  wrote:
> 
> Dear Team,
> 
> There is no update from the plugin developer/maintainer, please let me know 
> how to proceed here.
> 
> Thanks,
> Sanketh
> 
> On Tuesday, December 15, 2015 at 9:38:27 PM UTC+5:30, Sanketh P B wrote:
> Sure, I agree with you. We could enhance the existing plugin. 
> @Leonardo Kobus: Please provide your inputs on how to proceed.
> 
> Thanks,
> Sanketh
> 
> On Monday, December 14, 2015 at 1:32:22 PM UTC+5:30, Oleg Nenashev wrote:
> In general we try to avoid creation of new plugins wherever it is possible. 
> IMHO it makes sense to consider integrating the functionality into a single 
> plugin^ because they are very close. I agree that the existing plugin does 
> not cover all your case, but it could be solved by the plugin extension and 
> renaming.
> 
> I've added Leonardo Kobus (maintainer of change-assembly-version-plugin) to 
> Cc.
> 
> воскресенье, 13 декабря 2015 г., 16:46:14 UTC+3 пользователь Sanketh P B 
> написал:
> Dear Oleg Nenashev,
> 
> This plugin offers support for frequently performed operations (change in 
> product version, file version and copyright info) on .Net, managed .Net and 
> C++ assembly information in a easy way. The other concentrates on .Net only 
> and for updating versions. Kindly suggest your thoughts, I feel this could be 
> separate plugins.
> 
> Best Regards,
> Sanketh
> 
> On Sunday, December 13, 2015 at 2:42:07 AM UTC+5:30, Oleg Nenashev wrote:
> Hi Sanketh,
> 
> How the plugin differs from 
> https://github.com/jenkinsci/change-assembly-version-plugin ?
> From what I see it would be better to update that plugin instead of creating 
> the new one
> 
> Best regards,
> Oleg Nenashev
> 
> пятница, 11 декабря 2015 г., 18:29:12 UTC+3 пользователь Sanketh P B написал:
> Dear All,
> Any updates here? Is this pending due to any changes required?
> 
> Thanks,
> Sanketh
> 
> 
> 
> -- 
> 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/57fb76aa-0c69-4053-89ee-66642cc78ce5%40googlegroups.com.
> 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/1110C184-3AE6-4497-8C20-30CB5DB6003E%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: Docker Ephemeral Cloud

[Daniel Beck]

I'm not sure where this thread is now -- are you still asking for hosting of 
this plugin?

If so, could anyone speak up wrt whether there are legitimate reasons not to do 
this? So far the number of existing similar implementations has been mentioned 
-- how similar are they? Would an implementation switch like the Git Plugin has 
be a reasonable approach to support multiple APIs/libs?

> On 23.11.2015, at 17:56, kmbulebu  wrote:
> 
> The Docker landscape in Jenkins is kind of a mess, but I do feel this is a 
> good thing for an extensible open source project. The situation is 
> exaggerated here because there is so much interest and momentum in Docker. 
> We've discussed two Docker client libraries in this thread. There is a third, 
> used by Jenkins/Cloudbees, that relies on calling the docker client from the 
> command line. I know they're using it in the Docker Custom Build Environments 
> plugin, but I believe it's used in all of the new Docker plugins that were 
> released this year.
> 
> The approach calls the docker command line client and I think it is flawed 
> approach. I would much rather see the docker-commons plugin become a focal 
> point for a pure Java docker client, credentials management, and reusable 
> jelly components. I believe this has worked out well for launchers and other 
> 'common' plugins. Here's some of the issues I've encountered while working 
> with the plugins that rely on the docker cli:
>   • Requires an existing executor, on master or a slave, for use in 
> invoking the docker client. A pure docker build environment isn't possible.
>   • Docker clients are currently married by version to the server. 
> Connecting to a 1.7.1 server, requires a 1.7.1 client. This breaks down 
> quickly from a maintenance perspective.
>   • The REST apis are built with API stability and backwards 
> compatibility in mind, where as the cli makes no such guarantees. 
> If we want to address divergent strategies, I think we should start with the 
> above. 
> 
> 
> 
> 
> 
> 
> -- 
> 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/c77af750-7924-4a02-a6e6-07e2fb3343d7%40googlegroups.com.
> 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/D6DABFFA-D218-49C0-8D41-1275774A93A3%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin hosting request

[Sanketh P B]

Sure, I agree with you. We could enhance the existing plugin. 
@Leonardo Kobus: Please provide your inputs on how to proceed.

Thanks,
Sanketh

On Monday, December 14, 2015 at 1:32:22 PM UTC+5:30, Oleg Nenashev wrote:
>
> In general we try to avoid creation of new plugins wherever it is 
> possible. IMHO it makes sense to consider integrating the functionality 
> into a single plugin^ because they are very close. I agree that the 
> existing plugin does not cover all your case, but it could be solved by the 
> plugin extension and renaming.
>
> I've added Leonardo Kobus (maintainer of change-assembly-version-plugin) 
> to Cc.
>
> воскресенье, 13 декабря 2015 г., 16:46:14 UTC+3 пользователь Sanketh P B 
> написал:
>>
>> Dear Oleg Nenashev,
>>
>> This plugin offers support for frequently performed operations (change in 
>> product version, file version and copyright info) on .Net, managed .Net and 
>> C++ assembly information in a easy way. The other concentrates on .Net only 
>> and for updating versions. Kindly suggest your thoughts, I feel this could 
>> be separate plugins.
>>
>> Best Regards,
>> Sanketh
>>
>> On Sunday, December 13, 2015 at 2:42:07 AM UTC+5:30, Oleg Nenashev wrote:
>>>
>>> Hi Sanketh,
>>>
>>> How the plugin differs from 
>>> https://github.com/jenkinsci/change-assembly-version-plugin ?
>>> From what I see it would be better to update that plugin instead of 
>>> creating the new one
>>>
>>> Best regards,
>>> Oleg Nenashev
>>>
>>> пятница, 11 декабря 2015 г., 18:29:12 UTC+3 пользователь Sanketh P B 
>>> написал:

 Dear All,

 Any updates here? Is this pending due to any changes required?

 Thanks,
 Sanketh



-- 
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/67b4c403-e466-46d3-a279-282673a180c5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin hosting request

[Oleg Nenashev]

In general we try to avoid creation of new plugins wherever it is possible. 
IMHO it makes sense to consider integrating the functionality into a single 
plugin^ because they are very close. I agree that the existing plugin does 
not cover all your case, but it could be solved by the plugin extension and 
renaming.

I've added Leonardo Kobus (maintainer of change-assembly-version-plugin) to 
Cc.

воскресенье, 13 декабря 2015 г., 16:46:14 UTC+3 пользователь Sanketh P B 
написал:
>
> Dear Oleg Nenashev,
>
> This plugin offers support for frequently performed operations (change in 
> product version, file version and copyright info) on .Net, managed .Net and 
> C++ assembly information in a easy way. The other concentrates on .Net only 
> and for updating versions. Kindly suggest your thoughts, I feel this could 
> be separate plugins.
>
> Best Regards,
> Sanketh
>
> On Sunday, December 13, 2015 at 2:42:07 AM UTC+5:30, Oleg Nenashev wrote:
>>
>> Hi Sanketh,
>>
>> How the plugin differs from 
>> https://github.com/jenkinsci/change-assembly-version-plugin ?
>> From what I see it would be better to update that plugin instead of 
>> creating the new one
>>
>> Best regards,
>> Oleg Nenashev
>>
>> пятница, 11 декабря 2015 г., 18:29:12 UTC+3 пользователь Sanketh P B 
>> написал:
>>>
>>> Dear All,
>>>
>>> Any updates here? Is this pending due to any changes required?
>>>
>>> Thanks,
>>> Sanketh
>>>
>>>

-- 
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/75297327-8289-4109-9e01-99ca0b35a1cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin hosting request

[Sanketh P B]

Dear Oleg Nenashev,

This plugin offers support for frequently performed operations (change in 
product version, file version and copyright info) on .Net, managed .Net and 
C++ assembly information in a easy way. The other concentrates on .Net only 
and for updating versions. Kindly suggest your thoughts, I feel this could 
be separate plugins.

Best Regards,
Sanketh

On Sunday, December 13, 2015 at 2:42:07 AM UTC+5:30, Oleg Nenashev wrote:
>
> Hi Sanketh,
>
> How the plugin differs from 
> https://github.com/jenkinsci/change-assembly-version-plugin ?
> From what I see it would be better to update that plugin instead of 
> creating the new one
>
> Best regards,
> Oleg Nenashev
>
> пятница, 11 декабря 2015 г., 18:29:12 UTC+3 пользователь Sanketh P B 
> написал:
>>
>> Dear All,
>>
>> Any updates here? Is this pending due to any changes required?
>>
>> Thanks,
>> Sanketh
>>
>>

-- 
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/485090a8-a422-4cd3-8d43-3d9e29e81259%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin hosting request

[Oleg Nenashev]

Hi Sanketh,

How the plugin differs from 
https://github.com/jenkinsci/change-assembly-version-plugin ?
>From what I see it would be better to update that plugin instead of 
creating the new one

Best regards,
Oleg Nenashev

пятница, 11 декабря 2015 г., 18:29:12 UTC+3 пользователь Sanketh P B 
написал:
>
> Dear All,
>
> Any updates here? Is this pending due to any changes required?
>
> Thanks,
> Sanketh
>
>

-- 
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/a1a83808-22f5-49cb-ba84-1efdd407f62f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin hosting request

[Slide]

You posted on a weekend, so please be patient.

On Mon, Dec 7, 2015 at 1:04 AM Sanketh P B  wrote:

> Dear All,
>
> Any updates here?
>
> Thanks,
> Sanketh
>
> --
> 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/711ae2b1-05cb-44ef-a023-06b5c895652f%40googlegroups.com
> .
> 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/CAPiUgVesQ4yimHWwLZYXY%3Doj%2Bxgz9kM2FwP5xZVNs%2B%2Bb%2BrJcqA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: Docker Ephemeral Cloud

[kmbulebu]

The Docker landscape in Jenkins is kind of a mess, but I do feel this is a 
good thing for an extensible open source project. The situation is 
exaggerated here because there is so much interest and momentum in Docker. 
We've discussed two Docker client libraries in this thread. There is a 
third, used by Jenkins/Cloudbees, that relies on calling the docker client 
from the command line. I know they're using it in the Docker Custom Build 
Environments plugin, but I believe it's used in all of the new Docker 
plugins that were released this year.

The approach calls the docker command line client and I think it is flawed 
approach. I would much rather see the docker-commons plugin become a focal 
point for a pure Java docker client, credentials management, and reusable 
jelly components. I believe this has worked out well for launchers and 
other 'common' plugins. Here's some of the issues I've encountered while 
working with the plugins that rely on the docker cli:

   1. Requires an existing executor, on master or a slave, for use in 
   invoking the docker client. A pure docker build environment isn't possible.
   2. Docker clients are currently married by version to the server. 
   Connecting to a 1.7.1 server, requires a 1.7.1 client. This breaks down 
   quickly from a maintenance perspective.
   3. The REST apis are built with API stability and backwards 
   compatibility in mind, where as the cli makes no such guarantees. 

If we want to address divergent strategies, I think we should start with 
the above. 





-- 
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/c77af750-7924-4a02-a6e6-07e2fb3343d7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: Docker Ephemeral Cloud

['Jesse Glick' via Jenkins Developers]

On Mon, Nov 23, 2015 at 11:56 AM, kmbulebu  wrote:
> 'Here's some of the issues I've encountered while working
> with the plugins that rely on the docker cli:

All valid points (with some workarounds), but the flip side is that
when calling a CLI you can reproduce the exact command Jenkins was
running and try it yourself from a shell if anything goes wrong. Also
I am not sure where the Docker landscape is in this regard, but our
experience with SCM plugins using native Java clients has been that
performance is often poor and there are endless subtle behavioral
differences from the “golden standard” CLI. Users are rightly
frustrated when something that works fine from a shell fails with a
mysterious error in Jenkins.

-- 
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/CANfRfr2g2YX5aPhahKerxfKb%2BFT77b2TECM_VqVNbT-g1ME9XA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: Docker Ephemeral Cloud

[David Karlsen]

This is the problem about jenkins - 1000 half backed plugins.
Would be better with 100 well curated :)
That's where I'd be willing to pay for support.

2015-11-18 16:48 GMT+01:00 Kirill Merkushev :
> Think plugins can be merged without any problem with saving of current
> functionality for both. (With shading of both libs).
> One will use one type of cloud, another - own type of cloud. They can be
> located in separate packages and don't mix in different cases.
>
> (But please use org.jenkinsci.plugins.* prefix for new packages)
>
>
> суббота, 14 ноября 2015 г., 6:07:15 UTC+3 пользователь kmbulebu написал:
>>
>> Hi,
>>
>> I'd like to introduce a new plugin for hosting on jenkins-ci.org, the
>> docker ephemeral cloud plugin.
>>
>> Github Home: https://github.com/kmbulebu/docker-ephemeral-cloud
>> Github and Jenkins username: kmbulebu
>> Name: docker-ephemeral-cloud-plugin
>>
>> Description:
>>
>> The Docker Ephemeral Cloud plugin provides an elastic pool of slaves,
>> using Docker containers, that live only as long as the job. When a job is
>> scheduled, Jenkins checks for Docker image configurations that match the
>> labels of the job. When one is found, Docker is invoked via REST APIs to
>> pull the image and run the container. Within the container, the Jenkins JNLP
>> slave jar is downloaded and run. Communication is established to the Jenkins
>> master and the new slave node performs the requested job. When complete, the
>> container is stopped and removed.
>>
>> The key differentiators here are that this plugin enables stateless slaves
>> on containers, without the need for any port mappings, SSH servers, docker
>> clients, or existing slaves. The focus is on stateless jobs and builds and
>> not continuous deployment via containers.
>>
>> More on how this plugin differs from similar Docker plugins:
>> https://github.com/kmbulebu/docker-ephemeral-cloud#comparative-to-other-docker-plugins
>>
>> Thanks,
>>
>> Kevin
>>
>>
> --
> 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/33893b7f-b1bb-49d5-9276-70bd3b787a46%40googlegroups.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen

-- 
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/CAGO7Ob31%3D7ZKR4cPON-2PEsxCCL-sNObfzjjP%2BqPdHHG_b%2Bijg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: Docker Ephemeral Cloud

[Kanstantsin Shautsou]

> 
> On Nov 18, 2015, at 17:32, domi  wrote:
> 
> To be honest, the whole list of jenkins docker plugins feels like a zoo and 
> there is no way a normal user can keep up and make the right choice.
Technically it’s a question to plugin manager and providing ratings & 
statistics. That afair will be enhanced soon.
> I think this work should be coordinated better and an uptodate comparison 
> should be kept at a central place.
> ..my 2cents
@Domi, i thought the same and even tried to go through processes, but they are 
ends into project organisation (or miss organisation).
What should i do if plugin author don’t want to use PRs or static analysing 
tools? Right, leave into fork. 

What should you do if, for example, you make business around docker and jenkins 
and enough power to support yourself this code? You will of course make your 
own company internally decided plugins hierarchy. And project organisation of 
course allows you to make your development under jenkinsci hosting. That what i 
understand too late after personal talk with Kohsuke - his project is “bazaar”. 
You solve your cases and share sources and it’s usage. If you disagree you can 
do your plugin :). 

> /Domi
> 
> 
>> On 18 Nov 2015, at 15:26, Kanstantsin Shautsou > > wrote:
>> 
>> 
>> 
>> On Tuesday, November 17, 2015 at 7:28:00 PM UTC+3, Jesse Glick wrote:
>> On Mon, Nov 16, 2015 at 10:02 PM, kmbulebu > wrote: 
>> > I believe the real horse race is between the 
>> > underlying docker libraries. In the end, we'll likely have a clear winner, 
>> > and can standardize a group of plugins around that. Perhaps docker-commons 
>> > becomes that focal point, and we have smaller plugins that deliver slaves, 
>> > build steps, workflow DSL, etc. 
>> 
>> Seems reasonable to me to have smaller plugins with focused features, 
>> and a little competition. I would not object to hosting as is, 
>> provided that plugin wikis clearly link to alternatives. 
>> 
>> IIUC the main differences between your plugin and the `Cloud` portion 
>> of the `docker` plugin are 
>> 
>> · Different client libraries. No clear winner yet. 
>> I created small thread between docker-java and docker-client to unify 
>> efforts, but obviously it will be long time action and probably will have no 
>> results. Both libraries missing different things, but technically 
>> docker-client doesn't support callbacks for long running commands. 
>> 
>> · Slave launcher: yours uses JNLP; `docker` plugin currently ships 
>> SSH, has JNLP support in code but disabled. 
>> It was disabled because of lack of integration tests, ssh launching 
>> stabilisation was very hard and i didn't want to have broken instances with 
>> one more untested launcher. Those PR that tried enable JNLP was not exactly 
>> how it was planned to work from design view point.
>> 
>> If you can later reach consensus with the `docker` plugin devs on the 
>> approach to take for a general-purpose Docker cloud provider, it 
>> should be possible to unify code into a new plugin release. Automatic 
>> migration of user settings will be a bit trickier but is possible. 
>> As soon as @magnayn likes "master development" without test cases he will of 
>> course merge any changes. So you are free to submit any PRs to docker-plugin 
>> now.  
>> 
>> By the way your comparison chart neglected to mention 
>> 
>> https://github.com/ndeloof/docker-slaves-plugin 
>>  
>> 
>> which is a novel approach that I think is very promising. 
>> Very promising thing will be finally implement normal Cloud API in core (or 
>> in plugin but provide normal extension points) because docker is not only 
>> the single cloud provider.
>> 
>> PS i'm co-maintainer of docker-java atm and working on one more docker cloud 
>> plugin for jenkins which from my viewpoint will have the best implementation 
>> of currently possible state. 
>> TLS support in docker-plugin is also possible (or even already works) 
>> because docker-java resolves system variables for connection builder (though 
>> there is no right implementation for this field).
>> PPS From tech viewpoint i see that "ephemeral cloud" has queue lock issues 
>> and shading. But if this plugin solves user issue, then it should be hosted 
>> and allow people experiment on it.
>> 
>> 
>> 
>> -- 
>> 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/d10a18f3-1c8c-4398-aecb-b9e474818ff4%40googlegroups.com
>>  
>> 

Re: New Plugin hosting request: Docker Ephemeral Cloud

[Nigel Magnay]

>
>
> To be honest, the whole list of jenkins docker plugins feels like a zoo
> and there is no way a normal user can keep up and make the right choice.
> I think this work should be coordinated better and an uptodate comparison
> should be kept at a central place.
> ..my 2cents
> /Domi
>
>
I think some duplication occurs accidentally (e.g: closed-source plugin
becomes open), some that is scope-creep (we started here and wanted this
feature too - I didn't know plugin  already also did that), and some
that is 'I just want to play with a different library / technique /
sandpit'.

​Other duplication though is for less healthy reasons. Needing to do TLS
and JNLP rose to the top of my stack last week, and I was pleasantly
surprised that most of the initial work had already been done for the
latter. I was rather less pleasantly surprised that - though there were
bugs and someone had submitted a PR
 that effectively made
the feature work (​maybe not in all eventualities, but sufficient for many
cases) over 2 months ago, but had effectively been told to 'go away'. To
me, that's not the right approach for a whole host of reasons - the
pertinent one being that it drives a 'not invented here' culture that leads
to duplication because dealing with the gatekeeper becomes too painful.

It could well be that some plugins could be folded together.

-- 
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/CAPYP83SZYeCs19OQchpFzpvv%3DTR3kJa7p-kL27P_9ek5975VvA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: Docker Ephemeral Cloud

[Kanstantsin Shautsou]

> On Nov 18, 2015, at 18:25, Nigel Magnay  wrote:
> 
> 
> To be honest, the whole list of jenkins docker plugins feels like a zoo and 
> there is no way a normal user can keep up and make the right choice.
> I think this work should be coordinated better and an uptodate comparison 
> should be kept at a central place.
> ..my 2cents
> /Domi
> 
> 
> I think some duplication occurs accidentally (e.g: closed-source plugin 
> becomes open), some that is scope-creep (we started here and wanted this 
> feature too - I didn't know plugin  already also did that), and some 
> that is 'I just want to play with a different library / technique / sandpit'.
> 
> ​Other duplication though is for less healthy reasons. Needing to do TLS and 
> JNLP rose to the top of my stack last week, and I was pleasantly surprised 
> that most of the initial work had already been done for the latter. I was 
> rather less pleasantly surprised that - though there were bugs and someone 
> had submitted a PR  that 
> effectively made the feature work (​maybe not in all eventualities, but 
> sufficient for many cases) over 2 months ago, but had effectively been told 
> to 'go away’.
It wasn’t “go away”, it was “it needs changes” instead “it my rapid hack (or 
checkbox) for my case”. This was affected in open for everybody 
https://github.com/jenkinsci/docker-plugin/issues/235 
 roadmap. Everybody can 
join and help with development, but people do only small hacky PRs and nobody 
wants spend their time on real development. Docker allows flexibility and any 
change without integration tests ends in broken places. As soon as SSH was 
stabilised (with enough blood) i started working on ITs and delayed untested 
JNLP launcher (that btw may work in 3 different ways). Saying that it “shame” 
is harmful. Like ephemeral plugin it just single user case that will be hardly 
changeable after releasing in bad state. 
I made the most hard work and now you can:
 - continue and create ITs with releasing tested and stable features
 - pick untested (implemented) work and release as is, then deal (or not deal) 
with tones of bugs.

ITs in general is not well powered in Jenkins in comparison to maven-its, so i 
end with digging into ATH spaghetti and making own simple ITs. You can find my 
parallel emails about tests implementation.

> To me, that's not the right approach for a whole host of reasons - the 
> pertinent one being that it drives a 'not invented here' culture that leads 
> to duplication because dealing with the gatekeeper becomes too painful.
> 
> It could well be that some plugins could be folded together.
> 
> 
> 
> 
> 
>  
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-dev/S06tNF53NxA/unsubscribe 
> .
> To unsubscribe from this group and all its topics, 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/CAPYP83SZYeCs19OQchpFzpvv%3DTR3kJa7p-kL27P_9ek5975VvA%40mail.gmail.com
>  
> .
> 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/21D29E6A-8B72-4B7B-83C7-69D4C234C12B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: Docker Ephemeral Cloud

[Kirill Merkushev]

Think plugins can be merged without any problem with saving of current 
functionality for both. (With shading of both libs).
One will use one type of cloud, another - own type of cloud. They can be 
located in separate packages and don't mix in different cases.

(But please use org.jenkinsci.plugins.* prefix for new packages)


суббота, 14 ноября 2015 г., 6:07:15 UTC+3 пользователь kmbulebu написал:
>
> Hi,
>
> I'd like to introduce a new plugin for hosting on jenkins-ci.org, the 
> docker ephemeral cloud plugin. 
>
> Github Home: https://github.com/kmbulebu/docker-ephemeral-cloud
> Github and Jenkins username: kmbulebu
> Name: docker-ephemeral-cloud-plugin 
>
> Description: 
>
> The Docker Ephemeral Cloud plugin provides an elastic pool of slaves, 
> using Docker containers, that live only as long as the job. When a job is 
> scheduled, Jenkins checks for Docker image configurations that match the 
> labels of the job. When one is found, Docker is invoked via REST APIs to 
> pull the image and run the container. Within the container, the Jenkins 
> JNLP slave jar is downloaded and run. Communication is established to the 
> Jenkins master and the new slave node performs the requested job. When 
> complete, the container is stopped and removed.
>
> The key differentiators here are that this plugin enables stateless slaves 
> on containers, without the need for any port mappings, SSH servers, docker 
> clients, or existing slaves. The focus is on stateless jobs and builds and 
> not continuous deployment via containers. 
>
> More on how this plugin differs from similar Docker plugins: 
> https://github.com/kmbulebu/docker-ephemeral-cloud#comparative-to-other-docker-plugins
>
> Thanks,
>
> Kevin
>
>
>

-- 
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/33893b7f-b1bb-49d5-9276-70bd3b787a46%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: Docker Ephemeral Cloud

[Kanstantsin Shautsou]

On Tuesday, November 17, 2015 at 7:28:00 PM UTC+3, Jesse Glick wrote:
>
> On Mon, Nov 16, 2015 at 10:02 PM, kmbulebu  > wrote: 
> > I believe the real horse race is between the 
> > underlying docker libraries. In the end, we'll likely have a clear 
> winner, 
> > and can standardize a group of plugins around that. Perhaps 
> docker-commons 
> > becomes that focal point, and we have smaller plugins that deliver 
> slaves, 
> > build steps, workflow DSL, etc. 
>
> Seems reasonable to me to have smaller plugins with focused features, 
> and a little competition. I would not object to hosting as is, 
> provided that plugin wikis clearly link to alternatives. 
>
> IIUC the main differences between your plugin and the `Cloud` portion 
> of the `docker` plugin are 
>
> · Different client libraries. No clear winner yet. 
>
I created small thread between docker-java and docker-client to unify 
efforts, but obviously it will be long time action and probably will have 
no results. Both libraries missing different things, but technically 
docker-client doesn't support callbacks for long running commands. 

· Slave launcher: yours uses JNLP; `docker` plugin currently ships 
> SSH, has JNLP support in code but disabled. 
>
It was disabled because of lack of integration tests, ssh launching 
stabilisation was very hard and i didn't want to have broken instances with 
one more untested launcher. Those PR that tried enable JNLP was not exactly 
how it was planned to work from design view point.

>
> If you can later reach consensus with the `docker` plugin devs on the 
> approach to take for a general-purpose Docker cloud provider, it 
> should be possible to unify code into a new plugin release. Automatic 
> migration of user settings will be a bit trickier but is possible. 
>
As soon as @magnayn likes "master development" without test cases he will 
of course merge any changes. So you are free to submit any PRs to 
docker-plugin now.  

>
> By the way your comparison chart neglected to mention 
>
> https://github.com/ndeloof/docker-slaves-plugin 
>
> which is a novel approach that I think is very promising. 
>
Very promising thing will be finally implement normal Cloud API in core (or 
in plugin but provide normal extension points) because docker is not only 
the single cloud provider.

PS i'm co-maintainer of docker-java atm and working on one more docker 
cloud plugin for jenkins which from my viewpoint will have the best 
implementation of currently possible state. 
TLS support in docker-plugin is also possible (or even already works) 
because docker-java resolves system variables for connection builder 
(though there is no right implementation for this field).
PPS From tech viewpoint i see that "ephemeral cloud" has queue lock issues 
and shading. But if this plugin solves user issue, then it should be hosted 
and allow people experiment on it.


-- 
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/d10a18f3-1c8c-4398-aecb-b9e474818ff4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: Docker Ephemeral Cloud

[domi]

To be honest, the whole list of jenkins docker plugins feels like a zoo and 
there is no way a normal user can keep up and make the right choice.
I think this work should be coordinated better and an uptodate comparison 
should be kept at a central place.
..my 2cents
/Domi


> On 18 Nov 2015, at 15:26, Kanstantsin Shautsou  
> wrote:
> 
> 
> 
> On Tuesday, November 17, 2015 at 7:28:00 PM UTC+3, Jesse Glick wrote:
> On Mon, Nov 16, 2015 at 10:02 PM, kmbulebu  
> wrote: 
> > I believe the real horse race is between the 
> > underlying docker libraries. In the end, we'll likely have a clear winner, 
> > and can standardize a group of plugins around that. Perhaps docker-commons 
> > becomes that focal point, and we have smaller plugins that deliver slaves, 
> > build steps, workflow DSL, etc. 
> 
> Seems reasonable to me to have smaller plugins with focused features, 
> and a little competition. I would not object to hosting as is, 
> provided that plugin wikis clearly link to alternatives. 
> 
> IIUC the main differences between your plugin and the `Cloud` portion 
> of the `docker` plugin are 
> 
> · Different client libraries. No clear winner yet. 
> I created small thread between docker-java and docker-client to unify 
> efforts, but obviously it will be long time action and probably will have no 
> results. Both libraries missing different things, but technically 
> docker-client doesn't support callbacks for long running commands. 
> 
> · Slave launcher: yours uses JNLP; `docker` plugin currently ships 
> SSH, has JNLP support in code but disabled. 
> It was disabled because of lack of integration tests, ssh launching 
> stabilisation was very hard and i didn't want to have broken instances with 
> one more untested launcher. Those PR that tried enable JNLP was not exactly 
> how it was planned to work from design view point.
> 
> If you can later reach consensus with the `docker` plugin devs on the 
> approach to take for a general-purpose Docker cloud provider, it 
> should be possible to unify code into a new plugin release. Automatic 
> migration of user settings will be a bit trickier but is possible. 
> As soon as @magnayn likes "master development" without test cases he will of 
> course merge any changes. So you are free to submit any PRs to docker-plugin 
> now.  
> 
> By the way your comparison chart neglected to mention 
> 
> https://github.com/ndeloof/docker-slaves-plugin 
>  
> 
> which is a novel approach that I think is very promising. 
> Very promising thing will be finally implement normal Cloud API in core (or 
> in plugin but provide normal extension points) because docker is not only the 
> single cloud provider.
> 
> PS i'm co-maintainer of docker-java atm and working on one more docker cloud 
> plugin for jenkins which from my viewpoint will have the best implementation 
> of currently possible state. 
> TLS support in docker-plugin is also possible (or even already works) because 
> docker-java resolves system variables for connection builder (though there is 
> no right implementation for this field).
> PPS From tech viewpoint i see that "ephemeral cloud" has queue lock issues 
> and shading. But if this plugin solves user issue, then it should be hosted 
> and allow people experiment on it.
> 
> 
> 
> -- 
> 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/d10a18f3-1c8c-4398-aecb-b9e474818ff4%40googlegroups.com
>  
> .
> 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/127A6A84-F1F2-42C6-9195-922972EA3D68%40fortysix.ch.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: Docker Ephemeral Cloud

['Jesse Glick' via Jenkins Developers]

On Mon, Nov 16, 2015 at 10:02 PM, kmbulebu  wrote:
> I believe the real horse race is between the
> underlying docker libraries. In the end, we'll likely have a clear winner,
> and can standardize a group of plugins around that. Perhaps docker-commons
> becomes that focal point, and we have smaller plugins that deliver slaves,
> build steps, workflow DSL, etc.

Seems reasonable to me to have smaller plugins with focused features,
and a little competition. I would not object to hosting as is,
provided that plugin wikis clearly link to alternatives.

IIUC the main differences between your plugin and the `Cloud` portion
of the `docker` plugin are

· Different client libraries. No clear winner yet.
· Slave launcher: yours uses JNLP; `docker` plugin currently ships
SSH, has JNLP support in code but disabled.

If you can later reach consensus with the `docker` plugin devs on the
approach to take for a general-purpose Docker cloud provider, it
should be possible to unify code into a new plugin release. Automatic
migration of user settings will be a bit trickier but is possible.

By the way your comparison chart neglected to mention

https://github.com/ndeloof/docker-slaves-plugin

which is a novel approach that I think is very promising.

-- 
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/CANfRfr1hTuSsTQ8RWL%3DdqSZLDH_JRZ6jPpMBQ51o2Hrv%2BKCNUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: Docker Ephemeral Cloud

[Nigel Magnay]

FWIW, I have pushed changes for both TLS and JNLP in docker-plugin, so the
comparison can now be reduced to

Docker Plugin 


   - Provides additional capabilities beyond slaves, such as Docker build
  steps.







On Tue, Nov 17, 2015 at 4:27 PM, 'Jesse Glick' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> On Mon, Nov 16, 2015 at 10:02 PM, kmbulebu  wrote:
> > I believe the real horse race is between the
> > underlying docker libraries. In the end, we'll likely have a clear
> winner,
> > and can standardize a group of plugins around that. Perhaps
> docker-commons
> > becomes that focal point, and we have smaller plugins that deliver
> slaves,
> > build steps, workflow DSL, etc.
>
> Seems reasonable to me to have smaller plugins with focused features,
> and a little competition. I would not object to hosting as is,
> provided that plugin wikis clearly link to alternatives.
>
> IIUC the main differences between your plugin and the `Cloud` portion
> of the `docker` plugin are
>
> · Different client libraries. No clear winner yet.
> · Slave launcher: yours uses JNLP; `docker` plugin currently ships
> SSH, has JNLP support in code but disabled.
>
> If you can later reach consensus with the `docker` plugin devs on the
> approach to take for a general-purpose Docker cloud provider, it
> should be possible to unify code into a new plugin release. Automatic
> migration of user settings will be a bit trickier but is possible.
>
> By the way your comparison chart neglected to mention
>
> https://github.com/ndeloof/docker-slaves-plugin
>
> which is a novel approach that I think is very promising.
>
> --
> 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/CANfRfr1hTuSsTQ8RWL%3DdqSZLDH_JRZ6jPpMBQ51o2Hrv%2BKCNUA%40mail.gmail.com
> .
> 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/CAPYP83QwyEVY2kVw9_F6D9hz%2Ba_QVGoHZ5wk69%3Dc%3DFxXq-hBCA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: Docker Ephemeral Cloud

[R. Tyler Croy]

(replies inline)

On Fri, 13 Nov 2015, kmbulebu wrote:

> I'd like to introduce a new plugin for hosting on jenkins-ci.org, the 
> docker ephemeral cloud plugin. 
> 
> Github Home: https://github.com/kmbulebu/docker-ephemeral-cloud
> Github and Jenkins username: kmbulebu
> Name: docker-ephemeral-cloud-plugin 
> 
> Description: 
> 
> The Docker Ephemeral Cloud plugin provides an elastic pool of slaves, using 
> Docker containers, that live only as long as the job. When a job is 
> scheduled, Jenkins checks for Docker image configurations that match the 
> labels of the job. When one is found, Docker is invoked via REST APIs to 
> pull the image and run the container. Within the container, the Jenkins 
> JNLP slave jar is downloaded and run. Communication is established to the 
> Jenkins master and the new slave node performs the requested job. When 
> complete, the container is stopped and removed.
> 
> The key differentiators here are that this plugin enables stateless slaves 
> on containers, without the need for any port mappings, SSH servers, docker 
> clients, or existing slaves. The focus is on stateless jobs and builds and 
> not continuous deployment via containers. 
> 
> More on how this plugin differs from similar Docker 
> plugins: 
> https://github.com/kmbulebu/docker-ephemeral-cloud#comparative-to-other-docker-plugins



The differences between this plugin and the Docker plugin don't seem very
major to me, is there an objection you would have to merging this with the
Docker plugin? That plugin already has many thousands of installations and the
TLS support in particular I think would be useful as well.

Have you also seen the Docker build step plugin, I believe that might overlap
with your work as well, and already has a few thousand installations.


There's some really good work here and by merging efforts with the existing
Jenkins/Docker plugins I think we can improve the usage for many existing users
and help attract new ones.



Let me know what you think, if you're open to it I'm happy to help where I can.


If you're not keen on merging, then I suppose I'll make a frowney face and
setup the hosting, etc.



Cheers
- R. Tyler Croy

--
 Code: 
  Chatter: 

  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
--

-- 
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/20151116153241.GV23766%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: New Plugin hosting request: Docker Ephemeral Cloud

[kmbulebu]

Thanks for your kind words :). 

I understand. At a high level, they both aim to deliver slaves using 
Docker. This is an old problem; do you break away and create new, or revise 
in place? I think we should move forward with the new one, and let it work 
itself out. I'm not opposed to merging, but I don't want to delay 
delivering immediate value to users. I created the plugin out of urgency (I 
couldn't get the firewall rules for 100+ SSH ports approved in my 
organization) and I feel others have similar needs. Before looking at 
merging the two, I would like to gain some more learning through user 
experience.

I recall we once had two Gerrit plugins, but have since seen the two 
combine into one excellent plugin. I believe the real horse race is between 
the underlying docker libraries. In the end, we'll likely have a clear 
winner, and can standardize a group of plugins around that. Perhaps 
docker-commons becomes that focal point, and we have smaller plugins that 
deliver slaves, build steps, workflow DSL, etc. For now, I think it's too 
early to settle. 

I don't want you to frown, but can we go ahead and move forward with this 
as-is?

Thanks,

Kevin



On Monday, November 16, 2015 at 10:34:07 AM UTC-5, R Tyler Croy wrote:
>
> (replies inline) 
>
> On Fri, 13 Nov 2015, kmbulebu wrote: 
>
> > I'd like to introduce a new plugin for hosting on jenkins-ci.org, the 
> > docker ephemeral cloud plugin. 
> > 
> > Github Home: https://github.com/kmbulebu/docker-ephemeral-cloud 
> > Github and Jenkins username: kmbulebu 
> > Name: docker-ephemeral-cloud-plugin 
> > 
> > Description: 
> > 
> > The Docker Ephemeral Cloud plugin provides an elastic pool of slaves, 
> using 
> > Docker containers, that live only as long as the job. When a job is 
> > scheduled, Jenkins checks for Docker image configurations that match the 
> > labels of the job. When one is found, Docker is invoked via REST APIs to 
> > pull the image and run the container. Within the container, the Jenkins 
> > JNLP slave jar is downloaded and run. Communication is established to 
> the 
> > Jenkins master and the new slave node performs the requested job. When 
> > complete, the container is stopped and removed. 
> > 
> > The key differentiators here are that this plugin enables stateless 
> slaves 
> > on containers, without the need for any port mappings, SSH servers, 
> docker 
> > clients, or existing slaves. The focus is on stateless jobs and builds 
> and 
> > not continuous deployment via containers. 
> > 
> > More on how this plugin differs from similar Docker 
> > plugins: 
> https://github.com/kmbulebu/docker-ephemeral-cloud#comparative-to-other-docker-plugins
>  
>
>
>
> The differences between this plugin and the Docker plugin don't seem very 
> major to me, is there an objection you would have to merging this with the 
> Docker plugin? That plugin already has many thousands of installations and 
> the 
> TLS support in particular I think would be useful as well. 
>
> Have you also seen the Docker build step plugin, I believe that might 
> overlap 
> with your work as well, and already has a few thousand installations. 
>
>
> There's some really good work here and by merging efforts with the 
> existing 
> Jenkins/Docker plugins I think we can improve the usage for many existing 
> users 
> and help attract new ones. 
>
>
>
> Let me know what you think, if you're open to it I'm happy to help where I 
> can. 
>
>
> If you're not keen on merging, then I suppose I'll make a frowney face and 
> setup the hosting, etc. 
>
>
>
> Cheers 
> - R. Tyler Croy 
>
> -- 
>  Code:  
>   Chatter:  
>
>   % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F 
> -- 
>

-- 
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/c9ba5f44-73db-41ed-b6de-1f7719d01ab6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: AWS Lambda Jenkins plugin

[nicolas de loof]

https://github.com/jenkinsci/aws-lambda-plugin

2015-03-18 18:16 GMT+01:00 Kanstantsin Shautsou kanstantsin@gmail.com:

 I don't remember on what wiki page it was, but afair using word 'jenkins'
 for jenkins plugins is not good.
 Please wait while somebody process your request.

 On Wednesday, March 11, 2015 at 7:16:13 PM UTC+3, Michael Willemse wrote:

 Do you have any updates relating this plugin? Anything that can be
 improved.

  --
 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/5fc03eff-7569-4eda-91d8-ea8f234c462e%40googlegroups.com
 https://groups.google.com/d/msgid/jenkinsci-dev/5fc03eff-7569-4eda-91d8-ea8f234c462e%40googlegroups.com?utm_medium=emailutm_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/CANMVJz%3Dv4hA7QUQGeScQtB94Hh6snMXymBib4HhUboSyg4Jazg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: AWS Lambda Jenkins plugin

[Daniel Beck]

And the artifactId should probably be changed to aws-lambda before the first 
release.

On 18.03.2015, at 18:19, nicolas de loof nicolas.del...@gmail.com wrote:

 https://github.com/jenkinsci/aws-lambda-plugin
 
 2015-03-18 18:16 GMT+01:00 Kanstantsin Shautsou kanstantsin@gmail.com:
 I don't remember on what wiki page it was, but afair using word 'jenkins' for 
 jenkins plugins is not good.
 Please wait while somebody process your request.
 
 On Wednesday, March 11, 2015 at 7:16:13 PM UTC+3, Michael Willemse wrote:
 Do you have any updates relating this plugin? Anything that can be improved.
 
 -- 
 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/5fc03eff-7569-4eda-91d8-ea8f234c462e%40googlegroups.com.
 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/CANMVJz%3Dv4hA7QUQGeScQtB94Hh6snMXymBib4HhUboSyg4Jazg%40mail.gmail.com.
 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/C45B7604-86C3-439B-8AB8-B7873B26F29A%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin hosting request: AWS Lambda Jenkins plugin

[Michael Willemse]

Do you have any updates relating this plugin? Anything that can be improved.

-- 
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/0f4fb7f3-60c7-4382-946e-567dde45d031%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: new plugin hosting request

[Christopher Orr]

Hi Matt,

Sorry to hijack this thread, but would you mind taking a look at the 
Google OAuth plugin issues when you get some time?


https://github.com/jenkinsci/google-oauth-plugin/issues/2

Thanks,
Chris


On 09/09/14 17:41, 'Matthew Moore' via Jenkins Developers wrote:

I have posted a new plugin here:
https://github.com/mattmoor/yaml-project-plugin

and added its associated wiki page here:
https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin

FWIW, this is the basis of the talk I plan to give at JUC 2014 this Fall.


thanks,
-M


--
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.
For more options, visit https://groups.google.com/d/optout.

Re: new plugin hosting request

['Bruno P. Kinoshita' via Jenkins Developers]

Hey Matthew, 

I'm working with a team using Ansible YAML playbooks, so probably using similar 
syntax for creating Jenkins projects would be a good idea. 

Are you going to host the plug-in under jenkinsci org at GitHub? 

Thanks!
Bruno



 From: 'Matthew Moore' via Jenkins Developers jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Tuesday, September 9, 2014 12:41 PM
Subject: new plugin hosting request
 


I have posted a new plugin here:

  https://github.com/mattmoor/yaml-project-plugin



and added its associated wiki page here:
  https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin


FWIW, this is the basis of the talk I plan to give at JUC 2014 this Fall.





thanks,
-M



-- 

Matthew Moore
DI/Docker (aka Convoy)
Developer Infrastructure @ Google

-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: new plugin hosting request

['Matthew Moore' via Jenkins Developers]

To be clear: I am not defining any YAML syntax.

The syntax for the YAML this parses is entirely defined by Jenkins'
Structured Form Submissions.

This is entirely by design, since it means that basically any plugin that
Jenkins can create through the UI, this plugin *should* be able to create
from YAML.

Better still, the YAML asks users to specify precisely what the UI does :)



*Are you going to host the plug-in under jenkinsci org at GitHub?*

Yes, that is essentially what this thread is about.


Happy to chat more, especially if any of the above isn't clear.
-M



On Tue, Sep 9, 2014 at 8:55 AM, 'Bruno P. Kinoshita' via Jenkins Developers
jenkinsci-dev@googlegroups.com wrote:


 Hey Matthew,

 I'm working with a team using Ansible YAML playbooks, so probably using
 similar syntax for creating Jenkins projects would be a good idea.

 Are you going to host the plug-in under jenkinsci org at GitHub?

 Thanks!
 Bruno

   --
  *From:* 'Matthew Moore' via Jenkins Developers 
 jenkinsci-dev@googlegroups.com
 *To:* jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com
 *Sent:* Tuesday, September 9, 2014 12:41 PM
 *Subject:* new plugin hosting request

 I have posted a new plugin here:
   https://github.com/mattmoor/yaml-project-plugin

 and added its associated wiki page here:
   https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin

 FWIW, this is the basis of the talk I plan to give at JUC 2014 this Fall.


 thanks,
 -M


 --
 Matthew Moore
 DI/Docker (aka Convoy)
 Developer Infrastructure @ Google
  --
 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.
 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.
 For more options, visit https://groups.google.com/d/optout.




-- 
Matthew Moore
DI/Docker (aka Convoy)
Developer Infrastructure @ Google

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: new plugin hosting request

['Bruno P. Kinoshita' via Jenkins Developers]

Oh got it, then you simply convert the YAML file back to JSON. 

If there's no objection, I'll fork this repository under jenkinsci using the 
IRC bot in the next hour. The Wiki looks good, no similar plug-ins, or any 
other that could have this plug-in as a feature, code looks good as well, 
license compatible.

I think the only thing wrong is the artifactId. Can you rename it to 
artifactIdyaml-project/artifactId, please? The plug-in part only gets added 
to the github repository name. We can create a component in JIRA and assign you 
as maintainer, do you have a JIRA user already?

Thanks!
Bruno





 From: 'Matthew Moore' via Jenkins Developers jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Tuesday, September 9, 2014 1:41 PM
Subject: Re: new plugin hosting request
 


To be clear: I am not defining any YAML syntax.


The syntax for the YAML this parses is entirely defined by Jenkins' Structured 
Form Submissions.


This is entirely by design, since it means that basically any plugin that 
Jenkins can create through the UI, this plugin should be able to create from 
YAML.



Better still, the YAML asks users to specify precisely what the UI does :)






Are you going to host the plug-in under jenkinsci org at GitHub?


Yes, that is essentially what this thread is about.




Happy to chat more, especially if any of the above isn't clear.
-M





On Tue, Sep 9, 2014 at 8:55 AM, 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com wrote:



Hey Matthew, 


I'm working with a team using Ansible YAML playbooks, so probably using 
similar syntax for creating Jenkins projects would be a good idea. 


Are you going to host the plug-in under jenkinsci org at GitHub? 


Thanks!
Bruno




 From: 'Matthew Moore' via Jenkins Developers 
 jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Tuesday, September 9, 2014 12:41 PM
Subject: new plugin hosting request
 


I have posted a new plugin here:

  https://github.com/mattmoor/yaml-project-plugin



and added its associated wiki page here:
  https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin


FWIW, this is the basis of the talk I plan to give at JUC 2014 this Fall.





thanks,
-M



-- 

Matthew Moore
DI/Docker (aka Convoy)
Developer Infrastructure @ Google
-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.




-- 

Matthew Moore
DI/Docker (aka Convoy)
Developer Infrastructure @ Google

-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.

Re: new plugin hosting request

['Bruno P. Kinoshita' via Jenkins Developers]

testng-plugin and build-flow-plugin also use the -plugin suffix in the artifact 
id .

All set Matthew, plugin created at [1], component yaml-project created in JIRA. 
You should already have commit access, but let me know if that doesn't work. 

Also, I have already tried the YAML plug-in and I liked it. Are there other 
ways to get the YAML file, like from some web site, ftp, etc? 

Thanks!
Bruno

[1] https://github.com/jenkinsci/yaml-project-plugin



 From: 'Matthew Moore' via Jenkins Developers jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Tuesday, September 9, 2014 3:00 PM
Subject: Re: new plugin hosting request
 


Found one:
dependency
  groupIdorg.jenkins-ci.plugins/groupId
  artifactIdbuild-pipeline-plugin/artifactId
  version1.4.3/version
  optionaltrue/optional
/dependency


However, I'm just happy it means I'm not crazy, I have already pushed a change 
removing '-plugin' from artifactId.




thanks again,
-M







On Tue, Sep 9, 2014 at 10:57 AM, Matthew Moore mattm...@google.com wrote:

Huh, my mistake on Artifact ID.  I've been using -plugin for the various 
Google-specific plugins, but I sampled a few plugins I would have referenced 
and you are 100% correct :)


I'll change the artifact id shortly.  My username is generally 'mattmoor', 
pretty sure I am registered, since I've released a few plugins now.


thanks for the quick turnaround.
-M



On Tue, Sep 9, 2014 at 10:49 AM, 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com wrote:

Oh got it, then you simply convert the YAML file back to JSON. 


If there's no objection, I'll fork this repository under jenkinsci using the 
IRC bot in the next hour. The Wiki looks good, no similar plug-ins, or any 
other that could have this plug-in as a feature, code looks good as well, 
license compatible.


I think the only thing wrong is the artifactId. Can you rename it to 
artifactIdyaml-project/artifactId, please? The plug-in part only gets 
added to the github repository name. We can create a component in JIRA and 
assign you as maintainer, do you have a JIRA user already?


Thanks!
Bruno







 From: 'Matthew Moore' via Jenkins Developers 
 jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Tuesday, September 9, 2014 1:41 PM
Subject: Re: new plugin hosting request
 


To be clear: I am not defining any YAML syntax.


The syntax for the YAML this parses is entirely defined by Jenkins' 
Structured Form Submissions.


This is entirely by design, since it means that basically any plugin that 
Jenkins can create through the UI, this plugin should be able to create 
from YAML.



Better still, the YAML asks users to specify precisely what the UI does :)






Are you going to host the plug-in under jenkinsci org at GitHub?


Yes, that is essentially what this thread is about.




Happy to chat more, especially if any of the above isn't clear.
-M





On Tue, Sep 9, 2014 at 8:55 AM, 'Bruno P. Kinoshita' via Jenkins Developers 
jenkinsci-dev@googlegroups.com wrote:



Hey Matthew, 


I'm working with a team using Ansible YAML playbooks, so probably using 
similar syntax for creating Jenkins projects would be a good idea. 


Are you going to host the plug-in under jenkinsci org at GitHub? 


Thanks!
Bruno




 From: 'Matthew Moore' via Jenkins Developers 
 jenkinsci-dev@googlegroups.com
To: jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com 
Sent: Tuesday, September 9, 2014 12:41 PM
Subject: new plugin hosting request
 


I have posted a new plugin here:

  https://github.com/mattmoor/yaml-project-plugin



and added its associated wiki page here:
  https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin


FWIW, this is the basis of the talk I plan to give at JUC 2014 this Fall.





thanks,
-M



-- 

Matthew Moore
DI/Docker (aka Convoy)
Developer Infrastructure @ Google
-- 
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.
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.
For more options, visit https://groups.google.com/d/optout.






-- 

Matthew Moore
DI/Docker (aka Convoy)
Developer Infrastructure @ Google

-- 
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.
For more options, visit

Re: new plugin hosting request

['Matthew Moore' via Jenkins Developers]

You mean besides reading from a file in the workspace?  Not right now, but
it should.

One thing I've had on my TODO list forever is to add support for direct
entry of the YAML at the project level (big text box), but also possibly at
the BuildStep and Publisher levels.


Now that JIRA is set up, I should move my known issues / TODO items into
there, which will enable folks to poach and submit PR's ;-)

thanks again for getting me set up, and definitely LMK if you have any
feedback or hit any issues.
-M




On Tue, Sep 9, 2014 at 11:13 AM, 'Bruno P. Kinoshita' via Jenkins
Developers jenkinsci-dev@googlegroups.com wrote:

 testng-plugin and build-flow-plugin also use the -plugin suffix in the
 artifact id .

 All set Matthew, plugin created at [1], component yaml-project created in
 JIRA. You should already have commit access, but let me know if that
 doesn't work.

 Also, I have already tried the YAML plug-in and I liked it. Are there
 other ways to get the YAML file, like from some web site, ftp, etc?

 Thanks!
 Bruno

 [1] https://github.com/jenkinsci/yaml-project-plugin

   --
  *From:* 'Matthew Moore' via Jenkins Developers 
 jenkinsci-dev@googlegroups.com
 *To:* jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com
 *Sent:* Tuesday, September 9, 2014 3:00 PM

 *Subject:* Re: new plugin hosting request

 Found one:
 dependency
   groupIdorg.jenkins-ci.plugins/groupId
   artifactIdbuild-pipeline-plugin/artifactId
   version1.4.3/version
   optionaltrue/optional
 /dependency

 However, I'm just happy it means I'm not crazy, I have already pushed a
 change removing '-plugin' from artifactId.


 thanks again,
 -M




 On Tue, Sep 9, 2014 at 10:57 AM, Matthew Moore mattm...@google.com
 wrote:

 Huh, my mistake on Artifact ID.  I've been using -plugin for the various
 Google-specific plugins, but I sampled a few plugins I would have
 referenced and you are 100% correct :)

 I'll change the artifact id shortly.  My username is generally 'mattmoor',
 pretty sure I am registered, since I've released a few plugins now.

 thanks for the quick turnaround.
 -M


 On Tue, Sep 9, 2014 at 10:49 AM, 'Bruno P. Kinoshita' via Jenkins
 Developers jenkinsci-dev@googlegroups.com wrote:

 Oh got it, then you simply convert the YAML file back to JSON.

 If there's no objection, I'll fork this repository under jenkinsci using
 the IRC bot in the next hour. The Wiki looks good, no similar plug-ins, or
 any other that could have this plug-in as a feature, code looks good as
 well, license compatible.

 I think the only thing wrong is the artifactId. Can you rename it
 to artifactIdyaml-project/artifactId, please? The plug-in part only
 gets added to the github repository name. We can create a component in JIRA
 and assign you as maintainer, do you have a JIRA user already?

 Thanks!
 Bruno



   --
  *From:* 'Matthew Moore' via Jenkins Developers 
 jenkinsci-dev@googlegroups.com
 *To:* jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com
 *Sent:* Tuesday, September 9, 2014 1:41 PM
 *Subject:* Re: new plugin hosting request

 To be clear: I am not defining any YAML syntax.

 The syntax for the YAML this parses is entirely defined by Jenkins'
 Structured Form Submissions.

 This is entirely by design, since it means that basically any plugin that
 Jenkins can create through the UI, this plugin *should* be able to create
 from YAML.

 Better still, the YAML asks users to specify precisely what the UI does :)



 *Are you going to host the plug-in under jenkinsci org at GitHub?*

 Yes, that is essentially what this thread is about.


 Happy to chat more, especially if any of the above isn't clear.
 -M



 On Tue, Sep 9, 2014 at 8:55 AM, 'Bruno P. Kinoshita' via Jenkins
 Developers jenkinsci-dev@googlegroups.com wrote:


 Hey Matthew,

 I'm working with a team using Ansible YAML playbooks, so probably using
 similar syntax for creating Jenkins projects would be a good idea.

 Are you going to host the plug-in under jenkinsci org at GitHub?

 Thanks!
 Bruno

   --
  *From:* 'Matthew Moore' via Jenkins Developers 
 jenkinsci-dev@googlegroups.com
 *To:* jenkinsci-dev@googlegroups.com jenkinsci-dev@googlegroups.com
 *Sent:* Tuesday, September 9, 2014 12:41 PM
 *Subject:* new plugin hosting request

 I have posted a new plugin here:
   https://github.com/mattmoor/yaml-project-plugin

 and added its associated wiki page here:
   https://wiki.jenkins-ci.org/display/JENKINS/YAML+Project+Plugin

 FWIW, this is the basis of the talk I plan to give at JUC 2014 this Fall.


 thanks,
 -M


 --
 Matthew Moore
 DI/Docker (aka Convoy)
 Developer Infrastructure @ Google
  --
 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.
 For more options, visit

Re: New Plugin Hosting Request (Scoverage)

[Ulli Hafner]

Created: https://github.com/jenkinsci/scoverage-plugin

Welcome aboard!

Ulli

Am 21.03.2014 um 07:54 schrieb Shanbin Wang shanbin.w...@gmail.com:

 Hello,
 
 I'd like to create a new plugin to publish Scala code coverage trend graph 
 based on scoverage results.
 
 GitHub username: shanbin
 GitHub repo: https://github.com/shanbin/scoverage-plugin
 Plugin name: Scoverage Plugin
 
 Please help grant the commit access.
 
 Thanks,
 Shanbin
 
 -- 
 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.
 For more options, visit https://groups.google.com/d/optout.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: New Plugin Hosting Request (Scoverage)

[Shanbin Wang]

Thank you Ulli!

On Friday, March 21, 2014 2:54:15 PM UTC+8, Shanbin Wang wrote:

 Hello,

 I'd like to create a new plugin to publish Scala code coverage trend graph 
 based on scoverage results.

 GitHub username: shanbin
 GitHub repo: https://github.com/shanbin/scoverage-plugin
 Plugin name: Scoverage Plugin

 Please help grant the commit access.

 Thanks,
 Shanbin


-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: New Plugin Hosting Request (Scoverage)

[Shanbin Wang]

Thank you Ulli!

On Saturday, March 22, 2014 6:35:30 PM UTC+8, Ullrich Hafner wrote:

 Created: https://github.com/jenkinsci/scoverage-plugin

 Welcome aboard!

 Ulli

 Am 21.03.2014 um 07:54 schrieb Shanbin Wang shanbi...@gmail.comjavascript:
 :

 Hello,

 I'd like to create a new plugin to publish Scala code coverage trend graph 
 based on scoverage results.

 GitHub username: shanbin
 GitHub repo: https://github.com/shanbin/scoverage-plugin
 Plugin name: Scoverage Plugin

 Please help grant the commit access.

 Thanks,
 Shanbin

 -- 
 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 javascript:.
 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.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin hosting request

[Ulli Hafner]

Created https://github.com/jenkinsci/semantic-versioning-plugin

Welcome aboard! 

Ulli
Am 15.03.2014 um 23:30 schrieb ciroque.dr...@gmail.com:

 Hi,
 
 I would like to add a new plugin to the repo. As per the instructions:
 
 The plugin name is: SemanticVersioning
 My Github id is: ciroque
 Existing Githib repo: https://github.com/ciroque/SemanticVersioning
 
 The plugin parses both SBT-based and POM-based build definition files 
 and populates a build variable for use in later build steps. 
 Additionally, the version is written to a file in the artifact directory.
 
 The second part of the plugin creates a new column that shows the 
 version for the most-recent successful build.
 
 The version is generated based on the value in the build definition file 
 with the Jenkins build number subbed in for the, well, build number. 
 SNAPSHOT builds are supported as well.
 
 I searched around and the only thing I found that was remotely close is 
 this project which has only skeleton files in place, no functionality.
 
 In the short term I intend on adding parsing support for build.sbt 
 files. I am most definitely open to feature requests and pull requests 
 for enhancing the functionality.
 
 Best,
 
 Steve Wagner
 
 -- 
 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.
 For more options, visit https://groups.google.com/d/optout.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: New plugin hosting request

[Mads Mohr Christensen]

Hi,

Is there anything required by me in order to move forward with this request?

Mads.

On 02-12-2013 19:22, Mads Mohr Christensen wrote:
 Hi,

 I have been working on a plugin that can bridge the two plugins
 Promoted Builds and Parameterized Trigger:

 https://github.com/hrmohr/promoted-builds-parameterized-trigger-bridge

 The initial version adds support for using a promoted build as a
 parameter when triggered using Parmaterized Trigger Plugin.

 I would like to release this plugin and would like to host it under
 jenkinsci at github.

 This is my first attempt at writing a plugin and I would appreciate
 any comments. 

 Cheers,

 Mads.

-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: new plugin hosting request

[Maurice Williams]

Thanks Dominik,

You're right, there is no pure credentials authentication just yet. The 
closest thing to it using the API Token Jenkins generates for each user. It 
was the easiest thing to get implemented :-p 

I also saw your comments on my last commit - this is my first Jenkins 
plugin, so they are greatly appreciated! I'll make sure to review them 
before publishing.

Oh, and I had a question: since my personal repo was forked to the 
Jenkins-CI repo, is there a recommended ? Should I make the changes on my 
repo then sync up with the Jenkins-CI one, or should I just ditch my repo 
all together and work only on the Jenkins one?


On Saturday, November 30, 2013 6:02:49 AM UTC-5, Dominik Bartholdi wrote:

 Hey, this is really cool, been waiting for something like this!
 The only thing I think is missing: support for the credentials plugin.

 Your repo is forked: 
 https://github.com/jenkinsci/parameterized-remote-trigger-plugin
 A component in JIRA is created 'parameterized-remote-trigger’ and your the 
 lead of it.
 The CI Jobs will be created by someone else (Nicolas/ndeloof?)

 /Domi


 On 30.11.2013, at 04:14, Maurice Williams morf...@gmail.com javascript: 
 wrote:

 Hello there,

 I've created a new plugin to easily trigger a (parametrized or 
 non-parametrized) job on a remote Jenkins host, with multiple 
 authentication options (build token, API token or using the build token 
 root plugin) and I would love to share this with the community.

 My GitHub ID is morficus http://github.com/morficus and the plugin 
 already exists here: 
 https://github.com/morficus/Parameterized-Remote-Trigger-Plugin, so you 
 can just fork it.

 The one thing that's missing from it write now is automated test cases 
 (either unit or functional). But I should have time to work on those come 
 mid-December.

 I'm currently reading through the Hosting Plugins wiki page and should 
 be ready to release the plugin soon.
 Let me know if there is anything I'm missing.

 -- 
 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 javascript:.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: new plugin hosting request

[Maurice Williams]

 Oh, and I had a question: since my personal repo was forked to the 
 Jenkins-CI repo, is there a recommended ? Should I make the changes on my 
 repo then sync up with the Jenkins-CI one, or should I just ditch my repo 
 all together and work only on the Jenkins one?


Ignore that... I answered my own question as I went through the publishing 
process :-p


On Saturday, November 30, 2013 12:11:10 PM UTC-5, Maurice Williams wrote:

 Thanks Dominik,

 You're right, there is no pure credentials authentication just yet. The 
 closest thing to it using the API Token Jenkins generates for each user. It 
 was the easiest thing to get implemented :-p 

 I also saw your comments on my last commit - this is my first Jenkins 
 plugin, so they are greatly appreciated! I'll make sure to review them 
 before publishing.

 Oh, and I had a question: since my personal repo was forked to the 
 Jenkins-CI repo, is there a recommended ? Should I make the changes on my 
 repo then sync up with the Jenkins-CI one, or should I just ditch my repo 
 all together and work only on the Jenkins one?


 On Saturday, November 30, 2013 6:02:49 AM UTC-5, Dominik Bartholdi wrote:

 Hey, this is really cool, been waiting for something like this!
 The only thing I think is missing: support for the credentials plugin.

 Your repo is forked: 
 https://github.com/jenkinsci/parameterized-remote-trigger-plugin
 A component in JIRA is created 'parameterized-remote-trigger’ and your 
 the lead of it.
 The CI Jobs will be created by someone else (Nicolas/ndeloof?)

 /Domi


 On 30.11.2013, at 04:14, Maurice Williams morf...@gmail.com wrote:

 Hello there,

 I've created a new plugin to easily trigger a (parametrized or 
 non-parametrized) job on a remote Jenkins host, with multiple 
 authentication options (build token, API token or using the build token 
 root plugin) and I would love to share this with the community.

 My GitHub ID is morficus http://github.com/morficus and the plugin 
 already exists here: 
 https://github.com/morficus/Parameterized-Remote-Trigger-Plugin, so you 
 can just fork it.

 The one thing that's missing from it write now is automated test cases 
 (either unit or functional). But I should have time to work on those come 
 mid-December.

 I'm currently reading through the Hosting Plugins wiki page and should 
 be ready to release the plugin soon.
 Let me know if there is anything I'm missing.

 -- 
 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.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: New plugin hosting request: Dynamic Search View Plugin

[Oleg Nenashev]

Hello,

Seems that I have enough permissions to release plugin on my own. So, it is 
available for download now.
Plugin's wiki page: 
https://wiki.jenkins-ci.org/display/JENKINS/Dynamic+Search+View+Plugin

Best regards,
Oleg Nenashev

вторник, 2 июля 2013 г., 23:03:44 UTC+4 пользователь Oleg Nenashev написал:

 Hello,

 Plugin provides extended implementation of ListView.
 Dynamic Search View allows setting of additional filters at the view's 
 main page, which will be applied after clicking on the Submit button. So, 
 user is able to filter and search jobs without creation of new Views.

 GitHub URL: https://github.com/synopsys-arc-oss/dynamic-search-view-plugin

 Best regards,
 Oleg Nenashev
 RD Engineer, Synopsys Inc.

 P.S: I'll be grateful for any comments and proposals
 P.P.S: I'll be very grateful if anybody knows way, which allows to get 
 HTTP request parameters in Jelly. Current internal caching approach is 
 doesn't seem good :(


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: new plugin hosting request: Windows Azure Storage plugin

[Kohsuke Kawaguchi]

Hi, I created https://github.com/jenkinsci/windows-azure-storage-plugin 
and you should have all the access.


If you want us to add other people as committers, please let us know. Or 
if you can come to IRC, we can set you up so that you can add others by 
yourself.


Also, I looked at the POM, and I'd suggest you change the artifactId 
from WindowsAzureStorage to windows-azure-storage. Not a big deal if you 
feel strongly. but it'll just be more inline with our current naming 
convention.




On 04/01/2013 01:50 PM, Martin Sawicki (MS OPEN TECH) wrote:

Hello,

Kindly requesting the hosting of our new Jenkins plugin:

-  git clone: https://git01.codeplex.com/wastorageplugin

-  my GitHub userid: martinsawicki

Thank you.

Martin Sawicki

Principal Program Manager

Microsoft Open Technologies, Inc.

A subsidiary of Microsoft Corporation

--
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.
For more options, visit https://groups.google.com/groups/opt_out.





--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Try Nectar, our professional version of Jenkins

--
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.
For more options, visit https://groups.google.com/groups/opt_out.

RE: new plugin hosting request: Windows Azure Storage plugin

[Martin Sawicki (MS OPEN TECH)]

Great. I'd appreciate if you could add the following github ids as additional 
committers then: 
- sureshreddygithub
- msopentech-lab

Thanks!

-Original Message-
From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On 
Behalf Of Kohsuke Kawaguchi
Sent: Wednesday, April 03, 2013 10:40 AM
To: jenkinsci-dev@googlegroups.com
Cc: Martin Sawicki (MS OPEN TECH)
Subject: Re: new plugin hosting request: Windows Azure Storage plugin


Hi, I created https://github.com/jenkinsci/windows-azure-storage-plugin
and you should have all the access.

If you want us to add other people as committers, please let us know. Or if you 
can come to IRC, we can set you up so that you can add others by yourself.

Also, I looked at the POM, and I'd suggest you change the artifactId from 
WindowsAzureStorage to windows-azure-storage. Not a big deal if you feel 
strongly. but it'll just be more inline with our current naming convention.



On 04/01/2013 01:50 PM, Martin Sawicki (MS OPEN TECH) wrote:
 Hello,

 Kindly requesting the hosting of our new Jenkins plugin:

 -  git clone: https://git01.codeplex.com/wastorageplugin

 -  my GitHub userid: martinsawicki

 Thank you.

 Martin Sawicki

 Principal Program Manager

 Microsoft Open Technologies, Inc.

 A subsidiary of Microsoft Corporation

 --
 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.
 For more options, visit https://groups.google.com/groups/opt_out.




--
Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our 
professional version of Jenkins

--
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.
For more options, visit https://groups.google.com/groups/opt_out.





-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

RE: New Plugin Hosting Request for Gearman Plugin

[Sandell, Robert]

Done, sorry for the delay.

This looks very interesting, seems like it would solve one of our long term 
goals at my work. I might just try this out whenever I get time :)


Robert Sandell
Software Tools Engineer - SW Environment and Product Configuration
Sony Mobile Communications

From: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] On 
Behalf Of Zaro
Sent: den 25 mars 2013 22:29
To: jenkinsci-dev@googlegroups.com
Subject: Re: New Plugin Hosting Request for Gearman Plugin

Bumping request.. :)

On Tuesday, February 26, 2013 3:44:18 PM UTC-8, Zaro wrote:
I'd like to request hosting for a new plugin the Gearman Plugin

Please clone it from: https://github.com/openstack-infra/gearman-plugin
I've already created a wiki for it: 
https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin

My GitHub id is 'zaro0508'
My jenkins-ci.orghttp://jenkins-ci.org/ id is 'zaro'

If I'm missing something that I need to have done, please let me know.

Thanks!
Khai 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.commailto:jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: New Plugin Hosting Request for Gearman Plugin

[Zaro Do]

hey. thanks Sam.

On Tuesday, February 26, 2013 3:54:47 PM UTC-8, Sam Kottler wrote:

 An I just made the same mistake :-)

 https://github.com/openstack-infra/gearman-plugin

 -Sam

 On Tue, Feb 26, 2013 at 6:50 PM, Sam Kottler 
 s...@kottlerdevelopment.comjavascript:
  wrote:

 The href for the link to the plugin is not correct. It should be 
 https://github.com/openstack-infra/gearman-pluginhttps://github.com/randycoulman/visualworks-store-plugin.git
 .
  
 On Tue, Feb 26, 2013 at 6:44 PM, Zaro Do zaro...@gmail.com javascript:
  wrote:

 I'd like to request hosting for a new plugin the Gearman Plugin

 Please clone it from: 
 https://github.com/openstack-infra/gearman-pluginhttps://github.com/randycoulman/visualworks-store-plugin.git
 I've already created a wiki for it: 
 https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin
 Issue tracking is here:https://bugs.launchpad.net/~gearman-plugin-core

 My GitHub id is 'zaro0508'
 My jenkins-ci.org http://jenkins-ci.org/ id is 'zaro'

 If I'm missing something that I need to have done, please let me know.

 Thanks!
 Khai 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-de...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/groups/opt_out.
  
  





-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: New Plugin Hosting Request for Gearman Plugin

[Sam Kottler]

The href for the link to the plugin is not correct. It should be
https://github.com/openstack-infra/gearman-pluginhttps://github.com/randycoulman/visualworks-store-plugin.git
.

On Tue, Feb 26, 2013 at 6:44 PM, Zaro Do zaro0...@gmail.com wrote:

 I'd like to request hosting for a new plugin the Gearman Plugin

 Please clone it from: 
 https://github.com/openstack-infra/gearman-pluginhttps://github.com/randycoulman/visualworks-store-plugin.git
 I've already created a wiki for it:
 https://wiki.jenkins-ci.org/display/JENKINS/Gearman+Plugin
 Issue tracking is here:https://bugs.launchpad.net/~gearman-plugin-core

 My GitHub id is 'zaro0508'
 My jenkins-ci.org http://jenkins-ci.org/ id is 'zaro'

 If I'm missing something that I need to have done, please let me know.

 Thanks!
 Khai 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.
 For more options, visit https://groups.google.com/groups/opt_out.




-- 
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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: New Plugin Hosting Request: Uptime

[Vojtech Juranek]

Hi,

 I'd like to request hosting for my new Jenkins uptime plugin. 

done [1], welcome aboard.
Cheers
Vojta

[1] https://github.com/jenkinsci/uptime-plugin

-- 
You received this message because you are subscribed to the Google Groups 
Jenkins Developers group.
To unsubscribe from this group, send email to 
jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.