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

Gemfile: Pin to Puppet ~> 7.24 #824

Merged
merged 1 commit into from
Apr 27, 2023
Merged

Conversation

bastelfreak
Copy link
Member

This is the first step to deprecate puppet 6. We raise the default puppet version in the Gemfile in our modules. also we limit it to 7.x so we don't pull in puppet 8 by accident. And we pin to 7.24 or newer to prevent issues with ruby-concurrent.

This is the first step to deprecate puppet 6. We raise the default
puppet version in the Gemfile in our modules. also we limit it to 7.x so
we don't pull in puppet 8 by accident. And we pin to 7.24 or newer to
prevent issues with ruby-concurrent.
Copy link
Member

@smortex smortex left a comment

Choose a reason for hiding this comment

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

Looks good. I guess we will change this back to a >= at some point when Puppet 8 has settled?

@bastelfreak
Copy link
Member Author

I'm not sure yet. We saw breaking CI pipelines because we had >= 6 and unexpectedly got puppet 8. In gems we try to set upper versions. I think ~> 7.24 is fine now and as soon as puppet 8 is available we could move to ~> 8.0.1. This is just a default/fallback. It can be overwritten via environment variable (and we do that in CI).

@bastelfreak bastelfreak merged commit 6718cab into voxpupuli:master Apr 27, 2023
@bastelfreak bastelfreak deleted the puppet8 branch April 27, 2023 06:45
@@ -13,7 +13,7 @@
Jenkinsfile:
delete: true
Gemfile:
puppet_version: '>= 6.0'
puppet_version: '~> 7.24'
Copy link
Member

Choose a reason for hiding this comment

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

Previously it also allowed Puppet 8, now it no longer does. Is this intended?

Copy link
Member Author

Choose a reason for hiding this comment

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

indeed. we allowed puppet 8 and that break our CI. To prevent that in the future it makes sense to limit to a single version. and the gemfile has an environment variable to overwrite it.

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