-
Notifications
You must be signed in to change notification settings - Fork 52
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
set multiarch container as default, disable... #177
Conversation
Question: should we move from
to new repo in existing quay che-incubator org?
That way we're not using as part of the build process, when we're ultimately pushing to Quay anyway. |
No changes to code coverage between the base branch and the head branch |
✅ E2E dashboard-next tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-177 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nobody complained about removing multi-arch build, it's why it was made as optional due stability reasons.
I see potential value in multiarch build as default but github workflow should be reworked in the corresponding way where each (or some of) architectures are mandatory.
And then I don't see a value in keeping single arch image if Che Server and deployments depends on multiarch.
So, in general I'm OK with proposed multiarch by default, but if it won't be stable again, we will need to review it.
7e808c2
to
e9e10f7
Compare
❌ E2E dashboard-next tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
No changes to code coverage between the base branch and the head branch |
Docker image build succeeded: docker.io/maxura/che-server:che-dashboard-pull-177 |
[dashboard-next-ci-test] |
❌ E2E dashboard-next tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
[dashboard-next-ci-test] |
✅ E2E dashboard-next tests succeed 🎉 See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)
|
e9e10f7
to
de97a23
Compare
Codecov Report
@@ Coverage Diff @@
## main #177 +/- ##
=======================================
Coverage 51.51% 51.51%
=======================================
Files 143 143
Lines 5536 5536
Branches 913 913
=======================================
Hits 2852 2852
Misses 2410 2410
Partials 274 274 Continue to review full report at Codecov.
|
@@ -106,5 +104,5 @@ jobs: | |||
echo "[!] The job 'build-images' didn't provide any outputs. Can't create the manifest list." | |||
exit 1; | |||
fi | |||
docker manifest create ${{ env.IMAGE }}:multiarch-next $AMEND | |||
docker manifest push ${{ env.IMAGE }}:multiarch-next | |||
docker manifest create ${{ env.IMAGE }}:next $AMEND |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, it also requires adapting PR check not to pass when multiarch build fails.
And it has a drawback... For some reason amd64 build takes 4-6 minutes, while other 35-45 minutes which is not critical but not pleasure when you add a rewording fix in the PR before merging.
Docker image build succeeded: docker.io/maxura/che-dashboard:che-dashboard-pull-177 |
1 similar comment
Docker image build succeeded: docker.io/maxura/che-dashboard:che-dashboard-pull-177 |
✅ E2E dashboard tests succeed 🎉 See Details
Test product:
Eclipse Che QE channel: https://mattermost.eclipse.org/eclipse/channels/eclipse-che-qe |
❌ E2E dashboard tests failed ❗ See Details
Test product:
Eclipse Che QE channel: https://mattermost.eclipse.org/eclipse/channels/eclipse-che-qe |
What does this PR do?
set multiarch container as default, disable single-arch build
Change-Id: I3bf13419e30b11b520b4243dbb21b0cf6374547f
Signed-off-by: nickboldt [email protected]
Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
eclipse-che/che#19688 (moving to travis for multiarch)
How to test this PR?
N/A
PR Checklist
As the author of this Pull Request I made sure that:
Reviewers
Reviewers, please comment how you tested the PR when approving it.