Evolene CI

	Default	Latest
🐳 Docker - Continuous Delivery Reference Application
📦 npm - npm-template

Evolene CI runs a sequence of steps that build, test and in the end stores a Docker or NPM package in a registry. It is our way of standardising the build process, so that developers never have to learn anything about our continuous integration systems 😃 or having to care where built artefacts are stored, or what processes to follow. Every user of Evolene run the same steps and when we add new features, everyone gets them without having to do anything 🍾

The main principle for Evolene is everything that a developer runs on her laptop is run the same way in the CI environment. No need for setting up a build or integration test environment on an external service. The idea is that a developer does a git push when it works locally, and Evolene handles the rest.

Evolene uses Convention Over Configuration. That means that Evolene is configured by following standard naming convensions rather then per project configuration. The Slack integration helps the developers if any configuration is missing or test breaks.

Use Evolene CI with Github Actions

Add the Github Action yaml content below to a the Github Action workflow .github/workflows/main.yml, and have a KTH Organization Owner add the repository to the list of repos that have the right to read EVOLENE_RUN_COMMAND That is it 🎉! You now have access to all repositories, testing and sercurity features.

If you have 🔑 secret environment variables somewhere in your process (like tests) add them in / Settings / Secrets / Repository secrets / EVOLENE_TEST_SECRETS as key=value pairs. Read more about secrets in Evolene here, there are more customizing you can do:

• 🛠️ Common Docker and NPM
• 🐳 How to build, test and publish your Docker application
• 📦 How to build, test and publish your NPM application

name: Evolene CI

on:  
  push:
  pull_request:
    branches:
      - master
      - main
    paths-ignore:
          - '*.md'
          - '*.png'
  workflow_dispatch:

jobs:
  Evolene:
    name: Continuous Integration
    runs-on: ubuntu-20.04
    steps:
      - uses: actions/checkout@v2.3.4
      - name: Run Evolene CI pipeline steps
        shell: bash
        env:
          SLACK_CHANNELS: "#team-development"
          BUILD_INFORMATION_OUTPUT_FILE: "/config/version.js"
          EVOLENE_TEST_SECRETS: "${{secrets.EVOLENE_TEST_SECRETS}}"
        run: |
          ${{ secrets.EVOLENE_RUN_COMMAND }}

Need a good looking badge?

Add ![Continous Integration](https://github.com/KTH/YOUR-REPO_NAME/actions/workflows/main.yml/badge.svg) to your README.md 😃 and you will get a .