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

gh action CI #132

Merged
merged 6 commits into from
Sep 5, 2023
Merged

gh action CI #132

merged 6 commits into from
Sep 5, 2023

Conversation

deantchi
Copy link
Contributor

this is just a skeleton CI that build and publishes Hord to docker cloud.
we can treat the PR as a WIP until the CI tasks is complete with testing and any additional CI tasks that may be needed before a release.

@CharlieC3
Copy link
Member

@deantchi If this is still a WIP and not ready for review, can you change this to a draft?

@deantchi deantchi marked this pull request as draft July 20, 2023 19:23
@CharlieC3 CharlieC3 removed their request for review July 20, 2023 19:44
Dockerfile Outdated
@@ -0,0 +1,17 @@
FROM rust:bullseye as build
Copy link
Contributor

Choose a reason for hiding this comment

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

We already have a similar Dockerfile in dockerfiles/

Copy link
Contributor Author

Choose a reason for hiding this comment

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

we should follow the same pattern as other repos and. that is to keep the Dockerfile at the root of the project.

Copy link
Contributor

Choose a reason for hiding this comment

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

I like the idea of keeping the project root nice an clean, we will also probably end up with multiple dockerfiles (debian, alpine, etc).
The dockerfiles directory convention is also adopted in our other repos (https://github.com/hirosystems/clarinet, https://github.com/hirosystems/chainhook).

@deantchi deantchi marked this pull request as ready for review August 31, 2023 21:20
@deantchi
Copy link
Contributor Author

deantchi commented Aug 31, 2023

ready for review
recent run here

Copy link
Contributor

@lgalabru lgalabru left a comment

Choose a reason for hiding this comment

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

Looking great, thank you so much @deantchi!
Could we please rely on the existing dockerfile instead?
Thanks!

@deantchi
Copy link
Contributor Author

deantchi commented Sep 1, 2023

Looking great, thank you so much @deantchi!
Could we please rely on the existing dockerfile instead?
Thanks!

done!

Copy link
Member

@CharlieC3 CharlieC3 left a comment

Choose a reason for hiding this comment

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

LGTM! :shipit:

@lgalabru
Copy link
Contributor

lgalabru commented Sep 1, 2023

Thanks @deantchi!

Looking more closely at the build process, would it be possible to run in parallel:

  • cargo test
  • docker build

and only publish the image to docker hub if the test passed?
This simple trick would halve the CI time!

@lgalabru lgalabru merged commit 9f2192b into develop Sep 5, 2023
1 check passed
@lgalabru lgalabru deleted the devops-1262 branch September 5, 2023 17:06
@blockstack-devops
Copy link

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants