fact rendering - Githubissues

input-output-hk / cicero

event-driven automation for Nomad

https://handbook.cicero.ci.iog.io

41 stars 11 forks source link

fact rendering #72

Open jhbertra opened 1 year ago

jhbertra commented 1 year ago

The run page's summary at the top is missing some useful information related to the run. Notably it would be helpful to include

The commit hash that triggered the build (as a link)
The branch name (as a link)
A link to the pull request (if applicable)

jonathanknowles commented 1 year ago

I would like to second this request!

Being able to link back to the PR that triggered a build is extremely helpful for tracking builds.

dermetfan commented 1 year ago

This information is in the fact that triggered the run which is shown in the table called "Inputs" when you click on the fact ID. It's a huge JSON though so not very discoverable. As Cicero is a general if-this-then-that machine we should not directly include some very CI- and GitHub-specific information. The planned solution for this is programmable fact rendering which would display facts in some nice GitHub-specific way.

jhbertra commented 1 year ago

I am not at all impressed by this explanation. Why was our existing CI system replaced by something that is not a CI system? I don't want a general ITTT machine, I want a CI system!

dermetfan commented 1 year ago

See https://input-output-rnd.slack.com/archives/CCZSDE005/p1666615101667619?thread_ts=1666580400.126099&cid=CCZSDE005.

We had to migrate to cicero way earlier than we wanted to because packet.net shut down the datacenter that Hydra was running on. I'm therefore not surprised that the experience is far from that of a purpose-built CI system. CI is one of the things cicero should become great at but it just was not ready for prime time yet.