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

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

Re: [Experiment] Reviewers Team

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

Re: Not able to release new version of plugin

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

Re: Not able to release new version of plugin

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. > > > >

Re: Maintainer request for Amazon EC2 Spot Fleet Plugin

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] ---

Re: Maintainer request for Amazon EC2 Spot Fleet Plugin

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

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

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

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

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

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

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

AW: new version not in update center

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

Re: Not able to release new version of plugin

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.