-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
-
Declarative backlog
I was having issues with configuring a docker agent in a declarative pipeline project, which I tracked down to an inconsistency with the way the configuration parameters are handled while pulling and running the image.
Given a configuration that includes this:
agent { docker { registryUrl "https://my-project.nexus.mydomain.com" registryCredentialsId "myproject-registry-creds" image "myproject/build:latest" } }
I would expect to happen given this configuration would be something like this:
docker pull my-project.nexus.mydomain.com/myproject/build:latest docker run ... my-project.nexus.mydomain.com/myproject/build:latest
What actually happens though, is this:
Unable to find source-code formatter for language: shell. Available languages are: actionscript, ada, applescript, bash, c, c#, c++, cpp, css, erlang, go, groovy, haskell, html, java, javascript, js, json, lua, none, nyan, objc, perl, php, python, r, rainbow, ruby, scala, sh, sql, swift, visualbasic, xml, yaml
docker pull my-project.nexus.mydomain.com/myproject/build:latest docker run ... myproject/build:latest
This means that even though the console logs showed the correct image being pulled, a different image was actually run.
[JENKINS-49280] pipeline docker agent configuration is inconsistent
Assignee | Original: Andrew Bayer [ abayer ] | New: Jose Blas Camacho Taboada [ jtaboada ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Sprint | New: Declarative backlog [ 621 ] |
Labels | New: triaged-2018-11 |
Labels | Original: triaged-2018-11 |
Status | Original: In Progress [ 3 ] | New: Open [ 1 ] |
Assignee | Original: Jose Blas Camacho Taboada [ jtaboada ] |