-
Notifications
You must be signed in to change notification settings - Fork 8
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
CI: add GHA to build/publish Docker image #56
base: master
Are you sure you want to change the base?
Conversation
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.
Created environment and added secrets
|
||
on: | ||
push: | ||
branches: |
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 think that we should not upload docker image on push to master because we are going to upload to this branch stats from benchmark execution each day.
I see 2 options:
- push the benchmarks stats to a different branch, maybe gh-pages?
- before uploading docker we should check if anything has change apart of stats
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.
@smiasojed But what will be the pattern (files or folders) of changes? Stats will be pushed to some folder?
So we can setup paths/paths-ignore
for push
events which will lead to release of new Docker image.
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.
results/.csv results/.png
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.
So we can just ignore whole results
folder?
Resolves https://github.com/paritytech/ci_cd/issues/830
GHA introduced by this PR tests building of Docker image in PR's.
And builds/publishes Docker image to hub.docker.com when PR is merged to
master
branch.!!! BEFORE MERGE
Setup environment
master
and add there secrets DOCKERHUB_USERNAME and DOCKERHUB_PASSWORD