[JIRA] [dynamicparameter-plugin] (JENKINS-25748) Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts
Title: Message Title Johan Haleby commented on JENKINS-25748 Re: Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts Ioannis Moutsatsos Seems promising but I don't get this to work in Active Choices plugin either. I'll add the same issue on it's issue tracker. 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] [active-choices-plugin] (JENKINS-28764) Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts
Title: Message Title
Johan Haleby created an issue
Jenkins / JENKINS-28764
Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts
Issue Type:
Bug
Assignee:
Bruno P. Kinoshita
Components:
active-choices-plugin
Created:
05/Jun/15 10:36 AM
Environment:
Version 1.0 of Active Choices plugin
Priority:
Major
Reporter:
Johan Haleby
I'm using a Active Choices Parameter on a parameterized build (by selecting This build is parameterized in the job settings). If I've defined a global environment variables/properties or password in Jenkins (defined under Manage Jenkins - Configure System - Global Properties and Manage Jenkins - Configure System - Global Passwords) I cannot seem to use these (for example $ {MY_ENV_NAME}
) as an input parameter to Scriptler scripts. This means that I have to duplicate my global environment variable value when used together with the active choice plugin which is not optimal. The passwords are also visible in clear text when configuring the project.
[JIRA] [scriptler-plugin] (JENKINS-19372) Token macro support for scripts with parameters
Title: Message Title Johan Haleby commented on JENKINS-19372 Re: Token macro support for scripts with parameters This is really quite important. For example I have scripts where need to pass a globally defined username and password as a parameter to my script. Now I have to duplicate the username and password for job that uses the script. The password is then shown in plain text in the parameter when editing the job which is not good. If password is to change I need to edit all jobs using the script and change it manually. 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] [dynamicparameter-plugin] (JENKINS-25748) Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts
Johan Haleby
created JENKINS-25748
Environment variables are not expanded and thus cannot be used as parameter values to Scriptler scripts
Issue Type:
Improvement
Assignee:
Unassigned
Components:
dynamicparameter-plugin
Created:
23/Nov/14 6:01 AM
Description:
If I've defined a global environment variable in Jenkins then I cannot seem to use environment variables (for example ${MY_ENV_NAME})as an input parameter to Scriptler scripts when using the dynamic parameter plugin (in my case I use Dynamic Choice Scriptler). I suspect that expansion of environment variables is not implemented. This means that I have to duplicate my global environment variable value when used together with the dynamic parameter plugin in this way.
Project:
Jenkins
Labels:
plugin
plugins
Priority:
Minor
Reporter:
Johan Haleby
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/d/optout.
[JIRA] [dynamicparameter-plugin] (JENKINS-25661) Dynamic Parameter plugin doesn't expand parameters in description
Johan Haleby
created JENKINS-25661
Dynamic Parameter plugin doesnt expand parameters in description
Issue Type:
Improvement
Assignee:
Unassigned
Components:
dynamicparameter-plugin
Created:
18/Nov/14 11:02 AM
Description:
The description field next to a parameter doesn't expand jenkins environment variables. For example if the description is "Current workspace is ${WORKSPACE}" then ${WORKSPACE} is not expanded.
Project:
Jenkins
Labels:
plugins
Priority:
Major
Reporter:
Johan Haleby
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/d/optout.
[JIRA] [dynamicparameter-plugin] (JENKINS-25661) Dynamic Parameter plugin doesn't expand parameters in description
Johan Haleby commented on JENKINS-25661 Dynamic Parameter plugin doesnt expand parameters in description It doesn't seem like it. Since I'm a not a Jenkins (plugin) developer I'm not sure if this is handled per plugin och globally. I know that several other plugins have (had) issues with not expanding parameters and fixed it (although in their case it was probably not about expanding variables in the description). 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/d/optout.
[JIRA] [dynamicparameter-plugin] (JENKINS-25661) Dynamic Parameter plugin doesn't expand parameters in description
Johan Haleby commented on JENKINS-25661 Dynamic Parameter plugin doesnt expand parameters in description I only used workspace as an example but I hear what you're saying and I agree that it's probably not the best idea to add support for it in this plugin. My use case is actually a bit different. We use the dynamic parameter plugin and scriptler to allow users to select tags from git to include in a release bundle. In addition to this we would like to show which versions are actually deployed to production and stage next to the git tag drop down. So my hope was to use the EnvInject plugin and figure out the deployed versions (using a script) and put them as environment variables whose values would show up in the description field next to each drop down presented by the dynamic parameter plugin. But if the dynamic parameter plugin kicks in before EnvInject then it would still be impossible. The workaround we'll probably use is to present all production and stage versions in their own dropdown (populated by dynamic parameter choices (scripler)). Not quite as nice but at least I think it should work. I still want to say that the Dynamic Parameter plugin (especially with the scriptler support) have helped us tremendously, so thank you very much. 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/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25427) Build Pipleline Plugin no longer allows starting build with parameters
Johan Haleby created JENKINS-25427 Build Pipleline Plugin no longer allows starting build with parameters Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 04/Nov/14 8:51 AM Description: I just upgraded from 1.4.3 to 1.4.4 and now it seems like I no longer have to option to start the build pipeline (first job) with parameters which worked in the previous version. In version 1.4.3 when I pressed the "build now" button a modal window appeared where I could select my parameters for the first job. Now it just builds and automatically selects the pre-defined parameter values. For us this is critical since the initial job allows the user to select version numbers to download from git branches that are later packaged to a release. Project: Jenkins Priority: Critical Reporter: Johan Haleby 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/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25427) Build Pipleline Plugin no longer allows starting build with parameters
Johan Haleby updated JENKINS-25427 Build Pipleline Plugin no longer allows starting build with parameters Change By: Johan Haleby (04/Nov/14 8:52 AM) Environment: BuildPipelinePluginv1.4.4 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/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25430) Clicking on console icon doesn't work
Johan Haleby created JENKINS-25430 Clicking on console icon doesnt work Issue Type: Bug Assignee: Unassigned Components: build-pipeline-plugin Created: 04/Nov/14 12:14 PM Description: When running the build pipeline and clicking the "console" icon the modal window only shows (in Chrome) "Unable to resolve the server's DNS address." The problem is that clicking on the "console" icon tries to load the following address which obviously doesn't work: http://job/JobName/71/console Environment: Build Pipeline v1.4.4 Project: Jenkins Labels: plugin Priority: Major Reporter: Johan Haleby 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/d/optout.
