Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add 1.18 release notes

...

Jira Issues
anonymoustrue
urlhttps://issues.jenkins-ci.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+docker-workflow-plugin+ORDER+BY+issuetype+ASC%2C+priority+DESC%2C+key+ASC&tempMax=1000

Version history

Version 1.18 (April 2, 2019)

  • Jira
    serverJenkins JIRA
    serverIddd058dce-0c66-3b77-8b09-71b1d7728747
    keyJENKINS-48437
     Allow users with Credentials/UseItem permission (implied by Job/Configure permission) on a Pipeline Job to use credentials which that job has access to in the withDockerRegistry and withDockerServer steps even when Authorize Project Plugin is installed and configured to run builds as a user other than the default Jenkins superuser.
  • Jira
    serverJenkins JIRA
    serverIddd058dce-0c66-3b77-8b09-71b1d7728747
    keyJENKINS-46105
     Extend fix for ARGs in FROM added in version 1.15 to support ARGs with default values.
  • Jira
    serverJenkins JIRA
    serverIddd058dce-0c66-3b77-8b09-71b1d7728747
    keyJENKINS-56674
     Mask environment variables used by steps that use the Launcher API inside of a withDockerContainer step.
  • (PR 153) Update help related to image.pull() to explain what problems might happen if the method is not called.

Version 1.17 (May 18, 2018)

  • Jira
    serverJenkins JIRA
    serverIddd058dce-0c66-3b77-8b09-71b1d7728747
    keyJENKINS-51395
     The withDockerRegistry step now preferentially takes a “flat” argument list, but continues to support older syntaxes, including the one broken in 1.16.
  • Jira
    serverJenkins JIRA
    serverIddd058dce-0c66-3b77-8b09-71b1d7728747
    keyJENKINS-51397
     May solve login issues in certain environments, especially with a custom Docker server endpoint. The non-CLI-based login behavior in 1.15.1 may be restored using the Jenkins startup flag -Dorg.jenkinsci.plugins.docker.commons.credentials.DockerRegistryToken.USE_CUSTOM_LOGIN=true but this suffers from a number of known limitations including lack of guaranteed support for parallel builds on one computer, failure to clean up credentials at the end of a build, incompatibility with the JSON format from some versions of the Docker client, etc.
     

Version 1.16 (May 11, 2018)

  • Jira
    serverJenkins JIRA
    serverIddd058dce-0c66-3b77-8b09-71b1d7728747
    keyJENKINS-38018
     and allied issues: using CLI-based registry login by default

WARNING: introduced some known regressions 

Jira
serverJenkins JIRA
serverIddd058dce-0c66-3b77-8b09-71b1d7728747
keyJENKINS-51395
 & 
Jira
serverJenkins JIRA
serverIddd058dce-0c66-3b77-8b09-71b1d7728747
keyJENKINS-51397

Version 1.15.1 (Feb 13, 2018)

  • Jira
    serverJenkins JIRA
    serverIddd058dce-0c66-3b77-8b09-71b1d7728747
    keyJENKINS-49278
     command in docker agents not detected correctly
  • Jira
    serverJenkins JIRA
    serverIddd058dce-0c66-3b77-8b09-71b1d7728747
    keyJENKINS-42152
     do not use (deprecated) --force when tagging images
  • better error message for JENKINS-41316 

...