julian7 / goshipdone Goto Github PK

Let multiple, independent steps run asynchronously.

• put all steps into waitgroups, and run them in goroutines
• make dependent steps wait for artifacts using mutex locks
• propagate build cancelation on error using context

The only difference between build and archive, is that build is generating artifacts from source, and archive is generating artifacts from other artifacts.

From the goal's perspective (eg. all artifacts have to be created), it should not matter.

Currently, the only build file considered is what's provided in the API call, or .goshipdone.yml as the default.

Use a multi-tiered approach instead:

• GOSHIPDONE_CONFIG env. var
• provided file name
• .goshipdone.local.yml
• .goshipdone.yml

This way, input can be provided by a file name provided by environment, by command line, or by convention, with the ability of having an alternative to the official one.

While the project is good for shipping a release, it is not suitable for DOING the release. However, the drill is about the same:

• adjust CHANGELOG for the new release
• make the final commit announcing the release
• create tag for the release (github can do it automatically on publish)

There is a rudimendary uploader for github, but other artifact storage solutions (eg. gitlab, artifactory) should be supported as well.

publish:artifact doesn't read from default token file.