Commit 8f3cef87 authored by Achilleas Pipinellis's avatar Achilleas Pipinellis

Merge branch '55621-gitlab-ci-yml' into 'master'

Fix typos around .gitlab-ci.yml in docs

Closes #55621

See merge request gitlab-org/gitlab-ce!23964
parents a26e37de de3dd67f
...@@ -81,7 +81,7 @@ export default { ...@@ -81,7 +81,7 @@ export default {
</p> </p>
<ul> <ul>
<li>Your repository does not have a corresponding <code>serverless.yml</code> file.</li> <li>Your repository does not have a corresponding <code>serverless.yml</code> file.</li>
<li>Your <code>gitlab-ci.yml</code> file is not properly configured.</li> <li>Your <code>.gitlab-ci.yml</code> file is not properly configured.</li>
<li> <li>
The functions listed in the <code>serverless.yml</code> file don't match the namespace The functions listed in the <code>serverless.yml</code> file don't match the namespace
of your cluster. of your cluster.
......
...@@ -254,7 +254,7 @@ To ensure our changes don't break the build and all tests still pass, we utilize ...@@ -254,7 +254,7 @@ To ensure our changes don't break the build and all tests still pass, we utilize
Continuous Integration (CI) to run these checks automatically for every push. Continuous Integration (CI) to run these checks automatically for every push.
Read through this article to understand [Continuous Integration, Continuous Delivery, and Continuous Deployment](https://about.gitlab.com/2016/08/05/continuous-integration-delivery-and-deployment-with-gitlab/), Read through this article to understand [Continuous Integration, Continuous Delivery, and Continuous Deployment](https://about.gitlab.com/2016/08/05/continuous-integration-delivery-and-deployment-with-gitlab/),
and how these methods are leveraged by GitLab. and how these methods are leveraged by GitLab.
From the [last tutorial](https://ryanhallcs.wordpress.com/2017/03/15/devops-and-game-dev/) we already have a `gitlab-ci.yml` file set up for building our app from From the [last tutorial](https://ryanhallcs.wordpress.com/2017/03/15/devops-and-game-dev/) we already have a `.gitlab-ci.yml` file set up for building our app from
every push. We need to set up a new CI job for testing, which GitLab CI/CD will run after the build job using our generated artifacts from gulp. every push. We need to set up a new CI job for testing, which GitLab CI/CD will run after the build job using our generated artifacts from gulp.
Please read through the [documentation on CI/CD configuration](../../../ci/yaml/README.md) file to explore its contents and adjust it to your needs. Please read through the [documentation on CI/CD configuration](../../../ci/yaml/README.md) file to explore its contents and adjust it to your needs.
......
...@@ -29,7 +29,7 @@ You can either use the user interface (UI), or connect your local computer ...@@ -29,7 +29,7 @@ You can either use the user interface (UI), or connect your local computer
with GitLab [through the command line](../../../gitlab-basics/command-line-commands.md#start-working-on-your-project). with GitLab [through the command line](../../../gitlab-basics/command-line-commands.md#start-working-on-your-project).
To configure [GitLab CI/CD](../../../ci/README.md) to build, test, and deploy To configure [GitLab CI/CD](../../../ci/README.md) to build, test, and deploy
you code, add a file called [.`gitlab-ci.yml`](../../../ci/quick_start/README.md) you code, add a file called [`.gitlab-ci.yml`](../../../ci/quick_start/README.md)
to your repository's root. to your repository's root.
**From the user interface:** **From the user interface:**
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment