[jira] [Commented] (CB-7550) define a Vagrant vm to test npm publishing

["Marcel Kinard (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CB-7550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14134126#comment-14134126 ] 

Marcel Kinard commented on CB-7550:
-----------------------------------

I did update the cadence release documentation to test the rc from the main registry before moving the "latest" tag in npm. This might be sufficient.

https://git-wip-us.apache.org/repos/asf?p=cordova-coho.git;a=commit;h=91cb46f59146473094880175c0110d301d0260ef

> define a Vagrant vm to test npm publishing
> ------------------------------------------
>
>                 Key: CB-7550
>                 URL: https://issues.apache.org/jira/browse/CB-7550
>             Project: Apache Cordova
>          Issue Type: Improvement
>          Components: Coho
>            Reporter: Marcel Kinard
>            Priority: Minor
>
> Given the "npm publish" problems during the 3.6 release, it might be helpful to have a private npm registry to which we could replicate from registry.npmjs.org and then do a test publish and a test "npm install". And do all that before publishing it to the real npm registry.
> Implementing this private npm registry as a Vagrant VM might be a nice way to do this.



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