Commit e38bd445 authored by William Chia's avatar William Chia 🌴

Update links

parent eb5e3324
Pipeline #34386723 passed with stages
in 28 minutes and 40 seconds
......@@ -980,7 +980,7 @@ features:
description: "GitLab has Issue Boards, each list of an Issue Board is based on a label that exists in your issue tracker. The Issue Board will therefore match the state of your issue tracker in a user-friendly way."
screenshot_url: "images/feature_page/screenshots/05-issue-boards.png"
link_description: "Learn more about GitLab Issue Boards"
link: /features/issueboard/
link: /product/issueboard/
feature_page: true
pricing_page: true
category:
......@@ -1136,7 +1136,7 @@ features:
- title: "Service Desk"
description: "Allow external users to create issues in your GitLab instance without an account and without access to anything except their issue. Manage tickets from the GitLab interface."
link_description: "Learn more about Service Desk"
link: /features/service-desk/
link: /product/service-desk/
category:
- unknown
gitlab_core: false
......@@ -1299,7 +1299,7 @@ features:
- title: "Cycle Analytics"
description: "GitLab provides a dashboard that lets teams measure the time it takes to go from planning to monitoring. GitLab can provide this data because it has all the tools built-in: from the idea, to the CI, to code review, to deploy to production."
link_description: "Learn more about Cycle Analytics"
link: /features/cycle-analytics/
link: /product/cycle-analytics/
screenshot_url: images/feature_page/screenshots/15-cycle-analytics.png
feature_page: true
category:
......@@ -1350,7 +1350,7 @@ features:
- title: "Issue board templates"
description: "Issue boards/dashboards reflect an organizations flow for processing work items. These boards can reflect individualized workflow or follow established patterns. Templates for established patterns (such as Scrum and Kanban) can make setup of new boards easier."
link_description: "Learn more about GitLab Issue Boards"
link: /features/issueboard/
link: /product/issueboard/
category:
- issue_boards
gitlab_core: false
......@@ -1651,7 +1651,7 @@ features:
for your merge requests with the ability to preview your branch in a live
environment.
link_description: "Learn more about Review Apps"
link: /features/review-apps/
link: /product/review-apps/
screenshot_url: images/feature_page/screenshots/10-review-apps.png
feature_page: true
category:
......@@ -3459,7 +3459,7 @@ features:
description: "GitLab Pages provides an easy system for hosting static sites using GitLab repositories and GitLab CI, complete with custom domains, access control, and HTTPS support."
screenshot_url: 'images/feature_page/screenshots/03-gitlab-pages.png'
link_description: "Learn more about GitLab Pages"
link: '/features/pages/'
link: '/product/pages/'
feature_page: true
category:
- source_code_management
......
......@@ -182,7 +182,7 @@ features:
- name: Issue Board Usability Improvements
available_in: [core, starter, premium]
webpage_url: '/features/issueboard/'
webpage_url: '/product/issueboard/'
documentation_text: "Learn more about GitLab Issue Boards"
image_url: '/images/9_3/issue_board_usability_improvements.png'
description: |
......
......@@ -14,7 +14,7 @@ features:
lifecycle, built on top of [GitLab CI/CD](/features/gitlab-ci-cd/).
As it stands, GitLab offers a single environment where a code change can not only initiate a build,
but deploy a [Review App](/features/review-apps/) to preview your changes from
but deploy a [Review App](/product/review-apps/) to preview your changes from
within each merge request. During the review process GitLab's recently introduced ability to measure
[Code Quality](https://docs.gitlab.com/ee/user/project/merge_requests/code_quality_diff.html#code-quality)
ensures changes improve the overall quality of your software.
......
......@@ -38,7 +38,7 @@ features:
Starting with GitLab 10.1 you can easily connect your Google account to your projects and
create a new [Kubernetes cluster](https://docs.gitlab.com/ee/user/project/clusters/)
directly from the GitLab **Cluster** page. Then you can use it to host
[Review Apps](https://about.gitlab.com/features/review-apps/) and deployment environments.
[Review Apps](https://about.gitlab.com/product/review-apps/) and deployment environments.
In GitLab 10.2 we go even further, allowing you to install
[Helm Tiller](https://docs.helm.sh/) and [Nginx Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/)
......@@ -295,7 +295,7 @@ features:
reporter: bikebilly
issue_url: 'https://gitlab.com/gitlab-org/gitlab-ce/issues/23000'
description: |
[GitLab Pages](https://about.gitlab.com/features/pages/) allow you to publish a static website
[GitLab Pages](https://about.gitlab.com/product/pages/) allow you to publish a static website
directly from your project's pipeline. If you want to make it more professional, you can also
define custom domains for your content, and protect them with certificates.
......
......@@ -39,13 +39,13 @@ extra_css:
your applications. In this demo, you will get a short overview of
%strong GitLab’s built-in
%a{ href: "https://docs.gitlab.com/ee/user/project/issues/", target: "_blank" } issue tracking,
%a{ href: "https://about.gitlab.com/features/issueboard/", target: "_blank" } issue boards,
%a{ href: "https://about.gitlab.com/product/issueboard/", target: "_blank" } issue boards,
%a{ href: "https://about.gitlab.com/product/source-code-management/", target: "_blank" } version control,
%a{ href: "https://about.gitlab.com/product/code-review/", target: "_blank" } code review,
%a{ href: "https://about.gitlab.com/auto-devops/", target: "_blank" } Auto DevOps,
%a{ href: "https://about.gitlab.com/product/auto-devops/", target: "_blank" } Auto DevOps,
%a{ href: "https://about.gitlab.com/features/gitlab-ci-cd/", target: "_blank" } CI/CD,
%a{ href: "https://docs.gitlab.com/ee//user/project/merge_requests/sast.html", target: "_blank" } SAST
%a{ href: "https://docs.gitlab.com/ee/user/project/merge_requests/dast.html", target: "_blank" } /DAST
%a{ href: "https://docs.gitlab.com/ee/user/project/merge_requests/dast.html", target: "_blank" } /DAST
and more!
#confirmform{style: "display:none;"}
.centered-form-info
......
......@@ -134,7 +134,7 @@ extra_css:
to check if your code is valid
%li
Look at a live preview of your development branch with
%a{href: "/features/review-apps/"}Review Apps
%a{href: "/product/review-apps/"}Review Apps
before merging into stable
%li
%b Deploy
......
......@@ -38,7 +38,7 @@ feature of our product. While there is little or no disagreement on this approac
found it difficult, as an organization, to get started. This blueprint is intended to produce
a first step on the iterations towards CI/CD.
The end goal of this effort is to allow [GitLab Auto DevOps](https://about.gitlab.com/auto-devops/)
The end goal of this effort is to allow [GitLab Auto DevOps](/product/auto-devops/)
to deploy to GitLab.com.
## Today
......@@ -211,7 +211,7 @@ an even wider perspective than the one outlined in this blueprint (which, as not
Rather than putting together a grand plan to dogfood CI/CD, let's deploy our [values](/handbook/values/) to help us navigate through this transition:
* **Collaboration: Dogfooding** Let's dogfood GitLab's top-of-class CI/CD features.
* **Results: Write Promises Down** Let's commit [OKRs](/company/okrs/) on best-practice items we
* **Results: Write Promises Down** Let's commit [OKRs](/company/okrs/) on best-practice items we
know we must start thinking about: service versioning, feature flags and evolutionary
database design techniques, to name a few.
* **Results: Tenacity** Let's commit to this transition.
......
......@@ -103,7 +103,7 @@ Related Reading:
**VP Apps/Development/Engineering** - Helping to meet business demand for innovation, updates, and capability. This role is typically bonused/compensated on velocity, time to market and alignment with the business.
1. Value Prop
- GitLab’s single application that supports the entire DevOps lifecycle is of significant importance. The DevOps tool chain crisis is real and there is a lot of ‘bubble gum and duct tape’ going on in and around integrating all these point DevOps tools in order to convey the full story of what’s really happening.
- Finding new areas across the SDLC to automate is top of mind to this role. GitLab’s [Auto DevOps](https://about.gitlab.com/auto-devops/) will be a competitive differentiator
- Finding new areas across the SDLC to automate is top of mind to this role. GitLab’s [Auto DevOps](https://about.gitlab.com/product/auto-devops/) will be a competitive differentiator
1. Resources:
- [GitLab Pitch Deck](https://docs.google.com/presentation/d/1dVPaGc-TnbUQ2IR7TV0w0ujCrCXymKP4vLf6_FDTgVg/)
- [GitLab home page](https://about.gitlab.com)
......@@ -114,7 +114,7 @@ Related Reading:
- [Geographically distributed teams](https://about.gitlab.com/features/gitlab-geo/)
- [High availability development](https://about.gitlab.com/high-availability/)
- [Team development platform](https://about.gitlab.com/solutions/developer-platform/)
- [Auto DevOps](https://about.gitlab.com/auto-devops/)
- [Auto DevOps](https://about.gitlab.com/product/auto-devops/)
- [CI/CD](https://about.gitlab.com/features/gitlab-ci-cd/)
- [Product page](https://about.gitlab.com/product/)
- [Comparison page](https://about.gitlab.com/devops-tools/)
......@@ -129,7 +129,7 @@ Related Reading:
- [GitLab home page](https://about.gitlab.com)
- [ROI](https://about.gitlab.com/roi/replace/)
- [Concurrent DevOps](https://about.gitlab.com/concurrent-devops/)
- [Auto DevOps](https://about.gitlab.com/auto-devops/)
- [Auto DevOps](https://about.gitlab.com/product/auto-devops/)
- [Geographically distributed teams](https://about.gitlab.com/features/gitlab-geo/)
- [High availability development](https://about.gitlab.com/high-availability/)
- [DevSecOps](https://about.gitlab.com/solutions/dev-sec-ops)
......
......@@ -176,9 +176,9 @@ Maybe we should make our features easier to search to replace the section below.
[Clement Ho]: /team/#ClemMakesApps
[Aricka]: /team/#arickaflowers
[Suri]: /team/#suripatel
[Pages]: /features/pages/
[Pages]: /product/pages/
[Geo]: /features/gitlab-geo/
[Continuous Integration (CI)]: /features/gitlab-ci-cd/
[Continuous Delivery (CD)]: /features/gitlab-ci-cd/
[Subgroups]: /features/subgroups/
[Service Desk]: /features/service-desk/
[Service Desk]: /product/service-desk/
......@@ -98,7 +98,7 @@ People that join GitLab all say they already practice this iteration. But this i
The way to resolve this is to write down only what you can do with the time you have for this project right now. That might be 5 minutes or 2 hours. Think of what you can complete in that time that would improve the current situation. Iteration feels uncomfortable, and people might ask why something was not perfect. In that case mention that it was an iteration, you spent only x amount of time on it, and that the next iteration will contain y and be ready on z.
1. **Reduce cycle time** Short iterations reduce [our cycle time](/features/cycle-analytics/).
1. **Reduce cycle time** Short iterations reduce [our cycle time](/product/cycle-analytics/).
1. **Work as part of the community** Small iterations make it easier to work with the wider community. Their work looks more like our work and our work is quicker to give feedback too.
1. **Minimum Viable Change (MVC)** Always look to make the quickest change possible to improve the outcome. If you think it is better than what is there now do it. No need to wait for something polished. [More information is in the product handbook](/handbook/product/#the-minimally-viable-change) but it applies to everything we do in all functions.
1. **Make a proposal** If you need to decide something as a team make a proposal instead of calling a meeting to get everyone's input. Having a proposal will be a much more effective use of everyone's time. The people that receive the proposal should not feel left out, the person making it should not feel bad if a completely different proposal is implemented. Don't let your ego to be involved early or to see your solution implemented stand in the way of getting to the best outcome.
......
......@@ -13,7 +13,7 @@
-# %li{class: ("active" if current_page.url == "/features/file-locking/")}
-# %a{href: "/features/file-locking"}
-# File Locking
-# %li{class: ("active" if current_page.url == "/features/service-desk/")}
-# %li{class: ("active" if current_page.url == "/product/service-desk/")}
-# %a{href: "/features/service-desk"}
-# Service Desk
%li{class: ("active" if current_page.url == "/features/gitlab-ci-cd/")}
......
......@@ -37,7 +37,7 @@
%h4
Issue Boards
%p Plan, organize and visualize your release with multiple issue boards per project.
%a{href:"/features/issueboard/", class: "white-background-link"}
%a{href:"/product/issueboard/", class: "white-background-link"}
Learn more...
.col-md-4.clearfix
.col-xs-2
......
......@@ -193,7 +193,7 @@ great features in GitLab 8.11. [Register here][webcast].
[cycle]: https://gitlab.com/gitlab-org/gitlab-ce/issues/20975
[direction]: /direction/
[doc]: http://docs.gitlab.com/ee/user/project/issue_board.html
[GitLab Issue Board]: /features/issueboard/
[GitLab Issue Board]: /product/issueboard/
[issue]: /2016/03/03/start-with-an-issue/
[koding]: /2016/07/26/koding-and-gitlab-integrated/
[mattermost]: /2015/08/18/gitlab-loves-mattermost/
......
......@@ -116,7 +116,7 @@ VP of Product, [Ashley Smith][ashley], Chief Marketing Officer, and guest MC Com
[container]: /2016/05/23/gitlab-container-registry/
[cycle]: https://gitlab.com/gitlab-org/gitlab-ce/issues/20975
[event-page]: https://Page.gitlab.com/20160913_UnveilingMasterPlan_landingpage.html
[GitLab Issue Board]: /features/issueboard/
[GitLab Issue Board]: /product/issueboard/
[gitlab-vision]: /direction/#vision
[issue-board-launch]: /2016/08/22/announcing-the-gitlab-issue-board/
[issue]: /2016/03/03/start-with-an-issue/
......
......@@ -236,7 +236,7 @@ As always, if you have any questions feel free to comment on this post or [tweet
[GitLab Pages]: https://pages.gitlab.io/
[gitlab-scope]: /direction/#scope
[gitlab-twitter]: https://twitter.com/gitlab
[Issue Board]: /features/issueboard/
[Issue Board]: /product/issueboard/
[job-twitter]: https://twitter.com/Jobvo
[jono-twitter]: https://twitter.com/jonobacon
[releases]: /blog/categories/releases/
......
......@@ -9,7 +9,7 @@ description: "See how GitLab's Cycle Analytics can help measure your team's velo
date: 2016-09-21 10:00
---
On September 22nd, we will release [GitLab 8.12](/2016/09/22/gitlab-8-12-released/) with [Cycle Analytics](/features/cycle-analytics/). Cycle Analytics tells you how long
On September 22nd, we will release [GitLab 8.12](/2016/09/22/gitlab-8-12-released/) with [Cycle Analytics](/product/cycle-analytics/). Cycle Analytics tells you how long
it takes your team to go [from idea to production][idea-production] on each of their projects.
Few teams can answer how long
......@@ -90,7 +90,7 @@ We recognize that every team does not follow the same flow. And while GitLab is
## Getting Started
On September 22nd, [Cycle Analytics](/features/cycle-analytics/) will be available in GitLab.com, GitLab Community Edition, and GitLab Enterprise Edition. Getting started is the same in all three products. All you have to do is navigate to your Project’s **Pipelines** tab and then select **Cycle Analytics** to see your project's dashboard.
On September 22nd, [Cycle Analytics](/product/cycle-analytics/) will be available in GitLab.com, GitLab Community Edition, and GitLab Enterprise Edition. Getting started is the same in all three products. All you have to do is navigate to your Project’s **Pipelines** tab and then select **Cycle Analytics** to see your project's dashboard.
Keep in mind that if you're working in a new project and you haven't deployed anything to production then you won't see any data on your Cycle Analytics dashboard.
......
......@@ -116,7 +116,7 @@ Register for an event near you:
[condev]: /2016/09/14/gitlab-live-event-recap/#convdev
[container]: /2016/05/23/gitlab-container-registry/
[cycle]: /2016/09/21/cycle-analytics-feature-highlight/
[GitLab Issue Board]: /features/issueboard/
[GitLab Issue Board]: /product/issueboard/
[gitlab-vision]: /direction/#vision
[issue-board-launch]: /2016/08/22/announcing-the-gitlab-issue-board/
[issue]: /2016/03/03/start-with-an-issue/
......
......@@ -89,7 +89,7 @@ GitLab has always shipped a new version on the
[MrTrustor's Shiny Blog: Gitlab's Master Plan](http://blog.mrtrustor.net/post/gitlab-grand-master-plan/)
Iterations is so important to us that we built
[Cycle Analytics](/features/cycle-analytics/) to
[Cycle Analytics](/product/cycle-analytics/) to
allow anyone to measure how long it takes them to get from [Idea to Production](https://www.youtube.com/watch?v=t_rB1oQdG98),
with GitLab its a matter of minutes!
......
......@@ -391,7 +391,7 @@ Questions? Feedback? Please leave a comment or tweet at us [@GitLab]! 🙌
[board]: /features/issueboard
[bulk subscriptions]: /2016/07/22/gitlab-8-10-released/#bulk-subscribe-to-issues
[ca-post]: /2016/09/21/cycle-analytics-feature-highlight/
[ca]: /features/cycle-analytics/
[ca]: /product/cycle-analytics/
[ci-cd-cd]: /2016/08/05/continuous-integration-delivery-and-deployment-with-gitlab/
[ci]: /gitlab-ci/
[confid-issue]: /2016/03/31/feature-highlihght-confidential-issues/
......
......@@ -458,7 +458,7 @@ Next, we define the Review Apps.
### Review Apps
When opening a merge request for the docs site we use a new feature called [Review Apps](/features/review-apps/) to test changes. This lets us test new features, style changes, new sections, etc., by deploying the updated static site to a test domain. On every merge request that all jobs finished successfully, we can see a link with the URL to the temporary deployed docs site.
When opening a merge request for the docs site we use a new feature called [Review Apps](/product/review-apps/) to test changes. This lets us test new features, style changes, new sections, etc., by deploying the updated static site to a test domain. On every merge request that all jobs finished successfully, we can see a link with the URL to the temporary deployed docs site.
![Review apps](/images/blogimages/gitlab-docs-review-apps-screenshot.png){: .shadow}
......
......@@ -397,7 +397,7 @@ k8s-deploy-production:
The `environment` keyword associates the job with a specific environment while the `url` element is used to generate a handy hyperlink to our application on the GitLab Environments page (found under your project's `Pipelines > Environments`). The `only` keyword signals to GitLab CI that the job should be executed only when the pipeline is building the listed branches. Finally, `when: manual` is used to turn the job execution from automatic to manual. Turning the execution of this job to `automatic` would project us in the world of [Continuous Deployment](/2016/08/05/continuous-integration-delivery-and-deployment-with-gitlab/#continuous-deployment) rather than [Continuous Delivery](/2016/08/05/continuous-integration-delivery-and-deployment-with-gitlab/#continuous-delivery). From a Kubernetes perspective, we are making use of `namespaces` to segregate the different environments.
By committing on `master` and `production` we [trigger a pipeline per environment](/2016/08/26/ci-deployment-and-environments/). As mentioned before, we are not making use of any collaboration tool because it is out of the scope of this tutorial. In real-world scenarios, we would use [merge requests](/2016/10/25/gitlab-workflow-an-overview/#merge-request) with [Review Apps](/features/review-apps/) to move code across branches. Merge requests allow the team to review and discuss the changes before they get merged into the target branch. [Review Apps](/features/review-apps/) take that one step further by spinning up dynamic environments for our merge requests, offering the team access to a deployed instance of our application without the need of checking out the branch. This is extremely useful not only for non-technical members of the team, but also to collaborators and project managers to preview the changes without having to clone and install the app and its dependencies when evaluating a proposal.
By committing on `master` and `production` we [trigger a pipeline per environment](/2016/08/26/ci-deployment-and-environments/). As mentioned before, we are not making use of any collaboration tool because it is out of the scope of this tutorial. In real-world scenarios, we would use [merge requests](/2016/10/25/gitlab-workflow-an-overview/#merge-request) with [Review Apps](/product/review-apps/) to move code across branches. Merge requests allow the team to review and discuss the changes before they get merged into the target branch. [Review Apps](/product/review-apps/) take that one step further by spinning up dynamic environments for our merge requests, offering the team access to a deployed instance of our application without the need of checking out the branch. This is extremely useful not only for non-technical members of the team, but also to collaborators and project managers to preview the changes without having to clone and install the app and its dependencies when evaluating a proposal.
```shell
git commit -am "Showcasing Pipelines"
......
......@@ -7,7 +7,7 @@ image_title: '/images/blogimages/code-gitlab-tanuki.png'
description: "GitLab's Head of Product shares an inside look at iterating on one of our latest features"
---
A bunch of us on the GitLab team have known for a while just how important review apps are. Even though this wasn’t something that a lot of customers asked for, we knew we had to tackle it because of how we'd seen it transform a developer's flow. We also knew that tightly integrating it into GitLab would make it even better. Although our aspirations for the feature started out gigantic and magical, we ultimately constrained them to the practical and concrete. Here's a behind-the-scenes look at how we iterated and shipped [Review Apps](/features/review-apps/) over the last 3 releases.
A bunch of us on the GitLab team have known for a while just how important review apps are. Even though this wasn’t something that a lot of customers asked for, we knew we had to tackle it because of how we'd seen it transform a developer's flow. We also knew that tightly integrating it into GitLab would make it even better. Although our aspirations for the feature started out gigantic and magical, we ultimately constrained them to the practical and concrete. Here's a behind-the-scenes look at how we iterated and shipped [Review Apps](/product/review-apps/) over the last 3 releases.
<!-- more -->
......
......@@ -174,7 +174,7 @@ GitLab 8.11 was probably the most exciting release of the year, bringing with it
### Issue Boards
[Issue Boards](/features/issueboard/) are another way of tracking project issues. Similar to existing kanban board software, [issue boards integrate](https://docs.gitlab.com/ee/user/project/issue_board.html) with the issues you already have in GitLab and organize themselves based on project labels. If you're already using labels to track progress on issues, issue boards shouldn't take more than a minute to set up.
[Issue Boards](/product/issueboard/) are another way of tracking project issues. Similar to existing kanban board software, [issue boards integrate](https://docs.gitlab.com/ee/user/project/issue_board.html) with the issues you already have in GitLab and organize themselves based on project labels. If you're already using labels to track progress on issues, issue boards shouldn't take more than a minute to set up.
![Issue Boards](/images/8_11/issue_boards.gif){:.shadow}
......@@ -212,7 +212,7 @@ With the addition of [Slash Commands](https://docs.gitlab.com/ee/user/project/sl
### Cycle Analytics
The headline feature of 8.12 was [Cycle Analytics](/features/cycle-analytics/), a new way of [tracking software development](https://docs.gitlab.com/ee/user/project/cycle_analytics.html) using the data GitLab gathers as you use it. Cycle Analytics is the last step of the [GitLab Workflow](/2016/10/25/gitlab-workflow-an-overview/).
The headline feature of 8.12 was [Cycle Analytics](/product/cycle-analytics/), a new way of [tracking software development](https://docs.gitlab.com/ee/user/project/cycle_analytics.html) using the data GitLab gathers as you use it. Cycle Analytics is the last step of the [GitLab Workflow](/2016/10/25/gitlab-workflow-an-overview/).
See [our feature highlight blog post](/2016/09/21/cycle-analytics-feature-highlight/) for more information.
......@@ -260,7 +260,7 @@ We introduced [Chat Commands](https://docs.gitlab.com/ee/project_services/matter
### Review Apps
A new addition to GitLab CI in this release was [Review Apps](/features/review-apps/). Review Apps can be used to [deploy merge requests from your GitLab instance to a dev or staging environment for testing](https://docs.gitlab.com/ee/ci/review_apps/index.html). At GitLab, we use these for testing [about.gitlab.com](https://gitlab.com/gitlab-com/www-gitlab-com) as well as [docs.gitlab.com](https://gitlab.com/gitlab-com/gitlab-docs).
A new addition to GitLab CI in this release was [Review Apps](/product/review-apps/). Review Apps can be used to [deploy merge requests from your GitLab instance to a dev or staging environment for testing](https://docs.gitlab.com/ee/ci/review_apps/index.html). At GitLab, we use these for testing [about.gitlab.com](https://gitlab.com/gitlab-com/www-gitlab-com) as well as [docs.gitlab.com](https://gitlab.com/gitlab-com/gitlab-docs).
For more information on Review Apps, see [our feature highlight blog post](/2016/11/22/introducing-review-apps/).
......@@ -296,5 +296,5 @@ What improvements do you want to see this year?
<!-- Links -->
[issue boards]: /features/issueboard/
[cycle analytics]: /features/cycle-analytics/
[issue boards]: /product/issueboard/
[cycle analytics]: /product/cycle-analytics/
......@@ -177,7 +177,7 @@ Cover image: screenshot of [About CodePen][about].
<!-- identifiers -->
[about]: http://codepen.io/about/
[boards]: /features/issueboard/#step-6
[boards]: /product/issueboard/#step-6
[burndown]: https://gitlab.com/gitlab-org/gitlab-ee/issues/91
[ce]: /products/ "GitLab Community Edition"
[ci-cd]: /2016/08/05/continuous-integration-delivery-and-deployment-with-gitlab/
......@@ -187,7 +187,7 @@ Cover image: screenshot of [About CodePen][about].
[ee]: /gitlab-ee/ "GitLab Enterprise Edition"
[ff]: https://docs.gitlab.com/ee/user/project/merge_requests/fast_forward_merge.html
[importer]: https://docs.gitlab.com/ee/workflow/importing/import_projects_from_github.html
[Issue Boards]: /features/issueboard/
[Issue Boards]: /product/issueboard/
[jase smith]: http://codepen.io/jasesmith/
[pen]: http://codepen.io/jasesmith/pen/GqaVrx
[pipes]: https://docs.gitlab.com/ee/ci/pipelines.html
......
......@@ -45,7 +45,7 @@ Examples of this are:
1. The issue page (which shows an individual issue), has a lot of jQuery on it. We won't rewrite now, because it works well. We will rewrite small parts in Vue once we make certain features more real-time. We are currently making the title and description real time.
1. The [Issue Boards](/features/issueboard/), which [Phil](https://twitter.com/iamphill) wrote, was a perfect candidate for Vue. It was a brand new feature and had lots of reactive parts.
1. The [Issue Boards](/product/issueboard/), which [Phil](https://twitter.com/iamphill) wrote, was a perfect candidate for Vue. It was a brand new feature and had lots of reactive parts.
1. The current issue page loads all comments at once and adds lots of event listeners to the page. This page could benefit from Vue for performance reasons. We could make the comment section a Vue app and make the comments a component with the emoji picker as components as well, etc. While we're in there, we'll amp up the UX by allowing you to see the comment you linked to immediately without waiting. There are better ways to show massive amounts of comments so we have to potentially rethink that.
......
......@@ -84,7 +84,7 @@ To remove an issue from your board, select it to bring up the sidebar, and hit
Take a look at the [Issue Board documentation][board-doc] to learn more.
[board]: /features/issueboard/
[board]: /product/issueboard/
[board-doc]: https://docs.gitlab.com/ee/user/project/issue_board.html
![Remove issue from board in GitLab 8.17](/images/8_17/board_remove.png){: .shadow}
......
......@@ -16,7 +16,7 @@ Continuous methods go beyond integration, delivery and deployment. Releasing ear
## What are Review Apps?
[Review Apps](/features/review-apps/) are ephemeral app environments that are created dynamically every time you push a new branch up to GitLab, and they're automatically deleted when the branch is deleted. What this means in practice is that rather than having a single dev environment for a project, or even separate dev apps for each developer, you get a new app for every topic branch, automatically. This lets you test and demo new features easily: product managers can check out exactly what a merge request is going to look like without having to download and run a topic branch, while QA and other users can take a look without having a development environment installed on their laptop at all.
[Review Apps](/product/review-apps/) are ephemeral app environments that are created dynamically every time you push a new branch up to GitLab, and they're automatically deleted when the branch is deleted. What this means in practice is that rather than having a single dev environment for a project, or even separate dev apps for each developer, you get a new app for every topic branch, automatically. This lets you test and demo new features easily: product managers can check out exactly what a merge request is going to look like without having to download and run a topic branch, while QA and other users can take a look without having a development environment installed on their laptop at all.
## How we released Review Apps
......
......@@ -275,7 +275,7 @@ We also brought back the ability the create a new project quickly, by simply cli
## Reorder Issues in Board List ce ees eep
[Issue Boards](/features/issueboard/) are a great way to manage issues moving through the different stages ("lists" in GitLab), in order to quickly get an idea to production. But users often want to further represent order or priority of issues within a single list. With 9.0, you can now reorder issues within an issue board list, using the intuitive and existing drag and drop mechanism.
[Issue Boards](/product/issueboard/) are a great way to manage issues moving through the different stages ("lists" in GitLab), in order to quickly get an idea to production. But users often want to further represent order or priority of issues within a single list. With 9.0, you can now reorder issues within an issue board list, using the intuitive and existing drag and drop mechanism.
<i class="fas fa-book" aria-hidden="true"></i>
[Learn more about Issue Boards for Community Edition in our docs](https://docs.gitlab.com/ee/user/project/issue_board.html).
......
......@@ -16,7 +16,7 @@ cta_button_link: 'https://www.youtube.com/watch?v=py8c6-3zyKM&feature=youtu.be'
At GitLab, the pile of work to be done is perhaps even more visible than most. Right now, on the GitLab Community Edition [issue tracker](https://gitlab.com/gitlab-org/gitlab-ce) alone, there are 6,826 open issues, a number that could be numbing at best, and overwhelming at worst if viewed without a strong system for prioritization. Although I'm now the Frontend Lead, I started at GitLab as an engineer, and quickly became more productive than in any other previous job. I attribute this largely to the simple process that every new technical hire learns when they join, including a clear roadmap to follow when they start work every day. The key difference for me is that people at GitLab spend most of their time writing code, rather than talking about and planning it.
The secret hinges largely on our [issue board and labels](/features/issueboard/), with which we meticulously track progress and conversation. This also helps us meet other goals that are necessary for successful asynchronous work — we always opt for fewer meetings, and more communication through the issue tracker. All of these methods were passed down (and remixed) by our CTO, [Dmitriy Zaporozhets](/team/#dzaporozhets).
The secret hinges largely on our [issue board and labels](/product/issueboard/), with which we meticulously track progress and conversation. This also helps us meet other goals that are necessary for successful asynchronous work — we always opt for fewer meetings, and more communication through the issue tracker. All of these methods were passed down (and remixed) by our CTO, [Dmitriy Zaporozhets](/team/#dzaporozhets).
It boils down to three rules that help engineers sort issues and know exactly what to work on next, largely without consulting anyone:
......
......@@ -48,7 +48,7 @@ Deploys are risky when there is a lack of visibility between Development and Ops
### Measurement and Monitoring
For most teams, measurement and monitoring are tedious tasks in software development, but they're incredibly important to teams that are looking to continuously improve. Measurement, like GitLab's [Cycle Analytics](/features/cycle-analytics/), is key to helping teams understand what parts of their development process might be slowing them down. In 9.0, we're moving beyond measurement and working to help teams solve application performance monitoring challenges. Monitoring is critical to ensuring application performance meets the team's quality bar. Imagine if your application monitoring tool could help you avoid pushing poor-performing code in the first place? That's exactly where we are heading.
For most teams, measurement and monitoring are tedious tasks in software development, but they're incredibly important to teams that are looking to continuously improve. Measurement, like GitLab's [Cycle Analytics](/product/cycle-analytics/), is key to helping teams understand what parts of their development process might be slowing them down. In 9.0, we're moving beyond measurement and working to help teams solve application performance monitoring challenges. Monitoring is critical to ensuring application performance meets the team's quality bar. Imagine if your application monitoring tool could help you avoid pushing poor-performing code in the first place? That's exactly where we are heading.
#### Prometheus Environment Monitoring (CE)
......
......@@ -28,7 +28,7 @@ On-premise – installing and customizing software on your own machines in your
### Integration with other tools
Source code management is just one element of the software development lifecycle. Your teams will most likely want other features such as [issue tracking](/features/issueboard/), [CI/CD](/features/gitlab-ci-cd/), [code review](https://www.youtube.com/watch?v=XluG9mAQdSo&feature=youtu.be) and [collaboration tools](/2017/04/04/why-collaboration-tools-matter/). When choosing a Git management solution it's important to know what other tools or features your teams require, and whether the solution you're considering includes or supports those.
Source code management is just one element of the software development lifecycle. Your teams will most likely want other features such as [issue tracking](/product/issueboard/), [CI/CD](/features/gitlab-ci-cd/), [code review](https://www.youtube.com/watch?v=XluG9mAQdSo&feature=youtu.be) and [collaboration tools](/2017/04/04/why-collaboration-tools-matter/). When choosing a Git management solution it's important to know what other tools or features your teams require, and whether the solution you're considering includes or supports those.
### Cost
......
......@@ -435,7 +435,7 @@ Learn more about [usage ping](https://docs.gitlab.com/ee/user/admin_area/setting
### Issue Boards Focus Mode ees eep
[Issue Boards](/features/issueboard/) are a great solution for planning and managing issues that are being
[Issue Boards](/product/issueboard/) are a great solution for planning and managing issues that are being
worked together by a team, allowing you to track them as they move from stage to stage
in your workflow.
......
......@@ -28,7 +28,7 @@ Our three core teams involved in the process are product managers, designers, an
### Our process
We have the benefit of constant dogfooding, or using our own product so as to discover new use cases, test our assumptions, and generally improve GitLab for our users. Loosely, we have a product-design phase, and a code implementation phase. We use [GitLab issues](/features/issueboard/) to mediate product-design discussions, and GitLab merge requests to mediate code discussions. We encourage “[WIP](/2016/01/08/feature-highlight-wip/)”, or work in progress, merge requests for code collaboration, especially when people with different skills are working together: non-engineers often actively engage in WIP merge request discussions to hash out edge cases and design decisions. Since we ship monthly, we schedule work monthly, and putting up WIP merge requests early helps us plan ahead and adjust the scope when we need to.
We have the benefit of constant dogfooding, or using our own product so as to discover new use cases, test our assumptions, and generally improve GitLab for our users. Loosely, we have a product-design phase, and a code implementation phase. We use [GitLab issues](/product/issueboard/) to mediate product-design discussions, and GitLab merge requests to mediate code discussions. We encourage “[WIP](/2016/01/08/feature-highlight-wip/)”, or work in progress, merge requests for code collaboration, especially when people with different skills are working together: non-engineers often actively engage in WIP merge request discussions to hash out edge cases and design decisions. Since we ship monthly, we schedule work monthly, and putting up WIP merge requests early helps us plan ahead and adjust the scope when we need to.
We generally assign one backend engineer and one frontend engineer to each feature, which is scoped as small as possible to reduce risk and help us move fast. The backend engineer and frontend engineer collaborate in the WIP merge request, and there is at least one reviewer who reviews the code and makes comments. When all comments, bugs, and design questions are addressed, we merge the feature branch into master. All designers, product team members, and engineers typically check out branches themselves and run code in a local or virtual environment to verify features throughout the development process. (This is also the case for our marketing and people operations teams — GitLab's UI makes it simple for non-technical users to get up to speed and start contributing without needing to work from the command line.) Engineers do their own manual and sanity testing, but we use [Test Driven Development](http://agiledata.org/essays/tdd.html) to catch most errors. We don’t follow a strict Agile flow, instead, we call it [Conversational Development](http://conversationaldevelopment.com/).
......
......@@ -26,11 +26,11 @@ Using an open source solution has its advantages: it's free, and you can look un
## Support for integrations
It's fairly common for an organization's software development lifecycle to rely on several integrated tools (such as [issue boards](/features/issueboard/) and other discussion features). Find out what your teams are already using and if the CI/CD solution you're considering is supported. There's been growing interest in built-in CI/CD, which means developers can spend less time stringing together their tooling and more on new features and improvements. Bringing all your tools under one product with one interface and datastore is also useful for things like [cycle analytics](/features/cycle-analytics/), which can help to reduce the time between coming up with an idea and deploying it.
It's fairly common for an organization's software development lifecycle to rely on several integrated tools (such as [issue boards](/product/issueboard/) and other discussion features). Find out what your teams are already using and if the CI/CD solution you're considering is supported. There's been growing interest in built-in CI/CD, which means developers can spend less time stringing together their tooling and more on new features and improvements. Bringing all your tools under one product with one interface and datastore is also useful for things like [cycle analytics](/product/cycle-analytics/), which can help to reduce the time between coming up with an idea and deploying it.
## Visualizing the release process
One of the advantages of leveraging CI/CD is being able to see changes and new additions from the moment they're created. Does your chosen solution offer [Review Apps](/features/review-apps/), so you can automatically check out a live preview of new code? You might also benefit from [Deploy Boards](/2017/03/22/gitlab-9-0-released/#deploy-boards-eep), where you can watch a deploy roll out across pods and monitor the health and deployment status of each environment, all in one place. This makes it easier to spot problems and stop or roll back with one click. These are just a couple of features that can make a significant difference to your team's efficiency.
One of the advantages of leveraging CI/CD is being able to see changes and new additions from the moment they're created. Does your chosen solution offer [Review Apps](/product/review-apps/), so you can automatically check out a live preview of new code? You might also benefit from [Deploy Boards](/2017/03/22/gitlab-9-0-released/#deploy-boards-eep), where you can watch a deploy roll out across pods and monitor the health and deployment status of each environment, all in one place. This makes it easier to spot problems and stop or roll back with one click. These are just a couple of features that can make a significant difference to your team's efficiency.
## So how does GitLab CI/CD stack up?
......@@ -41,7 +41,7 @@ and a **hosted** option for GitLab Enterprise Edition Premium on [GitLab.com](/)
We have a **free and open source** offering, GitLab Community Edition, and two **enterprise** offerings,
Enterprise Edition Starter and Enterprise Edition Premium, with advanced features such as [GitLab Geo](/features/gitlab-geo/), [High Availability and Disaster Recovery](/high-availability/), [File Locking](https://docs.gitlab.com/ee/user/project/file_lock.html) and [Service Desk](https://docs.gitlab.com/ee/user/project/service_desk.html).
You can **visualize your release process** in all versions of GitLab with GitLab [CI/CD Pipelines](https://docs.gitlab.com/ee/ci/pipelines.html), [Review Apps](/features/review-apps/) and [Prometheus monitoring](https://docs.gitlab.com/ee/administration/monitoring/prometheus/).
You can **visualize your release process** in all versions of GitLab with GitLab [CI/CD Pipelines](https://docs.gitlab.com/ee/ci/pipelines.html), [Review Apps](/product/review-apps/) and [Prometheus monitoring](https://docs.gitlab.com/ee/administration/monitoring/prometheus/).
GitLab Enterprise Premium comes with [Deploy Boards](https://docs.gitlab.com/ee/user/project/deploy_boards.html) and
[Canary Deployments](/2017/04/22/gitlab-9-1-released/#canary-deployments-eep) for even more advanced control over deployments.
......
......@@ -23,7 +23,7 @@ For developers, containers make it possible to build one version of an applicati
Communication and collaboration between developers and operations also improves because developers have seen exactly what it is that operations is getting, and operations are running exactly what the developers gave them. The result is that everyone can focus more on shipping quality code faster because applications don't have to be rebuilt as they move through the development lifecycle.
GitLab integrates with both Kubernetes and OpenShift container orchestration platforms, making it possible to run continuous integration and continuous delivery related jobs in the cluster. It also gives you the ability to set up different environments, called [Review Apps](/features/review-apps/), for different branches of your code base. Review Apps make it easy to view and test changes in an environment, in the cluster, so you can iterate and test faster.
GitLab integrates with both Kubernetes and OpenShift container orchestration platforms, making it possible to run continuous integration and continuous delivery related jobs in the cluster. It also gives you the ability to set up different environments, called [Review Apps](/product/review-apps/), for different branches of your code base. Review Apps make it easy to view and test changes in an environment, in the cluster, so you can iterate and test faster.
### Demo
......
......@@ -27,7 +27,7 @@ There’s no substitute for the work of the human brain, but by automating some
## 3. They use collaboration tools
Having space for comments, questions or suggestions at each stage of the cycle is critical for fostering collaboration and making sure that everyone can follow the latest progress of a project. “For us, the single source of truth is always the [issue](/features/issueboard/). Tools like labels, milestones, assigning to people, these all make sure that the right person knows when it’s their turn to do something, and the handoff happens through issue comments,” explains Douwe. This is another area in which we’ve had to become disciplined about documenting the latest update on an issue, because as a distributed team we can’t just walk over to a colleague’s desk to check something. “We don’t have the problem where after two days people will be like, ‘Hmm, what did we decide again?’” says Douwe. Discussion takes place right in the same environment where we’re working – whether it’s a comment on an issue or a merge request or an inline question on the code itself – so it’s easy for everyone to see the context for it and to refer back to it later.
Having space for comments, questions or suggestions at each stage of the cycle is critical for fostering collaboration and making sure that everyone can follow the latest progress of a project. “For us, the single source of truth is always the [issue](/product/issueboard/). Tools like labels, milestones, assigning to people, these all make sure that the right person knows when it’s their turn to do something, and the handoff happens through issue comments,” explains Douwe. This is another area in which we’ve had to become disciplined about documenting the latest update on an issue, because as a distributed team we can’t just walk over to a colleague’s desk to check something. “We don’t have the problem where after two days people will be like, ‘Hmm, what did we decide again?’” says Douwe. Discussion takes place right in the same environment where we’re working – whether it’s a comment on an issue or a merge request or an inline question on the code itself – so it’s easy for everyone to see the context for it and to refer back to it later.
## 4. They use integrated platforms
......
......@@ -16,7 +16,7 @@ If your new features often get stalled in the initial discussion phase, read our
## 1. Measure your cycle time
The first step towards making a change is having the numbers to motivate it. If you measure the duration of time from the moment an idea is first discussed in chat, all the way through to its release in production, you can make a good case for changing your approach if others can see that something is causing delays. Try a feature like [cycle analytics](/features/cycle-analytics/) to monitor each stage in your workflow.
The first step towards making a change is having the numbers to motivate it. If you measure the duration of time from the moment an idea is first discussed in chat, all the way through to its release in production, you can make a good case for changing your approach if others can see that something is causing delays. Try a feature like [cycle analytics](/product/cycle-analytics/) to monitor each stage in your workflow.
## 2. Start with minimum viable changes
......
......@@ -10,7 +10,7 @@ description: "A GitLab user shows us how to deploy Docker containers as a Review
tags: user stories, CI
---
Last year GitLab introduced the [Review Apps](/features/review-apps/) feature. Review Apps are app environments that are created dynamically every time you push a new branch up to GitLab. As a bonus point the app environments are automatically deleted when the branch is deleted. Since we moved to using Docker for quite a few of our projects I was keen on figuring out how to combine Docker and the GitLab Review Apps functionality as the documentation only mentions NGINX as a way to run Review Apps. As it turns out, it is rather simple to deploy Docker containers as a Review App.
Last year GitLab introduced the [Review Apps](/product/review-apps/) feature. Review Apps are app environments that are created dynamically every time you push a new branch up to GitLab. As a bonus point the app environments are automatically deleted when the branch is deleted. Since we moved to using Docker for quite a few of our projects I was keen on figuring out how to combine Docker and the GitLab Review Apps functionality as the documentation only mentions NGINX as a way to run Review Apps. As it turns out, it is rather simple to deploy Docker containers as a Review App.
<!-- more -->
......
......@@ -19,7 +19,7 @@ tools, GitLab by default provides all the capabilities modern development teams
<!-- more -->
Last year, we announced the first iteration of the [GitLab Issue Board](/features/issueboard/), a major
Last year, we announced the first iteration of the [GitLab Issue Board](/product/issueboard/), a major
milestone in our mission to create an open source and integrated
product for modern software development. Built on top of our integrated issue
tracking system, it became possible to visualize your work and customize your
......
......@@ -302,7 +302,7 @@ company would.
~~The other way to look at it is that this is pretty advanced stuff, and frankly,
it doesn’t deserve to be, free, open source. It’s probably really complicated
stuff, and you’re going to have to pay there.~~ *[Editor's note: Advancedness is not a criteria in open sourcing or not open sourcing. There are advanced features that are open source, such as [Review Apps](/features/review-apps/). There are basic features that are proprietary, such as [File Locking](/features/file-locking/). The criteria we use to decide which version the features go in are documented on our [stewardship page](/company/stewardship/#what-features-are-paid-only).]* Maybe there’d be levels to it,
stuff, and you’re going to have to pay there.~~ *[Editor's note: Advancedness is not a criteria in open sourcing or not open sourcing. There are advanced features that are open source, such as [Review Apps](/product/review-apps/). There are basic features that are proprietary, such as [File Locking](/features/file-locking/). The criteria we use to decide which version the features go in are documented on our [stewardship page](/company/stewardship/#what-features-are-paid-only).]* Maybe there’d be levels to it,
right? There’d be a version that gives you an alert: we’ll run this test once a
day. Or even just have a blog post about how to do this: you set up a recurring,
scheduled pipeline job, once a day, to test if any of your dependencies have
......
......@@ -54,7 +54,7 @@ team. Missing even the most minute detail can completely derail an otherwise
successful development project, so react immediately if you spot any oversights,
no matter how small.
Features like Issues and [Issue Boards](/features/issueboard/) can help everyone break down
Features like Issues and [Issue Boards](/product/issueboard/) can help everyone break down
complex tasks into smaller individual ones and track their progress across the
development lifecycle. Singular tasks are often be the best way for developers
to tackle a subject – this is especially true for junior developers and
......@@ -120,7 +120,7 @@ it’s certainly [helped big software companies like Shopify refine their develo
If you want to find problems, you need to be tracking them first! From
collecting the right data, to testing and tracking, make sure that you
constantly keeping tabs on the project as it progresses. Adopting tools like
[Cycle Analytics](/features/cycle-analytics/) will
[Cycle Analytics](/product/cycle-analytics/) will
ensure that you always stay on track with how your projects are progressing,
and the data you’ll harness will become an invaluable source of business intelligence.
......
......@@ -15,11 +15,11 @@ Actively triaging issues is crucial for keeping an overview on your repository,
## Preparation
There are three types of issues: questions, bug reports, and feature requests. Define which you want to tackle in your tracker and which you handle elsewhere (you can use different [GitLab Issue Boards](/features/issueboard/) to help keep different types of issues together). Once this has been done, check each issue with the following scheme:
There are three types of issues: questions, bug reports, and feature requests. Define which you want to tackle in your tracker and which you handle elsewhere (you can use different [GitLab Issue Boards](/product/issueboard/) to help keep different types of issues together). Once this has been done, check each issue with the following scheme:
## 1. Filter noise
Check whether the issue is the type you want in your tracker (as defined in the preparation phase). If not, point the user to the right place or move it to the relevant [issue board](/features/issueboard/) yourself. For example, indicate that questions will be answered on Stack Overflow or feature requests are best being posted for discussion in the Slack channel. Be friendly; remember the user just provided valuable feedback. Close the issue once you’ve pointed the user to the right place.
Check whether the issue is the type you want in your tracker (as defined in the preparation phase). If not, point the user to the right place or move it to the relevant [issue board](/product/issueboard/) yourself. For example, indicate that questions will be answered on Stack Overflow or feature requests are best being posted for discussion in the Slack channel. Be friendly; remember the user just provided valuable feedback. Close the issue once you’ve pointed the user to the right place.
## 2. Look for similars
......
......@@ -28,7 +28,7 @@ concepts and even invoices.
Being a [Certified Scrum Product Owner](https://www.scrumalliance.org/certifications/practitioners/cspo-certification) and using a [GitLab](/) instance at work, I decided to take advantage of the free private repositories and use GitLab.com for UnscrewMe. This combines the simplicity of “just” storing everything in files and folders, with the advantage of being able to use Markdown for more advanced formatting, including sub headings, nested lists and images. And all information can easily be accessed on any device, either via Git directly or the GitLab.com web interface, which also renders Markdown files nicely.
In addition, project management features of GitLab like [issues](https://docs.gitlab.com/ee/user/project/issues/), [milestones](https://docs.gitlab.com/ee/user/project/milestones/) and
[Issue Boards](/features/issueboard/) would provide a useful, flexible and lightweight framework to
[Issue Boards](/product/issueboard/) would provide a useful, flexible and lightweight framework to
track my progress. By defining project phases and grouping all open tasks in
various ways, I could get a quick overview of what I would need to do next,
before I could actually launch my Minimum Viable Product (MVP).
......
......@@ -27,7 +27,7 @@ In thinking about the other tools I've used in the past, they didn't seem to mee
## Enter GitLab Issue Boards
With these requirements, and my newfound GitLab knowledge, I was able to come up with a novel solution to the problem we were having: why not use a [GitLab Issue Board](/features/issueboard/) to manage our ever-changing home renovation priorities?
With these requirements, and my newfound GitLab knowledge, I was able to come up with a novel solution to the problem we were having: why not use a [GitLab Issue Board](/product/issueboard/) to manage our ever-changing home renovation priorities?
With Issue Boards, we would have a fantastic solution for mobile and desktop (shout out to the [GitLab UX team](https://docs.gitlab.com/ee/development/ux_guide/)!). With [labels](https://docs.gitlab.com/ee/user/project/labels.html), I could organize and group issues however we wanted. And the customizable columns would allow us to prioritize, track and manage the various issues and ideas.
......
......@@ -10,7 +10,7 @@ twitter_text: "How to set up advanced monitoring for your @gitlab environment wi
tags: integrations
---
GitLab comes with some built-in monitoring and visualization capabilities, such as [Cycle Analytics](/features/cycle-analytics/) and the [per-project contributors](https://docs.gitlab.com/ee/user/group/contribution_analytics/) and [repository](https://docs.gitlab.com/ee/user/project/repository/#repository-graph) graphs, as well as [integration with Prometheus](https://docs.gitlab.com/ee/administration/monitoring/prometheus/) to monitor your GitLab instance at the server level. Cycle Analytics is especially useful as it enables teams to analyze their efficiency. However, if you want to analyze the data by searching and querying, or if you want to visualize the data yourself, you might find it helpful to adopt a more centralized methodology by integrating with the [ELK Stack](https://logz.io/learn/complete-guide-elk-stack/) (Elasticsearch, Logstash and Kibana).
GitLab comes with some built-in monitoring and visualization capabilities, such as [Cycle Analytics](/product/cycle-analytics/) and the [per-project contributors](https://docs.gitlab.com/ee/user/group/contribution_analytics/) and [repository](https://docs.gitlab.com/ee/user/project/repository/#repository-graph) graphs, as well as [integration with Prometheus](https://docs.gitlab.com/ee/administration/monitoring/prometheus/) to monitor your GitLab instance at the server level. Cycle Analytics is especially useful as it enables teams to analyze their efficiency. However, if you want to analyze the data by searching and querying, or if you want to visualize the data yourself, you might find it helpful to adopt a more centralized methodology by integrating with the [ELK Stack](https://logz.io/learn/complete-guide-elk-stack/) (Elasticsearch, Logstash and Kibana).
<!-- more -->
......
......@@ -37,7 +37,7 @@ Once connected, you can install applications like [Helm Tiller](https://helm.sh/
### Enable Auto DevOps
We've also worked with Google to integrate GitLab Auto DevOps with GKE. Using them together, you'll have a continuous deployment pipeline that automatically creates a [review app](/features/review-apps/) for each merge request and once you merge, deploys the application into production on production-ready GKE.
We've also worked with Google to integrate GitLab Auto DevOps with GKE. Using them together, you'll have a continuous deployment pipeline that automatically creates a [review app](/product/review-apps/) for each merge request and once you merge, deploys the application into production on production-ready GKE.
To get started, go to CI/CD -> General pipeline settings, and select “Enable Auto DevOps.” For more information, read the [Auto DevOps docs](https://docs.gitlab.com/ee/topics/autodevops/).
......
......@@ -27,7 +27,7 @@ Recently, we announced our [migration from Azure to GCP](/2018/06/25/moving-to-g
With a built-in container registry and [Kubernetes integration](/solutions/kubernetes/), GitLab makes it easier than ever to get started with containers and cloud native development. Gitlab CI/CD can deploy your application to any Kubernetes cluster.
If you don’t have a Kubernetes cluster, we’ve got you covered. The easiest way to get set up in using our [GKE Integration](/solutions/google-cloud-platform/) and [Auto DevOps](/auto-devops/). It takes just a few clicks to set up, then you have a full deployment pipeline. Just commit your code and GitLab does rest.
If you don’t have a Kubernetes cluster, we’ve got you covered. The easiest way to get set up in using our [GKE Integration](/solutions/google-cloud-platform/) and [Auto DevOps](/product/auto-devops/). It takes just a few clicks to set up, then you have a full deployment pipeline. Just commit your code and GitLab does rest.
![GitLab deploys your app to Google Cloud Platform](/images/google-cloud-platform/gitlab-send-app-medium.png)
......
......@@ -74,7 +74,7 @@ On the day of the migration, we are planning to start at 10:00 UTC. The time wi
### GitLab Pages and custom domains
If you have a custom domain on [GitLab Pages](https://about.gitlab.com/features/pages/):
If you have a custom domain on [GitLab Pages](https://about.gitlab.com/product/pages/):
* We will have a proxy in place so you do not have to change your DNS immediately.
* GitLab Pages will ultimately go to 35.185.44.232 after the July 28 migration.
......
......@@ -15,7 +15,7 @@ There are many different ways to build software and run projects. When we began
to build portfolio and project management tools within GitLab, we asked
ourselves, "How do you build tools to support a diverse array of workflows
without crippling users with complexity?" Our conclusion? Build fewer, but more
flexible tools. GitLab's built-in [issue boards](/features/issueboard/) is a
flexible tools. GitLab's built-in [issue boards](/product/issueboard/) is a
great example of how choosing to build a single, versatile tool can significantly
reduce complexity and tooling maintenance for the user without limiting its
capabilities.
......
......@@ -13,9 +13,9 @@ twitter_text: "Confused about how Auto DevOps works? Here’s a chance to see @g
---
Better and faster. These two words best describe the production goals of the IT leaders and engineers building today’s cutting-edge software. And GitLab [Auto DevOps](/auto-devops/) can help them hit those goals while improving their overall business outcomes.
Better and faster. These two words best describe the production goals of the IT leaders and engineers building today’s cutting-edge software. And GitLab [Auto DevOps](/product/auto-devops/) can help them hit those goals while improving their overall business outcomes.
As the only single application for the complete [DevOps](/devops/) lifecycle, GitLab Auto DevOps gives development teams all the tools they need to deliver secure, high-quality software at previously unattainable speeds. The secret sauce that makes Auto DevOps so effective is the way it automatically sets up the required integrations and pipeline needed to get your software out of the door faster. With Auto DevOps, your code is automatically tested for quality, scanned for security vulnerabilities and licensing issues, packaged and then set up for monitoring and deployment, leaving engineers with time to place more attention on creating a better product.
As the only single application for the complete [DevOps](/devops/) lifecycle, GitLab Auto DevOps gives development teams all the tools they need to deliver secure, high-quality software at previously unattainable speeds. The secret sauce that makes Auto DevOps so effective is the way it automatically sets up the required integrations and pipeline needed to get your software out of the door faster. With Auto DevOps, your code is automatically tested for quality, scanned for security vulnerabilities and licensing issues, packaged and then set up for monitoring and deployment, leaving engineers with time to place more attention on creating a better product.
This may all make sense in theory, but as they say, a picture is worth 1,000 words. And it is [rumored](https://idearocketanimation.com/4293-video-worth-1-million-words/?) that video is worth 1.8 million words. With that being said, why not take a look at GitLab Auto DevOps in action? Check out this demo from a recent [Release Radar webcast](/webcast/monthly-release/):