{"id":1798,"date":"2020-10-02T11:15:08","date_gmt":"2020-10-02T09:15:08","guid":{"rendered":"https:\/\/blog.besharp.it\/?p=1798"},"modified":"2021-03-18T16:23:40","modified_gmt":"2021-03-18T15:23:40","slug":"gitlab-vs-aws-codepipeline-the-ultimate-battle-royal","status":"publish","type":"post","link":"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/","title":{"rendered":"GitLab VS AWS CodePipeline: the ultimate Battle Royal!"},"content":{"rendered":"\n<p><span style=\"font-weight: 400;\"><strong>GitLab<\/strong> has become a widely used DevOps tool as it packs a lot of features into a single service. It can be deployed on-premise, or you can use the SaaS version.<\/span><\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">The free tier is enough for common tasks like maintaining a codebase, running pipelines and managing project information. Amazon Web Services offers a suite of services (<strong>AWS CodeCommit, AWS CodeBuild, AWS CodePipeline<\/strong>) to implement <strong>CI\/CD<\/strong> best practices with a pay-as-you-go pricing model. <\/span><\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">It\u2019s never easy to choose the perfect set of tools to use when planning a new business or to migrate legacy applications to the cloud.&nbsp;<\/span>\n\n<span style=\"font-weight: 400;\">Fear not, dear developers: this article is going to clear things out through an ultimate Royal Battle!<\/span>\n\n<span style=\"font-weight: 400;\">Since we\u2019re talking about cloud environments, we need to find a common playfield to start the fight: for an equal challenge, we choose the <strong>AWS Well-Architected Framework<\/strong>, the framework designed by AWS to help you design maintainable, secure, resilient, efficient, and cost-effective applications and architectures<\/span><\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">Based on <a href=\"https:\/\/aws.amazon.com\/blogs\/apn\/the-5-pillars-of-the-aws-well-architected-framework\/\" target=\"_blank\" rel=\"noopener noreferrer\">5 pillars<\/a> &#8211; Operational Excellence, Security, Reliability, Performance Efficiency, and Cost Optimization &#8211; it does not involve any AWS service in particular, so it can be used as a design reference to build any service or infrastructure.<\/span><\/p>\n\n\n\n<p>Let&#8217;s welcome today&#8217;s fighters: on one side GitLab. On the other side, AWS CodePipeline is warming up!<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Rules of the game<\/h2>\n\n\n\n<p>Let\u2019s begin an hypothetical match between GitLab and AWS Codepipeline. <\/p>\n\n\n\n<p>Each pillar will be used as a round; scores will be based on the design principles of the pillar.\n<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Round 1: Operational Excellence<\/h3>\n\n\n\n<p>For this game, points will be defined based on the following principles:<\/p>\n\n\n\n<div class=\"wp-block-group\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n<ul><li>Perform operations as code<\/li><li>Make frequent, small, reversible changes<\/li><li>Refine operations procedures frequently<\/li><li>Anticipate failure<\/li><li>Learn from all operational failures<\/li><\/ul>\n\n\n\n<p>GitLab and CodePipeline can define pipelines for various tasks, build projects and deploy them using a yaml template. It is possible to define different stages and execution steps for each stage.\n<\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">We\u2019ll use <a href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab\/-\/blob\/master\/lib\/gitlab\/ci\/templates\/Python.gitlab-ci.yml\" target=\"_blank\" rel=\"noopener noreferrer\">a sample<\/a><\/span>\n\n&nbsp;<\/p>\n\n\n\n<p>GitLab at serve:<\/p>\n<\/div><\/div>\n\n\n\n<pre>image: python:latest\n\nvariables:\n  PIP_CACHE_DIR: \"$CI_PROJECT_DIR\/.cache\/pip\"\n\ntest:\n  script:\n\t- python setup.py test\n\t- pip install tox flake8  # you can also use tox\n\t- tox -e py36,flake8\n\nrun:\n  script:\n    - python setup.py bdist_wheel\n    - pip install dist\/*\n  artifacts:\n    paths:\n      - dist\/*.whl\n<\/pre>\n\n\n\n<p>And now CodePipeline turn<\/p>\n\n\n\n<pre>version: 0.2\nenv:\n\tvariables: PIP_CACHE_DIR: \"$CI_PROJECT_DIR\/.cache\/pip\"\nphases:\n\ttest:\n    \t  - python setup.py test\n    \t  - pip install tox flake8  # you can also use tox\n    \t  - tox -e py36,flake8\n\n\trun:\n    \t  - python setup.py bdist_wheel\n    \t  - pip install dist\/*\n   \t \n  artifacts:\n\tfiles:\n  \t  - dist\/*.whl\n<\/pre>\n\n\n\n<p>GitLab allows you to define the image used for building, while CodePipeline allows you to define the image in pipeline definition, not in build steps. The syntax is quite similar and very clear in both cases and the deriving flexibility is considerable.\n<\/p>\n\n\n\n<p><strong>It&#8217;s 1 &#8211; 1.<\/strong><\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">Anyway, CodePipeline allows you to <a href=\"https:\/\/docs.aws.amazon.com\/AWSCloudFormation\/latest\/UserGuide\/continuous-delivery-codepipeline-basic-walkthrough.html\" target=\"_blank\" rel=\"noopener noreferrer\">deploy entire infrastructure stacks using CloudFormation<\/a>, too. This means: Continuous Delivery for entire infrastructures!<\/span><\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">CodePipeline takes the lead. <\/span>\n\n<span style=\"font-weight: 400;\"><strong>It&#8217;s 2 &#8211; 1!<\/strong><\/span><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Round 2: Security<\/h3>\n\n\n\n<p>For this game, points will be defined based on the following principles:  <\/p>\n\n\n\n<ul><li>Enable traceability<\/li><li>Apply security at all layers<\/li><li>Automate security best practices<\/li><li>Protect data in transit and at rest<\/li><li>Keep not authorized people away from data<\/li><li>Prepare for security events<\/li><\/ul>\n\n\n\n<p>GitLab offers authentication mechanisms that can leverage other IdP and federations like Active Directory and SAML and you can take advantage of centralized user management if you plan your configuration carefully. \nAnyway, if you also need SAML SSO for groups, you have to opt for the paid tier. <\/p>\n\n\n\n<p>AWS CodePipeline uses the same authentication and authorization layer of AWS: it features Active Directory, SAML, and&#8230; SAML SSO for groups. Given that not every authentication feature is available on GitLab\u2019s free tier, AWS takes the lead. <\/p>\n\n\n\n<p>Let&#8217;s speak about traceability and keeping people away from data: the audit log is available only on GitLab paid plans while CloudTrail is included and configured for every AWS service in your account. \n\n<\/p>\n\n\n\n<p>AWS scores: <strong>it&#8217;s 3 &#8211; 1.<\/strong><\/p>\n\n\n\n<p>The hardest part to deal with for GitLab comes with <span style=\"font-weight: 400;\"><a href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/-\/issues\/25351\" target=\"_blank\" rel=\"noopener noreferrer\">open issues and discussions on GitLab about runner security<\/a> and about <a href=\"https:\/\/gitlab.com\/gitlab-org\/gitlab-runner\/-\/issues\/3232\" target=\"_blank\" rel=\"noopener noreferrer\">data encryption at rest (cache and artifacts).<\/a><\/span><\/p>\n\n\n\n<p>If you need to interact with AWS services to deploy your application, you\u2019ll need to give the runner-manager a role with the right permissions. If you need to deploy multiple applications that run on different services, you\u2019ll need to provide additional permissions to your runner or to spawn multiple runners, giving them the minimum access required (note that, by doing so, the number of the resources will increase, along with costs)\n<\/p>\n\n\n\n<p>This round is won by AWS services, as every service provides encryption at rest and in transit for data. Also, IAM roles allow you to avoid using tokens, access keys, and other vulnerable authentication mechanisms for services. <\/p>\n\n\n\n<p><strong>CodePipeline scores again and it&#8217;s 4 &#8211; 1.<\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Round 3: Reliability<\/h3>\n\n\n\n<p>For this game, points will be defined based on the following principles:  <\/p>\n\n\n\n<ul><li>Automatically recover from failure<\/li><li>Test recovery procedures<\/li><li>Scale horizontally to increase aggregate workload availability<\/li><li>Stop guessing capacity<\/li><li>Automatic management of changes<\/li><\/ul>\n\n\n\n<p><em>Before diving into this round, it is necessary to keep in mind that in this case, <span style=\"font-weight: 400;\">a lot depends on your expectations when implementing your build environment in both services.&nbsp;<\/span><\/em><\/p>\n\n\n\n<p>Both GitLab and AWS CodePipeline are characterized by horizontal scalability, they both automate changes, and don\u2019t require any intervention for advanced capacity planning (except for using a single big on-premise runner for GitLab).<\/p>\n\n\n\n<p><strong>They both score: it&#8217;s a 5 &#8211; 2.<\/strong><\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">In terms of flexibility in scaling, GitLab implements a plugin system, and you can also use custom executors. Definitely an extra gear: <strong>nice shot, GitLab: 5 &#8211; 3.<\/strong><\/span><\/p>\n\n\n\n<p>AWS CodePipeline allows you to use a multi-az deployment. This ensures, for example, your build can run on the other 2 availability zones in case of failure in eu-west-1-a.\n<\/p>\n\n\n\n<p>Note that if you are using GitLab\u2019s EC2 Autoscaling plugin, multi-az deployment is not implemented. Here\u2019s the sample config taken from <a href=\"https:\/\/docs.gitlab.com\/runner\/configuration\/runner_autoscale_aws\/\" target=\"_blank\" rel=\"noopener noreferrer\">this sample.<\/a><\/p>\n\n\n\n<pre>[runners.machine]\n    IdleCount = 1\n    IdleTime = 1800\n    MaxBuilds = 10\n    MachineDriver = \"amazonec2\"\n    MachineName = \"gitlab-docker-machine-%s\"\n    MachineOptions = [\n      \"amazonec2-access-key=XXXX\",\n      \"amazonec2-secret-key=XXXX\",\n      \"amazonec2-region=us-central-1\",\n      \"amazonec2-vpc-id=vpc-xxxxx\",\n      <b>\"amazonec2-subnet-id=subnet-xxxxx\",<\/b>\n      <b>\"amazonec2-zone=x\",<\/b>\n      \"amazonec2-use-private-address=true\",\n      \"amazonec2-tags=runner-manager-name,gitlab-aws-autoscaler,gitlab,true,gitlab-runner-autoscale,true\",\n      \"amazonec2-security-group=xxxxx\",\n      \"amazonec2-instance-type=m4.2xlarge\",\n    ]\n<\/pre>\n\n\n\n<p><span style=\"font-weight: 400;\">As you can see, it is possible to set a single subnet only and a single Availability Zone. With this configuration, your build will fail in case of failure in the chosen zone. AWS gets the point. <strong>It&#8217;s 6 &#8211; 3.<\/strong><\/span><\/p>\n\n\n\n<p>Note that is possible to implement a custom executor to increase reliability, but you\u2019ll need to develop it and test it on your own with a considerable waste of time.\n<\/p>\n\n\n\n<p>Let\u2019s continue with the two last two rounds. <\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Round 4: Performance Efficiency<\/h3>\n\n\n\n<p>For this game, points will be defined based on the following principles:  <\/p>\n\n\n\n<ul><li>Democratizing advanced technologies<\/li><li>Going global in minutes<\/li><li>Using serverless architectures<\/li><li>Experimenting more often<\/li><li>Conoscere e tenere in considerazione l\u2019infrastruttura sottostante (<a href=\"https:\/\/dzone.com\/articles\/mechanical-sympathy\" target=\"_blank\" rel=\"noreferrer noopener\">qualche specifica qui<\/a>).<\/li><\/ul>\n\n\n\n<p>Even if GitLab and CodePipeline have a lot in common, there\u2019s a little more flexibility on the GitLab side, as it supports a lot of different deployments and configurations. <\/p>\n\n\n\n<p>One point to GitLab: <strong>6 &#8211; 4.<\/strong><\/p>\n\n\n\n<p>On the other side, CodePipeline offers better support for serverless builds, in comparison with the limited GitLab support for some serverless approaches. For example, you can\u2019t use Docker in Docker leveraging on the same Docker socket on the fargate custom executor. <\/p>\n\n\n\n<p>Sembra che su questo argomento ci sia un pareggio! Entrambi i servizi guadagnano un punto: <strong>7 &#8211; 4 per CodePipeline.<\/strong><\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Round 5: Cost Optimization<\/h3>\n\n\n\n<p>For this game, points will be defined based on the following principles:  <\/p>\n\n\n\n<ul><li>Implement cloud financial management<\/li><li>Adopt a consumption model<\/li><li>Measure overall efficiency<\/li><li><span style=\"font-weight: 400;\">Stop spending money on undifferentiated heavy lifting<\/span><\/li><li>Analyze and attribute expenditure<\/li><\/ul>\n\n\n\n<p><span style=\"font-weight: 400;\">Let&#8217;s analyze pricing models: <\/span>\n\n<span style=\"font-weight: 400;\">GitLab is based on a per-user pricing model, while AWS users are free.&nbsp;<\/span><span style=\"font-weight: 400;\"><a href=\"https:\/\/aws.amazon.com\/codebuild\/pricing\/\" target=\"_blank\" rel=\"noopener noreferrer\">CodeBuild minutes are priced based on the time you use resources<\/a> for a build. If you manage to use a general1.small (2 cores and 3gb of RAM), you\u2019ll end up spending 5 dollars for 1.000 minutes.&nbsp;<\/span><\/p>\n\n\n\n<p>With GitLab shared runners, instead, you can purchase 1.000 minutes of shared runners for 10$ (the first 2.000 minutes are free).<\/p>\n\n\n\n<p>If you don\u2019t want to use GitLab\u2019s shared runners, you can use AWS Auto Scaling for builds, but keep in mind that you\u2019ll need an EC2 instance for the runner manager and other instances to allow your builds to scale. Other possibilities are purchasing reserved instances or using spot instances if your business allows you to do it.\n<\/p>\n\n\n\n<p>For this round, no doubts for the winner: AWS CodePipeline gets the last point, as it offers a more pre-built and out-of-the-box and integrated solution. \n<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Podium and conclusions<\/h2>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"576\" src=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/2009666-rocky_iv_original_k-1024x576.png\" alt=\"AWS CodePipeline wins over GitLab\" class=\"wp-image-1820\" srcset=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/2009666-rocky_iv_original_k-1024x576.png 1024w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/2009666-rocky_iv_original_k-400x225.png 400w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/2009666-rocky_iv_original_k-768x432.png 768w, https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/2009666-rocky_iv_original_k-1536x864.png 1536w\" sizes=\"(max-width: 1024px) 100vw, 1024px\" \/><\/figure><\/div>\n\n\n\n<p>Our friendly fight between 2 of the most widely adopted services has ended. With a score of 8 &#8211; 4, we are welcoming <strong>AWS CodePipeline on the top step of the podium!<\/strong><\/p>\n\n\n\n<p>Will it keep its supremacy?<\/p>\n\n\n\n<p>Don\u2019t get us wrong: GitLab remains an excellent service with great features for teams and top user experience for developers and under specific conditions, it is still the best choice, according to specific use cases.\n\n\n<\/p>\n\n\n\n<p>In some other cases, choosing isn&#8217;t a good idea at all&#8230; Depending on the needs, mixing both of the services can be a winning choice&#8230; but this is a plain and simple spoiler for the next series of articles&#8230; \ud83d\ude42<\/p>\n\n\n\n<p><span style=\"font-weight: 400;\">Keep warm for the next fight. Till then, code secure and see you in 14 days on <strong>#Proud2beCloud<\/strong>!<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>GitLab has become a widely used DevOps tool as it packs a lot of features into a single service. It [&hellip;]<\/p>\n","protected":false},"author":13,"featured_media":1791,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[242],"tags":[276,292,367,294,286,365],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v21.9.1 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>GitLab VS AWS CodePipeline: the ultimate Battle Royal! - Proud2beCloud Blog<\/title>\n<meta name=\"description\" content=\"It\u2019s never easy to choose the perfect tool. But fear not, dear developers: this article is going to clear things out!\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"GitLab VS AWS CodePipeline: the ultimate Battle Royal!\" \/>\n<meta property=\"og:description\" content=\"It\u2019s never easy to choose the perfect tool. But fear not, dear developers: this article is going to clear things out!\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/\" \/>\n<meta property=\"og:site_name\" content=\"Proud2beCloud Blog\" \/>\n<meta property=\"article:published_time\" content=\"2020-10-02T09:15:08+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-03-18T15:23:40+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/facebook-link-image.png\" \/>\n<meta name=\"author\" content=\"Damiano Giorgi\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"GitLab VS AWS CodePipeline: the ultimate Battle Royal!\" \/>\n<meta name=\"twitter:description\" content=\"It\u2019s never easy to choose the perfect tool. But fear not, dear developers: this article is going to clear things out!\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/twitter-gitalb-vs-code.png\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Damiano Giorgi\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/\",\"url\":\"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/\",\"name\":\"GitLab VS AWS CodePipeline: the ultimate Battle Royal! - Proud2beCloud Blog\",\"isPartOf\":{\"@id\":\"https:\/\/blog.besharp.it\/#website\"},\"datePublished\":\"2020-10-02T09:15:08+00:00\",\"dateModified\":\"2021-03-18T15:23:40+00:00\",\"author\":{\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/a9195473e4a658b45cb12d3df3fdf293\"},\"description\":\"It\u2019s never easy to choose the perfect tool. But fear not, dear developers: this article is going to clear things out!\",\"breadcrumb\":{\"@id\":\"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blog.besharp.it\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"GitLab VS AWS CodePipeline: the ultimate Battle Royal!\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blog.besharp.it\/#website\",\"url\":\"https:\/\/blog.besharp.it\/\",\"name\":\"Proud2beCloud Blog\",\"description\":\"il blog di beSharp\",\"alternateName\":\"Proud2beCloud Blog\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blog.besharp.it\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/a9195473e4a658b45cb12d3df3fdf293\",\"name\":\"Damiano Giorgi\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/9a20b8c97250d4fb49857192f7e4bedf?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/9a20b8c97250d4fb49857192f7e4bedf?s=96&d=mm&r=g\",\"caption\":\"Damiano Giorgi\"},\"description\":\"Ex sistemista on-prem, pigro e incline all'automazione di task noiosi. Alla ricerca costante di novit\u00e0 tecnologiche e quindi passato al cloud per trovare nuovi stimoli. L'unico hardware a cui mi dedico ora \u00e8 quello del mio basso; se non mi trovate in ufficio o in sala prove provate al pub o in qualche aeroporto!\",\"url\":\"https:\/\/blog.besharp.it\/author\/damiano-giorgi\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"GitLab VS AWS CodePipeline: the ultimate Battle Royal! - Proud2beCloud Blog","description":"It\u2019s never easy to choose the perfect tool. But fear not, dear developers: this article is going to clear things out!","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/","og_locale":"en_US","og_type":"article","og_title":"GitLab VS AWS CodePipeline: the ultimate Battle Royal!","og_description":"It\u2019s never easy to choose the perfect tool. But fear not, dear developers: this article is going to clear things out!","og_url":"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/","og_site_name":"Proud2beCloud Blog","article_published_time":"2020-10-02T09:15:08+00:00","article_modified_time":"2021-03-18T15:23:40+00:00","og_image":[{"url":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/facebook-link-image.png"}],"author":"Damiano Giorgi","twitter_card":"summary_large_image","twitter_title":"GitLab VS AWS CodePipeline: the ultimate Battle Royal!","twitter_description":"It\u2019s never easy to choose the perfect tool. But fear not, dear developers: this article is going to clear things out!","twitter_image":"https:\/\/blog.besharp.it\/wp-content\/uploads\/2020\/10\/twitter-gitalb-vs-code.png","twitter_misc":{"Written by":"Damiano Giorgi","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/","url":"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/","name":"GitLab VS AWS CodePipeline: the ultimate Battle Royal! - Proud2beCloud Blog","isPartOf":{"@id":"https:\/\/blog.besharp.it\/#website"},"datePublished":"2020-10-02T09:15:08+00:00","dateModified":"2021-03-18T15:23:40+00:00","author":{"@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/a9195473e4a658b45cb12d3df3fdf293"},"description":"It\u2019s never easy to choose the perfect tool. But fear not, dear developers: this article is going to clear things out!","breadcrumb":{"@id":"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/blog.besharp.it\/gitlab-vs-aws-codepipeline-the-ultimate-battle-royal\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blog.besharp.it\/"},{"@type":"ListItem","position":2,"name":"GitLab VS AWS CodePipeline: the ultimate Battle Royal!"}]},{"@type":"WebSite","@id":"https:\/\/blog.besharp.it\/#website","url":"https:\/\/blog.besharp.it\/","name":"Proud2beCloud Blog","description":"il blog di beSharp","alternateName":"Proud2beCloud Blog","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blog.besharp.it\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/a9195473e4a658b45cb12d3df3fdf293","name":"Damiano Giorgi","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blog.besharp.it\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/9a20b8c97250d4fb49857192f7e4bedf?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/9a20b8c97250d4fb49857192f7e4bedf?s=96&d=mm&r=g","caption":"Damiano Giorgi"},"description":"Ex sistemista on-prem, pigro e incline all'automazione di task noiosi. Alla ricerca costante di novit\u00e0 tecnologiche e quindi passato al cloud per trovare nuovi stimoli. L'unico hardware a cui mi dedico ora \u00e8 quello del mio basso; se non mi trovate in ufficio o in sala prove provate al pub o in qualche aeroporto!","url":"https:\/\/blog.besharp.it\/author\/damiano-giorgi\/"}]}},"_links":{"self":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/1798"}],"collection":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/comments?post=1798"}],"version-history":[{"count":0,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/posts\/1798\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media\/1791"}],"wp:attachment":[{"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/media?parent=1798"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/categories?post=1798"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.besharp.it\/wp-json\/wp\/v2\/tags?post=1798"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}