Webhooks & Notifications

Currently the webhook is sent afterbuild finished. is there a way to get when build started too so we can show progress bar or something on our side something like whats asked here https://discuss.circleci.com/t/build-webhook-notifications-for-starting-a-build-and-for-each-step-as-it-goes/5500 similar thread that was closed https://discuss.circleci.com/t/send-webhook-notification-on-build-start/2995 CCI-I-525

Many cloud compute providers are adding support for OIDC for supporting cross-vendor workloads and I'd love to see CircleCI join in. OIDC enables federation of credentials/identity from one provider to another. Rather than require that a user supply static credentials, OIDC allows them to exchange a short-lived credential injected by the platform with the remote service. That credential embeds information about the identity of a workload. In git, that identity information might include the organization/repo name and the branch/ref. This makes it easy to author fine grained access policies for specific repos and ensures that long-lived credentials aren't exposed to CI workloads. OIDC is supported by GitHub Actions and GitLab CI/CD: https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect https://docs.gitlab.com/ee/ci/cloud_services/

Currently the certificate verification checkbox is unchecked by default. This is only recommended during testing for security reasons so it would be helpful to either explain the security risk and/or have this box checked by default.

We would like to received webhook callbacks when jobs and workflows are cancelled. Currently nothing is returned from the job or webhook when it is cancelled and this is not ideal for our alerting and monitoring

The workflow level webhook contains "created_at" which provides some context around when the workflow started, since it's a collection of jobs. The Job API endpoint: https://circleci.com/docs/api/v2/#operation/getJobDetails provides "started_at" to determine when the job actually started. This field should also be included in the webhook payload.

Some users would like the ability to receive workflow level event notifications. CCI-I-1248

Just like the workflow event, it would be useful to have job start and stop timestamps.

Currently, CCI automagically kills a job when a new job is started on top of it. However, there is no way to trigger any custom actions when the job is killed. In some scenarios, the previous job may have triggered outside actions that also need to be killed (i.e. testing on a third party service such as Saucelabs). It would be great to have the ability to add a custom action/webhook that gets triggered after CCI kills a job. That would allow us to perform cleanup actions such as killing the running third party jobs as well. CCI-I-1047