Re: API-created jobs have missing "Build Now" link and don't run.
Specifically here line 61:
https://github.com/entagen/jenkins-build-per-branch/blob/master/src/main/groovy/com/entagen/jenkins/JenkinsApi.groovy
On Tue, Oct 15, 2013 at 6:39 AM, Ashley Coker <
ashley.co...@prowebsoftware.net> wrote:
> Going back to above - how to trigger a save remotely to let jenkins jump
> though the hoops yet still leave the job in a build-able state once it has
> been copied.
>
> I have tried posting a second time to /config.xml for that job to try and
> save it after the job is created but it is still left as not build-able
> until you either restart Jenkins or go and save the job again using the web
> UI.
>
> I need to copy these jobs remotely and have them build-able straight away
> but I am unsure how to implement what you have suggested Stephen via the
> remote Rest json api any ideas?
>
>
>
>
> On Wed, Oct 9, 2013 at 12:49 PM, ashleycoker <
> ashley.co...@prowebsoftware.net> wrote:
>
>> How do I install this from the update centre?
>>
>> I managed to extract:
>>
>> {"gav":"org.jenkins-ci.plugins:literate:0.1-beta-2","latestRelease":true,"timestamp":138083690,"title":"Literate
>> Plugin","version":"0.1-beta-2","wiki":"
>> https://wiki.jenkins-ci.org/display/JENKINS/Literate+Plugin"}
>>
>> Does it work with Jenkins 1.533 that I am using?
>>
>> I am happy to use polling of GitHub repos. Will it pick up merged
>> branches?
>>
>>
>>
>> --
>> View this message in context:
>> http://jenkins-ci.361315.n4.nabble.com/API-created-jobs-have-missing-Build-Now-link-and-don-t-run-tp3215035p4678697.html
>>
>> Sent from the Jenkins users mailing list archive at Nabble.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.
>>
>
>
>
> --
> *Ashley Coker*
> *w*: ProWebSoftware.Net
> *e*: ashley.co...@prowebsoftware.net
> *m*: 077382 64519
>
> Unit 7, Fosters Business Park, Old School Road, Hook, Hampshire, RG27 9NY, UK
> Tel: +44 (0)1189 353339 Web: www.prowebsoftware.net, (Company No.
> 6898498)
>
--
*Ashley Coker*
*w*: ProWebSoftware.Net
*e*: ashley.co...@prowebsoftware.net
*m*: 077382 64519
Unit 7, Fosters Business Park, Old School Road, Hook, Hampshire, RG27 9NY, UK
Tel: +44 (0)1189 353339 Web: www.prowebsoftware.net, (Company No. 6898498)
--
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: API-created jobs have missing "Build Now" link and don't run.
Going back to above - how to trigger a save remotely to let jenkins jump
though the hoops yet still leave the job in a build-able state once it has
been copied.
I have tried posting a second time to /config.xml for that job to try and
save it after the job is created but it is still left as not build-able
until you either restart Jenkins or go and save the job again using the web
UI.
I need to copy these jobs remotely and have them build-able straight away
but I am unsure how to implement what you have suggested Stephen via the
remote Rest json api any ideas?
On Wed, Oct 9, 2013 at 12:49 PM, ashleycoker <
ashley.co...@prowebsoftware.net> wrote:
> How do I install this from the update centre?
>
> I managed to extract:
>
> {"gav":"org.jenkins-ci.plugins:literate:0.1-beta-2","latestRelease":true,"timestamp":138083690,"title":"Literate
> Plugin","version":"0.1-beta-2","wiki":"
> https://wiki.jenkins-ci.org/display/JENKINS/Literate+Plugin"}
>
> Does it work with Jenkins 1.533 that I am using?
>
> I am happy to use polling of GitHub repos. Will it pick up merged
> branches?
>
>
>
> --
> View this message in context:
> http://jenkins-ci.361315.n4.nabble.com/API-created-jobs-have-missing-Build-Now-link-and-don-t-run-tp3215035p4678697.html
> Sent from the Jenkins users mailing list archive at Nabble.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.
>
--
*Ashley Coker*
*w*: ProWebSoftware.Net
*e*: ashley.co...@prowebsoftware.net
*m*: 077382 64519
Unit 7, Fosters Business Park, Old School Road, Hook, Hampshire, RG27 9NY, UK
Tel: +44 (0)1189 353339 Web: www.prowebsoftware.net, (Company No. 6898498)
--
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 error "file was lost" in matrix build
Ok, I've updated JENKINS-17965, but since that issue was opened 6 months ago I'm guessing this is not a problem a lot of people are seeing? On 10/14/13 3:02 PM, "Michael Clarke" wrote: >Ok. I've not tried reproducing your issue (the plugin works fine for >me during development and on various different production servers I >manage) but the warning indicates that the Entries file used to track >filed doesn't match what's on the file system. Since you haven't >changed the files, I suspect something is going wrong with the way we >manage the entries file. Could you add some details about your system >to JENKINS-17965 (operating system, default file encoding, cvs server >version etc). > >Thanks >Michael > > >> On 14 Oct 2013, at 21:53, Chris Cooper >>wrote: >> >> Up-to-date: Jenkins 1.534 with Jenkins CVS Plug-in version 2.9 >> >>> On 10/14/13 2:46 PM, "Michael Clarke" >>>wrote: >>> >>> Which version of Jenkins and cvs-plugin are you using? >>> >>> Thanks >>> Michael >>> On 14 Oct 2013, at 21:44, cscooper wrote: We have a matrix job that runs fine except that when the master does that initial CVS update on the master prior to launching any of the matrix builds on slaves, it gives a CVS "file was lost" error for every file in the project. The job is parameterized with a boolean named DELETE_WORKSPACE which is set as the "Check parameter" for "Delete workspace before build starts" in the Build Environment. If I set DELETE_WORKSPACE to true, the build runs perfectly without any CVS errors which implies that my CVS authentication is correct. I tried running the CVS commands from the terminal window, and here's what I see. If I run the commands directly: 1) cvs checkout -P -d project project (this is what Jenkins does if DELETE_WORKSPACE is true) 2) cvs update -C -d -P project (this is what Jenkins does if DELETE_WORKSPACE is false) Both CVS commands run fine. If I let Jenkins run the first command by performing the build: 1) Run the Jenkins job with DELETE_WORKSPACE=true 2) cvs update -C -d -P project During the cvs update, CVS gives me a bunch of warnings about locally modified files being moved to temporary files. And wait, it gets stranger. If I do this: 1) Run the Jenkins job with DELETE_WORKSPACE=true 2) cvs status project 3) cvs update -C -d -P project Then I _don't_ get any warnings during the cvs update about locally modified files. So it looks like Jenkins is somehow leaving CVS in a strange state where it thinks my local files have been modified when they really haven't? Thanks, Chris -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/CVS-error-file-was-lost-in-matri x- build-tp4678897.html Sent from the Jenkins users mailing list archive at Nabble.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. >>> >>> -- >>> 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. > >-- >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: Git plugin: Failed to connect to repository ...password with special characters okay?
@ in URL indeed has to be encoded as %40, but I guess there's many places where such encoding is not handled correctly. try git-plugin 2.0, that introduce support for http credentials. I guess it better support such encoding issue. 2013/10/14 Scott Danzig > I'm trying to add a repository URL for a private git repo (Stash > specifically).. the URL is in this format: > https://theu...@stashserver.company.net/scm/PROJECTNAME/jenkins_setup.git > ... works from another Jenkins server, but I'm getting "Failed to connect > to repository : Failed to connect to " > > I see, from the jenkins server, I can access the URL with "git ls-remote", > but it asks for a password. So I hard-coded the password and git ls-remote > works fine. The password had a @ in it, so I had to replace that with %40 > to get git ls-remote to work. Anyway, the URL with the hard-coded password > is not working when I enter the URL into Jenkins. I figured maybe it > didn't like the %, but my attempts to escape that somehow were fruitless. > > Is the only way to get this working to set up auto-authentication for the > new Jenkins server somehow? > > -- > 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: CVS error "file was lost" in matrix build
Ok. I've not tried reproducing your issue (the plugin works fine for me during development and on various different production servers I manage) but the warning indicates that the Entries file used to track filed doesn't match what's on the file system. Since you haven't changed the files, I suspect something is going wrong with the way we manage the entries file. Could you add some details about your system to JENKINS-17965 (operating system, default file encoding, cvs server version etc). Thanks Michael > On 14 Oct 2013, at 21:53, Chris Cooper wrote: > > Up-to-date: Jenkins 1.534 with Jenkins CVS Plug-in version 2.9 > >> On 10/14/13 2:46 PM, "Michael Clarke" wrote: >> >> Which version of Jenkins and cvs-plugin are you using? >> >> Thanks >> Michael >> >>> On 14 Oct 2013, at 21:44, cscooper >>> wrote: >>> >>> We have a matrix job that runs fine except that when the master does >>> that >>> initial CVS update on the master prior to launching any of the matrix >>> builds >>> on slaves, it gives a CVS "file was lost" error for every file in the >>> project. >>> >>> The job is parameterized with a boolean named DELETE_WORKSPACE which is >>> set >>> as the "Check parameter" for "Delete workspace before build starts" in >>> the >>> Build Environment. If I set DELETE_WORKSPACE to true, the build runs >>> perfectly without any CVS errors which implies that my CVS >>> authentication is >>> correct. >>> >>> I tried running the CVS commands from the terminal window, and here's >>> what I >>> see. >>> >>> If I run the commands directly: >>> 1) cvs checkout -P -d project project (this is what Jenkins does if >>> DELETE_WORKSPACE is true) >>> 2) cvs update -C -d -P project (this is what Jenkins does if >>> DELETE_WORKSPACE is false) >>> Both CVS commands run fine. >>> >>> If I let Jenkins run the first command by performing the build: >>> 1) Run the Jenkins job with DELETE_WORKSPACE=true >>> 2) cvs update -C -d -P project >>> During the cvs update, CVS gives me a bunch of warnings about locally >>> modified files being moved to temporary files. >>> >>> And wait, it gets stranger. If I do this: >>> 1) Run the Jenkins job with DELETE_WORKSPACE=true >>> 2) cvs status project >>> 3) cvs update -C -d -P project >>> Then I _don't_ get any warnings during the cvs update about locally >>> modified >>> files. >>> >>> So it looks like Jenkins is somehow leaving CVS in a strange state >>> where it >>> thinks my local files have been modified when they really haven't? >>> >>> Thanks, >>> Chris >>> >>> >>> >>> >>> >>> -- >>> View this message in context: >>> http://jenkins-ci.361315.n4.nabble.com/CVS-error-file-was-lost-in-matrix- >>> build-tp4678897.html >>> Sent from the Jenkins users mailing list archive at Nabble.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. >> >> -- >> 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. -- 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 error "file was lost" in matrix build
Up-to-date: Jenkins 1.534 with Jenkins CVS Plug-in version 2.9 On 10/14/13 2:46 PM, "Michael Clarke" wrote: >Which version of Jenkins and cvs-plugin are you using? > >Thanks >Michael > >> On 14 Oct 2013, at 21:44, cscooper >>wrote: >> >> We have a matrix job that runs fine except that when the master does >>that >> initial CVS update on the master prior to launching any of the matrix >>builds >> on slaves, it gives a CVS "file was lost" error for every file in the >> project. >> >> The job is parameterized with a boolean named DELETE_WORKSPACE which is >>set >> as the "Check parameter" for "Delete workspace before build starts" in >>the >> Build Environment. If I set DELETE_WORKSPACE to true, the build runs >> perfectly without any CVS errors which implies that my CVS >>authentication is >> correct. >> >> I tried running the CVS commands from the terminal window, and here's >>what I >> see. >> >> If I run the commands directly: >> 1) cvs checkout -P -d project project (this is what Jenkins does if >> DELETE_WORKSPACE is true) >> 2) cvs update -C -d -P project (this is what Jenkins does if >> DELETE_WORKSPACE is false) >> Both CVS commands run fine. >> >> If I let Jenkins run the first command by performing the build: >> 1) Run the Jenkins job with DELETE_WORKSPACE=true >> 2) cvs update -C -d -P project >> During the cvs update, CVS gives me a bunch of warnings about locally >> modified files being moved to temporary files. >> >> And wait, it gets stranger. If I do this: >> 1) Run the Jenkins job with DELETE_WORKSPACE=true >> 2) cvs status project >> 3) cvs update -C -d -P project >> Then I _don't_ get any warnings during the cvs update about locally >>modified >> files. >> >> So it looks like Jenkins is somehow leaving CVS in a strange state >>where it >> thinks my local files have been modified when they really haven't? >> >> Thanks, >> Chris >> >> >> >> >> >> -- >> View this message in context: >>http://jenkins-ci.361315.n4.nabble.com/CVS-error-file-was-lost-in-matrix- >>build-tp4678897.html >> Sent from the Jenkins users mailing list archive at Nabble.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. > >-- >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: CVS error "file was lost" in matrix build
Which version of Jenkins and cvs-plugin are you using? Thanks Michael > On 14 Oct 2013, at 21:44, cscooper wrote: > > We have a matrix job that runs fine except that when the master does that > initial CVS update on the master prior to launching any of the matrix builds > on slaves, it gives a CVS "file was lost" error for every file in the > project. > > The job is parameterized with a boolean named DELETE_WORKSPACE which is set > as the "Check parameter" for "Delete workspace before build starts" in the > Build Environment. If I set DELETE_WORKSPACE to true, the build runs > perfectly without any CVS errors which implies that my CVS authentication is > correct. > > I tried running the CVS commands from the terminal window, and here's what I > see. > > If I run the commands directly: > 1) cvs checkout -P -d project project (this is what Jenkins does if > DELETE_WORKSPACE is true) > 2) cvs update -C -d -P project (this is what Jenkins does if > DELETE_WORKSPACE is false) > Both CVS commands run fine. > > If I let Jenkins run the first command by performing the build: > 1) Run the Jenkins job with DELETE_WORKSPACE=true > 2) cvs update -C -d -P project > During the cvs update, CVS gives me a bunch of warnings about locally > modified files being moved to temporary files. > > And wait, it gets stranger. If I do this: > 1) Run the Jenkins job with DELETE_WORKSPACE=true > 2) cvs status project > 3) cvs update -C -d -P project > Then I _don't_ get any warnings during the cvs update about locally modified > files. > > So it looks like Jenkins is somehow leaving CVS in a strange state where it > thinks my local files have been modified when they really haven't? > > Thanks, > Chris > > > > > > -- > View this message in context: > http://jenkins-ci.361315.n4.nabble.com/CVS-error-file-was-lost-in-matrix-build-tp4678897.html > Sent from the Jenkins users mailing list archive at Nabble.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. -- 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 error "file was lost" in matrix build
We have a matrix job that runs fine except that when the master does that initial CVS update on the master prior to launching any of the matrix builds on slaves, it gives a CVS "file was lost" error for every file in the project. The job is parameterized with a boolean named DELETE_WORKSPACE which is set as the "Check parameter" for "Delete workspace before build starts" in the Build Environment. If I set DELETE_WORKSPACE to true, the build runs perfectly without any CVS errors which implies that my CVS authentication is correct. I tried running the CVS commands from the terminal window, and here's what I see. If I run the commands directly: 1) cvs checkout -P -d project project (this is what Jenkins does if DELETE_WORKSPACE is true) 2) cvs update -C -d -P project (this is what Jenkins does if DELETE_WORKSPACE is false) Both CVS commands run fine. If I let Jenkins run the first command by performing the build: 1) Run the Jenkins job with DELETE_WORKSPACE=true 2) cvs update -C -d -P project During the cvs update, CVS gives me a bunch of warnings about locally modified files being moved to temporary files. And wait, it gets stranger. If I do this: 1) Run the Jenkins job with DELETE_WORKSPACE=true 2) cvs status project 3) cvs update -C -d -P project Then I _don't_ get any warnings during the cvs update about locally modified files. So it looks like Jenkins is somehow leaving CVS in a strange state where it thinks my local files have been modified when they really haven't? Thanks, Chris -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/CVS-error-file-was-lost-in-matrix-build-tp4678897.html Sent from the Jenkins users mailing list archive at Nabble.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.
Git plugin: Failed to connect to repository ...password with special characters okay?
I'm trying to add a repository URL for a private git repo (Stash specifically).. the URL is in this format: https://theu...@stashserver.company.net/scm/PROJECTNAME/jenkins_setup.git ... works from another Jenkins server, but I'm getting "Failed to connect to repository : Failed to connect to " I see, from the jenkins server, I can access the URL with "git ls-remote", but it asks for a password. So I hard-coded the password and git ls-remote works fine. The password had a @ in it, so I had to replace that with %40 to get git ls-remote to work. Anyway, the URL with the hard-coded password is not working when I enter the URL into Jenkins. I figured maybe it didn't like the %, but my attempts to escape that somehow were fruitless. Is the only way to get this working to set up auto-authentication for the new Jenkins server somehow? -- 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: Create JIRA issue on Jmeter test fail
I think you will find that creating issues automatically from Jenkins will flood your issue tracker with reports and will create organizational overhead managing those reports. Even if you only run your JMeter tests once a day, do you really want an issue submitted per failure per day? Wouldn't it be better to first try e-mail messages that inform someone about the failure, then they can decide if it is a long-lived failure and might be worth creating an issue? Mark Waite On Mon, Oct 14, 2013 at 10:20 AM, 1042907P wrote: > We are using performance plugin for parsing Jmeter test cases and showing > HTML reports.Would like to create JIRA issue upon test case failures. > I have tried JIRA plugin ,but it does not even trigger the post build > action. > Please advise > > > > -- > View this message in context: > http://jenkins-ci.361315.n4.nabble.com/Create-JIRA-issue-on-Jmeter-test-fail-tp4678879.html > Sent from the Jenkins users mailing list archive at Nabble.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. > -- 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.
Create JIRA issue on Jmeter test fail
We are using performance plugin for parsing Jmeter test cases and showing HTML reports.Would like to create JIRA issue upon test case failures. I have tried JIRA plugin ,but it does not even trigger the post build action. Please advise -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Create-JIRA-issue-on-Jmeter-test-fail-tp4678879.html Sent from the Jenkins users mailing list archive at Nabble.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: What characters are illegal to include in job names?
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 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 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, 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: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Maureen
Barger
Sent: 14 October 2013 16:50
To: jenkinsci-users@googlegroups.com
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 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
> 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 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.
--
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.
>>>
>>> --
>>> 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 messag
Re: What characters are illegal to include in job names?
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 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, 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: jenkinsci-users@googlegroups.com
>>> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Maureen
>>> Barger
>>> Sent: 14 October 2013 16:50
>>> To: jenkinsci-users@googlegroups.com
>>> 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 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
>>> > 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 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.
>>>
>>> --
>>> 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.
>>
>> --
>> 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 uns
Re: What characters are illegal to include in job names?
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, 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: jenkinsci-users@googlegroups.com
>> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Maureen
>> Barger
>> Sent: 14 October 2013 16:50
>> To: jenkinsci-users@googlegroups.com
>> 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 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
>> > 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 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.
>>
>> --
>> 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.
>
> --
> 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 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 G
RE: What characters are illegal to include in job names?
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: jenkinsci-users@googlegroups.com
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Maureen
> Barger
> Sent: 14 October 2013 16:50
> To: jenkinsci-users@googlegroups.com
> 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 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 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 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.
>
> --
> 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.
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
RE: What characters are illegal to include in job names?
Since job names form part of Jenkins URLs, I think the main limitation is characters which would need escaping when forming a URL (e.g., slash) From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Scott Evans Sent: 14 October 2013 16:40 To: jenkinsci-users@googlegroups.com Subject: Re: What characters are illegal to include in job names? 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 mailto:mobar...@gmail.com>> wrote: Hi - I am having a hard time finding any list of characters we should not use in job names. Are there any? Thanks. -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
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 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 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 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.
--
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: What characters are illegal to include in job names?
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 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 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.
What characters are illegal to include in job names?
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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
