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.

Sign up for GitHub

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

Jump to bottom

Build out GCWS #240

Closed
1 task done
Tracked by #232
chadwhitacre opened this issue Feb 15, 2024 · 3 comments
Closed
1 task done
Tracked by #232

Build out GCWS #240

chadwhitacre opened this issue Feb 15, 2024 · 3 comments

Comments

@chadwhitacre
Copy link
Member

chadwhitacre commented Feb 15, 2024 •
edited
Loading

Goal here is to have a Google Cloud Workstation with a development environment customized for self-hosted Sentry. This will make development easier and enable us to better match development and CI.

🔒 Design doc

PRs

  • PRs
@chadwhitacre chadwhitacre mentioned this issue Feb 15, 2024
Open
12 tasks
@chadwhitacre chadwhitacre changed the title build out GCWS Build out GCWS Feb 15, 2024
@chadwhitacre
Copy link
Member Author

Initial implementation complete, one more PR outstanding, @azaslavsky to close this with that.

@chadwhitacre
Copy link
Member Author

https://github.com/getsentry/sentry/tree/azaslavsky/wip-workstations is the branch with remaining WIP

@chadwhitacre
Copy link
Member Author

Had a success event with a dev needing to test something on self-hosted and using this new feature.

azaslavsky added a commit to getsentry/self-hosted that referenced this issue Apr 17, 2024
@azaslavsky
Add workstation configuration
4904dc2 
These are prebuilt docker images for spinning up a local self-hosted
image on the Google Cloud Workstation project. While primarily intended
for internal development at Sentry, in theory these can be used by
anyone with GCWS project to create a fresh workstation for developing
self-hosted via a remote VSCode connection.

Users who have GCWS properly configured will be able to use the
forthcoming `workstations ...` command in the `sentry` dev CLI to
create, manage, and destroy one-off or long-lived workstations in either
the pre-install or post-install configuration.

Note that the `sentry workstations ...` CLI has not yet landed in the
`sentry` repo - those changes are coming soon!

Issue: getsentry/team-ospo#240
@azaslavsky azaslavsky mentioned this issue Apr 17, 2024
Merged
azaslavsky added a commit to getsentry/self-hosted that referenced this issue Apr 18, 2024
@azaslavsky
Add workstation configuration (#2968)
d59c0aa 
* Add workstation configuration

These are prebuilt docker images for spinning up a local self-hosted
image on the Google Cloud Workstation project. While primarily intended
for internal development at Sentry, in theory these can be used by
anyone with GCWS project to create a fresh workstation for developing
self-hosted via a remote VSCode connection.

Users who have GCWS properly configured will be able to use the
forthcoming `workstations ...` command in the `sentry` dev CLI to
create, manage, and destroy one-off or long-lived workstations in either
the pre-install or post-install configuration.

Note that the `sentry workstations ...` CLI has not yet landed in the
`sentry` repo - those changes are coming soon!

Issue: getsentry/team-ospo#240

* Fix shfmt complaints
ngudbhav added a commit to KingsGambitLab/self-hosted-sentry that referenced this issue Apr 20, 2024
@ngudbhav @aldy505
@dependabot @hubertdeng123 @chadwhitacre @getsentry-bot @LvckyAPI @RexTim @victorelec14 @erfantkerfan @phacops @JannKleen @lynnagara @edwardgou-sentry @edgariscoding @saz @mdtro @azaslavsky
feat: Sync fork (#8)
480ee55 
* feat: provide csrf settings information for sentry config (getsentry#2762)

* feat: provide csrf settings information for sentry config

* chore: trim trailing whitespace

* build(deps): bump actions/setup-python from 4 to 5 (getsentry#2644)

Bumps [actions/setup-python](https://github.com/actions/setup-python) from 4 to 5.
- [Release notes](https://github.com/actions/setup-python/releases)
- [Commits](actions/setup-python@v4...v5)

---
updated-dependencies:
- dependency-name: actions/setup-python
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Hubert Deng <[email protected]>

* Fix groupedmessage indexing error (getsentry#2777)

* fix groupedmessage indexing error

* Check memcached backend in Django (getsentry#2778)

Bail if using old memcached backend

* release: 24.1.2

* build: Set master version to nightly

#skip-changelog

* fix: DB migration script (getsentry#2779)

* use different approach to wait for postgres server

* Tweak postgres indexing fix (getsentry#2792)

* tweak postgres indexing fix

* add exists constraint

* build(deps): bump pre-commit/action from 3.0.0 to 3.0.1 (getsentry#2788)

Bumps [pre-commit/action](https://github.com/pre-commit/action) from 3.0.0 to 3.0.1.
- [Release notes](https://github.com/pre-commit/action/releases)
- [Commits](pre-commit/action@v3.0.0...v3.0.1)

---
updated-dependencies:
- dependency-name: pre-commit/action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* Bump nginx version (getsentry#2797)

bump nginx version

* release: 24.2.0

* build: Set master version to nightly

#skip-changelog

* use rust consumers in self-hosted

* revert changes in 3067683

* chore: Use django ORM to perform sql commands (getsentry#2827)

* use django orm

* chore: provide clearer csrf url example (getsentry#2833)

* Upgrade to FSL-1.1 (getsentry#2835)

* simplify if for open-ai-suggestion (getsentry#2732)

* simplify if for open-ai-suggestion

* Add snuba rust consumers (getsentry#2831)

* add snuba rust consumers

* Enable proxy buffering in nginx (getsentry#2844)

Enable proxy buffering

Setting the proxy_buffering directive to “off” is a common mistake because it can cause performance issues and unexpected behavior in NGINX. When proxy buffering is disabled, NGINX receives a response from the proxied server and immediately sends it to the client without storing it in a buffer. This can cause problems if the response is large or if the connection between NGINX and the client is slow, because it can result in increased memory usage and potentially lead to request timeouts.

To avoid this mistake, it is recommended to always enable proxy buffering in NGINX.

* deps: bump maxmind/geoipupdate to 6.1.0 (getsentry#2859)

https://github.com/maxmind/geoipupdate/releases/tag/v6.1.0

* increase postgres max_connections above 100 connections (getsentry#2740)

* use default value and env for postgres max_connections

* Integration test improvements (getsentry#2858)

* integration test improvements

* feat(spans): Ingest spans (getsentry#2861)

* release: 24.3.0

* build: Set master version to nightly

#skip-changelog

* Remove duplicate feature flags (getsentry#2899)

* feat: run outcomes-billing consumer (getsentry#2909)

* Integration tests in python (getsentry#2892)

* integration tests in python

* Fix defunct java processes (getsentry#2914)

revert kafka healthcheck change

* Port backup tests to python (getsentry#2907)

* port backup tests to python

* feat(clickhouse): Added max_suspicious_broken_parts to the config.xml (getsentry#2853)

* feat(clickhouse): Added max_suspicious_broken_parts to the config.xml

* refactor(clickhouse): Set default max_suspicious_bronken_parts and Issue reference

---------

Co-authored-by: Hubert Deng <[email protected]>

* Write Customization tests in python (getsentry#2918)

* port everything integration test related to python

* Bump ubuntu version for tests (getsentry#2923)

* bump ubuntu version used for testing

* get rid of codecov cli dependency

* fix(spans): Adds organizations:standalone-span-ingestion flag to default config (getsentry#2936)

Adds organizations:standalone-span-ingestion flag to default config

* feat: adds group attributes consumer (getsentry#2927)

adds group attributes consumer

* Use python for e2e tests (getsentry#2953)

* bump e2e action commit sha

* release: 24.4.0

* build: Set master version to nightly

#skip-changelog

* Port last integration tests to python (getsentry#2966)

* port custom ca cert test to python

* Add example to docker compose version in problem report (getsentry#2959)

* Use docker compose exec to create additional kafka topics (getsentry#2904)

* chore(deps): bump memcached and redis to latest patch versions (getsentry#2973)

* release: 24.4.1

* build: Set master version to nightly

#skip-changelog

* Add workstation configuration (getsentry#2968)

* Add workstation configuration

These are prebuilt docker images for spinning up a local self-hosted
image on the Google Cloud Workstation project. While primarily intended
for internal development at Sentry, in theory these can be used by
anyone with GCWS project to create a fresh workstation for developing
self-hosted via a remote VSCode connection.

Users who have GCWS properly configured will be able to use the
forthcoming `workstations ...` command in the `sentry` dev CLI to
create, manage, and destroy one-off or long-lived workstations in either
the pre-install or post-install configuration.

Note that the `sentry workstations ...` CLI has not yet landed in the
`sentry` repo - those changes are coming soon!

Issue: getsentry/team-ospo#240

* Fix shfmt complaints

* Upgrade postgres to 14.11 (getsentry#2975)

chore(deps): bump postgres to latest 14 alpine version

* Bump docker compose version in CI (getsentry#2980)

* only rerun tests on v2.0.1

* change from http error to request error

* use 3 retries like before

* fix: backport changes

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: Reinaldy Rafli <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Hubert Deng <[email protected]>
Co-authored-by: Chad Whitacre <[email protected]>
Co-authored-by: getsentry-bot <[email protected]>
Co-authored-by: getsentry-bot <[email protected]>
Co-authored-by: hubertdeng123 <[email protected]>
Co-authored-by: Iven Schlenther <[email protected]>
Co-authored-by: RexTim <[email protected]>
Co-authored-by: Victor <[email protected]>
Co-authored-by: Erfan <[email protected]>
Co-authored-by: Pierre Massat <[email protected]>
Co-authored-by: Jann Kleen <[email protected]>
Co-authored-by: Lyn Nagara <[email protected]>
Co-authored-by: edwardgou-sentry <[email protected]>
Co-authored-by: Stephen Cefali <[email protected]>
Co-authored-by: Edgar Sanchez <[email protected]>
Co-authored-by: Steffen Zieger <[email protected]>
Co-authored-by: Matthew T <[email protected]>
Co-authored-by: Alex Zaslavsky <[email protected]>
ngudbhav pushed a commit to KingsGambitLab/self-hosted-sentry that referenced this issue Apr 20, 2024
@azaslavsky @ngudbhav
Add workstation configuration (getsentry#2968)
48d24dd 
* Add workstation configuration

These are prebuilt docker images for spinning up a local self-hosted
image on the Google Cloud Workstation project. While primarily intended
for internal development at Sentry, in theory these can be used by
anyone with GCWS project to create a fresh workstation for developing
self-hosted via a remote VSCode connection.

Users who have GCWS properly configured will be able to use the
forthcoming `workstations ...` command in the `sentry` dev CLI to
create, manage, and destroy one-off or long-lived workstations in either
the pre-install or post-install configuration.

Note that the `sentry workstations ...` CLI has not yet landed in the
`sentry` repo - those changes are coming soon!

Issue: getsentry/team-ospo#240

* Fix shfmt complaints
ngudbhav pushed a commit to KingsGambitLab/self-hosted-sentry that referenced this issue Apr 20, 2024
@azaslavsky @ngudbhav
Add workstation configuration (getsentry#2968)
da57b62 
* Add workstation configuration

These are prebuilt docker images for spinning up a local self-hosted
image on the Google Cloud Workstation project. While primarily intended
for internal development at Sentry, in theory these can be used by
anyone with GCWS project to create a fresh workstation for developing
self-hosted via a remote VSCode connection.

Users who have GCWS properly configured will be able to use the
forthcoming `workstations ...` command in the `sentry` dev CLI to
create, manage, and destroy one-off or long-lived workstations in either
the pre-install or post-install configuration.

Note that the `sentry workstations ...` CLI has not yet landed in the
`sentry` repo - those changes are coming soon!

Issue: getsentry/team-ospo#240

* Fix shfmt complaints
jamesbaber1 pushed a commit to Algo-Trading-Tools/sentry that referenced this issue Jun 20, 2024
@azaslavsky @jamesbaber1
Add workstation configuration (getsentry#2968)
615d29c 
* Add workstation configuration

These are prebuilt docker images for spinning up a local self-hosted
image on the Google Cloud Workstation project. While primarily intended
for internal development at Sentry, in theory these can be used by
anyone with GCWS project to create a fresh workstation for developing
self-hosted via a remote VSCode connection.

Users who have GCWS properly configured will be able to use the
forthcoming `workstations ...` command in the `sentry` dev CLI to
create, manage, and destroy one-off or long-lived workstations in either
the pre-install or post-install configuration.

Note that the `sentry workstations ...` CLI has not yet landed in the
`sentry` repo - those changes are coming soon!

Issue: getsentry/team-ospo#240

* Fix shfmt complaints
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@chadwhitacre