WIP: Benefits of a deploy board post
6 unresolved threads
6 unresolved threads
Closes marketing#1086
Merge request reports
Activity
Created new MR as something unrelated was breaking the build on the previous one.
@bikebilly if you could please review for corrections/suggestions I would appreciate it! @markpundsack your input welcome too.
cc @erica
@rebecca yes, it's hard to tell what's actually being shown in the gif.
-
@rebecca great post!
assigned to @erica
-
@erica Assigning to you in case this is resolved while I'm away – the title will just need to be update to whatever date you publish.
-
@bikebilly Has there been any progress with resolving the problems with deploy boards? Just wondering if I can reschedule this post yet.
assigned to @rebecca
6 categories: GitLab EE 7 image_title: '/images/blogimages/benefits-of-deploy-boards.jpg' 8 description: Here's how our built-in deploy board can tighten up your deployments. 9 cta_button_text: 'Check out our webcast, <strong>Managing the DevOps Culture Shift</strong>!' 10 cta_button_link: 'http://get.gitlab.com/managing-devops-culture-shift/' 11 --- 12 13 We released GitLab [9.0 with Deploy Boards](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#deploy-boards-eep) for environments running on Kubernetes, and followed it up with [Canary Deployments in 9.1](https://about.gitlab.com/2017/04/22/gitlab-9-1-released/#canary-deployments-eep) – now let's take a closer look at how you can use them to improve your DevOps flow. 14 15 <!-- more --> 16 17 ## 1. Get Real-Time Monitoring in One Interface 18 19 Deploy Boards allow you to watch a deployment roll out across pods and monitor the health and deployment status of each environment, all in one place. This makes it easier to spot potential problems and stop or roll back with one click. Where the Deploy Board really comes into its own is with Canary Deployments: similar to incremental rollouts, Canary Deployments aim to minimize the impact of any issues with a new version of your application, by releasing only to a small percentage of users so that you can monitor the rollout and behavior before deploying to everyone. 20 21 <iframe src="https://giphy.com/embed/13BWpAhW8VuNj2" width="480" height="270" frameBorder="0" class="giphy-embed" allowFullScreen></iframe> 4 author_twitter: 5 author_gitlab: rebecca 6 categories: GitLab EE 7 image_title: '/images/blogimages/benefits-of-deploy-boards.jpg' 8 description: Here's how our built-in deploy board can tighten up your deployments. 9 cta_button_text: 'Check out our webcast, <strong>Managing the DevOps Culture Shift</strong>!' 10 cta_button_link: 'http://get.gitlab.com/managing-devops-culture-shift/' 11 --- 12 13 We released GitLab [9.0 with Deploy Boards](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#deploy-boards-eep) for environments running on Kubernetes, and followed it up with [Canary Deployments in 9.1](https://about.gitlab.com/2017/04/22/gitlab-9-1-released/#canary-deployments-eep) – now let's take a closer look at how you can use them to improve your DevOps flow. 14 15 <!-- more --> 16 17 ## 1. Get Real-Time Monitoring in One Interface 18 19 Deploy Boards allow you to watch a deployment roll out across pods and monitor the health and deployment status of each environment, all in one place. This makes it easier to spot potential problems and stop or roll back with one click. Where the Deploy Board really comes into its own is with Canary Deployments: similar to incremental rollouts, Canary Deployments aim to minimize the impact of any issues with a new version of your application, by releasing only to a small percentage of users so that you can monitor the rollout and behavior before deploying to everyone. 8 description: Here's how our built-in deploy board can tighten up your deployments. 9 cta_button_text: 'Check out our webcast, <strong>Managing the DevOps Culture Shift</strong>!' 10 cta_button_link: 'http://get.gitlab.com/managing-devops-culture-shift/' 11 --- 12 13 We released GitLab [9.0 with Deploy Boards](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#deploy-boards-eep) for environments running on Kubernetes, and followed it up with [Canary Deployments in 9.1](https://about.gitlab.com/2017/04/22/gitlab-9-1-released/#canary-deployments-eep) – now let's take a closer look at how you can use them to improve your DevOps flow. 14 15 <!-- more --> 16 17 ## 1. Get Real-Time Monitoring in One Interface 18 19 Deploy Boards allow you to watch a deployment roll out across pods and monitor the health and deployment status of each environment, all in one place. This makes it easier to spot potential problems and stop or roll back with one click. Where the Deploy Board really comes into its own is with Canary Deployments: similar to incremental rollouts, Canary Deployments aim to minimize the impact of any issues with a new version of your application, by releasing only to a small percentage of users so that you can monitor the rollout and behavior before deploying to everyone. 20 21 <iframe src="https://giphy.com/embed/13BWpAhW8VuNj2" width="480" height="270" frameBorder="0" class="giphy-embed" allowFullScreen></iframe> 22 23 "Having everything integrated into the GitLab interface allows you real-time monitoring of deployments, so you don’t have to rely on the Kubernetes dashboard or another tool in order to see the status," says GitLab CI/CD Product Manager, [Fabio Busatto](https://about.gitlab.com/team/#bikebilly). "Also you don’t have to wait until the end of the deployment to spot problems." This is especially useful for bigger deployments, which can take up to an hour, Fabio explains. "During this hour you have an integrated interface where you can see everything, and from the Environments tab you can roll back or take other actions based on feedback you're getting from the Deploy Board." 12 13 We released GitLab [9.0 with Deploy Boards](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#deploy-boards-eep) for environments running on Kubernetes, and followed it up with [Canary Deployments in 9.1](https://about.gitlab.com/2017/04/22/gitlab-9-1-released/#canary-deployments-eep) – now let's take a closer look at how you can use them to improve your DevOps flow. 14 15 <!-- more --> 16 17 ## 1. Get Real-Time Monitoring in One Interface 18 19 Deploy Boards allow you to watch a deployment roll out across pods and monitor the health and deployment status of each environment, all in one place. This makes it easier to spot potential problems and stop or roll back with one click. Where the Deploy Board really comes into its own is with Canary Deployments: similar to incremental rollouts, Canary Deployments aim to minimize the impact of any issues with a new version of your application, by releasing only to a small percentage of users so that you can monitor the rollout and behavior before deploying to everyone. 20 21 <iframe src="https://giphy.com/embed/13BWpAhW8VuNj2" width="480" height="270" frameBorder="0" class="giphy-embed" allowFullScreen></iframe> 22 23 "Having everything integrated into the GitLab interface allows you real-time monitoring of deployments, so you don’t have to rely on the Kubernetes dashboard or another tool in order to see the status," says GitLab CI/CD Product Manager, [Fabio Busatto](https://about.gitlab.com/team/#bikebilly). "Also you don’t have to wait until the end of the deployment to spot problems." This is especially useful for bigger deployments, which can take up to an hour, Fabio explains. "During this hour you have an integrated interface where you can see everything, and from the Environments tab you can roll back or take other actions based on feedback you're getting from the Deploy Board." 24 25 ## 2. Your Entire Cycle Is Linked 26 27 Of course there are other monitoring tools out there. One of the major advantages of the built-in Deploy Board is that it's another tool in the software development process that's under one roof. Tighter integration between different stages of the process facilitates the creation of cross-references between code, tests and deployments while discussing them, making it easier to see the full context. 10 cta_button_link: 'http://get.gitlab.com/managing-devops-culture-shift/' 11 --- 12 13 We released GitLab [9.0 with Deploy Boards](https://about.gitlab.com/2017/03/22/gitlab-9-0-released/#deploy-boards-eep) for environments running on Kubernetes, and followed it up with [Canary Deployments in 9.1](https://about.gitlab.com/2017/04/22/gitlab-9-1-released/#canary-deployments-eep) – now let's take a closer look at how you can use them to improve your DevOps flow. 14 15 <!-- more --> 16 17 ## 1. Get Real-Time Monitoring in One Interface 18 19 Deploy Boards allow you to watch a deployment roll out across pods and monitor the health and deployment status of each environment, all in one place. This makes it easier to spot potential problems and stop or roll back with one click. Where the Deploy Board really comes into its own is with Canary Deployments: similar to incremental rollouts, Canary Deployments aim to minimize the impact of any issues with a new version of your application, by releasing only to a small percentage of users so that you can monitor the rollout and behavior before deploying to everyone. 20 21 <iframe src="https://giphy.com/embed/13BWpAhW8VuNj2" width="480" height="270" frameBorder="0" class="giphy-embed" allowFullScreen></iframe> 22 23 "Having everything integrated into the GitLab interface allows you real-time monitoring of deployments, so you don’t have to rely on the Kubernetes dashboard or another tool in order to see the status," says GitLab CI/CD Product Manager, [Fabio Busatto](https://about.gitlab.com/team/#bikebilly). "Also you don’t have to wait until the end of the deployment to spot problems." This is especially useful for bigger deployments, which can take up to an hour, Fabio explains. "During this hour you have an integrated interface where you can see everything, and from the Environments tab you can roll back or take other actions based on feedback you're getting from the Deploy Board." 24 25 ## 2. Your Entire Cycle Is Linked 22 23 "Having everything integrated into the GitLab interface allows you real-time monitoring of deployments, so you don’t have to rely on the Kubernetes dashboard or another tool in order to see the status," says GitLab CI/CD Product Manager, [Fabio Busatto](https://about.gitlab.com/team/#bikebilly). "Also you don’t have to wait until the end of the deployment to spot problems." This is especially useful for bigger deployments, which can take up to an hour, Fabio explains. "During this hour you have an integrated interface where you can see everything, and from the Environments tab you can roll back or take other actions based on feedback you're getting from the Deploy Board." 24 25 ## 2. Your Entire Cycle Is Linked 26 27 Of course there are other monitoring tools out there. One of the major advantages of the built-in Deploy Board is that it's another tool in the software development process that's under one roof. Tighter integration between different stages of the process facilitates the creation of cross-references between code, tests and deployments while discussing them, making it easier to see the full context. 28 29 "If you use an external tool you don’t have the link between your pipeline and your workflow," Fabio explains. "If you start the pipeline into GitLab, from compiling the code, the testing to the end of deployment, everything is related so if you have multiple deployments, you can follow the path in a very simple way." This spares you from creating the link between the information you have in GitLab and in another interface yourself. 30 31 ## 3. You Can Monitor After Deployments 32 33 Not just useful during the deployment itself, the Deploy Board can also monitor afterwards. "Say you have 10 instances of your application and you want to increase them to 20, you can see the deployment of the additional 10 in the Deploy Board," says Fabio. "This is not a new deployment started within GitLab – it's internal to Kubernetes – but you can observe the feedback in the GitLab interface." 34 35 ## 4. Complete the DevOps Workflow 36 37 Deployment represents the last stage in the software development lifecycle, and Deploy Boards together with Canary Deployments are part of streamlining the Ops segment of that workflow. In doing so, this completes a single workflow that covers all aspects of Dev and Ops, in one interface, which helps to support the shared responsibility and collaboration that DevOps practices emphasize. @rebecca @bikebilly I added my comments. It's pretty good, but there are several things that concern me.
AFAIK, there are no problems with deploy boards preventing us from publishing.
Please register or sign in to reply