Discussion of how Atlassian moved from subversion source code management to DVCS tools such as Git and Mercurial.
Covers a basic recipe for making the switch from the Atlassian experience and ideas as to why DVCS has become a competitive advantage to businesses.
Enterprise-Ready Private and Hybrid Cloud Computing TodayRightScale
RightScale User Conference NYC 2011:
Enterprise-Ready Private and Hybrid Cloud Computing Today
Rich Wolski - Founder and CTO, Eucalyptus
In this session, we'll discuss the use of Eucalyptus and RightScale to build enterprise-grade cloud computing environments. By combining on-premise clouds with Amazon Web Services (AWS) through a common cloud management interface, Eucalyptus and AWS form a coherent platform for reliable and cost-effective enterprise cloud computing. The RightScale Cloud Management Platform delivers the high-level framework for cost-effectively automating and managing this ensemble of technologies.
Docker Enables DevOps - Keep C.A.L.M.S. and Docker on ...Boyd Hemphill
The pillars of DevOps are Culture, Automation, Measurement and Sharing. Docker is a rare tool at enables DevOps through all 4 pillars. These slides take a look at how Docker can affect each pillar in your organization through a Lean lens.
On November 4th, 2016 some 300+ IT decision makers gathered in the Amsterdam ArenA for a game-changing DevOps Masterclass: Better, Faster, Smarter with DevOps. Dutch thought leader and subject matter expert Rik Farenhorst illustrated the five key DevOps building blocks. Attendees also attended the famed Phoenix Project game zone, where they simulated organizational silos / key unit all the while trying to gain momentum in digital transformation. Several attendees got a hold of a golden ticket, earning them a seat with one of our local DevOps Experts. Xebia can guide you through any stage you are at while gaining momentum with the DevOps journey.
DevOps is the union of people, process, and products to enable continuous delivery of value to our end users. The contraction of “Dev” and “Ops” refers to replacing siloed Development and Operations to create multidisciplinary teams that now work together with shared and efficient practices and tools. Essential DevOps practices include agile planning, continuous integration, continuous delivery, and monitoring of applications.
Working on DevSecOps culture - a team centric viewPatrick Debois
A presentation to help you better understand the context in which devsecops transformation happen. With a focus on how the teams are empowered to really care about security.
Presented at The Devops Conference - organized by Eficode
Enterprise-Ready Private and Hybrid Cloud Computing TodayRightScale
RightScale User Conference NYC 2011:
Enterprise-Ready Private and Hybrid Cloud Computing Today
Rich Wolski - Founder and CTO, Eucalyptus
In this session, we'll discuss the use of Eucalyptus and RightScale to build enterprise-grade cloud computing environments. By combining on-premise clouds with Amazon Web Services (AWS) through a common cloud management interface, Eucalyptus and AWS form a coherent platform for reliable and cost-effective enterprise cloud computing. The RightScale Cloud Management Platform delivers the high-level framework for cost-effectively automating and managing this ensemble of technologies.
Docker Enables DevOps - Keep C.A.L.M.S. and Docker on ...Boyd Hemphill
The pillars of DevOps are Culture, Automation, Measurement and Sharing. Docker is a rare tool at enables DevOps through all 4 pillars. These slides take a look at how Docker can affect each pillar in your organization through a Lean lens.
On November 4th, 2016 some 300+ IT decision makers gathered in the Amsterdam ArenA for a game-changing DevOps Masterclass: Better, Faster, Smarter with DevOps. Dutch thought leader and subject matter expert Rik Farenhorst illustrated the five key DevOps building blocks. Attendees also attended the famed Phoenix Project game zone, where they simulated organizational silos / key unit all the while trying to gain momentum in digital transformation. Several attendees got a hold of a golden ticket, earning them a seat with one of our local DevOps Experts. Xebia can guide you through any stage you are at while gaining momentum with the DevOps journey.
DevOps is the union of people, process, and products to enable continuous delivery of value to our end users. The contraction of “Dev” and “Ops” refers to replacing siloed Development and Operations to create multidisciplinary teams that now work together with shared and efficient practices and tools. Essential DevOps practices include agile planning, continuous integration, continuous delivery, and monitoring of applications.
Working on DevSecOps culture - a team centric viewPatrick Debois
A presentation to help you better understand the context in which devsecops transformation happen. With a focus on how the teams are empowered to really care about security.
Presented at The Devops Conference - organized by Eficode
Introduction to DevOps - Rackspace tech nightMarc Cluet
Talk given during the July Rackspace tech night which is an introduction to DevOps, no need for any previous technical knowledge as this concentrates on the culture and methodology.
As the world of system and application deployment continues to change, the sys admin and security community needs to change with it. With agile development, continuous deployment, the pace of change in IT has only increased. Add in Dev/Ops and the traditional sys admin and security processes just don’t work. How can you rapidly deliver servers and applications while making sure they are built reliably and securely. Rackspace has been developing a tool to help them design, deploy and security assess complex configurations for customers called Checkmate. This talk will cover the concepts behind and the architecture of Checkmate and how it helps minimize the time to deploy systems and verify they have been created to spec and in a secure state. A discussion of how Checkmate has inspired the concept of Test Driven Security based on the Test Driven Development model familiar to the development world.
DevOps brings together people, processes and technology, automating software delivery to provide continuous value to your users. With Azure DevOps solutions, deliver software faster and more reliably—no matter how big your IT department or what tools you are using
This webinar discusses the gaps that prevent enterprises from fully automating the DevOps lifecycle and how technologies like Containers and Sandboxes can assist with crossing that chasm.
Deploy Resources to Azure using ARM templatesAmal Dev
Provision various resources in Azure using ARM templates from the command line using Azure CLI. With this approach one will be able to automate their deployments very easily
Microsoft recently released Azure DevOps, a set of services that help developers and IT ship software faster, and with higher quality. These services cover planning, source code, builds, deployments, and artifacts. One of the great things about Azure DevOps is that it works great for any app and on any platform regardless of frameworks.
In this session, I will provide a hands on workshop guiding you through getting started with Azure Pipelines to build your application. Using continuous integration and deployment processes, you will leave with clear understanding and skills to get your applications up and running quickly in Azure DevOps and see the full benefits that CI/CD can bring to your organization.
DevOps brings together people, processes and technology, automating software delivery to provide continuous value to your users. With Azure DevOps solutions, deliver software faster and more reliably—no matter how big your IT department or what tools you are using
Open Source and Content Management (+audio)Matt Hamilton
Open Source solutions are becoming more commonplace in corporate IT, with two thirds of companies using Open Source today or planning to use it soon. We've all heard the hype: cheaper to buy, cheaper to run, cheaper to fix. Using Open Source software reduces your risks. But how does this translate to the world of Content Management?
The advantages of Open Source systems go beyond simple cost savings. Content management by its very nature requires a significant level of customisation and integration to meet business requirements. By not prohibiting the inspection and modification of the source code, Open Source enables a level of flexibility not available with proprietary systems.
Open Source enables you to leverage a culture of trust and openness, rather than secrecy. By having access to the source code, a customer can be safe in the knowledge that everything that the software vendor was intended to deliver can be independently verified.
In this talk you will learn how the Open Source community works, how its distributed nature makes it more resilient, and how you can become a part of it and benefit. We will cover the key criteria to consider when evaluating which Open Source CMS is the right fit for your requirements.
¿Qué es Azure DevOps? Vamos a ver un ejemplo de ciclo completo de despliegue con Azure DevOps que nos permita, durante el resto de sesiones, integrar los conceptos que veremos en ellas.
En esta sesión os explicaremos que son los Azure Pipelines, YAML, Releases y el ciclo completo de compilación-testing-despliegue de una aplicación mediante estos pipelines
Microservices: Organizing Large Teams for Rapid DeliveryVMware Tanzu
SpringOne Platform 2016
Speakers: Patricia Anderson; Senior Consultant, Credera. Micah Blalock; Senior Architect, Credera. Jason Goth; Principal Architect, Credera.
A microservice architecture is pattern that is most commonly associated with larger organizations where services and teams are organized around separate business capabilities. In a project our team recently completed, we used a microservice architecture to allow us to organize a large team to develop a large analytics platform at speeds that would not have been possible using a more typical service-oriented architecture.
In this session, we discuss the organizational structure and communication and development strategies and tools to allow teams to work in parallel without drowning in process overhead and coordination costs.
DevOps, microservices and stress-free incidents. How toy have your cake and ...Peter Holditch
A discussion of the complexity trade-offs between the development and deployment phases of the application lifecycle driven by microservice architecture and how to most efficiently manage applications across the lifecycle in a DevOps model
Devops core principles
CI/CD basics
CI/CD with asp.net core webapi and Angular app
Iac Why and What?
Demo using Azure and Azure Devops
Docker why and what ?
Demo using Azure and Azure Devops
Kubernetes why and what?
Demo using Azure and Azure Devops
Introduction to DevOps - Rackspace tech nightMarc Cluet
Talk given during the July Rackspace tech night which is an introduction to DevOps, no need for any previous technical knowledge as this concentrates on the culture and methodology.
As the world of system and application deployment continues to change, the sys admin and security community needs to change with it. With agile development, continuous deployment, the pace of change in IT has only increased. Add in Dev/Ops and the traditional sys admin and security processes just don’t work. How can you rapidly deliver servers and applications while making sure they are built reliably and securely. Rackspace has been developing a tool to help them design, deploy and security assess complex configurations for customers called Checkmate. This talk will cover the concepts behind and the architecture of Checkmate and how it helps minimize the time to deploy systems and verify they have been created to spec and in a secure state. A discussion of how Checkmate has inspired the concept of Test Driven Security based on the Test Driven Development model familiar to the development world.
DevOps brings together people, processes and technology, automating software delivery to provide continuous value to your users. With Azure DevOps solutions, deliver software faster and more reliably—no matter how big your IT department or what tools you are using
This webinar discusses the gaps that prevent enterprises from fully automating the DevOps lifecycle and how technologies like Containers and Sandboxes can assist with crossing that chasm.
Deploy Resources to Azure using ARM templatesAmal Dev
Provision various resources in Azure using ARM templates from the command line using Azure CLI. With this approach one will be able to automate their deployments very easily
Microsoft recently released Azure DevOps, a set of services that help developers and IT ship software faster, and with higher quality. These services cover planning, source code, builds, deployments, and artifacts. One of the great things about Azure DevOps is that it works great for any app and on any platform regardless of frameworks.
In this session, I will provide a hands on workshop guiding you through getting started with Azure Pipelines to build your application. Using continuous integration and deployment processes, you will leave with clear understanding and skills to get your applications up and running quickly in Azure DevOps and see the full benefits that CI/CD can bring to your organization.
DevOps brings together people, processes and technology, automating software delivery to provide continuous value to your users. With Azure DevOps solutions, deliver software faster and more reliably—no matter how big your IT department or what tools you are using
Open Source and Content Management (+audio)Matt Hamilton
Open Source solutions are becoming more commonplace in corporate IT, with two thirds of companies using Open Source today or planning to use it soon. We've all heard the hype: cheaper to buy, cheaper to run, cheaper to fix. Using Open Source software reduces your risks. But how does this translate to the world of Content Management?
The advantages of Open Source systems go beyond simple cost savings. Content management by its very nature requires a significant level of customisation and integration to meet business requirements. By not prohibiting the inspection and modification of the source code, Open Source enables a level of flexibility not available with proprietary systems.
Open Source enables you to leverage a culture of trust and openness, rather than secrecy. By having access to the source code, a customer can be safe in the knowledge that everything that the software vendor was intended to deliver can be independently verified.
In this talk you will learn how the Open Source community works, how its distributed nature makes it more resilient, and how you can become a part of it and benefit. We will cover the key criteria to consider when evaluating which Open Source CMS is the right fit for your requirements.
¿Qué es Azure DevOps? Vamos a ver un ejemplo de ciclo completo de despliegue con Azure DevOps que nos permita, durante el resto de sesiones, integrar los conceptos que veremos en ellas.
En esta sesión os explicaremos que son los Azure Pipelines, YAML, Releases y el ciclo completo de compilación-testing-despliegue de una aplicación mediante estos pipelines
Microservices: Organizing Large Teams for Rapid DeliveryVMware Tanzu
SpringOne Platform 2016
Speakers: Patricia Anderson; Senior Consultant, Credera. Micah Blalock; Senior Architect, Credera. Jason Goth; Principal Architect, Credera.
A microservice architecture is pattern that is most commonly associated with larger organizations where services and teams are organized around separate business capabilities. In a project our team recently completed, we used a microservice architecture to allow us to organize a large team to develop a large analytics platform at speeds that would not have been possible using a more typical service-oriented architecture.
In this session, we discuss the organizational structure and communication and development strategies and tools to allow teams to work in parallel without drowning in process overhead and coordination costs.
DevOps, microservices and stress-free incidents. How toy have your cake and ...Peter Holditch
A discussion of the complexity trade-offs between the development and deployment phases of the application lifecycle driven by microservice architecture and how to most efficiently manage applications across the lifecycle in a DevOps model
Devops core principles
CI/CD basics
CI/CD with asp.net core webapi and Angular app
Iac Why and What?
Demo using Azure and Azure Devops
Docker why and what ?
Demo using Azure and Azure Devops
Kubernetes why and what?
Demo using Azure and Azure Devops
Leiningen2 - humane build management for clojureJohn Stevenson
Managing project builds does not have to be an endless fight with XML. Using Leiningen for Clojure projects allows you to define the project in Clojure as well.
C# .net Interfacing with embedded system Raghav Shetty
Build your Custom based Human Machine Interface (HMI) C# with Embedded system. This book covers interfacing GSM modem, RFID and Interfacing with USB Relay
Dreamforce 13 developer session: Introduction to HerokuJohn Stevenson
An introduction to Heroku platform as a service for developers at Salesforce Dreamforce conference 2013. The presentation discusses how Heroku fits into the Salesforce platform and relates it to development with Force.com.
The presentation also shows how easy it is to get your custom application deployed on Heroku, leading to an iterative and continuous deployment approach to app development.
Get into Functional Programming with ClojureJohn Stevenson
A brief guide on how to think in the way of Functional Programming, using Clojure as the example code.
Covers the main concepts and abstractions within Functional Programming & Clojure
Presented at several conferences and meetup events through 2016, with a video captured via GoPro at CeBIT Developer world 2016 on youtube at:
https://www.youtube.com/watch?v=mEfqULqChZs
interfacing matlab with embedded systemsRaghav Shetty
This Book is all about Interfacing Embedded System with Matlab. This book guides the beginners for creating GUI , Modeling with SimuLink & Interfacing Arduino , Raspberry Pi , BeagleBone with Embedded System. This Book is NOT FOR SALE , Only knowledge base for Open Source Community
Collaboration forms communities from the individual communications of others.
In our continually evolving society it is so important to be part of the community for your own discovery and to help socieity evolve even further.
This talk discusses how communication has evolved and the benefits that collaboration bring to our lives.
Introducing Heroku at the Customer Company Tour in Munich 2013. Covering the value of Heroku within the Salesforce family, especially for customer facing custom applications.
An updated and condense version of the recipe Atlassian uses to help migrate their teams to DVCS tooling.
This presentation was given in a Webinar by Clearvision http://www.clearvision-cm.com/
This webinar discusses the gaps that prevent enterprises from fully automating the DevOps lifecycle and how technologies like Containers and Sandboxes can assist with crossing that chasm.
Businesses are speeding up development and automating operations to remain competitive and to get large organizations to scale. Project based monolithic application updates are replaced by product teams owning containerized microservices. This puts developers on call, responsible for pushing code to production, fixing it when it breaks, and managing the cost and security aspects of running their microservices. In this world operations skill-sets are either embedded in the microservices development teams, or building and operating API driven platforms. The platform automates stress testing, canary based deployment, penetration testing and enforces availability and security requirements. There are no meetings or tickets to file in the delivery process for updating a containerized microservice, which can happen many times a day, and takes seconds to complete. The role of site reliability engineering moves from firefighting and fixing outages to buiding tools for finding problems and routing those problems to the right developers. SREs manage the incident lifecycle for customer visible problems, and measure and publish availability metrics. This may sound futuristic but Werner Vogels described this as “You build it, you run it” in 2006.
How to Avoid Cloud Confusion, DevOps dilemma, Microservice MadnessBMK Lakshminarayanan
on 10 Dec 2019 as part of Global SKILup Day organised by DevOps Institute, I presented on topic "How to Avoid Cloud Confusion, DevOps dilemma, Microservice Madness" along with DevOps leaders, practitioners, authors and speakers.
The presentation covers three major areas of today's trend: Cloud, DevOps, Microservices and I presented on some practical "How to" #DevOps session as an invited speaker.
Kubo (Cloud Foundry Container Platform): Your Gateway Drug to Cloud-nativecornelia davis
You’re at the Cloud Foundry Summit, which means you are by definition a cloud-native enthusiast. There’s no question that building apps in this architectural style will produce resilient, scalable software in an agile manner, and allow you to operate it far more efficiently than you’ve been able to in the past. But you’ve also got a whole lot of software in your company’s portfolio that isn’t there yet. Do you have to resign yourself to the pains of managing those applications the old way until you can finally refactor them to be cloud-native? Kubo to the rescue.
You can run legacy applications on Kubo without significant refactoring – pure and simple. As an added bonus, it allows you to satisfy the CIO mandate of running containers (check). But it’s far more than that – running those workloads on Kubo offers advantages over running them on traditional virtualized infrastructure. This session covers those advantages –resource consolidation, health management, multi-cloud and more. It will also present the abstractions in Kubernetes, things like pods and stateful sets, that support running legacy workloads in the cloud environments that are far more distributed and changing than they have been in the past. It’s a first step to cloud-native.
Kubo (Cloud Foundry Container Platform): Your Gateway Drug to Cloud-nativeVMware Tanzu
You’re at the Cloud Foundry Summit, which means you are by definition a cloud-native enthusiast. There’s no question that building apps in this architectural style will produce resilient, scalable software in an agile manner, and allow you to operate it far more efficiently than you’ve been able to in the past. But you’ve also got a whole lot of software in your company’s portfolio that isn’t there yet. Do you have to resign yourself to the pains of managing those applications the old way until you can finally refactor them to be cloud-native? Kubo to the rescue.
You can run legacy applications on Kubo without significant refactoring – pure and simple. As an added bonus, it allows you to satisfy the CIO mandate of running containers (check). But it’s far more than that – running those workloads on Kubo offers advantages over running them on traditional virtualized infrastructure. This session covers those advantages –resource consolidation, health management, multi-cloud and more. It will also present the abstractions in Kubernetes, things like pods and stateful sets, that support running legacy workloads in the cloud environments that are far more distributed and changing than they have been in the past. It’s a first step to cloud-native.
DevOps as a culutre has proven to help you ship faster, creating a better feedback mechanism between developers, operations and the systems they work on. It has been around for a while, but it is still not something that teams have been able to adopt completely and practice on a day-to-day basis, despite of its proven results. There is a gap between developers and operations, which needs to be closed.
In this talk, we will see how Vagrant can help developers and operations individually, and then how it can be used to bridge that gap for developers and operations to work more closely with each other. We will see how Vagrant can prove to be an effective tool for developers as it can offer cheap throw away environments that closely resembles production. We will also see how operations can make use of Vagrant for quickly testing out configuration management changes. And finally, we will discuss some advanced use-cases of Vagrant.
Distributed Version Control Systems: A Guide For The PerplexedAlan Stevens
In this session you will learn what Distributed Version Control is, the benefits of DVCS, the primary DVCS platforms and their relative benefits and shortcomings. Much of the discussion around version control currently centers around Distributed Version Control Systems (DVCS). More tools, web sites and platforms continue to enable DVCS access and interaction. For many developers and teams, DVCS remains unfamiliar. This session aims to make attendees familiar with DVCS so they can make informed choices and begin deeper investigation of DVCS features and benefits.
Some tools such as Chef and Jenkins are used by engineers in ops to great effect. Rarely though, a technology brings a paradigm to the masses.
Docker, like cloud virtualization is of this more rare breed.
Containers brought new approach for implementation of DevOps workflows. So our CEO, Ruslan Synytsky, devoted a speech to this topic during Madrid meetup and described in details how Java developers can get benefits from Docker containers in Jelastic Cloud.
Impact of CD, Clean Code, ... on Team PerformanceFredrik Wendt
Why is DevOps, Continuous Delivery, Docker, Clean Code, Vagrant, Software Craftsmanship and agile trending? How do these topics and techniques reflect on team performance?
As software teams transition to cloud-based architectures and adopt more agile processes, the tools they need to support their development cycles will change. In this session, we'll take you through the transition that Amazon made to a service-oriented architecture over a decade ago. We will share the lessons we learned, the processes we adopted, and the tools we built to increase both our agility and reliability. We will also introduce you to AWS CodeCommit, AWS CodePipeline, and AWS CodeDeploy, three new services born out of Amazon's internal DevOps.
Keynote at Dockercon Europe Amsterdam Dec 4th, 2014.
Speeding up development with Docker.
Summary of some interesting web scale microservice architectures.
Please send me updates and corrections to the architecture summaries @adrianco
Thanks Adrian
Confessions of a developer community builderJohn Stevenson
Slides from my talk on building developer communities at London Software Craftsmanship conference 5th & 6th October.
I share my experiences of interacting with the software development community over the last 22 years.
Discussion includes what kinds of events you could run in your community and how to get your community started.
Progscon 2017: Taming the wild fronteer - Adventures in ClojurescriptJohn Stevenson
Progscon 2017 conference talk, introducing Clojurescript for a functional programming approach to building React.js apps.
Examples include using React.js directly and the Om Clojurescript library that closely follows the React.js API. Also cover a simpler approach to React with the Clojurescript libraries called Reagent and Rum.
Discussing the challenges of communication that affect us all and techniques to help you be more effective
- Six Thinking Hats
- Thinking Fast & Slow
- Cognitive bias / confirmation bias
This talk was last given at DevRelCon in London, December 2016.
Helping others learn Clojure can be a little different to how you learnt. What makes sense for one person may not make relate to another persons experiences. This presentation gives a brief introduction to guiding people into Clojure.
This presentation was first given at Clojure Remote 2016
Git and github - Verson Control for the Modern DeveloperJohn Stevenson
An introduction to Git and Github, tools for distributed version control that give an easy to use and highly collaborative approach to version code and configuration.
An overview of Functional Programming and Clojure, helping you understand the importance of minimising side effects and walking through examples of functional programming concepts.
Dreamforce14 Metadata Management with Git Version ControlJohn Stevenson
An introduction to using Git version control to manage changes in the metadata of your Salesforce Org as you develop your apps.
Your app is put into an unmanaged package, copied to your local machine with Force.com CLI and changes pushed to Github using Github for Mac/Windows client.
An introduction to Heroku, the Platform as a Service from Salesforce for all your customer facing applications.
Discover how to get going with the Heroku platform and additional services you can use to speed up the deployment of your custom application.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Le nuove frontiere dell'AI nell'RPA con UiPath Autopilot™UiPathCommunity
In questo evento online gratuito, organizzato dalla Community Italiana di UiPath, potrai esplorare le nuove funzionalità di Autopilot, il tool che integra l'Intelligenza Artificiale nei processi di sviluppo e utilizzo delle Automazioni.
📕 Vedremo insieme alcuni esempi dell'utilizzo di Autopilot in diversi tool della Suite UiPath:
Autopilot per Studio Web
Autopilot per Studio
Autopilot per Apps
Clipboard AI
GenAI applicata alla Document Understanding
👨🏫👨💻 Speakers:
Stefano Negro, UiPath MVPx3, RPA Tech Lead @ BSP Consultant
Flavio Martinelli, UiPath MVP 2023, Technical Account Manager @UiPath
Andrei Tasca, RPA Solutions Team Lead @NTT Data
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
40. Not just the command line
The command line is like Marmite...
41. “ Distributed Version Control is flexible and can fit any
”
workflow - you can even treat it like Subversion.
42. “ Distributed Version Control is flexible and can fit any
”
workflow - you can even treat it like Subversion.
Steve Streeting
Creator of SourceTree
Welcome to Unite, I hope you are enjoying the day so far...\n
Why am talking about DVCS and what is that anyway?\n\n[Opportunity to ask people who they are (developers of any kind) and if they have heard of DVCS. If there are more than a handful of devs, then ask if they are using Subversion, Git, Mercurial, anything else?]\n\n\n
\n
JIRA is versioning tool for your issues - you can see the history of the issue and who got involved with that issue.\n
Confluence is a versioning tool for your collaborative content.\n\nThese are important changes to manage, but they are relatively simple to manage, working with code is usually more complex.\n\n\n
Now we are supporting developers directly and helping shape the future of code versioning with Bitbucket and SourceTree, a great pair of DVCS tools to help developers get work done.\n\nUsing these tools we improve the way developers manage all the changes around all of the projects they work on, from code, configurations, web artifacts, images, etc.\n\nI hope to show that using DVCS for your versioning provides real business benefit to your organisation and makes your developers happy nerds.\n
We want to share our experience of our move to DVCS\n- talking about why we did it, \n- how we did it and \n- what benefits we got from it.\n\n[Quick slide to make sure people are settled and know what they are about to hear]\n
Version control is a safe place to keep your code and other important scripts and configuration files, so you can manage them safely...\n\n\n
- A place where the team can work together\nEverybody can work on the same code base and get changes from other team mates\n\n- Time Machine\nYou can go back in time - if you want the code base of an older version, you can get it out of the version control system.\n\n- Make duplicates\nMaking a copy of the code and work on that\n
- A place where the team can work together\nEverybody can work on the same code base and get changes from other team mates\n\n- Time Machine\nYou can go back in time - if you want the code base of an older version, you can get it out of the version control system.\n\n- Make duplicates\nMaking a copy of the code and work on that\n
- A place where the team can work together\nEverybody can work on the same code base and get changes from other team mates\n\n- Time Machine\nYou can go back in time - if you want the code base of an older version, you can get it out of the version control system.\n\n- Make duplicates\nMaking a copy of the code and work on that\n
- A place where the team can work together\nEverybody can work on the same code base and get changes from other team mates\n\n- Time Machine\nYou can go back in time - if you want the code base of an older version, you can get it out of the version control system.\n\n- Make duplicates\nMaking a copy of the code and work on that\n
- A place where the team can work together\nEverybody can work on the same code base and get changes from other team mates\n\n- Time Machine\nYou can go back in time - if you want the code base of an older version, you can get it out of the version control system.\n\n- Make duplicates\nMaking a copy of the code and work on that\n
- A place where the team can work together\nEverybody can work on the same code base and get changes from other team mates\n\n- Time Machine\nYou can go back in time - if you want the code base of an older version, you can get it out of the version control system.\n\n- Make duplicates\nMaking a copy of the code and work on that\n
- A place where the team can work together\nEverybody can work on the same code base and get changes from other team mates\n\n- Time Machine\nYou can go back in time - if you want the code base of an older version, you can get it out of the version control system.\n\n- Make duplicates\nMaking a copy of the code and work on that\n
It used to be the case that all new projects in the Enterprise and open source world were started with subversion.\n\nYes there were (still are) a few die hards still using CVS, but the defacto standard was Subversion.\n\nThere were many reasons for the popularity:\n- it fixed a lot of flaws with CVS (the previous defacto version control system)\n- it was easy to learn as it had the same file based versioning mindset\n- it was easy to set up a repository with access over a secure Internet connection\n- services like sourceforge provided open source projects with all the subversion servers they could want\n\n
Using Beef as a more colourful term for problem, to follow the UK theme of changing the guards (beefeaters)\n\n\n
With a centralised server, everyone shares the same resource. Its like going to a all you can eat buffet, anyone can go up to buffet at any time and make a change, but if two people want the last slice of peperoni pizza you have a conflict.\n\nIts not quite that bad for developers (we seem to have a never ending supply of pizza)\n\nIf two developers make a changes to the same part of the code they could create a conflict when they both attempt to save those changes back to the repository. The bigger they changes they make, the more risk of conflict they have with changes from one or more other developers.\n\nUsing a central model is how Atlassian teams used to work and it could make us all very angry nerds some times.\n\n\n
Angry nerds....\n
Subversion is still used by a lot of developers, even though they regularly have issues with merging all the code together from each developer. As subversion only understands changes to individual files, it takes a lot of communication for a development team to not stand on each others toes when working on the same product.\n\nWhen using subversion, you have one server you connect with to save all your changes. All the changes have to be in sync with each other. If two developers work on the same code and want to commit their changes, considerable effort can be involved to merge all these changes into subversion.\n\nWhen you also have a continuous integration server attached to your subversion server, developers can become concerned about breaking the build and often delay checkin in code, making it harder to merge all these changes together.\n\nUsing DVCS, you encourage developers to commit their changes constantly.\n\n
Subversion is still used by a lot of developers, even though they regularly have issues with merging all the code together from each developer. As subversion only understands changes to individual files, it takes a lot of communication for a development team to not stand on each others toes when working on the same product.\n\nWhen using subversion, you have one server you connect with to save all your changes. All the changes have to be in sync with each other. If two developers work on the same code and want to commit their changes, considerable effort can be involved to merge all these changes into subversion.\n\nWhen you also have a continuous integration server attached to your subversion server, developers can become concerned about breaking the build and often delay checkin in code, making it harder to merge all these changes together.\n\nUsing DVCS, you encourage developers to commit their changes constantly.\n\n
A changing of the guard - UK reference - may want to change this for other countries\n\nOpen source has lead the way for many innovations in the tools development teams use, from the early days of Linux, JUnit framework, Apache Web Server, MySQL, Eclipse / Netbeans, Web Services, NoSQL. The trends in the Open Source community help enterprises understand important technologies. With DVCS being the fastest technology adoption in the community, its sending all the right signals for adoption. \n\nIts no surprise that Enterprise scale organisations like Google, Facebook, Disney and others are making use of Distributed version control tools like Bitbucket and SourceTree to help grow and sustain their business.\n\n\n
A changing of the guard - UK reference - may want to change this for other countries\n\nOpen source has lead the way for many innovations in the tools development teams use, from the early days of Linux, JUnit framework, Apache Web Server, MySQL, Eclipse / Netbeans, Web Services, NoSQL. The trends in the Open Source community help enterprises understand important technologies. With DVCS being the fastest technology adoption in the community, its sending all the right signals for adoption. \n\nIts no surprise that Enterprise scale organisations like Google, Facebook, Disney and others are making use of Distributed version control tools like Bitbucket and SourceTree to help grow and sustain their business.\n\n\n
A changing of the guard - UK reference - may want to change this for other countries\n\nOpen source has lead the way for many innovations in the tools development teams use, from the early days of Linux, JUnit framework, Apache Web Server, MySQL, Eclipse / Netbeans, Web Services, NoSQL. The trends in the Open Source community help enterprises understand important technologies. With DVCS being the fastest technology adoption in the community, its sending all the right signals for adoption. \n\nIts no surprise that Enterprise scale organisations like Google, Facebook, Disney and others are making use of Distributed version control tools like Bitbucket and SourceTree to help grow and sustain their business.\n\n\n
A changing of the guard - UK reference - may want to change this for other countries\n\nOpen source has lead the way for many innovations in the tools development teams use, from the early days of Linux, JUnit framework, Apache Web Server, MySQL, Eclipse / Netbeans, Web Services, NoSQL. The trends in the Open Source community help enterprises understand important technologies. With DVCS being the fastest technology adoption in the community, its sending all the right signals for adoption. \n\nIts no surprise that Enterprise scale organisations like Google, Facebook, Disney and others are making use of Distributed version control tools like Bitbucket and SourceTree to help grow and sustain their business.\n\n\n
A changing of the guard - UK reference - may want to change this for other countries\n\nOpen source has lead the way for many innovations in the tools development teams use, from the early days of Linux, JUnit framework, Apache Web Server, MySQL, Eclipse / Netbeans, Web Services, NoSQL. The trends in the Open Source community help enterprises understand important technologies. With DVCS being the fastest technology adoption in the community, its sending all the right signals for adoption. \n\nIts no surprise that Enterprise scale organisations like Google, Facebook, Disney and others are making use of Distributed version control tools like Bitbucket and SourceTree to help grow and sustain their business.\n\n\n
Everyone is either using DVCS or seriously evaluating it\n\n\n
Everyone is either using DVCS or seriously evaluating it\n\n\n
Everyone is either using DVCS or seriously evaluating it\n\n\n
Everyone is either using DVCS or seriously evaluating it\n\n\n
Everyone is either using DVCS or seriously evaluating it\n\n\n
DVCS and the rise of services like Bitbucket have helped evolve open source projects to a new level of social coding.\n\nDevelopers across the world can quickly share their code with everyone, anyone can take that code and change it, then send a message to say hey “I found a bug in your code, here is a fix for it”\n\nThis social coding is obviously great for open source project acceleration, as many hands get more work done. This is main reason why so many projects have switched. \n\nFor enterprises this sharing of code supports innovation and promotes collaboration within an organisation. With a private repository from Bitbucket, a team can share their code safely within the organisation and create high quality software products.\n
DVCS and the rise of services like Bitbucket have helped evolve open source projects to a new level of social coding.\n\nDevelopers across the world can quickly share their code with everyone, anyone can take that code and change it, then send a message to say hey “I found a bug in your code, here is a fix for it”\n\nThis social coding is obviously great for open source project acceleration, as many hands get more work done. This is main reason why so many projects have switched. \n\nFor enterprises this sharing of code supports innovation and promotes collaboration within an organisation. With a private repository from Bitbucket, a team can share their code safely within the organisation and create high quality software products.\n
\n
The basics of how we have enhanced the way we develop software at Atlassian.\n\nA slide to just take a quick breath and see how people are doing...\n
Walk through the main idea of a central server - SVN style. Mention others - CVS, P4, ClearCase\n\nMost people are familiar with the centralized version controls of the world - SVN, P4, CVS\nDescribe centralized versions control with SVN (image of how it works)\nThis what Atlassian was doing across a majority of our product teams teams\n\n\n\n
Walk through the main idea of a central server - SVN style. Mention others - CVS, P4, ClearCase\n\nMost people are familiar with the centralized version controls of the world - SVN, P4, CVS\nDescribe centralized versions control with SVN (image of how it works)\nThis what Atlassian was doing across a majority of our product teams teams\n\n\nThe P stands for Power - enabling developers...\n\n
\n
Instead of one big repository, the common approach is to split your code up into a more modular set of components or plugins - this is the way that Atlassian have been working for a while. In JIRA and Confluence, nearly everything is a plugin, even if it is a core part of the product.\n\nInstead of three month projects (97 days at Atlassian) a two week iteration is now running for development teams, allowing much quicker feedback from the rest of Atlassian. \n\nAs a developer you learn so much more the sooner you get feedback from your code. Code reviews are a great example of this, as are unit tests. However, there is no greater feedback than someone actually using your code day in day out. As we dogfood our products at Atlassian, any new features have over 400 eyes on them a few days after they were written and we can give feedback to the developers whilst they still remember clearly how they created those features.\n\nAn increased feedback cycle spawns more collaboration and innovation throughout Atlassian, as new features lead on to new ideas.\n\n
Every developer can create a copy of a DVCS repository on their own PC, this is called a clone. The cloned repository has the full history of the original repository and so you can trace back through all the changes that were ever done for that project.\n\nAs we are using change sets to record the change rather than individual file changes, then it is easier to manage many different branches (Forks), especially when using pull requests.\n\nPull requests give an opportunity for code review, integration testing and continuous integration builds to run.\n\n
The way you work with DVCS commands (for both Git & Mercurial) are very similar to the subversion and CVS commands used. As DVCS has an additional remote repository (usually called the origin in Open Source projects) there is one extra optional step.\n\nIf you do not need to share your whole repository with anyone, there is no need to push your repository to another one.\n\nIf you want to submit a simple change, you can package it up as a pull request - a request to have your specific change pulled into someone elses repository. For example if you fork someones project on Bitbucket, making a copy that has a link back to the original repository, you can make changes to your copy of the code, commit them to your own repository and then create a pull request using the magic button on Bitbucket to send a message back to the owner of the repository. If the owner likes your change, it will be added into their repository and become officially part of the project.\n\n\n
Previously we showed the commands for git you enter on your operating system command line, you can uses visual tools like SourceTree from Atlassian to manage the whole workflow.\n\nIt seems the command line is like Marmite, you either love it or hate it. [Add your own opinion here if you wish]\n
Previously we showed the commands for git you enter on your operating system command line, you can uses visual tools like SourceTree from Atlassian to manage the whole workflow.\n\nIt seems the command line is like Marmite, you either love it or hate it. [Add your own opinion here if you wish]\n
Previously we showed the commands for git you enter on your operating system command line, you can uses visual tools like SourceTree from Atlassian to manage the whole workflow.\n\nIt seems the command line is like Marmite, you either love it or hate it. [Add your own opinion here if you wish]\n
- You don’t have to use DVCS full power right away\n- Feel safe at home by keeping your workflow\n- Explore the possibilities as you get more familiar with the tool\n\n
\n
\n
\n
\n
\n
The following should be a slide in their own right....\n\n\nBring our history with us. The team wanted the Mercurial repository to resemble it’s Subversion counterpart as much as possible. We wanted to have the all the history contributing to our development branch (trunk) as well as our two supported release branches (2.2 and 2.3 at the time). Other branches such as fedex branches and 20% time were less important but ideally converted as well. We were happy to exclude accidental commits and commits of large files from the conversion.\nTool Integration. We wanted to make sure the tools and software that we used for development provided the same level of integration with Mercurial as they do for Subversion. These were mainly FishEye, Crucible, Bamboo, Eclipse and Intellij IDEA.\nIncremental. The conversion should be performed incrementally. This was incredibly important in order to ensure that the history was how we expected it, system integration worked and everyone could perform their development tasks without running into problems due to Mercurial. This was also important in minimising the disruptions that would occur for developers.\nReplicate team process. At least initially, we wanted to replicate the current Subversion development workflow using Mercurial. We were happy the experiment with other workflows which aren’t possible in subversion after the initial migration.\n\n
Share the knowledge around the team\n\n\n
Using SourceTree to help us work with our code in DVCS systems so we don’t have to learn the command line.\n\n
Using SourceTree to help us work with our code in DVCS systems so we don’t have to learn the command line.\n\n
\n
View file history \nView authors/blame - BB or Stash\nSwitching/creating a branch - BB\nListing Tags\n\n
[Add stuff about crucible and DVCS]\n
View file history \nView authors/blame - BB or Stash\nSwitching/creating a branch - BB\n\n\n
View file history \nView authors/blame - BB or Stash\nSwitching/creating a branch - BB\nListing Tags\n\n
\n
Show how you write JIRA issue numbers in your commit statements to link up your commits with the issues in JIRA that commit addresses.\n\nThen cover how Crucible uses that JIRA number in commit to help you find the right review\n
\n
Share the knowledge around the team\n\n\n
Using a good tool you can start using the power of DVCS whist still having a subversion repository. Using things like GitSVN you can have local git repos that will push to a subversion.\n\nGive developers a chance to learn the tools well, so you are not slowing down the development process or making it too frustrating.\n\nDVCS is a new skill, so give your teams time to adopt.\n
Bring as much of the history from Subversion as you can, its an important record of your development.\n\nMake sure code is checked into the subversion, then make it read only\n
Share the knowledge around the team\n\n\n
Include a person of experience with DVCS in the team\nThe knowledge and experience spreads round the team\nMove people with DVCD experience around teams\n
Include a person of experience with DVCS in the team\nThe knowledge and experience spreads round the team\nMove people with DVCD experience around teams\n
Include a person of experience with DVCS in the team\nThe knowledge and experience spreads round the team\nMove people with DVCD experience around teams\n
Include a person of experience with DVCS in the team\nThe knowledge and experience spreads round the team\nMove people with DVCD experience around teams\n
Include a person of experience with DVCS in the team\nThe knowledge and experience spreads round the team\nMove people with DVCD experience around teams\n
Everything is on your own machine - don’t be afraid to mess up, it is easy to get back into a stage where things are stable.\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
\n
Be a coding ninja and commit all your changes early and often. Typically you write a failing unit test, then commit. Write some code to pass the tests and then commit. Think about refactoring and the start all over again.\n\nSome developers say the code is the documentation, but the code is just the present. By giving meaningful commit messages anyone can review the code and have a better understanding of how that code evolved.\n
Be a coding ninja and commit all your changes early and often. Typically you write a failing unit test, then commit. Write some code to pass the tests and then commit. Think about refactoring and the start all over again.\n\nSome developers say the code is the documentation, but the code is just the present. By giving meaningful commit messages anyone can review the code and have a better understanding of how that code evolved.\n
Share the knowledge around the team\n\n\n
I got the need, the need for SPEED (we like to drive fast)\n Common commands, just faster - status, log, commit, branch/merge are instantaneous\n The speed with which DVCS carries out common tasks lowers the bar and encourages developers in making use of those procedures. That, in turn, means that teams are using their version control system in more versatile and effective ways.\n Dev history without going over the network\nFast tool = Happy Developers\n No Servers bogging you down - push when you are ready\n Commit often\n Use the features instead of bypassing them bc they are slow\nCode without limitations\n Do "stuff" after the fact\n apply changes to a different branch <cmd>\n need more here....\n Jump between and modify branches\n need more here...\n \nAs stated in the previous slides, common commands become useful again. When commands are instantaneous that are used more often than not. Think back to any fuction in JIRA or Confluence...if they were not easily accesible you may not use them. Same with version control - if they take time or the commands are advanced you may not use the full power of the technology.\n\n\nYou will use the command line as its faster ???\n\n\nExample to give ambassadors context: Working without a network connection to your subversion repository is more than just committing the changes. If you make a mistake in a file or try a spike solution, and want to start over, you can&#x2019;t until the network returns. If you want to diff between previous versions to help find a problem, you can&#x2019;t until the network returns.\n\nDVCS allows you to utilize version control during your development without contaminating the team repository.\n
Developers have a clearer understanding of the impact of their work, both in the benefits they deliver to the customers and the potential problems if issues should arise.\n\nMore lessons learnt throughout the whole company. Small changes that build on each other are easier to absorb and get meaningful feedback, in a way that a big bang approach does not.\n\nFeeback from customers (dogfooding or OnDemand) make better products as Atlassian has a better understanding of the customer experience.\n
Naturally, as we use DVCS ourselves, all our products work with DVCS tools.\n
Naturally, as we use DVCS ourselves, all our products work with DVCS tools.\n
[A very quick wrap up, just to get people to sign up to Bitbucket for free, for unlimited public or private repositories. Also to download SourceTree for the MacOSX]\n\n- Bitbucket\n- Sourcetree\n- Making the change recipe\n- DVCS microsite\n- Blog series\n- integration with all our tools\n\n