Community - Carol Chen, Sergio Ocon - ManageIQ Design Summit 2016ManageIQ
The document outlines the agenda for a ManageIQ design summit, including discussions around the community status, ways to collaborate, and licensing. It provides details on community members and channels for collaboration such as Gitter, forums, and mailing lists. It also notes that ManageIQ has transitioned to using the Apache License 2.0 to be more inclusive of potential contributors and users.
This document discusses DevOps workflows using OpenShift and ManageIQ. It describes using GitLab for source code management, CI/CD, and collaboration. OpenShift is used as a platform for deploying and managing containerized applications. ManageIQ orchestrates provisioning of the DevOps tools including FreeIPA for authentication, GitLab, and OpenShift. The ecosystem is integrated through a CI/CD pipeline that builds, tests, reviews, and deploys code changes from a Git repository to OpenShift.
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.
Using Git/Gerrit and Jenkins to Manage the Code Review ProcessordMarc Karasek
Developers write code and check it into source control systems like Git, CVS, or SVN. The code is then reviewed through a code review tool called Gerrit, which provides a web interface for inline and block comments. A continuous integration server called Jenkins automatically builds any code changes submitted to Gerrit to check for errors or failures. Together, Git, Gerrit, and Jenkins form a development workflow where code review is integrated and the final approved code is built and tested before being committed to the main branch.
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.
Code Review with Git and Gerrit - Devoxx 2011 - Tools in Action - 2011-11-14msohn
The document discusses code review using Git and Gerrit. It describes Git as a distributed revision control system built for facilitating code review. It also discusses how Eclipse is moving to Git and the roles of JGit, EGit, and Gerrit Code Review in implementing Git-based code review in Java projects. Gerrit allows code review workflows by hosting Git repositories and providing access control and review capabilities.
Large Scale Development with Git and Gerrit - EclipseCon Europe 2012msohn
This document discusses using Git and Gerrit for large-scale development at SAP. It describes how SAP migrated large projects like a C++ engine project and Netweaver Cloud platform to use Git and Gerrit. Key aspects covered include setting up a central Gerrit server, introducing code reviews, implementing branching strategies, and establishing quality barriers through Gerrit and testing. The document also provides recommendations for migrating large projects and highlights benefits like improved quality from review and pre-tested commits.
Gerrit is a code review system that tightly integrates with Git. It provides a web-based user interface and API for reviewing changes, managing access control, and integrating with other tools like Jenkins. Key features include fast and easy code reviews, flexible integration options, and tools for managing projects, users, and access control. Gerrit supports code review workflows and allows configuring commit policies and change submission actions.
Community - Carol Chen, Sergio Ocon - ManageIQ Design Summit 2016ManageIQ
The document outlines the agenda for a ManageIQ design summit, including discussions around the community status, ways to collaborate, and licensing. It provides details on community members and channels for collaboration such as Gitter, forums, and mailing lists. It also notes that ManageIQ has transitioned to using the Apache License 2.0 to be more inclusive of potential contributors and users.
This document discusses DevOps workflows using OpenShift and ManageIQ. It describes using GitLab for source code management, CI/CD, and collaboration. OpenShift is used as a platform for deploying and managing containerized applications. ManageIQ orchestrates provisioning of the DevOps tools including FreeIPA for authentication, GitLab, and OpenShift. The ecosystem is integrated through a CI/CD pipeline that builds, tests, reviews, and deploys code changes from a Git repository to OpenShift.
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.
Using Git/Gerrit and Jenkins to Manage the Code Review ProcessordMarc Karasek
Developers write code and check it into source control systems like Git, CVS, or SVN. The code is then reviewed through a code review tool called Gerrit, which provides a web interface for inline and block comments. A continuous integration server called Jenkins automatically builds any code changes submitted to Gerrit to check for errors or failures. Together, Git, Gerrit, and Jenkins form a development workflow where code review is integrated and the final approved code is built and tested before being committed to the main branch.
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.
Code Review with Git and Gerrit - Devoxx 2011 - Tools in Action - 2011-11-14msohn
The document discusses code review using Git and Gerrit. It describes Git as a distributed revision control system built for facilitating code review. It also discusses how Eclipse is moving to Git and the roles of JGit, EGit, and Gerrit Code Review in implementing Git-based code review in Java projects. Gerrit allows code review workflows by hosting Git repositories and providing access control and review capabilities.
Large Scale Development with Git and Gerrit - EclipseCon Europe 2012msohn
This document discusses using Git and Gerrit for large-scale development at SAP. It describes how SAP migrated large projects like a C++ engine project and Netweaver Cloud platform to use Git and Gerrit. Key aspects covered include setting up a central Gerrit server, introducing code reviews, implementing branching strategies, and establishing quality barriers through Gerrit and testing. The document also provides recommendations for migrating large projects and highlights benefits like improved quality from review and pre-tested commits.
Gerrit is a code review system that tightly integrates with Git. It provides a web-based user interface and API for reviewing changes, managing access control, and integrating with other tools like Jenkins. Key features include fast and easy code reviews, flexible integration options, and tools for managing projects, users, and access control. Gerrit supports code review workflows and allows configuring commit policies and change submission actions.
The Road to Continuous Delivery: Evolution Not Revolution Perforce
The document discusses the evolution of Perforce's workflow from a slow and steady development process to a faster and more collaborative continuous delivery model using Git Fusion. Git Fusion allows teams using Git to integrate with Perforce services, enabling continuous integration and delivery. The document provides guidance on setting up a continuous delivery pipeline and releasing artifacts through multiple stages of testing to stabilize before release. Customers can now try out fixes and features as they are developed rather than waiting weeks or months for major releases.
Gerrit is the review software used in the TYPO3 ecosphere.
These slides were used to introduce the participants of the workshop into the Gerrit workflow and the concept of software reviews.
Workshop at the TYPO3 Developer Days Munich, 2012
http://t3dd12.typo3.org
As the popularity of Git grows, questions around security and code quality are moving center stage. Learn why the combination of Git/Gerrit and TeamForge form the industry’s leading enterprise-grade solution to manage Git based development programs, both on-premises and in the cloud.
In this webinar, Johannes Nicolai will provide an overview of Git/Gerrit- and why enterprises choose to use the Git-TeamForge integration for unmatched security, scalability and compliance, as well as introduce and demonstrate the power of Gerrit 2.8 with TeamForge:
How you can ensure meeting regulatory and corporate compliance mandates with TeamForge’s tamper-proof audit trails.
How TeamForge provides 100% history protection for accidentally deleted branches and helps you meet the most stringent compliance standards.
How Git, Gerrit and Jenkins reduces the number of manual code reviews by automatically pre-validating builds via Jenkins.
How to graphically design your own review workflows using CollabNet’s Quality Gate Wizard for Gerrit
You shall not pass - Control your code quality gates with a wizard.Eryk Szymanski
For those of us who does not speak Prolog, there is an easier way to configure your submit rules in Gerrit. The Quality gate wizard lets you to set up your submit rules in less than 3 minutes.
The Evolving Role of Build Engineering in Managing Open SourceDevOps.com
In this webinar, we’ll explore how the role of build engineering is evolving to reconcile two key trends: massive wide-scale adoption of open source; the most devastating cyber-attacks in recent history tied to unpatched dependencies & other vulnerabilities.
Reconciling these trends will enable enterprises to unlock the the potential of open source & mitigate the risks. Further, our expert panelists will dive into how automating build engineering can accelerate your build time to gain you win speed & predictability in your open source language build pipeline and decrease the risk to deployed applications.
Do your users already know how to use Git? Of course they do. Git offers a great workflow, but scalability is a concern. In this talk explore benchmarks comparing the performance of Git and Helix DVCS. See how to use command aliases in Helix Versioning Engine 2016.1 to make Helix look like Git. What could be better than a version control system that works just like Git but doesn't buckle under the weight of your massive assets?
Test-Driven-Development for Networking: Making CI Work for You by Colin McNam...DevOps4Networks
The document discusses how continuous integration (CI) and test-driven development (TDD) can benefit network engineers. It presents an overview of CI/TDD processes and concepts. A key point is that CI/TDD can increase quality, decrease risk, and increase development speed for network operations. The document proposes a maturity model to guide organizations in implementing CI/TDD practices for networking, starting from basic self-service builds and progressing to integrated testing and continuous deployment.
Gerrit & Jenkins Workflow: An Integrated CI Demonstrationvanoorts
This document discusses integrating Gerrit code review with Jenkins automation using Docker containers. It presents a use case of mobile development where Gerrit is used for centralized source and code review, Jenkins for automation and integration, and Repo for cross-repository features. It then introduces using the Gerrit Trigger plugin and Jenkins Workflow together as of August 2015 to handle multiple parallel jobs more cleanly and with built-in concurrency and failure handling options. The demonstration is dockerized using images from Gerritforge and Jenkins to showcase the integration.
Innovation at Perforce never stops. Since the last MERGE conference, there have been continual updates across the board in response to user requests. In this session, we're going to look at what's new and take a peek at what's in the works so that you can start planning to exploit them when they're available.
It’s 2021. Why are we -still- rebooting for patches? A look at Live Patching.All Things Open
Presented by: Igor Seletskiy
Presented at the All Things Open 2021
Raleigh, NC, USA
Raleigh Convention Center
Abstract: IT Teams know the drill. New security bulletins, new issues, new patches to deploy. Schedule another maintenance operation and prepare for system downtime.
There is a better way to do things. Live patching has been around in the Linux Kernel for some time now, but adoption has not been ideal so far - either because of a lack of trust in the technology or just lack of awareness - or sysadmins just enjoy interrupting their workloads or users.
Live patching consists of two aspects. First, there has to be a mechanism for function redirection in the kernel. As in many things, the kernel actually provides three different subset of tools that provide this functionality - kprobes, fprobes and Livepatching. Secondly, Live Patching relies on a set of tools to generate the actual patches to deploy, replacing the old code with new one. This is arguably the most involved part: you need to fit your new code in the proper space, you can’t overwrite other unrelated code and you need to maintain compatibility with other functions. If you change your parameter list, for example, its game over - something will break in the worst possible way.
In this talk we’ll go over issues like Consistency model, patch generation, deployment mechanisms and identify situations that are ideal candidates for live patching instead of traditional patching operations.
Trunk-based development is a workflow where developers work directly on a main branch called the "trunk". The trunk is always in a deployable state. Short lived branches are used for developing new features which are then merged into the trunk after passing tests. Releases are cut from the trunk periodically. This allows for continuous integration and deployment while maintaining a stable release.
The printing press of 2021 - using GitLab to publish the VSHN HandbookAarno Aukia
VSHNs public employee handbook.vshn.ch is created and published using GitLab and GitLab pipelines. In this talk, Aarno will show you the process from Asciidoc sources in the Git repo all the way to being deployed on APPUiO.ch Kubernetes.
[Webinar] The Frog And The Butler: CI Pipelines For Modern DevOpsBaruch Sadogursky
No relationship in DevOps is more important than that between your CI/CD server and your Binary Repository. Jenkins has long been the go-to server for CI/CD, and JFrog Artifactory has long been one of the most popular integrations with it. This webinar focuses on the new features of the integration, leveraging the Jenkins Pipeline DSL for infrastructure-as-code of your favorite artifactory features whether it be generic, maven, gradle or Docker, and will show an end-to-end example of pipelines across multiple technologies and how powerful these new capabilities are.
Jfrog artifactory artifact management c tamilmaran presentation - copyTAMILMARAN C
JFrog Artifactory is an artifact management tool that allows users to store, manage, and distribute software artifacts. It supports all major package formats and integrates with various DevOps tools and technologies. JFrog Artifactory provides a single place to manage binaries for continuous integration and deployment pipelines. It offers features like access control, high availability, security analysis, and integration with tools like Jenkins, Docker, and Kubernetes.
This document provides an overview of Gerrit Code Review, including:
- Gerrit allows code review of commits before they are integrated into branches through a "push for code review" workflow. It creates changes and change refs for pushed commits.
- Changes can be reviewed through the Gerrit web interface by viewing diffs and leaving comments. Reviewers can vote on changes using configurable review labels like "Code-Review".
- The standard workflow involves pushing commits for review, reviewing and voting on changes, and then submitting approved changes to branches. Gerrit integrates with Git and provides access controls and permissions on repositories.
Preventing Supply Chain Attacks on Open Source SoftwareAll Things Open
Supply chain attacks on open source software increased 650% in 2021. Software supply chain attacks occur when adversaries manipulate third-party code to compromise downstream applications. Organizations must map dependencies, monitor for vulnerabilities, and quickly patch issues. A Software Bill of Materials (SBOM) provides visibility into components. OWASP Dependency Track helps generate SBOMs and identify vulnerabilities and license risks in dependencies. Implementing standards like the Supply Levels for Software Artifacts (SLSA) can help secure software supply chains and prevent tampering of artifacts.
Multi-container Applications on OpenShift with the Ansible Service Broker Mul...Amazon Web Services
The Kubernetes/OpenShift Service Catalog and Open Service Broker API are creating a new way for users to provision and manage services on Kubernetes/OpenShift through a collection of Service Brokers. One of these brokers, the Ansible Service Broker, is focused on providing a mechanism for allowing applications defined with Ansible to be exposed to the Service Catalog. We call this application definition an Ansible Playbook Bundle (APB); a lightweight definition that is essentially a few Ansible playbooks named for each of the Open Service Broker API methods. The bundle is packaged as a container image with an Ansible runtime for distribution to be consumed by the Ansible Service Broker. In this talk we will introduce the concept of the Ansible Playbook Bundle and Ansible Service Broker. Additionally, we will walk through a few example and live demo demonstrating how to define and deploy multi-container applications.
Puzzle ITC Talk @Docker CH meetup CI CD_with_Openshift_0.2Amrita Prasad
This document discusses continuous delivery using OpenShift. It begins with an overview of OpenShift v3, including that it is a container platform as a service based on Docker and Kubernetes. It then covers key concepts in continuous integration and continuous delivery like automated database migrations and rolling updates. Finally, it provides an example of setting up a continuous integration/continuous delivery pipeline in OpenShift using Jenkins, including building and deploying a Java/Maven application through various stages.
Buddy, partnered with industry leaders such as Amazon, Docker, Github, Microsoft, and Google, is a winning development automation platform that serves a rapidly growing market valued to become $345 billion by 2022. Over 7,000 developers use Buddy every day across 120+ countries. Featured customers: INC. Magazine, CGI.com & ING Bank. Our vision is to become the backbone on which talented people can build world-altering apps & services. Our goal is to take the load off millions of developers by offloading everything that can be automated – giving them back the time for being creative.
The Road to Continuous Delivery: Evolution Not Revolution Perforce
The document discusses the evolution of Perforce's workflow from a slow and steady development process to a faster and more collaborative continuous delivery model using Git Fusion. Git Fusion allows teams using Git to integrate with Perforce services, enabling continuous integration and delivery. The document provides guidance on setting up a continuous delivery pipeline and releasing artifacts through multiple stages of testing to stabilize before release. Customers can now try out fixes and features as they are developed rather than waiting weeks or months for major releases.
Gerrit is the review software used in the TYPO3 ecosphere.
These slides were used to introduce the participants of the workshop into the Gerrit workflow and the concept of software reviews.
Workshop at the TYPO3 Developer Days Munich, 2012
http://t3dd12.typo3.org
As the popularity of Git grows, questions around security and code quality are moving center stage. Learn why the combination of Git/Gerrit and TeamForge form the industry’s leading enterprise-grade solution to manage Git based development programs, both on-premises and in the cloud.
In this webinar, Johannes Nicolai will provide an overview of Git/Gerrit- and why enterprises choose to use the Git-TeamForge integration for unmatched security, scalability and compliance, as well as introduce and demonstrate the power of Gerrit 2.8 with TeamForge:
How you can ensure meeting regulatory and corporate compliance mandates with TeamForge’s tamper-proof audit trails.
How TeamForge provides 100% history protection for accidentally deleted branches and helps you meet the most stringent compliance standards.
How Git, Gerrit and Jenkins reduces the number of manual code reviews by automatically pre-validating builds via Jenkins.
How to graphically design your own review workflows using CollabNet’s Quality Gate Wizard for Gerrit
You shall not pass - Control your code quality gates with a wizard.Eryk Szymanski
For those of us who does not speak Prolog, there is an easier way to configure your submit rules in Gerrit. The Quality gate wizard lets you to set up your submit rules in less than 3 minutes.
The Evolving Role of Build Engineering in Managing Open SourceDevOps.com
In this webinar, we’ll explore how the role of build engineering is evolving to reconcile two key trends: massive wide-scale adoption of open source; the most devastating cyber-attacks in recent history tied to unpatched dependencies & other vulnerabilities.
Reconciling these trends will enable enterprises to unlock the the potential of open source & mitigate the risks. Further, our expert panelists will dive into how automating build engineering can accelerate your build time to gain you win speed & predictability in your open source language build pipeline and decrease the risk to deployed applications.
Do your users already know how to use Git? Of course they do. Git offers a great workflow, but scalability is a concern. In this talk explore benchmarks comparing the performance of Git and Helix DVCS. See how to use command aliases in Helix Versioning Engine 2016.1 to make Helix look like Git. What could be better than a version control system that works just like Git but doesn't buckle under the weight of your massive assets?
Test-Driven-Development for Networking: Making CI Work for You by Colin McNam...DevOps4Networks
The document discusses how continuous integration (CI) and test-driven development (TDD) can benefit network engineers. It presents an overview of CI/TDD processes and concepts. A key point is that CI/TDD can increase quality, decrease risk, and increase development speed for network operations. The document proposes a maturity model to guide organizations in implementing CI/TDD practices for networking, starting from basic self-service builds and progressing to integrated testing and continuous deployment.
Gerrit & Jenkins Workflow: An Integrated CI Demonstrationvanoorts
This document discusses integrating Gerrit code review with Jenkins automation using Docker containers. It presents a use case of mobile development where Gerrit is used for centralized source and code review, Jenkins for automation and integration, and Repo for cross-repository features. It then introduces using the Gerrit Trigger plugin and Jenkins Workflow together as of August 2015 to handle multiple parallel jobs more cleanly and with built-in concurrency and failure handling options. The demonstration is dockerized using images from Gerritforge and Jenkins to showcase the integration.
Innovation at Perforce never stops. Since the last MERGE conference, there have been continual updates across the board in response to user requests. In this session, we're going to look at what's new and take a peek at what's in the works so that you can start planning to exploit them when they're available.
It’s 2021. Why are we -still- rebooting for patches? A look at Live Patching.All Things Open
Presented by: Igor Seletskiy
Presented at the All Things Open 2021
Raleigh, NC, USA
Raleigh Convention Center
Abstract: IT Teams know the drill. New security bulletins, new issues, new patches to deploy. Schedule another maintenance operation and prepare for system downtime.
There is a better way to do things. Live patching has been around in the Linux Kernel for some time now, but adoption has not been ideal so far - either because of a lack of trust in the technology or just lack of awareness - or sysadmins just enjoy interrupting their workloads or users.
Live patching consists of two aspects. First, there has to be a mechanism for function redirection in the kernel. As in many things, the kernel actually provides three different subset of tools that provide this functionality - kprobes, fprobes and Livepatching. Secondly, Live Patching relies on a set of tools to generate the actual patches to deploy, replacing the old code with new one. This is arguably the most involved part: you need to fit your new code in the proper space, you can’t overwrite other unrelated code and you need to maintain compatibility with other functions. If you change your parameter list, for example, its game over - something will break in the worst possible way.
In this talk we’ll go over issues like Consistency model, patch generation, deployment mechanisms and identify situations that are ideal candidates for live patching instead of traditional patching operations.
Trunk-based development is a workflow where developers work directly on a main branch called the "trunk". The trunk is always in a deployable state. Short lived branches are used for developing new features which are then merged into the trunk after passing tests. Releases are cut from the trunk periodically. This allows for continuous integration and deployment while maintaining a stable release.
The printing press of 2021 - using GitLab to publish the VSHN HandbookAarno Aukia
VSHNs public employee handbook.vshn.ch is created and published using GitLab and GitLab pipelines. In this talk, Aarno will show you the process from Asciidoc sources in the Git repo all the way to being deployed on APPUiO.ch Kubernetes.
[Webinar] The Frog And The Butler: CI Pipelines For Modern DevOpsBaruch Sadogursky
No relationship in DevOps is more important than that between your CI/CD server and your Binary Repository. Jenkins has long been the go-to server for CI/CD, and JFrog Artifactory has long been one of the most popular integrations with it. This webinar focuses on the new features of the integration, leveraging the Jenkins Pipeline DSL for infrastructure-as-code of your favorite artifactory features whether it be generic, maven, gradle or Docker, and will show an end-to-end example of pipelines across multiple technologies and how powerful these new capabilities are.
Jfrog artifactory artifact management c tamilmaran presentation - copyTAMILMARAN C
JFrog Artifactory is an artifact management tool that allows users to store, manage, and distribute software artifacts. It supports all major package formats and integrates with various DevOps tools and technologies. JFrog Artifactory provides a single place to manage binaries for continuous integration and deployment pipelines. It offers features like access control, high availability, security analysis, and integration with tools like Jenkins, Docker, and Kubernetes.
This document provides an overview of Gerrit Code Review, including:
- Gerrit allows code review of commits before they are integrated into branches through a "push for code review" workflow. It creates changes and change refs for pushed commits.
- Changes can be reviewed through the Gerrit web interface by viewing diffs and leaving comments. Reviewers can vote on changes using configurable review labels like "Code-Review".
- The standard workflow involves pushing commits for review, reviewing and voting on changes, and then submitting approved changes to branches. Gerrit integrates with Git and provides access controls and permissions on repositories.
Preventing Supply Chain Attacks on Open Source SoftwareAll Things Open
Supply chain attacks on open source software increased 650% in 2021. Software supply chain attacks occur when adversaries manipulate third-party code to compromise downstream applications. Organizations must map dependencies, monitor for vulnerabilities, and quickly patch issues. A Software Bill of Materials (SBOM) provides visibility into components. OWASP Dependency Track helps generate SBOMs and identify vulnerabilities and license risks in dependencies. Implementing standards like the Supply Levels for Software Artifacts (SLSA) can help secure software supply chains and prevent tampering of artifacts.
Multi-container Applications on OpenShift with the Ansible Service Broker Mul...Amazon Web Services
The Kubernetes/OpenShift Service Catalog and Open Service Broker API are creating a new way for users to provision and manage services on Kubernetes/OpenShift through a collection of Service Brokers. One of these brokers, the Ansible Service Broker, is focused on providing a mechanism for allowing applications defined with Ansible to be exposed to the Service Catalog. We call this application definition an Ansible Playbook Bundle (APB); a lightweight definition that is essentially a few Ansible playbooks named for each of the Open Service Broker API methods. The bundle is packaged as a container image with an Ansible runtime for distribution to be consumed by the Ansible Service Broker. In this talk we will introduce the concept of the Ansible Playbook Bundle and Ansible Service Broker. Additionally, we will walk through a few example and live demo demonstrating how to define and deploy multi-container applications.
Puzzle ITC Talk @Docker CH meetup CI CD_with_Openshift_0.2Amrita Prasad
This document discusses continuous delivery using OpenShift. It begins with an overview of OpenShift v3, including that it is a container platform as a service based on Docker and Kubernetes. It then covers key concepts in continuous integration and continuous delivery like automated database migrations and rolling updates. Finally, it provides an example of setting up a continuous integration/continuous delivery pipeline in OpenShift using Jenkins, including building and deploying a Java/Maven application through various stages.
Buddy, partnered with industry leaders such as Amazon, Docker, Github, Microsoft, and Google, is a winning development automation platform that serves a rapidly growing market valued to become $345 billion by 2022. Over 7,000 developers use Buddy every day across 120+ countries. Featured customers: INC. Magazine, CGI.com & ING Bank. Our vision is to become the backbone on which talented people can build world-altering apps & services. Our goal is to take the load off millions of developers by offloading everything that can be automated – giving them back the time for being creative.
XP teams try to keep systems fully integrated at all times, and shorten the feedback cycle to minutes and hours instead of weeks or months. The sooner you know, the sooner you can adapt.
Watch our record for the webinar "Continuous Integration" to explore how Azure DevOps helps us in achieving continuous feedback using continuous integration.
Building environment of #UserDevOps and not only DevOpsRajnish Chauhan
In so much of IT tools and technology we missed and forgotten the very user and requirement. If requirement are not of high quality , we can not expect the software of quality as quality is not only all about defects & bugs but also if it is usable and meeting the need of user community.
There are many tools and methodology and I have detailed what minimum with one can start UserDevOps transformation and can bring values to business.
DevOps for absolute beginners (2022 edition)Ahmed Misbah
Are you planning to pursue a career in DevOps?
Already working with DevOps but want to know what’s new in 2022?
This session is for you!
Join us in the 2022 edition of “DevOps for absolute beginners” session, where you will learn all about DevOps from the perspective of People, Process, and Technology. We will be talking about topics like Automation, Continous Integration, Continous Delivery, Infrastructure as Code, etc. We will also be talking about the latest trends in DevOps, including Chaos Engineering, MLOps, and eBPF.
The session will conclude with great bonus material for software professional enthusiastic about DevOps, one of them being a carefully crafted learning path for DevOps from years of experience in the industry. Don’t miss out on the rest of the material.
Although not an entirely new concept, Platform Engineering and Internal Developer Platforms (IDPs) are all the rage due to their potential to increase development velocity and deployment frequency while boosting reliability and security.
Join Joe Dahlquist, VP of PMM and Mohamed Ahmed, VP of Developer Platforms at Weaveworks to learn the 6 tell-tale signs your company should implement a platform engineering approach. The webinar draws on hundreds of conversations with SRE’s, developers, and platform engineering teams to help you better understand what works, what doesn’t and what might be missing from your strategy. Attendees can apply these learnings to their first (or next) developer platform regardless of your build vs. buy journey.
You will learn:
* The difference between Internal Developer Platforms and Platform Engineering
* Why platform engineering now?
* How Dev and Ops benefit from an IDP
* 6 tell-tale signs to start platform engineering
* Drafting your platform engineering strategy - where to begin and what to avoid
Dashlane Triple Track : à la recherche de la bonne organisation - Agile en Se...Agile En Seine
Présenté par Frédéric Rivain, Dashlane
L'histoire Agile de Dashlane : comment nous avons évolué et itéré sur notre organisation, depuis les premiers jours de la start-up jusqu'au modèle actuel à triple track, pour nous adapter aux besoins de notre entreprise, ainsi que la façon dont nous avons fini par aborder les investissements techniques au fur et à mesure des évolutions du produit et de l'entreprise.
Frédéric Rivain, CTO - Scaling Identity | Tech Agilist, Dashlane
Frederic is the CTO of Dashlane, passionate about scaling Digital Identity. He joined Dashlane after several years working in Gaming, Gambling and eCommerce. He is eager to learn, innovate and have fun with his team, so that Engineering can efficiently support the Dashlane business and offer the best service to Dashlane users.
Data integration case study: Oil & Gas industryETLSolutions
This document discusses a data integration project for an oil and gas company. The company needed a framework to integrate data from multiple sources into their new software product based on the PPDM data standard. The solution involved using the Transformation Manager software and consulting services from ETL Solutions to develop export components mapping PPDM data to LAS, DLIS and WITSML formats. The project was divided into design, development and testing phases to successfully deliver the integration framework.
This document provides an overview and agenda for a webinar on continuous delivery in the enterprise. The webinar will define continuous delivery and differentiate it from continuous integration, Agile, quality and DevOps practices. It will explore the continuous delivery pipeline and key aspects like continuous development, integration and the ability to continuously release software. Attendees will learn about their role in continuous delivery and why it is important. The webinar will also discuss tools, products and solutions for continuous delivery and include case studies. It aims to explain how organizations can adopt continuous delivery practices.
MuleSoft Surat Virtual Meetup#17 - Automated Code ReviewJitendra Bafna
This document provides information about an upcoming MuleSoft Meetup event on automated code review. It introduces the organizers and speakers for the event and provides an agenda. The event will discuss how automated code review can help improve code quality and efficiency by reducing the time spent on manual reviews and bug fixes. It will introduce the IZ Analyzer tool, which allows configuring rules to automatically analyze code quality and conformance to standards.
Efficient platform engineering with Microk8s & gopaddle.pdfVinothini Raju
This document discusses the evolution of DevOps and platform engineering challenges. It introduces gopaddle as a low-code DevSecOps platform for Kubernetes that can provide automated multi-cloud provisioning, issue identification, and app release automation. Using MicroK8s and the gopaddle Lite addon allows setting up a platform in 15-20 minutes, improving efficiency and reducing time to develop and deploy microservices compared to traditional methods.
This document discusses transforming monolithic applications into microservices using Docker and the 12 factor app methodology. It begins by describing the issues with monolithic applications and how Docker can help transform them. It then covers the key aspects of building applications for scale, including portability, horizontal scalability, automation, traceability, and robust deployments. Finally, it details the twelve factors of building 12 factor apps and provides both dos and don'ts for applying each factor when transforming applications.
Discover the key technical skills that top tech companies seek in software developers. Learn how to up-level your career and become a highly valued professional in the competitive world of software engineering.
This document discusses DOTSOFT's technological framework for developing projects into products. It outlines DOTSOFT's history and services and describes some common problems in software development like changing requirements and communication gaps. It then details the components of DOTSOFT's agile development cycle including source control, issue tracking, continuous integration, testing, and programming languages and frameworks used like PHP, GIT, Jenkins, and Jinx. The cycle aims to provide robust, portable, and documented code through practices like distributed version control, unit testing, and reusable development environments.
Training Bootcamp - MainframeDevOps.pptxNashet Ali
Cloud Migration services from your on-premise environment can sometimes be very simple and other times an extremely complicated project to implement. For either scenario, there are always considerations to bear in mind when doing so. This course has been designed to highlight these topics to help you ask the right questions to aid in a successful Cloud migration.
Within this course, we look at how timing plays an important part in your project's success and why phased deployments are important. Security is also examined where we focus on a number of key questions that you should have answers to from a business perspective before your Cloud migration. One of the biggest decisions is your chosen public cloud vendor, how do you make the decision between the available vendors, what should you look for when selecting you will host your architecture, this course dives into this question to help you finalize your choice.
Understanding the correct deployment model is essential, it affects how you architect your environment and each provides different benefits, so gaining the knowledge. I look at how you can break this question down to help you with your design considerations. We also cover service readiness from your on-premise environment and how to align these to the relevant Cloud services. Your design will certainly be different from your on-premise solution, I discuss the best approach when you start to think about your solution design, some of the dos and some of the don’ts.
Once you have your design, it’s important to understand how you are actually going to migrate your services ensuring optimum availability and minimal interruption to your customer base, for example looking at Blue/Green and Canary deployments. Cloud migration allows for some great advantages within your business continuity plans, as a result, I have included a lecture to discuss various models that work great within the Cloud.
Course Objectives
By completing this course you will:
Have greater visibility of some of the key points of a cloud migration
Be able to confidently assess the requirements for your migration
Intended Audience
This course has been designed for anyone who works or operates in business management, business strategy, technical management, and technical operations.
Prerequisites
For this course, it's assumed that you have a working knowledge of cloud computing and cloud principles.
What You Will Learn about Cloud Migration
Introduction - This provides an introduction to the trainer and covers the intended audience. We will also look at what lectures are included in the course, and what you will gain as a student from attending the course.
Time Management – How time plays an important part in successful cloud migration. We discuss the key points to allow time for and how to use it to plan a phased migration.
Security – This lecture will give you the ability to ask the key security questions to the business before performing a migration to the Cloud.
Production-Ready Kubernetes: It's Not About TechnologyAntoine Craske
Adopting cloud-native technologies can seem like a technological challenge, but it's far from being the only theme.
The organization, culture and people aspects is the main challenge to overcome resistance to change, drive value creation and accelerate the transformation.
This talk shares our journey in adopting a Cloud-native application stack with a Kubernetes PaaS, focusing on the transformation journey.
Accelerating DevOps at the SF DevOps MeetUpjwi11iams
The Codenvy slide presentation given on September 28, 2015 at the SF DevOps MeetUp. This talk covered Codenvy's journey to continuous development and how Codenvy helps accelerate DevOps though increasing code commits and feedback iterations.
Similar to Code Management and Promotion (DDT) - Jason Cornell - ManageIQ Design Summit 2016 (20)
This document summarizes the Sprint 235 review meeting for the ManageIQ project. The meeting covered bug fixes and enhancements to the UI, providers, and platform. Key items discussed included fixing various tests, adding provider details to screens, updating container base images, and removing Gemfile locks from shipped gems. The sprint review wrapped up with questions and confirmation of the next sprint review meeting.
This document summarizes the Sprint 234 review meeting which took place on April 3, 2024. The meeting covered UI fixes and enhancements by Jeffrey Bonson, provider updates by Adam Grare, and platform changes by Joe Rafaniello such as adding region counts to audit reporting and upgrading dependencies. Bugs addressed include tagging and workflow credential issues while enhancements included updating UI components. Questions were invited for discussion with the next Sprint 235 review scheduled for April 17, 2024.
The document summarizes the Sprint 233 review meeting held on March 20, 2024. It includes:
- An overview of the meeting agenda and speakers for UI, Providers, and Platform updates
- Details of bugs fixed and enhancements implemented across the UI, Providers, and Platform areas during the sprint
- Questions and information about the next Sprint 234 review meeting
This document summarizes the Sprint 232 review meeting of March 6, 2024. The meeting covered bug fixes and enhancements to the UI, providers, and platform. Four speakers presented updates: Jason Frey provided an overview, Jeffrey Bonson discussed UI improvements, Adam Grare reviewed provider changes, and Joe Rafaniello outlined platform enhancements. Bugs addressed included hostname errors and incorrect action values. Enhancements included search bars and React conversions. Changes to Amazon, Kubernetes, Kubevirt, Ansible Tower, Cisco Intersight, and Workflows were also noted.
The document summarizes the Sprint 231 review meeting of the ManageIQ platform. It includes:
1. An overview of the meeting agenda covering UI, Providers, Platform, and API updates.
2. Details on bugs fixed and enhancements made to the UI, Providers, and Platform.
3. Questions from attendees and information on the next Sprint 232 review meeting.
This document summarizes the Sprint 230 review meeting for the ManageIQ project. The meeting covered bugs and technical debts across the UI, Providers, and Platform teams. Bugs included errors on EMS network text, service catalog errors, and typos. Technical debts addressed PR templates and catalog resources. Provider updates involved zones, snapshots, and targeted refreshes. Platform discussed container versions, Ruby/Rails upgrades, messaging, and role enabling. The next Sprint 231 review was scheduled.
This document summarizes the Sprint 229 review meeting for the ManageIQ project. It includes sections on bugs and enhancements for the UI, Providers, and Platform teams. The meeting discussed 6 bugs and 13 enhancements fixed in the UI, issues addressed for Ansible Tower, Floe, and Workflows providers, and improvements to orchestrator certificates, gem management, translations and testing for the Platform team. It concluded with next steps for the Sprint 230 review meeting.
The Sprint 228 Review meeting covered:
1. Bugs and enhancements completed during the sprint for the UI, providers, platform, and workflows. This included 6 UI bugs fixed and 3 UI enhancements completed.
2. Upcoming work for providers including deleting disks for failed clones on Google and moving feature checks to subclasses for Ovirt and VMware.
3. Platform enhancements and bugs including mounting messaging certificates, Kafka configuration, and Ruby 3.1 support.
This document summarizes the Sprint 227 review meeting. The meeting covered bug fixes and enhancements for the UI, providers, and platform. For the UI, issues addressed included permission fixes, error handling, and accessibility. Provider updates included dropping dependencies and pagination fixes. For the platform, changes involved removing a default feature and updating apt packages. The next Sprint 228 review is scheduled for January 10, 2023.
The Sprint 226 review meeting covered:
1. Bugs fixed in the UI, providers, and platform areas.
2. Enhancements made to the UI, providers, and platform including code updates.
3. Provider changes including updating Azure and VMware integrations.
The Sprint 225 Review meeting covered updates from the UI, Providers, and Platform teams. Key items included:
- The UI team fixed various bugs relating to missing toast notifications, accessibility issues, and table headers. They also updated JSON files and dropped Ruby 2.7 support.
- The Providers team refactored Amazon region specs and added AWS region syncing. For Nuage, they reverted the Xlab-si org name. Floe provider work included validation, error handling, and test improvements.
- The Platform team enhanced worker handling, added Ruby 3 support, updated translations, fixed messaging and gems, and removed unnecessary code.
The Sprint 224 review meeting covered:
1. An overview was provided by Jason Frey.
2. David Resende discussed fixes and enhancements to the UI, including refactoring components and introducing Ansible playbook payloads.
3. Adam Grare discussed provider updates, including fixing API pagination issues for Google and updating regions for Amazon.
4. Joe Rafaniello provided an update on platform work, including adding new resource pool attributes and dropping unused tools.
5. Keenan Brock noted an enhancement to the API involving dropping a lifecycle event table.
The document summarizes the Sprint 223 review meeting which took place on October 18, 2023. It includes sections on Bugs, UI, Providers, Platform, and API. Key details discussed include fixes to the UI to display alert descriptions and chargeback rates, provider specification additions and fixes for Lenovo, Oracle Cloud, and Redfish, workflow improvements for Floe, and platform enhancements around automation jobs and Ruby/Python support. The meeting concluded with questions and an announcement of the next Sprint 224 review on November 1, 2023.
The document summarizes the Sprint 222 review meeting for the ManageIQ project. It includes sections for UI, Providers, Platform, API, and questions. Key topics discussed were the recent Petrosian-1 release, several bug fixes and enhancements across UI, Providers, and Platform areas, and upcoming meetings.
This document summarizes the Sprint 221 review meeting which took place on September 20, 2023. The meeting covered bug fixes and enhancements across various components including the UI, providers, and platform. Specific issues that were addressed included fixing tenants list viewing, adding sorting options to chargeback, and converting collection forms from HAML to React. Presenters also provided updates on IBM CIC, Openstack, VMware, workflows, upgrading dependencies, and dropping Ems destroy callbacks. The next sprint review is scheduled for October 4, 2023.
The document summarizes the Sprint 220 review meeting that took place on September 6th, 2023. It discusses bugs, enhancements, and work done on the UI, providers, and platform during the sprint. Bugs addressed include package lockdowns, notification refactors, CI fixes. Enhancements included automate method conversions and chargeback rate tests. Work on providers focused on VMware and Amazon updates. Platform work involved messaging, Zeitwerk, certificates, and container upgrades. Questions were invited for discussion before information on the next sprint review.
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Fueling AI with Great Data with Airbyte WebinarZilliz
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Trusted Execution Environment for Decentralized Process MiningLucaBarbaro3
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Your One-Stop Shop for Python Success: Top 10 US Python Development Providersakankshawande
Simplify your search for a reliable Python development partner! This list presents the top 10 trusted US providers offering comprehensive Python development services, ensuring your project's success from conception to completion.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
3. 3
Who is Cox Automotive?
Our Vision
To transform the way the world
buys, sells and owns cars.
Our Mission
To provide key solutions that
create greater efficiencies in the
automotive ecosystem.
Our Values
Our employees drive the growth
of our business and strengthen
our leadership position in the
industry.
Our Heritage
A subsidiary of 116-year-old Cox
Enterprises Inc., one of the
world’s largest privately owned
communications, media and
automotive services companies.
4. 4
Challenges to Automation Development
• Code (methods, dialogs, buttons, etc) are not in a repository
• Developer must cut-n-paste code from IDE into the UI
• Difficult to track development
• Easy to step on another developer’s changes if not careful
• Difficult to keep code synchronized between multiple
environments
• No easy method to promote code from development into
production
5. 5
Solution
Introducing the ManageIQ Developer Deployment Toolkit (DDT). The
toolkit includes custom developed helper tools as well as integrations
with:
• Git: all code/configuration data
• Deployment Automation: Ansible
• IDE: RubyMine
7. 7
What is the Developer Deployment Toolkit?
Quick demo of basic edit and push to developer’s lab appliance
8. 8
What are the benefits of DDT
• Ability to follow software development practices
• Develop local via your favorite IDE
• Commit and push your changes
• Ruby gem cf_ddt updates the MIQ server on push
• Can run unit test right after MIQ updates
• Ability to rapidly revert back if issues
9. 9
Demo of creating a new branch
• Bring MIQ customizations into code management with Git
• 7 different stores, Datastore (automate), Buttons, Dialogs, Service
Catalogs, Customization Templates, Roles
10. 10
Rapid Code Promotion or Rollback
• Merge is done at the Git level
• Process is no different from daily dev
• Merge/promote/push to master branch
• cf_ddt updates MIQ Production server with master branch
• Rollback (restore from Git) if needed
11. 11
Review Challenges to Automation Development
• Code (methods, dialogs, buttons, etc) are not in a repository
• Developer must cut-n-paste code from IDE into the UI
• Difficult to track development
• Easy to step on another developer’s changes if not careful
• Difficult to keep code synchronized between multiple
environments
• No easy method to promote code from development into
production
12. 13
Conclusion
• DDT brings ManageIQ customization components into code
management
• Maintain state with branches
• Code locally, deploy to targeted ManageIQ server
• Code rollback and regression testing
• Rapid code promotion with low risk
13. 14
Current and Future State
• Development and testing ~80% completed
• Want to perform unit testing via integration testing
• Want to enable nightly/weekly automation builds
• Plan to publish to the MIQ Depot very soon
• How does this align with MIQ vision?
• Is anyone interested in helping complete/expand these
capabilities?
• What else can we enable with this functionality?
14. Thank you!
JD Calder
JD.Calder (at) coxautoinc.com
Jason Cornell
Jason.Cornell (at) coxautoinc.com
Daniel Garcia
Daniel.Garcia (at) coxautoinc.com
15