-
Improvement
-
Resolution: Fixed
-
Major
-
None
As developer I would like to get the enviroment variables when I'm working with a Job. For that, we have the getEnvironment method, designed for:
Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job.
Use case
- I'm using a Subversion repository
- My repository URL is parametized, for example: https://server/project1/$MODULE
- I want to do polling
Use case
- Validate Subversion repositories when its URL is parametized.
This bug would be solved with this improvement.
- is related to
-
JENKINS-29340 E200015: ISVNAuthentication provider did not provide credentials
-
- Closed
-
[JENKINS-29817] Inject environment variables for a Job
| Description |
Original:
As developer I would like to get the enviroment variables when I'm working with a {{Job}} and use the {{getEnvironment}} mehtod. This method is designed for: bq. Creates an environment variable override for launching processes for this project. bq. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job. |
New:
As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for: bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job. h5. Use case # I'm using a Subversion repository # My repository URL is parametized, for example: https://server/project1/${BRANCH} # I want to do polling |
| Description |
Original:
As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for: bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job. h5. Use case # I'm using a Subversion repository # My repository URL is parametized, for example: https://server/project1/${BRANCH} # I want to do polling |
New:
As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for: bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job. h5. Use case # I'm using a Subversion repository # My repository URL is parametized, for example: {{https://server/project1/$MODULE}} # I want to do polling |
| Summary | Original: Injects environment variables for a Job | New: Inject environment variables for a Job |
| Description |
Original:
As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for: bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job. h5. Use case # I'm using a Subversion repository # My repository URL is parametized, for example: {{https://server/project1/$MODULE}} # I want to do polling |
New:
As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for: bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job. h5. Use case # I'm using a Subversion repository # My repository URL is parametized, for example: {{https://server/project1/$MODULE}} # I want to do polling This [bug|https://issues.jenkins-ci.org/browse/JENKINS-29340] would be solved with this improvement. |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Link |
New:
This issue duplicates |
| Description |
Original:
As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for: bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job. h5. Use case # I'm using a Subversion repository # My repository URL is parametized, for example: {{https://server/project1/$MODULE}} # I want to do polling This [bug|https://issues.jenkins-ci.org/browse/JENKINS-29340] would be solved with this improvement. |
New:
As developer I would like to get the enviroment variables when I'm working with a {{Job}}. For that, we have the {{getEnvironment}} method, designed for: bq. Creates an environment variable override for launching processes for this project. This is for process launching outside the build execution (such as polling, tagging, deployment, etc.) that happens in a context of a specific job. h5. Use case # I'm using a Subversion repository # My repository URL is parametized, for example: {{https://server/project1/$MODULE}} # I want to do polling h5. Use case # Validate Subversion repositories when its URL is parametized. This [bug|https://issues.jenkins-ci.org/browse/JENKINS-29340] would be solved with this improvement. |
| Link |
Original:
This issue duplicates |
| Link |
New:
This issue is related to |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |