When there are no refs in a repository, the server does not appear to send a capabilities frame:

Internally, see PHI1165 for nine pages of me complaining about this.

exciting new wire protocol

Currently, properties on upstream build steps are driven by CustomFields. T13248 briefly discusses a bit of context.

After D20229, the rules are:

@jbrownEP Hey! Was this implemented yet? I'm interested in this feature aswell.. (being able to run hook action once per push, no matter how many commits there are in the push).

Some of this touches Drydock but I'm just kicking it off the board since this mostly turned into a Harbormaster task.

This currently appears to be mooted by T13188.

See-Also: https://circleci.com/ideas/?idea=CCI-I-430
See-Also: https://discuss.circleci.com/t/webhook-support-removed-from-documentation-still-supported/19984

I wrote a patch for this, for both new log prototype and old log viewer here some screenshots for the view. If it is look OK, I will submit it.

After D19615, callers to harbormaster.sendmessage can specify "format": "remarkup" to get "details" rendered as remarkup (including {Fxxx}) instead of plain text.

The unit test results also don't currently show on individual builds, which is a little whack?

See T13189#240682 for some planning on the Unit Test result table.

(Feature request with no support mana.)

I expect to add flags like "this doesn't block undrafting" and "this build doesn't matter" soon, and then possibly refine those. I'd consider revisiting this after those deploy, but am not excited about formalizing the idea of "only some of your tests failed so it's okay" or adding a check for each build (since this won't scale very far). The tooltip is reasonable but I'll just turn that into a note on T13088.

(Feature request with no support mana and no discussion.)

Feature request with no support mana and no discussion / unique insight.

Nothing really actionable here.

This is reasonable to build eventually, but there's currently no support mana behind it and this task doesn't have any unique context or discussion.

No support mana behind this and no unique information in the task.

This isn't an actionable task so I'm banishing it to the shadow realm.

We don't have any support mana behind this request, it's a good candidate for third-party development, and there's no unique information in this task so I'm just going to close it out.

The actual evidence about webhooks is a little spotty and it's possible that they "work" and are just undocumented and not officially supported. It's possible that CircleCI just needs a nudge to actually document/support them.

See T13188 for CircleCI 2.0. Upshot: they removed webhooks so we can no longer interact with them.

Looks like CircleCI will stop supporting the V1 API, which we use, in about 5 weeks: https://circleci.com/sunset1-0/