Clean up gzdev calls and use docker cache via ADD for gzdev changes #1200
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.
The PR clean up most of the gzdev code that deal with possible changes in gzdev configuraton in different parts of the Dockerfile: The mechanism used is to leverage the caching actions to the Docker layer caching using the
ADD https://api.github.com/repos/gazebo-tooling/gzdev/git/refs/heads/$branch version.json
that should invalidate the cache on changes done to the branch inside gzdev (affecting code or configurations). The current implementation will invalidate all the cache on any change to the gzdev branch.The PR also changes the installation of gzdev to be under the /root directory.