You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Geoffrey Corey (JIRA)" <ji...@apache.org> on 2016/04/15 03:55:26 UTC
[jira] [Commented] (INFRA-11686) Accumulo TravisCI enable/disable
branches
[ https://issues.apache.org/jira/browse/INFRA-11686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242286#comment-15242286 ]
Geoffrey Corey commented on INFRA-11686:
----------------------------------------
Right now, giving out control over travis-ci listed above does require elevated privileges in the ASF github org (write access), and yes accumulo isn't part of the github experiment.
As for limiting the branches, have you seen/tired https://docs.travis-ci.com/user/customizing-the-build/#Whitelisting-or-blacklisting-branches ?
> Accumulo TravisCI enable/disable branches
> -----------------------------------------
>
> Key: INFRA-11686
> URL: https://issues.apache.org/jira/browse/INFRA-11686
> Project: Infrastructure
> Issue Type: Task
> Components: Github
> Reporter: Christopher Tubbs
> Priority: Minor
>
> The following branches should be building commits and pull requests and should be turned on:
> gh-pages
> The following branches should NOT be building commits and pull requests and should be turned off:
> asf-site
> Related question:
> How can the PMC/committers enable, disable, abort, and re-trigger TravisCI builds themselves on branches they control? Is that disabled because it would require write access to the GitHub repo, and Accumulo is not part of the 2-way sync GitHub experiment?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)