[
https://issues.apache.org/jira/browse/HBASE-23874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043734#comment-17043734
]
Nick Dimiduk commented on HBASE-23874:
--------------------------------------
I've updated the script defined in the job config to first check for the
presence of the precommit script in git. If it's there, it'll call out to that
script instead. If it's not, it'll continue using what's configured in the job.
Once these patches are verified and merged on all branches, I'll edit the job
config script to only call out to the script found in git.
> Move Jira-attached file precommit definition from script in Jenkins config to
> dev-support
> -----------------------------------------------------------------------------------------
>
> Key: HBASE-23874
> URL: https://issues.apache.org/jira/browse/HBASE-23874
> Project: HBase
> Issue Type: Task
> Components: build
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: HBASE-23874.0.patch, HBASE-23874.1.branch-1.3.patch,
> HBASE-23874.1.branch-1.4.patch, HBASE-23874.1.branch-1.patch,
> HBASE-23874.1.branch-2.1.patch, HBASE-23874.1.branch-2.2.patch,
> HBASE-23874.1.branch-2.patch
>
>
> Right now the precommit job that scans Jira for attachments is defined
> entirely in the Jenkins job configuration. Let's move this into git so that
> changes can be tracked.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
