Help people with producing GitHub artifacts

Question

Help people with producing GitHub artifacts

epage opened this issue 5 years ago · 8 comments

For binaries, it is common on tagged releases to upload them to github following a specific pattern to be compatible with gh-install tools, see trust

Answer 1 · 2019-07-13T15:54:36.000Z

One of the problems is we can't offer a pre-built solution because there might be various requirements (legal notification, completion files, etc). cargo-tarball is meant to help solve that problem but I've not been getting time to finish stager and cargo-tarball. In the mean time, we might want to at least give an example of how to build and upload a binary on a tagged release.

Answer 2 · 2019-07-15T13:09:51.000Z

I think @Keats' azure-pipelines.yml from over here may be good inspiration for this.

Answer 3 · 2019-07-15T13:10:09.000Z

See also this discussion.

Answer 4 · 2019-07-18T13:29:10.000Z

There are a number of other GitHub artefacts we may also want to produce. Two good examples are pushing master documentation to gh-pages and producing GitHub releases. There is some more context over at tokio-rs/tracing#191 (comment).

Answer 5 · 2019-07-18T14:10:35.000Z

I split ghp docs out into #35

Answer 6 · 2019-07-19T20:04:28.000Z

We can probably learn from https://github.com/rustwasm/wasm-bindgen/blob/master/azure-pipelines.yml + https://github.com/rustwasm/wasm-bindgen/tree/master/ci here!

Answer 7 · 2020-01-20T18:42:19.000Z

I think this is now explicitly out-of-scope. If your project wants this, it should write a job that uses the install-rust template and then upload the artifact. That said, maybe we want an examples/ directory that gives example jobs for things like this?

Answer 8 · 2020-01-20T18:47:55.000Z