Re: GSOC 17

2017-01-06 Thread martinda
On Thursday, January 5, 2017 at 1:48:23 PM UTC-5, shubham sharma wrote:

> Hello, I am looking forward to participate in GSOC'17 & am new to open 
> source developmemt. Please can anyone help getting started ?
>

Hello Shubham.

If you want to participate as a mentor, see this message 
.

If you are interested to participate as a student, the process has not 
started yet, but you can see the official GSoC timeline 
.

If you'd like to propose a project as a mentor or a as student, perhaps you 
can start a discussion with your ideas on this mailing list or on the 
jenkins user mailing list (I am not sure which list would be better). For 
example, there are plugins that would greatly benefit from being compatible 
with the Jenkins Pipeline DSL. You could do some research and pick one that 
has lots of users, and make some proposals to make it compatible to the 
Jenkins Pipeline DSL. There are other ways to contribute as well, such as 
providing additional features to the core or to the plugins. You can find a 
list of current feature requests and issues here 
.

If you'd rather join forces with an existing GSoC 2017 project proposal, I 
am afraid that those have not been captured yet because it is still too 
early in the process. So check this list for the official announcement.

Martin

-- 
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/4c07ac61-104e-4661-a331-d3957667d1bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: confused by new Jenkins plugins web pages

2017-01-06 Thread Slide
When can we get rid of the wiki pages and source from the plugins readme
directly? :-)

On Fri, Jan 6, 2017, 18:14 Daniel Beck  wrote:

>
> > On 07.01.2017, at 01:47, Moshe Cohen  wrote:
> >
> > 1) Where is the link to the Github repo?
>
> I filed this https://issues.jenkins-ci.org/browse/WEBSITE-279
>
> > 2) How can I edit the page itself when there is an update?
>
> The documentation content is still sourced from the plugin wiki page, so
> edit that and wait a bit. Each plugin's detail view contains a link to the
> wiki page in the bar to the right.
>
> --
> 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/814455F8-DD56-47DD-AB41-472B044259B2%40beckweb.net
> .
> 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/CAPiUgVfXjHc43WRjgPqjdDyqj0fHRoU7VjbHnsUuUKiVAaEv%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: confused by new Jenkins plugins web pages

2017-01-06 Thread Daniel Beck

> On 07.01.2017, at 01:47, Moshe Cohen  wrote:
> 
> 1) Where is the link to the Github repo?

I filed this https://issues.jenkins-ci.org/browse/WEBSITE-279

> 2) How can I edit the page itself when there is an update?

The documentation content is still sourced from the plugin wiki page, so edit 
that and wait a bit. Each plugin's detail view contains a link to the wiki page 
in the bar to the right.

-- 
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/814455F8-DD56-47DD-AB41-472B044259B2%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


confused by new Jenkins plugins web pages

2017-01-06 Thread Moshe Cohen
Hi,

In the new Jenkins web site, on a plugin page:
1) Where is the link to the Github repo?
2) How can I edit the page itself when there is an update?


-- 
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/994908fd-fb72-4849-bd5a-e4b3cb1ae294%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: ConfigurationSlicing plugin looking for new ownership

2017-01-06 Thread Daniel Beck

> On 06.01.2017, at 16:16, Michael Donohue  wrote:
> 
> I would love for someone to take on this plugin. 

I tagged its wiki page to increase the visibility of this.

-- 
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/DC3C7E7D-2C2B-4107-9162-AADAC0078D3F%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Re: distributed build behavior, java.io.* classes, and security

2017-01-06 Thread Jesse Glick
On Fri, Jan 6, 2017 at 1:45 PM, Robert St. John  wrote:
> Does master-slave
> communication use TLS

Depends entirely on the agent’s launcher. SSH is common, for example.
For purposes of your plugin you may assume that the connection itself
is secure.

Your current approach to extract the `PrivateKey` from the keystore on
the master makes sense to me. While you *could* transmit the entire
`CertificateCredentialsImpl`, this seems like a needless risk.

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


Re: distributed build behavior, java.io.* classes, and security

2017-01-06 Thread Robert St. John
Thank you both for your input.  The plugin currently does as you say, 
Stephen, looking up the StandardCertificateCredentials instance on the 
master node.  The part that makes me wary is using the FileCallable to send 
the decrypted java.security.Key to the slave.  Does master-slave 
communication use TLS as it pertains to FileCallable?

The only other solution obvious to me is to send the file to the master to 
be signed.  While not desirable, that would not be too horrible because the 
files should be tolerably small - probably no bigger than 10 MB in most 
cases.

I'd like to release this plugin as a Jenkins-hosted plugin eventually, but 
I of course would not want to release something that undermines users' 
security, especially in enterprise and cloud environments.  I'd be grateful 
if you both took a brief look at the code 
 to make sure it's on 
the up and up.  It's a small project, and everything relevant is in the 
SignApksBuilder class.  Are there any other security-related items I should 
document, such as your note, Jesse, to enable slave-to-master security?

By the way, Stephen, is there any reason that 
StandardCertificateCredentials could not be modified to allow a passphrase 
per private key, separate from the keystore's passphrase?

Thanks.

Robert


On Friday, January 6, 2017 at 7:45:06 AM UTC-7, Jesse Glick wrote:
>
> On Thu, Jan 5, 2017 at 10:18 PM, Robert St. John  > wrote: 
> > I ended up passing a decrypted 
> > java.security.Key instance through a FileCallable to the slave.  Would 
> that 
> > ever be written to disk? 
>
> Not unless you write it. 
>
> > I could alternatively look up the private key from 
> > within the FlleCallable, but I believe that would result in the 
> Credentials 
> > plugin sending the key store password secret over the wire anyway. 
>
> I suppose you are talking about two kinds of secrets here: a keystore 
> passphrase, which might be used to protect many keys, some more 
> important than others; and a particular private key needed by this 
> build to sign something. In that case it is appropriate to obtain the 
> particular private key on the master side and send only it over the 
> wire, so that a malicious build would not obtain access to anything 
> else in the keystore or its passphrase. (Make sure the global security 
> setting for “slave-to-master security” is enabled!) 
>

-- 
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/6e1519bd-c496-4233-aa04-6e3a48b90afa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Retrieving a list of Pipeline jobs

2017-01-06 Thread Emory Penney
Perfect that got me exactly what I needed, thanks!

On Friday, January 6, 2017 at 6:24:30 AM UTC-8, Jesse Glick wrote:
>
> On Thu, Jan 5, 2017 at 7:07 PM, Emory Penney  > wrote: 
> > Neither of those classes have getTrigger() implemented, any tips 
> > for how to get build triggers from Job.class or WorkflowJob.class? 
>
> `ParameterizedJobMixIn.ParameterizedJob.getTriggers()` 
>

-- 
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/ba02579e-8d00-48c7-b848-e78562e77875%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Maintainer request for Amazon EC2 Spot Fleet Plugin

2017-01-06 Thread Chad Schmutzer
Thank you!

On Friday, January 6, 2017 at 8:45:17 AM UTC-8, Oleg Nenashev wrote:
>
> Hi, merged the PR. Good luck with the release!
>
> 2017-01-06 17:43 GMT+01:00 Chad Schmutzer  >:
>
>> Thanks so much for your help, Oleg.
>> Do you have any advice on how to get this PR accepted so I can push a new 
>> version of the plugin?
>>
>> https://github.com/jenkins-infra/repository-permissions-updater/pull/170
>>
>> thanks again!
>> chad
>>
>> On Wednesday, December 28, 2016 at 11:54:59 PM UTC-8, Oleg Nenashev wrote:
>>>
>>> Hi,
>>>
>>> Sorry for the delay. Permissions have been granted.
>>> Welcome aboard!
>>>
>>> BR, Oleg
>>>
>>> 2016-12-28 18:50 GMT+01:00 Oleg Nenashev :
>>>
 Nope, there is all info I need, thanks!
 I'll grant the permissions today

 2016-12-28 18:44 GMT+01:00 Chad Schmutzer :

> Checking if you need anything else to move forward with this?
>
> thanks,
> chad
>
>
> On Tuesday, December 27, 2016 at 11:41:39 AM UTC-8, Chad Schmutzer 
> wrote:
>>
>>  
>>
>> *From: *"Besogonov, Aleksei" 
>> *Date: *Thursday, December 22, 2016 at 4:53 AM
>> *To: *Oleg Nenashev , "
>> jenkin...@googlegroups.com" 
>> *Cc: *"Schmutzer, Chad" 
>> *Subject: *Re: Maintainer request for Amazon EC2 Spot Fleet Plugin
>>
>>  
>>
>> Yes, I’m authorizing this.
>>
>>  
>>
>> On Wednesday, December 21, 2016 at 3:38:29 PM UTC-8, Chad Schmutzer 
>> wrote:
>>>
>>> Greetings-
>>>
>>>
>>> I’m requesting to be made maintainer of the Amazon EC2 Spot Fleet 
>>> Plugin:
>>>
>>> https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Fleet+Plugin
>>>
>>> and
>>>
>>> https://github.com/jenkinsci/ec2-fleet-plugin
>>>
>>>
>>> I’m hoping this process can be fast-looped, as the current 
>>> maintainer Aleksei (cybe...@amazon.com) is my co-worker and copied 
>>> (and of course has approved).
>>>
>>>
>>> GitHub id: schmutze
>>>
>>> Jenkins infrastructure account id: schmutze
>>>
>>>
>>> Please let me know if you need anything else from me or Aleksei.
>>>
>>>
>>> Thanks for your help,
>>>
>>> Chad
>>>
>>> (schm...@amazon.com)
>>>
>>>
>>>
>>> -- 
> 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/sTs3LWvcmV8/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/f492d20d-7b90-4596-ac4f-c73273307415%40googlegroups.com
>  
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>


>>> -- 
>> 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/sTs3LWvcmV8/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/7ef25f8e-08ea-4f6a-be29-63225fefde8a%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/a5ca8e12-86a6-475f-88a0-a34da6fa2c7e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Maintainer request for Amazon EC2 Spot Fleet Plugin

2017-01-06 Thread Oleg Nenashev
Hi, merged the PR. Good luck with the release!

2017-01-06 17:43 GMT+01:00 Chad Schmutzer :

> Thanks so much for your help, Oleg.
> Do you have any advice on how to get this PR accepted so I can push a new
> version of the plugin?
>
> https://github.com/jenkins-infra/repository-permissions-updater/pull/170
>
> thanks again!
> chad
>
> On Wednesday, December 28, 2016 at 11:54:59 PM UTC-8, Oleg Nenashev wrote:
>>
>> Hi,
>>
>> Sorry for the delay. Permissions have been granted.
>> Welcome aboard!
>>
>> BR, Oleg
>>
>> 2016-12-28 18:50 GMT+01:00 Oleg Nenashev :
>>
>>> Nope, there is all info I need, thanks!
>>> I'll grant the permissions today
>>>
>>> 2016-12-28 18:44 GMT+01:00 Chad Schmutzer :
>>>
 Checking if you need anything else to move forward with this?

 thanks,
 chad


 On Tuesday, December 27, 2016 at 11:41:39 AM UTC-8, Chad Schmutzer
 wrote:
>
>
>
> *From: *"Besogonov, Aleksei" 
> *Date: *Thursday, December 22, 2016 at 4:53 AM
> *To: *Oleg Nenashev , "jenkin...@googlegroups.com"
> 
> *Cc: *"Schmutzer, Chad" 
> *Subject: *Re: Maintainer request for Amazon EC2 Spot Fleet Plugin
>
>
>
> Yes, I’m authorizing this.
>
>
>
> On Wednesday, December 21, 2016 at 3:38:29 PM UTC-8, Chad Schmutzer
> wrote:
>>
>> Greetings-
>>
>>
>> I’m requesting to be made maintainer of the Amazon EC2 Spot Fleet
>> Plugin:
>>
>> https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Fleet+Plugin
>>
>> and
>>
>> https://github.com/jenkinsci/ec2-fleet-plugin
>>
>>
>> I’m hoping this process can be fast-looped, as the current maintainer
>> Aleksei (cybe...@amazon.com) is my co-worker and copied (and of
>> course has approved).
>>
>>
>> GitHub id: schmutze
>>
>> Jenkins infrastructure account id: schmutze
>>
>>
>> Please let me know if you need anything else from me or Aleksei.
>>
>>
>> Thanks for your help,
>>
>> Chad
>>
>> (schm...@amazon.com)
>>
>>
>>
>> --
 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/to
 pic/jenkinsci-dev/sTs3LWvcmV8/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to
 jenkinsci-de...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/ms
 gid/jenkinsci-dev/f492d20d-7b90-4596-ac4f-c73273307415%40goo
 glegroups.com
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>> --
> 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/sTs3LWvcmV8/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/7ef25f8e-08ea-4f6a-be29-63225fefde8a%
> 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/CAPfivLCNum4YCXSQxVQ7fMWQM0Q8Kmw5PGUe29Dyk5S7ULkMbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Maintainer request for Amazon EC2 Spot Fleet Plugin

2017-01-06 Thread Chad Schmutzer
Thanks so much for your help, Oleg.
Do you have any advice on how to get this PR accepted so I can push a new 
version of the plugin?

https://github.com/jenkins-infra/repository-permissions-updater/pull/170

thanks again!
chad

On Wednesday, December 28, 2016 at 11:54:59 PM UTC-8, Oleg Nenashev wrote:
>
> Hi,
>
> Sorry for the delay. Permissions have been granted.
> Welcome aboard!
>
> BR, Oleg
>
> 2016-12-28 18:50 GMT+01:00 Oleg Nenashev  >:
>
>> Nope, there is all info I need, thanks!
>> I'll grant the permissions today
>>
>> 2016-12-28 18:44 GMT+01:00 Chad Schmutzer > >:
>>
>>> Checking if you need anything else to move forward with this?
>>>
>>> thanks,
>>> chad
>>>
>>>
>>> On Tuesday, December 27, 2016 at 11:41:39 AM UTC-8, Chad Schmutzer wrote:

  

 *From: *"Besogonov, Aleksei" 
 *Date: *Thursday, December 22, 2016 at 4:53 AM
 *To: *Oleg Nenashev , "
 jenkin...@googlegroups.com " 
 *Cc: *"Schmutzer, Chad" 
 *Subject: *Re: Maintainer request for Amazon EC2 Spot Fleet Plugin

  

 Yes, I’m authorizing this.

  

 On Wednesday, December 21, 2016 at 3:38:29 PM UTC-8, Chad Schmutzer 
 wrote:
>
> Greetings-
>
>
> I’m requesting to be made maintainer of the Amazon EC2 Spot Fleet 
> Plugin:
>
> https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Fleet+Plugin
>
> and
>
> https://github.com/jenkinsci/ec2-fleet-plugin
>
>
> I’m hoping this process can be fast-looped, as the current maintainer 
> Aleksei (cybe...@amazon.com ) is my co-worker and copied 
> (and of course has approved).
>
>
> GitHub id: schmutze
>
> Jenkins infrastructure account id: schmutze
>
>
> Please let me know if you need anything else from me or Aleksei.
>
>
> Thanks for your help,
>
> Chad
>
> (schm...@amazon.com )
>
>
>
> -- 
>>> 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/sTs3LWvcmV8/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to 
>>> jenkinsci-de...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/f492d20d-7b90-4596-ac4f-c73273307415%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/7ef25f8e-08ea-4f6a-be29-63225fefde8a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Not able to release new version of plugin

2017-01-06 Thread Baptiste Mathus
Can you create a branch or a PR against your repo so that we check actual
code/thing?

Also, did you *remove* the distributionManagement part from your pom as I
said?

2017-01-06 15:08 GMT+01:00 Irfan Sayed :

> I changed the version from 2.3 to 2.5 , but still it refers to old repo.
> then i again changed to more updated version of plugin POM : 2.11 , still
> the same issue...
> in the effective POM, there is no entry with 8081 port
>
> i have checked the .m2/settings.xml file as well, there is also not any
> old repo.
>
> i have referred this sample POM: https://github.com/
> jenkinsci/maven-hpi-plugin/blob/49fc9860c98b23a3690c5110b8
> 4aeefed12a/hpi-archetype/pom.xml#L6...L29
> i have deleted all the contents of local maven repo (just in case) and
> tried again.
>
> I am still not getting what is wrong ?
>
> regards,
>
>
>
>
> On Fri, Jan 6, 2017 at 5:30 AM, Daniel Beck  wrote:
>
>>
>> > On 06.01.2017, at 14:26, Irfan Sayed  wrote:
>> >
>> > 2.3 
>> >
>>
>> The first response you got linked to:
>> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#
>> HostingPlugins-Workingaroundcommonissues
>>
>> And it says:
>>
>> > … or update to the parent plugins POM 2.5 or newer
>>
>> 2.3 is not newer than 2.5.
>>
>> --
>> 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/ms
>> gid/jenkinsci-dev/AC4A284C-F84D-4F1C-AFE3-31EB11A6C819%40beckweb.net.
>> 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/CACGLCJapwky4ADhy88iiY%3DBUvNDa-
> k7ASQ7bXdjXTxRE0kQA5g%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/CANWgJS4q9uP5jz5n_5wnLdDFbX-K37BrgeAzNdPs9mKEWv6umg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


ConfigurationSlicing plugin looking for new ownership

2017-01-06 Thread Michael Donohue
The configurationslicing plugin has transitioned around a bit, and I've
tried to maintain it recently, but I don't have the time.   There are 3
pending PRs right now, that all look reasonable.  I would love for someone
to take on this plugin.

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


Re: distributed build behavior, java.io.* classes, and security

2017-01-06 Thread Jesse Glick
On Thu, Jan 5, 2017 at 10:18 PM, Robert St. John  wrote:
> I ended up passing a decrypted
> java.security.Key instance through a FileCallable to the slave.  Would that
> ever be written to disk?

Not unless you write it.

> I could alternatively look up the private key from
> within the FlleCallable, but I believe that would result in the Credentials
> plugin sending the key store password secret over the wire anyway.

I suppose you are talking about two kinds of secrets here: a keystore
passphrase, which might be used to protect many keys, some more
important than others; and a particular private key needed by this
build to sign something. In that case it is appropriate to obtain the
particular private key on the master side and send only it over the
wire, so that a malicious build would not obtain access to anything
else in the keystore or its passphrase. (Make sure the global security
setting for “slave-to-master security” is enabled!)

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


Re: distributed build behavior, java.io.* classes, and security

2017-01-06 Thread Jesse Glick
On Fri, Jan 6, 2017 at 4:47 AM, Stephen Connolly
 wrote:
> NEVER send a Credentials instance to an agent
>
> The secret will be unencryptable when it lands on the agent as the agent
> does not have the master key
>
> You need to extract the secrets on the master JVM and handle sending them
> over yourself.

Can you explain please? `Secret.value` is plaintext and is in the
serialized form, so when a `UsernamePasswordCredentialsImpl` (for
example) is passed over the Remoting channel its `password` should
arrive intact.

> This is why there are bugs in e.g. Subversion plugin and Git plugin
> (manifesting most obviously in the inability to use git with SSH key
> credentials that have a passphrase to checkout on a remote agent)

Is this not precisely what
`BasicSSHUserPrivateKey.CredentialsSnapshotTakerImpl` is for? Again
the `passphrase` is a `Secret` which ought to survive the trip to the
agent. And `writeReplace` ought to be ensuring that the `snapshot` is
taken automatically when the credentials are included in any
serialized request.

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


Re: distributed build behavior, java.io.* classes, and security

2017-01-06 Thread Jesse Glick
On Thu, Jan 5, 2017 at 10:18 PM, Robert St. John  wrote:
> my Builder code is executed on master

Yes, `perform` is run in the master JVM.

> while the
> process I invoked using the launcher ran on the slave

`Launcher` transparently starts processes remotely where required.

> I assumed that all
> the instructions of my Builder were executing on the slave.

No. BTW Daniel Beck is working on improved developer documentation
which ought to make the division clearer. See the docs mailing list.

> I ran into a
> problem when code in my Builder needed to use a java.io.File object in the
> Builder to reference the output file of the process I launched with the
> launcher, and so the java.io.File did not exist as far as the Builder was
> concerned.

Again, from code invoked via from `perform`, you may only use
`FilePath`, not `java.io.*`. (Unless you are inside a remote callable;
e.g., `FilePath.act`.)

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


Re: Retrieving a list of Pipeline jobs

2017-01-06 Thread Jesse Glick
On Thu, Jan 5, 2017 at 7:07 PM, Emory Penney  wrote:
> Neither of those classes have getTrigger() implemented, any tips
> for how to get build triggers from Job.class or WorkflowJob.class?

`ParameterizedJobMixIn.ParameterizedJob.getTriggers()`

-- 
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/CANfRfr02Dgq%2BCPeqELxKY-5vKf-1uc-%2BBG55W61h0LuKvd3foQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Not able to release new version of plugin

2017-01-06 Thread Irfan Sayed
I changed the version from 2.3 to 2.5 , but still it refers to old repo.
then i again changed to more updated version of plugin POM : 2.11 , still
the same issue...
in the effective POM, there is no entry with 8081 port

i have checked the .m2/settings.xml file as well, there is also not any old
repo.

i have referred this sample POM:
https://github.com/jenkinsci/maven-hpi-plugin/blob/49fc9860c98b23a3690c5110b84aeefed12a/hpi-archetype/pom.xml#L6...L29
i have deleted all the contents of local maven repo (just in case) and
tried again.

I am still not getting what is wrong ?

regards,




On Fri, Jan 6, 2017 at 5:30 AM, Daniel Beck  wrote:

>
> > On 06.01.2017, at 14:26, Irfan Sayed  wrote:
> >
> > 2.3 
> >
>
> The first response you got linked to:
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+
> Plugins#HostingPlugins-Workingaroundcommonissues
>
> And it says:
>
> > … or update to the parent plugins POM 2.5 or newer
>
> 2.3 is not newer than 2.5.
>
> --
> 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/AC4A284C-F84D-4F1C-AFE3-31EB11A6C819%40beckweb.net.
> 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/CACGLCJapwky4ADhy88iiY%3DBUvNDa-k7ASQ7bXdjXTxRE0kQA5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Not able to release new version of plugin

2017-01-06 Thread Daniel Beck

> On 06.01.2017, at 14:26, Irfan Sayed  wrote:
> 
> 2.3 
> 

The first response you got linked to:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues

And it says:

> … or update to the parent plugins POM 2.5 or newer

2.3 is not newer than 2.5.

-- 
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/AC4A284C-F84D-4F1C-AFE3-31EB11A6C819%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.


Re: Not able to release new version of plugin

2017-01-06 Thread Irfan Sayed
Sorry. actually i was confused. i red again and i guess i have to make
following changes and did that.
I made these changes in my plugin POM


org.jenkins-ci.plugins
plugin
2.3 
  

  
1.609.1
1.106
  

is this seems correct now?
but in the Plugin.POM file , i got following entries :

 

  false
  maven.jenkins-ci.org
  http://maven.jenkins-ci.org:8081/content/repositories/releases



  maven.jenkins-ci.org
  http://maven.jenkins-ci.org:8081/content/repositories/snapshots


  

i am not getting what is wrong. please help
Regards,





On Fri, Jan 6, 2017 at 3:31 AM, Baptiste Mathus  wrote:

> Irfan, seems like my mail went through looking at the archive. So please
> read it, and click on the link...
>
> We are spending time trying to help, so please at least read the link we
> provide.
>
> Thank you
>
> 2017-01-06 11:55 GMT+01:00 Irfan Sayed :
>
>> Thanks.
>>
>> any specific wiki to refer how to upgrade the version of Parent POM to
>> 2.x ?
>> I have removed the DistributionManagement entry from my plugin POM.
>>
>> Regards,
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Fri, Jan 6, 2017 at 12:38 AM, Oliver Gondža  wrote:
>>
>>> On 2017-01-06 08:37, Irfan Sayed wrote:
>>>
 Thanks.
 In the effective POM, i have following:

  
 
   java.net-m2-repository
   http://maven.jenkins-ci.org/content/repositories/releases/
 
 
 
   maven.jenkins-ci.org 

 http://maven.jenkins-ci.org:8081/content/repositories/snapshots
 
 
 
   github-pages

 gitsite:g...@github.com/jenkinsci/maven-site.git:plugin-
 parent/sinatra-chef-builder
 
 
   

 in snapshot repository, there is a port 8081
 but in release repo it is not.
 please let me know

>>>
>>> maven.jenkins-ci.org was discontinued, repo.jenkins-ci.org is the
>>> replacement. As long as the old hostname is coming up in effective pom,
>>> your pom is not configured correctly.
>>>
>>> This is annoying as hell, no question about that, but the easiest way to
>>> go here is to update the plugin-pom.
>>>
>>> --
>>> oliver
>>>
>>> --
>>> 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/ms
>>> gid/jenkinsci-dev/354e531b-24ac-be3e-d77d-8ca1e11fad9a%40gmail.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/ms
>> gid/jenkinsci-dev/CACGLCJbSvb869jJ_SGSrjrPMg%3DXYY2ykhU8U0T1
>> X5vF0yZxaQw%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/CANWgJS6_jOUvG%2BVgFZe%2BLp%
> 2BkCOKMzCQMRgo1EVbXs1oy0LasHQ%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/CACGLCJZW8tZipuJg31KFXKqO1JM%3Dvq-vC2tSPVA5ze4NEHECsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Not able to release new version of plugin

2017-01-06 Thread Baptiste Mathus
Irfan, seems like my mail went through looking at the archive. So please
read it, and click on the link...

We are spending time trying to help, so please at least read the link we
provide.

Thank you

2017-01-06 11:55 GMT+01:00 Irfan Sayed :

> Thanks.
>
> any specific wiki to refer how to upgrade the version of Parent POM to 2.x
> ?
> I have removed the DistributionManagement entry from my plugin POM.
>
> Regards,
>
>
>
>
>
>
>
>
>
>
> On Fri, Jan 6, 2017 at 12:38 AM, Oliver Gondža  wrote:
>
>> On 2017-01-06 08:37, Irfan Sayed wrote:
>>
>>> Thanks.
>>> In the effective POM, i have following:
>>>
>>>  
>>> 
>>>   java.net-m2-repository
>>>   http://maven.jenkins-ci.org/content/repositories/releases/
>>> 
>>> 
>>> 
>>>   maven.jenkins-ci.org 
>>>
>>> http://maven.jenkins-ci.org:8081/content/repositories/snapshots
>>> 
>>> 
>>> 
>>>   github-pages
>>>
>>> gitsite:g...@github.com/jenkinsci/maven-site.git:plugin-
>>> parent/sinatra-chef-builder
>>> >> in-parent/sinatra-chef-builder>
>>> 
>>>   
>>>
>>> in snapshot repository, there is a port 8081
>>> but in release repo it is not.
>>> please let me know
>>>
>>
>> maven.jenkins-ci.org was discontinued, repo.jenkins-ci.org is the
>> replacement. As long as the old hostname is coming up in effective pom,
>> your pom is not configured correctly.
>>
>> This is annoying as hell, no question about that, but the easiest way to
>> go here is to update the plugin-pom.
>>
>> --
>> oliver
>>
>> --
>> 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/ms
>> gid/jenkinsci-dev/354e531b-24ac-be3e-d77d-8ca1e11fad9a%40gmail.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/CACGLCJbSvb869jJ_SGSrjrPMg%3DXYY2ykhU8U0T1X5vF0yZxaQw%
> 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/CANWgJS6_jOUvG%2BVgFZe%2BLp%2BkCOKMzCQMRgo1EVbXs1oy0LasHQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Not able to release new version of plugin

2017-01-06 Thread Irfan Sayed
Thanks.

any specific wiki to refer how to upgrade the version of Parent POM to 2.x ?
I have removed the DistributionManagement entry from my plugin POM.

Regards,










On Fri, Jan 6, 2017 at 12:38 AM, Oliver Gondža  wrote:

> On 2017-01-06 08:37, Irfan Sayed wrote:
>
>> Thanks.
>> In the effective POM, i have following:
>>
>>  
>> 
>>   java.net-m2-repository
>>   http://maven.jenkins-ci.org/content/repositories/releases/
>> 
>> 
>> 
>>   maven.jenkins-ci.org 
>>
>> http://maven.jenkins-ci.org:8081/content/repositories/snapshots
>> 
>> 
>> 
>>   github-pages
>>
>> gitsite:g...@github.com/jenkinsci/maven-site.git:plugin-
>> parent/sinatra-chef-builder
>> > in-parent/sinatra-chef-builder>
>> 
>>   
>>
>> in snapshot repository, there is a port 8081
>> but in release repo it is not.
>> please let me know
>>
>
> maven.jenkins-ci.org was discontinued, repo.jenkins-ci.org is the
> replacement. As long as the old hostname is coming up in effective pom,
> your pom is not configured correctly.
>
> This is annoying as hell, no question about that, but the easiest way to
> go here is to update the plugin-pom.
>
> --
> oliver
>
> --
> 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/ms
> gid/jenkinsci-dev/354e531b-24ac-be3e-d77d-8ca1e11fad9a%40gmail.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/CACGLCJbSvb869jJ_SGSrjrPMg%3DXYY2ykhU8U0T1X5vF0yZxaQw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: distributed build behavior, java.io.* classes, and security

2017-01-06 Thread Stephen Connolly
On 6 January 2017 at 03:18, Robert St. John  wrote:

> Thanks for your reply.  I discovered by trial and error today what you
> said about using FilePath.  I changed all my java.io usage to FilePath
> and used a MasterToSlaveFileCallable subclass to accomplish my goal.  What
> was not intuitive to me was that my Builder code is executed on master,
> while the process I invoked using the launcher ran on the slave.  I assumed
> that all the instructions of my Builder were executing on the slave.  I ran
> into a problem when code in my Builder needed to use a java.io.File object
> in the Builder to reference the output file of the process I launched with
> the launcher, and so the java.io.File did not exist as far as the Builder
> was concerned.  Am I interpreting what I'm seeing correctly?
>
> Regarding what you said about secrets, I ended up passing a decrypted
> java.security.Key instance through a FileCallable to the slave.  Would that
> ever be written to disk?  I could alternatively look up the private key
> from within the FlleCallable, but I believe that would result in the
> Credentials plugin sending the key store password secret over the wire
> anyway.  What should I do to maximize the security and minimize assumptions
> about the way my Builder is run?
>

BEWARE THE ANTIPATTERN

NEVER send a Credentials instance to an agent

The secret will be unencryptable when it lands on the agent as the agent
does not have the master key

You need to extract the secrets on the master JVM and handle sending them
over yourself.

This is why there are bugs in e.g. Subversion plugin and Git plugin
(manifesting most obviously in the inability to use git with SSH key
credentials that have a passphrase to checkout on a remote agent)


>
> Thanks.
>
> Robert
>
> On Thu, Jan 5, 2017 at 3:12 PM, Jesse Glick  wrote:
>
>> On Tue, Dec 27, 2016 at 12:54 PM, Robert St. John 
>> wrote:
>> > I am using the Credentials
>> > plugin to load a keystore from a StandardCertificateCredential, which
>> as I
>> > understand ultimately uses FilePath to load the keystore from the master
>> > node.
>>
>> Yes, existing Jenkins code does send secrets over the wire to agents,
>> if they are being used for a build run on that agent. In general this
>> is unavoidable; in many cases the secrets will in fact wind up on disk
>> on the agent for the duration of the build, or be accessible from
>> `/proc`.
>>
>> If you wish to protect secrets from access by other builds, you have
>> no choice but to ensure either that each build runs on a “one-shot”
>> agent running in a container/VM (the Docker cloud model); or that each
>> build is somehow required to run all its build steps inside a fresh
>> container/VM even when the agent is reused (the Docker Pipeline model,
>> with restricted scripts).
>>
>> And yes you must use `FilePath` for all file operations relating to
>> workspaces. You can use `act` to perform a chunk of work remotely in
>> the interests of efficiency.
>>
>> --
>> 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/to
>> pic/jenkinsci-dev/xdyw9Jo4Fug/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/ms
>> gid/jenkinsci-dev/CANfRfr3gqj2OuSNdKeH5MNRrhACFpyLi-N5%
>> 2BLBHMeNdvj272rQ%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/CAEoDabuM2X6JnJh42LJfrv%2B55RzqOE%2B2U-
> 4EMEW32GtXPVciJw%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/CA%2BnPnMwhPeXiZEMF8yU51D5wJdsKfJR3Vhcx_EXd8EAJ6TgTJQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


How to set the UCD parameter in jenkins

2017-01-06 Thread Niranjana K N
Hello All 

we are using the jenkins for build and deploy 

when deploying from UCD how we can set the parameter, So we can select the 
server and process and ENV
How to set the parameter in jenkins for UCD 

Thanks
Niranajna

-- 
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/2c3972fa-30cf-45bf-9248-a73ec61b8b0f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Not able to release new version of plugin

2017-01-06 Thread Oliver Gondža

On 2017-01-06 08:37, Irfan Sayed wrote:

Thanks.
In the effective POM, i have following:

 

  java.net-m2-repository
  http://maven.jenkins-ci.org/content/repositories/releases/


  maven.jenkins-ci.org 

http://maven.jenkins-ci.org:8081/content/repositories/snapshots


  github-pages

gitsite:g...@github.com/jenkinsci/maven-site.git:plugin-parent/sinatra-chef-builder


  

in snapshot repository, there is a port 8081
but in release repo it is not.
please let me know


maven.jenkins-ci.org was discontinued, repo.jenkins-ci.org is the 
replacement. As long as the old hostname is coming up in effective pom, 
your pom is not configured correctly.


This is annoying as hell, no question about that, but the easiest way to 
go here is to update the plugin-pom.


--
oliver

--
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/354e531b-24ac-be3e-d77d-8ca1e11fad9a%40gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: Not able to release new version of plugin

2017-01-06 Thread Baptiste Mathus
Upgrade to the 2.x version of the parent pom + remove the
distributionManagement tag from your pom.

https://github.com/jenkinsci/plugin-pom

(Note : unrelated to upgrading to 2.x core baseline)

Cheers

Le 6 janv. 2017 8:37 AM, "Irfan Sayed"  a écrit :

> Thanks.
> In the effective POM, i have following:
>
>  
> 
>   java.net-m2-repository
>   http://maven.jenkins-ci.org/content/repositories/releases/
> 
> 
> 
>   maven.jenkins-ci.org
>   http://maven.jenkins-ci.org:8081/content/repositories/snapshots
> 
> 
> 
>   github-pages
>   gitsite:g...@github.com/jenkinsci/maven-site.git:
> plugin-parent/sinatra-chef-builder
> 
>   
>
> in snapshot repository, there is a port 8081
> but in release repo it is not.
> please let me know
>
> regards,
>
>
>
> On Thu, Jan 5, 2017 at 6:46 AM, Daniel Beck  wrote:
>
>>
>> > On 05.01.2017, at 15:15, Irfan Sayed  wrote:
>> >
>> > still the same error
>>
>> Unsurprising given that this still referenced the host name that has been
>> shut down.
>>
>> --
>> 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/ms
>> gid/jenkinsci-dev/6EF8E60C-351D-43F5-B873-B201E5F32FC9%40beckweb.net.
>> 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/CACGLCJaqJQjO-8ctOya5-U5kMALULRqY2fiadqiRg5FrB07tqA%
> 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/CANWgJS4j3NBqH2L5HSJXidT4tmfWnqzyfC2RK7yEwBmRaemriw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.