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

Configure default Python version using integration-tests job environment #473

Merged

Conversation

lgarber-akamai
Copy link
Contributor

@lgarber-akamai lgarber-akamai commented Nov 12, 2024

📝 Description

This pull request fixes a small issue that caused runs triggered by pushes to dev and main to not resolve a valid Python version, leading to a failure. This works by moving the default and EOL Python versions to the job-level environment rather than in the workflow_dispatch input defaults.

Sample Runs:

✔️ How to Test

Manual Testing

  1. Checkout this PR and push it up to your fork's main or dev branch.
  2. Ensure the integration tests workflow successfully installs Python in the following cases:
    • When triggered by a push
    • When manually triggered using a custom Python version
    • When manually triggered with Run EOL python version? set to true

@lgarber-akamai lgarber-akamai added the repo-ci-improvement for improvements in the repository or CI workflow in the changelog. label Nov 12, 2024
@lgarber-akamai lgarber-akamai marked this pull request as ready for review November 12, 2024 15:40
@lgarber-akamai lgarber-akamai requested a review from a team as a code owner November 12, 2024 15:40
@lgarber-akamai lgarber-akamai requested review from yec-akamai and ezilber-akamai and removed request for a team November 12, 2024 15:40
@ykim-akamai
Copy link
Contributor

Thank you for the fix!

@@ -28,11 +27,14 @@ on:
- main
- dev

env:
DEFAULT_PYTHON_VERSION: "3.10"
EOL_PYTHON_VERSION: "3.9"
Copy link
Contributor

Choose a reason for hiding this comment

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

It seems 3.9 is not officially EOL now. Is it okay to leave it as it is?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good call! I just pushed up a commit with the adjusted versions; this probably needs to be applied to the other Python repos too 👍

Copy link
Contributor

@yec-akamai yec-akamai left a comment

Choose a reason for hiding this comment

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

Nice fix!

@lgarber-akamai lgarber-akamai merged commit 9db9dcc into linode:dev Nov 12, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
repo-ci-improvement for improvements in the repository or CI workflow in the changelog.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants