Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Fix Docker RMI Failure #1113

Merged
merged 3 commits into from
Jun 3, 2021
Merged

Fix Docker RMI Failure #1113

merged 3 commits into from
Jun 3, 2021

Conversation

kj4ezj
Copy link
Contributor

@kj4ezj kj4ezj commented Jun 2, 2021

Change Description

From #help-automation, eosio-dot-cdt build 3461, and AUTO-876 in epic AUTO-880, tagged builds are failing because the docker rmi command is not followed by an "or no-op" || : to suppress the error if the image no longer exists.

This is an error we have already solved in EOSIO. In fact, quite a bit of work has gone into the equivalent script in EOSIO, so I just went ahead and copied it here (with the relevant name changes) from commit a7b5566.

I also brought in the branch name sanitation code I wrote for AUTO-848. The set of characters allowed in git branch names is much larger than the set of characters allowed in docker container names, so this code removes or replaces those characters following a specific and predictable pattern.

See Also

API Changes

  • API Changes

None.

Documentation Additions

  • Documentation Additions

None.

This was referenced Jun 2, 2021
@kj4ezj kj4ezj merged commit f624906 into release/1.8.x Jun 3, 2021
@kj4ezj kj4ezj deleted the zach-rmi-1.8 branch June 3, 2021 12:36
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants