-
Notifications
You must be signed in to change notification settings - Fork 933
remove explicit calls to pyenv #2004
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
Conversation
|
🎉 All Contributor License Agreements have been signed. Ready to merge. |
This comment has been minimized.
This comment has been minimized.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
Removes explicit pyenv commands from the Semaphore CI pipeline to prepare for an upcoming migration to mise.
- Eliminates manual lookup of Python versions and PATH exports across build steps
- Relies solely on the
sem-version pythoncommand to set up the Python environment
MSeal
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Applied a fix for tag builds, looks good now for merge now
This comment has been minimized.
This comment has been minimized.
1 similar comment
emasab
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving for @confluentinc/clients after @MSeal review
What
This changes the Semaphore pipeline to no longer contain explicit calls to
pyenv.This approach will enable an upcoming change to Semaphore agents to replace
pyenvusage withmise, which is an analogous tool that supports many different languages.Checklist
References
JIRA:
Test & Review
Open questions / Follow-ups