Skip to content
This repository was archived by the owner on Nov 2, 2026. It is now read-only.
AndreKuraitPublic archive

About

Archived configured test scenarios for the TemporalCI proof of concept.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Archived TemporalCI test scenarios — November 2026. This repository is frozen with TemporalCI. Its GitHub webhook is disabled. The configuration files are preserved as examples; do not treat archival as cancellation of any independently running workflows or schedules.

TemporalCI-test

Configured examples for the TemporalCI proof of concept. Some scenarios contain real Kubernetes, Helm, and optional EKS lifecycle commands; the utility examples include placeholders and do not establish complete feature support.

Features Demonstrated

7 Named Pipeline Configurations (.temporalci/)

Pipeline Trigger Features Used
ci.yaml push + PR Matrix builds, service containers, DinD, conditionals, artifacts, gate, parameters, post hooks, path filtering
security.yaml push + weekly cron Scheduled triggers, parallel steps
release.yaml tag push (v*) Tag triggers, cross-compilation matrix (2×2), artifacts, parameters, gate
auto-label.yaml issue opened Placeholder for labeling; command: true does not invoke a label activity
branch-cleanup.yaml PR closed Placeholder for cleanup; command: true does not delete branches

| helm-e2e.yaml | configured events | Helm/Kubernetes integration scenario; inspect commands before use | | k8s-migration-e2e.yaml | configured events | Migration scenario with optional EKS setup/teardown |

The release configuration also contains a placeholder release-creation step. Schedule declarations alone do not establish active schedules. The capabilities below describe intended scenarios, not evidence of successful live execution.

CI Pipeline Features

  • Matrix builds — Tests run across Go 1.22 and 1.23 in parallel
  • Service containers — Redis sidecar with health check for integration tests
  • Docker-in-Docker — Builds a container image inside CI
  • Conditional steps — coverage-check only runs on PRs, docker-build only on push
  • Parameterized — COVERAGE_THRESHOLD (choice) and RUN_E2E (boolean)
  • Artifacts — Build binary and coverage reports uploaded to S3
  • Gate step — all-checks-pass aggregates all results for branch protection
  • Post hooks — always reports metrics, on_failure sends notification
  • Path filtering — CI only triggers on .go, go.mod, or .temporalci/ changes

CI Dashboard

View builds at: https://your-temporalci-host/ci/builds

  • Build list with repo/branch/status filters
  • Build detail with step timeline, inline logs, DAG visualization
  • Manual trigger UI at /ci/triggers
  • Repo overview at /ci/repos
  • Analytics at /ci/analytics

Local Development

go test -v -race ./...
go build ./...

About

Archived configured test scenarios for the TemporalCI proof of concept.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages