-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
0.6.5
I'm not sure if this is a bug or not, but I tried putting an environment variable in the Task Name, and it's not consuming it.
The reason is that we have 1 job (deploy) that deploys based on a parameter (env var), but the pipeline does not expand that environment variable.
- is related to
-
JENKINS-25377 Ability to add variables to stage and task name
-
- Resolved
-
-
JENKINS-25685 Parameterized Trigger - Delivery Pipeline compatibilety
-
- Resolved
-
-
JENKINS-29637 Ability to provide description for the task
-
- Closed
-
[JENKINS-20608] Cannot use Env Var in Task Name
Priority | Original: Major [ 3 ] | New: Minor [ 4 ] |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JNJira [ 152133 ] | New: JNJira + In-Review [ 207159 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Closed [ 6 ] | New: In Review [ 10005 ] |
Status | Original: In Review [ 10005 ] | New: In Progress [ 3 ] |