-
Notifications
You must be signed in to change notification settings - Fork 84
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.
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
GHA pipeline rewrite for ease and speed #1551
Merged
Merged
Changes from 1 commit
Commits
Show all changes
71 commits
Select commit
Hold shift + click to select a range
943ca6a
Renmove unnecessary/old workflow files
gpmayorga 9ea2c6f
Add PR common checks and wasm build(s)
gpmayorga 298c307
Modify docs buld
gpmayorga 06dc4ef
modify benchmark
gpmayorga 77948d5
Modify CI script (simpler)
gpmayorga 949dbeb
Add docker build
gpmayorga 934145d
Add prep action for common Ubuntu steps.
gpmayorga 3641a11
separate sccache gcloud action
gpmayorga 98ca8f3
fix dockertag pattern
gpmayorga c2bc2cf
delete old benchmark check
gpmayorga 79eff04
Trick the wasm publish for this branch
gpmayorga bb5713e
new benchmark pipeline
gpmayorga c6be052
additional cache options
gpmayorga 309afdb
exclude runtime integration tests from dockerfile
gpmayorga c2b8fc7
fix buildwasm
gpmayorga 53a21a0
fix docker build & fix benchmarks
gpmayorga f79e94b
remove old benchmark job
gpmayorga 97fa94e
debug benchmark cache
gpmayorga 6a4c523
fix wasm location upload
gpmayorga 12292b0
better benchmark PR
gpmayorga 9486c1e
small fixes
gpmayorga ed7ec02
fix typo on build-wasm
gpmayorga 5200f38
better Docker build and management
gpmayorga d467440
small fixes
gpmayorga 0bfbf7a
cleanup and concurrency review
gpmayorga 9fddac4
simplify docker and fix bench-check cache
gpmayorga 9ca1e9a
inject sccache in the docker image
gpmayorga 61cbe48
fix benchmark write access for PRs
gpmayorga d72014a
test gha cache for docker
gpmayorga c9264d8
remove sccache from dockerfile
gpmayorga e23b574
adjust machine size and fix quotation in Dockfile
gpmayorga 8087d93
try fix docker var quoting
gpmayorga 3b1d5b3
pin all github action versions
gpmayorga 06ec8e1
fix srtool build
gpmayorga 0271fdb
Upload srtool report from wasm build
gpmayorga ec97693
add code coverage to wasm build
gpmayorga d4512b0
Merge branch 'main' into ci-rewrite-n-cache
gpmayorga 8ed4eda
fix typo
gpmayorga b0b406c
add nix build (fully commented)
gpmayorga 64d1822
Update build-wasm.yml
gpmayorga 7868914
change build wasm docker run
gpmayorga fae3288
Move the code coverage up to see erros
gpmayorga c47131e
check if wasm builds
gpmayorga 30a8468
try and force the report generation
gpmayorga b967a3a
Merge branch 'main' into ci-rewrite-n-cache
gpmayorga 31660dd
review the PR with @wischli
gpmayorga 8a9f774
Merge remote-tracking branch 'origin/main' into ci-rewrite-n-cache
gpmayorga eed117c
Try cargo install --locked
gpmayorga d03c379
Use toolchain from toml file
gpmayorga d51ee77
small fixes
gpmayorga 31d1884
comment code coverage reports
gpmayorga 7d486b7
trigger wasm build only on tag push
gpmayorga 44012ad
Rename benchmarks job
gpmayorga 2ce5707
try and fix the docker tag logic
gpmayorga 780adbf
small fixes
gpmayorga f0f25af
more minor fixes
gpmayorga 0d414a8
fix cache warning
gpmayorga 2ce04c8
srtool has no latest tag on the repo, using 1.69
gpmayorga 3eda725
remove production environment restrictions
gpmayorga aeaaedd
Fix GITHUB_ENV and bump srtool version
gpmayorga 5a5d394
Merge remote-tracking branch 'origin/main' into ci-rewrite-n-cache
wischli 8879d86
chore: update srtool version to latest
wischli 61fcacb
fix: remove unused rust toolchain from setup
wischli 9dfdcfb
fix: toolchain version docker build
wischli 43e5d7a
fix: remove unused thread_local
wischli 5177624
Update build-wasm.yml
gpmayorga 8398d7a
Final review of CI changes
gpmayorga 13e2085
review of sanity-checks
gpmayorga 3e9b865
Final review of CI PR with @wischli
gpmayorga bfc67a5
Use Rust docker image for building the binary
gpmayorga 2fac7af
Fix review comments
gpmayorga File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not development?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought we didnt need to check dev benchmarks to save time. I know this kind of contradicts my argument of keeping benchmarks in Dev. However, in the past releases I merged Centrifuge benchmarks to Dev because there was no runtime benchmark pipeline. I think thats feasible because this way we mimic mainnet.
How about we iterate over that when we build the next feature, which will probably first only exist in Dev runtime?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this are PR checks, let's keep it minimal, this won't actually publish or set benchmarks anywhere, it's just to check that the benchmarks run
Do we really need all 3 to run?