> On May 1, 2017, at 8:04 PM, suraj acharya <[email protected]> wrote:
>
> If i am to understand the system correctly, there is currently a jenkins
> job which triggers the Pre-Commit job. Is the discussion here to make that
> more permissive, or is there a check in precomit.sh I have overlooked?
precommit-admin is a job that sits in an abandoned svn tree in the
hadoop universe. It's responsible for querying JIRA and kicking off the
Jenkins jobs. I think I filed an issue in YETUS a year+ ago to pull into our
tree. Lots of projects are using that code (whether they know it or not), so
if we replace the master precommit-admin job, we need to communicate it heavily.
(On the plus side, it'd give us a chance to unify JIRA and github
access.)
> Either way, I agree that relaxing Pre-commit is a good idea. And I can
> volunteer some time to help if a jira is filed.
Relaxing precommit is going to end up with a lot of extra runs (if not
execution storms when mass changes happen) if we aren't careful here. So you
or anyone else that decides to take this up: this is not a small task.
