Create 'Dockerfile' to configure ci-operator #495
Conversation
artaleks9
requested review from
l0rd,
ibuziuk,
vinokurig and
nickboldt
as code owners
|
@artaleks9: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
artaleks9
requested review from
dmytro-ndp,
svor and
tolusha
and removed request for
nickboldt,
l0rd and
ibuziuk
|
Build 3.7 :: server_3.x/157: Console, Changes, Git Data |
| @@ -0,0 +1,28 @@ | |||
| #!/bin/bash | |||
| # | |||
| # Copyright (c) 2019-2021 Red Hat, Inc. | |||
There was a problem hiding this comment.
| # Copyright (c) 2019-2021 Red Hat, Inc. | |
| # Copyright (c) 2023 Red Hat, Inc. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: artaleks9, svor, tolusha 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.7 :: sync-to-downstream_3.x/3014: Console, Changes, Git Data |
|
Build 3.7 :: push-latest-container-to-quay_3.x/2141: Console, Changes, Git Data |
|
Build 3.7 :: get-sources-rhpkg-container-build_3.x/2827: server : 3.x :: Build 51979946 : quay.io/devspaces/server-rhel8:3.7-4 |
|
Build 3.7 :: update-digests_3.x/2784: Console, Changes, Git Data |
|
Build 3.7 :: server_3.x/157: Upstream sync done; /DS_CI/sync-to-downstream_3.x/3014 triggered |
|
Build 3.7 :: operator-bundle_3.x/1125: Console, Changes, Git Data |
|
Build 3.7 :: sync-to-downstream_3.x/3015: Console, Changes, Git Data |
|
Build 3.7 :: push-latest-container-to-quay_3.x/2142: Console, Changes, Git Data |
|
Build 3.7 :: copyIIBsToQuay/1236: Console, Changes, Git Data |
|
Build 3.7 :: sync-to-downstream_3.x/3015: Build container: devspaces-operator-bundle synced; /DS_CI/get-sources-rhpkg-container-build_3.x/2828 triggered; /job/DS_CI/job/dsc_3.x triggered; |
|
Build 3.7 :: operator-bundle_3.x/1125: Upstream sync done; /DS_CI/sync-to-downstream_3.x/3015 triggered |
|
Build 3.7 :: dsc_3.x/798: Console, Changes, Git Data |
|
Build 3.7 :: update-digests_3.x/2784: Detected new images: rebuild operator-bundle |
|
Build 3.7 :: dsc_3.x/798: 3.7.0 CI |
|
Build 3.7 :: server_3.x/158: Console, Changes, Git Data |
|
Build 3.7 :: sync-to-downstream_3.x/3051: Console, Changes, Git Data |
|
Build 3.7 :: push-latest-container-to-quay_3.x/2175: Console, Changes, Git Data |
|
Build 3.7 :: get-sources-rhpkg-container-build_3.x/2873: server : 3.x :: Build 52034951 : quay.io/devspaces/server-rhel8:3.7-5 |
|
Build 3.7 :: server_3.x/158: Upstream sync done; /DS_CI/sync-to-downstream_3.x/3051 triggered |
|
Build 3.7 :: update-digests_3.x/2819: Console, Changes, Git Data |
|
Build 3.7 :: operator-bundle_3.x/1143: Console, Changes, Git Data |
|
Build 3.7 :: sync-to-downstream_3.x/3056: Console, Changes, Git Data |
|
Build 3.7 :: push-latest-container-to-quay_3.x/2185: Console, Changes, Git Data |
|
Build 3.7 :: sync-to-downstream_3.x/3056: Build container: devspaces-operator-bundle synced; /DS_CI/get-sources-rhpkg-container-build_3.x/2880 triggered; /job/DS_CI/job/dsc_3.x triggered; |
|
Build 3.7 :: operator-bundle_3.x/1143: Upstream sync done; /DS_CI/sync-to-downstream_3.x/3056 triggered |
|
Build 3.7 :: copyIIBsToQuay/1256: Console, Changes, Git Data |
|
Build 3.7 :: dsc_3.x/818: Console, Changes, Git Data |
|
Build 3.7 :: update-digests_3.x/2819: Detected new images: rebuild operator-bundle |
|
Build 3.7 :: dsc_3.x/818: 3.7.0 CI |
What does this PR do?
the build root failed after 22s with reason ManageDockerfileFailed: Failed to prepare the dockerfile for the build.Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
eclipse-che/che#21753
How to test this PR?
N/A
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.