temporalio / temporalio/temporal-worker-controller

Automate execution of internal controller validation pipelines

Open
#492 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

build-release cicd
Dominant language
Go
Stars
187
Forks
70
Avg merge
4d 1h
Merged PRs (30d)
31

Description

After building a release branch test image and pushing it to dockerhub, the next step in the release process is to execute a pair of Temporal Workflows that have been wrapped in a Github Action in the private temporalio/saas-cicd repository.

We test the temporal-worker-controller images built and pushed in the previous step against an internal testing environment. There is a Github Action called oss-cicd.e2e in the temporalio/saas-cicd source code repository that has a parameterized run definition. The parameters for oss-cicd.e2e are --type and --input because all this Github Action does is call the Temporal StartWorkflowExecution API so --type corresponds to the Workflow Type (i.e. the name of the workflow to execute) and --input corresponds to the JSON-ified input parameter that is passed to StartWorkflowExecution.

The two workflows that validate the temporal-worker-controller image are:

  • PipelineWorkerControllerFaultInjectionRestarts
  • PipelineWorkerControllerUpgrade

The task for this issue is to automate the execution of these things, triggering the execution after a successful push of the release branch test image.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the GitHub Actions workflow that builds and pushes the release-branch test image, then review the oss-cicd.e2e run definition in the referenced saas-cicd repository. Use the two named workflow types and their required --type and --input parameters; done means both validations run automatically after a successful image push.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, github-actions, go
Domain
ci-cd, devops, release, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.