[v10] APT/YUM publishing fixes#17646
Merged
Merged
Conversation
These were running in parallel, but we want them to run serially. Therefore, we add a dependency between each step and its previous step.
r0mant
reviewed
Oct 21, 2022
Collaborator
r0mant
left a comment
r0mant
left a comment
There was a problem hiding this comment.
Because the v10 version of this patch stack is the same as the v11 version. I do not plan to run a build and promote specifically for v10.
Can you test it? Last 2 v10 releases had hiccups related to apt/yum publishing so I'd rather not take chances and make sure it works.
Contributor
Author
Sure -- I'll update the description in a moment with links. edit: updated |
This helps test a couple more changes from this pipeline when cutting a dev build. Particularly, we saw the download and role assumption steps fail in #17334, and this change would have allowed us to catch that error during testing.
This bug does not appear to affect anything currently. However it should be fixed in case the rm is important at some point in the future. The bug is: when a wildcard is inside quotes, it is treated as a literal filename. So rm -rf "$ARTIFACT_PATH/*" tries to remove the file named '*' instead of trying to remove everything in artifact path.
All other roles environment variables end in AWS_ROLE, and consistency is our friend here.
wadells
force-pushed
the
walt/v10-fix-yum-race
branch
from
770ddf2 to
224a289
Compare
reedloden
approved these changes
Oct 21, 2022
r0mant
approved these changes
Oct 21, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backports #17638
This PR includes a variety of fixes and improvements to our apt & yum promotion pipelines. These are broken out by commit:
Serialize apt/yum promote pipelinesfixes the errors seen in https://drone.platform.teleport.sh/gravitational/teleport/16694/1/5 by serializing pipeline steps via dependencies.Allow dev build promotes to proceed in deb/rpm pipelinesallows us to test the fix above, which was formerly skipped on promotes of dev builds. This is the future of the changes proposed in Allow dev build promotes to proceed in deb/rpm pipelines #17340Fix globbing bugfixes a seemingly harmless globbing bug. This was opportunistic cleanup.Swap YUM_REPO_NEW_ROLE to YUM_REPO_NEW_AWS_ROLEintroduces the changes from [v10] Swap YUM_REPO_NEW_ROLE to YUM_REPO_NEW_AWS_ROLE #17408, in case this lands first.No further changes changes/merged conflic resolution was needed for v10 beyond what I did for v11 in #17645
Testing
Tag: https://drone.platform.teleport.sh/gravitational/teleport/16752
Promote: https://drone.platform.teleport.sh/gravitational/teleport/16758
I won't merge until I see both of these are green.