Robert Muir created LUCENE-6018:
-----------------------------------
Summary: move libversions check out of precommit to another target?
Key: LUCENE-6018
URL: https://issues.apache.org/jira/browse/LUCENE-6018
Project: Lucene - Core
Issue Type: Bug
Reporter: Robert Muir
The libversions check can be especially heavy (taking minutes and downloading a
lot?). Lately, i cannot get it to finish. To run precommit checks i have to
hack build.xml and then revert it.
Can we move this from precommit to another target? A few things:
1. i dont think most commits contain changes to third party dependencies, so it
discourages precommit, which is already hard to get people to run.
2. most commits that DO contain changes to third party dependencies, the people
committing them don't run precommit before doing so. We know this from the
jenkins fails that happen.
3. really, for a "packaging" change like dependencies nightly-smoke is the one
to run to get best verification.
We should do the same for other problematic targets, I know i opened an issue
for the jtidy one... that is still unresolved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
