Go to file
2021-11-24 18:45:59 +03:00
.github Initial actions (#1) 2021-11-23 14:15:21 +03:00
packages fix deploy repository name (#7) 2021-11-24 18:45:59 +03:00
.eslintignore Initial actions (#1) 2021-11-23 14:15:21 +03:00
.eslintrc.json Initial actions (#1) 2021-11-23 14:15:21 +03:00
.gitignore Initial actions (#1) 2021-11-23 14:15:21 +03:00
.prettierrc.js Initial actions (#1) 2021-11-23 14:15:21 +03:00
jest.config.js Initial actions (#1) 2021-11-23 14:15:21 +03:00
LICENSE Let's make it opensource 2021-11-24 15:25:01 +03:00
package.json fix deploy repository name (#7) 2021-11-24 18:45:59 +03:00
README.md Initial actions (#1) 2021-11-23 14:15:21 +03:00
tsconfig.json Initial actions (#1) 2021-11-23 14:15:21 +03:00
yarn.lock Bump @types/jest from 26.0.24 to 27.0.3 (#3) 2021-11-24 16:19:20 +03:00

build-actions

Centralized repository for all GitHub Actions used in our CI/CD pipelines

Example of use

An example of using actions in your repository. Create a github action file ./github/build.yml with the following content:

name: Deploy Docker Image

on:
  push:
    branches:
      - 'master'

jobs:
  build-and-deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v2
      - uses: rbkmoney/build-actions/packages/jdk-build@v1.0.0
      - uses: rbkmoney/build-actions/packages/deploy-docker@v1.0.0
        with:
          registry-username: ${{secrets.DOCKER_HUB_USERNAME}}
          registry-password: ${{secrets.DOCKER_HUB_ACCESS_TOKEN}}

This is how we get the project build and the docker image deploy.

Complex actions

You can create actions by writing custom code that interacts with your repository in any way you'd like.

Types of actions

You can build Docker container and JavaScript actions. Actions require a metadata file to define the inputs, outputs and main entrypoint for your action. The metadata filename must be either action.yml or action.yaml

An example of creating custom action dotenv using JavaScript