You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cordova.apache.org by "jcesarmobile (JIRA)" <ji...@apache.org> on 2018/12/09 21:42:00 UTC

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

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

jcesarmobile closed CB-7550.
----------------------------
    Resolution: Won't Do

Closing as we didn't get the vagrant as far as I know, but nobody else has proposed it and we have continued doing releases without it, so I don't think it's needed

> 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: cordova-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.
> And having a private registry would give us a chance to wipe content from it to republish any new rc's without having to bump version numbers.
> Implementing this private npm registry as a Vagrant VM might be a nice way to do this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@cordova.apache.org
For additional commands, e-mail: issues-help@cordova.apache.org