The checks API looks great, but it seems like there is a disconnect between the all-in-one Pipeline of Jenkins and what the checks API expects to be working with. The examples in the article show elements such as linting, build, static analysis as separate and individually runnable things. In Jenkins 2.x Pipeline it feels like bundling these things together is more encouraged. While you can break things up a bit, it can become unwieldy when you get into things like multibranch building.
There's still a lot of potential for helpful usage of the API, these differences are just something that I find interesting when reading about software pipeline concepts and applications in abstract. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bb280e5a-d639-4029-8115-9379f10f37cb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
