Skip to content

feat(ci): tag GHCR image with release version #88181

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

Merged
merged 6 commits into from
Jun 13, 2025

Conversation

aldy505
Copy link
Contributor

@aldy505 aldy505 commented Mar 28, 2025

Similar work with these PRs:

While also trying to provide a solution (or at least an alternative) for this issue: getsentry/self-hosted#3593

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

Copy link
Member

@BYK BYK left a comment

Choose a reason for hiding this comment

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

This should be done in Craft.

Kind of similar to getsentry/vroom#576 (comment)

@aldy505
Copy link
Contributor Author

aldy505 commented Mar 28, 2025

@asottile-sentry do you think it's possible to publish the image (long SHA + short SHA + nightly + tagged release) as ghcr.io/getsentry/sentry instead of ghcr.io/getsentry/sentry-self-hosted. Does it has to do with how the actual getsentry repo is being built? Although I'm sure the build was done on GCR.

@asottile-sentry
Copy link
Member

asottile-sentry commented Mar 28, 2025

@asottile-sentry do you think it's possible to publish the image (long SHA + short SHA + nightly + tagged release) as ghcr.io/getsentry/sentry instead of ghcr.io/getsentry/sentry-self-hosted. Does it has to do with how the actual getsentry repo is being built? Although I'm sure the build was done on GCR.

maybe? is there a strong reason to rename it -- it'd probably be easier to just leave it as-is

also I don't think we need the nightly tag at all -- it's always the same as latest

@aldy505
Copy link
Contributor Author

aldy505 commented Mar 29, 2025

@asottile-sentry do you think it's possible to publish the image (long SHA + short SHA + nightly + tagged release) as ghcr.io/getsentry/sentry instead of ghcr.io/getsentry/sentry-self-hosted. Does it has to do with how the actual getsentry repo is being built? Although I'm sure the build was done on GCR.

maybe? is there a strong reason to rename it -- it'd probably be easier to just leave it as-is

also I don't think we need the nightly tag at all -- it's always the same as latest

If you've seen getsentry/self-hosted#3593, it'll be easier if we can just say "if you have a problem with DockerHub, prepend ghcr.io/ in front of the image names", which is being defined here https://github.com/getsentry/self-hosted/blob/ae05091f9ff55c664ef453d121fe5c89c48a4b9d/.env#L12-L16

@BYK
Copy link
Member

BYK commented Mar 31, 2025

@asottile-sentry

also I don't think we need the nightly tag at all -- it's always the same as latest

This is not correct, at least in terms of self-hosted releases. There nightly means the last build from the default branches and latest should be the latest release (as in 25.3.0 at the time of writing this).

@aldy505
Copy link
Contributor Author

aldy505 commented Mar 31, 2025

@asottile-sentry

also I don't think we need the nightly tag at all -- it's always the same as latest

This is not correct, at least in terms of self-hosted releases. There nightly means the last build from the default branches and latest should be the latest release (as in 25.3.0 at the time of writing this).

I never see anyone using the latest tag. Usually it's either nightly or the tagged version.

@BYK
Copy link
Member

BYK commented Mar 31, 2025

I never see anyone using the latest tag. Usually it's either nightly or the tagged version.

Yes but I don't think that gives you the freedom to change it willy-nilly and break people's expectations? 😅

@aldy505
Copy link
Contributor Author

aldy505 commented Apr 3, 2025

So.. what do you think? @asottile-sentry

@aldy505
Copy link
Contributor Author

aldy505 commented Apr 21, 2025

.....anything? @asottile-sentry @hubertdeng123

@getsantry getsantry bot added the Stale label Jun 6, 2025
@getsantry
Copy link
Contributor

getsantry bot commented Jun 6, 2025

This pull request has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you add the label WIP, I will leave it alone unless WIP is removed ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@getsantry getsantry bot removed the Stale label Jun 7, 2025
BYK pushed a commit to getsentry/vroom that referenced this pull request Jun 12, 2025
Similar work with these PRs:

- getsentry/relay#4532
- getsentry/symbolicator#1635
- getsentry/snuba#6997
- getsentry/sentry#88181

While also trying to provide a solution (or at least an alternative) for this issue: getsentry/self-hosted#3593


### Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.
@aldy505 aldy505 requested a review from BYK June 12, 2025 14:54
@BYK BYK added the Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests label Jun 13, 2025
@BYK BYK enabled auto-merge (squash) June 13, 2025 16:27
@BYK BYK merged commit ee8b8e9 into getsentry:master Jun 13, 2025
32 of 34 checks passed
billyvg pushed a commit that referenced this pull request Jun 18, 2025
Similar work with these PRs:

- getsentry/relay#4532
- getsentry/symbolicator#1635
- getsentry/snuba#6997

While also trying to provide a solution (or at least an alternative) for
this issue: getsentry/self-hosted#3593

### Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

---------

Co-authored-by: Burak Yigit Kaya <[email protected]>
andrewshie-sentry pushed a commit that referenced this pull request Jun 19, 2025
Similar work with these PRs:

- getsentry/relay#4532
- getsentry/symbolicator#1635
- getsentry/snuba#6997

While also trying to provide a solution (or at least an alternative) for
this issue: getsentry/self-hosted#3593

### Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated
in the State of Delaware in 2015 as Functional Software, Inc. and is
gonna need some rights from me in order to utilize my contributions in
this here PR. So here's the deal: I retain all rights, title and
interest in and to my contributions, and by keeping this boilerplate
intact I confirm that Sentry can use, modify, copy, and redistribute my
contributions, under Sentry's choice of terms.

---------

Co-authored-by: Burak Yigit Kaya <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Trigger: getsentry tests Once code is reviewed: apply label to PR to trigger getsentry tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants