How a Jenkins Job Broke our Jenkins UI

Re:How a Jenkins Job Broke our Jenkins UI by danielheath on Thursday June 03, 2021 @10:47PM (#27389997)

Buildkite might be an option in a regulated environment.

They don't get access to your code (BYO runners, they manage pipeline config / logs / notifications). You run their (open source, easy to build yourself) agent on infrastructure you control.

It's really nicely put together.

[ Parent | on HN ]

Re:How a Jenkins Job Broke our Jenkins UI by maccard on Friday June 04, 2021 @07:18AM (#27392467)

Buildkite's problem is they only support git, unfortuantely.

[ Parent | on HN ]

Re:How a Jenkins Job Broke our Jenkins UI by danielheath on Friday June 04, 2021 @10:06PM (#27401294)

https://buildkite.com/docs/agent/v3/hooks indicates you can override the builtin git support with your own checkout system. Sucks having to write a plug-in but it should be short.

[ Parent | on HN ]

Re:How a Jenkins Job Broke our Jenkins UI by sj26 on Monday June 07, 2021 @07:26PM (#27428682)

Somebody already has, for perforce:

https://github.com/improbable-eng/perforce-buildkite-plugin

[ Parent | on HN ]

Re:How a Jenkins Job Broke our Jenkins UI by maccard on Wednesday June 09, 2021 @06:51AM (#27446450)

I've looked into this plugin before (we also use perforce). This does techincally let you build from perforce, in the same way making `p4 sync` your first build step does.

[ Parent | on HN ]