CI: build a test artifact #527
Conversation
TriplEight
added
A3-inprogress
B0-silent
|
@bkchr @apopiak @lovelaced done, it's published automatically on tags to s3://releases.parity.io/cumulus/x86_64-debian:stretch/ [tag name]/polkadot-collator AND /latest/polkadot-collator by default. |
|
Please raise a new issue with details on publishing the containerized version. |
DQ: Does that mean it's not published to github? |
|
@apopiak we didn't talk about publishing to GitHub yet, only testing release. |
* CI: build a test artifact * CI: try building before testing * CI: try proper bin name * CI: preempty cache to benchmark properly * CI: run build after test * CI: change target source * CI: try build before test once again * CI: chore * CI: prepopulate target cache * CI: conditional build; aws sync * CI: mock building to test publishing * CI: lacks permissions in the other job * CI: undebug
build --release --bin polkadot-collatortakes 5 minutes after a test,test --release --allgets built in ~8 minutes without the cache.So in the case of building after the test it saves a parallel/concurrent task, but certainly it doesn't make sense to run it every time on PRs, not even on every master pipeline.
I can run the build as it is, in the same job, but only when the pipeline's executed by schedule/trigger, @lovelaced WDYT?
Closes: https://github.com/paritytech/ci_cd/issues/141