Check in go changes for CRW-4933 to 7.76 #1771
Conversation
Downside of short sprints is if a release gets delayed I have to change the same thing into 3 branches...
SDawley
requested review from
nickboldt,
tolusha,
ibuziuk and
l0rd
as code owners
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: SDawley The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Build 3.10 :: operator_3.10/4: Console, Changes, Git Data |
|
Build 3.10 :: operator_3.10/4: Upstream sync done; No sync or Brew build |
|
Build 3.10 :: operator_3.10/5: Console, Changes, Git Data |
|
Build 3.10 :: operator-bundle_3.10/16: Console, Changes, Git Data |
|
Build 3.10 :: sync-to-downstream_3.10/52: Console, Changes, Git Data |
|
Build 3.10 :: sync-to-downstream_3.10/53: Console, Changes, Git Data |
|
Build 3.10 :: push-latest-container-to-quay_3.10/16: Console, Changes, Git Data |
|
Build 3.10 :: push-latest-container-to-quay_3.10/17: Console, Changes, Git Data |
|
Build 3.10 :: get-sources-rhpkg-container-build_3.10/49: devspaces-operator : 3.10 :: Build 56579661 : quay.io/devspaces/devspaces-rhel8-operator:3.10-20 |
|
Build 3.10 :: operator_3.10/5: Upstream sync done; /DS_CI/sync-to-downstream_3.10/52 triggered |
|
Build 3.10 :: sync-to-downstream_3.10/53: Build container: devspaces-operator-bundle synced; /DS_CI/get-sources-rhpkg-container-build_3.10/50 triggered; /job/DS_CI/job/dsc_3.10 triggered; |
|
Build 3.10 :: operator-bundle_3.10/16: Upstream sync done; /DS_CI/sync-to-downstream_3.10/53 triggered |
|
Build 3.10 :: copyIIBsToQuay/2019: Console, Changes, Git Data |
|
Build 3.10 :: dsc_3.10/8: Console, Changes, Git Data |
|
Build 3.10 :: update-digests_3.10/32: Console, Changes, Git Data |
|
Build 3.10 :: update-digests_3.10/32: No new images detected: nothing to do! |
|
Build 3.10 :: operator_3.10/6: Console, Changes, Git Data |
|
Build 3.10 :: sync-to-downstream_3.10/57: Console, Changes, Git Data |
|
Build 3.10 :: operator-bundle_3.10/18: Console, Changes, Git Data |
|
Build 3.10 :: sync-to-downstream_3.10/66: Console, Changes, Git Data |
|
Build 3.10 :: push-latest-container-to-quay_3.10/31: Console, Changes, Git Data |
|
Build 3.10 :: copyIIBsToQuay/2023: Console, Changes, Git Data |
|
Build 3.10 :: sync-to-downstream_3.10/66: Build container: devspaces-operator-bundle synced; /DS_CI/get-sources-rhpkg-container-build_3.10/64 triggered; /job/DS_CI/job/dsc_3.10 triggered; |
|
Build 3.10 :: operator-bundle_3.10/18: Upstream sync done; /DS_CI/sync-to-downstream_3.10/66 triggered |
|
Build 3.10 :: dsc_3.10/10: Console, Changes, Git Data |
|
Build 3.10 :: operator-bundle_3.10/19: Console, Changes, Git Data |
|
Build 3.10 :: sync-to-downstream_3.10/68: Console, Changes, Git Data |
|
Build 3.10 :: push-latest-container-to-quay_3.10/34: Console, Changes, Git Data |
|
Build 3.10 :: copyIIBsToQuay/2024: Console, Changes, Git Data |
|
Build 3.10 :: sync-to-downstream_3.10/68: Build container: devspaces-operator-bundle synced; /DS_CI/get-sources-rhpkg-container-build_3.10/67 triggered; /job/DS_CI/job/dsc_3.10 triggered; |
|
Build 3.10 :: operator-bundle_3.10/19: Upstream sync done; /DS_CI/sync-to-downstream_3.10/68 triggered |
|
Build 3.10 :: dsc_3.10/11: Console, Changes, Git Data |
|
Build 3.10 :: operator-bundle_3.10/20: Console, Changes, Git Data |
|
Build 3.10 :: sync-to-downstream_3.10/69: Console, Changes, Git Data |
|
Build 3.10 :: push-latest-container-to-quay_3.10/35: Console, Changes, Git Data |
|
Build 3.10 :: copyIIBsToQuay/2033: Console, Changes, Git Data |
|
Build 3.10 :: sync-to-downstream_3.10/69: Build container: devspaces-operator-bundle synced; /DS_CI/get-sources-rhpkg-container-build_3.10/68 triggered; /job/DS_CI/job/dsc_3.10 triggered; |
|
Build 3.10 :: operator-bundle_3.10/20: Upstream sync done; /DS_CI/sync-to-downstream_3.10/69 triggered |
|
Build 3.10 :: dsc_3.10/12: Console, Changes, Git Data |
Downside of short sprints is if a release gets delayed I have to change the same thing into 3 branches...
PR Checklist
As the author of this Pull Request I made sure that:
What issues does this PR fix or referenceandHow to test this PRcompletedReviewers
Reviewers, please comment how you tested the PR when approving it.