Skip to content

Release 22.4.0 #1421

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

Closed
5 tasks done
chadwhitacre opened this issue Apr 15, 2022 · 11 comments
Closed
5 tasks done

Release 22.4.0 #1421

chadwhitacre opened this issue Apr 15, 2022 · 11 comments

Comments

@chadwhitacre
Copy link
Member

chadwhitacre commented Apr 15, 2022

22.3.0 | 22.4.0 | 22.5.0

@chadwhitacre chadwhitacre mentioned this issue Apr 15, 2022
5 tasks
@chadwhitacre
Copy link
Member Author

relay snuba sentry accepted

@chadwhitacre chadwhitacre mentioned this issue Apr 15, 2022
6 tasks
@chadwhitacre
Copy link
Member Author

expecting self-hosted and sentry-docs to kick off in ~10 minutes

@chadwhitacre
Copy link
Member Author

relay ongoing, no visibility

@chadwhitacre
Copy link
Member Author

Issue with Relay: getsentry/publish#1010 (comment)

Reminiscent of #1193 (comment) 🤔

@chadwhitacre
Copy link
Member Author

self-hosted and sentry-docs are prepped, holding off on accepting until relay is done

@chadwhitacre
Copy link
Member Author

Alright what's going on, second relay run is dead in the water after an hour, still at 5 uploads.

@chadwhitacre
Copy link
Member Author

relay done, down in the muck on self-hosted

@chadwhitacre
Copy link
Member Author

Kind of a mess.

The self-hosted release is blocked on flaky CI.

My thought was to start debugging locally to see if I could find a quick fix for the CI failure ... but I have a new M1 laptop and self-hosted doesn't run on it.

Best bet at this point still seems to be to fix the web CI flake and restart the release from the beginning (re-run prepare).

Could also disable docker-compose v1 checks in CI, i.e., drop Docker Compse v1 support for self-hosted. That is not a great option because I'm sure people are still using it and we will hear about it. This would still require a restart from prepare (since we would need to disable the checks in code and re-branch).

@chadwhitacre
Copy link
Member Author

So then the question is can I fix the web flake without a local dev environment? I guess it is a longer cycle but I can debug via CI.

@chadwhitacre
Copy link
Member Author

I went down the rabbit hole on #1415, afaict the CI failures in self-hosted under Docker Compose v1 are due to no change we introduced in any component we control (self-hosted, sentry, etc.). Best guess atm is that something changed in the GitHub Actions environment (hard for me to test because self-hosted doesn't run on M1).

My plan is to temporarily(?) turn off the Docker Compose v1 CI checks, and restart the self-hosted release with a new release branch.

@chadwhitacre
Copy link
Member Author

I added a note about Docker Compose v1 to the release notes. Case closed.

@github-actions github-actions bot locked and limited conversation to collaborators May 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant