Skip to content

Latest commit

 

History

History
166 lines (104 loc) · 6.43 KB

HACKING.md

File metadata and controls

166 lines (104 loc) · 6.43 KB
Raw

Hacking

This document describes the technical details of hacking on Cucumber.

Monorepo

This git repository is a monorepo. It contains several libraries that Cucumber is built on, in many programming languages. The goal is to migrate all of the Cucumber codebase into this repository.

You can learn more about monorepos here:

Installing build tools

Because of the polyglot nature of the Cucumber project, a lot of different tools are required to build it. Here is how:

OSX

brew install go cmake maven gpg gpg-agent

Branching and CI

The CI build will synchronise from the monorepo to all the subrepos for the master branch.

Local Testing / Development checks

Cucumber runs with a highly coupled system of tests. Because cucumber is a mono-repo, testing these is best done in a docker container, due to needing a large amount of pre-requisites. The setting up of these often can be a tricky task, so we use Docker to help us with this.

To start with, we need to ensure we have Docker installed. How to do this is documented extensively on the official docker site HERE for most operating systems.

Once docker is installed, we then need to grab a copy of the official cucumber image. This should only need to be done once and will likely take 5-10 minutes.

$ make docker-run # This requires at least 2.5Gig of space on your directory

This will create a localised version of the Docker image used on CI to build cucumber then run through all of the associated make tasks in each of the sub-repos. This can take a while, but it saves you needing to push each individual commit up to the repo and then wait for the CI tests to finish.

Now we have a copy of the official docker image for building cucumber, it will use the local version cached on your machine so long as you keep hold of it. So future calls to run the docker-run script won't take longer than a couple of seconds. This allows us to build the cucumber image quickly and easily from now on.

One the docker container has been started you will be entered into "interactive" mode inside the docker container. This allows you to run any command inside the container.

It is important to note that as we are developing locally, the image does not contain any of the cucumber code from the cucumber repositories, it uses shared volumes. When the container starts, it mounts the local directory as a shared volume, allowing it to access files from your host OS. As such some of the state between your host OS and the docker image being run is persisted to your host OS. These could be things such as compiled code, downloaded packages and any files that have been written during the build.

Adding a new subrepo

Occasionally, a sub directory is promoted to a separate subrepo. The process for doing this is:

Create a new directory in the monorepo

For example:

mkdir -p tag-expressions/go

Add initial files

In the new directory, create the following files:

.rsync, with the following sample contents (adapt to the programming language):

../../LICENSE LICENSE
../../.templates/github/ .github/
../../.templates/go/.travis.yml .travis.yml

README.md with a build badge for the new subrepo. For example:

# Cucumber Tag Expressions for Java

[![Maven Central](https://img.shields.io/maven-central/v/io.cucumber/tag-expressions.svg?label=Maven%20Central)](https://search.maven.org/search?q=g:%22io.cucumber%22%20AND%20a:%22tag-expressions%22)

[The docs are here](https://cucumber.io/docs/cucumber/api/#tag-expressions).

Sync files

git add .
source scripts/functions.sh && rsync_files
git add .
git commit -m "New project"

Create new subrepo.

Create a new, empty subrepo at GitHub. Check the box for initialising with a README.md file - it's needed to create an initial master branch to push to.

Log into CircleCI and set up a build for the new (empty) subrepo.

Initialise the subrepo, for example:

echo "cucumber/tag-expressions-go" > tag-expressions/go/.subrepo
git add tag-expressions/go/.subrepo
git commit -m "Add cucumber/tag-expressions-go subrepo"

Push to the subrepo:

push_subrepo tag-expressions/go

Wait for CircleCI to build.

Write some code in the monorepo, and push whenever you want to sync to the subrepo.

Set up GPG and automatic deployment

The GPG key in use is cukebot@cucumber.io, which has id E60E1F911B996560FFB135DAF4CABFB5B89B8BE6.

The secret key is encrypted and added to git (scripts/codesigning.asc.enc). The secret key is decrypted to scripts/codesigning.asc during a CI build.

The secret key must be re-encrypted for each subrepo, as Travis encrypts it differently for each subrepo.

gpg --export-secret-key E60E1F911B996560FFB135DAF4CABFB5B89B8BE6 > scripts/codesigning.asc
# Replace SLUG with the name of the subrepo, for example cucumber-expressions-java
travis encrypt-file scripts/codesigning.asc scripts/codesigning.asc.enc --repo cucumber/SLUG

Copy the bold text and create a new file scripts/decrypt_signing_key.sh with:

#!/usr/bin/env bash
set -euf -o pipefail
openssl aes-256-cbc -K $encrypted_1570928b04a6_key -iv $encrypted_1570928b04a6_iv -in scripts/codesigning.asc.enc -out scripts/codesigning.asc -d

(The openssl line should be copied from travis encrypt output).

Make it executable and add to git:

chmod +x scripts/decrypt_signing_key.sh
git add scripts/codesigning.asc.enc scripts/decrypt_signing_key.sh
git commit -m "Add encrypted signing key"

Maven-specific

IMPORTANT: Make sure you escape characters with \ in the password/passphrase when running the commands below:

Add the password for Sonatype cukebot (in 1Password)

travis encrypt 'CI_SONATYPE_PASSWORD=secretvalue' --add --repo cucumber/SLUG

Add the passphrase for the GPG signing key (in 1Password)

travis encrypt 'CI_GPG_PASSPHRASE=secretvalue' --add --repo cucumber/SLUG

Docker and CI

Our CI build uses Docker. We have our own docker images defined in cucumber-build. These need to be rebuilt and published manually whenever they change.