It'd make releasing new versions of ExtCore significantly easier if we could build + release new versions of the nuget package directly from within the CI builds. Some initial thoughts:
We could use travis encrypt to encrypt the nuget API key needed to publish new versions of the package -- for obvious reasons the key should not be made public.
We (probably?) don't want the package to be released on every CI build. The git commit message(s) are available to the CI build through environment variables. Perhaps we'd implement something in the build script to check the commit message so project maintainers can trigger a new release via a git tag and/or including something like [ci package] in the commit message. Travis CI does something like this now -- including [ci skip] in the commit message prevents a commit from triggering a CI build.
It'd make releasing new versions of ExtCore significantly easier if we could build + release new versions of the nuget package directly from within the CI builds. Some initial thoughts:
travis encrypt
to encrypt the nuget API key needed to publish new versions of the package -- for obvious reasons the key should not be made public.[ci package]
in the commit message. Travis CI does something like this now -- including[ci skip]
in the commit message prevents a commit from triggering a CI build.