@@ -26,6 +26,7 @@ Build, test, and deploy the software you develop with [GitLab CI/CD](../ci/READM
...
@@ -26,6 +26,7 @@ Build, test, and deploy the software you develop with [GitLab CI/CD](../ci/READM
| Article title | Category | Publishing date |
| Article title | Category | Publishing date |
| :------------ | :------: | --------------: |
| :------------ | :------: | --------------: |
| [How to test and deploy Laravel/PHP applications with GitLab CI and Envoy](test_and_deploy_laravel_apps_with_gitlab_ci_and_envoy/index.md) | Tutorial | 2017-08-31 |
| [How to deploy Maven projects to Artifactory with GitLab CI/CD](artifactory_and_gitlab/index.md) | Tutorial | 2017-08-15 |
| [How to deploy Maven projects to Artifactory with GitLab CI/CD](artifactory_and_gitlab/index.md) | Tutorial | 2017-08-15 |
| [Making CI Easier with GitLab](https://about.gitlab.com/2017/07/13/making-ci-easier-with-gitlab/) | Concepts | 2017-07-13 |
| [Making CI Easier with GitLab](https://about.gitlab.com/2017/07/13/making-ci-easier-with-gitlab/) | Concepts | 2017-07-13 |
To start using Container Registry on our machine, we first need to login to the GitLab registry using our GitLab username and password.
To start using Container Registry on our machine, we first need to login to the GitLab registry using our GitLab username and password.
...
@@ -460,7 +460,7 @@ To run the above commands, we first need to have [Docker](https://docs.docker.co
...
@@ -460,7 +460,7 @@ To run the above commands, we first need to have [Docker](https://docs.docker.co
Congratulations! You just pushed the first Docker image to the GitLab registry, and if you refresh the page you should be able to see it.
Congratulations! You just pushed the first Docker image to the GitLab registry, and if you refresh the page you should be able to see it.
![container registry page with image](img/container-registry-page-with-image.png)
![container registry page with image](img/container_registry_page_with_image.png)
>**Note:**
>**Note:**
You can also [use GitLab CI](https://about.gitlab.com/2016/05/23/gitlab-container-registry/#use-with-gitlab-ci) to build and push your Docker images, rather than doing that on your machine!
You can also [use GitLab CI](https://about.gitlab.com/2016/05/23/gitlab-container-registry/#use-with-gitlab-ci) to build and push your Docker images, rather than doing that on your machine!
...
@@ -629,7 +629,7 @@ You may also want to add another job for [staging environment](https://about.git
...
@@ -629,7 +629,7 @@ You may also want to add another job for [staging environment](https://about.git
We have prepared everything we need to test and deploy our app with GitLab CI.
We have prepared everything we need to test and deploy our app with GitLab CI.
To do that, commit and push `.gitlab-ci.yml` to the `master` branch. It will trigger a pipeline, which you can watch live under your project's **Pipelines**.
To do that, commit and push `.gitlab-ci.yml` to the `master` branch. It will trigger a pipeline, which you can watch live under your project's **Pipelines**.
![pipelines page](img/pipelines-page.png)
![pipelines page](img/pipelines_page.png)
Here we see our **Test** and **Deploy** stages.
Here we see our **Test** and **Deploy** stages.
The **Test** stage has the `unit_test` build running.
The **Test** stage has the `unit_test` build running.