[GRADLE-1633] Allow the build to be failed in such a way that execution does not stop Created: 23/Jun/11  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: New Feature
Reporter: Luke Daley Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Issue Links:
Related
Related to GRADLE-1632 Add convenience methods to appropriat... Resolved

 Description   

It's reasonable to want the build to continue after a task has failed, but for the end result to be failure.

The classic case is a long CI build. I don't want the build to stop at the first failure because it may have taken 20 mins to get to the point where it failed. I see that that test failed, fix, push and then 21 minutes later I find out that the very next test task was going to fail as well.

This does mean that you may get false negatives with subsequent failures stemming from the same root cause of the initial, but it's likely that developers will be able to deduce this so I don't see it as that big of an issue.

Perhaps this should be configurable on a per task level. A task can already mark itself as failed, we could add the ability for the task to indicate whether its failure should stop the build automatically. This could also be set from "out side" on each and every task which could be useful.

 Comments   
Comment by Adam Murdoch [ 06/Dec/12 ]

Is this something different to --continue?

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 12:00:30 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.