Centralized repository for all GitHub Actions used in our CI/CD pipelines
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/[email protected]
- uses: rbkmoney/build-actions/packages/[email protected]
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.
You can create actions by writing custom code that interacts with your repository in any way you'd like.
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