Re: Request to be a maintainer for the IvyTrigger Plugin

2017-11-10 Thread Daniel Beck 

> On 10. Nov 2017, at 20:16, Bergquist, Brett  wrote:
> 
> https://wiki.jenkins.io/display/JENKINS/IvyTrigger+Plugin
>  
> I have privately emails Gregory Boissinot about becoming a maintainer but 
> have not heard back.   Here is what I had sent Gregory
>  
> … 
> I have done no Jenkins plugin development but am starting to learn my way 
> around and will probably have to ask questions especially in the area of 
> making this plugin Pipeline compatible while maintaining backward 
> compatibility.   But I do think I can contribute to this plug development.
>  
> My github ID is “bbergquist0930” and my Jenkin infrastructure account is 
> “bbergquist”.
> 

Gregory told me in an email a year or so ago that he no longer has the time to 
maintain his plugins, and put them all up for adoption. So we can proceed 
assuming this transfer is fine with him.

Please follow the instructions in 
https://github.com/jenkins-infra/repository-permissions-updater/ and we'll set 
you up. Make sure to mention in the PR that you also need commit access, if 
applicable.

-- 
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/B195132D-C41F-4A98-8C6B-7F8CD9E81DDB%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: stack trace in configure system (docker, plugin development)

2017-11-10 Thread Ewelina Wilkosz 
wow, I forgot 'checkout scm' step :D it was using the old workspace from 
previous version of Jenkinsfile, that was the source of conflict I guess
thanks guys for pointing me the workspace as the source of problem, solved!

On Friday, November 10, 2017 at 8:32:52 PM UTC+1, Ewelina Wilkosz wrote:
>
> ok, when I build locally I do not get stack trace, something is messed up 
> in my Jenkins job or agent :)
>
> On Friday, November 10, 2017 at 8:06:43 PM UTC+1, Ewelina Wilkosz wrote:
>>
>> right, it does look like a git merge, the thing is, I can't see any 
>> conflicts in my repo
>> so it's just me not understanding how docker build works, I guess I will 
>> have to dig more into the issue
>>
>> On Friday, November 10, 2017 at 6:27:29 PM UTC+1, Mark Waite wrote:
>>>
>>> That looks like a failed "git merge".  No idea of the source of that 
>>> failed merge, but those markers are used by git when it can't resolve a 
>>> merge of a historical file into the current file.
>>>
>>> Mark Waite
>>>
>>> On Fri, Nov 10, 2017 at 10:14 AM Ewelina Wilkosz  
>>> wrote:
>>>
 I'm working on dockerizing Configuration as Code plugin, which means I 
 create a docker image, based on jenkins:2.60.3, I build the plugin and I 
 install it in a Dockerfile: 
 https://github.com/jenkinsci/configuration-as-code-plugin/blob/praqma/dev/Dockerfile

 It seems to be working, but I get stack trace in Configure System:

 org.apache.commons.jelly.JellyTagException: 
 jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.60.3.jar!/jenkins/model/Jenkins/configure.jelly:59:84:
   org.kohsuke.stapler.ScriptLoadException: 
 org.apache.commons.jelly.JellyException: Could not parse Jelly script : 
 jar:file:/var/jenkins_home/plugins/configuration-as-code/WEB-INF/lib/configuration-as-code.jar!/org/jenkinsci/plugins/casc/ConfigurationAsCode/index.jelly
at 
 org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
at 
 org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
 org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)

 (...)

 So I attached to docker container and checked 
 /var/jenkins_home/plugins/configuration-as-code/WEB-INF/lib/configuration-as-code.jar!/org/jenkinsci/plugins/casc/ConfigurationAsCode/index.jelly,
  
 and in it I can see:

 <<< HEAD

 ${c.name}

 

   Implementation of ${c.extensionpoint.simpleName}

 ===

 ${c.name}

 

   Implementation of https://jenkins.io/doc/developer/extensions/${c.extensionSource}/#${c.extensionPoint.simpleName.toLowerCase()}
 ">${c.extensionPoint.simpleName}

 >>> fork/master

 And I don't understand where it comes from... Complete newbie here. 
 Anyone willing to help with troubleshooting?

 -- 
 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/3cb870c9-4e69-413d-a4d2-29e106459725%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/4be8db36-f99f-48a9-be0e-1d21b2b0e95c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Request to be a maintainer for the IvyTrigger Plugin

2017-11-10 Thread Bergquist, Brett 
https://wiki.jenkins.io/display/JENKINS/IvyTrigger+Plugin

I have privately emails Gregory Boissinot about becoming a maintainer but have 
not heard back.   Here is what I had sent Gregory

I am going to be using this plugin and have already figured out how it is 
mostly designed and working.   I have opened

https://issues.jenkins-ci.org/browse/JENKINS-47794

and have implemented this locally as I mention in the JIRA.   This also takes 
care of

https://issues.jenkins-ci.org/browse/JENKINS-23429

Which was my first stumbling block with the plugin on use with Jenkins running 
on Solaris 10.

I am still learning my way around plugin development, Jenkins architecture, 
Jelly, etc. so I am not that productive at this point but I have been able to 
build with my change and install and run and debug.

One of the features that I would like to add is to make this plugin compatible 
with the new "Pipeline" support of Jenkins 2.x so I am researching what needs 
to be done for that (and having a little trouble going through all of the bits 
and pieces of documentation, blogs, etc.)

I have done no Jenkins plugin development but am starting to learn my way 
around and will probably have to ask questions especially in the area of making 
this plugin Pipeline compatible while maintaining backward compatibility.   But 
I do think I can contribute to this plug development.

My github ID is "bbergquist0930" and my Jenkin infrastructure account is 
"bbergquist".





Canoga Perkins
20600 Prairie Street
Chatsworth, CA 91311
(818) 718-6300

This e-mail and any attached document(s) is confidential and is intended only 
for the review of the party to whom it is addressed. If you have received this 
transmission in error, please notify the sender immediately and discard the 
original message and any attachment(s).

-- 
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/97EB699F861AD841B5908C7CA9C9565604A104377D3C%40VSERVER1.canoga.com.
For more options, visit https://groups.google.com/d/optout.

Re: stack trace in configure system (docker, plugin development)

2017-11-10 Thread Ewelina Wilkosz 
ok, when I build locally I do not get stack trace, something is messed up 
in my Jenkins job or agent :)

On Friday, November 10, 2017 at 8:06:43 PM UTC+1, Ewelina Wilkosz wrote:
>
> right, it does look like a git merge, the thing is, I can't see any 
> conflicts in my repo
> so it's just me not understanding how docker build works, I guess I will 
> have to dig more into the issue
>
> On Friday, November 10, 2017 at 6:27:29 PM UTC+1, Mark Waite wrote:
>>
>> That looks like a failed "git merge".  No idea of the source of that 
>> failed merge, but those markers are used by git when it can't resolve a 
>> merge of a historical file into the current file.
>>
>> Mark Waite
>>
>> On Fri, Nov 10, 2017 at 10:14 AM Ewelina Wilkosz  
>> wrote:
>>
>>> I'm working on dockerizing Configuration as Code plugin, which means I 
>>> create a docker image, based on jenkins:2.60.3, I build the plugin and I 
>>> install it in a Dockerfile: 
>>> https://github.com/jenkinsci/configuration-as-code-plugin/blob/praqma/dev/Dockerfile
>>>
>>> It seems to be working, but I get stack trace in Configure System:
>>>
>>> org.apache.commons.jelly.JellyTagException: 
>>> jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.60.3.jar!/jenkins/model/Jenkins/configure.jelly:59:84:
>>>   org.kohsuke.stapler.ScriptLoadException: 
>>> org.apache.commons.jelly.JellyException: Could not parse Jelly script : 
>>> jar:file:/var/jenkins_home/plugins/configuration-as-code/WEB-INF/lib/configuration-as-code.jar!/org/jenkinsci/plugins/casc/ConfigurationAsCode/index.jelly
>>> at 
>>> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
>>> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
>>> at 
>>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>> at 
>>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>>
>>> (...)
>>>
>>> So I attached to docker container and checked 
>>> /var/jenkins_home/plugins/configuration-as-code/WEB-INF/lib/configuration-as-code.jar!/org/jenkinsci/plugins/casc/ConfigurationAsCode/index.jelly,
>>>  
>>> and in it I can see:
>>>
>>> <<< HEAD
>>>
>>> ${c.name}
>>>
>>> 
>>>
>>>   Implementation of ${c.extensionpoint.simpleName}
>>>
>>> ===
>>>
>>> ${c.name}
>>>
>>> 
>>>
>>>   Implementation of https://jenkins.io/doc/developer/extensions/${c.extensionSource}/#${c.extensionPoint.simpleName.toLowerCase()}
>>> ">${c.extensionPoint.simpleName}
>>>
>>> >>> fork/master
>>>
>>> And I don't understand where it comes from... Complete newbie here. 
>>> Anyone willing to help with troubleshooting?
>>>
>>> -- 
>>> 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/3cb870c9-4e69-413d-a4d2-29e106459725%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/d38be3d9-7821-4def-bf5a-fb76a41bceb1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: stack trace in configure system (docker, plugin development)

2017-11-10 Thread Ewelina Wilkosz 
right, it does look like a git merge, the thing is, I can't see any 
conflicts in my repo
so it's just me not understanding how docker build works, I guess I will 
have to dig more into the issue

On Friday, November 10, 2017 at 6:27:29 PM UTC+1, Mark Waite wrote:
>
> That looks like a failed "git merge".  No idea of the source of that 
> failed merge, but those markers are used by git when it can't resolve a 
> merge of a historical file into the current file.
>
> Mark Waite
>
> On Fri, Nov 10, 2017 at 10:14 AM Ewelina Wilkosz  > wrote:
>
>> I'm working on dockerizing Configuration as Code plugin, which means I 
>> create a docker image, based on jenkins:2.60.3, I build the plugin and I 
>> install it in a Dockerfile: 
>> https://github.com/jenkinsci/configuration-as-code-plugin/blob/praqma/dev/Dockerfile
>>
>> It seems to be working, but I get stack trace in Configure System:
>>
>> org.apache.commons.jelly.JellyTagException: 
>> jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.60.3.jar!/jenkins/model/Jenkins/configure.jelly:59:84:
>>   org.kohsuke.stapler.ScriptLoadException: 
>> org.apache.commons.jelly.JellyException: Could not parse Jelly script : 
>> jar:file:/var/jenkins_home/plugins/configuration-as-code/WEB-INF/lib/configuration-as-code.jar!/org/jenkinsci/plugins/casc/ConfigurationAsCode/index.jelly
>>  at 
>> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
>>  at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
>>  at 
>> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>>  at 
>> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>>
>> (...)
>>
>> So I attached to docker container and checked 
>> /var/jenkins_home/plugins/configuration-as-code/WEB-INF/lib/configuration-as-code.jar!/org/jenkinsci/plugins/casc/ConfigurationAsCode/index.jelly,
>>  
>> and in it I can see:
>>
>> <<< HEAD
>>
>> ${c.name}
>>
>> 
>>
>>   Implementation of ${c.extensionpoint.simpleName}
>>
>> ===
>>
>> ${c.name}
>>
>> 
>>
>>   Implementation of https://jenkins.io/doc/developer/extensions/${c.extensionSource}/#${c.extensionPoint.simpleName.toLowerCase()}
>> ">${c.extensionPoint.simpleName}
>>
>> >>> fork/master
>>
>> And I don't understand where it comes from... Complete newbie here. 
>> Anyone willing to help with troubleshooting?
>>
>> -- 
>> 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/3cb870c9-4e69-413d-a4d2-29e106459725%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/f7554b15-0bb9-4539-ad45-a912dd81733f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: stack trace in configure system (docker, plugin development)

2017-11-10 Thread Daniel Beck 

> On 10. Nov 2017, at 17:12, Ewelina Wilkosz  wrote:
> 
> And I don't understand where it comes from... Complete newbie here. Anyone 
> willing to help with troubleshooting?

Judging from your Dockerfile, I expect that to already be in the file at 
https://github.com/jenkinsci/configuration-as-code-plugin/blob/praqma/dev/Dockerfile#L28
 -- probably a bad merge in your local workspace. Check there.

-- 
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/36B8E23C-FA52-4ABD-8EC7-FD8BC57874DC%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: stack trace in configure system (docker, plugin development)

2017-11-10 Thread Mark Waite 
That looks like a failed "git merge".  No idea of the source of that failed
merge, but those markers are used by git when it can't resolve a merge of a
historical file into the current file.

Mark Waite

On Fri, Nov 10, 2017 at 10:14 AM Ewelina Wilkosz 
wrote:

> I'm working on dockerizing Configuration as Code plugin, which means I
> create a docker image, based on jenkins:2.60.3, I build the plugin and I
> install it in a Dockerfile:
> https://github.com/jenkinsci/configuration-as-code-plugin/blob/praqma/dev/Dockerfile
>
> It seems to be working, but I get stack trace in Configure System:
>
> org.apache.commons.jelly.JellyTagException: 
> jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.60.3.jar!/jenkins/model/Jenkins/configure.jelly:59:84:
>   org.kohsuke.stapler.ScriptLoadException: 
> org.apache.commons.jelly.JellyException: Could not parse Jelly script : 
> jar:file:/var/jenkins_home/plugins/configuration-as-code/WEB-INF/lib/configuration-as-code.jar!/org/jenkinsci/plugins/casc/ConfigurationAsCode/index.jelly
>   at 
> org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
>   at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
>   at 
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
>   at 
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
>
> (...)
>
> So I attached to docker container and checked 
> /var/jenkins_home/plugins/configuration-as-code/WEB-INF/lib/configuration-as-code.jar!/org/jenkinsci/plugins/casc/ConfigurationAsCode/index.jelly,
> and in it I can see:
>
> <<< HEAD
>
> ${c.name}
>
> 
>
>   Implementation of ${c.extensionpoint.simpleName}
>
> ===
>
> ${c.name}
>
> 
>
>   Implementation of https://jenkins.io/doc/developer/extensions/${c.extensionSource}/#${c.extensionPoint.simpleName.toLowerCase()}
> ">${c.extensionPoint.simpleName}
>
> >>> fork/master
>
> And I don't understand where it comes from... Complete newbie here. Anyone
> willing to help with troubleshooting?
>
> --
> 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/3cb870c9-4e69-413d-a4d2-29e106459725%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/CAO49JtFWea-Uj-z_uSmhRN8bsZQ4UTKRLyeOw%3DzfVB%3DstE1cUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

stack trace in configure system (docker, plugin development)

2017-11-10 Thread Ewelina Wilkosz 
I'm working on dockerizing Configuration as Code plugin, which means I 
create a docker image, based on jenkins:2.60.3, I build the plugin and I 
install it in a 
Dockerfile: 
https://github.com/jenkinsci/configuration-as-code-plugin/blob/praqma/dev/Dockerfile

It seems to be working, but I get stack trace in Configure System:

org.apache.commons.jelly.JellyTagException: 
jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.60.3.jar!/jenkins/model/Jenkins/configure.jelly:59:84:
  org.kohsuke.stapler.ScriptLoadException: 
org.apache.commons.jelly.JellyException: Could not parse Jelly script : 
jar:file:/var/jenkins_home/plugins/configuration-as-code/WEB-INF/lib/configuration-as-code.jar!/org/jenkinsci/plugins/casc/ConfigurationAsCode/index.jelly
at 
org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281)
at 
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)
at 
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)

(...)

So I attached to docker container and checked 
/var/jenkins_home/plugins/configuration-as-code/WEB-INF/lib/configuration-as-code.jar!/org/jenkinsci/plugins/casc/ConfigurationAsCode/index.jelly,
 
and in it I can see:

<<< HEAD

${c.name}



  Implementation of ${c.extensionpoint.simpleName}

===

${c.name}



  Implementation of https://jenkins.io/doc/developer/extensions/${c.extensionSource}/#${c.extensionPoint.simpleName.toLowerCase()}">${c.extensionPoint.simpleName}

>>> fork/master

And I don't understand where it comes from... Complete newbie here. Anyone 
willing to help with troubleshooting?

-- 
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/3cb870c9-4e69-413d-a4d2-29e106459725%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

2017-11-10 Thread jxpearce 
 
,.-'"...``~., 
.,.-"..."-., 
.,/...":, 
.,?.., 
.../...,}
 
./..,:`^`..}
 
.../...,:"./
 
..?.__.:`.../ 
./__.(."~-,_..,:`../ 
.../(_"~,_"~,_,:`_/ 
..{.._$;_.."=,_..."-,_...,.-~-,},.~";/} 
...((.*~_..."=-._..";,,./`/"../ 
...,,,___.`~,.."~.,`.}../ 
(`=-,,...`(..;_,,-" 
/.`~,..`-./ 
.`~.*-,.|,./.,__ 
,,_..}.>-._...|..`=~-, 
.`=~-,__..`,. 
...`=~-,,.,... 
`:,,...`..__
 
.`=-,...,%`>--==`` 
_..._,-%...` 
..., 

On Friday, November 10, 2017 at 8:54:23 AM UTC-8, Daniel Beck wrote:
>
>
> > On 10. Nov 2017, at 16:53, jxpe...@godaddy.com  wrote: 
> > 
> > since you asked 
>
> They didn't, this is just spam. Just check where the 'Jenkins' link leads. 
>
>

-- 
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/b572799c-f40b-4811-8b9b-b624336212cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

2017-11-10 Thread Daniel Beck 

> On 10. Nov 2017, at 17:54, Daniel Beck  wrote:
> 
>  this is just spam

And the text is just copied and pasted from a quora.com answer from 2011.

-- 
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/409E6B7C-4E3C-49F1-BFD5-F1B641A20150%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

2017-11-10 Thread Daniel Beck 

> On 10. Nov 2017, at 16:53, jxpea...@godaddy.com wrote:
> 
> since you asked

They didn't, this is just spam. Just check where the 'Jenkins' link leads.

-- 
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/707FEA8B-4938-470B-B983-C020A2D66BE3%40beckweb.net.
For more options, visit https://groups.google.com/d/optout.

Re: For Continuous Integration Should I Use a Jenkin or Hudson?

2017-11-10 Thread jxpearce 
The Jenkins Users list might be a better place for this question, but since 
you asked I can tell you what we're doing.

I'm not sure what you mean by a Corporate Environment. I work for a medium 
size corporation, 800ish engineers (I think) and we use Jenkins for 
everything. We choose to manage it ourselves, but Cloudbees offers a 
managed version if you want that. It's nice to have both options. 

It's also nice that Jenkins is a well run open source project. The main 
developers seem to be easy to access, and you have a problem with a plugin, 
you can always submit a PR to fix it yourself.

On Thursday, November 9, 2017 at 9:51:04 PM UTC-8, Naresh K wrote:
>
> So many are getting Confused in Choosing Whether Jenkin or Hudson for 
> Continuous Integration. Here is the solution for this and it is only 
> according to my View only. If any mistake is there means Please Let me Know 
> So that i will Correct it. 
>
> When the Jenkins/Hudson divorce came about, most of the Hudson developers 
> (including, crucially, the original creator of the project, Kohsuke 
> Kawaguchi) moved on to Jenkins. 
>
> Since the split, Jenkins  has the 
> most work, most commits, better community, better plugins, and so on. 
>
> Hudson is tied to Oracle and its corporate infrastructure. The project 
> will attempt to go a more "enterprise" route, with fewer releases but more 
> testing and an emphasis on backward compatibility, possibly more Eclipse 
> integration. If your project is in a more corporate environment, a case 
> could be made that you should use Hudson. 
>
> Otherwise, stick with (or upgrade to) Jenkins. This is what the majority 
> of the community is moving to.
>

-- 
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/47cbc371-7452-4d61-add6-bc4c3043e6f6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Plugin- License Policy

2017-11-10 Thread Victor Martinez 
You can find the script in the below repo:
- https://github.com/v1v/license-crawler

Just to clarify, it takes about 50 minutes (main reason: it looks for 
license section in the pom.xml file, if it doesn't exit, then it does 
expand the effective-pom and look for the license section). It does also 
look for LICENSE files using the GH restAPI)

Cheers

-- 
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/7a9fdcc0-1a95-4492-917b-4cedda991878%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Backporting for LTS 2.89.1 started

2017-11-10 Thread Oliver Gondža 
Backporting has started and the RC is scheduled for 2017-11-22. Note 
that schedule for .2 might be modified as keeping the constant pace 
would require the RC testing during holidays.


Candidates: https://issues.jenkins-ci.org/issues/?filter=12146
Fixed: https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.89.1-fixed
Rejected: 
https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.89.1-rejected

--
oliver

--
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/839344fa-4026-8282-8a61-9e190769b499%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [configuration-as-code] Descriptors configuration

2017-11-10 Thread nicolas de loof 
Right, so hopefully we already have docs on best practices for plugin
developers ;)

An issue remain. Let's consider I refactor Mailer plugin to adopt this
approach (see
https://github.com/ndeloof/mailer-plugin/commit/ffc57e0ff1cb1b74dc1d6fdcb2329a5b9141daaa),
with a new nested optionalProperty describable SMTPAuthentication

{ username, password } to replace nullable attributes in Mailer$Descriptor

I'll rewrite configure method as :

public boolean configure(StaplerRequest req, JSONObject json) throws
FormException {

req.bindJSON(this, json);
save();
return true;
}


(by the way, shouldn't this be the default implementation ?)

But with this, if I UNCHECK the optional property, no
"authentication" value is posted to JSON form, and I don't get
SMTPAuthentication reset to null in my descriptor.
AFAICT Describable mechanism  documented here
 only
supports immutable components.

Does this mean Descriptors would need to include an extra "reset" method to
set all attributes to null / default value ?
This also make me think this configuration mechanism isn't atomic, and
there's some possible race condition for related attributes to have
inconsistent values seen from another thread while the configuration is
being changed.

As a resume, and considering recommended and well adopted approach to
retrieve a Descriptor is to use
Jenkins.getInstance.getDescriptor(describable), not referring to some final
static constant, I wonder we could get the Descriptor.configure mechanism
to rely on @DataBoundConstructors just like Describable do.
This means we will need to (atomically) swap Descriptor instance in
ExtensionList. Maybe this has too much impact (extensionLists Memoizer
would need to be reset) ? Or maybe there's a better way to support
re-configuration with @DataBound ?



2017-11-10 0:13 GMT+01:00 Jesse Glick :

> On Thu, Nov 9, 2017 at 9:45 AM, nicolas de loof
>  wrote:
> > As a sample for this
> > discussion let's consider Mailer plugin build step
>
> And the comment
>
> > this code is brain dead
>
> :-)
>
> > Until you have some clever hack to suggest, it looks to me we will need
> to
> > provide guidance for plugin developers for "best practice to implement
> > Descriptor" so it can be used by configuration-as-code.
>
> A lot of this is actually identical to the constraints needed to make
> code compatible with *Pipeline Syntax*, and more broadly with the
> `DescribableModel` API. See:
>
> https://jenkins.io/doc/developer/plugin-development/pipeline-integration/#
> constructor-vs-setters
>
> > I sounds to me we don't have any way to provide a generic mechanism
> without
> > changes to Descriptors in core/plugins - yes I known, this means hundreds
> > pull-requests
>
> Start filing them…
>
> The main difficulty is not in writing correct code, which is in fact
> usually easier than the old way, it is in maintaining deserialization
> compatibility. So you need to use `readResolve` and occasionally even
> XStream tricks to load old, awkward property layouts into a logical
> revised structure.
>
> > To reuse Mailer$Descriptor sample, this would require useSMTPAuth to be
> an
> > actual nested data structure, not just a boolean flag to configure some
> > optional attributes. This means that it would have to define a nested
> java
> > class to own smtpAuthUserName + smtpAuthPasswordSecret attributes.
>
> Yes. `f:optionalProperty` and a nested `Describable`. See for example
> `HeteroList` in `ui-samples`.
>
> --
> 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/CANfRfr3Vq3AVbvMFQDiB2xApKiqT%
> 3Dswcsr%3D606V5OuKVrkKZmA%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/CANMVJz%3DDrRF%3DXM8rp0A-zyt4D6wTXTBU2eQ_YFZ%3DHjQyHxzGpw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.