Gitlab-plugin: Add option to mark unstable builds as success in GitLab
i think UNSTABLE is success...
May be You can add option for this
salashnik
All 3 comments
Whether 'UNSTABLE' is success or fail really depends on the project. As I understand it, sometimes UNSTABLE can mean that the code compiled, but automated tests failed. In this case, UNSTABLE should result in a failure on the GitLab side. However, in some other cases that may not be desirable. If anything, it should be a configurable option.
dblessing
on 16 Feb 2016
If anything, it should be a configurable option.
of course!
salashnik
on 17 Feb 2016
I just tried the latest version (1.2.5) of the plugin and I have a "Passed" status in GitLab when the build in Jenkins is "Unstable". Is is the expected behavior? In my case, I would like it to be "Failed" in GitLab.
EDIT: I just found out why, my post-build action to publish the build status was before another action that turn the status into "Unstable".
sebastienbonami
on 28 Jun 2016
Related issues
omehegan
路
3Comments
crussell52
路
5Comments
ffrddrll
路
6Comments
dblessing
路
3Comments
MarcelNehring
路
5Comments
Most helpful comment
I just tried the latest version (1.2.5) of the plugin and I have a "Passed" status in GitLab when the build in Jenkins is "Unstable". Is is the expected behavior? In my case, I would like it to be "Failed" in GitLab.
EDIT: I just found out why, my post-build action to publish the build status was before another action that turn the status into "Unstable".