feat(devservices): Add option to setup sentry with new devservices to existing action

[hubertdeng123]

This adds an option to use new devservices to the setup-sentry action

[hubertdeng123]

It works!
https://github.com/getsentry/sentry/actions/runs/12774401700/job/35608444711?pr=83179

[asottile-sentry]

shouldn't we just convert the existing action to use devservices instead?

[hubertdeng123]

shouldn't we just convert the existing action to use devservices instead?

We should, but the existing action is used in snuba/relay/symbolicator for sentry integration tests. Adding this new action will allow a smoother cutover where we can ensure that the new action is working for those repos before we can go ahead and remove the existing action entirely.

Also, we can ensure that we don't completely break CI in those other repos while converting the existing action to use new devservices

[asottile-sentry]

shouldn't we just convert the existing action to use devservices instead?

We should, but the existing action is used in snuba/relay/symbolicator for sentry integration tests. Adding this new action will allow a smoother cutover where we can ensure that the new action is working for those repos before we can go ahead and remove the existing action entirely.

Also, we can ensure that we don't completely break CI in those other repos while converting the existing action to use new devservices

the separate action makes it really difficult to see what's different with the currently used action -- I remember the cron job having a bug with MATRIX_INSTANCE for instance

would it be possible to unify the two via an option and then we'd just delete the option later?

[hubertdeng123]

would it be possible to unify the two via an option and then we'd just delete the option later?

good point, can go down that path instead

[github-actions]

🚨 Warning: This pull request contains Frontend and Backend changes!

It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently.

Have questions? Please ask in the #discuss-dev-infra channel.

[asottile-sentry]

the docker ps -a is sometimes useful

[hubertdeng123]

tested this option in 4039e58, looks good to go