You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@bigtop.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2016/02/03 02:28:40 UTC

[jira] [Updated] (BIGTOP-2306) Add support for specifying git repository access credentials

     [ https://issues.apache.org/jira/browse/BIGTOP-2306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell updated BIGTOP-2306:
-----------------------------------
    Attachment: BIGTOP-2306.patch

First we check if the component definition in the BOM has defined <name>_GIT_USER_NAME and <name>_GIT_ACCESS_TOKEN. Then we try a global definition in the BOM for GIT_USER_NAME and GIT_ACCESS_TOKEN. If both have been defined we will clone using the supplied credentials. 

> Add support for specifying git repository access credentials
> ------------------------------------------------------------
>
>                 Key: BIGTOP-2306
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2306
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: build
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>            Priority: Minor
>             Fix For: 1.1.0
>
>         Attachments: BIGTOP-2306.patch
>
>
> Bigtop uses grgit (Groovy git integration) to support fetching component source from git repositories. Currently we expect all software sources are public repositories but we should support use cases where access credentials are required. We can do this by plumbing the Bigtop build control file to grgit.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)