Would you believe it just started working? SMH. Ended up with COPYARTIFACT_BUILD_NUMBER_MY_PROJECT_ I guess the stars were not aligned before ...
Thanks for all the help! On Mon, Oct 14, 2013 at 12:22 PM, Maureen Barger <[email protected]> wrote: > Hmm well printenv shows JOB_NAME=MY-PROJECT-1.0. Not much help there. > Any other ideas? > > On Mon, Oct 14, 2013 at 12:05 PM, Maureen Barger <[email protected]> wrote: >> Matthew you are right, I assumed that was the root of the issue. I >> will try as you suggest. Thanks! >> >> On Mon, Oct 14, 2013 at 11:59 AM, <[email protected]> wrote: >>> Ok, so your question is not >>> "What characters are illegal to include in job names" >>> but rather >>> "how does the Copy Artifact plugin derive an environment variable name >>> from a jobname, in order to report the job number" >>> >>> I've had the same problem with $COPYARTIFACT_BUILD_NUMBER - it seems >>> impossible to work out what environment variable it actually generates. The >>> simplest approach I have found is to run a shell build step after the Copy >>> Artifact step, and use the "printenv" or "set" command to see what >>> environment variables exist (if Windows, use the appropriate equivalent). >>> That should tell you what you need to know. >>> >>> Hope that helps >>> Matthew >>> >>>> -----Original Message----- >>>> From: [email protected] >>>> [mailto:[email protected]] On Behalf Of Maureen >>>> Barger >>>> Sent: 14 October 2013 16:50 >>>> To: [email protected] >>>> Subject: Re: What characters are illegal to include in job names? >>>> >>>> Thanks Scott. I am having trouble copying artifacts from another job >>>> using $COPYARTIFACT_BUILD_NUMBER. The job in question has a dot and >>>> hyphens in the name (ie MY-PROJECT-1.0) The documentation says that >>>> anything not a letter is replaced with "_" (ie >>>> projectName.toUpperCase().replaceAll("[^A-Z]+", "_")) but I am finding >>>> on this job, it does not work. >>>> So $COPYARTIFACT_BUILD_NUMBER_MY_PROJECT_ should be the string used >>>> but it is not working. I have tried a number of combinations as well. >>>> I thought I remembered reading somewhere that using a dot in a job >>>> name is not recommended but I cannot find anything in the docs or >>>> elsewhere to prove that. >>>> >>>> On Mon, Oct 14, 2013 at 11:39 AM, Scott Evans <[email protected]> wrote: >>>> > I'm not familiar with any offhand which are illegal, though I'd suggest >>>> > as >>>> > best practices to avoid anything that's not a standard alphabetic, >>>> > numeric, >>>> > or dash/underscore. Depending on what platform(s) you're working on, I'd >>>> > suggest for sure to avoid spaces, as that just gets weird with some >>>> > command-line stuff if there are spaces in the job name. It's probably >>>> > more >>>> > of an OS limitation on what would be a valid directory name rather than >>>> > anything within Jenkins itself. >>>> > >>>> > Scott >>>> > >>>> > >>>> > On Mon, Oct 14, 2013 at 10:33 AM, Maureen Barger <[email protected]> >>>> > wrote: >>>> >> >>>> >> Hi - I am having a hard time finding any list of characters we should >>>> >> not use in job names. Are there any? Thanks. >>>> >> >>>> >> -- >>>> >> 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 [email protected]. >>>> >> 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 [email protected]. >>>> > 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- >>>> [email protected]. >>>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> -- >>> 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 >>> >>> >>> >>> >>> -- >>> 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 [email protected]. >>> 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
