From df6844e364523410c1d7e9748a66dcd9deddf203 Mon Sep 17 00:00:00 2001 From: curben Date: Thu, 25 Oct 2018 14:03:04 +1030 Subject: [PATCH] Add 'How to check validity of GitLab CI config' post --- source/_posts/validity-gitlab-ci-config.md | 24 ++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 source/_posts/validity-gitlab-ci-config.md diff --git a/source/_posts/validity-gitlab-ci-config.md b/source/_posts/validity-gitlab-ci-config.md new file mode 100644 index 0000000..d35a23d --- /dev/null +++ b/source/_posts/validity-gitlab-ci-config.md @@ -0,0 +1,24 @@ +--- +title: How to check validity of GitLab CI config +date: 2018-10-25 00:00:00 +tags: +--- +It can be frustrating after you push the changes you made to `.gitlab-ci.yml`, only to discover it's invalid on gitlab.com. Here's how to verify/lint the config. + + + +Login to GitLab.com and navigate to any of your repo or project. It must be under your account. If you don't have one, simply create a new project or fork one. + +Simply add `/-/ci/lint` to the end of your repo link and navigate to that link. + +For example, + +``` +https://gitlab.com/curben/blog/-/ci/lint +``` + +This is what it looks like, + +{% cloudinary 20181025/lint.png %} + +Simply paste the content of your `.gitlab-ci.yml` and 'Validate'. \ No newline at end of file