Skip to content

Fix error when docker-image-common.yml runs on new tag#3140

Merged
samsrabin merged 3 commits into
ESCOMP:b4b-devfrom
samsrabin:simplify-docker-image-common
May 20, 2025
Merged

Fix error when docker-image-common.yml runs on new tag#3140
samsrabin merged 3 commits into
ESCOMP:b4b-devfrom
samsrabin:simplify-docker-image-common

Conversation

@samsrabin

@samsrabin samsrabin commented May 20, 2025

Copy link
Copy Markdown
Member

Description of changes

  • Delete an unused and possibly bad output
  • Try another way to get one image tag

Specific notes

Contributors other than yourself, if any: None

CTSM Issues Fixed:

Are answers expected to change (and if so in what way)? No

Any User Interface Changes (namelist or namelist defaults changes)? No

Does this create a need to change or add documentation? Did you do so? No

Testing performed, if any: Tested in a separate repository and it works!

@samsrabin samsrabin self-assigned this May 20, 2025
@samsrabin samsrabin added b4b bit-for-bit devops Development Operations to improve development throughput, E.g., adding GitHub Workflows labels May 20, 2025
@samsrabin samsrabin changed the title Fixes to docker-image-common.yml Fix docker-image-common.yml running on new tag May 20, 2025
Comment thread .github/workflows/docker-image-common.yml
Comment thread .github/workflows/docker-image-build.yml
@samsrabin samsrabin changed the title Fix docker-image-common.yml running on new tag Fix error when docker-image-common.yml runs on new tag May 20, 2025
@samsrabin samsrabin marked this pull request as ready for review May 20, 2025 21:27

@ekluzek ekluzek left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks right to me as well. The pathname fix is obviously required. And I looked at the change by hand, and think it makes sense to me, in removing the newline from the tagnames.

The one thing I wonder about though -- do we WANT the workflow to run on both push to master and the tag made immediately afterwards? And do we want it to run on push to b4b-dev? I'll let you think on that and decide, so approving.

Comment thread .github/workflows/docker-image-common.yml
Comment thread .github/workflows/docker-image-build.yml
@samsrabin samsrabin merged commit beebd92 into ESCOMP:b4b-dev May 20, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

b4b bit-for-bit devops Development Operations to improve development throughput, E.g., adding GitHub Workflows

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants