[
https://issues.apache.org/jira/browse/HCATALOG-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471963#comment-13471963
]
Travis Crawford commented on HCATALOG-524:
------------------------------------------
Hey [~ashutoshc] I assigned this to you because you have permissions to edit
our CI job. Feel free to send me the review for the test command, or ask any
questions related to setting up Jenkins. I'm happy to help, I just don't have
permissions.
> Checkin HCatalog jenkins build command
> --------------------------------------
>
> Key: HCATALOG-524
> URL: https://issues.apache.org/jira/browse/HCATALOG-524
> Project: HCatalog
> Issue Type: Improvement
> Reporter: Travis Crawford
> Assignee: Ashutosh Chauhan
>
> HCatalog has a [jenkins
> job|https://builds.apache.org/job/Hcatalog-trunk-build/] setup to run tests
> against our trunk to ensure the source tree is in working order.
> Jenkins can trigger a number of other useful actions, such as publishing
> snapshot jars to Maven so other projects can use the jars. When setting this
> up a typo was discovered in the snapshot string and publishing failed.
> Config files are critically important to a production system, and should be
> treated with the same processes as source files. For that reason we should
> checkin a script at
> https://svn.apache.org/repos/asf/incubator/hcatalog/trunk/build-support/scripts/
> that contains the full build command, and CI should be configured to simply
> run the checked-in script.
> In addition to getting peer review on changes that would hopefully catch
> typos like this, it also lets everyone know the canonical test invocation so
> they can test with the same command locally.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
