https://github.com/cucumber/build

Docker image used to build the Cucumber Project
https://github.com/cucumber/build

Last synced: 3 months ago
JSON representation

Docker image used to build the Cucumber Project

• Host: GitHub
• URL: https://github.com/cucumber/build
• Owner: cucumber
• License: mit
• Created: 2020-07-03T08:39:43.000Z (over 5 years ago)
• Default Branch: main
• Last Pushed: 2024-02-23T21:10:14.000Z (almost 2 years ago)
• Last Synced: 2024-04-14T04:19:07.833Z (over 1 year ago)
• Language: Shell
• Homepage:
• Size: 254 KB
• Stars: 2
• Watchers: 11
• Forks: 5
• Open Issues: 7
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

README

          
![Build](https://github.com/cucumber/build/actions/workflows/build.yaml/badge.svg)

# Cucumber Build

Docker image used to build and release projects in the Cucumber organization.

# Usage

In a cucumber project use the `cucumber/cucumber-build:TAG` image to build

and/or release. You'll find available tags at [Docker Hub](https://hub.docker.com/r/cucumber/cucumber-build/tags).

# Building the image

    make

## Processor Architecture

By default, the `make` script will build just for your local host machine's processor architecture, but you can try building for multiple platforms by specifying the PLATFORMS environment variable.

Before doing this, make sure you've started a multi-platform builder:

    docker buildx create --use

Now try running the build with multiple platforms, e.g.

    PLATFORMS=linux/arm64,linux/amd64 make

# Publishing a new version of the image

The Docker image is published to a public dockerhub repository via an [automated Continuous Deployment workflow](./.github/workflows/release.yaml) running off protected release branches.

To make a release, you'll need to be a member of the [@cucumber/build](https://github.com/orgs/cucumber/teams/build) team.

    export next_release=`changelog latest`

    git push origin main:release/v$next_release

This assumes you have updated the CHANGELOG.md with the next release, and have the [changelog] tool installed.

Make sure you have [set up a GPG key](https://docs.github.com/en/github/authenticating-to-github/signing-commits) - all commits to the `main` and `release` branches must be signed.

[changelog]: https://github.com/cucumber/changelog