Modify Qase Build and Execute Steps to Allow Non-Error Exits

(0 comments) (0 reactions) (0 assignees)Groovy (4 forks)auto 404

good first issue

Repository metrics

Handling Qase Build and Executable needs a revisit. Currently, it'll exit with error code and force an exceptional error catch
Image https://github.com/rancher/tests/blob/main/validation/Dockerfile.validation doesn't have ENTRYPOINT or CMD, with the ENTRYPOINT script below, we can do the wrap here - currently forced in the shared libraries run command, which causes to need unnecessary params for container (workspace and dir):

//entrypoint.sh
sh - c "@"

./qase-build-reporter

./reporter

Research direction: Review the current Qase build and execute steps in the Jenkins shared library. Understand how the entrypoint script and Docker container are used. Propose changes to allow non error exits without forcing error catches.
Tech stack: groovydocker
Domain: devopsci cd
Issue type: Refactor
Difficulty: 3
Estimated time: Half day
Activity status: Active
Clarity: Mostly clear
Prerequisites: GroovyJenkins PipelinesDocker
Newbie friendliness: 40