[JIRA] (JENKINS-36213) build-step - obtain environment variables from a non-pipeline job

2016-08-29 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36213  
 
 
  build-step - obtain environment variables from a non-pipeline job   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-36213) build-step - obtain environment variables from a non-pipeline job

2016-06-24 Thread m...@herbert.cc (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Benjamin Herbert created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36213  
 
 
  build-step - obtain environment variables from a non-pipeline job   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 workflow-plugin  
 
 
Created: 
 2016/Jun/24 1:20 PM  
 
 
Labels: 
 pipeline-build-step-plugin environment-variables  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Benjamin Herbert  
 

  
 
 
 
 

 
 One of my "Build Flow Plugin" jobs uses an environment variable FUU set by job1. It could be retrieved like: {{def b = build( "job1") def fuu = b.environment.get( "FUU" )}} Note, that job1 is a freestyle (non-pipeline) job. As Build Flow is deprecated, I am in the process to migrate this job to the pipeline plugin. I would expect that I can access the environment variables by using a snippet like {{def b = build 'job1' def b.buildVariables.FUU}} This does only return null in this case. It works correctly if job1 is a pipeline step, which I find counter intuitive.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment