Talk to us about Actuated

JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.

- Tell us what issues you've had with CI so far

- Understand your goals for CI

- Find the right plan for your needs & budget

- Understand next steps

You can get started same day, if you decide to go ahead and pilot actuated.

Just let us know whether it's GitLab CI or GitHub - self-hosted or hosted that you're using today.

Learn more: https://docs.actuated.dev

Email *

What's your name? *

Will this be for use at work or for personal use? *

Company name *

How/where did you hear about actuated?

What are you building or running in CI? Do you use public or private repos? *

Do you use Docker in your builds? *

Yes

Do you use Kubernetes in your builds? *

Yes

Are you building multi-arch (for ARM users)? *

Yes

Other:

Are your runners fully utilised? How much money do you spend on them? How long did it take to set them up initially? How much time on managing them? *

Are your runners running more than one job? *

Yes, runners may run multiple jobs

No, there's a clean VM for every job

What could be better about GitHub Actions? *

Have you tried or do you run self-hosted runners? If so, what challenges have you faced? *

Running out of resources due to poor scheduling

Wasting money - poor utilization of hardware

Keeping packages up to date

Dirty state between builds or clashing containers/K8s clusters

Unexpected issues with mutable hosts

Docker in Docker is slow / insecure

actions-runtime-controller is too complex

Lack of visibility across the organisation

Need to secure the supply chain (SLSA)

Other:

Required

If you decided to pilot actuated for your team - what outcome would make it a success for you?

Anything else you'd like to let us know?

Clear form

Never submit passwords through Google Forms.

This content is neither created nor endorsed by Google. - Terms of Service - Privacy Policy

Does this form look suspicious? Report

Forms