Combining the power of GitHub Actions with the flexibility of self hosting with DDEV Site Runner.
By now, many people are aware of the utility of “GitOps” automation platforms like GitHub Actions, BitBucket and GitLab Pipelines.
These tools are fantastic ways to quickly build out continuous investigation and testing, but they have their limitations.
The servers are ephemeral: they are destroyed as soon as your scripts are done. The sites are inaccessible, trapped on the provider's hosted infrastructure.
There is a solution: Self-hosted runners.
Self-hosted runners let you run your jobs on any server, hosted anywhere.
The benefits are significant:
1. All events run almost instantly. No webhooks or polling.
2. Runners reach out for job information, allowing them to run behind a firewall. No need to expose preview sites to the web.
3. Logs for every job are available in the GitHub interface.
4. Direct integration with GitHub’s commit status and deployment APIs. Developers see test results and deployment status and links directly to preview sites in the Pull Request interface.
5. Secrets management. Pass secrets to scripts using workflow configuration.
6. Sites can remain online after test driven, allowing manual review or debugging.
7. Developers control what commands are run using source code.
This session will give an overview of how Git runners work, with a demonstration of the DDEV Sites Runner we built for Washington State University, Vancouver.
For more information on Site Runner, see https://www.thinkdrop.net/run-cicd-preview-environments-anywhere-self-hosted-git-runners
Jon Pugh
Enterprise Drupal Consultant, Architect, & Engineer
https://drupal-govcon-2024.sessionize.com/session/693851
Jon Pugh
Enterprise Drupal Consultant, Architect, & Engineer
These tools are fantastic ways to quickly build out continuous investigation and testing, but they have their limitations.
The servers are ephemeral: they are destroyed as soon as your scripts are done. The sites are inaccessible, trapped on the provider's hosted infrastructure.
There is a solution: Self-hosted runners.
Self-hosted runners let you run your jobs on any server, hosted anywhere.
The benefits are significant:
1. All events run almost instantly. No webhooks or polling.
2. Runners reach out for job information, allowing them to run behind a firewall. No need to expose preview sites to the web.
3. Logs for every job are available in the GitHub interface.
4. Direct integration with GitHub’s commit status and deployment APIs. Developers see test results and deployment status and links directly to preview sites in the Pull Request interface.
5. Secrets management. Pass secrets to scripts using workflow configuration.
6. Sites can remain online after test driven, allowing manual review or debugging.
7. Developers control what commands are run using source code.
This session will give an overview of how Git runners work, with a demonstration of the DDEV Sites Runner we built for Washington State University, Vancouver.
For more information on Site Runner, see https://www.thinkdrop.net/run-cicd-preview-environments-anywhere-self-hosted-git-runners
Jon Pugh
Enterprise Drupal Consultant, Architect, & Engineer
https://drupal-govcon-2024.sessionize.com/session/693851
Jon Pugh
Enterprise Drupal Consultant, Architect, & Engineer