Why are happy path tests not running maven compile-time tests?

[nickboldt]

I discovered today that the dashboard-next-happy-path tests are not running the maven tests:

-DskipTests -Dskip-enforce -Dskip-validate-sources

-- https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/blue/rest/organizations/jenkins/pipelines/dashboard-next-happy-path/runs/377/nodes/41/steps/93/log/?start=0

Granted, they're being run elsewhere for nightly and release bulds...

• https://github.com/eclipse/che/blob/master/make-release.sh
• https://github.com/eclipse/che/tree/master/.github/workflows

But would it make sense to run them here too?

[benoitf]

Usually happy path test is taking a long time (build, spin up minikube, deploy che, etc), so we remove all checks of the build to test the build as soon as possible. And other jobs ensure that the build/unit tests are passing Also github action job maven build is mandatory to merge So, I don't see any issue there.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.