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

compose: Add --no-parent option #1829

Closed
wants to merge 3 commits into from
Closed

Conversation

jlebon
Copy link
Member

@jlebon jlebon commented May 8, 2019

There are cases where we do want all the things that specifying a ref
provides (e.g. change detection, version incrementing, SELinux labeling
optimizations, and of course writing the ref) but we don't want the
new commit to have a parent. Add a new --no-parent option to
accommodate this.

This will be used by coreos-assembler. See discussions at
coreos/coreos-assembler#159.

@jlebon
Copy link
Member Author

jlebon commented May 8, 2019

Requires: #1828.

jlebon added 3 commits May 8, 2019 15:03
We had a subtest that wasn't actually part of the `basic_test()` and so
was being executed when the file gets sourced instead of the function
being explicitly called.
There are cases where we do want all the things that specifying a ref
provides (e.g. change detection, version incrementing, SELinux labeling
optimizations, and of course writing the ref) but we *don't* want the
new commit to have a parent. Add a new `--no-parent` option to
accommodate this.

This will be used by coreos-assembler. See discussions at
coreos/coreos-assembler#159.
This allows one to run the tests from a container using overlay +
SELinux protection by running the actual compose into a non-overlay
bind-mount. Otherwise, we'll hit `ENOTSUP` when trying to set labels on
various checkouts.
@jlebon
Copy link
Member Author

jlebon commented May 8, 2019

Rebased!

@cgwalters
Copy link
Member

@rh-atomic-bot r+ 67ce461

rh-atomic-bot pushed a commit that referenced this pull request May 8, 2019
We had a subtest that wasn't actually part of the `basic_test()` and so
was being executed when the file gets sourced instead of the function
being explicitly called.

Closes: #1829
Approved by: cgwalters
@rh-atomic-bot
Copy link

⌛ Testing commit 67ce461 with merge ff77258...

rh-atomic-bot pushed a commit that referenced this pull request May 8, 2019
There are cases where we do want all the things that specifying a ref
provides (e.g. change detection, version incrementing, SELinux labeling
optimizations, and of course writing the ref) but we *don't* want the
new commit to have a parent. Add a new `--no-parent` option to
accommodate this.

This will be used by coreos-assembler. See discussions at
coreos/coreos-assembler#159.

Closes: #1829
Approved by: cgwalters
rh-atomic-bot pushed a commit that referenced this pull request May 8, 2019
This allows one to run the tests from a container using overlay +
SELinux protection by running the actual compose into a non-overlay
bind-mount. Otherwise, we'll hit `ENOTSUP` when trying to set labels on
various checkouts.

Closes: #1829
Approved by: cgwalters
@rh-atomic-bot
Copy link

💔 Test failed - status-atomicjenkins

@jlebon
Copy link
Member Author

jlebon commented May 9, 2019

@rh-atomic-bot retry

@rh-atomic-bot
Copy link

⌛ Testing commit 67ce461 with merge 4d84595...

rh-atomic-bot pushed a commit that referenced this pull request May 9, 2019
There are cases where we do want all the things that specifying a ref
provides (e.g. change detection, version incrementing, SELinux labeling
optimizations, and of course writing the ref) but we *don't* want the
new commit to have a parent. Add a new `--no-parent` option to
accommodate this.

This will be used by coreos-assembler. See discussions at
coreos/coreos-assembler#159.

Closes: #1829
Approved by: cgwalters
rh-atomic-bot pushed a commit that referenced this pull request May 9, 2019
This allows one to run the tests from a container using overlay +
SELinux protection by running the actual compose into a non-overlay
bind-mount. Otherwise, we'll hit `ENOTSUP` when trying to set labels on
various checkouts.

Closes: #1829
Approved by: cgwalters
@rh-atomic-bot
Copy link

☀️ Test successful - status-atomicjenkins
Approved by: cgwalters
Pushing 4d84595 to master...

jlebon added a commit to jlebon/rpm-ostree that referenced this pull request Jul 18, 2019
This may seem like a backflip on coreos#1829, but there's a common theme here:
in a promotion workflow, the parent (or lack of parent) of a commit is
an important parameter, so we need full flexibility in configuring it.

But again, like coreos#1829, we still want e.g. change detection, versioning,
and various optimizations to happen on whatever the latest commit on
that ref is in the build repo.
jlebon added a commit to jlebon/rpm-ostree that referenced this pull request Jul 18, 2019
This may seem like a backflip on coreos#1829, but there's a common theme here:
in a promotion workflow, the parent (or lack of parent) of a commit is
an important parameter, so we need full flexibility in configuring it.

But again, like coreos#1829, we still want e.g. change detection, versioning,
and various optimizations to happen on whatever the latest commit on
that ref is in the build repo.
rh-atomic-bot pushed a commit that referenced this pull request Jul 19, 2019
This may seem like a backflip on #1829, but there's a common theme here:
in a promotion workflow, the parent (or lack of parent) of a commit is
an important parameter, so we need full flexibility in configuring it.

But again, like #1829, we still want e.g. change detection, versioning,
and various optimizations to happen on whatever the latest commit on
that ref is in the build repo.

Closes: #1871
Approved by: cgwalters
rh-atomic-bot pushed a commit that referenced this pull request Jul 19, 2019
This may seem like a backflip on #1829, but there's a common theme here:
in a promotion workflow, the parent (or lack of parent) of a commit is
an important parameter, so we need full flexibility in configuring it.

But again, like #1829, we still want e.g. change detection, versioning,
and various optimizations to happen on whatever the latest commit on
that ref is in the build repo.

Closes: #1871
Approved by: cgwalters
rh-atomic-bot pushed a commit that referenced this pull request Jul 19, 2019
This may seem like a backflip on #1829, but there's a common theme here:
in a promotion workflow, the parent (or lack of parent) of a commit is
an important parameter, so we need full flexibility in configuring it.

But again, like #1829, we still want e.g. change detection, versioning,
and various optimizations to happen on whatever the latest commit on
that ref is in the build repo.

Closes: #1871
Approved by: cgwalters
@jlebon jlebon deleted the pr/no-parent branch April 23, 2023 23:32
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.

3 participants