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

Tweak versioning and set up Zincati & pinger enablement #112

Merged
merged 4 commits into from
Jul 12, 2019

Conversation

jlebon
Copy link
Member

@jlebon jlebon commented Jul 10, 2019

See individual commit messages for details.

In coreos/fedora-coreos-tracker#81, we agreed
on a versioning scheme for releases. This patch changes
`automatic-version-prefix` to respect this.

Note that it's not a perfect fit, since e.g. the first build doesn't
have a `.0` prefix.

In actuality, versioning in the pipeline will be driven by an external
process, and thus the scheme embedded here will have no effect (unless
we decide to use rpm-ostree itself as part of the external process...
though it'll need some tweaking first).

So really, this is more for the benefit of local developers so that
versioning looks similar to release builds.
We want to be able to distinguish between release and non-release
builds. To do this, we embed a `.dev` marker in the version string so
that the default developer workflow will use this. As mentioned in the
previous commit message, this will be overridden for release streams.

See coreos/fedora-coreos-tracker#212 for more
information about this.
On non-release/local developer builds, we don't want Zincati or pinger
to be active by default. Key off of the OSTree version and add a config
dropin to do this.

See discussions about this in:
coreos/fedora-coreos-tracker#212
By default, we don't enable Zincati and pinger on testing-devel. See
discussions in:

coreos/fedora-coreos-tracker#163
Copy link
Contributor

@rfairley rfairley left a comment

Choose a reason for hiding this comment

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

LGTM

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.

None yet

3 participants