Re: Not able to release new version of plugin

[Slide]

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, 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] Installing
> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>   .hpi to
> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>
> der\1.10\sinatra-chef-builder-1.10.hpi
> [INFO] Installing C:\sinatra-chef-builder-plugin\pom.xml to
> C:\Users\irfanjs
>
> \.m2\repository\org\jenkins-ci\plugins\sinatra-chef-builder\1.10\sinatra-chef-bu
>   ilder-1.10.pom
> [INFO] Installing
> C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
>   .jar to
> C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil
>
> der\1.10\sinatra-chef-builder-1.10.jar
> [INFO]
> -
> ---
> [INFO] BUILD SUCCESS
> [INFO]
> -
> ---
> [INFO] Total time: 02:35 min
> [INFO] Finished at: 2017-01-13T11:36:47-08:00
> [INFO] Final Memory: 62M/167M
> [INFO]
> -
> ---
> [INFO] Checking in modified POMs...
> [INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git rev-parse --show-toplevel"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git status --porcelain ."
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
> [WARNING] Ignoring unrecognized line: ?? release.properties
> [WARNING] Ignoring unrecognized line: ?? target/
> [INFO] Executing: cmd.exe /X /C "git commit --verbose -F
> C:\Users\irfanjs\AppDat
>   a\Local\Temp\maven-scm-1195565814.commit pom.xml"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO] Executing: cmd.exe /X /C "git push
> g...@github.com/jenkinsci/sinatra-chef-
> builder-plugin.git
> refs/heads/master:refs/heads/master"
> [INFO] Working directory: C:\sinatra-chef-builder-plugin
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 03:37 min
> [INFO] Finished at: 2017-01-13T11:36:48-08:00
> [INFO] Final Memory: 16M/39M
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.5
> .3:prepare (default-cli) on project
> sinatra-chef-builder: Unable to commit files
> [ERROR] Provider message:
> [ERROR] The git-push command failed.
> [ERROR] Command output:
> [ERROR] fatal: 'g...@github.com/jenkinsci/sinatra-chef-builder-plugin.git'
> does n   ot
> appear to be a git repository
> [ERROR] fatal: Could not read from remote repository.
> [ERROR]
> [ERROR] Please make sure you have the correct access rights
> [ERROR] and the repository exists.
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e swit   ch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please rea   d
> the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
> eption
>
> irfanjs@host-10 MINGW64 /c/sinatra-chef-builder-plugin (master)
> $
>
> regards,
>
>
> On Fri, Jan 13, 2017 at 11:10 AM, Slide  wrote:
>
> 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 

Re: Not able to release new version of plugin

[Slide]

>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] Installing
C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
  .hpi to
C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil

der\1.10\sinatra-chef-builder-1.10.hpi
[INFO] Installing C:\sinatra-chef-builder-plugin\pom.xml to
C:\Users\irfanjs

\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-builder\1.10\sinatra-chef-bu
  ilder-1.10.pom
[INFO] Installing
C:\sinatra-chef-builder-plugin\target\sinatra-chef-builder
  .jar to
C:\Users\irfanjs\.m2\repository\org\jenkins-ci\plugins\sinatra-chef-buil

der\1.10\sinatra-chef-builder-1.10.jar
[INFO]
-
---
[INFO] BUILD SUCCESS
[INFO]
-
---
[INFO] Total time: 02:35 min
[INFO] Finished at: 2017-01-13T11:36:47-08:00
[INFO] Final Memory: 62M/167M
[INFO]
-
---
[INFO] Checking in modified POMs...
[INFO] Executing: cmd.exe /X /C "git add -- pom.xml"
[INFO] Working directory: C:\sinatra-chef-builder-plugin
[INFO] Executing: cmd.exe /X /C "git rev-parse --show-toplevel"
[INFO] Working directory: C:\sinatra-chef-builder-plugin
[INFO] Executing: cmd.exe /X /C "git status --porcelain ."
[INFO] Working directory: C:\sinatra-chef-builder-plugin
[WARNING] Ignoring unrecognized line: ?? pom.xml.releaseBackup
[WARNING] Ignoring unrecognized line: ?? release.properties
[WARNING] Ignoring unrecognized line: ?? target/
[INFO] Executing: cmd.exe /X /C "git commit --verbose -F
C:\Users\irfanjs\AppDat
  a\Local\Temp\maven-scm-1195565814.commit pom.xml"
[INFO] Working directory: C:\sinatra-chef-builder-plugin
[INFO] Executing: cmd.exe /X /C "git symbolic-ref HEAD"
[INFO] Working directory: C:\sinatra-chef-builder-plugin
[INFO] Executing: cmd.exe /X /C "git push
g...@github.com/jenkinsci/sinatra-chef-
  builder-plugin.git
refs/heads/master:refs/heads/master"
[INFO] Working directory: C:\sinatra-chef-builder-plugin
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 03:37 min
[INFO] Finished at: 2017-01-13T11:36:48-08:00
[INFO] Final Memory: 16M/39M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.5
.3:prepare (default-cli) on project
sinatra-chef-builder: Unable to commit files
[ERROR] Provider message:
[ERROR] The git-push command failed.
[ERROR] Command output:
[ERROR] fatal: 'g...@github.com/jenkinsci/sinatra-chef-builder-plugin.git'
does n   ot
appear to be a git repository
[ERROR] fatal: Could not read from remote repository.
[ERROR]
[ERROR] Please make sure you have the correct access rights
[ERROR] and the repository exists.
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
swit   ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please rea   d
the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
  eption

irfanjs@host-10 MINGW64 /c/sinatra-chef-builder-plugin (master)
$

regards,


On Fri, Jan 13, 2017 at 11:10 AM, Slide  wrote:

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
http://github.com/jenkinsci/chefbuilder-plugin
HEAD

The URL's clearly don't match.


The SCM section for the token-macro-plugin that I maintain is like this:


scm:git:git://github.com/jenkinsci/token-macro-plugin.git
scm:git:g...@github.com:
jenkinsci/token-macro-plugin.git
HEAD

Can you post a build log of the current runs after the changes?

Docker-compose plugins

[pragya . mehta15]

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 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/1c64ddf6-6aa2-4d1b-bc5c-e29691e584c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

[Slide]

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
http://github.com/jenkinsci/chefbuilder-plugin
HEAD

The URL's clearly don't match.


The SCM section for the token-macro-plugin that I maintain is like this:


scm:git:git://github.com/jenkinsci/token-macro-plugin.git
scm:git:g...@github.com:
jenkinsci/token-macro-plugin.git
HEAD

Can you post a build log of the current runs after the changes?

On Fri, Jan 13, 2017 at 11:38 AM Irfan Sayed  wrote:

> 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  wrote:
>
> 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 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
> Regards,
>
>
> On Fri, Jan 13, 2017 at 11:16 PM, Slide  wrote:
>
> 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:
>
> 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 the new version of my plugin
> Installed git bash
> my github account and jenkins account is same
> created the public/private key pair
> uploaded the public key to the github.
> settings.xml is taken from the link:
> https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial
>
> troubleshooting steps i did:
> i followed most instruction in the URL:
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
>
> 1: hard-coded username and password in the settings section in
> settings.xml
> 2: pass the username/password in the mvn release command
> 3: able to push the latest changes in the github without asking for
> password
> 4: run the command mvn help:effective-settings to get the effective
> settings to check the distributionManagement tag. it seems OK
> 5: my plugin POM is updated with Jenkins parent plugin POM :
> https://github.com/jenkinsci/plugin-pom
> 6: effective POM is also seems OK
> 7:get the encrypted password from the repo.jenkins-ci.org and paste in
> the settings.xml instead of plain text password.
> 8: created the PR request for the review
> 9: followed the instruction in the :
> https://github.com/jenkins-infra/repository-permissions-updater
>
> actual commands :
> git clone https://github.com/jenkinsci/sinatra-chef-builder-plugin.git
> git add pom.xml src
> git commit -m "new version"
> git push origin master
>
> final release command:
> mvn release:prepare release:perform
>
> i am getting "401 unauthorized error"
> please suggest
>
> Regards,
>
>
>
>
>
>
> On Fri, Jan 13, 2017 at 9:16 PM, Slide  wrote:
>
> 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 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 is the snippet from settings.xml:
>
> 
> 
>   java.net-m2-repository 
>   irfanjs
>   $encryptedpassword
> 
>   
>
> still it throws the unauthorized error.
> can someone please provide me the access to release plugin ?
> regards,
>
>
>
>
> On Thu, Jan 12, 2017 at 11:25 PM, Irfan Sayed 
> wrote:
>
> As i am troubleshooting further, just wanted to confirm, if my ID :
> "irfanjs" has valid deploy artifact/release plugin permission to jenkins-ci
> org?
> Hi Baptiste/Daniel,
> Can i Request you to please have a 

Re: Not able to release new version of plugin

[Irfan Sayed]

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 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  wrote:
>
>> 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 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
>>> Regards,
>>>
>>>
>>> On Fri, Jan 13, 2017 at 11:16 PM, Slide  wrote:
>>>
>>> One question, why are you overriding the hpi plugin version?
>>> https://github.com/jenkinsci/sinatra-chef-builder-plugin/blo
>>> b/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:
>>>
>>> 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 the new version of my plugin
>>> Installed git bash
>>> my github account and jenkins account is same
>>> created the public/private key pair
>>> uploaded the public key to the github.
>>> settings.xml is taken from the link: https://wiki.jenkins-ci.
>>> org/display/JENKINS/Plugin+tutorial
>>>
>>> troubleshooting steps i did:
>>> i followed most instruction in the URL: https://wiki.jenkins-ci.org/di
>>> splay/JENKINS/Hosting+Plugins
>>>
>>> 1: hard-coded username and password in the settings section in
>>> settings.xml
>>> 2: pass the username/password in the mvn release command
>>> 3: able to push the latest changes in the github without asking for
>>> password
>>> 4: run the command mvn help:effective-settings to get the effective
>>> settings to check the distributionManagement tag. it seems OK
>>> 5: my plugin POM is updated with Jenkins parent plugin POM :
>>> https://github.com/jenkinsci/plugin-pom
>>> 6: effective POM is also seems OK
>>> 7:get the encrypted password from the repo.jenkins-ci.org and paste in
>>> the settings.xml instead of plain text password.
>>> 8: created the PR request for the review
>>> 9: followed the instruction in the : https://github.com/jenkins-i
>>> nfra/repository-permissions-updater
>>>
>>> actual commands :
>>> git clone https://github.com/jenkinsci/sinatra-chef-builder-plugin.git
>>> git add pom.xml src
>>> git commit -m "new version"
>>> git push origin master
>>>
>>> final release command:
>>> mvn release:prepare release:perform
>>>
>>> i am getting "401 unauthorized error"
>>> please suggest
>>>
>>> Regards,
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Jan 13, 2017 at 9:16 PM, Slide  wrote:
>>>
>>> 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 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 is the snippet from settings.xml:
>>>
>>> 
>>> 
>>>   java.net-m2-repository 
>>>   irfanjs
>>>   $encryptedpassword
>>> 
>>>   
>>>
>>> still it throws the unauthorized error.
>>> can someone please provide me the access to release plugin ?
>>> regards,
>>>
>>>
>>>
>>>
>>> On Thu, Jan 12, 2017 at 11:25 PM, Irfan Sayed 
>>> wrote:
>>>
>>> As i am troubleshooting further, just wanted to confirm, if my ID :
>>> "irfanjs" has valid deploy artifact/release plugin permission to jenkins-ci
>>> org?
>>> Hi Baptiste/Daniel,
>>> Can i Request you to please have a look on the same.
>>>
>>> Regards,
>>>
>>>
>>> On Thu, Jan 12, 2017 at 11:15 PM, Irfan Sayed 
>>> wrote:
>>>
>>> further update:
>>> i started ssh-agent and imported the private key 

Re: Not able to release new version of plugin

[Irfan Sayed]

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  wrote:

> 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 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
>> Regards,
>>
>>
>> On Fri, Jan 13, 2017 at 11:16 PM, Slide  wrote:
>>
>> 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:
>>
>> 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 the new version of my plugin
>> Installed git bash
>> my github account and jenkins account is same
>> created the public/private key pair
>> uploaded the public key to the github.
>> settings.xml is taken from the link: https://wiki.jenkins-ci.
>> org/display/JENKINS/Plugin+tutorial
>>
>> troubleshooting steps i did:
>> i followed most instruction in the URL: https://wiki.jenkins-ci.org/
>> display/JENKINS/Hosting+Plugins
>>
>> 1: hard-coded username and password in the settings section in
>> settings.xml
>> 2: pass the username/password in the mvn release command
>> 3: able to push the latest changes in the github without asking for
>> password
>> 4: run the command mvn help:effective-settings to get the effective
>> settings to check the distributionManagement tag. it seems OK
>> 5: my plugin POM is updated with Jenkins parent plugin POM :
>> https://github.com/jenkinsci/plugin-pom
>> 6: effective POM is also seems OK
>> 7:get the encrypted password from the repo.jenkins-ci.org and paste in
>> the settings.xml instead of plain text password.
>> 8: created the PR request for the review
>> 9: followed the instruction in the : https://github.com/jenkins-
>> infra/repository-permissions-updater
>>
>> actual commands :
>> git clone https://github.com/jenkinsci/sinatra-chef-builder-plugin.git
>> git add pom.xml src
>> git commit -m "new version"
>> git push origin master
>>
>> final release command:
>> mvn release:prepare release:perform
>>
>> i am getting "401 unauthorized error"
>> please suggest
>>
>> Regards,
>>
>>
>>
>>
>>
>>
>> On Fri, Jan 13, 2017 at 9:16 PM, Slide  wrote:
>>
>> 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 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 is the snippet from settings.xml:
>>
>> 
>> 
>>   java.net-m2-repository 
>>   irfanjs
>>   $encryptedpassword
>> 
>>   
>>
>> still it throws the unauthorized error.
>> can someone please provide me the access to release plugin ?
>> regards,
>>
>>
>>
>>
>> On Thu, Jan 12, 2017 at 11:25 PM, Irfan Sayed 
>> wrote:
>>
>> As i am troubleshooting further, just wanted to confirm, if my ID :
>> "irfanjs" has valid deploy artifact/release plugin permission to jenkins-ci
>> org?
>> Hi Baptiste/Daniel,
>> Can i Request you to please have a look on the same.
>>
>> Regards,
>>
>>
>> On Thu, Jan 12, 2017 at 11:15 PM, Irfan Sayed 
>> wrote:
>>
>> further update:
>> i started ssh-agent and imported the private key of the github account.
>> my github account and jenkins-ci account is same.
>> aftrer that, added username and password in the ~/.m2/settings.xml file
>> and run the command:
>> "mvn release:prepare release:perform"
>>
>> still the same issue : "401 unauthorized"
>>
>> Regards,
>>
>>
>> On Thu, Jan 12, 2017 at 6:47 PM, Irfan Sayed 
>> wrote:
>>
>> Hi,
>> Please 

Re: Not able to release new version of plugin

[Slide]

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 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
> Regards,
>
>
> On Fri, Jan 13, 2017 at 11:16 PM, Slide  wrote:
>
> 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:
>
> 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 the new version of my plugin
> Installed git bash
> my github account and jenkins account is same
> created the public/private key pair
> uploaded the public key to the github.
> settings.xml is taken from the link:
> https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial
>
> troubleshooting steps i did:
> i followed most instruction in the URL:
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
>
> 1: hard-coded username and password in the settings section in
> settings.xml
> 2: pass the username/password in the mvn release command
> 3: able to push the latest changes in the github without asking for
> password
> 4: run the command mvn help:effective-settings to get the effective
> settings to check the distributionManagement tag. it seems OK
> 5: my plugin POM is updated with Jenkins parent plugin POM :
> https://github.com/jenkinsci/plugin-pom
> 6: effective POM is also seems OK
> 7:get the encrypted password from the repo.jenkins-ci.org and paste in
> the settings.xml instead of plain text password.
> 8: created the PR request for the review
> 9: followed the instruction in the :
> https://github.com/jenkins-infra/repository-permissions-updater
>
> actual commands :
> git clone https://github.com/jenkinsci/sinatra-chef-builder-plugin.git
> git add pom.xml src
> git commit -m "new version"
> git push origin master
>
> final release command:
> mvn release:prepare release:perform
>
> i am getting "401 unauthorized error"
> please suggest
>
> Regards,
>
>
>
>
>
>
> On Fri, Jan 13, 2017 at 9:16 PM, Slide  wrote:
>
> 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 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 is the snippet from settings.xml:
>
> 
> 
>   java.net-m2-repository 
>   irfanjs
>   $encryptedpassword
> 
>   
>
> still it throws the unauthorized error.
> can someone please provide me the access to release plugin ?
> regards,
>
>
>
>
> On Thu, Jan 12, 2017 at 11:25 PM, Irfan Sayed 
> wrote:
>
> As i am troubleshooting further, just wanted to confirm, if my ID :
> "irfanjs" has valid deploy artifact/release plugin permission to jenkins-ci
> org?
> Hi Baptiste/Daniel,
> Can i Request you to please have a look on the same.
>
> Regards,
>
>
> On Thu, Jan 12, 2017 at 11:15 PM, Irfan Sayed 
> wrote:
>
> further update:
> i started ssh-agent and imported the private key of the github account. my
> github account and jenkins-ci account is same.
> aftrer that, added username and password in the ~/.m2/settings.xml file
> and run the command:
> "mvn release:prepare release:perform"
>
> still the same issue : "401 unauthorized"
>
> Regards,
>
>
> On Thu, Jan 12, 2017 at 6:47 PM, Irfan Sayed  wrote:
>
> Hi,
> Please suggest...
> i tried passing username and password as well in the maven release command
> but no luck
>
> Regards,
>
>
> On Thu, Jan 12, 2017 at 12:47 PM, Irfan Sayed 
> wrote:
>
> Hi,
> I have created the PR request :
> https://github.com/irfanjs/chefbuilder/pull/1
>
> Can you please review the same ?
> i made changes directly into master branch. so i guess no need to merge
> anything.
>
> I understand that i dont have plugin release upload permission.
>
> i 

Re: Not able to release new version of plugin

[Irfan Sayed]

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
Regards,


On Fri, Jan 13, 2017 at 11:16 PM, Slide  wrote:

> 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:
>
>> 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 the new version of my plugin
>> Installed git bash
>> my github account and jenkins account is same
>> created the public/private key pair
>> uploaded the public key to the github.
>> settings.xml is taken from the link: https://wiki.jenkins-ci.
>> org/display/JENKINS/Plugin+tutorial
>>
>> troubleshooting steps i did:
>> i followed most instruction in the URL: https://wiki.jenkins-ci.org/
>> display/JENKINS/Hosting+Plugins
>>
>> 1: hard-coded username and password in the settings section in
>> settings.xml
>> 2: pass the username/password in the mvn release command
>> 3: able to push the latest changes in the github without asking for
>> password
>> 4: run the command mvn help:effective-settings to get the effective
>> settings to check the distributionManagement tag. it seems OK
>> 5: my plugin POM is updated with Jenkins parent plugin POM :
>> https://github.com/jenkinsci/plugin-pom
>> 6: effective POM is also seems OK
>> 7:get the encrypted password from the repo.jenkins-ci.org and paste in
>> the settings.xml instead of plain text password.
>> 8: created the PR request for the review
>> 9: followed the instruction in the : https://github.com/jenkins-
>> infra/repository-permissions-updater
>>
>> actual commands :
>> git clone https://github.com/jenkinsci/sinatra-chef-builder-plugin.git
>> git add pom.xml src
>> git commit -m "new version"
>> git push origin master
>>
>> final release command:
>> mvn release:prepare release:perform
>>
>> i am getting "401 unauthorized error"
>> please suggest
>>
>> Regards,
>>
>>
>>
>>
>>
>>
>> On Fri, Jan 13, 2017 at 9:16 PM, Slide  wrote:
>>
>> 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 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 is the snippet from settings.xml:
>>
>> 
>> 
>>   java.net-m2-repository 
>>   irfanjs
>>   $encryptedpassword
>> 
>>   
>>
>> still it throws the unauthorized error.
>> can someone please provide me the access to release plugin ?
>> regards,
>>
>>
>>
>>
>> On Thu, Jan 12, 2017 at 11:25 PM, Irfan Sayed 
>> wrote:
>>
>> As i am troubleshooting further, just wanted to confirm, if my ID :
>> "irfanjs" has valid deploy artifact/release plugin permission to jenkins-ci
>> org?
>> Hi Baptiste/Daniel,
>> Can i Request you to please have a look on the same.
>>
>> Regards,
>>
>>
>> On Thu, Jan 12, 2017 at 11:15 PM, Irfan Sayed 
>> wrote:
>>
>> further update:
>> i started ssh-agent and imported the private key of the github account.
>> my github account and jenkins-ci account is same.
>> aftrer that, added username and password in the ~/.m2/settings.xml file
>> and run the command:
>> "mvn release:prepare release:perform"
>>
>> still the same issue : "401 unauthorized"
>>
>> Regards,
>>
>>
>> On Thu, Jan 12, 2017 at 6:47 PM, Irfan Sayed 
>> wrote:
>>
>> Hi,
>> Please suggest...
>> i tried passing username and password as well in the maven release
>> command but no luck
>>
>> Regards,
>>
>>
>> On Thu, Jan 12, 2017 at 12:47 PM, Irfan Sayed 
>> wrote:
>>
>> Hi,
>> I have created the PR request :
>> https://github.com/irfanjs/chefbuilder/pull/1
>>
>> Can you please review the same ?
>> i made changes directly into master branch. so i guess no need to merge
>> anything.
>>
>> I understand that i dont have plugin release upload permission.
>>
>> i followed the below link:
>> https://github.com/jenkins-infra/repository-permissions-updater
>>
>> and verified that YAML 

Re: Not able to release new version of plugin

[Slide]

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:

> 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 the new version of my plugin
> Installed git bash
> my github account and jenkins account is same
> created the public/private key pair
> uploaded the public key to the github.
> settings.xml is taken from the link:
> https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial
>
> troubleshooting steps i did:
> i followed most instruction in the URL:
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins
>
> 1: hard-coded username and password in the settings section in
> settings.xml
> 2: pass the username/password in the mvn release command
> 3: able to push the latest changes in the github without asking for
> password
> 4: run the command mvn help:effective-settings to get the effective
> settings to check the distributionManagement tag. it seems OK
> 5: my plugin POM is updated with Jenkins parent plugin POM :
> https://github.com/jenkinsci/plugin-pom
> 6: effective POM is also seems OK
> 7:get the encrypted password from the repo.jenkins-ci.org and paste in
> the settings.xml instead of plain text password.
> 8: created the PR request for the review
> 9: followed the instruction in the :
> https://github.com/jenkins-infra/repository-permissions-updater
>
> actual commands :
> git clone https://github.com/jenkinsci/sinatra-chef-builder-plugin.git
> git add pom.xml src
> git commit -m "new version"
> git push origin master
>
> final release command:
> mvn release:prepare release:perform
>
> i am getting "401 unauthorized error"
> please suggest
>
> Regards,
>
>
>
>
>
>
> On Fri, Jan 13, 2017 at 9:16 PM, Slide  wrote:
>
> 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 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 is the snippet from settings.xml:
>
> 
> 
>   java.net-m2-repository 
>   irfanjs
>   $encryptedpassword
> 
>   
>
> still it throws the unauthorized error.
> can someone please provide me the access to release plugin ?
> regards,
>
>
>
>
> On Thu, Jan 12, 2017 at 11:25 PM, Irfan Sayed 
> wrote:
>
> As i am troubleshooting further, just wanted to confirm, if my ID :
> "irfanjs" has valid deploy artifact/release plugin permission to jenkins-ci
> org?
> Hi Baptiste/Daniel,
> Can i Request you to please have a look on the same.
>
> Regards,
>
>
> On Thu, Jan 12, 2017 at 11:15 PM, Irfan Sayed 
> wrote:
>
> further update:
> i started ssh-agent and imported the private key of the github account. my
> github account and jenkins-ci account is same.
> aftrer that, added username and password in the ~/.m2/settings.xml file
> and run the command:
> "mvn release:prepare release:perform"
>
> still the same issue : "401 unauthorized"
>
> Regards,
>
>
> On Thu, Jan 12, 2017 at 6:47 PM, Irfan Sayed  wrote:
>
> Hi,
> Please suggest...
> i tried passing username and password as well in the maven release command
> but no luck
>
> Regards,
>
>
> On Thu, Jan 12, 2017 at 12:47 PM, Irfan Sayed 
> wrote:
>
> Hi,
> I have created the PR request :
> https://github.com/irfanjs/chefbuilder/pull/1
>
> Can you please review the same ?
> i made changes directly into master branch. so i guess no need to merge
> anything.
>
> I understand that i dont have plugin release upload permission.
>
> i followed the below link:
> https://github.com/jenkins-infra/repository-permissions-updater
>
> and verified that YAML file exist for my plugin with correct content.
> please let me know if i need to request anything more so that i can upload
> new release
>
> Regards,
>
>
> On Wed, Jan 11, 2017 at 8:56 AM, Irfan Sayed  wrote:
>
> Thanks.
> Let me thoroughly have a look and update
>
> Regards,
>
>
> On Wed, Jan 11, 2017 at 10:07 PM, Daniel Beck  wrote:
>
>
> > On 11.01.2017, at 17:34, Irfan Sayed  wrote:
> >
> > not getting why "unauthorized" error is coming
>
> Have you looked into all of the 

Re: Not able to release new version of plugin

[Irfan Sayed]

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 the new version of my plugin
Installed git bash
my github account and jenkins account is same
created the public/private key pair
uploaded the public key to the github.
settings.xml is taken from the link:
https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial

troubleshooting steps i did:
i followed most instruction in the URL:
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins

1: hard-coded username and password in the settings section in settings.xml
2: pass the username/password in the mvn release command
3: able to push the latest changes in the github without asking for password
4: run the command mvn help:effective-settings to get the effective
settings to check the distributionManagement tag. it seems OK
5: my plugin POM is updated with Jenkins parent plugin POM :
https://github.com/jenkinsci/plugin-pom
6: effective POM is also seems OK
7:get the encrypted password from the repo.jenkins-ci.org and paste in the
settings.xml instead of plain text password.
8: created the PR request for the review
9: followed the instruction in the :
https://github.com/jenkins-infra/repository-permissions-updater

actual commands :
git clone https://github.com/jenkinsci/sinatra-chef-builder-plugin.git
git add pom.xml src
git commit -m "new version"
git push origin master

final release command:
mvn release:prepare release:perform

i am getting "401 unauthorized error"
please suggest

Regards,






On Fri, Jan 13, 2017 at 9:16 PM, Slide  wrote:

> 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 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 is the snippet from settings.xml:
>>
>> 
>> 
>>   java.net-m2-repository 
>>   irfanjs
>>   $encryptedpassword
>> 
>>   
>>
>> still it throws the unauthorized error.
>> can someone please provide me the access to release plugin ?
>> regards,
>>
>>
>>
>>
>> On Thu, Jan 12, 2017 at 11:25 PM, Irfan Sayed 
>> wrote:
>>
>> As i am troubleshooting further, just wanted to confirm, if my ID :
>> "irfanjs" has valid deploy artifact/release plugin permission to jenkins-ci
>> org?
>> Hi Baptiste/Daniel,
>> Can i Request you to please have a look on the same.
>>
>> Regards,
>>
>>
>> On Thu, Jan 12, 2017 at 11:15 PM, Irfan Sayed 
>> wrote:
>>
>> further update:
>> i started ssh-agent and imported the private key of the github account.
>> my github account and jenkins-ci account is same.
>> aftrer that, added username and password in the ~/.m2/settings.xml file
>> and run the command:
>> "mvn release:prepare release:perform"
>>
>> still the same issue : "401 unauthorized"
>>
>> Regards,
>>
>>
>> On Thu, Jan 12, 2017 at 6:47 PM, Irfan Sayed 
>> wrote:
>>
>> Hi,
>> Please suggest...
>> i tried passing username and password as well in the maven release
>> command but no luck
>>
>> Regards,
>>
>>
>> On Thu, Jan 12, 2017 at 12:47 PM, Irfan Sayed 
>> wrote:
>>
>> Hi,
>> I have created the PR request :
>> https://github.com/irfanjs/chefbuilder/pull/1
>>
>> Can you please review the same ?
>> i made changes directly into master branch. so i guess no need to merge
>> anything.
>>
>> I understand that i dont have plugin release upload permission.
>>
>> i followed the below link:
>> https://github.com/jenkins-infra/repository-permissions-updater
>>
>> and verified that YAML file exist for my plugin with correct content.
>> please let me know if i need to request anything more so that i can
>> upload new release
>>
>> Regards,
>>
>>
>> On Wed, Jan 11, 2017 at 8:56 AM, Irfan Sayed 
>> wrote:
>>
>> Thanks.
>> Let me thoroughly have a look and update
>>
>> Regards,
>>
>>
>> On Wed, Jan 11, 2017 at 10:07 PM, Daniel Beck  wrote:
>>
>>
>> > On 11.01.2017, at 17:34, Irfan Sayed  wrote:
>> >
>> > not getting why "unauthorized" error is coming
>>
>> Have you looked into all of the suggestions in the 12th note at
>> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+
>> Plugins#HostingPlugins-Workingaroundcommonissues ?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop 

Re: Not able to release new version of plugin

[Slide]

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 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 is the snippet from settings.xml:
>
> 
> 
>   java.net-m2-repository 
>   irfanjs
>   $encryptedpassword
> 
>   
>
> still it throws the unauthorized error.
> can someone please provide me the access to release plugin ?
> regards,
>
>
>
>
> On Thu, Jan 12, 2017 at 11:25 PM, Irfan Sayed 
> wrote:
>
> As i am troubleshooting further, just wanted to confirm, if my ID :
> "irfanjs" has valid deploy artifact/release plugin permission to jenkins-ci
> org?
> Hi Baptiste/Daniel,
> Can i Request you to please have a look on the same.
>
> Regards,
>
>
> On Thu, Jan 12, 2017 at 11:15 PM, Irfan Sayed 
> wrote:
>
> further update:
> i started ssh-agent and imported the private key of the github account. my
> github account and jenkins-ci account is same.
> aftrer that, added username and password in the ~/.m2/settings.xml file
> and run the command:
> "mvn release:prepare release:perform"
>
> still the same issue : "401 unauthorized"
>
> Regards,
>
>
> On Thu, Jan 12, 2017 at 6:47 PM, Irfan Sayed  wrote:
>
> Hi,
> Please suggest...
> i tried passing username and password as well in the maven release command
> but no luck
>
> Regards,
>
>
> On Thu, Jan 12, 2017 at 12:47 PM, Irfan Sayed 
> wrote:
>
> Hi,
> I have created the PR request :
> https://github.com/irfanjs/chefbuilder/pull/1
>
> Can you please review the same ?
> i made changes directly into master branch. so i guess no need to merge
> anything.
>
> I understand that i dont have plugin release upload permission.
>
> i followed the below link:
> https://github.com/jenkins-infra/repository-permissions-updater
>
> and verified that YAML file exist for my plugin with correct content.
> please let me know if i need to request anything more so that i can upload
> new release
>
> Regards,
>
>
> On Wed, Jan 11, 2017 at 8:56 AM, Irfan Sayed  wrote:
>
> Thanks.
> Let me thoroughly have a look and update
>
> Regards,
>
>
> On Wed, Jan 11, 2017 at 10:07 PM, Daniel Beck  wrote:
>
>
> > On 11.01.2017, at 17:34, Irfan Sayed  wrote:
> >
> > not getting why "unauthorized" error is coming
>
> Have you looked into all of the suggestions in the 12th note at
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues
> ?
>
> --
> 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/7956E78F-980D-44AE-BDCF-D3509E827702%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/CACGLCJb-iR9LRoDpCGcwACSakU-MMkOrX5QpQGpe-9uUkAQBpQ%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/CAPiUgVf5NzjAnMDxVgwFRSxrqn8oTtcxTiLMhcr5rXfEzLtnNQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

[Irfan Sayed]

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 is the snippet from settings.xml:
>
> 
> 
>   java.net-m2-repository 
>   irfanjs
>   $encryptedpassword
> 
>   
>
> still it throws the unauthorized error.
> can someone please provide me the access to release plugin ?
> regards,
>
>
>
>
> On Thu, Jan 12, 2017 at 11:25 PM, Irfan Sayed 
> wrote:
>
>> As i am troubleshooting further, just wanted to confirm, if my ID :
>> "irfanjs" has valid deploy artifact/release plugin permission to jenkins-ci
>> org?
>> Hi Baptiste/Daniel,
>> Can i Request you to please have a look on the same.
>>
>> Regards,
>>
>>
>> On Thu, Jan 12, 2017 at 11:15 PM, Irfan Sayed 
>> wrote:
>>
>>> further update:
>>> i started ssh-agent and imported the private key of the github account.
>>> my github account and jenkins-ci account is same.
>>> aftrer that, added username and password in the ~/.m2/settings.xml file
>>> and run the command:
>>> "mvn release:prepare release:perform"
>>>
>>> still the same issue : "401 unauthorized"
>>>
>>> Regards,
>>>
>>>
>>> On Thu, Jan 12, 2017 at 6:47 PM, Irfan Sayed 
>>> wrote:
>>>
 Hi,
 Please suggest...
 i tried passing username and password as well in the maven release
 command but no luck

 Regards,


 On Thu, Jan 12, 2017 at 12:47 PM, Irfan Sayed 
 wrote:

> Hi,
> I have created the PR request :
> https://github.com/irfanjs/chefbuilder/pull/1
>
> Can you please review the same ?
> i made changes directly into master branch. so i guess no need to
> merge anything.
>
> I understand that i dont have plugin release upload permission.
>
> i followed the below link:
> https://github.com/jenkins-infra/repository-permissions-updater
>
> and verified that YAML file exist for my plugin with correct content.
> please let me know if i need to request anything more so that i can
> upload new release
>
> Regards,
>
>
> On Wed, Jan 11, 2017 at 8:56 AM, Irfan Sayed 
> wrote:
>
>> Thanks.
>> Let me thoroughly have a look and update
>>
>> Regards,
>>
>>
>> On Wed, Jan 11, 2017 at 10:07 PM, Daniel Beck  wrote:
>>
>>>
>>> > On 11.01.2017, at 17:34, Irfan Sayed  wrote:
>>> >
>>> > not getting why "unauthorized" error is coming
>>>
>>> Have you looked into all of the suggestions in the 12th note at
>>> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#
>>> HostingPlugins-Workingaroundcommonissues ?
>>>
>>> --
>>> 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/7956E78F-980
>>> D-44AE-BDCF-D3509E827702%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/CACGLCJb-iR9LRoDpCGcwACSakU-MMkOrX5QpQGpe-9uUkAQBpQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

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

[vsejdini]

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,
>
>
> http://stackoverflow.com/questions/38491324/what-need-to-be-passed-as-query-param-for-jenkins-jelly-fradioblock
>
> Basically, I need to have my Java Validate function to know which radio 
> block is selected. 
>
> Any help will be greatly appreciated.
>
> Thanks
> Jigar
>

-- 
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/d1c1221f-6053-424d-bb5e-815c2016cbd3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maintainer request for the Gatling plugin

[Cédric Cousseran]

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 
> :
>
>> 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* appreciated, and show 
>> a respect for other people's time. 
>> Having to two many roundtrips here for this is probably not enjoyable for 
>> anyone.
>>
>> The answer from Stéphane below is.
>>
>> Thanks
>>
>> 2017-01-13 9:58 GMT+01:00 Cédric Cousseran > >:
>>
>>> 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 additional maintainer, 
 then we need heads-up from an existing maintainer. I guess it's an obvious 
 default, anyway, isn't it?

 We can all save time if people provide more context in general for 
 those kinds of requests, thank you!

 2017-01-11 11:25 GMT+01:00 Cédric Cousseran :

> Hi,
>
> I want to be a maintainer of the Gatling Plugin: 
> https://github.com/jenkinsci/gatling-plugin
>
> GitHub ID: ccedric
> Jenkins ID: ccousseran
>
> Regards,
> Cédric Cousseran
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-dev/6552611c-3b4d-47b9-ad66-228781ec6566%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-de...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-dev/d73e1ad0-3203-421c-a05f-1b91ed2ae8b7%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/c738c15b-922c-47d0-b1ad-bc92cd46e387%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maintainer request for the Gatling plugin

[Daniel Beck]

> 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 wiki page is linked by the bot addressing how to 
proceed if there's no response.


-- 
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/7440B106-317F-46B9-8E5A-452F1B897532%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Maintainer request for the Gatling plugin

[Baptiste Mathus]

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 many of those, we quite unfortunately generally have to spend quite
some time asking for various proofs and so on.
And I hope you'll agree that time could be spent on more interesting
matters :-).

I won't deny the docs are generally a bit fluffy, but well, again, it seems
to me providing some context upfront is expected for any request to be
processed efficiently, anywhere.



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

Yes and no. There are definitely some similarities, sure, but this is case
is not an adoption IIUC?


> *Stéphane Landelle*
> *GatlingCorp CEO*
> slande...@gatling.io
>
>
> On Fri, Jan 13, 2017 at 10:45 AM, 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 :
>>
>>> 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* appreciated, and
>>> show a respect for other people's time.
>>> Having to two many roundtrips here for this is probably not enjoyable
>>> for anyone.
>>>
>>> The answer from Stéphane below is.
>>>
>>> Thanks
>>>
>>> 2017-01-13 9:58 GMT+01:00 Cédric Cousseran :
>>>
 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 additional maintainer,
> then we need heads-up from an existing maintainer. I guess it's an obvious
> default, anyway, isn't it?
>
> We can all save time if people provide more context in general for
> those kinds of requests, thank you!
>
> 2017-01-11 11:25 GMT+01:00 Cédric Cousseran :
>
>> Hi,
>>
>> I want to be a maintainer of the Gatling Plugin:
>> https://github.com/jenkinsci/gatling-plugin
>>
>> GitHub ID: ccedric
>> Jenkins ID: ccousseran
>>
>> Regards,
>> Cédric Cousseran
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to jenkinsci-de...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/6552611c-3b4
>> d-47b9-ad66-228781ec6566%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/ms
 gid/jenkinsci-dev/d73e1ad0-3203-421c-a05f-1b91ed2ae8b7%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/to
>> pic/jenkinsci-dev/iPRaDWYZccw/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/CANWgJS54ppDYo_NkweVdHytYamj9NkYZNP00%2Ba%
>> 2BydD1Ldq14%3Dw%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are 

Re: Maintainer request for the Gatling plugin

[Stéphane LANDELLE]

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 CEO*
slande...@gatling.io


On Fri, Jan 13, 2017 at 10:45 AM, 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 :
>
>> 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* appreciated, and show
>> a respect for other people's time.
>> Having to two many roundtrips here for this is probably not enjoyable for
>> anyone.
>>
>> The answer from Stéphane below is.
>>
>> Thanks
>>
>> 2017-01-13 9:58 GMT+01:00 Cédric Cousseran :
>>
>>> 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 additional maintainer,
 then we need heads-up from an existing maintainer. I guess it's an obvious
 default, anyway, isn't it?

 We can all save time if people provide more context in general for
 those kinds of requests, thank you!

 2017-01-11 11:25 GMT+01:00 Cédric Cousseran :

> Hi,
>
> I want to be a maintainer of the Gatling Plugin:
> https://github.com/jenkinsci/gatling-plugin
>
> GitHub ID: ccedric
> Jenkins ID: ccousseran
>
> Regards,
> Cédric Cousseran
>
> --
> You received this message because you are subscribed to the Google
> Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-dev/6552611c-3b4
> d-47b9-ad66-228781ec6566%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/ms
>>> gid/jenkinsci-dev/d73e1ad0-3203-421c-a05f-1b91ed2ae8b7%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/iPRaDWYZccw/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/CANWgJS54ppDYo_NkweVdHytYamj9NkYZNP00%2Ba%
> 2BydD1Ldq14%3Dw%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/CAJw%3DiaRWjs3ZnoE5x64t%2BLAobiMCF9DSFXYBr%2BRWR8Hy79DGww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maintainer request for the Gatling plugin

[Stéphane LANDELLE]

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 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 CEO*
> slande...@gatling.io
>
>
> On Fri, Jan 13, 2017 at 10:45 AM, 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 :
>>
>>> 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* appreciated, and
>>> show a respect for other people's time.
>>> Having to two many roundtrips here for this is probably not enjoyable
>>> for anyone.
>>>
>>> The answer from Stéphane below is.
>>>
>>> Thanks
>>>
>>> 2017-01-13 9:58 GMT+01:00 Cédric Cousseran :
>>>
 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 additional maintainer,
> then we need heads-up from an existing maintainer. I guess it's an obvious
> default, anyway, isn't it?
>
> We can all save time if people provide more context in general for
> those kinds of requests, thank you!
>
> 2017-01-11 11:25 GMT+01:00 Cédric Cousseran :
>
>> Hi,
>>
>> I want to be a maintainer of the Gatling Plugin:
>> https://github.com/jenkinsci/gatling-plugin
>>
>> GitHub ID: ccedric
>> Jenkins ID: ccousseran
>>
>> Regards,
>> Cédric Cousseran
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to jenkinsci-de...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-dev/6552611c-3b4
>> d-47b9-ad66-228781ec6566%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/ms
 gid/jenkinsci-dev/d73e1ad0-3203-421c-a05f-1b91ed2ae8b7%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/to
>> pic/jenkinsci-dev/iPRaDWYZccw/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/CANWgJS54ppDYo_NkweVdHytYamj9NkYZNP00%2Ba%
>> 2BydD1Ldq14%3Dw%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/CAJw%3DiaQp0LpH%2BYtQiCuy%3DZBXW%3DcY1Jz94-y5wBFEAHZ08zJjBw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Repo plugin is up for adoption

[Robert Sandell]

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 longer a repo user myself I can't really plan and
evolve the plugin and it could use some more active maintainership from
"real users".

I'll continue merging and releasing, but don't be shy if you feel a bit
hungry for some more responsibility ;)

-- 
Robert Sandell
*Software Engineer*
*CloudBees Inc.*

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

Re: Maintainer request for the Gatling plugin

[Baptiste Mathus]

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 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* appreciated, and show
> a respect for other people's time.
> Having to two many roundtrips here for this is probably not enjoyable for
> anyone.
>
> The answer from Stéphane below is.
>
> Thanks
>
> 2017-01-13 9:58 GMT+01:00 Cédric Cousseran :
>
>> 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 additional maintainer,
>>> then we need heads-up from an existing maintainer. I guess it's an obvious
>>> default, anyway, isn't it?
>>>
>>> We can all save time if people provide more context in general for those
>>> kinds of requests, thank you!
>>>
>>> 2017-01-11 11:25 GMT+01:00 Cédric Cousseran :
>>>
 Hi,

 I want to be a maintainer of the Gatling Plugin:
 https://github.com/jenkinsci/gatling-plugin

 GitHub ID: ccedric
 Jenkins ID: ccousseran

 Regards,
 Cédric Cousseran

 --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Developers" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to jenkinsci-de...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/ms
 gid/jenkinsci-dev/6552611c-3b4d-47b9-ad66-228781ec6566%40goo
 glegroups.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/d73e1ad0-3203-421c-a05f-1b91ed2ae8b7%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/CANWgJS54ppDYo_NkweVdHytYamj9NkYZNP00%2Ba%2BydD1Ldq14%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Not able to release new version of plugin

[Irfan Sayed]

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 unauthorized error.
can someone please provide me the access to release plugin ?
regards,




On Thu, Jan 12, 2017 at 11:25 PM, Irfan Sayed  wrote:

> As i am troubleshooting further, just wanted to confirm, if my ID :
> "irfanjs" has valid deploy artifact/release plugin permission to jenkins-ci
> org?
> Hi Baptiste/Daniel,
> Can i Request you to please have a look on the same.
>
> Regards,
>
>
> On Thu, Jan 12, 2017 at 11:15 PM, Irfan Sayed 
> wrote:
>
>> further update:
>> i started ssh-agent and imported the private key of the github account.
>> my github account and jenkins-ci account is same.
>> aftrer that, added username and password in the ~/.m2/settings.xml file
>> and run the command:
>> "mvn release:prepare release:perform"
>>
>> still the same issue : "401 unauthorized"
>>
>> Regards,
>>
>>
>> On Thu, Jan 12, 2017 at 6:47 PM, Irfan Sayed 
>> wrote:
>>
>>> Hi,
>>> Please suggest...
>>> i tried passing username and password as well in the maven release
>>> command but no luck
>>>
>>> Regards,
>>>
>>>
>>> On Thu, Jan 12, 2017 at 12:47 PM, Irfan Sayed 
>>> wrote:
>>>
 Hi,
 I have created the PR request :
 https://github.com/irfanjs/chefbuilder/pull/1

 Can you please review the same ?
 i made changes directly into master branch. so i guess no need to merge
 anything.

 I understand that i dont have plugin release upload permission.

 i followed the below link:
 https://github.com/jenkins-infra/repository-permissions-updater

 and verified that YAML file exist for my plugin with correct content.
 please let me know if i need to request anything more so that i can
 upload new release

 Regards,


 On Wed, Jan 11, 2017 at 8:56 AM, Irfan Sayed 
 wrote:

> Thanks.
> Let me thoroughly have a look and update
>
> Regards,
>
>
> On Wed, Jan 11, 2017 at 10:07 PM, Daniel Beck  wrote:
>
>>
>> > On 11.01.2017, at 17:34, Irfan Sayed  wrote:
>> >
>> > not getting why "unauthorized" error is coming
>>
>> Have you looked into all of the suggestions in the 12th note at
>> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#
>> HostingPlugins-Workingaroundcommonissues ?
>>
>> --
>> 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/7956E78F-980
>> D-44AE-BDCF-D3509E827702%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/CACGLCJYeLj6KTxkQ6_Ff2nY%3D2c_aFWGwzEr%2BCQ3ZuXh91rsYsg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maintainer request for the Gatling plugin

[Baptiste Mathus]

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* appreciated, and show
a respect for other people's time.
Having to two many roundtrips here for this is probably not enjoyable for
anyone.

The answer from Stéphane below is.

Thanks

2017-01-13 9:58 GMT+01:00 Cédric Cousseran :

> 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 additional maintainer,
>> then we need heads-up from an existing maintainer. I guess it's an obvious
>> default, anyway, isn't it?
>>
>> We can all save time if people provide more context in general for those
>> kinds of requests, thank you!
>>
>> 2017-01-11 11:25 GMT+01:00 Cédric Cousseran :
>>
>>> Hi,
>>>
>>> I want to be a maintainer of the Gatling Plugin:
>>> https://github.com/jenkinsci/gatling-plugin
>>>
>>> GitHub ID: ccedric
>>> Jenkins ID: ccousseran
>>>
>>> Regards,
>>> Cédric Cousseran
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Developers" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-de...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-dev/6552611c-3b4d-47b9-ad66-228781ec6566%40goo
>>> glegroups.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/d73e1ad0-3203-421c-a05f-1b91ed2ae8b7%
> 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/CANWgJS4_mNP1kSYRvCFc%3DTdekX0nKCAmxS4moOSnCvAAcXE6Rw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maintainer request for the Gatling plugin

[slandelle]

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 be added as an additional maintainer, 
> then we need heads-up from an existing maintainer. I guess it's an obvious 
> default, anyway, isn't it?
>
> We can all save time if people provide more context in general for those 
> kinds of requests, thank you!
>
> 2017-01-11 11:25 GMT+01:00 Cédric Cousseran  >:
>
>> Hi,
>>
>> I want to be a maintainer of the Gatling Plugin: 
>> https://github.com/jenkinsci/gatling-plugin
>>
>> GitHub ID: ccedric
>> Jenkins ID: ccousseran
>>
>> Regards,
>> Cédric Cousseran
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/6552611c-3b4d-47b9-ad66-228781ec6566%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/c43d95e5-9a56-4472-9130-5232d8d97b9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maintainer request for the Gatling plugin

[Cédric Cousseran]

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 additional maintainer, 
> then we need heads-up from an existing maintainer. I guess it's an obvious 
> default, anyway, isn't it?
>
> We can all save time if people provide more context in general for those 
> kinds of requests, thank you!
>
> 2017-01-11 11:25 GMT+01:00 Cédric Cousseran  >:
>
>> Hi,
>>
>> I want to be a maintainer of the Gatling Plugin: 
>> https://github.com/jenkinsci/gatling-plugin
>>
>> GitHub ID: ccedric
>> Jenkins ID: ccousseran
>>
>> Regards,
>> Cédric Cousseran
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/6552611c-3b4d-47b9-ad66-228781ec6566%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/d73e1ad0-3203-421c-a05f-1b91ed2ae8b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.