<Closed>Bitbucket Pipelines: Runners - Early Access

[#1]

About the self-hosted runners early access program

The early access program is closed and we are in open beta. 

---

We’re excited to introduce an early access program for the Bitbucket Pipelines Runners. 

Building a CI/CD workflow that spans across your own infrastructure and Atlassian cloud is hard. Currently, this can be done by opening a port in your firewall and allowing Bitbucket to access your internal resources, we know opening up a port has its own security implication and is not ideal. Many of you have asked for a better way to access resources in your own private network. This access is usually required for running integration tests against your internal databases, accessing the secret manager, deploying to your own infrastructure, among others.

We are building self-hosted runners so that you can execute your pipeline or step in your own infrastructure. The self-hosted runner is currently in development and soon we will be looking for people to participate in a trial. The Bitbucket Pipelines Runners early access program will allow you to try an early version of the self-hosted runner prior to the official release.

The goal of this program is to allow you to test and benefit from new features in advance and provide us with some useful feedback as we continue to build Runners.

The early version of the Runner is not a full release and will not have all features.

How to participate in this program

After submitting the form, you’ll be contacted if your requirements match our program criteria and we have available spots.

Once the self-hosted runners is available, we'll contact you with instructions on how to get started with self-hosted runners.

We want your feedback

We will be asking for feedback from all participants in the early access program. This feedback will help us improve the Runners for all customers and will help us understand your needs.

We’re looking for feedback on:

• Whether the experience worked for you, including any bugs or issues

• What documentation or information you need to use the runner

• What was helpful and easy

• What was difficult or just didn’t work

Get involved

Sign up for the early access program , or follow the progress of this work.

Thanks - I’m looking forward to shaping the future of Atlassian products with you!

[Alec Keeler]

Would be useful for us as we build C/C++ using Conan and Artifactory package manager

If we can do a pipeline build internally in a runner it would have access to our internal Artifactory package server

[Deleted user]

When can we use self hosted runners? We are using bitbucket pipeline but we are looking for a self hosted alternative.

[Justin Thomas]

@[deleted] The team is working on the early access release and we hope to make it available soon. Please join the EAP to ensure you are notified when the early access is available.

[Deleted user]

Hi Justin, any idea if the EAP is available, or what are the timeframes for this?

[Justin Thomas]

@[deleted] We are still working on the EAP, we plan to make it available this week.

[Michael Cutler]

Hi @Justin Thomas I've registered for the EAP, hope to hear from you this week.  We're literally assessing leaving Bitbucket Cloud because of this one lacking feature.  It would be great to join the EAP and see if it meets our needs.

[Albert Palomer]

Will this allow us to finally integrate windows builds for c++?

[Joost Van den Cruyce]

if this feature can be combined with the PBC concept for bamboo, and the runners can be scheduled on an (autoscaling) kubernetes cluster it would be fantastic. see https://bitbucket.org/atlassian/per-build-container/src/master/

[Justin Thomas]

@Albert Palomer Unfortunately, the EAP will only support Linux. But we do plan to add Windows support to runners in the next few months.

[crypton1]

@Justin Thomas When the early access build is released, is there place for all registrations? Or is this done in different phases? 

[Justin Thomas]

@crypton1 Sorry, I am not sure I understand the question. You can register for the EAP at Sign up for the early access program. 

[crypton1]

@Justin Thomas sorry. Yes we registered. But I was wondering if this means we should definitely get a spot (when it is released). Or it’s only sent to a small group of the registrations.    

[Jason Sheedy]

Nice work guys. 

[Justin Thomas]

@crypton1 To ensure we can respond to every feedback, we are controlling the group size and expanding it slowly. I have send out another batch of invite and I hope you have got the invite.  

[Albert Palomer]

@Justin Thomas another Atlassian building system that does not support windows..... with this decissions you are kicking out a hugh amount of developers that build for that platform.... Like bitbucket pipelines.... So sad to hear this... Will have to stick with azure dev ops.

[tperlaky]

Thank you, this will be very helpful for us. @Justin Thomas how/will these Runners consume build minutes?

[Justin Thomas]

@Albert Palomer We will be adding Windows support to Runners, it's on our roadmap. The current plan is to start work on it after Runners GA.

[Justin Thomas]

@tperlaky Steps running on the self-hosted runner will not consume any build minutes.

[Lewis Chung]

@Justin Thomas Very excited for this. Would that mean we have full control over resource limits as well? We've been having trouble with the 8GB limit on the 2x size machines.

[Justin Thomas]

@Lewis Chung In the initial release the self-hosted runner will have the same resource limitation as the cloud runner. In the future, we will be relaxing the limit and allow you full control of the hardware and resources. Thanks for the feedback.

[Uri Simchoni]

What is a self-hosted runner anyway? Is it an executable I can install on a VM/container of my choosing, or a VM image that can run containers which do the actual CI job? Asking because what was initially requested was something like gitlab-runner, and judging from the resource limit comments above it looks like something else.

[Justin Thomas]

@Uri Simchoni The self-hosted runner is currently packaged as a container and similar to Bitbucket Pipelines architecture, each step is executed in a separate container. The initial release will have restrictions around the resources, but in future, we plan to remove those restrictions. Hope this answers your question.

[Sander Mol]

@Justin ThomasIs there a specific communication channel for direct communication about the Beta of the Runners? I am already running into problems at the first run:

Status: Downloaded newer image for docker-public.packages.atlassian.com/sox/atlassian>/bitbucket-pipelines-runner:latest
+ ./entrypoint.sh
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/atlassian/pipelines/runner/core/RunnerImpl has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:601)

[Martin Rakovec]

Hi @Justin Thomas

do you plan to implement a "non-containerized" version of BBT runner? We have to connect the runner to the real HW to perform tests on in. This is very challenging with containers (most likely not impossible). Currently, we are using Bamboo agents which run as a service on the host OS/machine so it is easy to connect to USB or JTAG directly.

[drlundgren]

Support for FreeBSD will also be appreciated!