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

Enable docker build and release #3

Merged
merged 2 commits into from
Mar 14, 2024
Merged

Enable docker build and release #3

merged 2 commits into from
Mar 14, 2024

Conversation

Ivaka
Copy link
Contributor

@Ivaka Ivaka commented Mar 13, 2024

No description provided.

@Ivaka Ivaka self-assigned this Mar 13, 2024
# push: true
# tags: ghcr.io/castai/gpu-metrics-exporter/gpu-metrics-exporter:${{ github.sha }}
- name: Build and push PR
if: ${{ github.event_name == 'pull_request' }}
Copy link
Contributor

Choose a reason for hiding this comment

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

I might be wrong, since I'm not very familiar with the docker build push action. But will this push an image to the registry on each pull request opened?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, each pull request would result in an image pushed to registry. This is useful when we do some changes and want to deploy that specific image to a cluster without merging to main.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think that this is useful to build at every PR change (as it triggers on each pull_request event) but don't know if we also need to push the image 🤔

Copy link
Contributor

@atanasovskib atanasovskib Mar 13, 2024

Choose a reason for hiding this comment

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

Will PRs opened by people outside of our org also run this, and push it to our registry (how does GitHub handle this for public repos)?

Also maybe we can do it as a manual action instead of running on each PR

Copy link
Contributor

Choose a reason for hiding this comment

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

it might me useful in cases when we want to test how changes in PR works on dev/prod (any other cluster) without actually merging this PR

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think that this is useful to build at every PR change (as it triggers on each pull_request event) but don't know if we also need to push the image 🤔

So should we build and discard it? As Roman mentioned, it is useful to have these images when we want to test before merging

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will PRs opened by people outside of our org also run this, and push it to our registry (how does GitHub handle this for public repos)?

Also maybe we can do it as a manual action instead of running on each PR

Good point. I think that once the repository is public we'd be able to control whether GHA are ran for PR from forks. At the moment that option is disabled in settings, I am assuming it is because it is not a public repository.

@Ivaka Ivaka merged commit 0e167c6 into main Mar 14, 2024
2 checks passed
@atanasovskib atanasovskib deleted the chore/enable-docker-build branch April 9, 2024 15:01
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.

4 participants