[GitHub] [beam] kennknowles opened a new issue, #19118: Separate mechanism from policy: PreCommit is policy, the set of tests is a named suite

[GitBox <gi...@apache.org>]

kennknowles opened a new issue, #19118:
URL: https://github.com/apache/beam/issues/19118

   Throughout our build.gradle files we have sprinkled "preCommit" tasks. It obscures what is run sometimes.
   
   One consistent way of managing this is to have modules define test suites and to have centralized management of which suites are pre/post commit, defined entirely in the root build.gradle. We are almost doing this already, except for...
   
   The other way of doing it which is to let modules request which suites should be pre/post commits and the root build.gradle is expected to call those tasks.
   
   It isn't really clear what the intent of our tasks are right now, to me anyhow. I think they've organically grown and could now be put in order a bit.
   
   Imported from Jira [BEAM-5847](https://issues.apache.org/jira/browse/BEAM-5847). Original Jira may contain additional context.
   Reported by: kenn.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org