Re: Not able to release new version of plugin

[Irfan Sayed]

Thanks Baptiste.
I have created public gist and uploaded all data there.

https://gist.github.com/irfanjs/1e0315588d1e55dbbd28cc415fc4d157

please have a look.

Regards,
irfan


On Mon, Jan 9, 2017 at 11:28 AM, Baptiste Mathus  wrote:

> You're not helpable this way. Please describe what you did, and put the
> necessary data in gist.github.com or something. Like the error you're
> having. Is this really still the same error?
> You probably have something wrong locally or so you didn't push, because
> right now your pom.xml seems correct. At least can't see any ref to the old
> maven repo;
>
> 2017-01-09 17:44 GMT+01:00 Irfan Sayed :
>
>> Hi Baptiste,
>> Can you please help
>>
>> Regards,
>> Irfan
>>
>>
>> On Mon, Jan 9, 2017 at 12:08 PM, Irfan Sayed 
>> wrote:
>>
>>> Hi Baptiste,
>>> I tried creating settings.xml and try to perform the release. still the
>>> issue persist.
>>> Effective POM also looks OK.
>>>
>>>  
>>> 
>>>   maven.jenkins-ci.org
>>>   https://repo.jenkins-ci.org/releases/
>>> 
>>> 
>>>   maven.jenkins-ci.org
>>>   https://repo.jenkins-ci.org/snapshots/
>>> 
>>>   
>>>
>>> Regards,
>>> Irfan
>>>
>>>
>>>
>>> On Sun, Jan 8, 2017 at 12:57 AM, Irfan Sayed 
>>> wrote:
>>>
 Sorry. while experimenting, that modification left as it is. i fixed
 that and uploaded new version. please have a look
 further , please find the attached settings.xml as well

 Regards,


 On Sun, Jan 8, 2017 at 2:44 AM, Baptiste Mathus  wrote:

> Your current pom.xml is not even valid from a Maven PoV. You commented
> out the artifactId
> 
> for one.
> So I don't know what you're testing right now, but no, this is not
> what is on your repo because that immediately fails with Maven.
>
> Please file a PR with what you really have. For me, once this is
> removed this seems fine. Or maybe you have crap left somehow in your
> settings.xml.
>
> 2017-01-07 17:43 GMT+01:00 Irfan Sayed :
>
>> Thanks.
>> Yes. I did remove the DistributionManagement from my POM.
>> Please refer here actual code. This is the latest code which i would
>> like to release
>> https://github.com/jenkinsci/sinatra-chef-builder-plugin
>>
>> Regards,
>>
>>
>> On Fri, Jan 6, 2017 at 9:27 PM, Baptiste Mathus 
>> wrote:
>>
>>> 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/jenkin
 sci/maven-hpi-plugin/blob/49fc9860c98b23a3690c5110b84aee
 fed12a/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-F84
> D-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 

Re: [Experiment] Reviewers Team

[Jacob Larfors]

Nice, and thanks for the information.
I was recommended to add jenkinsci code-reviewers but perhaps this is not 
necessary for the low scale plugins I am working on as things have been 
working fine up until now.

PS - I accepted the invitation now to join jenkinsci (email got lost)

On Thursday, 5 January 2017 18:01:36 UTC+2, Daniel Beck wrote:
>
>
> > On 10.08.2016, at 08:42, James Dumay  
> wrote: 
> > 
> > All of the blueocean-plugin PRs mention the reviewers team... so If you 
> are looking to get involved in Blue Ocean reviewing is a great place to 
> start! 
>
> FTR I asked that this practice be stopped a few weeks ago, as it increased 
> the notification traffic a lot, and the BO developers generally seem to 
> have no problem finding reviewers for their changes. 
>
> Now @jenkinsci/code-reviewers should be back to be fairly low traffic and 
> limited to PRs where someone really thinks reviews are needed: 
>
>
> https://github.com/pulls?utf8=%E2%9C%93=is%3Aopen+is%3Apr+team%3Ajenkinsci%2Fcode-reviewers
>  
>
>

-- 
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/09926995-796e-4a27-a160-0554a2af9665%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Failed to deploy to http://maven.jenkins-ci.org:8081 for claim-plugin

[georg . henzler]

Just ran into the same issue... updating the  
section works. The Plugin Tutorial is outdated though:

  https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial  
links to 
  https://github.com/jenkinsci/hello-world-plugin/blob/master/pom.xml#L34 
(uses v2.2 of plugin parent)
v2.2 of plugin parent still uses the old :
  https://github.com/jenkinsci/plugin-pom/blob/plugin-2.2/pom.xml#L761 

It's probably best if the parent of hello-world-plugin would be updated to 
the latest plugin parent?

Regards
Georg

On Thursday, 10 November 2016 16:39:34 UTC+1, Daniel Beck wrote:
>
>
> > On 10.11.2016, at 08:12, Christian  
> wrote: 
> > 
> > I tried setting a new parent, but then the build fails see 
> https://github.com/jenkinsci/claim-plugin/commit/56098d240dfedffd6f1fbc2426ac4724de0880f3#diff-0
>  
> > I tried locally with several different jenkins-test-harness.version but 
> it always fails with compilation errors, what am I doing wrong? 
> > 
> > I am currently not developing this plugin actively but thought I would 
> release a new version with some pull request from the community but the 
> release process is not as easy as one would like.. 
>
> It seems like the dependency on mock_javamail needs to be explicit now. 
> Not sure where that's coming from. 
>
> And since we moved from our forked and patched HtmlUnit to the upstream 
> one more than a year ago[1] to be able to support testing with modern 
> JavaScript frameworks, some methods and types have changed. The alternative 
> is stagnation and obsolescence. 
>
> Additionally, the plugin used unsafe Jelly files, which could (with a 
> combination of other factors) result in XSS vulnerabilities. The HPI plugin 
> requires it to have an XML PI to escape by default for almost two years 
> now. 
>
> This might look like a lot, but if the plugin has been stale for years, 
> even a single change per year can pile up. 
>
> Note that the parent POM now by default runs FindBugs to improve code 
> quality, which results in a number of failures. You need to disable 
> FindBugs, or address these findings (fixing or ignoring). 
>
> I've opened a pull request with all my changes. 
>
>

-- 
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/5814114f-1463-4d9e-b743-5050716699cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

[Baptiste Mathus]

You're not helpable this way. Please describe what you did, and put the
necessary data in gist.github.com or something. Like the error you're
having. Is this really still the same error?
You probably have something wrong locally or so you didn't push, because
right now your pom.xml seems correct. At least can't see any ref to the old
maven repo;

2017-01-09 17:44 GMT+01:00 Irfan Sayed :

> Hi Baptiste,
> Can you please help
>
> Regards,
> Irfan
>
>
> On Mon, Jan 9, 2017 at 12:08 PM, Irfan Sayed  wrote:
>
>> Hi Baptiste,
>> I tried creating settings.xml and try to perform the release. still the
>> issue persist.
>> Effective POM also looks OK.
>>
>>  
>> 
>>   maven.jenkins-ci.org
>>   https://repo.jenkins-ci.org/releases/
>> 
>> 
>>   maven.jenkins-ci.org
>>   https://repo.jenkins-ci.org/snapshots/
>> 
>>   
>>
>> Regards,
>> Irfan
>>
>>
>>
>> On Sun, Jan 8, 2017 at 12:57 AM, Irfan Sayed 
>> wrote:
>>
>>> Sorry. while experimenting, that modification left as it is. i fixed
>>> that and uploaded new version. please have a look
>>> further , please find the attached settings.xml as well
>>>
>>> Regards,
>>>
>>>
>>> On Sun, Jan 8, 2017 at 2:44 AM, Baptiste Mathus  wrote:
>>>
 Your current pom.xml is not even valid from a Maven PoV. You commented
 out the artifactId
 
 for one.
 So I don't know what you're testing right now, but no, this is not what
 is on your repo because that immediately fails with Maven.

 Please file a PR with what you really have. For me, once this is
 removed this seems fine. Or maybe you have crap left somehow in your
 settings.xml.

 2017-01-07 17:43 GMT+01:00 Irfan Sayed :

> Thanks.
> Yes. I did remove the DistributionManagement from my POM.
> Please refer here actual code. This is the latest code which i would
> like to release
> https://github.com/jenkinsci/sinatra-chef-builder-plugin
>
> Regards,
>
>
> On Fri, Jan 6, 2017 at 9:27 PM, Baptiste Mathus  wrote:
>
>> 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/jenkin
>>> sci/maven-hpi-plugin/blob/49fc9860c98b23a3690c5110b84aee
>>> fed12a/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-F84
 D-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/CACGLCJapwky
>>> 4ADhy88iiY%3DBUvNDa-k7ASQ7bXdjXTxRE0kQA5g%40mail.gmail.com
>>> 

Need help configuring the pom.xml so I can have integration tests

['Claudiu Guiman' via Jenkins Developers]

Hi,
I'm trying to add integration tests in my plugin and I want them to be optional 
and only be triggered if you run a specific maven step.
To accomplish this I added a dependency to the maven failsafe plugin and now I 
need to run "mvn failsafe:integration-test" to run my specific integration 
tests.
So far so good, but when I need to execute some code that depends on jenkins 
I'm getting NoClassDefFoundError exceptions. I managed to fix some of these by 
adding a dependency to the jenkins-test-harness, but now I'm hitting one I 
can't fix: "java.lang.NoClassDefFoundError: 
com/google/common/reflect/TypeToken". The exception is due to the fact that I 
don't have a direct dependency to google guava, but the jenkins-core should 
bring that into my classpath, but even if I add the jenkins-core as a 
dependency within the "test" scope I can't manage to fix it.
Here's the pom file portion in question:

org.jenkins-ci.main
jenkins-test-harness
test


org.jenkins-ci.main
jenkins-core
provided


I'm using "provided" scope right now because that's what Maven recommends: 
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
Can someone help me understand what I'm doing wrong and how I should fix the 
pom file?

Thanks,
Claudiu

-- 
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/CY1PR0301MB1660D6BE07AB975399F2AFD2D7640%40CY1PR0301MB1660.namprd03.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maintainer request for Amazon EC2 Spot Fleet Plugin

[Oleg Nenashev]

Hi Chad,

It commonly takes several hours to get the release propagated to all
Jenkins mirrors. Before it the release does not show up in the update
center. If you do not see a release after 24 hours, please report the issue
to the Jenkins Infra mailing list.

BR, Oleg

2017-01-09 18:15 GMT+01:00 Chad Schmutzer :

> Dear Oleg,
>
> I've finally managed to push the release, but I'm having trouble
> understanding why the update is not showing up in the update center.
> Would you mind pointing me in the right direction? Should I create a
> ticket? I hate to bug, but I'm a bit stumped at this point.
>
> [INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @
> ec2-fleet ---
> Uploading: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2.hpi
> Uploaded: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2.hpi (970 KB at 345.6 KB/sec)
> Uploading: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2.pom
> Uploaded: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2.pom (4 KB at 8.4 KB/sec)
> Downloading: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/maven-metadata.xml
> Downloaded: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/maven-metadata.xml (396 B at 1.8 KB/sec)
> Uploading: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/maven-metadata.xml
> Uploaded: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/maven-metadata.xml (369 B at 1.1 KB/sec)
> Uploading: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2.jar
> Uploaded: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2.jar (27 KB at 68.8 KB/sec)
> Uploading: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2-sources.jar
> Uploaded: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2-sources.jar (14 KB at 35.1 KB/sec)
> Uploading: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2-javadoc.jar
> Uploaded: https://repo.jenkins-ci.org/releases/com/amazon/jenkins/
> fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2-javadoc.jar (80 KB at 169.5 KB/sec)
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 30.970 s
> [INFO] Finished at: 2017-01-08T21:03:17-08:00
> [INFO] Final Memory: 66M/849M
> [INFO] 
> 
> [INFO] Cleaning up after release...
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 01:28 min
> [INFO] Finished at: 2017-01-08T21:03:18-08:00
> [INFO] Final Memory: 18M/269M
> [INFO] 
> 
>
> thanks,
> chad
>
>
> 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, 

Re: Maintainer request for Amazon EC2 Spot Fleet Plugin

[Chad Schmutzer]

Dear Oleg,

I've finally managed to push the release, but I'm having trouble 
understanding why the update is not showing up in the update center.
Would you mind pointing me in the right direction? Should I create a 
ticket? I hate to bug, but I'm a bit stumped at this point.

[INFO] --- maven-deploy-plugin:2.8.2:deploy (default-deploy) @ 
ec2-fleet ---
Uploading: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2.hpi
Uploaded: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2.hpi
 
(970 KB at 345.6 KB/sec)
Uploading: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2.pom
Uploaded: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2.pom
 
(4 KB at 8.4 KB/sec)
Downloading: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/maven-metadata.xml
Downloaded: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/maven-metadata.xml
 
(396 B at 1.8 KB/sec)
Uploading: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/maven-metadata.xml
Uploaded: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/maven-metadata.xml
 
(369 B at 1.1 KB/sec)
Uploading: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2.jar
Uploaded: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2.jar
 
(27 KB at 68.8 KB/sec)
Uploading: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2-sources.jar
Uploaded: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2-sources.jar
 
(14 KB at 35.1 KB/sec)
Uploading: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2-javadoc.jar
Uploaded: 
https://repo.jenkins-ci.org/releases/com/amazon/jenkins/fleet/ec2-fleet/1.1.2/ec2-fleet-1.1.2-javadoc.jar
 
(80 KB at 169.5 KB/sec)
[INFO] 

[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time: 30.970 s
[INFO] Finished at: 2017-01-08T21:03:17-08:00
[INFO] Final Memory: 66M/849M
[INFO] 

[INFO] Cleaning up after release...
[INFO] 

[INFO] BUILD SUCCESS
[INFO] 

[INFO] Total time: 01:28 min
[INFO] Finished at: 2017-01-08T21:03:18-08:00
[INFO] Final Memory: 18M/269M
[INFO] 


thanks,
chad


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) 

Re: Pipeline steps reference not listing the external workspace manager plugin steps

[Kristin Whetstone]

Hi!

Responding to your questions much later, but the process hasn't changed 
that much since you originally posted.  The pipeline steps reference page 
is generated automatically; it should update frequently and there are 
constant improvements out there for that doc generation right now.  If your 
plugin is relatively new, then it might not have been picked up yet (though 
at this point depending, it should be).  I might need to check on that job 
to make sure it's still going.  It's INCREDIBLY resource intensive 
(basically it creates a Jenkins that knows about every single plugin in the 
Jenkins update center) (you might not want to try that in your own Jenkins 
environment!), and I need to see how it's doing on some of the new 
processes.

You don't need to do anything different with your plugin or add it to a 
list.  Recently, there was an update to make the documentation more 
complete.  So if your step integrated with the workflow-scm plugin (like it 
was a step in that you called it from "step" or "wrap") it'll be added.  
That should get rolled in soon, and the page will be updated shortly after.

Hope this answers your questions!

On Tuesday, September 6, 2016 at 5:14:01 AM UTC-4, Alexandru Somai wrote:
>
> Hello,
>
> Good point Martin.
> For example, I've seen that the *selectRun* step from the Run Selector 
> Plugin  
> is referenced on that list. AFAIK I haven't done anything different on the 
> Run Selector than on the External Workspace Manager.
>
> I wonder how that list is populated. Is it an automatic process? or 
> someone has to add the references somewhere?
>
> Alex
>
> On Tuesday, September 6, 2016 at 1:49:33 AM UTC+3, martinda wrote:
>>
>> Hi,
>>
>> The Pipeline steps reference  is 
>> not listing the steps provided by the External Workspace Manager Plugin 
>> 
>> .
>> Is there something missing in the plugin?
>>
>> 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/c4af4efa-2b0d-4c49-bb1e-4d78beee6181%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

[Irfan Sayed]

Hi Baptiste,
Can you please help

Regards,
Irfan


On Mon, Jan 9, 2017 at 12:08 PM, Irfan Sayed  wrote:

> Hi Baptiste,
> I tried creating settings.xml and try to perform the release. still the
> issue persist.
> Effective POM also looks OK.
>
>  
> 
>   maven.jenkins-ci.org
>   https://repo.jenkins-ci.org/releases/
> 
> 
>   maven.jenkins-ci.org
>   https://repo.jenkins-ci.org/snapshots/
> 
>   
>
> Regards,
> Irfan
>
>
>
> On Sun, Jan 8, 2017 at 12:57 AM, Irfan Sayed  wrote:
>
>> Sorry. while experimenting, that modification left as it is. i fixed that
>> and uploaded new version. please have a look
>> further , please find the attached settings.xml as well
>>
>> Regards,
>>
>>
>> On Sun, Jan 8, 2017 at 2:44 AM, Baptiste Mathus  wrote:
>>
>>> Your current pom.xml is not even valid from a Maven PoV. You commented
>>> out the artifactId
>>> 
>>> for one.
>>> So I don't know what you're testing right now, but no, this is not what
>>> is on your repo because that immediately fails with Maven.
>>>
>>> Please file a PR with what you really have. For me, once this is removed
>>> this seems fine. Or maybe you have crap left somehow in your settings.xml.
>>>
>>> 2017-01-07 17:43 GMT+01:00 Irfan Sayed :
>>>
 Thanks.
 Yes. I did remove the DistributionManagement from my POM.
 Please refer here actual code. This is the latest code which i would
 like to release
 https://github.com/jenkinsci/sinatra-chef-builder-plugin

 Regards,


 On Fri, Jan 6, 2017 at 9:27 PM, Baptiste Mathus  wrote:

> 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/jenkin
>> sci/maven-hpi-plugin/blob/49fc9860c98b23a3690c5110b84aee
>> fed12a/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-F84
>>> D-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/CACGLCJapwky
>> 4ADhy88iiY%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/CANWgJS4q9uP
> 5jz5n_5wnLdDFbX-K37BrgeAzNdPs9mKEWv6umg%40mail.gmail.com
> 

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

[Jesse Glick]

On Sat, Jan 7, 2017 at 10:18 AM, Stephen Connolly
 wrote:
> If you are sending a non-snapshotted credential over remoting

How is that even possible? `Credentials` implementations which have a
corresponding snapshotter override `writeReplace` to make sure
`snapshot` is called before being sent over the wire. 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/CANfRfr0jHxd4WPFWW_YmSFX387a7Np6qnZ%2BoD5TG%2BHoDsPr_Sg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

AW: new version not in update center

[Pönisch , Christian]

Hi,

 

I also have the same problem as Domi.

The new version 1.15 of my ecutest plugin released last Friday is not yet 
available in the Jenkins update center.

 

According to the wiki 

  the new version is listed in the release repo: 
https://repo.jenkins-ci.org/releases/de/tracetronic/jenkins/plugins/ecutest/1.15/

 

Thanks in advance!

Christian

 

Von: jenkinsci-dev@googlegroups.com [mailto:jenkinsci-dev@googlegroups.com] Im 
Auftrag von domi
Gesendet: Montag, 9. Januar 2017 08:49
An: Jenkins Developers
Betreff: new version not in update center

 

Hi,

 

last Friday I made a new realise of the config-file-provider plugin (version 
2.15.3). The release went smooth, but after 3 days, the new version is still 
not visible in the update center :(

 

…but the artefact is available in the repo

https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/config-file-provider/2.15.3/config-file-provider-2.15.3.hpi





has any one any idea whats wrong?

 

thanks Domi

-- 
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/86A03F31-620B-40EB-815B-EF17AAA0092C%40fortysix.ch
 

 .
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/066796B1E3688D44A767F43C874270945C6707E2%40HQ-EX2K10.tracetronic.local.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME cryptographic signature