This repository has been archived by the owner on Oct 5, 2023. It is now read-only.

Archival notice

This repository has been deprecated in favour of the denperidge-redpencil/ci-quickstart repository on GitHub.

Redpencil.io's CI/CD Templates

A repository for ready-to-use, but easily adaptable, quickstarts for CI/CD.

Structure/navigation:

On Woodpecker (recommended)...
- ... using Ember, I want to...
  - ... run tests
  - ... build dry run
  - ... push the latest build
  - ... push the tagged build
- ... building a Dockerised service, I want to...
  - ... build and push
  - ... build and push (tagged)
  - ... dry run
- ... for a Python project, I want to ...
  - ... publish a package to pypi
  - ... run my project & commit the changes
On Drone...
- ... using Ember, I want to...
  - ... run tests
  - ... build dry run
  - ... push the latest build
  - ... push the tagged build
- ... building a Dockerised service, I want to...
  - ... build and push
  - ... build and push (tagged)
  - ... dry run

Discussions

Navigation order

While seemingly random, there is a logic behind it!

Folder structure

The structure is as follows: {platform}/{language/toolkit}/{action}
An example would be {woodpecker,drone}/{ember,service}/{test,build}.yml.

Woodpecker above Drone

Due to a slow shift towards the open source Woodpecker as opposed to the proprietary Drone, Woodpecker has been moved upwards in the navigation

Actions are not alphabetically ordered

The navigation is ordered as to what would commonly happen first. Testing is put above building, building above releasing, etc.

Drone actions all navigate towards one file

Drone does not natively support splitting pipelines into different files. So the navigation all goes to one file. Sorry about that.