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

Runner versioning policy #32

Open
roman-khimov opened this issue Aug 20, 2024 · 3 comments
Open

Runner versioning policy #32

roman-khimov opened this issue Aug 20, 2024 · 3 comments
Labels
feature Completely new functionality I2 Regular impact S4 Routine U4 Nothing urgent

Comments

@roman-khimov
Copy link
Member

Is your feature request related to a problem? Please describe.

I'm always frustrated when we're talking about ubuntu-20.04/ubuntu-22.04/ubuntu-24.04 runners vs ubuntu-latest. We use ubuntu-based runners a lot and either we stick to some specific version and upgrade it from time to time or we're trusting the latest to be OK. Right now we do both, some places have fixed version, some latest. This leads to confusion.

Describe the solution you'd like

Establish some policy wrt this.

Describe alternatives you've considered

Don't worry about it.

Additional context

Just about any version update brings this discussion again and again, like nspcc-dev/rfc6979#10 (comment).

@roman-khimov roman-khimov added U4 Nothing urgent S4 Routine I2 Regular impact feature Completely new functionality labels Aug 20, 2024
@smallhive
Copy link

Using latest makes sense and it should be used by default. If some case requires a specified version, it should be done in place with a comment

@AnnaShaleva
Copy link
Member

Latest version has one drawback: we can’t control runner upgrades which may lead to unexpected job failures when runner version is updated. But these failures not hard to detect/investigate.

Using specific version requires its manual update, and it’s the thing that we should always remember. It’s kind of a drawback to me, and thus I vote for the latest version.

@EESergey
Copy link

If something important might stop working due to a version update, we need to test the new versions. If we are running tests before applying changes, we should use the latest version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Completely new functionality I2 Regular impact S4 Routine U4 Nothing urgent
Projects
None yet
Development

No branches or pull requests

4 participants