Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: publish metadata as gitlab artifact #459

Merged
merged 11 commits into from
May 2, 2023
Merged

chore: publish metadata as gitlab artifact #459

Changes from 4 commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
46528bf
chore: init
ggera Jan 26, 2023
5e31cfe
fix: rename
ggera Jan 26, 2023
677159c
chore: publish metadata as gitlab artifact
ggera Jan 27, 2023
76f365c
ci: add upload stage
ggera Jan 27, 2023
53bc2d0
Merge branch 'develop' into subwasm
trusch Feb 9, 2023
fd4d625
Merge branch 'develop' into subwasm
ntn-x2 Feb 9, 2023
64234b9
Update to new format
ntn-x2 Feb 9, 2023
b28cf74
Merge branch 'develop' of github.com:KILTprotocol/mashnet-node into s…
ggera Apr 27, 2023
24dea3c
upgrade srtool
ggera Apr 27, 2023
b4d2665
Merge branch 'subwasm' of github.com:KILTprotocol/mashnet-node into s…
ggera Apr 27, 2023
0928537
ci: add json artifacts path
ggera May 2, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions .gitlab-ci.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,7 @@
stages:
- test
- build
- upload

clippy:
# Corresponds to paritytech/ci-linux:production at the time of this PR
Expand Down Expand Up @@ -80,6 +81,7 @@ build-wasm-peregrine:
- export RUNTIME_DIR=runtimes/peregrine
- cp -r * /build
- /srtool/build build
- subwasm --json meta /out/peregrine_runtime.compact.wasm > /out/peregrine-metadata.json
- mkdir ./out
- mv /out/* ./out/
artifacts:
Expand All @@ -101,9 +103,25 @@ build-wasm-spiritnet:
- export RUNTIME_DIR=runtimes/spiritnet
- cp -r * /build
- /srtool/build build
- subwasm --json meta /out/spiritnet_runtime.wasm > /out/spiritnet-metadata.json
- mkdir ./out
- mv /out/* ./out/
artifacts:
paths:
- out/*.wasm
expire_in: 12 week

upload:
stage: upload
dependencies:
- build-wasm-spiritnet
- build-wasm-peregrine
image: amazon/aws-cli:2.9.18
script:
- aws configure set region $AWS_DEFAULT_REGION
- aws s3 cp /out/peregrine-metadata.json s3://$S3_BUCKET/peregrine/${CI_COMMIT_TAG}/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ggera as far as I know, CI_COMMIT_TAG could be empty if the job was simply triggered by a commit push. Would it make sense to have the same logic we have for Docker image tagging? Or maybe push something like <branch-commit> if a regular push and <tag> if a tag.

- aws s3 cp /out/spiritnet-metadata.json s3://$S3_BUCKET/spiritnet/${CI_COMMIT_TAG}/
only:
- master
- develop