Fix publising the next tag on commits to main branch
#616
Conversation
Signed-off-by: Artem Zatsarynnyi <[email protected]>
azatsarynnyy
requested review from
RomanNikitenko and
vitaliy-guliy
as code owners
|
Click here to review and test in web IDE: |
&message=Dev%20cluster%20(for%20maintainers)&logo=eclipseche&color=525C86&labelColor=FDB940)
azatsarynnyy
changed the title
next tag on commits to main branch
Signed-off-by: Artem Zatsarynnyi <[email protected]>
Signed-off-by: Artem Zatsarynnyi <[email protected]>
|
Pull Request images published ✨ Editor amd64: quay.io/che-incubator-pull-requests/che-code:pr-616-amd64 |
Signed-off-by: Artem Zatsarynnyi <[email protected]>
azatsarynnyy
changed the title
next tag on commits to main branchnext tag on commits to main branch and running in UBI9
|
Pull Request images published ✨ Editor amd64: quay.io/che-incubator-pull-requests/che-code:pr-616-amd64 |
|
Pull Request images published ✨ Editor amd64: quay.io/che-incubator-pull-requests/che-code:pr-616-amd64 |
azatsarynnyy
changed the title
next tag on commits to main branch and running in UBI9next tag on commits to main branch
|
The smoke-test job should be rerun once devfile/developer-images#247 is merged. |
|
Pull Request images published ✨ Editor amd64: quay.io/che-incubator-pull-requests/che-code:pr-616-amd64 |
|
I tried to restart Smoke test for the current PR couple times - but it's still failing... |
What does this PR do?
Decreases
VSCODE_MANGLE_WORKERSto 2 from the default 4,and increases JS memory heap for Gulp build.
This should consume less memory when building,
so it should unblock publishing the
nextimage tagson the commits to the
mainbranch.What issues does this PR fix?
fixes eclipse-che/che#23693
How to test this PR?
Does this PR contain changes that override default upstream Code-OSS behavior?
git rebasewere added to the .rebase folder