Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix publish frontend workflow by specifying jammy instead of latest ubuntu #247

Merged
merged 1 commit into from
Jan 21, 2025

Conversation

omar-selo
Copy link
Collaborator

Description

Charm builds on jammy so the runner building it must run jammy too.

Resolved issues

Fixes https://warthogs.atlassian.net/browse/RTW-427

Documentation

Web service API changes

Tests

@omar-selo omar-selo requested a review from a team January 20, 2025 13:20
Copy link
Contributor

@andrejvelichkovski andrejvelichkovski left a comment

Choose a reason for hiding this comment

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

LGTM!

@@ -53,7 +53,7 @@ jobs:

build-and-push-frontend-charm:
needs: build-and-push-frontend-image
runs-on: ubuntu-latest
runs-on: [self-hosted, linux, xlarge, jammy, x64]
Copy link
Contributor

Choose a reason for hiding this comment

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

Do the other options (all apart from jammy) guarantee that they will run jammy?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Based on the GH documentation

If you specify an array of strings or variables, your workflow will execute on any runner that matches all of the specified runs-on values. For example, here the job will only run on a self-hosted runner that has the labels linux, x64, and gpu:

runs-on: [self-hosted, linux, x64, gpu]

the existence of jammy keyword ensures that the runner will be jammy. It's basically an "and" comparison not "or".

@omar-selo omar-selo merged commit a4770f3 into main Jan 21, 2025
1 check passed
@omar-selo omar-selo deleted the fix-publish-frontend-workflow branch January 21, 2025 09:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants