chore: Rename next build job. Send notification of its failure to mattermost

[mkuznyetsov]

Signed-off-by: Mykhailo Kuznietsov [email protected]

What does this PR do?

Rename CI build job to next-build.yaml (To make it similar with other next build jobs in Eclipse Che projects)
Add notification that will be sent to Eclipse MM channel

Screenshot/screencast of this PR

What issues does this PR fix or reference?

How to test this PR?

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

Happy Path Channel

HAPPY_PATH_CHANNEL=stable

[codecov]

Codecov Report

Merging #1209 (3f4da8f) into main (c299f59) will decrease coverage by 0.16%.
The diff coverage is 19.21%.

@@            Coverage Diff             @@
##             main    #1209      +/-   ##
==========================================
- Coverage   32.78%   32.61%   -0.17%     
==========================================
  Files         290      295       +5     
  Lines        9885     9994     +109     
  Branches     1457     1473      +16     
==========================================
+ Hits         3241     3260      +19     
- Misses       6641     6731      +90     
  Partials        3        3              

Impacted Files	Coverage Δ
...theia-about/src/browser/about-che-theia-dialog.tsx	0.00% <0.00%> (ø)
...credentials/src/browser/che-credentials-service.ts	0.00% <0.00%> (ø)
...entials/src/browser/credentials-frontend-module.ts	0.00% <0.00%> (ø)
...eia-credentials/src/common/credentials-protocol.ts	0.00% <0.00%> (ø)
...eia-credentials/src/node/che-credentials-server.ts	0.00% <0.00%> (ø)
...s/src/node/che-theia-credentials-backend-module.ts	0.00% <0.00%> (ø)
...rowser/src/browser/che-mini-browser-environment.ts	0.00% <0.00%> (ø)
...he-server/src/node/che-server-http-service-impl.ts	0.00% <0.00%> (ø)
...-che-server/src/node/che-server-remote-api-impl.ts	38.88% <0.00%> (ø)
...browser/contribution/exec-terminal-contribution.ts	0.00% <0.00%> (ø)
... and 20 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 042927f...3f4da8f. Read the comment docs.

[azatsarynnyy]

Nice improvement. Thanks!

[che-bot]

❌ E2E Happy path tests failed ❗

See Details

• Jenkins job

• test report

• logs and configs

• Happy path tests DevFile

• images:

name	link
che-theia	quay.io/crw_pr/che-theia:1209
che-theia-endpoint-runtime-binary	quay.io/crw_pr/che-theia-endpoint-runtime-binary:1209

Test product:

• tested with Eclipse Che on K8S (minikube v1.22.0)
• E2E test scenario
• E2E test pipeline source code

• Use comment "[crw-ci-test]" to rerun happy path E2E test.
• Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

Eclipse Che QE channel: https://mattermost.eclipse.org/eclipse/channels/eclipse-che-qe

[vitaliy-guliy]

I suppose happy-path test are failing because of eclipse-che/che#20374 is not merged yet.
To merge that PR we need to have published che-theia:next to be sure tests are passed.

[RomanNikitenko]

I suppose happy-path test are failing because of eclipse/che#20374 is not merged yet.
To merge that PR we need to have published che-theia:next to be sure tests are passed.

@vitaliy-guliy
I see that eclipse-che/che#20374 is not ready to merge.

So:

• chore(workspace-plugin): display additional confirmation before cloning a project #1203 was merged
• but adaptation for happy path tests (chore(happy-path-tests): confirm trust git repository authors when necessary che#20374) was rejected

I would say it's better to have both PRs approved first and only then merge.

[azatsarynnyy]

@mkuznyetsov please wait a bit with merging your changes while we decide internally what we'll do to make the HappyPath green again. We will let you know.

[vitaliy-guliy]

[crw-ci-test]

[che-bot]

✅ E2E Happy path tests succeed 🎉

See Details

• Jenkins job

• test report

• logs and configs

• Happy path tests DevFile

• images:

name	link
che-theia	quay.io/crw_pr/che-theia:1209
che-theia-endpoint-runtime-binary	quay.io/crw_pr/che-theia-endpoint-runtime-binary:1209

Test product:

• tested with Eclipse Che on K8S (minikube v1.22.0)
• E2E test scenario
• E2E test pipeline source code

• Use comment "[crw-ci-test]" to rerun happy path E2E test.
• Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

Eclipse Che QE channel: https://mattermost.eclipse.org/eclipse/channels/eclipse-che-qe

[azatsarynnyy]

@mkuznyetsov now, it's good to merge

[azatsarynnyy]

@mkuznyetsov FYI: Send MM message step has failed
https://github.com/eclipse-che/che-theia/runs/3495740992?check_suite_focus=true