It's now possible to run CI job on gitlab.com. Document the process. Signed-off-by: Jiaxun Yang <jiaxun.y...@flygoat.com> --- doc/develop/ci_testing.rst | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/doc/develop/ci_testing.rst b/doc/develop/ci_testing.rst index ffaacedc3d88..b616d1c807d3 100644 --- a/doc/develop/ci_testing.rst +++ b/doc/develop/ci_testing.rst @@ -46,9 +46,10 @@ resources the project has available. For Custodians, it is a matter of enabling the pipeline feature in your project repository following the standard GitLab documentation. For non-custodians, the pipeline itself is part of the tree and should be able to be used on any GitLab instance, with whatever -runners you are able to provide. While it is intended to be able to run this -pipeline on the free public instances provided at https://gitlab.com/ a problem -with our squashfs tests currently prevents this. +runners you are able to provide. To run this pipeline on the free public +instances provided at https://gitlab.com/ you will need to fork the repository, +enable the CI/CD feature [1]_ for the repository, rise pipeline timeout [2]_ to +at least 2 hours and then push your changes to the repository. To push to Gitlab without triggering a pipeline use: @@ -74,3 +75,8 @@ developing features. In that case, it can be useful as part of your own testing cycle to edit these pipelines in separate local commits to pair them down to just the jobs you're interested in. These changes must be removed prior to submission. + +References +---------- +.. [1] https://docs.gitlab.com/ee/ci/quick_start/ +.. [2] https://docs.gitlab.com/ee/ci/pipelines/settings.html#set-a-limit-for-how-long-jobs-can-run -- 2.43.0
