Skip to content

Conversation

@BenjaminRodenberg
Copy link
Member

@BenjaminRodenberg BenjaminRodenberg commented Mar 31, 2025

  • Apply tag for both jobs
  • Set default if not run via workflow_dispatch

Apply tag for both jobs
@BenjaminRodenberg BenjaminRodenberg self-assigned this Mar 31, 2025
Copy link
Member

@IshaanDesai IshaanDesai left a comment

Choose a reason for hiding this comment

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

The default tag is nightly, so why do we need to additionally mention this now? Also, having such a tag specification is only relevant for release testing, right? Or is there some other motivation?

@BenjaminRodenberg
Copy link
Member Author

The default tag is nightly, so why do we need to additionally mention this now?

What do you mean? Be aware that if a workflow is triggered by a push that this does not pick up the defaults from the workflow dispatch. Meaning: this line evaluates to precice/precice: because ${{ inputs.docker_image_tag }} is undefined.

Also, having such a tag specification is only relevant for release testing, right? Or is there some other motivation?

Yes. That's the only reason.

@IshaanDesai
Copy link
Member

What do you mean? Be aware that if a workflow is triggered by a push that this does not pick up the defaults from the workflow dispatch.

Ah okay. I was missing this information about the function of how the default works 👍

@BenjaminRodenberg
Copy link
Member Author

What do you mean? Be aware that if a workflow is triggered by a push that this does not pick up the defaults from the workflow dispatch.

Ah okay. I was missing this information about the function of how the default works 👍

It's also 100% not intuitive. If you want to convince yourself that this is not your fault: Take a look at https://github.com/orgs/community/discussions/26322 😅

@BenjaminRodenberg BenjaminRodenberg merged commit c7384bf into develop Mar 31, 2025
7 of 8 checks passed
@BenjaminRodenberg BenjaminRodenberg deleted the fix-workflow-dispatch branch March 31, 2025 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants