Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ensure release artifacts are passing some basic tests like Happy Path tests before pushing chectl release binaries
See original GitHub issueIs your enhancement related to a problem? Please describe.
che-plugin-registry released image had invalid data in it. But all ‘release process’ was successful as jobs being successfully terminated.
But the resulting latest release was failing.
We should prevent to make publicly available a release if it’s not passing some basic tests.
Describe the solution you’d like
Before pushing chectl release artifacts, ensure that the tagged Che version is passing Happy Path tests. If it does not pass, we could hold the chectl release and then end-users don’t see a new version available.
Describe alternatives you’ve considered
Of course, each component could have its own checks as post-release check but a end-to-end check would ensure that something basic is still working.
Additional context
Issue Analytics
- State:
- Created 3 years ago
- Comments:15 (15 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
It’s possible to run Happy path tests and E2E Devfile tests against already released version of Eclipse Che even now by building the next Jenkins job with proper set of parameters, if chectl binary of released version is existed https://main-jenkins-csb-crwqe.apps.ocp4.prod.psi.redhat.com/job/Che/job/e2e/job/minikube/job/basic/job/eclipse-che/
@tolusha yes