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

cleaning up and improving the CI/CD pipeline #1122

Merged
merged 5 commits into from
Aug 30, 2021
Merged

cleaning up and improving the CI/CD pipeline #1122

merged 5 commits into from
Aug 30, 2021

Conversation

tcurdt
Copy link
Contributor

@tcurdt tcurdt commented Aug 28, 2021

I've cleaned up the CD pipeline a little.

The docker build is now a two-step build. The label passing might need some more testing though.

The CI runs on all pushes. If the tag starts with v it's a new version - and by that definition a new release. Note: Until now the version numbers were just numbers 0.2019.413. It would be good if we could switch to the v prefix. So a new release could be for example v0.2021.001.

The tag will create a new github release, which in turn trigger all the release distribution workflows.
For now that's npm and dockerhub. It's easy to add more.

@amark
Copy link
Owner

amark commented Aug 30, 2021

@tcurdt I'm glad you're smarter than me on htis stuff! IDK no clue what is going on but excited to pull :)

Dumb Q: not every commit has a new/different version number tho, does that matter? (nor do they need to always be published)

@amark amark merged commit 0eec835 into amark:master Aug 30, 2021
@amark
Copy link
Owner

amark commented Sep 7, 2021

@hillct will you please email me the Docker Hub username & credentials? Thank you!

@hillct
Copy link
Collaborator

hillct commented Sep 8, 2021 via email

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.

3 participants