GITS Class #16: CI/CD (Continuous Integration & Continuous Deployment) with GitLab Runner

Jul 8, 20190 likes698 views

Pada Juli 2019, berlangsung GITS Class #16, workshop gratis dan terbuka untuk umum, di kantor GITS Indonesia. Farhan (DevOps di GITS Indonesia) membawakan materi tentang CI/CD menggunakan GitLab Runner. Jangan sampai ketinggalan! Follow akun GITS Indonesia untuk mendapatkan info terkait event seru selanjutnya! Instagram: @gitsindonesia Twitter: @gitsindonesia Facebook: GITS Indonesia Medium: GITS Apps Insight YouTube: GITS Indonesia LinkedIn: GITS Indonesia Website: https://gits.id/

CI/CD
Continuous Integration &
Continuous Development

Self Introduction
Farhan Naufal
Ghani
Padalarang, Kab.
Bandung Barat
DevOps at GITS
Indonesia
Let’s know about me

What is CI ?
● Continuous Integration in Indonesia means
● “Integrate” your code into automated process continuously

What is CD ?
Its can be ....
Continuous Delivery
-> Give the result to User or Anyone?
Continuous Deployment
-> Run my apps and share it
I call it ...
Continuous
Development

What is Beneﬁt of CI/CD ?
Fast
Development
and
Feedbacks
Detect Issue
And
Fix it early
Minimize
Human Error
from nevercode.io Monitoring

Gitlab CI/CD
● “Continuous Integration is
built-in to GitLab”
● Fully integrated with GitLab
https://about.gitlab.com/product/continuous-integration/

What is Gitlab Runner?
● Agent Gitlab CI installed on PC/Laptop or Server
● Container for run your CI
● Written in GO
● Conﬁguration CI using .gitlab-ci.yml with YAML
You can see at : https://docs.gitlab.com/ee/ci/yaml/

Why Gitlab Runner?
● Multi-platform: Linux, OSX, Windows, Docker and etc ..
● Parallel builds
● Realtime logging
● Container Registry

Before you begin
1. Create Repository and Push your code to repository or you already have
one
2. Deploy your Apps (Continuous Deployment) : Web Application or API
3. Create Step Pipeline

Before you begin
4. Create Step Procedure based on Pipeline you build
Example Build in VueJS:
$ npm install
$ npm run build
Example Test in VueJS:
$ npm run test:unit

Example Gitlab CI/CD using VueJS
● Using :
○ Linux Ubuntu 18.04 (Production)
○ Windows (Local Laptop)
● Web Server :
○ NGINX (Production)
○ XAMPP Apache (Local Laptop)
● Depedency :
○ Nodejs ver 10.X.X
Production URL :
https://gits-class.farhan.id
Gitlab Runner Labs :
http://bit.ly/gits-class-runner-labs
Repository :
https://gitlab.com/gits-class-15

Best Practice
● Android — CI / CD Getting Started
http://bit.ly/cicd-android
● CI/CD di iOS Menggunakan GitLab Runner
http://bit.ly/cicd-ios
● Docker Laravel NGINX w Gitlab CI/CD
http://bit.ly/cicd-docker-laravel

Production URL :
https://gits-class.farhan.id
Gitlab Runner Labs :
http://bit.ly/gits-class-runner-labs
Repository :
https://gitlab.com/gits-class-15

Thank You
Don’t forget to give us feedbacks
http://bit.ly/GITSClass16

This document provides an introduction to Gitlab CI and continuous integration/continuous delivery (CI/CD) workflows. It discusses DevOps practices and the benefits of Gitlab CI. It then covers how to set up Gitlab runners, write a basic Gitlab CI configuration file, define jobs, stages, variables and environments. The document demonstrates concepts like Docker integration, artifacts, auto and manual deployments, and stopping deployments. It concludes with a live demo of a Gitlab CI configuration.

Devops Porto - CI/CD at GitlabFilipa Lacerda

The document discusses GitLab CI/CD, an overview of the types of pipelines in GitLab including how they are defined and can group jobs. It also mentions manual actions, multi-project pipeline graphs, and security on protected branches. Additional topics covered include review apps and environments, application performance monitoring, next steps such as moving from dev to devops, how everyone can contribute to GitLab, and current job openings.

Continuous Integration/Deployment with Gitlab CIDavid Hahn

This document discusses continuous integration/deployment with Gitlab CI. It provides an introduction and overview of continuous integration, continuous delivery, and deployment. It then discusses Gitlab and Gitlab CI in more detail, including stages and pipelines, the UI, runners, using CI as code, and examples for Node.js + React, Java + Angular, and Electron applications. The sources section lists links and image sources for additional information.

Gitlab CI/CDJEMLI Fathi

Gitlab CI/CD provides continuous integration and continuous delivery capabilities. It allows automating the building, testing, and deployment of code changes. At Proxym, Gitlab is used to host Git repositories and manage the complete DevOps lifecycle including CI/CD. It integrates with other tools and uses multiple runners to test code changes and deliver new features to customers quickly in an automated way.

What's New for GitLab CI/CD February 2020Noa Harel

The document summarizes new features and enhancements to GitLab's CI/CD capabilities between November 2019 and January 2020. Key updates include associating milestones with releases, adding an environments dashboard to pipelines, enabling squash and merge for merge trains, and collecting evidence for releases. Planned highlights for February 2020 focus on package management, release management, and automated testing capabilities.

Using GitLab CIColCh

Gitlab ci-cdDan MAGIER

This document discusses GitLab Continuous Integration (GitLab CI/CD). It defines continuous integration, continuous delivery, and continuous deployment. It explains that GitLab CI/CD uses pipelines made up of stages and jobs to test, build, and deploy code. Pipelines are configured using a YAML file. Jobs run on GitLab runners, which can execute jobs locally or using Docker. Benefits of GitLab CI/CD include integrated pipelines, Docker/Kubernetes integration, and not requiring plugins. The downside is that it is only available within GitLab.

Git Lab IntroductionKrunal Doshi

CI with Gitlab & DockerJoerg Henning

This document discusses using GitLab CI with Docker containers. It describes how to set up a GitLab Runner as a Docker container to execute jobs within Docker containers. The GitLab Runner is configured to use the Docker executor to pull custom images, link dependent services, and cache artifacts between jobs. Docker volumes and environment variables can also be configured for the Runner container.

GitLab for CI/CD processHYS Enterprise

This document provides an overview of using GitLab for continuous integration and continuous delivery (CI/CD) processes. It begins with definitions of CI, CD, and when they should be configured. It then discusses GitLab's capabilities for the DevOps lifecycle and its advantages as a single application for collaboration across teams. The document outlines basic CI/CD concepts in GitLab like the YAML configuration file, pipelines, jobs, stages, and runners. It concludes with suggestions for real-life project settings like defining stages, variables, templates, environments, dependencies, and examples of build, deployment, and integration jobs.

GitLab.pptxLeoulZewelde1

This document provides an overview of GitLab and discusses implementing GitLab within the Commercial Bank of Ethiopia (CBE). It describes GitLab as a self-hosted Git repository management system that allows users to privately manage code repositories. The document outlines key GitLab features like repository creation, user management, access controls, and integration with Git workflows. It recommends a single server GitLab architecture for CBE based on its reference architectures. The proposed CBE implementation would involve deploying a GitLab server authenticated via Active Directory, with an optional GitLab runner server, and various CBE teams using it for source code management, infrastructure as code, and change tracking.

Introducing GitLabTaisuke Inoue

The document compares features of GitHub and GitLab version control software. It notes that both support code repositories, issue tracking, pull requests, and project web pages. Additionally, it states that GitLab offers integrated continuous integration and container registry features. The document promotes GitLab as having CI integrated directly with the code repository, hassle-free pipeline creation, a seamless workflow, an open source business model, rapid growth, and complete transparency.

GitHub Actions in actionOleksii Holub

GitHub Actions is an automation platform for GitHub repositories that allows users to build workflows to automate software tasks. It was introduced in 2019 and is based on Azure Pipelines. Workflows are configured using YAML files and can be triggered by events like push commits, pull requests, or scheduled times. Actions, which are reusable code components, can be used in workflows and are sourced from the GitHub marketplace or created by users. GitHub Actions is free for public repositories and offers paid plans for private repositories.

Introducing GitLab (June 2018)Noa Harel

This document provides an overview and agenda for introducing GitLab tools. It discusses trends in modern development like increased use of open source tools and continuous integration/deployment. GitLab is presented as a one platform solution that provides version control, issue tracking, code review, CI/CD pipelines, and other DevOps tools. Key benefits of GitLab like open source contributions and frequent releases are outlined. Upcoming features in GitLab 11 like CI pipelines in the web IDE and license management are previewed. The presentation concludes with a Q&A and information on how to get a GitLab cheat sheet.

Jenkins vs GitLab CICEE-SEC(R)

This document compares GitLab CI and Jenkins for continuous integration. It discusses how GitLab CI is integrated directly into GitLab while Jenkins is a separate product. It also covers differences in programming languages used, configuration approaches, and extensibility through plugins. The document then demonstrates how to set up a sample CI/CD pipeline in GitLab CI to package and deploy code and websites for different environments.

CICD Pipeline Using Github ActionsKumar Shìvam

This document discusses using GitHub Actions for continuous integration and continuous delivery (CI/CD) workflows. It begins with an introduction and agenda, then discusses the basics of GitHub Actions including what problems it solves and why CI/CD is important. Several key aspects of GitHub Actions are then covered at a high level, including how it compares to AWS CodePipeline, examples of GitHub workflows, and the core components of actions, artifacts, events, jobs, runners, steps, and workflows. The document concludes with an overview of creating a GitHub Actions workflow and exploring further possibilities.

Introduction to Gitlab | Gitlab 101 | Training SessionAnwarul Islam

Default GitLab CI Pipeline - Auto DevOpsRajith Bhanuka Mahanama

This document discusses continuous integration (CI) pipelines in GitLab, including standard GitLab CI and Auto DevOps. Standard GitLab CI requires configuring pipelines, jobs, clusters, and environments manually, while Auto DevOps automatically generates CI/CD pipelines based on a project's code and requires minimal configuration. Auto DevOps provides features like automatic building, testing, code quality checks, security testing, and deployment. It utilizes Docker, Kubernetes, Helm, and GitLab runners to containerize applications and deploy them. The document demonstrates how to enable and configure Auto DevOps on GitLab, including setting up a Kubernetes cluster to deploy apps to production and staging environments.

Git branching strategiesjstack

The document discusses various Git branching strategies, including: - Common concepts like branches, merges, and pull requests - Popular workflows like GitHub Flow and branching per platform/release - A case study of Telenet's workflow of using long-running release branches merged from master for testing before production deployment - Best practices like using pull requests for code reviews, keeping long-running branches stable, and ensuring features are fully tested before being merged.

Git basicsGHARSALLAH Mohamed

Git is a distributed version control system that records changes to files over time. It allows multiple developers to work together and tracks the version history. The document outlines the basic concepts and commands of Git including repositories, commits, branches, merging, cloning, pulling and pushing changes between a local and remote repository. Examples are provided to demonstrate how to initialize a local repository, add and commit changes, switch branches, and push updates to a remote server.

Introducing GitLab (September 2018)Noa Harel

The document discusses GitLab, an open source DevOps platform. It provides an overview of GitLab's features including version control, issue tracking, code review, continuous integration/delivery, security tools, and more. Recent landmarks for GitLab include being used by over 100,000 organizations and having over 2,000 contributors. The document promotes GitLab as a one-stop shop that allows development from idea to production.

Introduction to GitHub ActionsBo-Yi Wu

CI/CD with Github ActionsMd. Minhazul Haque

This document discusses setting up a CI/CD pipeline using GitHub Actions. It begins with an introduction to CI/CD pipelines and their importance. It then provides an overview of GitHub Actions and how they can be used to automate builds, tests, releases and deployments. The document demonstrates a sample GitHub Actions workflow file and explains its key components like jobs, steps and actions. It also covers topics like workflow events, jobs and steps/actions that can be used in GitHub Actions.

Git & GitLabGaurav Wable

Git training v10Skander Hamza

Introduction to GItlab CICD Presentation.pptxKnoldus Inc.

Webinar - Unbox GitLab CI/CD Annie Huang

GitLab CI/CD is a built-in continuous integration and delivery tool in GitLab. It allows for automated testing, building, and deploying of applications. It supports various languages and tools through configuration files. Pipelines can be triggered on code pushes or manually to run tests and deploy code. The tool aims to speed up development workflows through automation while providing visibility into builds.

CI-CD WITH GITLAB WORKFLOWAddWeb Solution Pvt. Ltd.

This document describes a GitLab CI/CD workflow using GitLab, Docker, GitLab Runner, and Ansible. Developers push code to a GitLab repo, which triggers a GitLab Runner job to build a Docker image. Ansible is then used to provision servers based on the environment. The benefits of using Ansible include managing everything from one playbook to clone code, build containers, deploy applications, and more. Examples of using shell scripts versus Ansible playbooks are provided.

When Automation Keeps Your T-shirt CleanDevOps Indonesia

This document summarizes a presentation given at DevOpsDays Jakarta 2020 about automation and CI/CD. It defines automation and discusses why it is needed, especially in DevOps. Common types of automation for DevOps like infrastructure provisioning, CI/CD, and testing are covered. The presentation recommends Jenkins as a free and customizable CI/CD tool and describes how to implement a CI/CD pipeline using Jenkinsfile. It also discusses dockerizing the build process for flexibility and concludes by thanking the audience and sponsors.

Introduction to DevOpsAhmed Adel

My presentation (Introduction to DevOps) presented to AlQemam company during our technical sessions. Session main points: ♦ What is DevOps, its history and timeline. ♦ DevOps VS Traditional Silos. ♦ DevOps Culture: The culture of collaboration between Dev and Ops. ♦ DevOps Practices: The practices which support the goals of DevOps culture. ♦ DevOps Tools: The tools that help implement DevOps practices (Examples of tools used for each DevOps Practice). ♦ DevOps and the Cloud: The close relationship between DevOps and the cloud

More Related Content

What's hot (20)

CI with Gitlab & DockerJoerg Henning

GitLab for CI/CD processHYS Enterprise

GitLab.pptxLeoulZewelde1

Introducing GitLabTaisuke Inoue

GitHub Actions in actionOleksii Holub

Introducing GitLab (June 2018)Noa Harel

Jenkins vs GitLab CICEE-SEC(R)

CICD Pipeline Using Github ActionsKumar Shìvam

Introduction to Gitlab | Gitlab 101 | Training SessionAnwarul Islam

Default GitLab CI Pipeline - Auto DevOpsRajith Bhanuka Mahanama

Git branching strategiesjstack

Git basicsGHARSALLAH Mohamed

Introducing GitLab (September 2018)Noa Harel

Introduction to GitHub ActionsBo-Yi Wu

CI/CD with Github ActionsMd. Minhazul Haque

Git & GitLabGaurav Wable

Git training v10Skander Hamza

Introduction to GItlab CICD Presentation.pptxKnoldus Inc.

Webinar - Unbox GitLab CI/CD Annie Huang

CI-CD WITH GITLAB WORKFLOWAddWeb Solution Pvt. Ltd.

CI with Gitlab & DockerJoerg Henning

GitLab for CI/CD processHYS Enterprise

GitLab.pptxLeoulZewelde1

Introducing GitLabTaisuke Inoue

GitHub Actions in actionOleksii Holub

Introducing GitLab (June 2018)Noa Harel

Jenkins vs GitLab CICEE-SEC(R)

CICD Pipeline Using Github ActionsKumar Shìvam

Introduction to Gitlab | Gitlab 101 | Training SessionAnwarul Islam

Default GitLab CI Pipeline - Auto DevOpsRajith Bhanuka Mahanama

Git branching strategiesjstack

Git basicsGHARSALLAH Mohamed

Introducing GitLab (September 2018)Noa Harel

Introduction to GitHub ActionsBo-Yi Wu

CI/CD with Github ActionsMd. Minhazul Haque

Git & GitLabGaurav Wable

Git training v10Skander Hamza

Introduction to GItlab CICD Presentation.pptxKnoldus Inc.

Webinar - Unbox GitLab CI/CD Annie Huang

CI-CD WITH GITLAB WORKFLOWAddWeb Solution Pvt. Ltd.

Similar to GITS Class #16: CI/CD (Continuous Integration & Continuous Deployment) with GitLab Runner (20)

When Automation Keeps Your T-shirt CleanDevOps Indonesia

Introduction to DevOpsAhmed Adel

Transition from CI to CDNanjekye Joannah

During this talk, I’ll start by introducing continuous delivery and I will distinguish Continuous Integration from Continuous Delivery, why teams need to do continuous delivery and what is required for teams to do it. I’ll then present the principles and practices involved in continuous delivery along with the benefits in general and on a personal basis from my operations. Finally, I will wrap the talk up with a demo using one of the projects where I have used Continuous Delivery.

Deploying Mule Applications with Jenkins, Azure and BitBucket (1).pptxPankaj Goyal

The document outlines steps for deploying Mule applications with Jenkins, Azure and BitBucket using continuous integration and continuous delivery practices. It begins with an agenda and introductions. It then discusses software deployment, continuous integration, continuous delivery vs deployment, the tools Jenkins, Jenkins Pipelines and why CI/CD is important. Finally it demonstrates deploying applications with each tool - with Jenkins and Git, Azure DevOps and BitBucket - through configuring the tools, pipelines and deploying applications.

CI CD Jenkins for Swift DeploymentBintang Thunder

This document discusses continuous integration and continuous delivery (CI/CD) for app development at Mandiri. It begins with an overview of CI/CD, including elements like source control, building, testing and deploying. It then proposes a solution using Jenkins and Fastlane to automate building iOS and Android apps from code commits through testing to production deployment. The document demonstrates this process and discusses advantages like reduced errors and faster updates.

Continuous integration with git labMahyuddin Mahyuddin

This document discusses continuous integration using Gitlab-CI. It defines continuous integration as integrating work frequently, usually daily, by members of a software development team. It introduces Gitlab-CI as the continuous integration and continuous delivery tool integrated within Gitlab for testing, building, and deploying source code. Key features of Gitlab-CI highlighted include being multi-platform, multi-language, stable, supporting parallel builds, real-time logging, versioned tests, pipelines, autoscaling, and build artifacts. Best practices for configuration via .gitlab-ci.yml files are also outlined.

Simple ci cd with strider cdAmandeep Singh

This document discusses CI/CD pipelines and how StriderCD can be used to implement one. It begins with an overview of traditional code deployment processes versus CI/CD. CI/CD aims to automate testing and deployment through continuous integration and continuous deployment. The document then discusses why CI/CD is important for improving quality, keeping the build fast, and enabling visibility. It presents StriderCD as an open source CI/CD platform like Jenkins and Travis but easier to use. The rest of the document covers implementing a CI/CD pipeline with StriderCD, its features like integration with version control systems and notifications, and concludes that CI/CD is essential and StriderCD is a good option.

Beyond QAgilforcada

The document discusses improving quality assurance (QA) practices for software development. It recommends using tools like flake8, continuous integration (CI), and plone.recipe.codeanalysis to automate QA checks. Automating as many checks as possible through tools reduces manual effort and ensures quality is considered from the first commit. The goal is to enable refactoring and make it easier for newcomers to contribute, with the overall takeaway being that quality should be part of every development action through rigorous but not overly burdensome automated testing and linting.

Continuous integration for Ruby on RailsDavid Paluy

Continuous integration (CI) is a development practice that requires developers to integrate code into a shared repository multiple times per day. Each check-in is automatically built and tested to find problems early. For Ruby on Rails projects, CI can generate code coverage reports, perform static code analysis, and document APIs. CI builds confidence by continuously integrating and testing code changes. Continuous deployment further automates software delivery through continuous integration.

OpenTuesday: Aktuelle Standards der agilen SoftwareentwicklungDigicomp Academy AG

Dieses OpenTuesday-Referat von Michael Palotas ging gezielt auf die sogenannten «Agile Engineering Practices» ein und zeigte anhand praktischer Beispiele auf, wie die Anwendung dieser Praktiken als Enabler für agile Softwareentwicklung fungieren. Es gibt wohl kaum eine Firma, bei der agile Softwareentwicklung kein Thema ist. Viele Organisationen haben sich schon auf den Weg begeben, agil zu werden. Im ersten Schritt bedeutet dies in der Regel, die Prozesse auf eine agile Methodik wie z.B. SCRUM zu ändern. Auf der Strecke bleiben jedoch oft die (agilen) Entwicklungs-, Test- und Liefermethoden wie Continuous Integration, Test-Automatisierung, Test Driven Development, Pair Programming etc., die eine agile Vorgehensweise erst richtig ermöglichen.

Lets talk about CI CD Pipeline in Agile Poonam Panday

Continuous integration is a practice where developers integrate code into a shared repository frequently, such as daily, and automated builds and tests are used to detect errors. Continuous deployment is an approach where teams release software in short cycles to ensure it can be reliably released at any time. The principles of continuous integration and continuous deployment (CI/CD) include automating all build, test and deployment processes; keeping everything in version control; committing code frequently; and not merging broken code. CI/CD aims to release software faster through automation and frequent integration and deployment.

How can Enterprises benefit from GitOps.pdfOpsTree solutions

Implementing a template-based approach in GitOps significantly enhances developer experience and productivity. This strategy streamlines infrastructure and application configuration, reducing errors and promoting consistency. Templates encapsulate best practices and coding standards, accelerating onboarding and ensuring conformity across projects. They act as a common language, fostering collaboration among developers, operations, and other stakeholders. The modular nature of templates encourages code reuse, speeding up development and maintaining consistency. Version control for infrastructure and configuration becomes seamless, providing transparency and traceability. Automation, coupled with templates, enhances CI/CD pipelines, enabling faster releases and reducing manual errors. This approach revolutionizes development, offering a structured, scalable, and collaborative framework. It simplifies infrastructure management, empowering teams to focus on innovation and code quality. Overall, a template-based GitOps approach creates a more efficient and controlled development lifecycle.

Continuous Integration vs Continuous Delivery vs Continuous Deployment LGS, GBHS&IC, University Of South-Asia, TARA-Technologies

Continuous Integration vs Continuous Delivery vs Continuous Deployment I hope you now get the difference between Continuous Integration, Continuous Delivery and Continuous Deployment. As i mentioned above, these are really an important practices which needs to be implemented to get all the benefits of DevOps. Its a long journey to understand SCM and utilising all its benefits. Hope you enjoyed our today’s article as well ……

Docker e git labGianluca Padovani

Introduction to DevOps and the Practical Use Cases at Credit OKKriangkrai Chaonithi

The document provides an introduction to DevOps and practical use cases. It discusses what DevOps is, why it is popular, the skills required of DevOps engineers, and common DevOps technologies like version control, CI/CD pipelines, containers, and monitoring. It also summarizes Credit OK's use of DevOps practices like Docker, Kubernetes, and GitLab CI/CD pipelines for their credit scoring platform. Finally, it outlines some modern obstacles in software development and concludes that DevOps can help ensure quality, improve productivity, and automate infrastructure through practices like continuous integration, containerization, and logging/monitoring.

MuleSoft_Noida_Meetup_CICD_Azure_07_May_2022.pptxShiva Sahu

The document outlines the agenda for a CI/CD Pipelines using Azure Devops meetup. The agenda includes introductions, discussions on Continuous Integration/Continuous Delivery and Azure DevOps, a demonstration of implementing CI/CD pipelines using Azure DevOps, and a networking session. Continuous Integration/Continuous Delivery aims to merge code changes frequently and automate the entire software release process. Azure DevOps provides features like source code repositories, boards for planning work, pipelines for building and deploying applications, and tools for testing.

CICD Mule Naveen kumar Kavartapu

This document discusses continuous integration (CI) and continuous deployment (CD) achieved through MuleSoft. It provides an overview of DevOps tools and principles like CI, CD, and automation. The document outlines the benefits of CI/CD like faster delivery and recovery. It presents MuleSoft's high-level architecture and how it supports CI/CD. It also discusses APIs, system integration, and the benefits of applying CI/CD patterns with MuleSoft like increased code coverage and deploying code faster to production with less bugs.

KnolX _ Gitlab - Rahul_SoniKnoldus Inc.

Rahul Soni presented on Gitlab, an open source DevOps tool that provides Git repositories, issue tracking, wikis, and integrated CI/CD pipelines. Gitlab allows for automated builds, deployments, monitoring and flexible pipelines. It was discussed that Gitlab is useful for frequent application delivery, continuous feedback, and removing human involvement from secure build stages. Key features of Gitlab include version control, integrated project management, customizable pipelines, security/compliance features, deployment management, and an artifacts registry. Alternatives to Gitlab were briefly mentioned but not described. Rahul concluded by requesting feedback.

Chapter 2Sergio Andrés Rodríguez Galeano

When Automation Keeps Your T-shirt CleanDevOps Indonesia

Introduction to DevOpsAhmed Adel

Transition from CI to CDNanjekye Joannah

Deploying Mule Applications with Jenkins, Azure and BitBucket (1).pptxPankaj Goyal

CI CD Jenkins for Swift DeploymentBintang Thunder

Continuous integration with git labMahyuddin Mahyuddin

Simple ci cd with strider cdAmandeep Singh

Beyond QAgilforcada

Continuous integration for Ruby on RailsDavid Paluy

OpenTuesday: Aktuelle Standards der agilen SoftwareentwicklungDigicomp Academy AG

Lets talk about CI CD Pipeline in Agile Poonam Panday

How can Enterprises benefit from GitOps.pdfOpsTree solutions

Continuous Integration vs Continuous Delivery vs Continuous Deployment LGS, GBHS&IC, University Of South-Asia, TARA-Technologies

Docker e git labGianluca Padovani

Introduction to DevOps and the Practical Use Cases at Credit OKKriangkrai Chaonithi

MuleSoft_Noida_Meetup_CICD_Azure_07_May_2022.pptxShiva Sahu

CICD Mule Naveen kumar Kavartapu

KnolX _ Gitlab - Rahul_SoniKnoldus Inc.

Chapter 2Sergio Andrés Rodríguez Galeano

More from GITS Indonesia (10)

GITS Webinar: How to Build UI/UX Portfolio that Stand Out GITS Indonesia

Pada bulan September, dua UI/UX Designer GITS.ID, melakukan live streaming terkait cara membuat portfolio bagi designer aplikasi/website. Ikuti kami di kanal berikut, agar tidak ketinggalan acara seru selanjutnya: Instagram: @gitsindonesia LinkedIn: GITS Indonesia Website: gits.id -- Tentang GITS.ID GITS.ID memberikan solusi IT bagi perusahaan-perusahaan. Contoh aplikasinya dapat dilihat di gits.id/insight

GITS Webinar: Implementasi REST API di iOS Menggunakan Alamofire dan SwiftyJSONGITS Indonesia

Implementasi REST API di iOS menggunakan Alamofire dan SwiftyJSON memberikan ringkuman singkat tentang: 1. Alamofire dan SwiftyJSON merupakan library eksternal yang memudahkan pengembangan aplikasi iOS menggunakan jaringan HTTP dan memproses data JSON. 2. Alamofire dan SwiftyJSON lebih mudah digunakan dibandingkan fungsi bawaan Apple seperti URLSession dan JSONSerialization. 3. Dokumen ini mendemonstrasikan contoh kode menggunakan Alamofire dan

Fundamental Node.js (Workshop bersama Front-end Developer GITS Indonesia, War...GITS Indonesia

Gits class #22: [ONLINE] Analyze Your User's Activities Using BigQuery and Da...GITS Indonesia

This document provides an overview of BigQuery and how to analyze user activities using BigQuery and Analytics Data. It discusses what BigQuery is, when to use it, why use it, who uses it, where it can be used, and how to use it. It also provides examples of window functions and how to identify user sessions through steps like finding session start times, flagging sessions based on a threshold, and marking session IDs.

GITS Class #21 How to Build Your Dream Team to Achieve the TargetGITS Indonesia

Pada Maret 2020, berlangsung GITS Class #21, seminar gratis dan terbuka untuk umum, di kantor GITS Indonesia. Iyan, salah satu product owner di GITS Indonesia membawakan materi tentang bagaimana membangun tim yang baik agar target kerja dapat dicapai bersama-sama. Follow akun GITS Indonesia untuk mendapatkan info terkait event seru selanjutnya! Instagram: @gitsindonesia Twitter: @gitsindonesia Facebook: GITS Indonesia Medium: GITS Apps Insight YouTube: GITS Indonesia LinkedIn: GITS Indonesia Website: https://gits.id/

GITS Class #20: Building A Fast and Responsive UI in React NativeGITS Indonesia

Pada Desember 2019, berlangsung GITS Class #20, seminar gratis dan terbuka untuk umum, di kantor GITS Indonesia. Topik, salah satu iOS developer di GITS Indonesia membawakan materi yang lebih general tak hanya untuk pemograman iOS, yakni mengenai React Native. Follow akun GITS Indonesia untuk mendapatkan info terkait event seru selanjutnya! Instagram: @gitsindonesia Twitter: @gitsindonesia Facebook: GITS Indonesia Medium: GITS Apps Insight YouTube: GITS Indonesia LinkedIn: GITS Indonesia Website: https://gits.id/

GITS Class #19: Build Large Scale Vue.js Apps with VuexGITS Indonesia

Pada September 2019, berlangsung GITS Class #19, seminar gratis dan terbuka untuk umum, di kantor GITS Indonesia. Warsono, salah satu front-end developer di GITS Indonesia membawakan materi tentang Vuex yang cocok untuk membangun aplikasi Vue.js yang kompleks. Jangan sampai ketinggalan! Follow akun GITS Indonesia untuk mendapatkan info terkait event seru selanjutnya! Instagram: @gitsindonesia Twitter: @gitsindonesia Facebook: GITS Indonesia Medium: GITS Apps Insight YouTube: GITS Indonesia LinkedIn: GITS Indonesia Website: https://gits.id/

GITS Class #17: Coding Multiple Apps with FlutterGITS Indonesia

Pada Juli 2019, berlangsung GITS Class #17, workshop gratis dan terbuka untuk umum, di kantor GITS Indonesia. Daffa dan Nino dari GITS membawakan materi tentang Flutter. Jangan sampai ketinggalan! Follow akun GITS Indonesia untuk mendapatkan info terkait event seru selanjutnya! Instagram: @gitsindonesia Twitter: @gitsindonesia Facebook: GITS Indonesia Medium: GITS Apps Insight YouTube: GITS Indonesia LinkedIn: GITS Indonesia Website: https://gits.id/

GITS Class #12: iOS & Android Component Principles bersama Ajie Arga dan Radh...GITS Indonesia

Pada Maret 2019, berlangsung GITS Class #12, seminar gratis dan terbuka untuk umum, di kantor GITS Indonesia. Ajie Arga dan Radhika Yusuf (iOS dan Android developer di GITS Indonesia) membawakan materi mengenai perbandingan iOS dan Android Component Principles. Jangan sampai ketinggalan! Follow akun GITS Indonesia untuk mendapatkan info terkait event seru selanjutnya! Instagram: @gitscreative Facebook: GITS Indonesia YouTube: GITS Indonesia Linkedin: GITS Indonesia Website: https://gits.co.id/

GITS Class #11: Android Architecture Component bersama Derayan Bima (Android ...GITS Indonesia

Pada Februari 2019, berlangsung GITS Class #11, seminar gratis dan terbuka untuk umum, di kantor GITS Indonesia. Derayan Bima (salah satu Android developer di GITS Indonesia) membawakan materi mengenai Android Architecture Component. Jangan sampai ketinggalan! Follow akun GITS Indonesia untuk mendapatkan info terkait event seru selanjutnya! Instagram: @gitscreative Facebook: GITS Indonesia YouTube: GITS Indonesia Linkedin: GITS Indonesia Website: https://gits.co.id/