-
Bug
-
Resolution: Duplicate
-
Major
-
None
With the recent changes to auto-inject a jnlp container into the pod template, Jenkinsfiles which do not explicitly indicate which container to use are broken.
These jenkinsfiles previously worked correctly when used with a podtemplate which defined a container image which provided both the tools the jenkinsfile needed(eg maven) and also started up jnlp.
Now that the plugin is adding its own jnlp container, the jenkinsfile commands are run in the new container which does not have maven(for example) and the jenkinsfile fails.
I think the plugin should default to running the commands in the container defined by the user's explicit configuration, not the container being added implicitly by the plugin, the current behavior breaks backwards compatibility for existing configurations/jenkinsfiles.
- duplicates
-
-
- Closed
-
- is duplicated by
-
JENKINS-47760 Container selection should default to user container
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Resolved
-
