zeus
zeus copied to clipboard
getsentry
WIP: A dashboard for CI
Rough plan: 1. Implement listeners for 'status' hooks from GitHub 2. When status hook includes anything related to Travis, use keys to pull data (vs push?) 3. When pushing data,...
We need to allow users to disconnect a repository, which should then unregister any hooks or keys associated with it. Disconnecting a repository will do so for all members of...
Now that we've got a semi functional stream we need to: - Implement channels on the backend - Propagate changes correctly into the UI (some endpoints are already setup to...
We can likely pass this as part of the artifact upload, since we'd want to report different style of JUnit tests to the same repo. You can see an example...
We want to be able to support public projects/repos. We will still require authentication. This means: - Default the project to state on GitHub (but persist it as the default,...
We dont want to keep them forever. Can do something like 30 days as an easy stop gap.
Our Travis provider could automatically create secure environment variables so the users don't have to do that manually: - `ZEUS_HOOK_BASE`: Currently used for artifact upload, might become unnecessary with #50...
Bumps [jinja2](https://github.com/pallets/jinja) from 2.11.1 to 3.1.4. Release notes Sourced from jinja2's releases. 3.1.4 This is the Jinja 3.1.4 security release, which fixes security issues and bugs but does not otherwise...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps [werkzeug](https://github.com/pallets/werkzeug) from 0.14.1 to 3.0.3. Release notes Sourced from werkzeug's releases. 3.0.3 This is the Werkzeug 3.0.3 security release, which fixes security issues and bugs but does not otherwise...