Jesper Eskilson

It seems like this could be accomplished by rerunning bec without the `-e` option afterwards.

What exactly does "machine parseable" mean in this context? What information would you like to be able to get from the parseable output, apart from "success/failure"?

Console output: ``` ===> Testing prop_api:prop_api() Workzone plugin is not supported. Corresponding tests will not be run. Hook 'com.nerdwin15.stash-stash-webhook-jenkins:jenkinsPostReceiveHook' is not available and will not be tested. Hook 'de.aeffle.stash.plugin.stash-http-get-post-receive-hook:http-get-post-receive-hook' is...

Ah, yes this might well be duplicate of #468.

Also, if I try to run without `--use_beams`, I get a truckload of missing includes, which seems like a bug to me. Should I report it?

`**/opsgenie.*` is a filelib wildcard, not a regexp. But a module list works for me.

Do you have a branch for me to test?

As far as I can tell it is a real bug because two things: 1. The [documentation](https://develop.sentry.dev/sdk/overview/#parsing-the-dsn) says the endpoint is `'{BASE_URI}/api/{PROJECT_ID}/{ENDPOINT}/'` 2. The URL used in the code (`{BASE_URI}/api/store/`)...

My best guess is that the restapi had a fallback to lookup the project in the payload if the URL was `/api/store/`, but that fallback was at some point removed.

I have disabled the workaround in our local fork, so this is not a critical issue at the moment.