Matrix build with multiple variables on one axis

[krislodz]

Is there a way to define a multiple variables for one axis in matrix build, 
like this:
Person_Axis: name,surname,address

So that when specifying concrete values for the axis it would be:
name=n1,surname=s1,address=a1
name=n2,surname=s2,address=a2

The solution of specifying 3 different axes for this example is not the one 
I would like because of the filtering and confusion that it might bring to 
the users.

So far I tried specifying it like that:
Person_Axis: n1,s1,a1 n2,s2,a2
and then using Groovy script or Windows batch script to split the value and 
assign to the variables name,surname and address but unfortunately I cannot 
give it to work because of the NullPointerException when I try to access 
configurations:
https://issues.jenkins-ci.org/browse/JENKINS-16772?focusedCommentId=13#comment-13

Any ideas?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Jenkins setup for people

[rakhee Kulkarni]

Hi,

I have a setup issue where I am missing some plugins for people. I have 
Jenkins 1.426, when I click on people I get

Status Code: 500Exception: 
Stacktrace:

java.lang.NoSuchMethodError: 
hudson.tasks.Mailer$UserProperty.hasExplicitlyConfiguredAddress()Z


Please advise.


Thanks,

Rakhee

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Aggregate report/view of regex-matched builds/jobs

[Pete Akey]

I would like a view or report that will allow me to choose which tests' results 
to view, viewing their latest xml or console output, and possibly filtering out 
certain output (allowing me to only display exactly what failed).

I think this guy was on the same track: 
https://issues.jenkins-ci.org/browse/JENKINS-3015 when he posted the feature 
request if you need my question phrased differently.

Any suggestions?

Thanks,
Pete

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

File Patching

[Aaron Golub]

I currently use Jenkins for CI, Jira for ticketing and SVN as a repository. 
 I'm wondering if there is a way to patch a specific files from SVN to a 
live server based on the jira issue and the latest files comitted via SVN. 
 Is there a plugin for this? Any help would be greatly appreciated. Thanks!
A

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

using puppet/svn and Jenkins with slaves

[Kamal Ahmed]

Hi,

Here is a scenario that i am currently working with:

I have a CentOs Slave host, where puppet updates/control the directory 
/extra/code/developer
then i run "mvn clean compile".

The PERL5LIB is ALSO set by puppet, to point to /extra/code/developer

Now, when i setup the slave, the name of the slave node "vm-devqa01" gets 
appended to the ROOT , which is 


/extra/code/

BUT puppet will never update there, so.

Can i have the root as /extra/code and name the node "developer" ? if i DO , 
then i have to name ALL the slave nodes "developer" 


Any ideas ?

Thanks,
-Kamal.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Perform a single svn checkout in a multi-configuration project

[Les Mikesell]

On Wed, Apr 24, 2013 at 10:50 AM, Les Mikesell  wrote:
>>>
>> Alright. So there just is no way to have a multi configuration job reuse the
>> same checkout?
>
> No, in the general case, the jobs will run on different slaves and may
> be checked out with different native line endings.  And they may run
> in parallel so they can't use the same workspace.  If you are really
> just doing everything in one build on one host, why not write your own
> script wrapper to handle the variations?
>

On a second thought - maybe you could make it work with "Use custom
workspace" and "." for the "directory for sub-builds" (see
https://issues.jenkins-ci.org/browse/JENKINS-8317).   But you may need
to think about the checkout strategy (probably revert before update)
and use the 'run each configuration sequentially' option.

--
   Les Mikesell
  lesmikes...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

[windycity]

Attach log.


Jessica
On Wednesday, April 24, 2013 4:04:04 PM UTC-5, windycity wrote:
>
> We are using tomcat, I have logs at 
> tomcat/apache-tomcat-6.0.35/logs/catalina.out, is that the right one? But 
> this one does not have any Jenkins error. Build #23 is the trouble one.
>
> Jessica
>
> On Wednesday, April 24, 2013 3:36:18 PM UTC-5, slide wrote:
>>
>> No, I mean the actual stderr type logs for the Jenkins app itself, it 
>> would be in different places depending on how you are running Jenkins. 
>> Could be in the tomcat logs, etc.
>>
>>
>> On Wed, Apr 24, 2013 at 1:33 PM, windycity  wrote:
>>
>>> By jenkins log, do you mean $JENKINS_HOME/jobs/project/builds/#/log 
>>> file?  If this is the file you refer, it does have build errors, but 
>>> sending mail seems fine.
>>>
>>> Sending e-mails to: j...@cboe.com
>>> channel stopped
>>> Sending e-mails to: j...@cboe.com
>>> Email was triggered for: Failure
>>> Sending email for trigger: Failure
>>> Sending email to: j...@cboe.com
>>> Finished: FAILURE
>>>
>>> If this is not the log you refer, would you please let me know where 
>>> should be the log file?
>>>
>>> Thanks much,
>>>
>>> Jessica
>>>
>>>
>>>
>>> On Wednesday, April 24, 2013 3:13:54 PM UTC-5, slide wrote:
>>>
 Do you have any errors in jenkins logs?


 On Wed, Apr 24, 2013 at 12:43 PM, windycity  wrote:

> I am looking at this file, actually, I figure 
>
> ${JELLY_SCRIPT,template="**html"}
>
> is the problem, if I get rid of this, everything seems working, though 
> I do not understand why. Somebody else put this in global configuration, 
> maybe this format is wrong, maybe it should be ${JELLY_SCRIPT, html}?
>
>
>  Following is the content of ExtendedEmailPublisher xml file from the 
> root of JENKINS_HOME
>
> Thanks much!
>
> Jessica
>
> 
>  plugin="email-ext@2.28">
>   
> http://openjdk2a:**8081/jenkins/
> 
>   address not configured yet 
> 
>   false
>   text/html<**/defaultContentType>
>   ${MAVEN_**PREBUILD_VERSION} $PROJECT_NAME - Build # 
> $BUILD_NUMBER - $BUILD_STATUS!
>   $PROJECT_NAME ${MAVEN_PREBUILD_VERSION}  - Build # 
> $BUILD_NUMBER - $BUILD_STATUS:
> 
> Check console output at $BUILD_URL to view the results.
> 
> ${JELLY_SCRIPT,template="**html"}
>   -1
>   j...@cboe.com
>
>   
>   false<**/overrideGlobalSettings>
>   false
>   false
>   false
> 
>
>
>
> On Wednesday, April 24, 2013 2:33:08 PM UTC-5, slide wrote:
>
>> My apologies, I need the ExtendedEmailPublisher xml file from the 
>> root of JENKINS_HOME.
>>
>>
>> On Wed, Apr 24, 2013 at 10:03 AM, windycity  wrote:
>>
>>>
>>> Here attached are the global and project config files, please let me 
>>> know what is wrong.
>>>
>>> Thanks much for all your help!
>>>
>>> Jessica
>>>
>>>
>>> On Wednesday, April 24, 2013 8:59:51 AM UTC-5, slide wrote:
>>>
 pre-build/post build added token 
 MIME-Version: 1.0 
 Content-Type: multipart/alternative; 
 boundary="=_Part_**89_9798859.1366811681215" 

 --=_Part_89_9798859.**1366811681215 
 Content-Type: text/plain; charset="utf-8" 
 Content-Transfer-Encoding: 7bit 

 They are expanded the same way, so I need more information (like 
 your 
 global and project config XML) to try and determine the issue. 

 Sent from my Windows Phone 
 From: windycity 
 Sent: 4/24/2013 6:54 
 To: jenkins...@googlegroups.**com 
 Subject: jenkins e-mail ext DEFAULT_CONTENT does not expand 
 pre-build/post build added token 
 I use jenkin's configuration pre-build and post build "Execute 
 Groovy 
 System Script"-> command to get a token $MAVE_PREBUIL_VERSION and 
 $MAVEN_POSTBUILD_MAVEN, and put this at e-mail ext plugin 
 configuration. In 
 both global and project session, DEFAULT_SUBJECT can extent these 
 Tokens, 
 but DEFAULT_CONTENT can not, is this a known issue or I am not 
 using it 
 right? 

 $DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION}, 
 ${MAVEN_POSTBUILD_VERSION} 
 Above expand the token, but following does not 


 $DEFAULT_CONTENT, ${MAVEN_PREBUILD_VERSION} 

 Thanks in advance, 

 jessica 

 -- 
 You received this message because you are subscribed to the Google 
 Groups "Jenkins Users" group. 
 To unsubscribe from this group and stop receiving emails from it, 
 send 
 an email to jenkinsci-use...@**googlegroups.com. 
 For more options, visit https://groups.google.com/**grou*

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

[windycity]

We are using tomcat, I have logs at 
tomcat/apache-tomcat-6.0.35/logs/catalina.out, is that the right one? But 
this one does not have any Jenkins error. Build #23 is the trouble one.

Jessica

On Wednesday, April 24, 2013 3:36:18 PM UTC-5, slide wrote:
>
> No, I mean the actual stderr type logs for the Jenkins app itself, it 
> would be in different places depending on how you are running Jenkins. 
> Could be in the tomcat logs, etc.
>
>
> On Wed, Apr 24, 2013 at 1:33 PM, windycity 
> > wrote:
>
>> By jenkins log, do you mean $JENKINS_HOME/jobs/project/builds/#/log 
>> file?  If this is the file you refer, it does have build errors, but 
>> sending mail seems fine.
>>
>> Sending e-mails to: j...@cboe.com 
>> channel stopped
>> Sending e-mails to: j...@cboe.com 
>> Email was triggered for: Failure
>> Sending email for trigger: Failure
>> Sending email to: j...@cboe.com 
>> Finished: FAILURE
>>
>> If this is not the log you refer, would you please let me know where 
>> should be the log file?
>>
>> Thanks much,
>>
>> Jessica
>>
>>
>>
>> On Wednesday, April 24, 2013 3:13:54 PM UTC-5, slide wrote:
>>
>>> Do you have any errors in jenkins logs?
>>>
>>>
>>> On Wed, Apr 24, 2013 at 12:43 PM, windycity  wrote:
>>>
 I am looking at this file, actually, I figure 

 ${JELLY_SCRIPT,template="**html"}

 is the problem, if I get rid of this, everything seems working, though 
 I do not understand why. Somebody else put this in global configuration, 
 maybe this format is wrong, maybe it should be ${JELLY_SCRIPT, html}?


  Following is the content of ExtendedEmailPublisher xml file from the 
 root of JENKINS_HOME

 Thanks much!

 Jessica

 
 >>> plugin="email-ext@2.28">
   
 http://openjdk2a:**8081/jenkins/
 
   address not configured yet 
   false
   text/html<**/defaultContentType>
   ${MAVEN_**PREBUILD_VERSION} $PROJECT_NAME - Build # 
 $BUILD_NUMBER - $BUILD_STATUS!
   $PROJECT_NAME ${MAVEN_PREBUILD_VERSION}  - Build # 
 $BUILD_NUMBER - $BUILD_STATUS:
 
 Check console output at $BUILD_URL to view the results.
 
 ${JELLY_SCRIPT,template="**html"}
   -1
   j...@cboe.com

   
   false<**/overrideGlobalSettings>
   false
   false
   false
 



 On Wednesday, April 24, 2013 2:33:08 PM UTC-5, slide wrote:

> My apologies, I need the ExtendedEmailPublisher xml file from the root 
> of JENKINS_HOME.
>
>
> On Wed, Apr 24, 2013 at 10:03 AM, windycity  wrote:
>
>>
>> Here attached are the global and project config files, please let me 
>> know what is wrong.
>>
>> Thanks much for all your help!
>>
>> Jessica
>>
>>
>> On Wednesday, April 24, 2013 8:59:51 AM UTC-5, slide wrote:
>>
>>> pre-build/post build added token 
>>> MIME-Version: 1.0 
>>> Content-Type: multipart/alternative; 
>>> boundary="=_Part_**89_9798859.1366811681215" 
>>>
>>> --=_Part_89_9798859.**1366811681215 
>>> Content-Type: text/plain; charset="utf-8" 
>>> Content-Transfer-Encoding: 7bit 
>>>
>>> They are expanded the same way, so I need more information (like 
>>> your 
>>> global and project config XML) to try and determine the issue. 
>>>
>>> Sent from my Windows Phone 
>>> From: windycity 
>>> Sent: 4/24/2013 6:54 
>>> To: jenkins...@googlegroups.**com 
>>> Subject: jenkins e-mail ext DEFAULT_CONTENT does not expand 
>>> pre-build/post build added token 
>>> I use jenkin's configuration pre-build and post build "Execute 
>>> Groovy 
>>> System Script"-> command to get a token $MAVE_PREBUIL_VERSION and 
>>> $MAVEN_POSTBUILD_MAVEN, and put this at e-mail ext plugin 
>>> configuration. In 
>>> both global and project session, DEFAULT_SUBJECT can extent these 
>>> Tokens, 
>>> but DEFAULT_CONTENT can not, is this a known issue or I am not using 
>>> it 
>>> right? 
>>>
>>> $DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION}, 
>>> ${MAVEN_POSTBUILD_VERSION} 
>>> Above expand the token, but following does not 
>>>
>>>
>>> $DEFAULT_CONTENT, ${MAVEN_PREBUILD_VERSION} 
>>>
>>> Thanks in advance, 
>>>
>>> jessica 
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Users" group. 
>>> To unsubscribe from this group and stop receiving emails from it, 
>>> send 
>>> an email to jenkinsci-use...@**googlegroups.com. 
>>> For more options, visit https://groups.google.com/**grou
>>> ps/opt_out . 
>>>
>>>
>>>
>>> --=_Part_89_9798859.**1366811681215 
>>> Content-Type: text/html; charset="utf-8" 
>>> Content-Transfer-Encoding: quoted-printable 
>

Re: Persist job results after the slave is destroyed

[Les Mikesell]

On Wed, Apr 24, 2013 at 12:12 PM, Kamal Ahmed  wrote:
>
> I just wanted to confirm, if i am running a max of 100 Jobs , with unit
> tests, static analysis, WebDriver tests, and then at some point destroy the
> slave to create a brand new one, would the results be persisted on the
> Jenkins Master ? , and when the new Slave ( Identical to the old one ) Comes
> back on, would it seem seemless ?

You can have multiple slaves and jenkins won't care where each job
runs - and will organize the logs and console output.   If you want
something from the workspace saved on the master, use the post-build
'archive the artifacts'  and specify what you want.

--
   Les Mikesell
 lesmikes...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

[Slide]

No, I mean the actual stderr type logs for the Jenkins app itself, it would
be in different places depending on how you are running Jenkins. Could be
in the tomcat logs, etc.


On Wed, Apr 24, 2013 at 1:33 PM, windycity  wrote:

> By jenkins log, do you mean $JENKINS_HOME/jobs/project/builds/#/log file?
> If this is the file you refer, it does have build errors, but sending mail
> seems fine.
>
> Sending e-mails to: j...@cboe.com
> channel stopped
> Sending e-mails to: j...@cboe.com
> Email was triggered for: Failure
> Sending email for trigger: Failure
> Sending email to: j...@cboe.com
> Finished: FAILURE
>
> If this is not the log you refer, would you please let me know where
> should be the log file?
>
> Thanks much,
>
> Jessica
>
>
>
> On Wednesday, April 24, 2013 3:13:54 PM UTC-5, slide wrote:
>
>> Do you have any errors in jenkins logs?
>>
>>
>> On Wed, Apr 24, 2013 at 12:43 PM, windycity  wrote:
>>
>>> I am looking at this file, actually, I figure
>>>
>>> ${JELLY_SCRIPT,template="**html"}
>>>
>>> is the problem, if I get rid of this, everything seems working, though I
>>> do not understand why. Somebody else put this in global configuration,
>>> maybe this format is wrong, maybe it should be ${JELLY_SCRIPT, html}?
>>>
>>>
>>>  Following is the content of ExtendedEmailPublisher xml file from the
>>> root of JENKINS_HOME
>>>
>>> Thanks much!
>>>
>>> Jessica
>>>
>>> 
>>> >> plugin="email-ext@2.28">
>>>   
>>> http://openjdk2a:**8081/jenkins/
>>> 
>>>   address not configured yet 
>>>   false
>>>   text/html<**/defaultContentType>
>>>   ${MAVEN_**PREBUILD_VERSION} $PROJECT_NAME - Build #
>>> $BUILD_NUMBER - $BUILD_STATUS!
>>>   $PROJECT_NAME ${MAVEN_PREBUILD_VERSION}  - Build #
>>> $BUILD_NUMBER - $BUILD_STATUS:
>>> 
>>> Check console output at $BUILD_URL to view the results.
>>> 
>>> ${JELLY_SCRIPT,template="**html"}
>>>   -1
>>>   j...@cboe.com
>>>
>>>   
>>>   false<**/overrideGlobalSettings>
>>>   false
>>>   false
>>>   false
>>> 
>>>
>>>
>>>
>>> On Wednesday, April 24, 2013 2:33:08 PM UTC-5, slide wrote:
>>>
 My apologies, I need the ExtendedEmailPublisher xml file from the root
 of JENKINS_HOME.


 On Wed, Apr 24, 2013 at 10:03 AM, windycity  wrote:

>
> Here attached are the global and project config files, please let me
> know what is wrong.
>
> Thanks much for all your help!
>
> Jessica
>
>
> On Wednesday, April 24, 2013 8:59:51 AM UTC-5, slide wrote:
>
>> pre-build/post build added token
>> MIME-Version: 1.0
>> Content-Type: multipart/alternative;
>> boundary="=_Part_**89_9798859.1366811681215"
>>
>> --=_Part_89_9798859.**1366811681215
>> Content-Type: text/plain; charset="utf-8"
>> Content-Transfer-Encoding: 7bit
>>
>> They are expanded the same way, so I need more information (like your
>> global and project config XML) to try and determine the issue.
>>
>> Sent from my Windows Phone
>> From: windycity
>> Sent: 4/24/2013 6:54
>> To: jenkins...@googlegroups.**com
>> Subject: jenkins e-mail ext DEFAULT_CONTENT does not expand
>> pre-build/post build added token
>> I use jenkin's configuration pre-build and post build "Execute Groovy
>> System Script"-> command to get a token $MAVE_PREBUIL_VERSION and
>> $MAVEN_POSTBUILD_MAVEN, and put this at e-mail ext plugin
>> configuration. In
>> both global and project session, DEFAULT_SUBJECT can extent these
>> Tokens,
>> but DEFAULT_CONTENT can not, is this a known issue or I am not using
>> it
>> right?
>>
>> $DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION},
>> ${MAVEN_POSTBUILD_VERSION}
>> Above expand the token, but following does not
>>
>>
>> $DEFAULT_CONTENT, ${MAVEN_PREBUILD_VERSION}
>>
>> Thanks in advance,
>>
>> jessica
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send
>> an email to jenkinsci-use...@**googlegroups.com.
>> For more options, visit https://groups.google.com/**grou
>> ps/opt_out .
>>
>>
>>
>> --=_Part_89_9798859.**1366811681215
>> Content-Type: text/html; charset="utf-8"
>> Content-Transfer-Encoding: quoted-printable
>>
>> > http-equiv=3D"Cont=
>> ent-Type"><**div style=3D"font-family:
>> Calibri,sans-serif; =
>> font-size: 11pt;">They are expanded the same way, so I need more
>> informatio=
>> n (like your global and project config XML) to try and determine the
>> issue.=
>> Sent from my Windows Phone> style=3D"font-f=
>> amily: Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">From:
>> > >> 10pt;">windycity=
>> > 10pt; =

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

[windycity]

By jenkins log, do you mean $JENKINS_HOME/jobs/project/builds/#/log file?  
If this is the file you refer, it does have build errors, but sending mail 
seems fine.

Sending e-mails to: j...@cboe.com
channel stopped
Sending e-mails to: j...@cboe.com
Email was triggered for: Failure
Sending email for trigger: Failure
Sending email to: j...@cboe.com
Finished: FAILURE

If this is not the log you refer, would you please let me know where should 
be the log file?

Thanks much,

Jessica


On Wednesday, April 24, 2013 3:13:54 PM UTC-5, slide wrote:
>
> Do you have any errors in jenkins logs?
>
>
> On Wed, Apr 24, 2013 at 12:43 PM, windycity 
> > wrote:
>
>> I am looking at this file, actually, I figure 
>>
>> ${JELLY_SCRIPT,template="html"}
>>
>> is the problem, if I get rid of this, everything seems working, though I 
>> do not understand why. Somebody else put this in global configuration, 
>> maybe this format is wrong, maybe it should be ${JELLY_SCRIPT, html}?
>>
>>
>>  Following is the content of ExtendedEmailPublisher xml file from the 
>> root of JENKINS_HOME
>>
>> Thanks much!
>>
>> Jessica
>>
>> 
>> > plugin="email-ext@2.28">
>>   http://openjdk2a:8081/jenkins/
>>   address not configured yet 
>>   false
>>   text/html
>>   ${MAVEN_PREBUILD_VERSION} $PROJECT_NAME - Build # 
>> $BUILD_NUMBER - $BUILD_STATUS!
>>   $PROJECT_NAME ${MAVEN_PREBUILD_VERSION}  - Build # 
>> $BUILD_NUMBER - $BUILD_STATUS:
>> 
>> Check console output at $BUILD_URL to view the results.
>> 
>> ${JELLY_SCRIPT,template="html"}
>>   -1
>>   j...@cboe.com 
>>   
>>   false
>>   false
>>   false
>>   false
>> 
>>
>>
>>
>> On Wednesday, April 24, 2013 2:33:08 PM UTC-5, slide wrote:
>>
>>> My apologies, I need the ExtendedEmailPublisher xml file from the root 
>>> of JENKINS_HOME.
>>>
>>>
>>> On Wed, Apr 24, 2013 at 10:03 AM, windycity  wrote:
>>>

 Here attached are the global and project config files, please let me 
 know what is wrong.

 Thanks much for all your help!

 Jessica


 On Wednesday, April 24, 2013 8:59:51 AM UTC-5, slide wrote:

> pre-build/post build added token 
> MIME-Version: 1.0 
> Content-Type: multipart/alternative; 
> boundary="=_Part_**8**9_9798859.1366811681215" 
>
> --=_Part_89_9798859.**136681**1681215 
> Content-Type: text/plain; charset="utf-8" 
> Content-Transfer-Encoding: 7bit 
>
> They are expanded the same way, so I need more information (like your 
> global and project config XML) to try and determine the issue. 
>
> Sent from my Windows Phone 
> From: windycity 
> Sent: 4/24/2013 6:54 
> To: jenkins...@googlegroups.**com 
> Subject: jenkins e-mail ext DEFAULT_CONTENT does not expand 
> pre-build/post build added token 
> I use jenkin's configuration pre-build and post build "Execute Groovy 
> System Script"-> command to get a token $MAVE_PREBUIL_VERSION and 
> $MAVEN_POSTBUILD_MAVEN, and put this at e-mail ext plugin 
> configuration. In 
> both global and project session, DEFAULT_SUBJECT can extent these 
> Tokens, 
> but DEFAULT_CONTENT can not, is this a known issue or I am not using 
> it 
> right? 
>
> $DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION}, 
> ${MAVEN_POSTBUILD_VERSION} 
> Above expand the token, but following does not 
>
>
> $DEFAULT_CONTENT, ${MAVEN_PREBUILD_VERSION} 
>
> Thanks in advance, 
>
> jessica 
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "Jenkins Users" group. 
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to jenkinsci-use...@**googlegroups.**com. 
> For more options, visit 
> https://groups.google.com/**grou**ps/opt_out.
>  
>
>
>
>
> --=_Part_89_9798859.**136681**1681215 
> Content-Type: text/html; charset="utf-8" 
> Content-Transfer-Encoding: quoted-printable 
>
>  http-equiv=3D"Cont= 
> ent-Type"><**d**iv style=3D"font-family: 
> Calibri,sans-serif; = 
> font-size: 11pt;">They are expanded the same way, so I need more 
> informatio= 
> n (like your global and project config XML) to try and determine the 
> issue.= 
> Sent from my Windows Phone style=3D"font-f= 
> amily: Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">From: 
>  > 10pt;">windycity= 
>  10pt; = 
> font-weight: bold;">Sent:  Tahoma,sans-se= 
> rif; font-size: 10pt;">4/24/2013 6:54 style=3D"font-family:= 
>  Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">To: 
>  tyle=3D"font-family: Tahoma,sans-serif; font-size: 
> 10pt;">jenkinsci-users@g= 
> ooglegroups.com<**spa**n style=3D"font-family: 
> Tahoma,sans-serif; fo= 
> nt-size: 10pt; font-weight: bold;">Subject:  style=3D"font-fam

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

[Slide]

Do you have any errors in jenkins logs?


On Wed, Apr 24, 2013 at 12:43 PM, windycity  wrote:

> I am looking at this file, actually, I figure
>
> ${JELLY_SCRIPT,template="html"}
>
> is the problem, if I get rid of this, everything seems working, though I
> do not understand why. Somebody else put this in global configuration,
> maybe this format is wrong, maybe it should be ${JELLY_SCRIPT, html}?
>
>
>  Following is the content of ExtendedEmailPublisher xml file from the root
> of JENKINS_HOME
>
> Thanks much!
>
> Jessica
>
> 
>  plugin="email-ext@2.28">
>   http://openjdk2a:8081/jenkins/
>   address not configured yet 
>   false
>   text/html
>   ${MAVEN_PREBUILD_VERSION} $PROJECT_NAME - Build #
> $BUILD_NUMBER - $BUILD_STATUS!
>   $PROJECT_NAME ${MAVEN_PREBUILD_VERSION}  - Build #
> $BUILD_NUMBER - $BUILD_STATUS:
> 
> Check console output at $BUILD_URL to view the results.
> 
> ${JELLY_SCRIPT,template="html"}
>   -1
>   j...@cboe.com
>   
>   false
>   false
>   false
>   false
> 
>
>
>
> On Wednesday, April 24, 2013 2:33:08 PM UTC-5, slide wrote:
>
>> My apologies, I need the ExtendedEmailPublisher xml file from the root of
>> JENKINS_HOME.
>>
>>
>> On Wed, Apr 24, 2013 at 10:03 AM, windycity  wrote:
>>
>>>
>>> Here attached are the global and project config files, please let me
>>> know what is wrong.
>>>
>>> Thanks much for all your help!
>>>
>>> Jessica
>>>
>>>
>>> On Wednesday, April 24, 2013 8:59:51 AM UTC-5, slide wrote:
>>>
 pre-build/post build added token
 MIME-Version: 1.0
 Content-Type: multipart/alternative;
 boundary="=_Part_**8**9_9798859.1366811681215"

 --=_Part_89_9798859.**136681**1681215
 Content-Type: text/plain; charset="utf-8"
 Content-Transfer-Encoding: 7bit

 They are expanded the same way, so I need more information (like your
 global and project config XML) to try and determine the issue.

 Sent from my Windows Phone
 From: windycity
 Sent: 4/24/2013 6:54
 To: jenkins...@googlegroups.**com
 Subject: jenkins e-mail ext DEFAULT_CONTENT does not expand
 pre-build/post build added token
 I use jenkin's configuration pre-build and post build "Execute Groovy
 System Script"-> command to get a token $MAVE_PREBUIL_VERSION and
 $MAVEN_POSTBUILD_MAVEN, and put this at e-mail ext plugin
 configuration. In
 both global and project session, DEFAULT_SUBJECT can extent these
 Tokens,
 but DEFAULT_CONTENT can not, is this a known issue or I am not using it
 right?

 $DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION}, ${MAVEN_POSTBUILD_VERSION}
 Above expand the token, but following does not


 $DEFAULT_CONTENT, ${MAVEN_PREBUILD_VERSION}

 Thanks in advance,

 jessica

 --
 You received this message because you are subscribed to the Google
 Groups "Jenkins Users" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to jenkinsci-use...@**googlegroups.**com.
 For more options, visit 
 https://groups.google.com/**grou**ps/opt_out.




 --=_Part_89_9798859.**136681**1681215
 Content-Type: text/html; charset="utf-8"
 Content-Transfer-Encoding: quoted-printable

 >>> http-equiv=3D"Cont=
 ent-Type"><**d**iv style=3D"font-family:
 Calibri,sans-serif; =
 font-size: 11pt;">They are expanded the same way, so I need more
 informatio=
 n (like your global and project config XML) to try and determine the
 issue.=
 Sent from my Windows Phone>>> style=3D"font-f=
 amily: Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">From:
 >>>  10pt;">windycity=
 >>> 10pt; =
 font-weight: bold;">Sent: >>> Tahoma,sans-se=
 rif; font-size: 10pt;">4/24/2013 6:54>>> style=3D"font-family:=
  Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">To:
 >>> tyle=3D"font-family: Tahoma,sans-serif; font-size:
 10pt;">jenkinsci-users@g=
 ooglegroups.com<**spa**n style=3D"font-family:
 Tahoma,sans-serif; fo=
 nt-size: 10pt; font-weight: bold;">Subject: >>> style=3D"font-fami=
 ly: Tahoma,sans-serif; font-size: 10pt;">jenkins e-mail ext
 DEFAULT_CONTENT=
  does not expand pre-build/post build added
 token>>> ml>I use jenkin's configuration pre-build and post build "Execute
 Groovy Sy=
 stem Script"-> command to get a token $MAVE_PREBUIL_VERSION and
 $MAVEN_P=
 OSTBUILD_MAVEN, and put this at e-mail ext plugin configuration. In
 both gl=
 obal and project session, DEFAULT_SUBJECT can extent these Tokens, but
 DEFA=
 ULT_CONTENT can not, is this a known issue or I am not using it
 right?<=
 br>$DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION},
 ${MAVEN_POSTBUILD_VERSION} =
 Above expand the token, but following does not$DEFAULT_**
 CONTEN**T,=
  ${MAVEN_PREBUILD_VERSION}Thanks i

Re: Passing parameters to downstream jobs

[Jared Griffith]

Not a problem!


On Wed, Apr 24, 2013 at 12:31 PM, Maureen Barger  wrote:

> I was just reading about that when your reply arrived, thank you!
>
>
> On Wed, Apr 24, 2013 at 1:41 PM, Jared Griffith <
> jgriff...@picsauditing.com> wrote:
>
>> Yeah, I asked this same question before.  Install the Jenkins
>> Parameterized Trigger 
>> plugin.
>> Then in the Post Build Actions section of the job, add the Trigger
>> Parameterized Build on Other Projects.  There are several options you can
>> pass to the down stream jobs from there.
>>  
>>
>>
>> On Wed, Apr 24, 2013 at 10:14 AM, Maureen Barger wrote:
>>
>>> Hi all -
>>> With a job that triggers many downstream jobs, is it possible to set a
>>> string parameter (ie a file path or a release number) in the first job
>>> and pass it on to all of the downstream jobs?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-users+unsubscr...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>
>>>
>>>
>>
>>
>> --
>>
>> Jared Griffith
>> Linux Administrator, PICS Auditing, LLC
>> P: (949) 936-4574
>> C: (909) 653-7814
>>
>> 
>>
>> 17701 Cowan #140 | Irvine, CA | 92614
>>
>> Join PICS on LinkedIn and Twitter!
>>
>> 
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 

Jared Griffith
Linux Administrator, PICS Auditing, LLC
P: (949) 936-4574
C: (909) 653-7814



17701 Cowan #140 | Irvine, CA | 92614

Join PICS on LinkedIn and Twitter!



-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

[windycity]

I am looking at this file, actually, I figure 

${JELLY_SCRIPT,template="html"}

is the problem, if I get rid of this, everything seems working, though I do 
not understand why. Somebody else put this in global configuration, maybe 
this format is wrong, maybe it should be ${JELLY_SCRIPT, html}?


 Following is the content of ExtendedEmailPublisher xml file from the root 
of JENKINS_HOME

Thanks much!

Jessica



  http://openjdk2a:8081/jenkins/
  address not configured yet 
  false
  text/html
  ${MAVEN_PREBUILD_VERSION} $PROJECT_NAME - Build # 
$BUILD_NUMBER - $BUILD_STATUS!
  $PROJECT_NAME ${MAVEN_PREBUILD_VERSION}  - Build # 
$BUILD_NUMBER - $BUILD_STATUS:

Check console output at $BUILD_URL to view the results.

${JELLY_SCRIPT,template="html"}
  -1
  j...@cboe.com
  
  false
  false
  false
  false



On Wednesday, April 24, 2013 2:33:08 PM UTC-5, slide wrote:
>
> My apologies, I need the ExtendedEmailPublisher xml file from the root of 
> JENKINS_HOME.
>
>
> On Wed, Apr 24, 2013 at 10:03 AM, windycity 
> > wrote:
>
>>
>> Here attached are the global and project config files, please let me know 
>> what is wrong.
>>
>> Thanks much for all your help!
>>
>> Jessica
>>
>>
>> On Wednesday, April 24, 2013 8:59:51 AM UTC-5, slide wrote:
>>
>>> pre-build/post build added token 
>>> MIME-Version: 1.0 
>>> Content-Type: multipart/alternative; 
>>> boundary="=_Part_**89_9798859.1366811681215" 
>>>
>>> --=_Part_89_9798859.**1366811681215 
>>> Content-Type: text/plain; charset="utf-8" 
>>> Content-Transfer-Encoding: 7bit 
>>>
>>> They are expanded the same way, so I need more information (like your 
>>> global and project config XML) to try and determine the issue. 
>>>
>>> Sent from my Windows Phone 
>>> From: windycity 
>>> Sent: 4/24/2013 6:54 
>>> To: jenkins...@googlegroups.**com 
>>> Subject: jenkins e-mail ext DEFAULT_CONTENT does not expand 
>>> pre-build/post build added token 
>>> I use jenkin's configuration pre-build and post build "Execute Groovy 
>>> System Script"-> command to get a token $MAVE_PREBUIL_VERSION and 
>>> $MAVEN_POSTBUILD_MAVEN, and put this at e-mail ext plugin configuration. 
>>> In 
>>> both global and project session, DEFAULT_SUBJECT can extent these 
>>> Tokens, 
>>> but DEFAULT_CONTENT can not, is this a known issue or I am not using it 
>>> right? 
>>>
>>> $DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION}, ${MAVEN_POSTBUILD_VERSION} 
>>> Above expand the token, but following does not 
>>>
>>>
>>> $DEFAULT_CONTENT, ${MAVEN_PREBUILD_VERSION} 
>>>
>>> Thanks in advance, 
>>>
>>> jessica 
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Users" group. 
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkinsci-use...@**googlegroups.com. 
>>> For more options, visit 
>>> https://groups.google.com/**groups/opt_out.
>>>  
>>>
>>>
>>>
>>>
>>> --=_Part_89_9798859.**1366811681215 
>>> Content-Type: text/html; charset="utf-8" 
>>> Content-Transfer-Encoding: quoted-printable 
>>>
>>> >> http-equiv=3D"Cont= 
>>> ent-Type"><**div style=3D"font-family: 
>>> Calibri,sans-serif; = 
>>> font-size: 11pt;">They are expanded the same way, so I need more 
>>> informatio= 
>>> n (like your global and project config XML) to try and determine the 
>>> issue.= 
>>> Sent from my Windows Phone>> style=3D"font-f= 
>>> amily: Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">From: 
>>> >> >>> 10pt;">windycity= 
>>> >> 10pt; = 
>>> font-weight: bold;">Sent: >> Tahoma,sans-se= 
>>> rif; font-size: 10pt;">4/24/2013 6:54>> style=3D"font-family:= 
>>>  Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">To: 
>>> >> tyle=3D"font-family: Tahoma,sans-serif; font-size: 
>>> 10pt;">jenkinsci-users@g= 
>>> ooglegroups.com<**span style=3D"font-family: 
>>> Tahoma,sans-serif; fo= 
>>> nt-size: 10pt; font-weight: bold;">Subject: >> style=3D"font-fami= 
>>> ly: Tahoma,sans-serif; font-size: 10pt;">jenkins e-mail ext 
>>> DEFAULT_CONTENT= 
>>>  does not expand pre-build/post build added token>> **ht= 
>>> ml>I use jenkin's configuration pre-build and post build "Execute Groovy 
>>> Sy= 
>>> stem Script"-> command to get a token $MAVE_PREBUIL_VERSION and 
>>> $MAVEN_P= 
>>> OSTBUILD_MAVEN, and put this at e-mail ext plugin configuration. In both 
>>> gl= 
>>> obal and project session, DEFAULT_SUBJECT can extent these Tokens, but 
>>> DEFA= 
>>> ULT_CONTENT can not, is this a known issue or I am not using it 
>>> right?<= 
>>> br>$DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION}, 
>>> ${MAVEN_POSTBUILD_VERSION} = 
>>> Above expand the token, but following does 
>>> not$DEFAULT_**CONTENT,= 
>>>
>>>  ${MAVEN_PREBUILD_VERSION}**Thanks in 
>>> advance,jessica<**br> 
>>>
>>>  
>>>
>>> --  
>>> You received this message because you are subscribed to the Google 
>>> Groups &= 
>>> quot;Jenkins Users" group. 
>>> To unsubscribe from this group and stop receiving emai

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

[Slide]

My apologies, I need the ExtendedEmailPublisher xml file from the root of
JENKINS_HOME.


On Wed, Apr 24, 2013 at 10:03 AM, windycity  wrote:

>
> Here attached are the global and project config files, please let me know
> what is wrong.
>
> Thanks much for all your help!
>
> Jessica
>
>
> On Wednesday, April 24, 2013 8:59:51 AM UTC-5, slide wrote:
>
>> pre-build/post build added token
>> MIME-Version: 1.0
>> Content-Type: multipart/alternative;
>> boundary="=_Part_**89_9798859.1366811681215"
>>
>> --=_Part_89_9798859.**1366811681215
>> Content-Type: text/plain; charset="utf-8"
>> Content-Transfer-Encoding: 7bit
>>
>> They are expanded the same way, so I need more information (like your
>> global and project config XML) to try and determine the issue.
>>
>> Sent from my Windows Phone
>> From: windycity
>> Sent: 4/24/2013 6:54
>> To: jenkins...@googlegroups.**com
>> Subject: jenkins e-mail ext DEFAULT_CONTENT does not expand
>> pre-build/post build added token
>> I use jenkin's configuration pre-build and post build "Execute Groovy
>> System Script"-> command to get a token $MAVE_PREBUIL_VERSION and
>> $MAVEN_POSTBUILD_MAVEN, and put this at e-mail ext plugin configuration.
>> In
>> both global and project session, DEFAULT_SUBJECT can extent these Tokens,
>> but DEFAULT_CONTENT can not, is this a known issue or I am not using it
>> right?
>>
>> $DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION}, ${MAVEN_POSTBUILD_VERSION}
>> Above expand the token, but following does not
>>
>>
>> $DEFAULT_CONTENT, ${MAVEN_PREBUILD_VERSION}
>>
>> Thanks in advance,
>>
>> jessica
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to jenkinsci-use...@**googlegroups.com.
>> For more options, visit 
>> https://groups.google.com/**groups/opt_out.
>>
>>
>>
>>
>> --=_Part_89_9798859.**1366811681215
>> Content-Type: text/html; charset="utf-8"
>> Content-Transfer-Encoding: quoted-printable
>>
>> > http-equiv=3D"Cont=
>> ent-Type"><**div style=3D"font-family:
>> Calibri,sans-serif; =
>> font-size: 11pt;">They are expanded the same way, so I need more
>> informatio=
>> n (like your global and project config XML) to try and determine the
>> issue.=
>> Sent from my Windows Phone> style=3D"font-f=
>> amily: Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">From:
>> > >> 10pt;">windycity=
>> > 10pt; =
>> font-weight: bold;">Sent: > Tahoma,sans-se=
>> rif; font-size: 10pt;">4/24/2013 6:54> style=3D"font-family:=
>>  Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">To: > s=
>> tyle=3D"font-family: Tahoma,sans-serif; font-size:
>> 10pt;">jenkinsci-users@g=
>> ooglegroups.com<**span style=3D"font-family:
>> Tahoma,sans-serif; fo=
>> nt-size: 10pt; font-weight: bold;">Subject: > style=3D"font-fami=
>> ly: Tahoma,sans-serif; font-size: 10pt;">jenkins e-mail ext
>> DEFAULT_CONTENT=
>>  does not expand pre-build/post build added token> **ht=
>> ml>I use jenkin's configuration pre-build and post build "Execute Groovy
>> Sy=
>> stem Script"-> command to get a token $MAVE_PREBUIL_VERSION and
>> $MAVEN_P=
>> OSTBUILD_MAVEN, and put this at e-mail ext plugin configuration. In both
>> gl=
>> obal and project session, DEFAULT_SUBJECT can extent these Tokens, but
>> DEFA=
>> ULT_CONTENT can not, is this a known issue or I am not using it
>> right?<=
>> br>$DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION},
>> ${MAVEN_POSTBUILD_VERSION} =
>> Above expand the token, but following does 
>> not$DEFAULT_**CONTENT,=
>>
>>  ${MAVEN_PREBUILD_VERSION}**Thanks in
>> advance,jessica<**br>
>>
>> 
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups
>> &=
>> quot;Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> e=
>> mail to jenkinsci-use...@**googlegroups.com.
>> For more options, visit https://groups.google.**
>> com/groups/opt_out= 
>> ">https://groups.google.com/**groups/opt_out.> />
>>  
>>  
>>
>> --=_Part_89_9798859.**1366811681215--
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
Website: http://earl-of-code.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Passing parameters to downstream jobs

[Maureen Barger]

I was just reading about that when your reply arrived, thank you!


On Wed, Apr 24, 2013 at 1:41 PM, Jared Griffith
wrote:

> Yeah, I asked this same question before.  Install the Jenkins
> Parameterized Trigger 
> plugin.
> Then in the Post Build Actions section of the job, add the Trigger
> Parameterized Build on Other Projects.  There are several options you can
> pass to the down stream jobs from there.
>  
>
>
> On Wed, Apr 24, 2013 at 10:14 AM, Maureen Barger wrote:
>
>> Hi all -
>> With a job that triggers many downstream jobs, is it possible to set a
>> string parameter (ie a file path or a release number) in the first job
>> and pass it on to all of the downstream jobs?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to jenkinsci-users+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>
>
> --
>
> Jared Griffith
> Linux Administrator, PICS Auditing, LLC
> P: (949) 936-4574
> C: (909) 653-7814
>
> 
>
> 17701 Cowan #140 | Irvine, CA | 92614
>
> Join PICS on LinkedIn and Twitter!
>
> 
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Passing parameters to downstream jobs

[Jared Griffith]

Yeah, I asked this same question before.  Install the Jenkins Parameterized
Trigger 
plugin.
Then in the Post Build Actions section of the job, add the Trigger
Parameterized Build on Other Projects.  There are several options you can
pass to the down stream jobs from there.



On Wed, Apr 24, 2013 at 10:14 AM, Maureen Barger  wrote:

> Hi all -
> With a job that triggers many downstream jobs, is it possible to set a
> string parameter (ie a file path or a release number) in the first job
> and pass it on to all of the downstream jobs?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>


-- 

Jared Griffith
Linux Administrator, PICS Auditing, LLC
P: (949) 936-4574
C: (909) 653-7814



17701 Cowan #140 | Irvine, CA | 92614

Join PICS on LinkedIn and Twitter!



-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Passing parameters to downstream jobs

[Maureen Barger]

Hi all -
With a job that triggers many downstream jobs, is it possible to set a
string parameter (ie a file path or a release number) in the first job
and pass it on to all of the downstream jobs?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Persist job results after the slave is destroyed

[Kamal Ahmed]

Hi,
I just wanted to confirm, if i am running a max of 100 Jobs , with unit tests, 
static analysis, WebDriver tests, and then at some point destroy the slave to 
create a brand new one, would the results be persisted on the Jenkins Master ? 
, and when the new Slave ( Identical to the old one ) Comes back on, would it 
seem seemless ?

Thanks,
-Kamal.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: jenkins e-mail ext DEFAULT_CONTENT does not expand

[windycity]

Here attached are the global and project config files, please let me know 
what is wrong.

Thanks much for all your help!

Jessica

On Wednesday, April 24, 2013 8:59:51 AM UTC-5, slide wrote:
>
> pre-build/post build added token 
> MIME-Version: 1.0 
> Content-Type: multipart/alternative; 
> boundary="=_Part_89_9798859.1366811681215" 
>
> --=_Part_89_9798859.1366811681215 
> Content-Type: text/plain; charset="utf-8" 
> Content-Transfer-Encoding: 7bit 
>
> They are expanded the same way, so I need more information (like your 
> global and project config XML) to try and determine the issue. 
>
> Sent from my Windows Phone 
> From: windycity 
> Sent: 4/24/2013 6:54 
> To: jenkins...@googlegroups.com  
> Subject: jenkins e-mail ext DEFAULT_CONTENT does not expand 
> pre-build/post build added token 
> I use jenkin's configuration pre-build and post build "Execute Groovy 
> System Script"-> command to get a token $MAVE_PREBUIL_VERSION and 
> $MAVEN_POSTBUILD_MAVEN, and put this at e-mail ext plugin configuration. 
> In 
> both global and project session, DEFAULT_SUBJECT can extent these Tokens, 
> but DEFAULT_CONTENT can not, is this a known issue or I am not using it 
> right? 
>
> $DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION}, ${MAVEN_POSTBUILD_VERSION} 
> Above expand the token, but following does not 
>
>
> $DEFAULT_CONTENT, ${MAVEN_PREBUILD_VERSION} 
>
> Thanks in advance, 
>
> jessica 
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "Jenkins Users" group. 
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to jenkinsci-use...@googlegroups.com . 
> For more options, visit https://groups.google.com/groups/opt_out. 
>
>
>
> --=_Part_89_9798859.1366811681215 
> Content-Type: text/html; charset="utf-8" 
> Content-Transfer-Encoding: quoted-printable 
>
>  http-equiv=3D"Cont= 
> ent-Type"> = 
> font-size: 11pt;">They are expanded the same way, so I need more 
> informatio= 
> n (like your global and project config XML) to try and determine the 
> issue.= 
> Sent from my Windows Phone style=3D"font-f= 
> amily: Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">From: 
>  > 10pt;">windycity= 
>  = 
> font-weight: bold;">Sent:  Tahoma,sans-se= 
> rif; font-size: 10pt;">4/24/2013 6:54 style=3D"font-family:= 
>  Tahoma,sans-serif; font-size: 10pt; font-weight: bold;">To:  s= 
> tyle=3D"font-family: Tahoma,sans-serif; font-size: 
> 10pt;">jenkinsci-users@g= 
> ooglegroups.com fo= 
> nt-size: 10pt; font-weight: bold;">Subject:  style=3D"font-fami= 
> ly: Tahoma,sans-serif; font-size: 10pt;">jenkins e-mail ext 
> DEFAULT_CONTENT= 
>  does not expand pre-build/post build added 
> token ml>I use jenkin's configuration pre-build and post build "Execute Groovy 
> Sy= 
> stem Script"-> command to get a token $MAVE_PREBUIL_VERSION and 
> $MAVEN_P= 
> OSTBUILD_MAVEN, and put this at e-mail ext plugin configuration. In both 
> gl= 
> obal and project session, DEFAULT_SUBJECT can extent these Tokens, but 
> DEFA= 
> ULT_CONTENT can not, is this a known issue or I am not using it 
> right?<= 
> br>$DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION}, ${MAVEN_POSTBUILD_VERSION} 
> = 
> Above expand the token, but following does 
> not$DEFAULT_CONTENT,= 
>  ${MAVEN_PREBUILD_VERSION}Thanks in 
> advance,jessica 
>
>  
>
> --  
> You received this message because you are subscribed to the Google Groups 
> &= 
> quot;Jenkins Users" group. 
> To unsubscribe from this group and stop receiving emails from it, send an 
> e= 
> mail to jenkinsci-use...@googlegroups.com . 
> For more options, visit  https://groups.google.com/groups/opt_out= 
> ">https://groups.google.com/groups/opt_out. 
>   
>   
>
> --=_Part_89_9798859.1366811681215-- 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




config_global.xml
Description: XML document


config_project.xml
Description: XML document

Allow external script to build jobs without allowing anonymous code viewing

[Nick Walke]

Hello!  Basically what the subject says, I want an external service 
(BitBucket in this case) to be able to build jobs, but I also want to lock 
down Jenkins so that anonymous can't view jobs/code.  I've tried giving 
anonymous the build attribute, but that doesn't seem to help anything.  Is 
there a way to do this?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: MultiOS configuration

[B.Latinville]

*> I'll be happy to read the documentation (in case it exists)*

Have a look at the "Jenkins:The Definitive Guide" Book, it is available for 
free pdf.


Le mercredi 24 avril 2013 15:15:49 UTC+2, Ceco a écrit :
>
> I don't want the master to do anything. I want all the slaves to do the 
> job. If that's something that is done by design I'll be happy to read the 
> documentation (in case it exists). And for starters I don't know what the 
> *name* and the *values* of the user axes should be and more important - *
> why* should they be the ones that Bertrand specified.
>
> On Wednesday, April 24, 2013 4:06:13 PM UTC+3, Stephen Connolly wrote:
>>
>> Did you wait for the master to finish checking out the source code and 
>> then start replicating the workspace to all slave nodes?
>>
>>
>> On 24 April 2013 13:57, Ceco  wrote:
>>
>>> Thank you for your answer. I guess you misjudged my knowledge about 
>>> Jenkins though and therefore there's no progress.
>>>
>>> 1. After searching a lot I figured out I have to use master and slave 
>>> nodes which I believe I've set up correctly in a way that works for me.
>>> 2. I created the two axes with the specified values. But when I build 
>>> the job only the master node is building, not the slave nodes. I want it to 
>>> be the other way around - the master should not be running the job, each 
>>> slave should do that. If only there was a way to find out what the values 
>>> should be in order to force the job to be run by the slave nodes. I find 
>>> the lack of documentation about this project extremely frustrating.
>>>
>>>  -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to jenkinsci-use...@googlegroups.com.
>>> For more options, visit https://groups.google.com/groups/opt_out.
>>>  
>>>  
>>>
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: cvs symbolic name parameter : how to use it to check out a specific tag ?

[Michael Clarke]

In the 'this build is parameterized' section of the config page, enter the
appropriate CVS connection details and which module to check for branches
and tags on. In the source control section, enter your CVS connection
details, select 'Tag' as the location, and in the tag name field enter the
parameter you created above (e.g ${tagName}). I've not used the SVN plugin
but think this is very similar to how it works.

Thanks
Michael

On 24 Apr 2013, at 16:16, "Barthélémy" 
wrote:

Hello,

I have installed the plugin "cvs symbolic name parameter". I wished to use
it as I do with Subversion : get the tag/branch name and use it in the
check out section.

I don't understand how to do the same with CVS because I have to select the
Location (ie. Head, Branches or Tags) when configuring.

Should I simply not use the Source Code Management task and create a shell
task to make a manual check out ?

Thank you in advance for your help,
Barthelemy

-- 
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Perform a single svn checkout in a multi-configuration project

[Les Mikesell]

On Wed, Apr 24, 2013 at 8:14 AM,   wrote:

>>> I think the typical way to handle this in subversion is to make each
>> project that builds separately have its own trunk/branches/tags tree
>> and every part that needs to include components from a separate area
>> would use svn externals to pull them into a checkout.
>
>
> This seems too complicated for my use case. Do you agree?

No, any time you are re-using components, svn externals make a lot of
sense.  And you should almost never have to check out the whole
trunk/branches/tags tree at once.

>> Yes, that is the layout your job requests.  But what I meant was that
>> on the 2nd and subsequent runs of this job,  jenkins should be doing
>> an 'svn update' into those existing workspaces which should not be an
>> expensive operation even if you have to repeat it a few times.
>
>
> Alright. So there just is no way to have a multi configuration job reuse the
> same checkout?

No, in the general case, the jobs will run on different slaves and may
be checked out with different native line endings.  And they may run
in parallel so they can't use the same workspace.  If you are really
just doing everything in one build on one host, why not write your own
script wrapper to handle the variations?

--
   Les Mikesell
 lesmikes...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

cvs symbolic name parameter : how to use it to check out a specific tag ?

[Barthélémy]

Hello, 

I have installed the plugin "cvs symbolic name parameter". I wished to use 
it as I do with Subversion : get the tag/branch name and use it in the 
check out section. 

I don't understand how to do the same with CVS because I have to select the 
Location (ie. Head, Branches or Tags) when configuring. 

Should I simply not use the Source Code Management task and create a shell 
task to make a manual check out ? 

Thank you in advance for your help,
Barthelemy

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: MultiOS configuration

[Les Mikesell]

On Wed, Apr 24, 2013 at 8:15 AM, Ceco  wrote:
> I don't want the master to do anything. I want all the slaves to do the job.
> If that's something that is done by design I'll be happy to read the
> documentation (in case it exists). And for starters I don't know what the
> name and the values of the user axes should be and more important - why
> should they be the ones that Bertrand specified.

You don't have to use those particular labels - you can apply
descriptive labels to the nodes and use them to either restrict jobs
to nodes with certain capabilities or to do matrix builds across
certain combinations.  You can use whatever names make sense for your
situation.

--
   Les Mikesell
 lesmikes...@gmail.com

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: MultiOS configuration

[B.Latinville]

On the node configuration you need to add labels : windows8 or windows7,  
x64 or x86 to reflects the node configuration.

It the matrix job configuration add 2 salves axes. One for windows(7/8) one 
for x(86/64) : Add Axes->Slaves. Tick the check box.

Le mercredi 24 avril 2013 16:01:39 UTC+2, Ceco a écrit :
>
> OK, I understand that now.
>
> What I don't though is how to specify the axes values so that the job is 
> run on all the slave nodes I want to.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: MultiOS configuration

[Ceco]

OK, I understand that now.

What I don't though is how to specify the axes values so that the job is 
run on all the slave nodes I want to.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

RE: jenkins e-mail ext DEFAULT_CONTENT does not expand

[Alex Earl]

 pre-build/post build added token
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="=_Part_89_9798859.1366811681215"

--=_Part_89_9798859.1366811681215
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

They are expanded the same way, so I need more information (like your
global and project config XML) to try and determine the issue.

Sent from my Windows Phone
From: windycity
Sent: 4/24/2013 6:54
To: jenkinsci-users@googlegroups.com
Subject: jenkins e-mail ext DEFAULT_CONTENT does not expand
pre-build/post build added token
I use jenkin's configuration pre-build and post build "Execute Groovy
System Script"-> command to get a token $MAVE_PREBUIL_VERSION and
$MAVEN_POSTBUILD_MAVEN, and put this at e-mail ext plugin configuration. In
both global and project session, DEFAULT_SUBJECT can extent these Tokens,
but DEFAULT_CONTENT can not, is this a known issue or I am not using it
right?

$DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION}, ${MAVEN_POSTBUILD_VERSION}
Above expand the token, but following does not


$DEFAULT_CONTENT, ${MAVEN_PREBUILD_VERSION}

Thanks in advance,

jessica

-- 
You received this message because you are subscribed to the Google
Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



--=_Part_89_9798859.1366811681215
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

They are expanded the same way, so I need more informatio=
n (like your global and project config XML) to try and determine the issue.=
Sent from my Windows PhoneFrom: windycity=
Sent: 4/24/2013 6:54To: jenkinsci-users@g=
ooglegroups.comSubject: jenkins e-mail ext DEFAULT_CONTENT=
 does not expand pre-build/post build added tokenI use jenkin's configuration pre-build and post build "Execute Groovy Sy=
stem Script"-> command to get a token $MAVE_PREBUIL_VERSION and $MAVEN_P=
OSTBUILD_MAVEN, and put this at e-mail ext plugin configuration. In both gl=
obal and project session, DEFAULT_SUBJECT can extent these Tokens, but DEFA=
ULT_CONTENT can not, is this a known issue or I am not using it right?<=
br>$DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION}, ${MAVEN_POSTBUILD_VERSION} =
Above expand the token, but following does not$DEFAULT_CONTENT,=
 ${MAVEN_PREBUILD_VERSION}Thanks in advance,jessica



-- 
You received this message because you are subscribed to the Google Groups &=
quot;Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out=
">https://groups.google.com/groups/opt_out.
 
 

--=_Part_89_9798859.1366811681215--

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

jenkins e-mail ext DEFAULT_CONTENT does not expand pre-build/post build added token

[windycity]

I use jenkin's configuration pre-build and post build "Execute Groovy 
System Script"-> command to get a token $MAVE_PREBUIL_VERSION and 
$MAVEN_POSTBUILD_MAVEN, and put this at e-mail ext plugin configuration. In 
both global and project session, DEFAULT_SUBJECT can extent these Tokens, 
but DEFAULT_CONTENT can not, is this a known issue or I am not using it 
right?

$DEFAULT_SUBJECT, ${MAVEN_PREBUILD_VERSION}, ${MAVEN_POSTBUILD_VERSION} 
Above expand the token, but following does not


$DEFAULT_CONTENT, ${MAVEN_PREBUILD_VERSION}

Thanks in advance,

jessica

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No link between a promoted build, and the build which was triggered by the promotion

[greg . smith]

Hi guys,

I'm having a problem where it seems like I am either doing something wrong, 
or have things mis-configured.  Here's my issue:

We use the promotion plugin to trigger a parameterized build.  Basically, 
that parameterized build just rebuilds the same SVN revision, but has an 
extra step of pushing out to a website.

When I promote the build, I get this in the promotion status of the build 
that was promoted:

CopyTools » promotion » Push To Content Server #3

Legacy code started this job.  No cause information is available
Building on master in workspace /var/lib/jenkins/jobs/CopyTools/workspace
Promoting CopyTools #7 
[parameterizedtrigger] no SubversionTagAction found -- is this project an SVN 
project ?
build hudson.plugins.parameterizedtrigger.BuildTrigger@5e8956ff SUCCESS
Finished: SUCCESS


Then, in the build that was caused by the trigger, I get this:

Started by upstream project "CopyTools - WL/promotion/Push To Content Server" 
build number 3
originally caused by:

   Legacy code started this job. No cause information is available



I can look and see that the promotion caused the triggered build, because the 
second build was started by "Push To Content Server" build number 3, and those 
match.


But is there any way to set this up so that there is actually a clickable link 
between the build that was promoted, and the build caused by the promotion?


Right now, I have to do a manual search to find the triggered build, based on 
the "Started by" text, and its really a pain.


Thanks for any advice,

Greg

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: MultiOS configuration

[Stephen Connolly]

There is a coordinating job that needs to run too and coordinates all the
'child' jobs that run on the different nodes. With a 2x2 matrix you will
have up to 5 jobs running during a matrix build:
1. The main build coordinator
2. R1C1
3. R1C2
4. R2C1
5. R2C2

The main build coordinator will start before any of the matrix entry jobs
and will not finish until they all finish.

HTH


On 24 April 2013 14:15, Ceco  wrote:

> I don't want the master to do anything. I want all the slaves to do the
> job. If that's something that is done by design I'll be happy to read the
> documentation (in case it exists). And for starters I don't know what the
> *name* and the *values* of the user axes should be and more important - *
> why* should they be the ones that Bertrand specified.
>
>
> On Wednesday, April 24, 2013 4:06:13 PM UTC+3, Stephen Connolly wrote:
>
>> Did you wait for the master to finish checking out the source code and
>> then start replicating the workspace to all slave nodes?
>>
>>
>> On 24 April 2013 13:57, Ceco  wrote:
>>
>>> Thank you for your answer. I guess you misjudged my knowledge about
>>> Jenkins though and therefore there's no progress.
>>>
>>> 1. After searching a lot I figured out I have to use master and slave
>>> nodes which I believe I've set up correctly in a way that works for me.
>>> 2. I created the two axes with the specified values. But when I build
>>> the job only the master node is building, not the slave nodes. I want it to
>>> be the other way around - the master should not be running the job, each
>>> slave should do that. If only there was a way to find out what the values
>>> should be in order to force the job to be run by the slave nodes. I find
>>> the lack of documentation about this project extremely frustrating.
>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to jenkinsci-use...@**googlegroups.com.
>>>
>>> For more options, visit 
>>> https://groups.google.com/**groups/opt_out
>>> .
>>>
>>>
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Looking for a Log File Reporting Parser

[Ishan Shah]

Hi Guys,

Currently we log our test results into a log file. What I am looking for is
a test result plugin that allows me to take log file as input, specify a
regular expression to parse the log file and generate a report with PASS,
FAILED and ERRORed test as output.

Something similar to the MSTest Plugin should also be fine.

Can anyone please help.

Thanks,
Ishan

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: test to check whether i am subscribed

[Andrew Melo]

pong

On Wed, Apr 24, 2013 at 3:19 AM, Ceco  wrote:

>
>  --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>



-- 
--
Andrew Melo

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: MultiOS configuration

[Ceco]

I don't want the master to do anything. I want all the slaves to do the 
job. If that's something that is done by design I'll be happy to read the 
documentation (in case it exists). And for starters I don't know what the *
name* and the *values* of the user axes should be and more important - 
*why*should they be the ones that Bertrand specified.

On Wednesday, April 24, 2013 4:06:13 PM UTC+3, Stephen Connolly wrote:
>
> Did you wait for the master to finish checking out the source code and 
> then start replicating the workspace to all slave nodes?
>
>
> On 24 April 2013 13:57, Ceco > wrote:
>
>> Thank you for your answer. I guess you misjudged my knowledge about 
>> Jenkins though and therefore there's no progress.
>>
>> 1. After searching a lot I figured out I have to use master and slave 
>> nodes which I believe I've set up correctly in a way that works for me.
>> 2. I created the two axes with the specified values. But when I build the 
>> job only the master node is building, not the slave nodes. I want it to be 
>> the other way around - the master should not be running the job, each slave 
>> should do that. If only there was a way to find out what the values should 
>> be in order to force the job to be run by the slave nodes. I find the lack 
>> of documentation about this project extremely frustrating.
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> For more options, visit https://groups.google.com/groups/opt_out.
>>  
>>  
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Perform a single svn checkout in a multi-configuration project

[roehnsch]

I have what I take to be problem related to Fernando's. And I think the 
solution should be the same. So here is my explanation.

I have essentially one svn repository. Its checkout is used for a multi 
configuration job. The user axes provide variants of my Ant build. The 
build is part of the checkout. It knows how to handle these variants 
itself, if provided with the current axes configuration as Ant properties, 
which the multi configuration job promised to do.

By default, Jenkins checks out the svn repository N times. N being the 
number of all combinations, e.g. axis1 contains 2 items, axis2 contains 3 
items, yielding 6 combinations.

This is a pain. Jenkins produces N checkouts, where I require only one. 
This results in overhead for the initial checkout as well as subsequent 
updates. How to fix that? I have found no solution so far elsewhere.

I think the typical way to handle this in subversion is to make each 
> project that builds separately have its own trunk/branches/tags tree 
> and every part that needs to include components from a separate area 
> would use svn externals to pull them into a checkout.


This seems too complicated for my use case. Do you agree? 

Yes, that is the layout your job requests.  But what I meant was that 
> on the 2nd and subsequent runs of this job,  jenkins should be doing 
> an 'svn update' into those existing workspaces which should not be an 
> expensive operation even if you have to repeat it a few times.


Alright. So there just is no way to have a multi configuration job reuse 
the same checkout? 

Regards,
Alexander

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: MultiOS configuration

[Stephen Connolly]

Did you wait for the master to finish checking out the source code and then
start replicating the workspace to all slave nodes?


On 24 April 2013 13:57, Ceco  wrote:

> Thank you for your answer. I guess you misjudged my knowledge about
> Jenkins though and therefore there's no progress.
>
> 1. After searching a lot I figured out I have to use master and slave
> nodes which I believe I've set up correctly in a way that works for me.
> 2. I created the two axes with the specified values. But when I build the
> job only the master node is building, not the slave nodes. I want it to be
> the other way around - the master should not be running the job, each slave
> should do that. If only there was a way to find out what the values should
> be in order to force the job to be run by the slave nodes. I find the lack
> of documentation about this project extremely frustrating.
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: MultiOS configuration

[Ceco]

Thank you for your answer. I guess you misjudged my knowledge about Jenkins 
though and therefore there's no progress.

1. After searching a lot I figured out I have to use master and slave nodes 
which I believe I've set up correctly in a way that works for me.
2. I created the two axes with the specified values. But when I build the 
job only the master node is building, not the slave nodes. I want it to be 
the other way around - the master should not be running the job, each slave 
should do that. If only there was a way to find out what the values should 
be in order to force the job to be run by the slave nodes. I find the lack 
of documentation about this project extremely frustrating.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Selenium Htmlsuite plugin

[Aswini Rajasekaran]

Hi,

Anyone knows how to use the selenium rc plugin in a job? I tried many 
things but nothing works. 
Thanks,
Aswini

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: MultiOS configuration

[B.Latinville]

Hi,

1.You should use matrix job instead of copying the jobs.
2 axes : 
 - platform : = Windows7 & Windows8
 - architecture: = x86 & x64

2.The path for git shall be configured on the node configuration :in the 
"Tool Locations" section.
The git plugin has an option to use the git defined at node level (Click on 
advanced)
In the node configuration, you should also define environment variables for 
your tools that will be used in the job.
The value of the environments variables will reflect the tools location on 
the node.


3. I did not used Nunit Plugin, but with the Junit plugin and matrix job, 
you have a overall view of all tests in the parent job.
Maybe Nunit does the same.

Bertrand.



-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: printing data next to parameters choice

[Eduardo Dias]

Hi,
try parameterized with scriptlet (groovy script). I do it to list all rc
that can be published, then, the user choose what wants based on date,build
number, etc...

At.,
Eduardo Dias

Sent by mobile phone powerded by Android.
Em 24/04/2013 03:07, "Tomek Kaczanowski" 
escreveu:

> Hi All,
>
> I would like to use Jenkins for performing some maintenance task of our
> application. I plan to use a parameterized build for this (so the user can
> configure it). So far so good.
>
> In addition I would like to run a script BEFORE the user is presented with
> parameters choice form, and print some data obtained by this script there
> (so the user can set reasonable options).
>
> How can I achieve this? I've looked through plugins but couldn't find
> anything close to what I want.
>
>
> --
> Regards,
> Tomek Kaczanowski
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

MultiOS configuration

[Ceco]

Hi,

I should start with the fact that I am new to jenkins. The problem is I've 
got extreme difficulties finding documentation and general information how 
to do things. But before abandoning it and using another CI server I 
decided to ask a question first.

I have a project which needs to build and its tests run on several OSes 
(Windows 7/8, x86/x64) so I've created a VM for each OS. So far I've 
installed jenkins on each VM and created a new job for each jenkins server 
and copied the configuration file. Then I edited the file for each VM 
because the path for git.exe, the build tool and the tool running the tests 
are different on x86 and x64. Yes, that's a stupid way to do it but it was 
a quick solution and I did it anyway to get things started. As always 
happens, today somethings needs to be changed and I don't want to change it 
several times. Are there any features in jenkins to support the these?

1. I guess my job needs to be created in a central place and I have to tell 
the jenkins server installed on each VM to use it.
2. My job needs to have some parameters - the path to git.exe, the build 
tool and the tool running the tests. I need to use those in the job (I 
suppose there's some $parameter-like syntax). Also, there should be a way 
to define the values for those parameters for each VM.
3. I used the NUnit plugin to publish results but I don't know whether the 
results from all VMs (in case that's possible) can be shown in one place? 
Alternatively, this is not needed if I can open the build log for each VM 
in my central jenkins server.

Any help will be greatly appreciated,
Ceco

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

test to check whether i am subscribed

[Ceco]

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: Re: LTS 1.509.1 RC testing

[Vojtech Juranek]

On Tuesday 23 April 2013 14:58:10 Kohsuke Kawaguchi wrote:
> Thanks for posting this!

+1 thanks!
Just a notice: we have part of these test already automated as Selenium test 
[1], so if you don't want to do any manual testing, you can download the tests 
and run them (however, some manual test of the tests, at least on windows, is 
still needed)

[1] https://github.com/jenkinsci/selenium-tests

> 
> On 04/20/2013 11:39 AM, Mark Waite wrote:
> > Hi,
> > 
> > LTS 1.509.1 RC is now available for download [1].
> > 
> > I would like to ask for your help. If you stage RC in your stage
> > environment
> > or just download RC and try to run it, please drop a note on the wiki
> > page [2],
> > shortly describe what you've tested, where it was done (OS, JDK
> > version) and the result.
> > 
> > Feel free to add new tests or repeat tests which were already done by
> > someone
> > else in different env. - it is also very useful as some bug can appear
> > only on
> > e.g. one OS but not on other etc.
> > 
> > Any test is very helpful, especially in case of new LTS RC.
> > 
> > Thanks in advance
> > Mark Waite (daring to post something similar to what Voyta posted
> > previously)
> > 
> > [1] http://mirrors.jenkins-ci.org/
> > [2] https://wiki.jenkins-ci.org/display/JENKINS/LTS+1.509.x+RC+Testing
> > 
> > 
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Jenkins Users" group.
> > To unsubscribe from this group and stop receiving emails from it, send
> > an email to jenkinsci-users+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/groups/opt_out.

signature.asc
Description: This is a digitally signed message part.