Configuration Templates
CI/CD Templates for Projects
GitFlic provides template configurations for working with CI/CD. You can select a template when creating a new project in the Add CI/CD Pipeline Configuration section or on your project's CI/CD page, provided your project doesn't yet have a gitflic-ci.yaml
file.
Available Project Templates
This list contains basic file sets needed to configure integration or start working with a project in one of the popular programming languages. Some templates require preliminary configuration before launch.
-
GitFlic Basic Template
Use this test template to learn about CI/CD pipelines and configure your firstgitflic-ci.yaml
. For deeper exploration of GitFlic CI/CD capabilities, refer to this article -
RuStore
Continuous integration and deployment template for publishing applications to RuStore. Addsrustore-deploy.sh
andgitflic-ci.yaml
files to the repository. Learn more -
Jmix
- .NET
- Android
- Bash
- C++
- Django
- Docker
- Elixir
- Flutter
- Go
- LaTeX
- Laravel
- MatLab
- Maven
- Python
- Ruby
Example of GitFlic Basic Template
This file is a template CI/CD pipeline configuration. You can modify it as needed.
Learn more about the syntax in the documentation
image: ubuntu:latest
variables:
TEST_1_SUCCESS: "true"
TEST_2_SUCCESS: "true"
before_script:
- echo "Pre-main instruction script (in each job)"
stages:
- test
- build
- deploy
build:
stage: build
script:
- echo "Building project"
- echo "Built project" > build.txt
artifacts:
paths: build.txt
test1:
stage: test
script:
- echo "First test set"
- echo $TEST_1_SUCCESS
test2:
stage: test
script:
- echo "Second test set"
- echo $TEST_2_SUCCESS
deploy:
stage: deploy
script:
- echo $(cat build.txt)
- echo "Deploying project"
needs:
- build
rules:
- if: $TEST_1_SUCCESS == "true" && $TEST_2_SUCCESS == "true"
after_script:
- echo "Post-main instruction script (in each job)"
Automatic Translation!
This page was automatically translated. The text may contain inaccuracies