[JIRA] [tfs-plugin] (JENKINS-33143) Polling doesn't work with variable in project path

[ian.willia...@telus.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ian Williams commented on  JENKINS-33143 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Polling doesn't work with variable in project path  
 
 
 
 
 
 
 
 
 
 
This is similar to the problem https://issues.jenkins-ci.org/browse/JENKINS-33117 Workspace name not parsed properly if a variable and https://issues.jenkins-ci.org/browse/JENKINS-30442 Creating label no longer support build parameters 
In our Jenkins configurations we need to use some sort of variable to reference BRANCH and could well use JOB_NAME too. There's simply too many repetitions in a Jenkins job (5+) across the various plugins and steps. The use of a String variable or Choice parameter simplifies the set up and minimizes errors copy using Jenkins Copy Item for a new job. 
My Corp follows a Job naming convention of - for static builds where path would be $/APP/Branch. 
If a variable has been defined - either Environment, Jenkins Global, Slave or job specific (either static, choice, etc.) prior to invocation, plugin should resolve that at invocation and use resolved value. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [tfs-plugin] (JENKINS-33143) Polling doesn't work with variable in project path

[oliv...@microsoft.com (JIRA)]

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Olivier Dagenais assigned an issue to Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Although asking the previous build for the value of the parameters would mostly work in this case (because JOB_NAME won't change - until you rename the job!), it wouldn't necessarily work in general. I might be able to address rarely-changing variables (assuming I have a way of detecting that, even if it's a hardcoded list) and then later add a way of handling the general case. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-33143 
 
 
 
  Polling doesn't work with variable in project path  
 
 
 
 
 
 
 
 
 

Change By:
 
 Olivier Dagenais 
 
 
 

Summary:
 
 TFS Plugin Always Rebuilding Without Change Polling doesn't work with variable in project path 
 
 
 

Assignee:
 
 redsolo Olivier Dagenais 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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+