Skip to content
Contribute to GitLab
Sign in / Register
CI / CD
CI / CD
Create a new issue
Last edited by
Jun 11, 2018
OAI Software Alliance Workflow
The OAI workflow is described in the following picture:
A ticket is created by a contributor following the
. The Technical Committee accepts it as a fixable issue.
The Technical Committee assesses if a dedicated branch should be created.
A dedicated branch is created following the
The developer/contributor works on implementing a solution to the ticket.
Once the developer is fine with the solution, he/she
merge in his/her working branch the latest
If the development is long (like for a feature branch), he/she should merge regularly from the
branch to ease the pain.
If there are merge conflicts, the developer/contributor can ask integrators/technical committee for help.
The developer pushes the working branch onto the centralized repository.
The developer proposes a merge-request/pull-request following the
By opening a MR/PR, the OAI Continuous Integration is triggered automatically.
OAI CI job will run on the proposed merge commit onto
OAI CI job will notify in the MR/PR comments the job status.
In case of
, the Technical Committee will ask the developer to fix the issue
New commits will be added to the developer's branch
MR/PR should be automatically updated and CI job retriggered.
Once the OAI CI job status is OK, the Technical Committee may perform manual inspections.
For example, if the CI job does not check for Coding Guidelines, the TC may check and ask developer to obey them.
The Technical Committee approves the MR/PR.
A merge commit is created onto the
The OAI Continuous Integration is triggered automatically on this commit.
We are doing this since we may have several pending MR/PR. CI Job runs on a real merged
commit (no more a proposed one).
OAI CI job will notify build status in the
should not occur very often.
In case of
, developer/integrator may go back onto working branch or directly in
branch (steps #10, #3, #4, #5).
Since OAI CI job was OK on the real merged
branch, the Technical Committee
Close the Ticket
Close the MR/PR
The Technical Committee
delete the branch
New Wiki Page
Tip: You can specify the full path for the new file. We will automatically create any missing directories.