Our journey and experience in dealing with the collection/analysis of Continuous Delivery log events using Gerrit Code Review, Jenkins with Apache Flume, ElasticSearch, Kibana and Spark
The document summarizes a presentation on test-driven development (TDD) given by Luca Milanesio. The presentation discusses some of the challenges and downsides of TDD that can occur, such as tests becoming more complex than the code itself, or code being warped to accommodate tests rather than clarity. It also discusses how to rebuild TDD practices to focus on writing accurate, readable tests of appropriate size and scope.
Speed up Continuous Delivery with BigData AnalyticsLuca Milanesio
Use Spark, Apache Flume and ElasticSearch-Kibana to unleash the power of your Code Review and Continuous Delivery Pipeline logs. Jenkins and Gerrit Code Review are the sources of your Analytics KPI dashboards.
Gerrit and Jenkins are used for continuous delivery of big data projects. The document discusses GerritForge, an organization that uses Git, Gerrit, Jenkins, Mesos, Marathon, and Docker to enable continuous integration and deployment of Spark projects onto CDH clusters. A code review lifecycle is presented involving Git, code review in Gerrit, automated builds in Jenkins, and deployment to ephemeral CDH clusters created through Mesos and Marathon for integration testing.
This document describes Luca Milanesio's presentation on zero downtime upgrades for Gerrit. It discusses the different types of upgrades for Gerrit, including code-only, code and database schema, and code, database schema, and repository upgrades. It then outlines an 8 stage process for performing zero downtime upgrades of Gerrit using HAProxy load balancing to minimize downtime and ensure high availability, redirecting traffic from the old to new upgraded version.
In this presentation, Dmitriy Zaporozhets and Job van der Voort talk about the GitLab Release process and give a guided tour of the new features in 8.4. You can find out why GitLab users always know when the next release is, and how they know what's coming next.
With CollabNet TeamForge it is now possible to use feature branch workflow in addition to standard gerrit workflow to work on your changes. In this presentation you will learn how it works, why we have decided to implement it, how was it implemented and what were the choices we have made and challenges along the way.
GitLab 8.5 Highlights and Step-by-step tutorialHeather McNamee
In this webcast, learn how to collaborate with GitLab. You'll see new features from GitLab 8.5 in practice. Check out our blog for more information. https://about.gitlab.com/2016/02/26/webcast-wrapup/
This document summarizes a GitLab webcast about new features in version 8.6 of their self-hosted, scalable version control platform. The webcast demonstrated improvements to confidentiality, organization, performance and the user interface. It also highlighted the new GitLab Pages feature for hosting static websites directly from a GitLab repository. The presenters encouraged community participation and news was shared about GitLab's open strategy and most valuable programmers.
Flex is an open source framework for building interactive web applications that run consistently across browsers and platforms. It uses MXML for declarative UI layouts and ActionScript for client logic. Flex includes a rich library of predefined UI controls like datagrids and charts. It can be used for both web and desktop development via AIR, adding features like file access.
This document summarizes a project meeting about the OCCIware Docker-Connector. The Docker-Connector allows connection between the OCCIware model and real Docker machines by projecting the model onto real machines and introspecting real machines to build the model. It uses Docker APIs and machine to connect Docker instances. Next steps include adding account forms, testing on other platforms, and developing an Infrastructure-Connector.
The document summarizes Christian Güdemann's presentation on OpenNTF and IBM collaboration tools. The presentation included updates on OpenNTF projects and usage, the OpenNTF Essentials toolkit for XPages developers, a demonstration of the IBM Social Business Toolkit SDK, and highlights of lesser known but useful OpenNTF projects. Güdemann encouraged using the available OpenNTF and collaboration resources and welcomed questions.
It's all about feedback - code review as a great tool in the agile toolboxStefan Lay
This document discusses how code review can be a valuable tool for agile teams. It provides arguments for how code review complements pair programming by allowing for asynchronous feedback from multiple reviewers. It also describes best practices for code review, such as keeping changes small and focused. The document advocates for using Git and Gerrit to facilitate code review at scale across large projects and multiple teams. Standardization of infrastructure and processes like contributor guides are highlighted as important for collaboration.
The document discusses WordPress documentation and the process for improving it. It notes that WordPress documentation includes end user docs on wordpress.org/support, developer docs on developer.wordpress.org, and contributor docs on make.wordpress.org. It also discusses misconceptions around documentation, using GitHub for reporting issues, and Google Season of Docs for improving documentation in 2020. The document advocates for collaborating across teams and using paired programming/documenting to improve WordPress documentation.
The document summarizes a presentation about integrating Titanium mobile applications with the OpenShift Platform as a Service (PaaS). It introduces OpenShift, describes how it can be used to code, build, and deploy Titanium apps, and demonstrates this process with a live demo. Attendees are encouraged to ask questions and are provided with support resources for OpenShift.
The document discusses how GitHub, Travis-CI, and APIs work together to enable continuous integration and make software development more collaborative. GitHub allows for social coding and free hosting of projects. Travis-CI monitors GitHub projects for commits and runs unit tests to report on success or failure. APIs allow additional features to be integrated and allow an ecosystem of tools to be built. The combination of these services enables easy continuous integration of Perl projects.
Git and branching workflows enable agile teams to deliver features faster while protecting the main code line from broken changes. The document discusses two common branching models: branch-per-issue and multiple-version support. With branch-per-issue, each developer works on a feature branch, merging to master once tests pass. An integration branch can also be used to catch incompatible changes before merging to master. The multiple-version model maintains stable release branches while new features branch off the alpha master branch. Both models incorporate continuous integration and peer review to catch errors early.
Slides from OpenSource101.com Talk (https://opensource101.com/sessions/wtf-is-gitops-why-should-you-care/)
If you’re interested in learning more about Cloud Native Computing or are already in the Kubernetes community you may have heard the term GitOps. It’s become a bit of a buzzword, but it’s so much more! The benefits of GitOps are real – they bring you security, reliability, velocity and more! And the project that started it all was Flux – a CNCF Incubating project developed and later donated by Weaveworks (the GitOps company who coined the term).
Pinky will share from personal experience why GitOps has been an essential part of achieving a best-in-class delivery and platform team. Pinky will give a brief overview of definitions, CNCF-based principles, and Flux’s capabilities: multi-tenancy, multi-cluster, (multi-everything!), for apps and infra, and more.
Pinky will cover a little of Flux’s microservices architecture and how the various components deliver this robust, secure, and trusted open source solution. Through the components of the Flux project, users today are enjoying compatibility with Helm, Jenkins, Terraform, Prometheus, and more as well as with cloud providers such as AWS, Azure, Google Cloud, and more.
Join us for this informative session and get all of your GitOps questions answered by an end user in the community!
Speaker: Priyanka (aka “Pinky”) is a Developer Experience Engineer at Weaveworks. She has worked on a multitude of topics including front end development, UI automation for testing and API development. Previously she was a software developer at State Farm where she was on the delivery engineering team working on GitOps enablement. She was instrumental in the multi-tenancy migration to utilize Flux for an internal Kubernetes offering. Outside of work, Priyanka enjoys hanging out with her husband and two rescue dogs as well as traveling around the globe.
OpenTuesday: Agile Testautomatisierung und Continuous IntegrationDigicomp Academy AG
In seinem Referat zeigte Michael Palotas von Gridfusion Software Solution auf, wie die einzelnen Komponenten Selenium / Selenium Grid, Maven, Git / GitHub und Jenkins zusammenspielen und wie durch ein solches System agile Testautomatisierung und Continuous Integration mit relativ einfachen Mitteln ermöglicht wird.
GitHub Copilot is an AI assistant that helps programmers write code faster by suggesting code snippets based on context. It was trained on public source code and understands both code and natural language. While it can provide helpful suggestions, the code it generates may not always work and should be carefully reviewed before use. Providing well-commented code, meaningful names, and dividing code into small functions can help Copilot provide better suggestions.
Moving to Git opens up a whole new level of agility for software teams. Freed from the clunky code freezes and monolithic mega-merges that plague centralized version control, developers can isolate work in progress and build in narrow vertical slices with ease. Branching is so painless with Git that many teams are making new branches for each user story or bug fix they implement. This model is quickly becoming the new gold standard for agile teams – and for good reason!
The document provides an introduction to Git and GitHub. It explains that Git is an open-source version control system created by Linus Torvalds, while GitHub is a hosting service for software development projects that uses Git for version control. The document outlines the agenda which includes explaining what a version control system is, demonstrating GitHub, and reviewing important Git commands.
Practical DevOps & Continuous Delivery – A Webinar to learn in depth on DevO...Hugo Messer
After the grant success of the C-level event "I/O: Intelligent Outsourcing", Bridge Global is conducting a free webinar under BEAM (Bridge Events And Meets) on September 6th, 2017.
We designed this webinar as a must-attend event for those who are looking for a kick-start moment to lead their organization into the DevOps environment. It attracted several attendees from all parts of the world. They all sat back and learned valuable insights on DevOps culture and practices.
People are tired of hearing the countless amount of suggestions and opinions while contemplating to start their DevOps journey. This webinar helped its attendees in getting rid of all kinds of apprehensions related to the topic.
Topics Covered
DevOps vs. Traditional Approach.
Addressing the Delivery Challenges.
Why Continuous Integration and Continuous Delivery is so relevant?
DevOps vs Release Management.
Best Practices.
Git is not just a version control system. Git can change the way you interact with your team members. Lot’s of teams don’t think about reflecting their development workflow in Git and just use it out-of-the-box. Git, however, can be much more powerful, giving your team a boost in productivity, protecting your delivery pipeline and helping you to work better together.
In this session we will start with a central workflow that is used by a lot of Subversion teams. You will learn how to practically integrate ALM solutions like continuous deployment, code reviews, change tracking and much more into your individual workflow. You will find out how to protect your master branch from accidental commits, broken builds and unreviewed code. This presentation will help you discover the best way to work together as a team – whether you’re yet to migrate to Git or even an experienced Git user.
At GitLab, we release a new version on 22nd of every month. This is a story of the evolution of GitLab Frontend and why we choose VueJS and how we use it on production.
This document discusses automating code reviews for Salesforce apps. It introduces Clayton, a tool that connects to GitHub or Bitbucket to automatically review pull requests and check for code quality issues. Clayton runs reviews in seconds and provides inline comments. The document outlines benefits of code reviews, how Clayton works, and some results from its use, including a project that reduced defects from 7% to 1% after two months using Clayton. It encourages readers to try Clayton and provide feedback.
EGit is an Eclipse plugin that allows developers to use the distributed revision control system Git within Eclipse. It is built on top of JGit, a lightweight Java library implementation of Git. The goal is for EGit and JGit to improve Git tooling for the Eclipse community. Gerrit is also introduced as a code review system that integrates with Git and provides access control and workflows for code reviews.
Creative Branching Models for Multiple Release StreamsAtlassian
Nuance Communications is making the move from SVN to Git! Why? To take advantage of its strong branching and merging capabilities... and to keep their developers happy. With wild variations between each product's release model, they have multiple releases of one or more components in play at a given time. So they had to get creative with a branching model. This talk will discuss choosing the right Git branching model for each of your release streams, and managing multiple releases using Bitbucket (including Stash), JIRA, Bamboo, and Maven.
Unleash the hidden value of your Gerrit Code Review data. See how to extract statistics from your Git repository and Reviews and update a real-time KPI dashboard with Apache Kafka Stream Events.
Gerrit Code Review: how to script a plugin with Scala and GroovyLuca Milanesio
This document discusses scripting plugins for Gerrit code review. It describes how plugins can now be written in Groovy or Scala by creating a simple class file and placing it in the plugins directory. This allows defining new SSH commands or REST APIs with just a few lines of code. The document outlines several examples including creating branches, listing projects, and validating commit messages. It announces plans to further develop scripting plugin support at the next Gerrit hackathon with the goal of merging it into the core Gerrit codebase.
Flex is an open source framework for building interactive web applications that run consistently across browsers and platforms. It uses MXML for declarative UI layouts and ActionScript for client logic. Flex includes a rich library of predefined UI controls like datagrids and charts. It can be used for both web and desktop development via AIR, adding features like file access.
This document summarizes a project meeting about the OCCIware Docker-Connector. The Docker-Connector allows connection between the OCCIware model and real Docker machines by projecting the model onto real machines and introspecting real machines to build the model. It uses Docker APIs and machine to connect Docker instances. Next steps include adding account forms, testing on other platforms, and developing an Infrastructure-Connector.
The document summarizes Christian Güdemann's presentation on OpenNTF and IBM collaboration tools. The presentation included updates on OpenNTF projects and usage, the OpenNTF Essentials toolkit for XPages developers, a demonstration of the IBM Social Business Toolkit SDK, and highlights of lesser known but useful OpenNTF projects. Güdemann encouraged using the available OpenNTF and collaboration resources and welcomed questions.
It's all about feedback - code review as a great tool in the agile toolboxStefan Lay
This document discusses how code review can be a valuable tool for agile teams. It provides arguments for how code review complements pair programming by allowing for asynchronous feedback from multiple reviewers. It also describes best practices for code review, such as keeping changes small and focused. The document advocates for using Git and Gerrit to facilitate code review at scale across large projects and multiple teams. Standardization of infrastructure and processes like contributor guides are highlighted as important for collaboration.
The document discusses WordPress documentation and the process for improving it. It notes that WordPress documentation includes end user docs on wordpress.org/support, developer docs on developer.wordpress.org, and contributor docs on make.wordpress.org. It also discusses misconceptions around documentation, using GitHub for reporting issues, and Google Season of Docs for improving documentation in 2020. The document advocates for collaborating across teams and using paired programming/documenting to improve WordPress documentation.
The document summarizes a presentation about integrating Titanium mobile applications with the OpenShift Platform as a Service (PaaS). It introduces OpenShift, describes how it can be used to code, build, and deploy Titanium apps, and demonstrates this process with a live demo. Attendees are encouraged to ask questions and are provided with support resources for OpenShift.
The document discusses how GitHub, Travis-CI, and APIs work together to enable continuous integration and make software development more collaborative. GitHub allows for social coding and free hosting of projects. Travis-CI monitors GitHub projects for commits and runs unit tests to report on success or failure. APIs allow additional features to be integrated and allow an ecosystem of tools to be built. The combination of these services enables easy continuous integration of Perl projects.
Git and branching workflows enable agile teams to deliver features faster while protecting the main code line from broken changes. The document discusses two common branching models: branch-per-issue and multiple-version support. With branch-per-issue, each developer works on a feature branch, merging to master once tests pass. An integration branch can also be used to catch incompatible changes before merging to master. The multiple-version model maintains stable release branches while new features branch off the alpha master branch. Both models incorporate continuous integration and peer review to catch errors early.
Slides from OpenSource101.com Talk (https://opensource101.com/sessions/wtf-is-gitops-why-should-you-care/)
If you’re interested in learning more about Cloud Native Computing or are already in the Kubernetes community you may have heard the term GitOps. It’s become a bit of a buzzword, but it’s so much more! The benefits of GitOps are real – they bring you security, reliability, velocity and more! And the project that started it all was Flux – a CNCF Incubating project developed and later donated by Weaveworks (the GitOps company who coined the term).
Pinky will share from personal experience why GitOps has been an essential part of achieving a best-in-class delivery and platform team. Pinky will give a brief overview of definitions, CNCF-based principles, and Flux’s capabilities: multi-tenancy, multi-cluster, (multi-everything!), for apps and infra, and more.
Pinky will cover a little of Flux’s microservices architecture and how the various components deliver this robust, secure, and trusted open source solution. Through the components of the Flux project, users today are enjoying compatibility with Helm, Jenkins, Terraform, Prometheus, and more as well as with cloud providers such as AWS, Azure, Google Cloud, and more.
Join us for this informative session and get all of your GitOps questions answered by an end user in the community!
Speaker: Priyanka (aka “Pinky”) is a Developer Experience Engineer at Weaveworks. She has worked on a multitude of topics including front end development, UI automation for testing and API development. Previously she was a software developer at State Farm where she was on the delivery engineering team working on GitOps enablement. She was instrumental in the multi-tenancy migration to utilize Flux for an internal Kubernetes offering. Outside of work, Priyanka enjoys hanging out with her husband and two rescue dogs as well as traveling around the globe.
OpenTuesday: Agile Testautomatisierung und Continuous IntegrationDigicomp Academy AG
In seinem Referat zeigte Michael Palotas von Gridfusion Software Solution auf, wie die einzelnen Komponenten Selenium / Selenium Grid, Maven, Git / GitHub und Jenkins zusammenspielen und wie durch ein solches System agile Testautomatisierung und Continuous Integration mit relativ einfachen Mitteln ermöglicht wird.
GitHub Copilot is an AI assistant that helps programmers write code faster by suggesting code snippets based on context. It was trained on public source code and understands both code and natural language. While it can provide helpful suggestions, the code it generates may not always work and should be carefully reviewed before use. Providing well-commented code, meaningful names, and dividing code into small functions can help Copilot provide better suggestions.
Moving to Git opens up a whole new level of agility for software teams. Freed from the clunky code freezes and monolithic mega-merges that plague centralized version control, developers can isolate work in progress and build in narrow vertical slices with ease. Branching is so painless with Git that many teams are making new branches for each user story or bug fix they implement. This model is quickly becoming the new gold standard for agile teams – and for good reason!
The document provides an introduction to Git and GitHub. It explains that Git is an open-source version control system created by Linus Torvalds, while GitHub is a hosting service for software development projects that uses Git for version control. The document outlines the agenda which includes explaining what a version control system is, demonstrating GitHub, and reviewing important Git commands.
Practical DevOps & Continuous Delivery – A Webinar to learn in depth on DevO...Hugo Messer
After the grant success of the C-level event "I/O: Intelligent Outsourcing", Bridge Global is conducting a free webinar under BEAM (Bridge Events And Meets) on September 6th, 2017.
We designed this webinar as a must-attend event for those who are looking for a kick-start moment to lead their organization into the DevOps environment. It attracted several attendees from all parts of the world. They all sat back and learned valuable insights on DevOps culture and practices.
People are tired of hearing the countless amount of suggestions and opinions while contemplating to start their DevOps journey. This webinar helped its attendees in getting rid of all kinds of apprehensions related to the topic.
Topics Covered
DevOps vs. Traditional Approach.
Addressing the Delivery Challenges.
Why Continuous Integration and Continuous Delivery is so relevant?
DevOps vs Release Management.
Best Practices.
Git is not just a version control system. Git can change the way you interact with your team members. Lot’s of teams don’t think about reflecting their development workflow in Git and just use it out-of-the-box. Git, however, can be much more powerful, giving your team a boost in productivity, protecting your delivery pipeline and helping you to work better together.
In this session we will start with a central workflow that is used by a lot of Subversion teams. You will learn how to practically integrate ALM solutions like continuous deployment, code reviews, change tracking and much more into your individual workflow. You will find out how to protect your master branch from accidental commits, broken builds and unreviewed code. This presentation will help you discover the best way to work together as a team – whether you’re yet to migrate to Git or even an experienced Git user.
At GitLab, we release a new version on 22nd of every month. This is a story of the evolution of GitLab Frontend and why we choose VueJS and how we use it on production.
This document discusses automating code reviews for Salesforce apps. It introduces Clayton, a tool that connects to GitHub or Bitbucket to automatically review pull requests and check for code quality issues. Clayton runs reviews in seconds and provides inline comments. The document outlines benefits of code reviews, how Clayton works, and some results from its use, including a project that reduced defects from 7% to 1% after two months using Clayton. It encourages readers to try Clayton and provide feedback.
EGit is an Eclipse plugin that allows developers to use the distributed revision control system Git within Eclipse. It is built on top of JGit, a lightweight Java library implementation of Git. The goal is for EGit and JGit to improve Git tooling for the Eclipse community. Gerrit is also introduced as a code review system that integrates with Git and provides access control and workflows for code reviews.
Creative Branching Models for Multiple Release StreamsAtlassian
Nuance Communications is making the move from SVN to Git! Why? To take advantage of its strong branching and merging capabilities... and to keep their developers happy. With wild variations between each product's release model, they have multiple releases of one or more components in play at a given time. So they had to get creative with a branching model. This talk will discuss choosing the right Git branching model for each of your release streams, and managing multiple releases using Bitbucket (including Stash), JIRA, Bamboo, and Maven.
Unleash the hidden value of your Gerrit Code Review data. See how to extract statistics from your Git repository and Reviews and update a real-time KPI dashboard with Apache Kafka Stream Events.
Gerrit Code Review: how to script a plugin with Scala and GroovyLuca Milanesio
This document discusses scripting plugins for Gerrit code review. It describes how plugins can now be written in Groovy or Scala by creating a simple class file and placing it in the plugins directory. This allows defining new SSH commands or REST APIs with just a few lines of code. The document outlines several examples including creating branches, listing projects, and validating commit messages. It announces plans to further develop scripting plugin support at the next Gerrit hackathon with the goal of merging it into the core Gerrit codebase.
Mobile Application Lifecycle with Jekins, Trello and CollabNet TeamForgeLuca Milanesio
SmartPhones have revolutionised the way we think and write software: software development on Mobile has and need to be agile ... but how can you make one step further and have actually your SmartPhone to drive your development ?
Can Mobile App development and Continuous Delivery be pushed to the edges?
See how you can follow every step of your development with your SmartPhone end-to-end:
Continuous Integration
Continuous Delivery
Install
Test execution
Issue tracking
This document discusses various Git concepts and commands. It begins with an introduction to Git and SCM concepts like branches and merging. It then demonstrates how to initialize a Git repository, add files, and commit changes. Different Git states like staged, unstaged, and clean are explained. Commands shown include git add, commit, status, log, and gui tools like gitk and gitgui. Branching, merging, rebasing, cherry-picking and resolving conflicts are demonstrated. The document concludes by discussing reverting and resetting changes in Git, noting the dangers of losing commits if not used carefully.
GerritHub.io was launched 2 years ago.
Learnings, problems and new ideas on how to improve the GitHub to Gerrit plugin and hints on Gerrit scalability and replication.
See how GitBlit has been plugged into Gerrit Code Review as repository viewer.
Includes a step-by-step guide on how to clone, build and use GitBlit plugin on Gerrit.
Jenkins is a tool that supports continuous integration by automatically building, testing, and deploying code changes. It integrates code changes frequently, at least daily, to avoid "big bang" integrations. Jenkins runs builds and tests across multiple platforms using slave nodes. It supports various source control systems and build tools and notifies developers of failed builds or tests through email or other plugins.
Synchronizing parallel delivery flows in jenkins using groovy, build flow and...Andrey Devyatkin
Slides from my talk on Automation Nights 15.09-STHLM
https://www.youtube.com/watch?v=1YmnTCVBdmc&index=2&list=PLuvRKxeqrv4I_y8Vxz-09-EJuP6yELwEX
Hadoop Summit 2013 : Continuous Integration on top of hadoopWisely chen
Wisely Chen and Neal Lee presented on continuous integration on Hadoop. They discussed automating the software development process, including automatically running unit tests on code commits, performing tests on staging environments that mimic production, and deploying to production. They demonstrated tools for unit testing Hadoop jobs, including PigUnit and Vaidya for performance diagnosis, and how these tools can integrate with a continuous integration system to automatically run tests with each code change.
The document is a presentation on cloud computing that provides definitions and examples. It defines cloud computing as internet-based computing where shared resources such as software, data, and services are provided on demand over the internet. The presentation discusses how cloud computing provides advantages such as flexibility, scalability, and a pay-as-you-go model. It provides examples of infrastructure as a service (Amazon EC2), platform as a service (Google App Engine), and software as a service (Salesforce.com). The presentation focuses on Salesforce.com's cloud offerings including Sales Cloud, Service Cloud, Chatter, and the Force.com platform.
"Groovy Maven Builds" presentation from Gr8Conf, Copenhagen (May 19, 2011)
It shows how Maven builds become more dynamic when Groovy power and flexibility is applied.
The document discusses the history and growth of Jenkins, an open source automation server. It began in 2004 as a personal project by Kohsuke Kawaguchi to automate builds. Over time it grew popular and now has over 470 plugins to support various tasks. The number of plugins and releases has increased dramatically each year as more developers contribute to and use Jenkins.
Basics of cloud computing & salesforce.comDeepu S Nath
This document provides an overview of cloud computing and discusses Salesforce.com. It defines cloud computing as using computing resources delivered over a network, and notes the cost savings and scalability benefits it provides compared to on-premise IT. Common cloud service models including SaaS, PaaS and IaaS are described. The document also summarizes how Salesforce.com alleviated concerns about security, integration and TCO that initially held some organizations back from adopting cloud computing. It identifies Salesforce.com as a major player in the cloud market with over 100,000 customers.
Jenkins User Conference - Continuous Delivery on MobileLuca Milanesio
SmartPhones have revolutionised the way we think and write software: how can you take an additional step and actually have your SmartPhone drive development? With Jenkins, you can drive and integrate every step of your development with your SmartPhone, end-to-end: CI and delivery - Application install - Test execution - Issue tracking. See how to implement mobile plugins for Jenkins on mobile
Continuous Integration for Spark Apps by Sean McIntyreSpark Summit
The document discusses the challenges of continuous integration for Apache Spark applications and presents a solution developed by Uncharted Software. It describes squeezing Spark, tests, and other tools into Docker containers to enable building and testing Spark apps across branches in a shared environment. This approach allows automating testing of Spark code commits, detecting issues early, and providing visibility of test results.
GitHub pull request model and Gerrit Code Review, which one is best for you ?
What are the plus and minuses of both models ?
See how it make sense to use one or the other or even both together.
The GitHub plugin for Gerrit Code Review allows the existing developers community to start exploring code review without loosing contact with the github.com presence.
The document discusses the use of Gerrit for code review in agile workflows. It begins by explaining some of the challenges of continuous integration, including broken builds that can occur when developers push untested code. It then discusses how Git addresses this issue by enabling early code integration through topic branches. However, it notes that Git alone does not enforce policy. Gerrit is introduced as a tool that builds upon Git to enable code review and enforce access controls and policies. It provides an overview of key Gerrit features like automatic topic branches, trigger builds, and democratic voting processes.
The document discusses the evolution of DevOps practices from earlier software development approaches. It outlines four stages of DevOps maturity: (1) identifying manual processes for automation, (2) automating processes for repeatability, (3) adding metrics for monitoring, and (4) using metrics to continuously improve processes. The document also provides examples of tools that support DevOps practices at different stages.
DevOpsGuys FutureDecoded 2016 - is DevOps the AnswerDevOpsGroup
This document provides information about DevOps and digital transformation. It discusses how DevOps can help organizations transform by moving from traditional command and control models to more collaborative and iterative approaches. A DevOps operating model is proposed that uses multi-disciplinary product delivery teams and platform teams to continuously deliver value to customers. Microsoft tools that can support a DevOps transformation are also highlighted. The document concludes by demonstrating how to deploy a Docker container cluster on Azure using DevOps techniques.
Dublin JUG Lightweight Microservices with Microprofile and Raspberry PIsJean-Louis MONTEIRO
Microservices has been buzzword in the last years in software engineering. It helps to solve issues we had with monolith applications, however it also brings new challenges.
Eclipse MicroProfile provides a time to market set of specifications and tools addressing these many challenges. Jean-Louis will be looking on how to use these spec implementations in practice throughout this presentation and show step-by-step examples on how to add monitoring with MP Health and with MP Metrics, security with MP JWT, custom configuration with MP Config, and also teach how to easily provide documentation with MP OpenAPI and much more.
Lightweight will be achieved by deploying and running Docker on raspberry PIs.
JAX London 2014 "Moving to DevOps Mode: easy, hard or just plain terrifying?"Daniel Bryant
DevOps - is it for you? Heard about the wonderful ways it could benefit your organisation, but put off by the scary stories? Can you really make the transition to DevOps, and is it worth it? Listen and learn from two DevOps practitioners about their hands-on experiences in making the change. Covering a range of real life examples, this talk will explain the real business benefits to be had from using DevOps techniques, as well as the technical and personal aspects involved.
Whether it’s a small team within a startup or one of hundreds within a large organisation, this talk has practical advice on how to approach the challenge, what critical changes need to be considered, and what tools and processes are best suited for the situation. The adoption of DevOps is a game changing event for the industry. Learn why and learn how you can benefit from it too.
This talk was presented with Steve Poole (@spoole167) at JAX London, October 2014
Moving to a DevOps mode - easy, hard or just plain terrifying? - Daniel Bryan...JAXLondon2014
The document discusses moving to a DevOps model and describes it as both easy and terrifying. It advocates breaking down silos between development and operations teams by emphasizing common goals, shared responsibility, and standard technology. The benefits of DevOps include faster reaction times for businesses and extending agility across IT organizations.
DevOpsGuys - Getting Started with DevOps - Github/Azure WebinarDevOpsGroup
DevOpsGuys - Getting Started with DevOps - Github/Azure Webinar in April 2017 that talks about the 5 key ingredients you need to kick start your DevOps Transformation
AgileLIVE Webinar: Build a DevOps Culture & Infrastructure for Success Part 1VersionOne
Lessons Learned from Target’s DevOps Journey
Heather Mickman, Director, Enterprise Services & Integration, and Ross Clanton, Sr. Group Manager - Engineering Practices, at retail giant Target, will share the key challenges and lessons learned.
The document discusses the origins and key principles of DevOps. It originates from a 2009 Velocity Conference talk about Flickr's deployment practices of 10+ deploys per day through automation, shared version control, and one-step builds. The main principles discussed are CAMS - Culture, Automation, Measurement, and Sharing. Culture focuses on respect, trust, and avoiding blame. Automation, measurement, and sharing are also emphasized as important aspects of DevOps.
LJC 4/21"Easy Debugging of Java Microservices Running on Kubernetes with Tele...Daniel Bryant
Many Java-based organizations adopt cloud native development practices with the goal of shipping features faster. The technologies and architectures may change when we move to the cloud, but the fact remains that we all still add the occasional bug to our code. The challenge here is that many of your existing local debugging tools and practices can't be used when everything is running in a container or deployed onto Kubernetes running in the cloud. This is where the open source Telepresence tool can help.
Join me to learn about:
- The challenges with scaling Kubernetes-based Java development i.e. you can only run so many microservices locally before minikube melts your laptop
- An exploration of how Telepresence can "intercept" or reroute traffic from a specified service in a remote K8s cluster to your local dev machine
- The benefits of getting a "hot reload" fast feedback loop between applications being developed locally and apps running in the remote environment
- A tour of Telepresence, from the sidecar proxy deployed into the remote K8s cluster to the CLI
- An overview of using "preview URLs" and header-based routing for the sharing, collaboration, and isolation of changes you are making on your local copy of an intercepted service
This document provides an overview of continuous testing in DevOps presented by Michael Hackett of LogiGear Corporation. It discusses what DevOps is and how testing fits into the continuous delivery pipeline. It emphasizes the need for testing at every step of development and deployment through test automation. It also provides examples of challenges companies face in implementing continuous testing and DevOps practices.
"Stop Caring about Kubernetes" is a humorous talk about how Kubernetes is an important technology for managing containerized applications, but it should be abstracted to the level of an operating system, making it transparent and easy for application teams to deploy their applications without needing deep knowledge of Kubernetes. The talk will discuss the benefits of using Kubernetes in this way, such as improved efficiency and scalability, and will also introduce tools and best practices for achieving this level of abstraction. The goal of the talk is to empower application teams to focus on what they do best, developing and deploying their applications while leaving the management of the underlying infrastructure to Kubernetes.
Slides from Jesper Ottosen's 2017 Fall OnlineTestConf session – Shifting is more than shift left.
Change is happening to the testing activities. Shift-left automates and codifies the testing activities. Shift-right does it for production.
This session was about a couple of other trends, changes, and shifts that are happening to testers and test managers.
– Shift-Coach, where It’s more about coaching teams.
– Shift-SME, where it’s more about business savvy.
– Shift-Deliver, where it’s more about the road to production
www.onlinetestconf.com
The document discusses microservices and the benefits of developing using a microservices architecture. It describes the author's experience working on both large monolithic systems and microservice architectures. Some key benefits of microservices mentioned include improved knowledge sharing, faster progress and adoption of new technologies, easier elimination of technical debt, and increased accountability. The author argues that developing with microservices can achieve scalable high productivity, but certain factors like doing agile well and defining roles appropriately are required to realize the benefits.
Nitobi was moving from products to services in 2007-2008 and faced a choice between specializing or remaining agnostic in their technology stack. They chose to remain agnostic and focused on being web-based. As mobile trends emerged, they began experimenting with mobile development which led to the creation of PhoneGap in 2008 to build mobile apps using web technologies. Since then, PhoneGap has grown significantly and Nitobi's business has evolved to focus more on services related to mobile development.
Microservices - Scaling Development and ServicePaulo Gaspar
This document discusses microservices and provides recommendations for developing microservice architectures. It begins by comparing experiences developing large and small systems. Microservices are then defined as independently deployable services that communicate via lightweight mechanisms like HTTP. Examples are provided of companies that pioneered microservices like Amazon and Netflix. The document concludes by recommending developers start small with microservices, focus on principles over specific technologies, and address challenges of distributed systems through monitoring, resilience patterns, and infrastructure support.
Building Microservice Systems Without Cooking Your Laptop: Going “Remocal” wi...Ambassador Labs
The document discusses using Docker Desktop and Telepresence to enable "remocal" development of microservice systems. Telepresence proxies a local machine into a Kubernetes cluster, allowing fast feedback by running code changes directly in the cluster. The Docker Desktop extension for Telepresence integrates this capability, allowing developers to use local tools while their code runs on Kubernetes. This enables a smooth development workflow for building and testing microservice applications in Kubernetes.
Building Microservice Systems Without Cooking Your Laptop: Going “Remocal” wi...Daniel Bryant
Join me for a tour of coding, testing, and shipping microservices using remote-to-local “remocal” tools and techniques. You will:
- Understand the challenges with scaling container-based application development – i.e. you can only run so many microservices locally before minikube melts your laptop.
- Learn when to use various types of development practices and tooling based on your use case and requirements for production realism, speed, and practicality.
- Explore how to utilize containerized dependencies and Docker for testing, including for both apps and services you own and those you don’t.
- Learn how Telepresence can enable “remocal” development, expanding your local machine and Docker Desktop out into a remote Kubernetes cluster.
MJC 2021: "Debugging Java Microservices Running on Kubernetes with Telepresence"Daniel Bryant
The document discusses using Telepresence to improve the development workflow for Java microservices running on Kubernetes. Telepresence allows developers to run their code locally while still connecting to the Kubernetes cluster, improving the speed of the inner development loop. It supports various workflows from small to large systems. The benefits of Telepresence include using local tools, connecting to cloud resources, and a very fast inner loop. It is an open source project maintained by the CNCF.
DevOps Days Toronto: From 6 Months Waterfall to 1 hour Code DeploysAndreas Grabner
Slides used for https://www.devopsdays.org/events/2017-toronto/program/andreas-grabner/
In 2011 we delivered 2 major releases of our on premise enterprise software. Market, technology and customer requirements forced us to change that in order to remain competitive.
Now – in 2017 - we are deploying and providing feature releases every 2 weeks for both our on premise and SaaS-based offering. We deploy 170 SaaS production changes per day and have a DevOps pipeline that allows us to deploy a code change within 1h if necessary.
To increase quality, we built and provide a DevOps pipeline that currently executes 31000 Unit & Integration Tests per Hour as well as 60h UI Tests per Build. Our application teams are responsible end-to-end for their features and use production monitoring to validate their deployments which allows them to find 93% of bugs in production before it impacts our end users.
In this session I explain how this transformation worked from both “Top Down” as well as “Bottom Up” in our organization. A key component was the 4 people strong DevOps Team who developed and “sell” their DevOps Pipeline to the globally distributed application teams. I will give insights into how our pipeline enables application teams to design, code, test and run a new feature for our user base.
I will also talk about the “dark moments” as change is never without friction. Both internally as well as with our customers who also had to get used to more rapid changes.
AllDayDevOps: "Microservices: The People and Organisational Impact"Daniel Bryant
Microservices are where it’s at. Everything is easier to manage when it’s smaller, right? ‘Micro’ things may appear to be easier to manage, but there is always a macro context, and working with people and teams is no exception. Join this session to learn more.
Microservices are where it’s at. Everything is easier to manage when it’s micro, right? Micro code bases (less than 10 LOC), micro containers (less than 10Mb), and micro teams (less than one person???). ‘Micro’ things may appear to be easier to manage, but there is always a macro context, and working with people and teams is no exception. This talk presents some of the challenges the OpenCredo team have seen when implementing microservices within a range of organisations, and we’ll suggest tricks and techniques to help you manage your ‘micro’ teams and the ‘macro’ level.
Topics covered include: leadership - advice on creating shared understanding, conveying strategy, and developing your team; empathy - because understanding others is at the heart of everything you do; organisational structure - from Zappos’ holocracy to MegaOrg’s strict hierarchy, from Spotify’s squads, chapters and guilds, to BigCorp’s command and control. There is a management style for everybody; and more.
Gerrit Analytics applied to Android source codeLuca Milanesio
GerritForge trialled the Gerrit Analytics plugin and ETL with the Android Open-Source Project code-base. The results of the trial have been presented at the Gerrit User Summit 2019 at Gothenburg and Sunnyvale CA. Find inside an overview of the problems involved, the solutions implemented and also the use of the pull-replication plugin to fetch the code from the official Android repository.
Gerrit Code Review is getting cloud-native, thanks to the extensions and plugins developed by GerritForge.
See how you can deploy and integrate Gerrit with AWS and GCloud and get the best of the serverless architecture, avoiding common pitfalls.
The document discusses different types of migrations ranging from trivial to ultrahazardous. It describes approaches for migrating Gerrit installations of varying complexity based on factors like team size, number of repositories, and distance of migration. Blue/green deployments are recommended for complex migrations to minimize risk and downtime. Automating migrations with Ansible and proper planning including staging and testing are emphasized to enable smooth upgrades.
Gerrit 3.2 and 3.3 introduced many new features and improvements including Java 11 support, performance optimizations like new caching, zero-downtime upgrades, file uploads in PolyGerrit, and expanded testing. Gerrit 3.3 focused on attention sets and replication stabilization. Native packages were also updated and Gerrit 3.0 is now end of life.
Last year we presented the vision and road-map of Gerrit multi-master setup at GerritHub.io. This year GerritForge and the Gerrit community have released the first version of the multi-site plugin, based on the legacy of the successful high-availability plugin started years ago by Ericsson.
The multi-site plugin is a 100% OpenSource solution and does not require any proprietary software installed or hardware/software level filesystem replication: it is fully based on the replication, healthcheck and multi-site plugins.
Multi-site is a journey and the Community is making big steps towards it.
Luca Milanesio from GerritForge gave a presentation on the new features in Gerrit 3.0 and beyond. Some of the key highlights included:
- PolyGerrit is the new Gerrit UI built without GWT for improved performance and customization.
- NoteDb stores all Gerrit data including commits, reviews, metadata, accounts and groups directly in Git for fully consistent backups and removal of single point of failure databases.
- Submit rules can now be written in any language through an extension point beyond just Prolog.
- New core plugins like Gitiles, delete project, and web hooks have been added with a plugin manager for easy installation.
- Future releases will
The document discusses the Gerrit User Summit 2019 hosted by Volvo Cars in Gothenburg, Sweden. It thanks Volvo Cars, Google, and GerritForge for sponsoring the event. It also mentions what's new in Gerrit 3.0 and beyond, a Google survey on Gerrit Code Review, that Gerrit is open source, the Gerrit analytics website, and the different roles that make up the Gerrit Code Review community.
Gerrit multi-master / multi-site at GerritHubLuca Milanesio
GerritHub evolved from a simple master-slave setup into a truly multi-master and multi-site service. See how the solution has been implemented and the next steps for making the service even better and more distributed and scalable.
This document provides information about the Gerrit User Summit 2018 being held in Palo Alto, CA from GerritForge.com. It includes the agenda for the two day summit, with talks and networking sessions on Day 1 and breakfast, more talks and a closing on Day 2. On the evening of Day 1 there will be a celebration for the 10 year anniversary of Gerrit Code Review at the Computer History Museum with drinks, dinner and cake. The summit will give attendees opportunities to learn about new Gerrit features, ask questions, share experiences, network with other Gerrit users, and contribute to the Gerrit Code Review project.
Jenkins plugin for Gerrit Code Review pipelinesLuca Milanesio
Introducing the brand new plugin that brings Gerrit Code Review into the Jenkins Pipeline world: simpler, faster and yet more powerful than ever. Gerrit becomes a first-class citizen into the Jenkins ecosystem by enabling a complete pipeline to fetch changes for review, building and submitting the relevant feedback as automated review comment to Gerrit. The new plugin comes from the CI validation workflow experience of the Gerrit Code Review project. The key aspects are stateless, configuration-less - apart from the standard SCM configuration settings. That means that multiple jobs and multiple branches of the same job, can have their own Gerrit integration defined and working out-of-the-box.
The document outlines the schedule and details of the Gerrit User Summit, an annual event that brings together the Gerrit community from over 14 countries. The summit focuses on allowing attendees to meet each other, exchange information, discuss ideas, and ask questions. It includes talks on both days, as well as time for lunch, demos of exhibitor booths, and Q&A with Gerrit maintainers.
How to keep Jenkins logs forever without performance issuesLuca Milanesio
Jenkins is a golden source of information: it contains logs, artifacts and feedback and x-refs from multiple sources. To keep our master healthy and responsive, often we need to remove precious data. The members of the Gerrit Code Review project wanted to keep everything and this is how we did it.
Jenkins Pipeline on your Local Box to Reduce Cycle TimeLuca Milanesio
A case study on how to reduce continuous delivery cycle time by using your local resources as the starting point for the continuous delivery Jenkins Pipeline. Your local box has spare CPU, memory and a Git repo to be used with a local Jenkins Pipeline. You get fast feedback and create lots of precious artifacts.
Jenkins world 2017 - Data-Driven CI Pipeline with Gerrit Code ReviewLuca Milanesio
There is hidden value in the data produced by your Continous Delivery Pipeline that could help
you achieve more efficient processing. The main objective of this workshop is to show you how to
extract that value and benefit from it.
We will introduce you to how to configure and improve your Continuous Delivery Pipeline using
data. After an overview of a Continuous Delivery Pipeline setup using Gerrit Code Review,
Jenkins, and Docker, we will go through the steps on how to extract and analyze data across all
the pipeline stages of the delivery chain.
Stable master workflow with Gerrit Code ReviewLuca Milanesio
This document provides an agenda for a training on Gerrit Code Review. The morning session will cover benefits of code review, an overview of Gerrit, advanced Git commands needed for review, and exercises on pushing changes for review and reviewing using Gerrit. The afternoon session will include exercises on adding new patch sets, multiple patch set reviews, rebase and conflict resolution, and questions. Key concepts discussed include the Gerrit code review workflow, target branches, magic refs, and changes and patch sets.
Noah Loul Shares 5 Steps to Implement AI Agents for Maximum Business Efficien...Noah Loul
Artificial intelligence is changing how businesses operate. Companies are using AI agents to automate tasks, reduce time spent on repetitive work, and focus more on high-value activities. Noah Loul, an AI strategist and entrepreneur, has helped dozens of companies streamline their operations using smart automation. He believes AI agents aren't just tools—they're workers that take on repeatable tasks so your human team can focus on what matters. If you want to reduce time waste and increase output, AI agents are the next move.
Complete Guide to Advanced Logistics Management Software in Riyadh.pdfSoftware Company
Explore the benefits and features of advanced logistics management software for businesses in Riyadh. This guide delves into the latest technologies, from real-time tracking and route optimization to warehouse management and inventory control, helping businesses streamline their logistics operations and reduce costs. Learn how implementing the right software solution can enhance efficiency, improve customer satisfaction, and provide a competitive edge in the growing logistics sector of Riyadh.
UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager APIUiPathCommunity
Join this UiPath Community Berlin meetup to explore the Orchestrator API, Swagger interface, and the Test Manager API. Learn how to leverage these tools to streamline automation, enhance testing, and integrate more efficiently with UiPath. Perfect for developers, testers, and automation enthusiasts!
📕 Agenda
Welcome & Introductions
Orchestrator API Overview
Exploring the Swagger Interface
Test Manager API Highlights
Streamlining Automation & Testing with APIs (Demo)
Q&A and Open Discussion
Perfect for developers, testers, and automation enthusiasts!
👉 Join our UiPath Community Berlin chapter: https://community.uipath.com/berlin/
This session streamed live on April 29, 2025, 18:00 CET.
Check out all our upcoming UiPath Community sessions at https://community.uipath.com/events/.
What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat
The MCP (Model Context Protocol) is a framework designed to manage context and interaction within complex systems. This SlideShare presentation will provide a detailed overview of the MCP Model, its applications, and how it plays a crucial role in improving communication and decision-making in distributed systems. We will explore the key concepts behind the protocol, including the importance of context, data management, and how this model enhances system adaptability and responsiveness. Ideal for software developers, system architects, and IT professionals, this presentation will offer valuable insights into how the MCP Model can streamline workflows, improve efficiency, and create more intuitive systems for a wide range of use cases.
How Can I use the AI Hype in my Business Context?Daniel Lehner
𝙄𝙨 𝘼𝙄 𝙟𝙪𝙨𝙩 𝙝𝙮𝙥𝙚? 𝙊𝙧 𝙞𝙨 𝙞𝙩 𝙩𝙝𝙚 𝙜𝙖𝙢𝙚 𝙘𝙝𝙖𝙣𝙜𝙚𝙧 𝙮𝙤𝙪𝙧 𝙗𝙪𝙨𝙞𝙣𝙚𝙨𝙨 𝙣𝙚𝙚𝙙𝙨?
Everyone’s talking about AI but is anyone really using it to create real value?
Most companies want to leverage AI. Few know 𝗵𝗼𝘄.
✅ What exactly should you ask to find real AI opportunities?
✅ Which AI techniques actually fit your business?
✅ Is your data even ready for AI?
If you’re not sure, you’re not alone. This is a condensed version of the slides I presented at a Linkedin webinar for Tecnovy on 28.04.2025.
Dev Dives: Automate and orchestrate your processes with UiPath MaestroUiPathCommunity
This session is designed to equip developers with the skills needed to build mission-critical, end-to-end processes that seamlessly orchestrate agents, people, and robots.
📕 Here's what you can expect:
- Modeling: Build end-to-end processes using BPMN.
- Implementing: Integrate agentic tasks, RPA, APIs, and advanced decisioning into processes.
- Operating: Control process instances with rewind, replay, pause, and stop functions.
- Monitoring: Use dashboards and embedded analytics for real-time insights into process instances.
This webinar is a must-attend for developers looking to enhance their agentic automation skills and orchestrate robust, mission-critical processes.
👨🏫 Speaker:
Andrei Vintila, Principal Product Manager @UiPath
This session streamed live on April 29, 2025, 16:00 CET.
Check out all our upcoming Dev Dives sessions at https://community.uipath.com/dev-dives-automation-developer-2025/.
This is the keynote of the Into the Box conference, highlighting the release of the BoxLang JVM language, its key enhancements, and its vision for the future.
Semantic Cultivators : The Critical Future Role to Enable AIartmondano
By 2026, AI agents will consume 10x more enterprise data than humans, but with none of the contextual understanding that prevents catastrophic misinterpretations.
Increasing Retail Store Efficiency How can Planograms Save Time and Money.pptxAnoop Ashok
In today's fast-paced retail environment, efficiency is key. Every minute counts, and every penny matters. One tool that can significantly boost your store's efficiency is a well-executed planogram. These visual merchandising blueprints not only enhance store layouts but also save time and money in the process.
Andrew Marnell: Transforming Business Strategy Through Data-Driven InsightsAndrew Marnell
With expertise in data architecture, performance tracking, and revenue forecasting, Andrew Marnell plays a vital role in aligning business strategies with data insights. Andrew Marnell’s ability to lead cross-functional teams ensures businesses achieve sustainable growth and operational excellence.
Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma
My talk for the Indian School of Business (ISB) Emerging Leaders Program Cohort 9. In this talk, I discussed key issues around adoption of GenAI in business - benefits, opportunities and limitations. I also discussed how my research on Theory of Cognitive Chasms helps address some of these issues
Spark is a powerhouse for large datasets, but when it comes to smaller data workloads, its overhead can sometimes slow things down. What if you could achieve high performance and efficiency without the need for Spark?
At S&P Global Commodity Insights, having a complete view of global energy and commodities markets enables customers to make data-driven decisions with confidence and create long-term, sustainable value. 🌍
Explore delta-rs + CDC and how these open-source innovations power lightweight, high-performance data applications beyond Spark! 🚀
TrsLabs - Fintech Product & Business ConsultingTrs Labs
Hybrid Growth Mandate Model with TrsLabs
Strategic Investments, Inorganic Growth, Business Model Pivoting are critical activities that business don't do/change everyday. In cases like this, it may benefit your business to choose a temporary external consultant.
An unbiased plan driven by clearcut deliverables, market dynamics and without the influence of your internal office equations empower business leaders to make right choices.
Getting things done within a budget within a timeframe is key to Growing Business - No matter whether you are a start-up or a big company
Talk to us & Unlock the competitive advantage
3. @gitenterprise#DevoxxPL
• Co-founder and
Director of GerritForge
• over 20 years in Agile
Development and ALM
• Contributor to many
OpenSource projects
• Mind and hands of
@gitenterprise and
@gerritreview
About Luca Milanesio
14. @gitenterprise#DevoxxPL
We use micro-services
• 100+ Components
• 200+ Repositories
• 300+ People and 100,000+ of review comments
• Cross-components [implicit] dependencies
• Lots of build chains
• 10,000+ of builds
Now feel the pain :-(
16. @gitenterprise#DevoxxPL
In order to deliver Feature ABC
I NEED
Ver. N of Service-A with
Ver. M of Service-B and
Ver. K of Service C
Problem #2 : Dependencies
18. @gitenterprise#DevoxxPL
Release small changes is GOOD
Release often every change is GOOD
BUT
How long it takes the "Big Picture" and End-to-End?
Where is my bottleneck?
Problem #4 : Cycle time
21. @gitenterprise#DevoxxPL
• Collect all review events
• Collect all logs
• Channel them to a
central store
• Crunch and Crunch
continuously
• Never delete
• Process, inspect and
learn
BigData to the rescue