Hey #DevOps#SysAdmin folks, if one already has an on-prem self-hosted #BitBucket instance, what would be the simplest, sanest on-prem / self-hostable CI/CD system to deploy along with it? :blobcateyes:
Asking for a friend. The friend is me. :blobcatcoffee:
Yes, I know of GitLab, Gitea, and so on — I am stuck with BitBucket on this one, so I am asking specifically about ways to get a CI/CD pipeline thingamabob working with the BitBucket instance I have.
@rysiek I haven't heard good things about it but it would seem like a natural choice for BitBucket. I have no experience with it so proceed with caution :)
The bitbucket plugin allows you to scan a Bitbucket project and dynamically create a job for each repository.
There is Jenkins DSL for sending status notifications to Bitbucket Pull Requests. You can also create tasks/comments on the PR for errors/warnings the build found.
Rather than write a build script using Jenkins DSL lots of people construct bash scripts. Jenkins DSL is highly portable, the bash scripts aren't.
You can also find a plugin to do anything and Jenkins doesn't have an opinion. So lots of people build insane workflows and then blame Jenkins when it breaks or takes ages or is inconsistent.
To solve this most other CI's are either far more restrictive and opinionated or simple bash script runners.
Add comment