Skip to content

R2bulary

r2bulary

R2Devops platform


Hub

We name "hub" the platform of R2Devops.


Job configuration

This is the configuration settings of the job.


Job ready to use

A job is ready to use when you just have to include it into your project in order to use it. Even if a job is ready to use, it's always customizable for your specific usage.


Mono repository

All job are manage in the same repository. In comparison to multi repository where each job has his own repository and his own git project url.


DevOps


Pipeline

Set of jobs launched in the same sequence. Pipeline can be run manually, after a commit or a merge into a branch. We consider the pipeline as succeeded if all jobs in the pipeline success.


Job

A job is a script hosted in R2Devops Hub that can be included in CI/CD pipeline to do a unitary work.

  • πŸ†• The job must be considered like a "disposable treatment" and not like something persistent.
  • πŸ–‡οΈ The job is included in a stage in a pipeline. 1 job belongs to 1 stage (and 1 stage may contain several jobs 1:N)
  • πŸ”« It is triggered by an action (either a merge on branch, or a manual triggering, or a previous job success).
  • 🎁 It may produce artifacts.
  • πŸ“„ A job always produces logs.
  • βœ‹ If a job fails, it can stop the pipeline (block the run of the next stages or in case of DAG, the next jobs of the graph).
  • ⚠️ If a job fails, it can just throw a non-blocking warning.
  • πŸ“ Once the pipeline is finished, the jobs inside the pipeline are considered as finished too. The results (logs, artifacts, output) as for them are persistent.
  • βš™οΈ The job can be customized by setting up the variables.
  • 🧬 A job instance in a pipeline is unique but a "job definition" can be implemented multiple time in a pipeline as multiple jobs instances.

CI

The Continuous Integration is a coding philosophy and set of practices that drive development teams to implement small changes and check in code to version control repositories frequently. This will ensure that your application meets your criteria of quality, security, performance, after each modification of your code.


CD

Continuous Deployment starts where continuous integration ends. CD philosophy is to automate the delivery of applications to the selected infrastructure environments.


Stage

A stage is an step of the CI/CD pipeline. Each stage can contain one or several jobs.

stage CI/CD


Last update: March 16, 2022