Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation/summary
I initially was tempted to add a retry/sleep command to wrap the packaging stage but it looks like it might cause some other issues, such as the workspace being reused (maybe go doesn't like it) and a bit hard to maintain.
This is a bit more elegant, based on the packer-cache approach that we use for other projects.
It will cache the required docker images for the packaging stage in the CI since those docker images are pulled from the docker registry everytime a build is triggered by the master branch. It will help to speed up the builds and avoid any kind of environmental issues with
500
errors.Just to clarify we do have something in place:
But it's not dynamic based on the go-version.
How to test these changes
Related issues
Further details
There is an entry for this project in the infra side
ansible/playbooks/group_vars/apm-ci/jenkins.yml
: