# Your first Gondola workflow

Use this worksheet to save your setup details and compare workflow results.
Keep the completed copy in your own records.

## Before starting the trial

- GitHub.com Actions with a Linux x64 or ARM64 workload.
- GitHub permissions to create and install a private App.
- AWS access to provision the module and store two Secrets Manager secrets.
- An existing VPC and two subnets in different Availability Zones with outbound HTTPS.
- Terraform 1.5+ or OpenTofu 1.12+, AWS CLI, and jq.
- A repository and workflow to run on Gondola.
- A budget for AWS charges, including during the trial.

Estimate costs: https://gondola.build/docs/costs#calculator
Follow setup: https://gondola.build/docs/install
Check image compatibility: https://gondola.build/docs/workflows

## Run your first build

1. Start your trial and save the private setup bundle securely.
2. Create the GitHub App, restrict the runner group to your repository, and
   store the two secrets using the guided commands.
3. Generate the Terraform configuration. Review permissions, networking,
   release references, and resource costs before applying it.
4. Run the generated Node, Go, or Docker recipe with your repository, or adapt
   an existing workflow. Check dependencies when moving from a hosted image.
5. Confirm the build completes and its EC2 instance terminates. Keep your
   existing CI available while you decide whether to move more workflows.

## Deployment details

| Detail | Your record |
| --- | --- |
| AWS region and protected infrastructure state location | |
| Module version and controller/runner image references | |
| Workflow and repository revision | |
| Runner architecture, size, capacity type, and fleet label | |
| Job result and observed instance cleanup | |
| Setup steps that needed extra work | |

Never put private keys, activation keys, entitlement tokens, Terraform state
contents, or full workflow logs in this worksheet.

| Same workload | Current runner | Gondola |
| --- | --- | --- |
| Hardware and dependencies | | |
| Cold or warm cache | | |
| Total workflow duration, including queue time | | |
| Failed attempts and retries | | |
| Billed runner time, including EC2 startup and cleanup | | |
| Monthly compute charge | | |
| Monthly software, controller, storage, and networking costs | | |
| Setup and ongoing operating effort | | |

Compare repeated runs of the same commit, including failed attempts and retries.
Optional S3 cache setup: https://gondola.build/docs/caching

## If you keep Gondola

Confirm your paid subscription and choose automatic or manual entitlement
renewal before expiry. Payment alone does not refresh running controllers.
The automatic helper and its notifications are documented here:
https://gondola.build/docs/renewal

Keep the deployment references, protected state location, and a known-good
rollback version with your operations records:
https://gondola.build/docs/operations

## If you stop

Move workflow labels back, drain active jobs, and use the documented removal
procedure. Confirm that no runner or other unwanted AWS resource remains.
Canceling the subscription does not delete AWS infrastructure.

- Remove infrastructure: https://gondola.build/docs/operations#decommission
- Manage billing separately: https://gondola.build/billing

## Get help by email

Use the troubleshooting guide and prepared support checklist. Review and
redact anything you choose to share; no runtime telemetry is required.

- Troubleshooting: https://gondola.build/docs/troubleshooting#find-next-step
- Support and response hours: https://gondola.build/contact
- Email: support@gondola.build
