[JIRA] [extensible-choice-parameter] (JENKINS-17875) Make Jenkins environment variables available to dynamic providers

Fri, 10 May 2013 18:40:01 -0700

ikedam commented on Improvement JENKINS-17875

Thanks for details.
So the points are:

  • Job names are used as an access control.
  • Users shouldn't copy jobs that they are not allowed to access to.

I agree that the best way is to use a job name in a groovy script for this case.

But as mentioned before, there seems no proper way to access the job information from ParameterDefinition...
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
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/groups/opt_out.
 
 

Reply via email to