[JIRA] [scripttrigger-plugin] (JENKINS-29918) $WORKSPACE has stopped working in ScriptTrigger shell script

2015-08-12 Thread t...@komta.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tim College created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29918 
 
 
 
  $WORKSPACE has stopped working in ScriptTrigger shell script  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Gregory Boissinot 
 
 
 

Components:
 

 scripttrigger-plugin 
 
 
 

Created:
 

 12/Aug/15 4:20 PM 
 
 
 

Environment:
 

 Jenkins 1.624 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Tim College 
 
 
 
 
 
 
 
 
 
 
I have jobs that monitor the status of external projects. These look for the latest version, and compare it to a known version. The known version is tracked in a file in the workspace. 
Unfortunately, sometime between July 11 (the last successful build) and August 9 (when I noticed it didn't work) the $WORKSPACE variable has stopped being available in the environment when the ScriptTrigger script is run. This ends up meaning my jobs are now looking in the wrong place. Since looking in the wrong place wound up exiting non-zero, the result was don't run, which meant I didn't notice something was wrong until the team noticed that an external project had been updated and our Jenkins jobs didn't trigger. 
I'm able to use a combination of $ {JENKINS_HOME} 
/workspace/$ {JOB_NAME} 
 to re-create the path, but that's a lot less clear, contains a hard-coded value, and I'd rather not have to update dozens of jobs manually.

[JIRA] [scripttrigger-plugin] (JENKINS-29918) $WORKSPACE has stopped working in ScriptTrigger shell script

2015-08-12 Thread t...@komta.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tim College updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29918 
 
 
 
  $WORKSPACE has stopped working in ScriptTrigger shell script  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tim College 
 
 
 
 
 
 
 
 
 
 Ihavejobsthatmonitorthestatusofexternalprojects.Theselookforthelatestversion,andcompareittoaknownversion.Theknownversionistrackedinafileintheworkspace.Unfortunately,sometimebetweenJuly11(thelastsuccessfulbuild)andAugust9(whenI*noticed*itdidn'twork)the$WORKSPACEvariablehasstoppedbeingavailableintheenvironmentwhentheScriptTriggerscriptisrun.Thisendsupmeaningmyjobsarenowlookinginthewrongplace.Sincelookinginthewrongplacewoundupexitingnon-zero,theresultwasdon'trun,whichmeantIdidn'tnoticesomethingwaswronguntiltheteamnoticedthatanexternalprojecthadbeenupdatedandourJenkinsjobsdidn'ttrigger.I'mabletouseacombinationof {{' ${JENKINS_HOME}/workspace/${JOB_NAME} '}} tore-createthepath,butthat'salotlessclear,containsahard-codedvalue,andI'drathernothavetoupdatedozensofjobsmanually.Ifthiswaschangedonpurpose,canyouexplainwhy,orlinktodocumentationthatexplainsit?Iwasn'tabletodetermine. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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

[JIRA] [scripttrigger-plugin] (JENKINS-29918) $WORKSPACE has stopped working in ScriptTrigger shell script

2015-08-12 Thread t...@komta.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Tim College updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29918 
 
 
 
  $WORKSPACE has stopped working in ScriptTrigger shell script  
 
 
 
 
 
 
 
 
 

Change By:
 
 Tim College 
 
 
 
 
 
 
 
 
 
 Ihavejobsthatmonitorthestatusofexternalprojects.Theselookforthelatestversion,andcompareittoaknownversion.Theknownversionistrackedinafileintheworkspace.Unfortunately,sometimebetweenJuly11(thelastsuccessfulbuild)andAugust9(whenI*noticed*itdidn'twork)the$WORKSPACEvariablehasstoppedbeingavailableintheenvironmentwhentheScriptTriggerscriptisrun.Thisendsupmeaningmyjobsarenowlookinginthewrongplace.Sincelookinginthewrongplacewoundupexitingnon-zero,theresultwasdon'trun,whichmeantIdidn'tnoticesomethingwaswronguntiltheteamnoticedthatanexternalprojecthadbeenupdatedandourJenkinsjobsdidn'ttrigger.I'mabletouseacombinationof{{'$ { JENKINS_HOME } /workspace/$ { JOB_NAME } '}}tore-createthepath,butthat'salotlessclear,containsahard-codedvalue,andI'drathernothavetoupdatedozensofjobsmanually.Ifthiswaschangedonpurpose,canyouexplainwhy,orlinktodocumentationthatexplainsit?Iwasn'tabletodetermine. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





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