-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add Github Action for publish spec to NeoFS #87
Conversation
110183b
to
612b1b4
Compare
ac89fe6
to
6966479
Compare
6966479
to
7e6c237
Compare
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.
Looks legit, @vvarg229?
.github/workflows/neofs.yml
Outdated
steps: | ||
- name: Set PATH_TO_FILES_DIR | ||
run: | | ||
echo "PATH_TO_FILES_DIR=output/neofs-spec-$(make version).pdf" |
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.
echo "PATH_TO_FILES_DIR=output" >> $GITHUB_ENV
.github/workflows/neofs.yml
Outdated
push: | ||
branches: [ master ] | ||
|
||
env: |
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.
Remove the variable definitions from here - they will be set by @roman-khimov in the repository settings.
4351eb8
to
c05f16a
Compare
with: | ||
NEOFS_WALLET: ${{ secrets.NEOFS_WALLET }} | ||
NEOFS_WALLET_PASSWORD: ${{ secrets.NEOFS_WALLET_PASSWORD }} | ||
NEOFS_NETWORK_DOMAIN: ${{ env.NEOFS_NETWORK_DOMAIN }} |
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.
@vvarg229, why do we have a domain here?
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.
@vvarg229, why do we have a domain here?
How else do you identify which neofs network to use?
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.
That's about gateway IIRC.
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.
To produce a link to download/view the uploaded thing.
.github/workflows/neofs.yml
Outdated
steps: | ||
- name: Set PATH_TO_FILES_DIR | ||
run: | | ||
echo "PATH_TO_FILES_DIR=output" >> $GITHUB_ENV |
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 is it hardcoded and not an env? @vvarg229
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 is it hardcoded and not an env? @vvarg229
Yes, you can put this variable into GitHub variables from the web interface
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.
Looks like there is some inconsistency there, we have PATH_TO_FILES_DIR
in an env
, but here it's hardcoded to a particular value appropriate for make docker/pdf
.
.github/workflows/neofs.yml
Outdated
steps: | ||
- name: Set PATH_TO_FILES_DIR | ||
run: | | ||
echo "PATH_TO_FILES_DIR=output" >> $GITHUB_ENV |
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.
Looks like there is some inconsistency there, we have PATH_TO_FILES_DIR
in an env
, but here it's hardcoded to a particular value appropriate for make docker/pdf
.
I've added envs/secrets (except PATH_TO_FILES_DIR). But we need to synchronize the name of the uploaded spec with the website then (see nspcc-dev/gh-push-to-neofs#2 also). |
c05f16a
to
3d2b003
Compare
closes #85 Signed-off-by: Mikhail Petrov <[email protected]>
72a39a6
to
113b8ab
Compare
Signed-off-by: Mikhail Petrov [email protected]
closes #85