![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
coverity |
|
Created:
|
15/Nov/13 12:26 PM
|
|
Description:
|
We use the "Build Flow Plugin" in combination with the "Conditional build plugin" to orchestrate our dependencies. The build flows are triggered by post-release hooks from GitLab. When the build flow triggers a "sub job" we only execute its build steps if the git commit tag changed or the last build was unsuccessful. Otherwise the build just successfully finishes while nothing was done. (All build steps are skipped)
One build step executes cov-build, cov-analysis and cov-commit. Now if we do not execute these steps because it is not neccessary, the plugin tells that the snapshot IDs did not match and fails the build. (Because neither analysis nor commit were done.)
It would be great to have an option to NOT let the build fail if no recent commit was found. Or anything else to achieve a successful build when no analysis/commit had taken place.
WORKAROUND: We added another conditional step which executes in the opposite case. That one just commits the last result again. But this is not beautiful at all, as it floods the Coverity database with snapshots which are not needed.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Sebastian Stickel
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.
