Re: Commit rights to cobertura-plugin

[Ullrich Hafner]

Actually I was never the maintainer. I just fixed some issues that blocked my 
projects… 

So feel free to take over the ownership!

> Am 13.03.2017 um 21:41 schrieb Daniel Beck :
> 
> Nice, well written request.
> 
> Re Ulli's old email address no longer working, I'm adding him in CC.
> 
>> On 13.03.2017, at 21:27, Michael Barrientos  wrote:
>> 
>> I would like to get commit rights to 
>> http://github.com/jenkinsci/cobertura-plugin.
>> 
>> Per instructions on both https://jenkins.io/project/governance/ and 
>> https://wiki.jenkins-ci.org/display/JENKINS/Adopt+a+Plugin this is my formal 
>> request for commit access.
>> 
>> The plugin has not had any activity in the master branch since May 2016 (10 
>> months), and there are several outstanding PRs I'd like to get merged in 
>> (including attempts to make it compatible with the new Jenkinsfile Workflow 
>> API).
>> 
>> On March 7 (one week ago) I attempted to contact all maintainers listed in 
>> 
>>  via the email listed in their last commit.
>> 
>> * drulli's @dev.java.net email address bounced
>> * tamini said "I added code once a few years ago and guess I got added as a 
>> maintainer when I made the merge.  I haven't really worked with Jenkins 
>> since then and have removed myself from the Cobertura team to reflect this." 
>> (Sorry tamini, to formally go through the process, I'm spamming your email 
>> address one last time.)
>> * Jenkins core maintainer olivergondza never responded.
>> 
>> Although a history of commits isn't necessary, I have contributed in the 
>> past to http://github.com/jenkinsci/ec2-plugin.
>> 
>> My Github ID and Jenkins infrastructure account IDs are both "mbarrien".
>> 
>> Please let me know if there is anything more information needed, or if there 
>> is anything I can do to help. 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/CAChLnmkhcZeuwq%2BM2yAQg0WuRchzxa0BhtxSEjrhKFr%3D5pF-gQ%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/420A1481-9153-4513-85EA-04BAFCAC521F%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Testing a plugin before release

[JordanGS]

Thanks for the reply, not what i meant tho. I know the project compiles and 
builds fine but for whatever reason the command

mvn release:prepare release:perform 


maybe due to a permission issue or it did the upload to maven but failed 
the git push. I was hoping for a sanity test for this.

On Monday, March 13, 2017 at 4:55:35 PM UTC-4, Stephen Connolly wrote:
>
> Always good to run `mvn hpi:run` and give it some manual sanity checks 
> first too
>
> On 13 March 2017 at 20:37, 'Bruno P. Kinoshita' via Jenkins Developers <
> jenkin...@googlegroups.com > wrote:
>
>> Normally I just run `mvn clean test`, or `mvn clean test firebug:firebug 
>> firebug:gui`. Then if everything works, I trust the mvn release:prepare & 
>> perform will work. If you are not confident it will work, you can try 
>> cutting an experimental release [1], which might be useful too if you'd 
>> like to deploy it to a test bed server. Just use -alpha in your version.
>>
>>
>> Hope that helps
>> B
>>
>>
>> [1] 
>> https://jenkins.io/blog/2013/09/23/experimental-plugins-update-center/
>>
>>
>>
>> 
>> From: JordanGS >
>> To: Jenkins Developers >
>> Sent: Tuesday, 14 March 2017 8:42 AM
>> Subject: Testing a plugin before release
>>
>>
>>
>> So as to avoid burning through version numbers with bad releases, i was 
>> wondering if there is a way to test to make sure everything will compile 
>> beforehand?
>>
>> To publish the plugin we use:
>>
>> mvn release:prepare release:perform
>> The documentation says that the jenkins credentials can be verified 
>> with:mvn deploy
>> Is there any way to verify that the build will succeed?
>>
>> Maybe (for maven)
>>
>> mvn release:prepare -DdryRun=true
>> and to make sure that the pull to GitHub won't have issues, just
>> ssh -T g...@github.com 
>>
>> Or is there anything else that can be used?
>>
>> --
>> 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/b7ede8ea-cc0f-4ca2-80d9-427a737f38e6%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/391913242.6212062.1489437449756%40mail.yahoo.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/465d2bde-ef8d-4937-94ca-e3555327c82a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Naming convention for sprints in Jira

[Daniel Beck]

> On 13.03.2017, at 21:54, James Dumay  wrote:
> 
> Though this is one of those situations where if we used JIRA correctly 
> (anything having its own lifecycle should have a project) we could avoid the 
> name spacing issues (with the added bonus of being able to use Release 
> Versions - no more confusion as to what has shipped or not...)

SECURITY does and I still see a list of your sprints in JENKINS when I edit 
SECURITY issues.

-- 
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/C76D1B1A-4E2D-4BF4-A407-A21EE4822D7E%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Naming convention for sprints in Jira

[Stephen Connolly]

Yeah but then we'd have lots of fun as the same issue moves through 1000's
of products because the user didn't know which one to file in

On 13 March 2017 at 20:54, James Dumay  wrote:

> Though this is one of those situations where if we used JIRA correctly
> (anything having its own lifecycle should have a project) we could avoid
> the name spacing issues (with the added bonus of being able to use Release
> Versions - no more confusion as to what has shipped or not...)
>
> On Tue, Mar 14, 2017 at 7:48 AM James Dumay  wrote:
>
>> SGTM
>>
>> On Tue, Mar 14, 2017 at 6:05 AM Daniel Beck  wrote:
>>
>> Hi everyone,
>>
>> it seems sprints in Jira are globally visible (across projects), and,
>> when editing an issue, provide little context as to what that sprint is.
>>
>> I think some sort of prefix in names should be adopted by everyone using
>> sprints in Jira -- basically James D right now -- to make it easy to see
>> what it relates to. "1.1" is just too light on context. In James' case, BO,
>> Blue Ocean, or similar would be helpful.
>>
>> In SECURITY related "sprints" (not really, but still helps plan) I've
>> started using the 'SECURITY' prefix for sprints. So, for example, the
>> 'sprint' released on Feb 1 was "SECURITY: Collins".
>>
>> WDYT?
>>
>> Daniel
>>
>> --
>> James Dumay
>> Product Manager
>> CloudBees, Inc.
>> Skype: jdumaycb Twitter: i386
>>
> --
> James Dumay
> Product Manager
> CloudBees, Inc.
> Skype: jdumaycb Twitter: i386
>
> --
> 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/CAErbOvSCb04K-2_K8q3DdfnGhX9YgqzCayd-
> mNz4cZpMCL%3DpXg%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMyS_LGXtj%2B4PbpKTP9CygnFUG5qduDLw321wrsduFkAzA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Testing a plugin before release

[Stephen Connolly]

Always good to run `mvn hpi:run` and give it some manual sanity checks
first too

On 13 March 2017 at 20:37, 'Bruno P. Kinoshita' via Jenkins Developers <
jenkinsci-dev@googlegroups.com> wrote:

> Normally I just run `mvn clean test`, or `mvn clean test firebug:firebug
> firebug:gui`. Then if everything works, I trust the mvn release:prepare &
> perform will work. If you are not confident it will work, you can try
> cutting an experimental release [1], which might be useful too if you'd
> like to deploy it to a test bed server. Just use -alpha in your version.
>
>
> Hope that helps
> B
>
>
> [1] https://jenkins.io/blog/2013/09/23/experimental-plugins-update-center/
>
>
>
> 
> From: JordanGS 
> To: Jenkins Developers 
> Sent: Tuesday, 14 March 2017 8:42 AM
> Subject: Testing a plugin before release
>
>
>
> So as to avoid burning through version numbers with bad releases, i was
> wondering if there is a way to test to make sure everything will compile
> beforehand?
>
> To publish the plugin we use:
>
> mvn release:prepare release:perform
> The documentation says that the jenkins credentials can be verified
> with:mvn deploy
> Is there any way to verify that the build will succeed?
>
> Maybe (for maven)
>
> mvn release:prepare -DdryRun=true
> and to make sure that the pull to GitHub won't have issues, just
> ssh -T g...@github.com
>
> Or is there anything else that can be used?
>
> --
> 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/b7ede8ea-cc0f-4ca2-80d9-427a737f38e6%
> 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/391913242.6212062.1489437449756%40mail.yahoo.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CA%2BnPnMxdZGMXpx3Hn2v5xiJhjraLoEV_L--tKQHzdSVLk--nXw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Naming convention for sprints in Jira

[James Dumay]

Though this is one of those situations where if we used JIRA correctly
(anything having its own lifecycle should have a project) we could avoid
the name spacing issues (with the added bonus of being able to use Release
Versions - no more confusion as to what has shipped or not...)

On Tue, Mar 14, 2017 at 7:48 AM James Dumay  wrote:

> SGTM
>
> On Tue, Mar 14, 2017 at 6:05 AM Daniel Beck  wrote:
>
> Hi everyone,
>
> it seems sprints in Jira are globally visible (across projects), and, when
> editing an issue, provide little context as to what that sprint is.
>
> I think some sort of prefix in names should be adopted by everyone using
> sprints in Jira -- basically James D right now -- to make it easy to see
> what it relates to. "1.1" is just too light on context. In James' case, BO,
> Blue Ocean, or similar would be helpful.
>
> In SECURITY related "sprints" (not really, but still helps plan) I've
> started using the 'SECURITY' prefix for sprints. So, for example, the
> 'sprint' released on Feb 1 was "SECURITY: Collins".
>
> WDYT?
>
> Daniel
>
> --
> James Dumay
> Product Manager
> CloudBees, Inc.
> Skype: jdumaycb Twitter: i386
>
-- 
James Dumay
Product Manager
CloudBees, Inc.
Skype: jdumaycb Twitter: i386

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

Re: Naming convention for sprints in Jira

[James Dumay]

SGTM

On Tue, Mar 14, 2017 at 6:05 AM Daniel Beck  wrote:

> Hi everyone,
>
> it seems sprints in Jira are globally visible (across projects), and, when
> editing an issue, provide little context as to what that sprint is.
>
> I think some sort of prefix in names should be adopted by everyone using
> sprints in Jira -- basically James D right now -- to make it easy to see
> what it relates to. "1.1" is just too light on context. In James' case, BO,
> Blue Ocean, or similar would be helpful.
>
> In SECURITY related "sprints" (not really, but still helps plan) I've
> started using the 'SECURITY' prefix for sprints. So, for example, the
> 'sprint' released on Feb 1 was "SECURITY: Collins".
>
> WDYT?
>
> Daniel
>
> --
James Dumay
Product Manager
CloudBees, Inc.
Skype: jdumaycb Twitter: i386

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

Re: Testing a plugin before release

['Bruno P. Kinoshita' via Jenkins Developers]

Normally I just run `mvn clean test`, or `mvn clean test firebug:firebug 
firebug:gui`. Then if everything works, I trust the mvn release:prepare & 
perform will work. If you are not confident it will work, you can try cutting 
an experimental release [1], which might be useful too if you'd like to deploy 
it to a test bed server. Just use -alpha in your version.


Hope that helps
B


[1] https://jenkins.io/blog/2013/09/23/experimental-plugins-update-center/




From: JordanGS 
To: Jenkins Developers  
Sent: Tuesday, 14 March 2017 8:42 AM
Subject: Testing a plugin before release



So as to avoid burning through version numbers with bad releases, i was 
wondering if there is a way to test to make sure everything will compile 
beforehand?

To publish the plugin we use: 

mvn release:prepare release:perform 
The documentation says that the jenkins credentials can be verified with:mvn 
deploy
Is there any way to verify that the build will succeed?

Maybe (for maven)

mvn release:prepare -DdryRun=true
and to make sure that the pull to GitHub won't have issues, just 
ssh -T g...@github.com

Or is there anything else that can be used?

-- 
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/b7ede8ea-cc0f-4ca2-80d9-427a737f38e6%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/391913242.6212062.1489437449756%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: Commit rights to cobertura-plugin

[Daniel Beck]

Nice, well written request.

Re Ulli's old email address no longer working, I'm adding him in CC.

> On 13.03.2017, at 21:27, Michael Barrientos  wrote:
> 
> I would like to get commit rights to 
> http://github.com/jenkinsci/cobertura-plugin.
> 
> Per instructions on both https://jenkins.io/project/governance/ and 
> https://wiki.jenkins-ci.org/display/JENKINS/Adopt+a+Plugin this is my formal 
> request for commit access.
> 
> The plugin has not had any activity in the master branch since May 2016 (10 
> months), and there are several outstanding PRs I'd like to get merged in 
> (including attempts to make it compatible with the new Jenkinsfile Workflow 
> API).
> 
> On March 7 (one week ago) I attempted to contact all maintainers listed in 
> 
>  via the email listed in their last commit.
> 
> * drulli's @dev.java.net email address bounced
> * tamini said "I added code once a few years ago and guess I got added as a 
> maintainer when I made the merge.  I haven't really worked with Jenkins since 
> then and have removed myself from the Cobertura team to reflect this." (Sorry 
> tamini, to formally go through the process, I'm spamming your email address 
> one last time.)
> * Jenkins core maintainer olivergondza never responded.
> 
> Although a history of commits isn't necessary, I have contributed in the past 
> to http://github.com/jenkinsci/ec2-plugin.
> 
> My Github ID and Jenkins infrastructure account IDs are both "mbarrien".
> 
> Please let me know if there is anything more information needed, or if there 
> is anything I can do to help. 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/CAChLnmkhcZeuwq%2BM2yAQg0WuRchzxa0BhtxSEjrhKFr%3D5pF-gQ%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/22714B14-CA5D-48F8-84EC-319BCF2C3354%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Commit rights to cobertura-plugin

[Michael Barrientos]

I would like to get commit rights to
http://github.com/jenkinsci/cobertura-plugin.

Per instructions on both https://jenkins.io/project/governance/ and
https://wiki.jenkins-ci.org/display/JENKINS/Adopt+a+Plugin this is my
formal request for commit access.

The plugin has not had any activity in the master branch since May 2016 (10
months), and there are several outstanding PRs I'd like to get merged in
(including attempts to make it compatible with the new Jenkinsfile Workflow
API).

On March 7 (one week ago) I attempted to contact all maintainers listed in <
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-cobertura.yml>
via the email listed in their last commit.

* drulli's @dev.java.net email address bounced
* tamini said "I added code once a few years ago and guess I got added as a
maintainer when I made the merge.  I haven't really worked with Jenkins
since then and have removed myself from the Cobertura team to reflect
this." (Sorry tamini, to formally go through the process, I'm spamming your
email address one last time.)
* Jenkins core maintainer olivergondza never responded.

Although a history of commits isn't necessary, I have contributed in the
past to http://github.com/jenkinsci/ec2-plugin.

My Github ID and Jenkins infrastructure account IDs are both "mbarrien".

Please let me know if there is anything more information needed, or if
there is anything I can do to help. 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/CAChLnmkhcZeuwq%2BM2yAQg0WuRchzxa0BhtxSEjrhKFr%3D5pF-gQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Testing a plugin before release

[JordanGS]

So as to avoid burning through version numbers with bad releases, i was 
wondering if there is a way to test to make sure everything will compile 
beforehand?

To publish the plugin we use: 

mvn release:prepare release:perform 

The documentation says that the jenkins credentials can be verified with:

mvn deploy

Is there any way to verify that the build will succeed?

Maybe (for maven)

mvn release:prepare -DdryRun=true

and to make sure that the pull to GitHub won't have issues, just 
ssh -T g...@github.com

Or is there anything else that can be used?

-- 
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/b7ede8ea-cc0f-4ca2-80d9-427a737f38e6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Naming convention for sprints in Jira

[Daniel Beck]

Hi everyone,

it seems sprints in Jira are globally visible (across projects), and, when 
editing an issue, provide little context as to what that sprint is.

I think some sort of prefix in names should be adopted by everyone using 
sprints in Jira -- basically James D right now -- to make it easy to see what 
it relates to. "1.1" is just too light on context. In James' case, BO, Blue 
Ocean, or similar would be helpful.

In SECURITY related "sprints" (not really, but still helps plan) I've started 
using the 'SECURITY' prefix for sprints. So, for example, the 'sprint' released 
on Feb 1 was "SECURITY: Collins".

WDYT?

Daniel

-- 
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/51EB3A86-FDC6-452D-A3B5-2996865B9BF9%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Error when running maven command to release on jenkins-ci.org

[Daniel Beck]

> On 13.03.2017, at 15:15, JordanGS  wrote:
> 
> published half the files for some reason, so i believe that caused the hidden

Right, you're not allowed to delete, which is what overwriting does (delete + 
create).

That version number is burnt, use the next one.

-- 
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/DD16C20C-300C-41C7-BD50-55115A8364AC%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Error when running maven command to release on jenkins-ci.org

[JordanGS]

It took a couple hours but i got it working. To answer your questions, i am 
using the same exact account.


   1. Install Git Bash and make sure to configure the line ending 
   conversions to *Check as-in, commit as-is*
   2. Make sure, JAVA_HOME and M2_HOME are recognized
   3. If using SSH, test connection with *ssh -T g...@github.com*
   4. Use *mvn deploy *to test your connection settings after having 
   configured settings.xml

One of the original failures, published half the files for some reason, so 
i believe that caused the hidden. Which is weird because i don't understand 
why it would upload files before doing the git commands. See here 
.

-- 
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/5aea9051-0c82-4d61-8b72-625d4986590a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Commit rights to matrix-auth-plugin

[Mathias Nyman]

10 days has passed. Is there something unusual or suspicious about my
request?


:Mathias

On 2017-03-03 17:50+0200, Mathias Nyman wrote:

Hi,

I'm asking for commit rights to matrix-auth-plugin
(https://github.com/jenkinsci/matrix-auth-plugin).

The plugin seems to lack an active maintainer and my first intention
is to merge my own (albeit reviewed) bug fix:
https://github.com/jenkinsci/matrix-auth-plugin/pull/16


Asking, as instructed on https://jenkins.io/project/governance/ :

"Plugin committers are those who have push access to specific plugin
repositories hosted under the jenkinsci GitHub organization. One is
not required to have a proven history of contributions before being
granted commit access. All you have to do is to ask. But that doesn’t
mean other existing committers will never revert your changes."


Thanks,
:Mathias
https://github.com/mathias-nyman



--
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/20170313130116.GA28446%40iki.fi.
For more options, visit https://groups.google.com/d/optout.

Re: Error when running maven command to release on jenkins-ci.org

[Daniel Beck]

> On 13.03.2017, at 11:10, Robert Sandell  wrote:
> 
> You might not be on the list of contributors allowed to upload artifacts
> https://github.com/jenkins-infra/repository-permissions-updater

He is, but may be using a different account now.

-- 
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/2FDD0EED-B25D-439F-9FDF-AE043F5C14BF%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to compile Jenkins itself with compilation level set to Java 8

[Marcin Zajączkowski]

I created an issue for that: 
https://issues.jenkins-ci.org/browse/JENKINS-42709\

Marcin


On Friday, February 3, 2017 at 1:46:41 PM UTC+1, Marcin Zajączkowski wrote:
>
> Hi,
>
> I was playing with the issue related to searchable nested views [1] and it 
> turned out that the implementation would be much easier with Java 8's 
> default methods in interfaces. Unfortunately after switching compiler in 
> Maven configuration to Java 8 the compilation fails with quite complex 
> looking generics related error:
>
> 
> [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ 
> jenkins-core ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 1046 source files to 
> /home/foo/code/jenkins/core/target/classes
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /home/foo/code/jenkins/core/src/main/java/hudson/model/User.java:[658,22] 
> error: method fromJobs in class RunList cannot be applied to given 
> types;
> [ERROR]   required: Iterable
>   found: Iterable
>   reason: inferred type does not conform to lower bound(s)
> inferred: J#2
> lower bound(s): T,Job
>   where J#1,R#1,R#2,J#2,R#3,T are type-variables:
> J#1 extends Job declared in method 
> fromJobs(Iterable)
> R#1 extends Run declared in method 
> fromJobs(Iterable)
> R#2 extends Run declared in class RunList
> J#2 extends Job
> R#3 extends Run
> T extends J#2
> /home/foo/code/jenkins/core/src/main/java/hudson/model/Computer.java:[781,22] 
> error: method fromJobs in class RunList cannot be applied to given 
> types;
> [INFO] 2 errors 
> 
>
> I wonder if it is a known issue or maybe even anyone gave a look at it 
> already?
>
> Changes in the configuration triggering that error are available in my 
> branch [2] (just in case :) ).
>
> [1] - https://groups.google.com/forum/#!topic/jenkinsci-dev/GTjiXQkN4Fs
> [2] - https://github.com/szpak/jenkins/tree/feature/searchableNestedViews
>
> Marcin
>
> -- 
> http://blog.solidsoft.info - Solid Soft - Working code is not enough
>
>

-- 
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/7319e614-d888-4134-9565-9d9d29858a90%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Unable to compile Jenkins itself with compilation level set to Java 8

[Marcin Zajączkowski]

On Monday, March 13, 2017 at 1:25:06 PM UTC+1, Marcin Zajączkowski wrote:
>
> I created an issue for that: 
> https://issues.jenkins-ci.org/browse/JENKINS-42709\
>

Corrected URL: https://issues.jenkins-ci.org/browse/JENKINS-42709
 


>
> Marcin
>
>
> On Friday, February 3, 2017 at 1:46:41 PM UTC+1, Marcin Zajączkowski wrote:
>>
>> Hi,
>>
>> I was playing with the issue related to searchable nested views [1] and 
>> it turned out that the implementation would be much easier with Java 8's 
>> default methods in interfaces. Unfortunately after switching compiler in 
>> Maven configuration to Java 8 the compilation fails with quite complex 
>> looking generics related error:
>>
>> 
>> [INFO] --- maven-compiler-plugin:3.0:compile (default-compile) @ 
>> jenkins-core ---
>> [INFO] Changes detected - recompiling the module!
>> [INFO] Compiling 1046 source files to 
>> /home/foo/code/jenkins/core/target/classes
>> [INFO] -
>> [ERROR] COMPILATION ERROR : 
>> [INFO] -
>> [ERROR] 
>> /home/foo/code/jenkins/core/src/main/java/hudson/model/User.java:[658,22] 
>> error: method fromJobs in class RunList cannot be applied to given 
>> types;
>> [ERROR]   required: Iterable
>>   found: Iterable
>>   reason: inferred type does not conform to lower bound(s)
>> inferred: J#2
>> lower bound(s): T,Job
>>   where J#1,R#1,R#2,J#2,R#3,T are type-variables:
>> J#1 extends Job declared in method 
>> fromJobs(Iterable)
>> R#1 extends Run declared in method 
>> fromJobs(Iterable)
>> R#2 extends Run declared in class RunList
>> J#2 extends Job
>> R#3 extends Run
>> T extends J#2
>> /home/foo/code/jenkins/core/src/main/java/hudson/model/Computer.java:[781,22]
>>  
>> error: method fromJobs in class RunList cannot be applied to given 
>> types;
>> [INFO] 2 errors 
>> 
>>
>> I wonder if it is a known issue or maybe even anyone gave a look at it 
>> already?
>>
>> Changes in the configuration triggering that error are available in my 
>> branch [2] (just in case :) ).
>>
>> [1] - https://groups.google.com/forum/#!topic/jenkinsci-dev/GTjiXQkN4Fs
>> [2] - https://github.com/szpak/jenkins/tree/feature/searchableNestedViews
>>
>> Marcin
>>
>> -- 
>> http://blog.solidsoft.info - Solid Soft - Working code is not enough
>>
>>

-- 
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/963e31b8-ab36-46f7-9acc-1af1edb1d5d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error when running maven command to release on jenkins-ci.org

[Robert Sandell]

You might not be on the list of contributors allowed to upload artifacts
https://github.com/jenkins-infra/repository-permissions-updater

/B

On Mon, Mar 13, 2017 at 8:08 AM, JordanGS  wrote:

> And to add another thing, when i try using windows cmd.exe, i get
>
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-
> plugin:2.8.2:deploy (default-deploy) on project zap: Failed to deploy
> artifacts: Could not transfer artifact org.jenkins-ci.plugins:zap:hpi:1.0.
> 6 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/):
> Access denied to: https://repo.jenkins-ci.org/releases/org/jenkins-ci/
> plugins/zap/1.0.6/zap-1.0.6.hpi, ReasonPhrase: Forbidden. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [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 read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/
> MojoExecutionException
>
> What is going on?
>
> --
> 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/5edc7f96-f129-4c7d-9a63-6f6a8bc5a56e%
> 40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
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/CALzHZS0i3p7xhgNn%3DcX7YGFmY6Rf-jUPzrMecZnTc0%2BvB2J%3DJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Releassing jacoco-plugin: timeout when pushing artifacts to maven.jenkins-ci.org

[Yuanbo Han]

Hi, please refer here: 
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues.
 
 You should update the parent org.jenkins-ci.plugins version. I updated to 
2.11 and it worked for me.

在 2016年9月29日星期四 UTC+8上午2:05:37，Dominik Stadler写道：
>
> Hi, 
>
> I feel a bit stupid, but I have a strange problem publishing a plugin 
> release, the same setup worked before, but now I get a timeout-error when 
> the artifacts are pushed to maven.jenkins-ci.org. 
>
> Anything changed since my last release in Jan?
>
> The pom.xml has
>
> 
> 
>   maven.jenkins-ci.org
>   
> http://maven.jenkins-ci.org:8081/content/repositories/releases/
> 
>  
>
> Full repo is at https://github.com/jenkinsci/jacoco-plugin
>
> Any hint in which direction I need to continue investigation?
>
> Thanks... Dominik.
>
> ...
> [INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ jacoco 
> ---
> [INFO] Uploading: 
> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/jacoco/2.1.0/jacoco-2.1.0.hpi
> [INFO] 
> [INFO] Uploading: 
> http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/jacoco/2.1.0/jacoco-2.1.0.pom
> [INFO] 
> [INFO] [INFO] 
> 
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO] 
> 
> [INFO] [INFO] Total time: 07:38 min
> [INFO] [INFO] Finished at: 2016-09-28T19:25:39+02:00
> [INFO] [INFO] Final Memory: 79M/810M
> [INFO] [INFO] 
> 
> [INFO] [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on 
> project jacoco: Failed to deploy artifacts: Could not transfer artifact 
> org.jenkins-ci.plugins:jacoco:hpi:2.1.0 from/to maven.jenkins-ci.org (
> http://maven.jenkins-ci.org:8081/content/repositories/releases/): Connect 
> to maven.jenkins-ci.org:8081 [maven.jenkins-ci.org/199.193.196.24] 
> failed: Die Wartezeit für die Verbindung ist abgelaufen -> [Help 1]
> [INFO] [ERROR] 
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven 
> with the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug 
> logging.
> [INFO] [ERROR] 
> [INFO] [ERROR] For more information about the errors and possible 
> solutions, please read the following articles:
> [INFO] [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 08:15 min
> [INFO] Finished at: 2016-09-28T19:25:40+02:00
> [INFO] Final Memory: 22M/265M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-release-plugin:2.5:perform (default-cli) on 
> project jacoco: Maven execution failed, exit code: '1' -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the 
> -e switch.
> [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 read the following articles:
> [ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>
>

-- 
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/0f4c3a9e-779b-46fa-8df6-d502b92d3d05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

[Yuanbo Han]

Please refer here: 
https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues.
 
 You should update the parent org.jenkins-ci.plugins version.

在 2016年11月8日星期二 UTC+8下午4:17:08，Christian写道：
>
> Hi, I have read 
> https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues
>  
> and tried several different things but when I try to release a new plugin 
> version it always fail with:
>
> INFO] [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on 
> project claim: Failed to deploy artifacts: Could not transfer artifact 
> org.jenkins-ci.plugins:claim:hpi:2.9 from/to maven.jenkins-ci.org (
> http://maven.jenkins-ci.org:8081/content/repositories/releases): Connect 
> to maven.jenkins-ci.org:8081 [maven.jenkins-ci.org/199.193.196.24] 
> failed: Operation timed out -> [Help 1]
>
> I have a ~/.m2/settings.xml that looks like this:
>
> http://maven.apache.org/SETTINGS/1.0.0";
>
>   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
>   xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
>
>   http://maven.apache.org/xsd/settings-1.0.0.xsd";>
>
>
>   
>
> 
>
>   maven.jenkins-ci.org 
>
>   ki82
>
>   ***
>
> 
>
>   
>
>
> 
>
>
> I have verified that my password works at 
> https://repo.jenkins-ci.org/webapp/#/login and I use the encrypted 
> password in the ~/m2/settings.xml
>
> I have executed the effective pom and verified that the id is correct.
>
>
> Does anyone have any idea why this is failing for me?
>
> Is there any way to test the connection to maven.jenkins-ci.org without 
> doing an actual release?
>
>
>
>
>

-- 
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/d3c3d903-44cf-40c4-9ad8-5c5f8596bbde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: New plugin Bitbucket Server Branch Source

['Robin Müller' via Jenkins Developers]

Hi

Am Sonntag, 12. März 2017 21:50:01 UTC+1 schrieb Stephen Connolly:
>
>
> On Sun 12 Mar 2017 at 18:23, 'Robin Müller' via Jenkins Developers <
> jenkin...@googlegroups.com > wrote: 
>
...   
>
Not everyone in the OSS community has the luxury of somebody who can pay to 
> get licenses for these and set up multiple Bitbucket server instances to 
> allow testing the different server plugins.
>
> If we add support for more we effectively push others in the OSS community 
> out of the ability to contribute.
>

This wouldn't be an issue if the add-on specific code is moved to a 
different Jenkins plugin. Just have a look at this 
,
 
how it can work.

If we leave the support for both Bitbucket Cloud and Bitbucket Server 
within the "Bitbucket Branch Source" plugin I'd suggest the following 
changes to improve the maintainability:
1. implement a BitbucketCloudSCMSourceNavigator and a 
BitbucketServerSCMSourceNavigator that share the same base class but have 
the tool specific implemented in itself (e.g. retrieving the correct client 
implementation). With this you don't need to distinguish based on the URL 
or some other user provided input whether to talk to Bitbucket Cloud or 
Bitbucket Server. You'll always know this information depending on the 
context.
2. Do the same for the SCMSource
3. Replace the current "REST client implementation" by using JAX-RS (see 
BitbucketServerAPI.java 

, BitbucketServerClientService.java 
).
 
The current implementation is error-prone. E.g. URLs get generated using 
String.fromat which means you have to care for proper URL encoding of path 
parameters yourself. You have to map status codes of error responses 
manually to exceptions. JAX-RS does this out-of-the-box. And last but not 
least. JAX-RS provides an easy way to read the whole request/response to 
add it the the log (see LoggingFilter.java 
)
 
which is very useful if some request failed.

I know that 1. and 2. will lead to some migration effort but this can be 
done automatically by the plugin within an initialisier. I did something 
similar already within the gitlab-plugin.

I don't know how your time schedule looks like but if you like I can 
support you reaching the above points. But as not everything of the plugin 
is covered by tests it could take some time to be sure I don't break any 
existing functionality.
Nevertheless I'll install my plugin for the moment in our Jenkins as this 
is working with our Bitbucket Server and will save the whole department a 
lot of time.

Regards,
Robin

-- 
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/85b5ac9b-b3b5-4063-8676-0418fb784607%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Error when running maven command to release on jenkins-ci.org

[JordanGS]

And to add another thing, when i try using windows cmd.exe, i get 

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-
plugin:2.8.2:deploy (default-deploy) on project zap: Failed to deploy 
artifacts: Could not transfer artifact org.jenkins-ci.plugins:zap:hpi:1.0.6 
from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): 
Access denied to: 
https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/zap/1.0.6/zap-1.0.6.hpi,
 
ReasonPhrase: Forbidden. -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with 
the -e switch.
[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 read the following articles:
[ERROR] [Help 1] http:
//cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

What is going on?

-- 
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/5edc7f96-f129-4c7d-9a63-6f6a8bc5a56e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.