Re: Not able to release new version of plugin

One question, why are you overriding the hpi plugin version? https://github.com/jenkinsci/sinatra-chef-builder-plugin/blob/master/pom.xml#L15 Also, it looks like the git scm info in the pom.xml is for an old repo link? On Fri, Jan 13, 2017 at 9:29 AM Irfan Sayed wrote: >

Docker-compose plugins

Hi, I am looking for jenkins plugins that run docker-compose commands, specially docker-compose build. I couldn't find any and I am wondering if anyone is building these? Thanks! -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To

Re: Not able to release new version of plugin

Made the changes and committed. command used: mvn release:prepare release:perform still the same issue: "401 unauthorized" regards, On Sat, Jan 14, 2017 at 12:08 AM, Irfan Sayed wrote: > Ok. thanks. > Let me remove below line and commit. > 1.106 > > so you mean, the

Re: Not able to release new version of plugin

Well, the SCM section doesn't match with the repo url: https://github.com/jenkinsci/sinatra-chef-builder-plugin is the repo URL, but the scm section has scm:git:git://github.com/jenkinsci/chefbuilder-plugin.git scm:git:ssh:// g...@github.com/jenkinsci/chefbuilder-plugin.git

Re: Not able to release new version of plugin

Ok. thanks. Let me remove below line and commit. 1.106 so you mean, the curent scm section look OK? should i mention any username and password in the settings.xml? is mvn release:prepare release:perform command is enough? regards, On Fri, Jan 13, 2017 at 11:57 PM, Slide

Re: Not able to release new version of plugin

You shouldn't need to specify an hpi plugin version at all, it will be handled in the parent pom. When I click on the repo you have in your previous email it takes me to a different name. On Fri, Jan 13, 2017, 10:52 Irfan Sayed wrote: > Thanks Slide. > Can you please tell

Re: Not able to release new version of plugin

Thanks Slide. Can you please tell me what should be the hpi plugin version in POM.xml? i will make necessary change and commit. further, git scm info is the same which i kept when i released the initial version. can you please tell me then what should be the correct link? please let me know

Re: Not able to release new version of plugin

>From the same console, can you do something like this: https://help.github.com/articles/testing-your-ssh-connection/ On Fri, Jan 13, 2017 at 12:55 PM Irfan Sayed wrote: made the scm section changes and committed. here is the build output log: ef-builder --- [INFO]

Re: Not able to release new version of plugin

Oh, I missed your message about the typo before I hit send. Are you able to login to https://accounts.jenkins.io/login?from=%2Fmyself%2F with the username/password combo that you have in your settings.xml? On Fri, Jan 13, 2017, 15:17 Slide wrote: > From the same console,

Re: Not able to release new version of plugin

Sure Thanks Let me explain: My current development environment: 1: windows box 2: eclipse MARs release 3: java 1.8 4: maven version: 3.3.9 5: fixed all the findbugs issues plugin details: Chef sinatra jenkins plugin: current version: 1.3 Release process: this is the first time i am uploading

Re: Sending which radioBlock is selected as query param in validate request

Hi All, I also have the exact same question as above. Any help much appreciated. Thanks. Valon On Monday, July 25, 2016 at 3:47:12 PM UTC-6, Jigar Mehta wrote: > > Hi All, > > I have posted a question here, > > >

Re: Not able to release new version of plugin

Further update: I got the Encrypted password of my account and put it in the settings.xml as well. https://repo.jenkins-ci.org/webapp/#/profile here is the snippet from settings.xml: java.net-m2-repository irfanjs $encryptedpassword still it throws the

Re: Maintainer request for the Gatling plugin

Done for GitHub. Welcome! If you want to be allowed to release, please file the associated PR against the permissions repository as usual. Cheers! 2017-01-13 10:41 GMT+01:00 Baptiste Mathus : > Note for later/other request of this type: this kind of answer is clearly > not

Re: Maintainer request for the Gatling plugin

Note for later/other request of this type: this kind of answer is clearly not what we can accept for obvious reasons... I thought that would be obvious at least. Providing provable information (like a confirmation on Github on a PR for example from the maintainer) up front is *much much*

Re: Maintainer request for the Gatling plugin

Hello, I want to be added as a new maintainer, I've contacted the current one. Thanks On Thursday, 12 January 2017 10:28:17 UTC+1, Baptiste Mathus wrote: > > Hello, > > Please follow the process, either this plugin is orphaned (which > apparently is not), or you want to be added as an

Re: Maintainer request for the Gatling plugin

Hey Baptiste, Yes, I'd like to have Cédric help me maintaining our Jenkins plugin. Cheers, Stéphane On Thursday, January 12, 2017 at 10:28:17 AM UTC+1, Baptiste Mathus wrote: > > Hello, > > Please follow the process, either this plugin is orphaned (which > apparently is not), or you want to

Re: Maintainer request for the Gatling plugin

For Cédric's defense, he did it this way because he saw other people doing so on this mailing list. For future reference, the process to be granted commit rights on a plugin seems to be documented here: https://wiki.jenkins-ci.org/display/JENKINS/Adopt+a+Plugin *Stéphane Landelle* *GatlingCorp

Re: Maintainer request for the Gatling plugin

And thanks Baptiste! *Stéphane Landelle* *GatlingCorp CEO* slande...@gatling.io On Fri, Jan 13, 2017 at 12:09 PM, Stéphane LANDELLE wrote: > For Cédric's defense, he did it this way because he saw other people doing > so on this mailing list. > For future reference, the

Repo plugin is up for adoption

I've put the repo plugin up for adoption. I've been babysitting it for a while since the former maintainers left; basically code reviewing, merging pull requests and releasing new versions after merging. And I can continue to do that, but I feel that I'm doing a disservice by doing it since I'm no

Re: Maintainer request for the Gatling plugin

2017-01-13 12:09 GMT+01:00 Stéphane LANDELLE : > For Cédric's defense, he did it this way because he saw other people doing > so on this mailing list. > And did you see us grant permissions blindly :) ? I suspect not... I'd be curious if you find an example of that. For

Re: Maintainer request for the Gatling plugin

Thanks :) On Friday, 13 January 2017 10:46:15 UTC+1, Baptiste Mathus wrote: > > Done for GitHub. Welcome! > > If you want to be allowed to release, please file the associated PR > against the permissions repository as usual. > > Cheers! > > 2017-01-13 10:41 GMT+01:00 Baptiste Mathus

Re: Maintainer request for the Gatling plugin

> On 13.01.2017, at 13:42, Baptiste Mathus wrote: > > Yes and no. There are definitely some similarities, sure, but this is case is > not an adoption IIUC? We should update https://wiki.jenkins-ci.org/display/JENKINS/Pull+Request+to+Repositories -- This unfortunately named

Re: Not able to release new version of plugin

hi, can someone please help. I am stuck totally. regards, On Fri, Jan 13, 2017 at 3:15 PM, Irfan Sayed wrote: > Further update: > I got the Encrypted password of my account and put it in the settings.xml > as well. > https://repo.jenkins-ci.org/webapp/#/profile > > here

Re: Not able to release new version of plugin

This is a pretty long thread, would it be possible for you to sum up where you are currently stuck, what you have tried and so forth? On Fri, Jan 13, 2017 at 8:19 AM Irfan Sayed wrote: > hi, > can someone please help. > I am stuck totally. > > regards, > > > On Fri, Jan