Regular expression for conditional build step?

2,678 views
Skip to first unread message

David Aldrich

unread,
Dec 3, 2015, 7:28:38 AM12/3/15
to jenkins...@googlegroups.com

Hi

 

I am using the multi-branch plugin to run a job on multiple branches and the trunk.  I want to add a conditional build step that is only executed on the trunk.  So I’m thinking of adding a conditional build step that uses a regular expression to check whether $WORKSPACE contains ‘trunk’.  I guess the regular expression would be something like:

 

Expression: ${ENV,var="WORKSPACE"}

Label: trunk

 

But that isn’t right. What would I specify please?

 

Best regards

 

David

 

David Aldrich

unread,
Dec 3, 2015, 9:04:00 AM12/3/15
to jenkins...@googlegroups.com

Have tried a bit harder.

 

WORKSPACE is:

 

C:\Jenkins\workspace\VS2010_all_branches_and_trunk\trunk

 

Jenkins replies:

 

Regular expression run condition: Expression=[.*\\trunk.*], Label=[${ENV,VAR=WORKSPACE}]
Run condition [Regular expression match] preventing perform for step [Execute Windows batch command]

 

I want the step to execute. What am I doing wrong?

 

Best regards

 

David

Click here to report this email as spam.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/41302A7145AC054FA7A96CFD03835A0A0BA2398D%40EX10MBX02.EU.NEC.COM.
For more options, visit https://groups.google.com/d/optout.

David Aldrich

unread,
Dec 4, 2015, 4:07:23 AM12/4/15
to jenkins...@googlegroups.com

Hi

 

I’m still struggling with this. My workspace is:

 

C:\Jenkins\workspace\VS2010_all_branches_and_trunk\trunk

 

My condition for a build step is:

 

Expression: .*trunk.*

Label: ${ENV,VAR=WORKSPACE}

 

So the build step should execute but it doesn’t:

 

C:\Jenkins\workspace\VS2010_all_branches_and_trunk\trunk\MSVC\Zodiac2010_Release>exit 0

Regular expression run condition: Expression=[.*trunk.*], Label=[${ENV,VAR=WORKSPACE}]

Run condition [Regular expression match] preventing perform for step [Execute Windows batch command]

 

Why is this?  Am I referencing the WORKSPACE variable incorrectly?

Matthew...@diamond.ac.uk

unread,
Dec 4, 2015, 8:47:37 AM12/4/15
to jenkins...@googlegroups.com

My jobs have something like ${ENV,var="GDA_squish_job_to_trigger"}/

Note var is in lower case, and the quote surrounding the variable name

Matthew Webber

--

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/d/optout.

 

-- 

This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
 

David Aldrich

unread,
Dec 4, 2015, 8:59:33 AM12/4/15
to jenkins...@googlegroups.com, Matthew...@diamond.ac.uk

Hi Matthew

 

Thanks very much. I didn’t notice that I was using the wrong case.

 

${ENV,var="WORKSPACE"}

 

works.

 

Best regards

 

David

Reply all
Reply to author
Forward
0 new messages