Publish Dev packages on merge

Description

The CI server should publish a dev package to NPM on a merge that successfully builds and passes tests.

This will make use of the fluid-publish module that we have been using to manually create dev packages.

Environment

None

Activity

Show:

Avtar Gill September 16, 2016 at 3:07 PM
Edited

A few notes summarizing what Justin and I discussed offline:

  • An account will need to be created for the CI server

  • The CI server should be able to authenticate itself without having to reveal the credentials so being able to use environment variables or having the secrets live in a config file would be ideal

  • The account will need to be given required privileges in order to publish Infusion dev packages

  • If the CI server is compromised someone could use it to publish malicious payloads

  • If the publishing process fails it should return non-zero exit codes

Details

Assignee

Reporter

Components

Priority

Created September 16, 2016 at 12:09 PM
Updated September 16, 2016 at 5:21 PM