Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Parallelize builds across OS and architecture

Open
#755 5 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
github-actions
Domain
ci-cd

Research direction

Start by reading the comments on this issue for the full design, then inspect bakery-build-native.yml and bakery-build-pr.yml. Trace how builds currently cover OS and architecture combinations across the three product repositories; done means each combination runs as its own parallel job for version builds and pull requests.

Written by the indexing model from the issue text.

Description

cvp:0 docker tdp:4

Problem

One build-test job builds every OS and architecture for a version. As we add more operating systems, this job needs more disk space and more time.

Workbench hit this limit when we added Ubuntu 26.04. We increased the runner size as a temporary fix.

This problem will return. RHEL 10 support is planned for Workbench and other products. Each new OS adds more work to the same job.

Scope

This affects two shared workflows: bakery-build-native.yml and bakery-build-pr.yml. All three product repos use these workflows — images-connect, images-package-manager, and images-workbench — including every pull request build.

Goal

Run each OS and architecture combination as its own parallel job, instead of building all of them in one job per version.

See the comments below for the full design. Each comment covers one part.

Dominant language
Python
Stars
2
Forks
0
Avg merge
1d 21h
Merged PRs (30d)
23

Getting set up

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.

More from posit-dev/images-shared

All issues in posit-dev/images-shared

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.