[JIRA] (JENKINS-60063) Add Signature to withEnv to take Map<String, String>

[jerrywiltse@gmail.com (JIRA)]

jerry wiltse created an issue

Jenkins / JENKINS-60063 Add Signature to withEnv to take Map<String, String> Issue Type: New Feature Assignee: Unassigned Components: workflow-basic-steps-plugin Created: 2019-11-05 15:51 Priority: Minor Reporter: jerry wiltse We have this utility function in our Jenkins Shared Library: static List<String> convertMapToJenkinsEnv(Map<String,String> srcEnv) { return srcEnv.collect { "${it.key}=${it.value}"} } It seems obvious that this could be an alternative signature to the current basic built-in function: withEnv For us, it's far more ergonomic to work with and compose maps in our Shared Library and scripted pipelines, taking advantage of it's well-defined characteristics surrounding unique keys etc. It seems as trivial as it could be to implement this. Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[jerrywiltse@gmail.com (JIRA)]

jerry wiltse updated an issue

Jenkins / JENKINS-60063 Add Signature to withEnv to take Map<String, String>

Change By: jerry wiltse

We have this utility function in our Jenkins Shared Library:

{code:java}

static List<String> convertMapToJenkinsEnv(Map<String,String> srcEnv) {     return srcEnv.collect { "${it.key}=${it.value}"}

}{code} It seems obvious that this could be an alternative signature and implementation to the current basic built-in function: {code:java} withEnv {code}

For us, it's far more ergonomic to work with and compose maps in our Shared Library and scripted pipelines, taking advantage of it's well-defined characteristics surrounding unique keys etc.   It seems as trivial as it could be to implement this.

Add Comment