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.

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

Merged
merged 1 commit into from
Nov 10, 2023

Conversation

mike-petrov
Copy link
Contributor

@mike-petrov mike-petrov commented Oct 20, 2023

Signed-off-by: Mikhail Petrov [email protected]

closes #85

@mike-petrov mike-petrov self-assigned this Oct 20, 2023
@mike-petrov mike-petrov force-pushed the feature/85-build_and_publish_to_neofs branch from 110183b to 612b1b4 Compare October 20, 2023 19:02
.github/workflows/neofs.yml Outdated Show resolved Hide resolved
.github/workflows/neofs.yml Outdated Show resolved Hide resolved
.github/workflows/neofs.yml Outdated Show resolved Hide resolved
@mike-petrov mike-petrov force-pushed the feature/85-build_and_publish_to_neofs branch from ac89fe6 to 6966479 Compare October 20, 2023 20:07
@mike-petrov mike-petrov force-pushed the feature/85-build_and_publish_to_neofs branch from 6966479 to 7e6c237 Compare October 22, 2023 21:19
roman-khimov
roman-khimov previously approved these changes Oct 23, 2023
Copy link
Member

@roman-khimov roman-khimov left a comment

Choose a reason for hiding this comment

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

Looks legit, @vvarg229?

steps:
- name: Set PATH_TO_FILES_DIR
run: |
echo "PATH_TO_FILES_DIR=output/neofs-spec-$(make version).pdf"
Copy link
Collaborator

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

push:
branches: [ master ]

env:
Copy link
Collaborator

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.

carpawell
carpawell previously approved these changes Oct 30, 2023
with:
NEOFS_WALLET: ${{ secrets.NEOFS_WALLET }}
NEOFS_WALLET_PASSWORD: ${{ secrets.NEOFS_WALLET_PASSWORD }}
NEOFS_NETWORK_DOMAIN: ${{ env.NEOFS_NETWORK_DOMAIN }}
Copy link
Member

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?

Copy link
Collaborator

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?

Copy link
Member

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.

Copy link
Member

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.

steps:
- name: Set PATH_TO_FILES_DIR
run: |
echo "PATH_TO_FILES_DIR=output" >> $GITHUB_ENV
Copy link
Member

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

Copy link
Collaborator

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

Copy link
Member

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.

vvarg229
vvarg229 previously approved these changes Nov 3, 2023
steps:
- name: Set PATH_TO_FILES_DIR
run: |
echo "PATH_TO_FILES_DIR=output" >> $GITHUB_ENV
Copy link
Member

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 Show resolved Hide resolved
.github/workflows/neofs.yml Outdated Show resolved Hide resolved
@roman-khimov
Copy link
Member

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).

@mike-petrov mike-petrov dismissed stale reviews from vvarg229 and carpawell via 3d2b003 November 10, 2023 13:26
@mike-petrov mike-petrov force-pushed the feature/85-build_and_publish_to_neofs branch from c05f16a to 3d2b003 Compare November 10, 2023 13:26
@mike-petrov mike-petrov force-pushed the feature/85-build_and_publish_to_neofs branch from 72a39a6 to 113b8ab Compare November 10, 2023 13:41
@roman-khimov roman-khimov merged commit 47a84d0 into master Nov 10, 2023
1 check passed
@roman-khimov roman-khimov deleted the feature/85-build_and_publish_to_neofs branch November 10, 2023 13:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Build and publish to NeoFS
4 participants