mynewt-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Collins (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (MYNEWT-805) Better support for private repos
Date Thu, 26 Oct 2017 19:36:00 GMT

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

Christopher Collins resolved MYNEWT-805.
----------------------------------------
    Resolution: Fixed

> Better support for private repos
> --------------------------------
>
>                 Key: MYNEWT-805
>                 URL: https://issues.apache.org/jira/browse/MYNEWT-805
>             Project: Mynewt
>          Issue Type: Improvement
>      Security Level: Public(Viewable by anyone) 
>          Components: Newt
>            Reporter: Todd Mitton
>            Assignee: Todd Mitton
>            Priority: Minor
>
> A password or personal access token must be specified in project.yml for `newt install`
to access a private repo. This makes it hard to use private repos in automated environments
because it would require checking in the clear text password/token.
> We should add support for getting the password/token from an env variables.  CI systems
like jenkins, travis, etc. securely store secrets and make them available to builds through
env variables.
> Even better then env variables is to use ssh instead of https. Private repos can be accessed
via ssh, and newt can simply use the local ssh agent when accessing the private repo.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message