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

Include ink_linting folder in releases + Test publish/install in CI #463

Merged
merged 11 commits into from
Mar 15, 2022

Conversation

cmichi
Copy link
Collaborator

@cmichi cmichi commented Mar 15, 2022

I'm super unhappy about the _Cargo.toml solution, but can't think of anything better right now.

Note that we also use this hack for the crates in templates/.

@cmichi cmichi marked this pull request as ready for review March 15, 2022 04:43
@cmichi cmichi requested review from a team, Robbepop, ascjones and HCastano as code owners March 15, 2022 04:43
@cmichi cmichi changed the title Include ink_linting folder in releases Include ink_linting folder in releases + Test publish/install in CI Mar 15, 2022
before_script:
# Set up a local registry.
- mkdir -p ./estuary/crates/ ./estuary/indices/
- estuary --base-url=http://0.0.0.0:7878 --crate-dir ./estuary/crates/ --index-dir ./estuary/indices &
Copy link
Collaborator

Choose a reason for hiding this comment

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

So is estuary already part of docker image or installed somewhere else?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I added it this morning in paritytech/scripts#396 and ran the Docker build manually, so it's part of the image.

@cmichi cmichi merged commit 63b870d into master Mar 15, 2022
@cmichi cmichi deleted the cmichi-include-ink_linting-in-releases branch March 15, 2022 10:12
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.

2 participants