-
Notifications
You must be signed in to change notification settings - Fork 787
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
jx upgrade boot doesn't fetch the tag to upgrade to, so hits cherry pick error #5974
Labels
area/boot
issues in the `jx boot` command
area/fox
area/upgrade
kind/bug
Issue is a bug
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
Milestone
Comments
abayer
added
kind/bug
Issue is a bug
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
area/upgrade
area/fox
area/boot
issues in the `jx boot` command
in progress
estimate/S
labels
Oct 29, 2019
Think I've got the fix, but I'm working on getting a test written to verify it first. |
abayer
added a commit
to abayer/jx
that referenced
this issue
Oct 29, 2019
…efore cherrypicking Without doing that, the cherry-pick will fail due to the commit from the release tag not being present in the local boot repo, since it's not on master. I had to set a brief sleep between `o.bootConfigRef` calls due to jenkins-x#5976 causing git to still be auto-GCing from the first call when it tries to delete and reclone for the second. fixes jenkins-x#5974 Signed-off-by: Andrew Bayer <[email protected]>
Merged
2 tasks
abayer
added a commit
to abayer/jx
that referenced
this issue
Oct 30, 2019
…efore cherrypicking Without doing that, the cherry-pick will fail due to the commit from the release tag not being present in the local boot repo, since it's not on master. fixes jenkins-x#5974 Signed-off-by: Andrew Bayer <[email protected]>
abayer
added a commit
to abayer/jx
that referenced
this issue
Oct 30, 2019
…efore cherrypicking Without doing that, the cherry-pick will fail due to the commit from the release tag not being present in the local boot repo, since it's not on master. fixes jenkins-x#5974 Signed-off-by: Andrew Bayer <[email protected]>
jenkins-x-bot
pushed a commit
that referenced
this issue
Oct 30, 2019
…efore cherrypicking Without doing that, the cherry-pick will fail due to the commit from the release tag not being present in the local boot repo, since it's not on master. fixes #5974 Signed-off-by: Andrew Bayer <[email protected]>
daveconde
pushed a commit
to daveconde/jx
that referenced
this issue
Apr 7, 2020
…efore cherrypicking Without doing that, the cherry-pick will fail due to the commit from the release tag not being present in the local boot repo, since it's not on master. fixes jenkins-x#5974 Signed-off-by: Andrew Bayer <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/boot
issues in the `jx boot` command
area/fox
area/upgrade
kind/bug
Issue is a bug
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
So what's happening here is that
1263ab91e40f6f4fe2d88f33942fca6ec5dc7765
is the release tag commit forv1.0.36
, but since we callo.Git().FetchBranch(o.Dir, bootConfigURL, "master")
, we don't have that commit in the local repo. We need to fetch the upgrade SHA, not the master branch.The text was updated successfully, but these errors were encountered: