[GRADLE-3425] Continuous build triggers a re-build when the user hasn't done changes. Changes in intermediate directories should be ignored Created: 31/Mar/16  Updated: 10/Feb/17  Resolved: 10/Feb/17

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

Type: Bug
Reporter: Lari Hotari Assignee: Unassigned
Resolution: Won't Fix Votes: 0

Issue Links:
Related
Related to GRADLE-3484 War plugin causes continuous to run c... Resolved
Known Issue Of:

 Description   

After adding feature "Continuous build detects changes that occur during build execution" in 2.11 this problem started appearing sporadically in a certain integration test on Windows. The commit message to ignore the test failure describes the problematic situation in the integration test.

The fix to the problem would be to ignore watching intermediate directories.

 Comments   
Comment by Lari Hotari [ 16/Jun/16 ]

https://discuss.gradle.org/t/war-plugin-causes-continuous-to-run-continuously/18074 has an example where the build gets in to a continuous loop. However that particular case would be solved without using "clean" in the continuous build targets.

Comment by Lari Hotari [ 22/Sep/16 ]

.gradle and build directories are now always ignored.

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:48:29 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.