Lets git together

May 26, 20150 likes365 views

This document discusses Git strategies for teams. It outlines several branching strategies including "wing and a prayer", long-running branches, Git flow, and branch-per-feature. Git flow uses long-running branches with specific rules for features, hotfixes, bugs, and only merging develop branches to master once stable. Branch-per-feature creates a new branch for each feature or change and nothing is merged until production deployment. The document also discusses automation, team composition, environments, and selection criteria to consider when choosing a branching strategy.

Let’s Git Together
GIT STRATEGIES FOR TEAMS

Me: Scott Coldwell
‣ DevOps
‣ Computer Know How
‣ Houston, TX
‣ @scottcoldwell
‣ CF dev since 2006
‣ Git since 2013
‣ 2nd ever tech presentation

‣ DO IT
‣ Track changes
‣ Backups
‣ Manage deployments
Source Control

‣ COMMUNICATION
‣ Standards
‣ Process
‣ Expectations
Source Control

‣ Branching!
‣ Forking!
‣ Pull requests!
‣ Distributedness!
‣ Conﬂicts!
‣ Other SC systems had (most of) these too!
The Blessings of Git

‣ Team makeup and competency
‣ Will you be the bottleneck?
‣ Who will approve code promotion?
‣ How much do you trust your developers?
Selection Criteria

‣ Business and/or Project process
‣ Ticketing system and workﬂow
‣ Environments - testing / staging / qa / ci / beta / etc
‣ Deployment process and schedule
‣ Automation (Continuous Integration/Delivery)
Selection Criteria

‣ Wing and a Prayer
‣ Long-Running Branches
‣ Git Flow
‣ Branch-per-Feature
Strategies

‣ Single Branch
‣ Commit when you want to
‣ Deploy with tags?
‣ Careful
‣ Unﬁnished code could creep in
‣ Unclear what’s in production
Wing and a Prayer

‣ One branch for development, one for production
‣ Cherry pick commits to deploy
‣ Tag production branch
‣ Cleaner history in Git than SVN
Long Running Branches

‣ Careful:
‣ Branches will diverge
‣ Not developing on production code
‣ Tedious to keep track of commits for a change
‣ Cumbersome to revert
Long Running Branches

‣ Long-running branches, but with merging
‣ Speciﬁc branches and rules around features,
hotﬁxes, bugs
‣ EVERYTHING in the develop branch WILL be
merged to master, once it is stable
‣ Pull requests are powerful
Git Flow

http://lanziani http://lanziani.com/slides/gitﬂow/images/
gitﬂow_1.png.com/slides/gitﬂow/images/gitﬂow_1.png

‣ Powerful for fast-moving teams
‣ Great separation between dev and prod
‣ Many toolsets available
‣ Much responsibility given to developers
Git Flow Pros

‣ Much responsibility given to developers
‣ Hard to pull stuff back
‣ Frustrating for project managers
‣ Limited number of environments
Git Flow Cons

‣ Master represents production
‣ Every feature and hotﬁx gets a branch
‣ Nothing is merged until prod deployment
‣ Utilize “throw away” branches for various
environments
‣ A build process reruns when branches are added/
removed
Branch per Feature

‣ Allows for limitless environments
‣ Restrict who can merge to master
‣ Granular control over code progression
‣ Easy to remove branches from an environment
‣ We can always deploy
BPF Pros

‣ Code conﬂicts can be tricky to track down
‣ Requires some automation
‣ Pull requests are used less frequently
‣ Training for team
BPF Cons

‣ Git Flow
‣ http://nvie.com/posts/a-successful-git-branching-model/
‣ http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-ﬂow/
‣ Branch per Feature
‣ https://www.acquia.com/blog/pragmatic-guide-branch-
feature-git-branching-strategy
‣ http://dymitruk.com/blog/2012/02/05/branch-per-feature/
Further Reading

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

GitLab: One Tool for Software Development (2018-02-06 @ SEIUM, Braga, Portugal)Pedro Moreira da Silva

Aimed at students of Universidade do Minho, in Portugal, this talk focused on answering the following questions: • What's GitLab and how did it came to be? • What's our tech stack? • How does it enhance tech education around the world? • What are the advantages of GitLab for students? GitLab is a product that covers the entire software development lifecycle. We gave a demo and showed how easy is it for students to start using the tools, workflow, and best practices that they'll be using at their future job. Event: SEIUM 2018 (https://www.facebook.com/events/276872629501903/) Date: February 6, 2018 Location: Universidade do Minho, Braga, Portugal Thanks to Filipa Lacerda, André Luís, and Job van der Voort

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

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

What's New in GitLab and Software Development TrendsNoa Harel

GitLab Frontend and VueJS at GitLabFatih Acet

Case Study: Migration to GitLab (from Bitbucket) at AppsFlyerNoa Harel

AppsFlyer migrated from BitBucket to GitLab for their 150 users and 680 repositories. They wanted to leave the hosted BitBucket solution due to API call limits and latency. The migration process involved converting repositories from Mercurial to Git, setting up the GitLab architecture on Amazon Web Services with an EFS file system, educating teams, and creating custom tooling like a Python script to notify Slack. Lessons learned included issues restoring backups and increasing Unicorn workers. The full technical details are available at the provided URL.

GitLab webcast - Release 8.4GitLab, Inc

Flex and .NET Integrationicaraion

Lesson Learned: Transforming from ClearCase to GitNoa Harel

Git & GitLabGaurav Wable

Introducing GitLab (September 2018)Noa Harel

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

GitLab 8.5 Highlights and Step-by-step tutorialHeather McNamee

Introducing GitLab (June 2018)Noa Harel

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

Intro to Git for Project ManagersOyeLabs

Git is a free and open source distributed version control system that allows for collaboration through features like tracking changes, managing versions, and reverting files. It works across operating systems and programming languages. Git uses a local repository that can be synced and shared through remote repositories on services like GitHub and GitLab. Branches allow for parallel development and features like commits, cloning, and pull requests help track changes.

Git WatchWilliam Narmontas

Git Watch provides continuous deployment by monitoring a Git repository for changes and immediately deploying those changes, without requiring a continuous integration service. This middle ground approach only requires an internet connection for the Git repository and Git Watch server. Some examples of use cases include deploying a static GitHub repository to Firebase Hosting in under 20 seconds, deploying local static content changes in under 5 seconds, and deploying a Scala application to production in about 30 seconds after tests pass on commit. Git Watch allows for frequent, immediate deploys with little overhead.

Git in the Enterprise: How to succeed at DevOps using Git and a monorepoGina Bustos

Join GitLab VP of Product Job van der Voort and Perforce VP of Community Matt Attaway to hear lessons learned from their customers on how to succeed with DevOps using Git and a monorepo. In this webinar we'll discuss: - Approaches for managing teams and projects using Git - Techniques for handling issue tracking across dependent projects - Methods for automating testing and deployment - Strategies for bringing enterprise scale, cross-project visibility and security to teams using Git

Gitlab CI/CDJEMLI Fathi

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

Evolution of GitLab FrontendFatih Acet

Bringing Pull Request to GerritEryk Szymanski

Sprachsteuerung mit dem Google Assistant – Add a new User Interface to your P...inovex GmbH

„Computer, Tee, Earl Grey, heiß“ Jeder Star-Trek-Fan wird dieses Zitat kennen, mit dem Capt. Picard sich regelmäßig sein Lieblingsgetränk replizieren lässt. Die Sprachsteuerung von Computern und Maschinen ist fester Bestandteil vieler Science-Fiction-Szenarien. Daher ist es auch nicht verwunderlich, dass schon mehrere Versuche unternommen wurden, diese Technologie zu etablieren, mit eher durchschnittlichem Erfolg. Allerdings deutet sich aktuell ein großer Fortschritt in der Entwicklung von Sprachsteuerungen an, die sich am deutlichsten in der Inkarnation von Geräten wie Amazon Echo oder Google Home darstellt. In der Session zeigen wir die prinzipielle Funktionsweise einer Sprachsteuerung, die Vergleichbarkeit mit Chatbots, und erweitern einen bestehenden Dienst um ein Voice-User-Interface. Dabei zeigen sich die Besonderheit dieser Benutzerschnittstelle im Vergleich zu grafischen Interfaces und die Herausforderungen, die damit verbunden sind. Event: MobileTech Conference 2017 Datum: 15.03.2017 Speaker: Dominik Helleberg, inovex GmbH Weitere Tech-Vorträge unter https://www.inovex.de/de/content-pool/vortraege/

Gitops: the kubernetes waysparkfabrik

GitOps è un nuovo metodo di CD che utilizza Git come unica fonte di verità per le applicazioni e per l'infrastruttura (declarative infrastructure/infrastructure as code), fornendo sia il controllo delle revisioni che il controllo delle modifiche. In questo talk vedremo come implementare workflow di CI/CD Gitops basati su Kubernetes, dalla teoria alla pratica passando in rassegna i principali strumenti oggi a disposizione come ArgoCD, Flux (aka Gitops engine) e JenkinsX

TuleapCon 2019. DevOps in TuleapTuleap

Thomson Reuters, TMS: Workflow in GitLabMatan Keidar

The document describes Thomson Reuters' use of GitLab for software development workflows. Some key features of GitLab used include issue tracking, merge requests, code reviews, continuous integration via Jenkins, and Slack integration. The typical life cycle of a feature involves a developer pulling an issue, creating a merge request with code changes, undergoing code review and testing, and merging into the master branch if approved. This process aims to prevent bugs and encourage knowledge sharing while keeping the team aware of the project status.

Intro to git and git hubJasleenSondhi

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.

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.

Building GitLab🌍 Job van der Voort

GitLab has grown from 5 employees in 2014 to over 262 employees today while being fully remote. They have no offices and everything is open source, including their business processes and policies. Being fully remote and open source allows GitLab to hire the best talent worldwide, have over 1,900 contributors, and get work done through asynchronous work, requiring everyone to contribute, offering unlimited vacation, and spending time bonding as a team.

Lightweight continuous delivery for small schoolsCharles Fulton

In a continuous delivery environment web application updates are pushed out fast and frequently. Implementing that environment requires many different pieces: version control, automated testing, and automated deployment. It’s a lot to wrap your head around, but there are tangible benefits for small schools, including new opportunities to collaborate among institutions or with student developers. In this presentation we will demonstrate how to build a lightweight continuous integration and delivery stack using free and open source tools: GitLab for version control, GitLab CI and Docker for testing, and Docker and Capistrano for deployment. We will walk through how each piece is separately important and how combining them creates a simple yet powerful deployment strategy. We will also describe concrete examples of how we are using these tools to share application development with students and each other.

Understanding the GitOps Workflow and CICD Pipeline - What It Is, Why It Matt...Gibran Badrulzaman

Travelio Tech Talks 2022 presentation The recommended workflow for implementing GitOps with Kubernetes manifests is known as trunk-based development. This method defines one branch as the "trunk" and carries out development on each environment in a different short-lived branch. When development is complete for that environment, the developer creates a pull request for the branch to the trunk. Developers can also create a fork to work on an environment, and then create a branch to merge the fork into the trunk. Once the proper approvals are done, the pull request (or the branch from the fork) gets merged into the trunk. The branch for that feature is deleted, keeping your branches to a minimum. Trunk-based development trades branches for directories. You can think of the trunk as a "main" or primary branch. production and prod are popular names for the trunk branch. Trunk-based development came about to enable continuous integration and continuous delivery by supplying a development model focused on the fast delivery of changes to applications. But this model also works for GitOps repositories because it keeps things simple and more in tune with how Kustomize and Helm work. When you record deltas between environments, you can clearly see what changes will be merged into the trunk. You won’t have to cherry-pick nearly as often, and you’ll have the confidence that what is in your Git repository is what is actually going into your environment. This is what you want in a GitOps workflow.

Weave GitOps 2022.09 Release: A Fast & Reliable Path to Production with Progr...Weaveworks

Weave GitOps 2022.09 Features Launch Event The latest release of Weave GitOps introduces new features enabling progressive delivery, policy as code, and accelerated application onboarding. Weave GitOps is the leading full-stack GitOps platform to automate trusted application delivery and secure infrastructure operations on premise, in the cloud and at the edge. Trusted by Customers, including Deutsche Telekom and The Department of Defense, Platform and Application Teams, Weave GitOps unlocks the benefits of increased efficiency and compliance, while boosting deployment velocity and confidence. Join us where we’ll do a live demo of Weave GitOps showcasing: - Advanced Deployment Patterns—Progressive Delivery has never been easier - Multi-tenancy and Application Portability—More collaboration and control - Strengthened GitOps Security—If you can code it, you can secure it.

More Related Content

What's hot (20)

Flex and .NET Integrationicaraion

Lesson Learned: Transforming from ClearCase to GitNoa Harel

Git & GitLabGaurav Wable

Introducing GitLab (September 2018)Noa Harel

GitLab 8.5 Highlights and Step-by-step tutorialHeather McNamee

Introducing GitLab (June 2018)Noa Harel

Intro to Git for Project ManagersOyeLabs

Git WatchWilliam Narmontas

Git in the Enterprise: How to succeed at DevOps using Git and a monorepoGina Bustos

Gitlab CI/CDJEMLI Fathi

Evolution of GitLab FrontendFatih Acet

Bringing Pull Request to GerritEryk Szymanski

Sprachsteuerung mit dem Google Assistant – Add a new User Interface to your P...inovex GmbH

Gitops: the kubernetes waysparkfabrik

TuleapCon 2019. DevOps in TuleapTuleap

Thomson Reuters, TMS: Workflow in GitLabMatan Keidar

Intro to git and git hubJasleenSondhi

It's all about feedback - code review as a great tool in the agile toolboxStefan Lay

Building GitLab🌍 Job van der Voort

Lightweight continuous delivery for small schoolsCharles Fulton

Flex and .NET Integrationicaraion

Lesson Learned: Transforming from ClearCase to GitNoa Harel

Git & GitLabGaurav Wable

Introducing GitLab (September 2018)Noa Harel

GitLab 8.5 Highlights and Step-by-step tutorialHeather McNamee

Introducing GitLab (June 2018)Noa Harel

Intro to Git for Project ManagersOyeLabs

Git WatchWilliam Narmontas

Git in the Enterprise: How to succeed at DevOps using Git and a monorepoGina Bustos

Gitlab CI/CDJEMLI Fathi

Evolution of GitLab FrontendFatih Acet

Bringing Pull Request to GerritEryk Szymanski

Sprachsteuerung mit dem Google Assistant – Add a new User Interface to your P...inovex GmbH

Gitops: the kubernetes waysparkfabrik

TuleapCon 2019. DevOps in TuleapTuleap

Thomson Reuters, TMS: Workflow in GitLabMatan Keidar

Intro to git and git hubJasleenSondhi

It's all about feedback - code review as a great tool in the agile toolboxStefan Lay

Building GitLab🌍 Job van der Voort

Lightweight continuous delivery for small schoolsCharles Fulton

Similar to Lets git together (20)

Understanding the GitOps Workflow and CICD Pipeline - What It Is, Why It Matt...Gibran Badrulzaman

Weave GitOps 2022.09 Release: A Fast & Reliable Path to Production with Progr...Weaveworks

Git essential training & sharing selfChen-Tien Tsai

Git provides several advantages over SVN including faster operations, cheaper branching and merging, and a distributed model. It allows for multiple workflows including creating branches for experimental work or bug fixes. Commits, trees, blobs, and tags provide integrity for file versions and changes. Pull requests enable collaboration across remote repositories. Migrating to Git from SVN and using tools like SubGit can help transition repositories.

Next Level DevOps Implementation with GitOpsRamadoni Ashudi

The document summarizes Ramadoni Ashudi's upcoming presentation on "Next Level DevOps Implementation with GitOps" at the GNOME Asia Summit 2021. The presentation will cover What is DevOps, What is GitOps, GitOps principles, how GitOps works, advantages of GitOps, best practices, and GitOps tools. It will include a demo of a GitOps workflow using tools like Argo CD, Kustomize, Jenkins, Docker Hub, GitHub and Kubernetes.

GitOps, Driving NGN Operations Teams 211127 #kcdgt 2021William Caban

Introduction to git & githubVinothini KadambavanaSundaram

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

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

KubeCon EU 2022 Istio, Flux & Flagger.pdfWeaveworks

Distributed Proxies have opened the floodgates for Service Meshes to provide substantial value at the Application Networking Layer, but early adopters of Service Meshes are often overwhelmed by operational complexities. How do you ensure that the proxy is distributed everywhere your software runs? How do you safely upgrade or roll back all those proxies? How can you ensure that your network config is correct - without pushing it to production and risking an outage? Following the GitOps Principles is key to simplifying Service Mesh Operations. Defining the entire service mesh declaratively - be it installation, proxy injection, or configuration - provides a mechanism to safely manage the complexities of a service mesh. Continuously reconciling declarative config with the latest service mesh release keeps you from being caught off-guard by CVEs. Progressive Delivery tools enable seamless movement from one version of a service mesh to another - and back - with minimal impact to traffic.

Distributed Versioning Tools, BeJUG 2010Pursuit Consulting

DevOps Service | MindtreeAnikeyRoy

GitLab is a popular DevOps platform that provides an ecosystem for code management, release management, and continuous integration and delivery (CI/CD) pipelines. This document discusses implementing DevOps using the GitLab ecosystem, including its tools, branching strategies, and designing a GitLab-based DevOps implementation. It provides an overview of the key GitLab tools and interfaces for users, and describes best practices for areas like source code management, continuous integration, monitoring, and security.

Room 2 - 4 - Juncheng Anthony Lin - Redhat - A Practical Approach to Traditio...Vietnam Open Infrastructure User Group

WTF is GitOps and Why You Should Care?Weaveworks

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.

WTF is GitOps & Why Should You Care?All Things Open

Presented at Open Source 101 2022 Presented by Priyanka Ravi, Weaveworks Abstract: 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!

Continuous Lifecycle London 2018 Event KeynoteWeaveworks

Today it’s all about delivering velocity without compromising on quality, yet it’s becoming increasingly difficult for organisations to keep up with the challenges of current release management and traditional operations. The demand for developers to own the end-to-end delivery, including operational ownership, is increasing. A “you build it, you own it” development process requires tools that developers know and understand. So I’d like to introduce “GitOps”- an agile software lifecycle for modern applications. In this session, I will discuss these industry challenges, including current CICD trends and how they’re converging with operations and monitoring. I’ll also illustrate the GitOps model, identify best practices and tools to use, and explain how you can benefit from adopting this methodology inherited from best practices going back 10-15 years.

Webinar: End to End Security & Operations with Chainguard and Weave GitOpsWeaveworks

One of the key values of GitOps relies on its fully declarative single source of truth in Git for the desired state of your entire system – configuration that continuously reconciles with the runtime of the system. Validating committer identity in your Git repository is a critical component towards a secure GitOps solution. Although basic capabilities are provided by Git service providers, more granular controls for governance and compliance are a requirement to satisfy most enterprise grade implementations. How do you keep that end to end process secure, from Git to Runtime? Join Weaveworks and Chainguard for a live webinar where we will look at how Chainguard Enforce for Git together with Weave GitOps Enterprise Policy Engine allows you to secure your end to end GitOps workflows, from Git to Runtime. You will learn how to: - Use Chainguard Enforce for Git to ensure only authorized GitOps tooling can modify your desired state. - Provide a secure identity to Weave GitOps Enterprise for all Git operations. - Use Weave GitOps Policy Engine to guarantee compliance on admission.

8 Essential DevOps Tools for SalesforceAutoRABIT

Make a better DevOps with GitOpsOpsta

Lambda Architectures in PracticeC4Media

Video and slides synchronized, mp3 and slide download available at URL http://bit.ly/1FQYcP0. Gian Merlino presents the advantages, challenges, and best practices to deploying and maintaining lambda architectures in the real world, using the infrastructure at Metamarkets as a case study. Filmed at qconsf.com. Gian Merlino is a senior software engineer at Metamarkets, responsible for the infrastructure behind its data ingestion pipelines and is a committer on the Druid project.

How to plan and define your CI-CD pipelineElasTest Project

Cloud Native Apps with GitOps Weaveworks

GitOps provides a way for organizations to adopt continuous delivery practices using cloud native technologies like Kubernetes and Docker. It advocates storing all infrastructure configurations and code in a Git repository to enable automated deployment and management of applications. Weaveworks adopted GitOps and was able to recover from a complete system failure in just 45 minutes by having their entire system defined as code. GitOps follows the principles of continuous delivery and observability by integrating deployment pipelines, monitoring, and security policies to drive faster, more reliable software releases.

Understanding the GitOps Workflow and CICD Pipeline - What It Is, Why It Matt...Gibran Badrulzaman

Weave GitOps 2022.09 Release: A Fast & Reliable Path to Production with Progr...Weaveworks

Git essential training & sharing selfChen-Tien Tsai

Next Level DevOps Implementation with GitOpsRamadoni Ashudi

GitOps, Driving NGN Operations Teams 211127 #kcdgt 2021William Caban

Introduction to git & githubVinothini KadambavanaSundaram

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

KubeCon EU 2022 Istio, Flux & Flagger.pdfWeaveworks

Distributed Versioning Tools, BeJUG 2010Pursuit Consulting

DevOps Service | MindtreeAnikeyRoy

Room 2 - 4 - Juncheng Anthony Lin - Redhat - A Practical Approach to Traditio...Vietnam Open Infrastructure User Group

WTF is GitOps and Why You Should Care?Weaveworks

WTF is GitOps & Why Should You Care?All Things Open

Continuous Lifecycle London 2018 Event KeynoteWeaveworks

Webinar: End to End Security & Operations with Chainguard and Weave GitOpsWeaveworks

8 Essential DevOps Tools for SalesforceAutoRABIT

Make a better DevOps with GitOpsOpsta

Lambda Architectures in PracticeC4Media

How to plan and define your CI-CD pipelineElasTest Project

Cloud Native Apps with GitOps Weaveworks

More from devObjective (20)

Raspberry Pi a la CFMLdevObjective

1) The document discusses running ColdFusion on a Raspberry Pi single board computer. It provides instructions for installing CommandBox and other tools to run CFML code on the Pi. 2) Performance tests show the Pi can handle over 1000 requests per second serving simple CFML pages. 3) The document explores various projects that can be built with the Pi including interacting with GPIO pins to control LEDs and shift registers, building a LED matrix display, and clustering multiple Pis.

Command boxdevObjective

CommandBox is a CLI (command line interface) package manager and automation tool for ColdFusion developers. It provides features like a package manager, REPL (read-eval-print loop), integrated server, scaffolding for frameworks like ColdBox and ContentBox, and automation commands to integrate CFML development with tasks like unit testing and source control. CommandBox aims to improve the ColdFusion development workflow and enable new use cases like packaging and distributing CFML applications and libraries.

Effective version controldevObjective

The document discusses effective version control. It begins with an introduction of the presenter and overview of topics to be covered, including concepts, evolution of version control systems, best practices, and whether centralized or distributed systems are better. Key concepts discussed include repositories, working copies, patches, history, tags, branches, merges, and ancestry. The evolution of version control systems from early ones like SCCS and RCS to modern ones like Git, Mercurial, Subversion, and Team Foundation Server is outlined. Best practices recommended include committing often, branching early and merging often, and keeping the master branch releasable. The document concludes by emphasizing the power of version control tools and reusing existing code rather than reinventing

Front end-modernizationdevObjective

This document discusses strategies for modernizing front-end codebases in an incremental way. It recommends starting with basic modularization by splitting code into logical chunks, then concatenating and minifying files. Next steps include loading modules on demand using various module systems. Graceful deprecation is advised by keeping deprecated code available temporarily while logging its usage. Framework choices should be informed by building prototypes in different options. Overall modernization should prioritize tools like testing, linting and performance testing over choosing specific frameworks. Changes should be made gradually to avoid diverging from existing workflows.

Using type script to build better appsdevObjective

TypeScript is a typed superset of JavaScript that compiles to plain JavaScript. It allows you to write JavaScript in a more structured way using types, classes, and interfaces. Using TypeScript can help catch errors early and provide better code completion through tooling. While TypeScript adds types and other features, JavaScript code is still valid TypeScript code. The TypeScript compiler outputs plain JavaScript that runs on any browser or environment.

Csp and http headersdevObjective

Who owns Software SecuritydevObjective

This document discusses software security and outlines a 4 step plan to improve it. It begins by recommending studying successful security initiatives at other companies. The second step is to inventory your own applications to understand what data and services they involve. The third step is to incorporate security practices into agile development processes and use tools to help scale this. The final step is to drive a security-focused culture change and have plans for incident response.

Naked and afraid Offline mobiledevObjective

The document discusses using offline storage on mobile devices by leveraging HTML, JavaScript, and technologies like Cordova, PouchDB, and CouchDB. It summarizes the evolution of HTML5 offline storage standards including Web Storage, Web SQL, and IndexedDB. It then outlines an approach to building a mobile app that works offline by storing data locally on the device using IndexedDB and syncing with a remote CouchDB database using PouchDB when an internet connection is available.

Web hackingtools 2015devObjective

This document provides an overview of a presentation on web penetration testing and hacking tools. It introduces the presenter and their background in security. It states that the presentation will demonstrate various penetration testing tools against virtual web applications and provide a quick overview of web application firewalls and vulnerability scanners. It provides details on some recent hacking events and vulnerabilities like Heartbleed and discusses tools like sqlmap, BeEF, and Metasploit that will be demonstrated.

Node without servers aws-lambdadevObjective

Node Without Servers: Event-Driven Computing with AWS Lambda describes AWS Lambda and how it allows running code without servers. Lambda runs code in response to events, scales automatically, and charges only for the compute time used. Code runs in isolated containers and Lambda manages the computing resources. This allows building event-driven applications and services that respond quickly to new information.

I am-designerdevObjective

This document is a presentation about design fundamentals given by Justine Arreche. It covers grids and content structure, color theory, and typography. For grids, it emphasizes laying out the grid first to keep content organized. Regarding color theory, it discusses using relevant colors aligned to messaging and creating contrast with colors on opposite sides of the color wheel. For typography, it recommends pairing type families and choosing typefaces with common traits or contrasts to create diversity and emphasis.

Garbage First and You!devObjective

The document discusses the Garbage First (G1) garbage collector in the Java Virtual Machine (JVM). It provides an overview of G1, including its core ideas of using snapshot-at-the-beginning marking and dividing memory into variable-sized regions. It describes how G1 handles young and old generation garbage collection using concurrent marking and mixed garbage collections. The document also discusses tuning G1, such as setting the maximum GC pause time goal and heap occupancy percentage for starting concurrent collection.

Fusion ReactordevObjective

FusionReactor is a monitoring and troubleshooting tool that provides visibility into application performance and issues. It allows users to view current and historical requests, database activity, errors and more. The tool helps diagnose problems by showing stack traces, logs and other details. FusionReactor 6 includes new metrics, enhanced session tracking, and an option for cloud-based monitoring. An upcoming feature called Unattended Production Debugger will automatically fix problems without user intervention.

Paying off emotional debtdevObjective

The document discusses Justine's personal experience with bulimia and how it affected her life and career. It provides information about eating disorders, including definitions and statistics. It offers suggestions for how companies can help employees who may be struggling with an eating disorder, such as addressing performance issues confidentially with HR, providing information on treatment resources and medical leave policies, and ensuring compliance with disability laws. The talk aims to help reduce stigma and support those suffering from these mental health issues.

My SQL Skills Killed the ServerdevObjective

This document discusses SQL skills and how queries can negatively impact server performance if not written efficiently. It covers topics like query plans, execution contexts, using parameters, indexing, handling large datasets, and external influences on SQL performance. Specific "bad" SQL examples are also provided and explained. The presenter's goal is to help developers optimize their SQL and prevent poorly written queries from bringing servers to their knees.

Authentication ControldevObjective

This document discusses authentication, authorization, and fine-grained access control. It introduces different levels of authorization from anonymous access to fine-grained control varying across users and resources. It provides examples of implementing fine-grained security using annotations and services. API security is also discussed, with authentication handled via OAuth2 and authorization using annotations. Pattern languages are presented as a way to discuss difficult technical problems using consistent terminology.

Multiply like rabbits with rabbit mqdevObjective

This document discusses using RabbitMQ for messaging between applications. It begins with an introduction to the presenter and agenda. It then contrasts traditional RPC-style calls with messaging and covers some benefits of messaging like decoupling and flexibility. Common messaging patterns like publish/subscribe, topics, and work queues are introduced. The AMQP protocol and RabbitMQ implementation are explained. Finally, a demo of RabbitMQ is promised along with Q&A.

Preso slidedeckdevObjective

This document contains notes from a presentation on software architecture. It discusses key principles like examining requirements to understand user needs, designing for foreseeable changes, and clear communication between architects and developers. Case studies are used to illustrate how understanding the problem domain leads to more elegant solutions. Overall it emphasizes that architecture is about managing risks to the application and knowing enough about the problem to design appropriately.

Intro to TDD & BDDdevObjective

This document discusses test-driven development (TDD) and behavior-driven development (BDD). It defines TDD as a process of writing automated tests before code to define desired functionality, then writing minimum code to pass tests and refactoring. BDD combines TDD techniques with domain-driven design and focuses on user stories over functions to promote communication. The document provides an example of using BDD to generate scenarios for a life insurance risk example, and shows how TestBox can be used to write automated tests based on those scenarios.

Rethink Async with RXJSdevObjective

The document discusses using RxJS (Reactive Extensions for JavaScript) to build an animated autocomplete widget. It introduces key concepts of RxJS like observables, operators like map and filter, and patterns for merging and concatenating streams. It then walks through building an autocomplete component that responds to keypresses, makes API requests, and animates search results in and out using RxJS observables and operators to coordinate asynchronous and event-driven code.

Raspberry Pi a la CFMLdevObjective

Command boxdevObjective

Effective version controldevObjective

Front end-modernizationdevObjective

Using type script to build better appsdevObjective

Csp and http headersdevObjective

Who owns Software SecuritydevObjective

Naked and afraid Offline mobiledevObjective

Web hackingtools 2015devObjective

Node without servers aws-lambdadevObjective

I am-designerdevObjective

Garbage First and You!devObjective

Fusion ReactordevObjective

Paying off emotional debtdevObjective

My SQL Skills Killed the ServerdevObjective

Authentication ControldevObjective

Multiply like rabbits with rabbit mqdevObjective

Preso slidedeckdevObjective

Intro to TDD & BDDdevObjective

Rethink Async with RXJSdevObjective

Recently uploaded (20)

Splunk Security Update | Public Sector Summit Germany 2025Splunk

Into The Box Conference Keynote Day 1 (ITB2025)Ortus Solutions, Corp

Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan

This is a Quick Research Guide (QRG). QRGs include the following: - A brief, high-level overview of the QRG topic. - A milestone timeline for the QRG topic. - Links to various free online resource materials to provide a deeper dive into the QRG topic. - Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic. QRGs planned for the series: - Artificial Intelligence QRG - Quantum Computing QRG - Big Data Analytics QRG - Spacecraft Guidance, Navigation & Control QRG (coming 2026) - UK Home Computing & The Birth of ARM QRG (coming 2027) Any questions or comments? - Please contact Arthur Morgan at [email protected]. 100% human made.

Cybersecurity Identity and Access Solutions using Azure ADVICTOR MAESTRE RAMIREZ

DevOpsDays Atlanta 2025 - Building 10x Development Organizations.pptxJustin Reock

Building 10x Organizations with Modern Productivity Metrics 10x developers may be a myth, but 10x organizations are very real, as proven by the influential study performed in the 1980s, ‘The Coding War Games.’ Right now, here in early 2025, we seem to be experiencing YAPP (Yet Another Productivity Philosophy), and that philosophy is converging on developer experience. It seems that with every new method we invent for the delivery of products, whether physical or virtual, we reinvent productivity philosophies to go alongside them. But which of these approaches actually work? DORA? SPACE? DevEx? What should we invest in and create urgency behind today, so that we don’t find ourselves having the same discussion again in a decade?

Transcript: #StandardsGoals for 2025: Standards & certification roundup - Tec...BookNet Canada

Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next. Link to recording, presentation slides, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/ Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.

ThousandEyes Partner Innovation Updates for May 2025ThousandEyes

TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc

Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency. This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data. Attendees will learn: - Consumer awareness around data brokers and what consumers are doing to limit data collection - How businesses assess third-party vendors and their consent management operations - Where business preparedness needs improvement - What these trends mean for the future of privacy governance and public trust This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.

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/.

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.

AI Changes Everything – Talk at Cardiff Metropolitan University, 29th April 2...Alan Dix

Talk at the final event of Data Fusion Dynamics: A Collaborative UK-Saudi Initiative in Cybersecurity and Artificial Intelligence funded by the British Council UK-Saudi Challenge Fund 2024, Cardiff Metropolitan University, 29th April 2025 https://alandix.com/academic/talks/CMet2025-AI-Changes-Everything/ Is AI just another technology, or does it fundamentally change the way we live and think? Every technology has a direct impact with micro-ethical consequences, some good, some bad. However more profound are the ways in which some technologies reshape the very fabric of society with macro-ethical impacts. The invention of the stirrup revolutionised mounted combat, but as a side effect gave rise to the feudal system, which still shapes politics today. The internal combustion engine offers personal freedom and creates pollution, but has also transformed the nature of urban planning and international trade. When we look at AI the micro-ethical issues, such as bias, are most obvious, but the macro-ethical challenges may be greater. At a micro-ethical level AI has the potential to deepen social, ethnic and gender bias, issues I have warned about since the early 1990s! It is also being used increasingly on the battlefield. However, it also offers amazing opportunities in health and educations, as the recent Nobel prizes for the developers of AlphaFold illustrate. More radically, the need to encode ethics acts as a mirror to surface essential ethical problems and conflicts. At the macro-ethical level, by the early 2000s digital technology had already begun to undermine sovereignty (e.g. gambling), market economics (through network effects and emergent monopolies), and the very meaning of money. Modern AI is the child of big data, big computation and ultimately big business, intensifying the inherent tendency of digital technology to concentrate power. AI is already unravelling the fundamentals of the social, political and economic world around us, but this is a world that needs radical reimagining to overcome the global environmental and human challenges that confront us. Our challenge is whether to let the threads fall as they may, or to use them to weave a better future.

How analogue intelligence complements AIPaul Rowe

Artificial Intelligence is providing benefits in many areas of work within the heritage sector, from image analysis, to ideas generation, and new research tools. However, it is more critical than ever for people, with analogue intelligence, to ensure the integrity and ethical use of AI. Including real people can improve the use of AI by identifying potential biases, cross-checking results, refining workflows, and providing contextual relevance to AI-driven results. News about the impact of AI often paints a rosy picture. In practice, there are many potential pitfalls. This presentation discusses these issues and looks at the role of analogue intelligence and analogue interfaces in providing the best results to our audiences. How do we deal with factually incorrect results? How do we get content generated that better reflects the diversity of our communities? What roles are there for physical, in-person experiences in the digital world?

SAP Modernization: Maximizing the Value of Your SAP S/4HANA Migration.pdfPrecisely

tecnologias de las primeras civilizaciones.pdffjgm517

2025-05-Q4-2024-Investor-Presentation.pptxSamuele Fogagnolo

Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo

Manifest Pre-Seed Update | A Humanoid OEM Deeptech In Francechb3

Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB

Want to learn practical tips for designing systems that can scale efficiently without compromising speed? Join us for a workshop where we’ll address these challenges head-on and explore how to architect low-latency systems using Rust. During this free interactive workshop oriented for developers, engineers, and architects, we’ll cover how Rust’s unique language features and the Tokio async runtime enable high-performance application development. As you explore key principles of designing low-latency systems with Rust, you will learn how to: - Create and compile a real-world app with Rust - Connect the application to ScyllaDB (NoSQL data store) - Negotiate tradeoffs related to data modeling and querying - Manage and monitor the database for consistently low latencies

#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025BookNet Canada

Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next. Link to recording, transcript, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/ Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.

Greenhouse_Monitoring_Presentation.pptx.hpbmnnxrvb