So I'm not familiar with npm publishing - in the Maven land, the creds for publishing are stored in ~/.m2/settings.xml, and our build slave puppet/ansible stuff populates that. If there's something similar for npm, and we can get an ASF "build user" account to publish with, we can add that for npm as well.
A. On Wed, Nov 26, 2014 at 4:41 PM, Steven Gill <[email protected]> wrote: > Okay. Thanks for the info! Let me know if I can help in any way. Should I > create an issue for getting role accounts to work with npm? > > I will also continue investigating if I can figure out a different solution > to publish to npm via jenkins. > > On Wed, Nov 26, 2014 at 11:29 AM, David Nalley <[email protected]> wrote: > > > On Wed, Nov 26, 2014 at 2:04 PM, Steven Gill <[email protected]> > > wrote: > > > Thanks for responding David! > > > > > > Just to clarify, we don't consider nightlys releases. They are just > > > snapshots and are published under the nightly tag to npm. You need to > be > > > explicit if you want to download it. It is only meant for testing. `npm > > > install cordova@nightly`. > > > > > > > Ahh, that's a great solution to the lack of non-release publishing to > NPM. > > > > > I have set the build to run once daily. If it does get triggered by a > > user, > > > it isn't a big deal. The version that gets published to npm under > nightly > > > has the date in it. If the script was run twice on the same day, it > would > > > just fail to publish because the version has already been published. > > > > > > Do we have any documentation on a role accounts? I'd be interested in > > > seeing if that would work for our use case. > > > > > > > I don't think that we have any documentation on this (or if we do I > > haven't seen it, I merely know of role account existence.) > > It may take us a while to figure out how to apply this to NPM, as I > > don't think we have anything currently going there. > > > > --David > > >
