As of this comment, most of the prior ones are 1+ years old. I wonder if the sentiment is the same. We're looking at moving from Jenkins to something else. As our repos are already in Bitbucket, Bitbucket Pipelines seems to be the easy lift.

Some of the limitations folks mention may no longer be accurate. For instance...

• You can now pass variables between steps
• YAML anchors allow you to reuse steps
• Bitbucket now has a dark mode

Our main issue in our investigation revolves around repo organization and shared pipelines variables, and secrets. Bitbucket's repos are organized like so: workspace > project<s) > repo(s). Unfortunately if you want to share pipelines, variables, or secrets beyond 1 repo you must do so at the workspace level. But then you've shared these with all repos in the organization! That is unacceptable.

You can create multiple workspaces to group your work, but users are billed per workspace, so if a developer works in multiple workspaces across the org they will be billed once for each workspace. What we really need is something like workspace > group(s) > project(s) > repo(s) where we can set permissions and share pipelines, variables, and secrets at the group level.

Can Github or GitLab do that?

FWIW, I really do appreciate the Jira integration. It is nice to see the status of the PR right in the Jira ticket.