[
https://issues.apache.org/jira/browse/YETUS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated YETUS-853:
-----------------------------------
Description:
test-patch should have a mode where the exit status is only -1 when testing
patches. This would allow for the same code path to be used in something like a
Jenkinsfile. Changes would still cause the build to fail if they broke a test,
but branches would continue to get processed even if the full source tree has
issues. This promotes 'continuous improvement' of the source while still being
productive.
was:
test-patch should have a mode where the exit status is only -1 when testing
patches. This would allow for the same code path to be used in something like a
Jenkinsfile. Changes would still cause the fail to build if they broke a test,
but branches would continue to get processed even if the full source tree has
issues. This promotes 'continuous improvement' of the source while still being
productive.
> "improvement" mode
> ------------------
>
> Key: YETUS-853
> URL: https://issues.apache.org/jira/browse/YETUS-853
> Project: Yetus
> Issue Type: New Feature
> Components: Precommit
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
> Fix For: 0.10.0
>
> Attachments: YETUS-853.00.patch
>
>
> test-patch should have a mode where the exit status is only -1 when testing
> patches. This would allow for the same code path to be used in something like
> a Jenkinsfile. Changes would still cause the build to fail if they broke a
> test, but branches would continue to get processed even if the full source
> tree has issues. This promotes 'continuous improvement' of the source while
> still being productive.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
