We have a Jenkins install that uses AWS ECR as a registry. We authenticate using the aws credentials chain (instance profile). Today we updated the Declarative plugin to 1.3.5 which broke all of our builds. Checking the changelog as Jira guidelines suggest do not include any changes to docker, however after reviewing the commit log in the repository it seems that
JENKINS-49950 is an unlisted change between 220.127.116.11 and 1.3.5.
Pipeline code that worked prior to the update:
After updating the plugin, the pipeline will not check the registry for the image.
Log output prior to update:
Log output after updating:
We have never needed to provide the credentailsId, however commit https://github.com/jenkinsci/pipeline-model-definition-plugin/commit/28d0aca0d9f4d54ee25e4d393a6683d92055aad3 appears to make this required. There was no indication that this would not be backwards compatible in the changelog.
Upon reverting the Declarative plugin to 18.104.22.168 has restored functionality. No other plugin needed to be rolled back.