Hi Shaun, We got an update that you had a meeting about this issue and it was resolved by doing two things:
1) We set the Custom URL Base in the configuration to point to the https proxy 2) We updated the .npmrc file to https. Best Regards, Nihal On Fri, Sep 18, 2015 at 9:58 AM, shaunm <[email protected]> wrote: > Hi there, as it says on the tin, our npm publish (v2.10.0) commands seem to > succeed but no artifacts appear to be stored in the repo. This pastebin > <http://pastebin.com/TCZTkgcx> shows the debug log output for a minute > of > runtime in which I ran multiple publish operations. I don't see anything in > the log that relates to a publish. tcpdump confirms that my publish command > is reaching out to the Artifactory server and not the global npm registry. > The user I'm testing the publish with has everything but Manage rights on > the repo. I've also confirmed that all my scoping is correct and working. > I'm not terribly familiar with NPM so please let me know if it sounds like > I've missed checking something. > > I guess I have two questions: > 1) Is this some limitation of the trial license? > 2) If not, what could be going on? > > > > -- > View this message in context: > http://forums.jfrog.org/Publishing-to-Pro-Trial-NPM-repo-seems-to-succeed-but-no-artifact-is-stored-tp7580472.html > Sent from the Artifactory - Users mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Artifactory-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/artifactory-users >
------------------------------------------------------------------------------
_______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
