What does it mean to 'do' Continuous Integration? It used to be enough to execute your unit tests in CI. But the bar is steadily raising for engineering practices. In the last decade we've seen tremendous improvements inacceptance testing. JavaScript is now a platform in it's own right. Cloudcomputing is now vital. There's growing interest in deployment to prod.So Continuous Integration is under more pressure than ever. As the bar slowly raises for engineering practices, we ll present 2011's minimum viable feature set for Continuous Integration
Introduction of Continuous Integration (CI)
* Try to answer questions from developers, testers, team leaders, and managers.
* The topology and features of CI.
* How can CI reduce risks?
Continuous Integration (CI) - An effective development practiceDao Ngoc Kien
This document introduces a very effective practice of software development method called Continuous Integration.
CTO/Manager of IT company (outsource/startup company) should have a look.
Introduction of Continuous Integration (CI)
* Try to answer questions from developers, testers, team leaders, and managers.
* The topology and features of CI.
* How can CI reduce risks?
Continuous Integration (CI) - An effective development practiceDao Ngoc Kien
This document introduces a very effective practice of software development method called Continuous Integration.
CTO/Manager of IT company (outsource/startup company) should have a look.
Workshop on continuous Integration by Priyanka Hasija and Shilpi Mittal. The concept was introduced to audience with the help of couple of scenarios contrasting projects with CI and without CI. Then they were asked to install Jenkins on their machines and integrate maven project created in previous workshop.
Quick guide about "WSO2 IoT Server Device Manufacturer Guide" (https://docs.wso2.com/display/IoTS300/Device+Manufacturer+Guide), including function description, source code brief, how to start, and some troubleshooting.
Usg Web Tech Day 2016 - Continuous Integration, Deployment, and DeliveryStephen Garrett
One developer, one machine, one sacred build process. For the past two years, we have worked to change this story into one that is more reliable, repeatable, and reproducible. I'll show you our process and give plenty of demos of how we safely push code into production multiple times per day.
Today’s cutting edge companies have software release cycles measured in days instead of months. This agility is enabled by the DevOps practice of continuous delivery, which automates building, testing, and deploying all code changes. This automation helps you catch bugs sooner and accelerates developer productivity. In this session, we’ll share best practices (including ones followed internally at Amazon) and how you can bring them to your company by using open source and AWS services.
Speaker: Raghuraman Balachandran, Solutions Architect, Amazon India
Slides from my presentation in JavaOne 2016 on the topic of how to keep your CI/CD pipeline under control. Don't let it grow to unmanageable build times! Learn to find out when your pipeline is too slow and you need to do something about it, and when it's fine and you can just carry on with your life.
Integration Testing as Validation and MonitoringMelissa Benua
In the world of software-as-a-service, just about anyone with a laptop and an Internet connection can spin up their very own cloud-based web service. Software startups, in particular, are often big on ideas but small on staff. This makes streamlining the traditional develop-test-integrate-deploy-monitor pipeline critically important. Melissa Benua says that an effective way to accomplish this is to reduce the number of different test suites that verify many of the same things for each stage. Melissa explains how teams can avoid this by authoring the right set of tests and using the right frameworks. Drawing on lessons learned in companies both large and small, Melissa shows how teams can drastically slash time spent developing automation, verifying builds for release, and monitoring code in production—without sacrificing availability or reliability.
The presentation from my talk on Continuous Integration and Builds at XP Days Indore 2010. The target audience was MCA students, faculty and members of IT industry in and around Indore.
Continuous Integration: How I stopped guessing if that merge was badJoe Ferguson
Continuous integration / deployment can be a daunting task. Especially if you are a team of one, or one among a small team. TeamCity is "continuous integration for everyone" It's a self hosted CI build server that is highly customizable for just about any project. I've built RocketFuel's CI/CD system on a spare box with TeamCity and customized it to handle legacy PHP applications and modern framework based projects. We'll cover install and configuration and all of the flexibility of setting up projects at that build, test, report errors, and trigger deployments for various application scenarios.
One of the challenges faced by many web development based projects is the integration of source code for multiple releases during parallel development. The task to build and test the multiple versions of source code can eat out the quality time and limit the efficiency of the development/QA team. The case study focuses to resolve the issues of extensive effort consumed in build and deployment process from multiple branches in source repository and aim at Identification of source code integration issues at the earliest stage. This can further be enhanced to limit the manual intervention by integration of build system with test automation tool.
The above can be achieved by using different CI tools (like Hudson/Bamboo/TeamCity/CruiseControl etc) for continuous build preparation and its integration with any test automation suite. The case study specifies the use of CI-Hudson tool for continuous integration using ANT tool for build preparation and further invoking the automation test suite developed using selenium. It also discusses the limitations and challenges of using such an integration system for testing a web based application deployed on Apache Tomcat server. It also details additional plugins available to enhance such an integration of multiple systems and what can be achieved using the above integration.
At J and Beyond 2011, I presented a session about using Continuous integration processes during Joomla and PHP development. I present the concepts of CI, and give some direction where to start setting it up yourself.
Continuous Delivery with TFS msbuild msdeployPeter Gfader
If you are deploying your software manually, you are doing it wrong.
If you deploying once a month, you are doing it wrong.
If you as a developer are deploying from Visual Studio by clicking "Publish", you are doing it wrong.
If a bug-fix takes you 1 hour but your customer needs to wait a week until he gets it, you are doing it wrong.
Manual deployments are NOT fun. See a good way on how to automate the deployment with TFS 2010, msbuild and msdeploy.
Workshop on continuous Integration by Priyanka Hasija and Shilpi Mittal. The concept was introduced to audience with the help of couple of scenarios contrasting projects with CI and without CI. Then they were asked to install Jenkins on their machines and integrate maven project created in previous workshop.
Quick guide about "WSO2 IoT Server Device Manufacturer Guide" (https://docs.wso2.com/display/IoTS300/Device+Manufacturer+Guide), including function description, source code brief, how to start, and some troubleshooting.
Usg Web Tech Day 2016 - Continuous Integration, Deployment, and DeliveryStephen Garrett
One developer, one machine, one sacred build process. For the past two years, we have worked to change this story into one that is more reliable, repeatable, and reproducible. I'll show you our process and give plenty of demos of how we safely push code into production multiple times per day.
Today’s cutting edge companies have software release cycles measured in days instead of months. This agility is enabled by the DevOps practice of continuous delivery, which automates building, testing, and deploying all code changes. This automation helps you catch bugs sooner and accelerates developer productivity. In this session, we’ll share best practices (including ones followed internally at Amazon) and how you can bring them to your company by using open source and AWS services.
Speaker: Raghuraman Balachandran, Solutions Architect, Amazon India
Slides from my presentation in JavaOne 2016 on the topic of how to keep your CI/CD pipeline under control. Don't let it grow to unmanageable build times! Learn to find out when your pipeline is too slow and you need to do something about it, and when it's fine and you can just carry on with your life.
Integration Testing as Validation and MonitoringMelissa Benua
In the world of software-as-a-service, just about anyone with a laptop and an Internet connection can spin up their very own cloud-based web service. Software startups, in particular, are often big on ideas but small on staff. This makes streamlining the traditional develop-test-integrate-deploy-monitor pipeline critically important. Melissa Benua says that an effective way to accomplish this is to reduce the number of different test suites that verify many of the same things for each stage. Melissa explains how teams can avoid this by authoring the right set of tests and using the right frameworks. Drawing on lessons learned in companies both large and small, Melissa shows how teams can drastically slash time spent developing automation, verifying builds for release, and monitoring code in production—without sacrificing availability or reliability.
The presentation from my talk on Continuous Integration and Builds at XP Days Indore 2010. The target audience was MCA students, faculty and members of IT industry in and around Indore.
Continuous Integration: How I stopped guessing if that merge was badJoe Ferguson
Continuous integration / deployment can be a daunting task. Especially if you are a team of one, or one among a small team. TeamCity is "continuous integration for everyone" It's a self hosted CI build server that is highly customizable for just about any project. I've built RocketFuel's CI/CD system on a spare box with TeamCity and customized it to handle legacy PHP applications and modern framework based projects. We'll cover install and configuration and all of the flexibility of setting up projects at that build, test, report errors, and trigger deployments for various application scenarios.
One of the challenges faced by many web development based projects is the integration of source code for multiple releases during parallel development. The task to build and test the multiple versions of source code can eat out the quality time and limit the efficiency of the development/QA team. The case study focuses to resolve the issues of extensive effort consumed in build and deployment process from multiple branches in source repository and aim at Identification of source code integration issues at the earliest stage. This can further be enhanced to limit the manual intervention by integration of build system with test automation tool.
The above can be achieved by using different CI tools (like Hudson/Bamboo/TeamCity/CruiseControl etc) for continuous build preparation and its integration with any test automation suite. The case study specifies the use of CI-Hudson tool for continuous integration using ANT tool for build preparation and further invoking the automation test suite developed using selenium. It also discusses the limitations and challenges of using such an integration system for testing a web based application deployed on Apache Tomcat server. It also details additional plugins available to enhance such an integration of multiple systems and what can be achieved using the above integration.
At J and Beyond 2011, I presented a session about using Continuous integration processes during Joomla and PHP development. I present the concepts of CI, and give some direction where to start setting it up yourself.
Continuous Delivery with TFS msbuild msdeployPeter Gfader
If you are deploying your software manually, you are doing it wrong.
If you deploying once a month, you are doing it wrong.
If you as a developer are deploying from Visual Studio by clicking "Publish", you are doing it wrong.
If a bug-fix takes you 1 hour but your customer needs to wait a week until he gets it, you are doing it wrong.
Manual deployments are NOT fun. See a good way on how to automate the deployment with TFS 2010, msbuild and msdeploy.
An almost complete continuous delivery pipeline including configuration manag...ulfmansson
How we have created a build pipeline for continous delivery at Recorded Future. This includes also test of Chef cookbooks and configuration.
Presentation at
Config Management Camp 2014
Continuous Delivery Pipeline - Patterns and Anti-patternsSonatype
Juni Mukherjee, Consultant CI/CD, Lifelock
Continuous Delivery (CD) is important for a business to be sustainable. However, CD is not a discipline on it’s own (not yet), and the science behind it is rarely covered in schools.
The intended audience for this talk are engineers, architects and technical managers who are starting out to build Continuous Delivery Pipelines, or are seeking to improve ROI on their existing investments.
Every company aspires to sustainably flow their ideas into the hands of their customers, and reduce Time2Market. This talk goes into the heart of this burning topic and provides technical recipes that the audience can take away.
This talk would cover:
a) Domain Driven Design (DDD) for CD, based on concepts authored by Eric Evans
The Continuous Delivery Pipeline can be modeled as a domain.
b) How the CD Pipeline, along with its assets, can be orchestrated with Jenkins
The Continuous Delivery Pipeline domain can be orchestrated with Jenkins 2.0, aka Pipeline-as-code. Each box in the model could be authored as a stage in Jenkinsfile.
c) Pipeline patterns and anti-patterns
There are some trends that are consistently observed in the industry.
d) KPIs to measure ROI from the Pipeline
“Show me the money!”. This is the “Jerry Maguire moment”, whereby the ROI is demonstrated.
L’intégration continue chez AXA FranceMicrosoft
Dans un contexte agile, AXA France Service a mis en place une démarche d'intégration continue au sein de son Web Center. Lors de cette session, nous allons voir comment personnaliser le processus de Build en y incluant des tests unitaires, des métriques de qualité comme la couverture de code puis la déployer en continue avec le lab management de Team Foundation Server 2012.
Fast deterministic screenshot tests for AndroidArnold Noronha
This is the slides from my presentation at Droidcon NYC 2015. We talk about the library we're open sourcing, and how you can use it to both iterate fast on UI code, and catch regressions in continuous integration.
(Seleniumcamp) Selenium RC for QA EngineerYan Alexeenko
The Selenium RC opportunities, problems and some features in work with it for cross-browser testing (Firefox, Internet Explorer, Safari, Google Chrome) are presented in the presentation. The issues, concerning testing automation start, the points of testing, performed data, test synchronization problems and different solutions of these problems are considered. Beside that, application testing problems, using Flash and Silverlight, file loading variants, XSS injections are discussed.
Adopting DevOps in an organization can start in many ways but from the technical perspective, a solid continuous integration environment is the mandatory foundation for many of the tools used by a DevOps team. This webinar shows how to build a continuous integration environment on Amazon Web Services (AWS) using services such as Amazon EC2, Amazon RDS and AWS CloudFormation. We also cover the benefits of using Amazon VPC to enable VPN access to the environment components, such as the source code repository, or the issue tracking database.
Demos included in this webinar:
- Building a core continuous integration environment with components such as Jenkins, Git and Bugzila, using Amazon EC2, Amazon RDS and Amazon CloudFormation.
- Baseline maintenance of the continuous integration environment.
View the Recording: http://youtu.be/5dJxhX1ChT4
Getting your mobile test automation process in place - using Cucumber and Cal...Niels Frydenholm
Taking your mobile development process cycle, and the quality of the apps, from good to great.
See how focusing on automated tests can improve app quality, time to market and much more, and learn some best practices to avoid too much trouble getting started
Presented at Xamarin Evolve 2014
The options for hosting ruby web application are plentiful, all with different advantages and disadvantages, options, limitations. How to start, how to grow, what are the pitfalls?
With this talk I’d first like to give a short overview of several cloud hosting alternatives such as plain VPS, AWS, EngineYard, Heroku, and provide some insights based on my experience with them – beyond just somehow getting it to run, but also how to handle continuous deployment, how to maintain and scale them.
While Rails already comes with many best practices build in, there are still plenty enough traps for you. We definitely had our fair share, and I’d like to share some of them for your entertainment and learning.
Introduction to cypress in Angular (Chinese)Hong Tat Yew
Cypress framework is a JavaScript-based end-to-end testing framework built on top of Mocha – a feature-rich JavaScript test framework running on and in the browser, making asynchronous testing simple and convenient. Cypress is like Protractor for Angular. In this talk, we will talk about how to write cypress test from scratch and some best practice.
At GOTO Amsterdam in 2019 I presented how to create an effective cloud native developer workflow. Two years later and many new developer technologies have come and gone, but I still hear daily from cloud developers about the pain and friction associated with building, debugging, and deploying to the cloud. In this talk I'll share my latest learning on how to bring the fun and productivity back into delivering Kubernetes-based software.
In this talk, you will:
- Learn why the core tenets of continuous delivery -- speed and safety -- must be considered in all parts of the cloud native SDLC
- Explore how cloud native coding benefits from thinking separately about the inner development loop, continuous integration, continuous deployment, observability, and analysis
- Understand how cloud native best practices and tooling fit together. Learn about artifact syncing (e.g. Skaffold), dev environment bridging (e.g. Telepresence), GitOps (e.g. Argo), and observability-focused monitoring (e.g. Prometheus, Jaeger)
- Explore the importance of cultivating an effective cloud platform and associated team of experts
- Walk away with an overview of tools that can help you develop and debug effectively when using Kubernetes
GOTOpia 2/2021 "Cloud Native Development Without the Toil: An Overview of Pra...Daniel Bryant
At GOTO Amsterdam in 2019 I presented how to create an effective cloud native developer workflow. Two years later and many new developer technologies have come and gone, but I still hear daily from cloud developers about the pain and friction associated with building, debugging, and deploying to the cloud. In this talk I'll share my latest learning on how to bring the fun and productivity back into delivering Kubernetes-based software.
Join this talk to:
Learn why the core tenets of continuous delivery -- speed and safety -- must be considered in all parts of the cloud native SDLC
Explore how cloud native coding benefits from thinking separately about the inner development loop, continuous integration, continuous deployment, observability, and analysis
Understand how cloud native best practices and tooling fit together. Learn about artifact syncing (e.g. Skaffold), dev environment bridging (e.g. Telepresence), GitOps (e.g. Argo), and observability-focused monitoring (e.g. Prometheus, Jaeger)
Explore the importance of cultivating an effective cloud platform and associated team of experts
Walk away with an overview of tools that can help you develop and debug effectively when using Kubernetes
OSDC 2013 | Introduction into Chef by Andy HawkinsNETWAYS
This presentation will give an overview about what Chef is and how to access it. It will describe the typical use cases and architecture as well as Cookbooks, data bags and other concepts and will explain how to implement your CM solution. Finally it will show how to drive a successful Chef project.
In this session we'll discuss and demonstrate key concepts and design patterns for continuous deployment and integration using technologies like AWS OpsWorks and Chef to enable better control of applications and infrastructures.
Continuous delivery applied (DC CI User Group)Mike McGarr
These are slides I used to present to the DC Continuous Integration, Delivery and Deployment User Group on
Writing code is fun, but deploying to production is not. Production releases are scary events that last all weekend, and you find yourself worrying about how it will go. Did we miss a configuration file? Is the database schema the same as the one in the test environment? Does the last minute hot fix we just applied break any other features? Did I forget to include an installation instruction for the system administrators?
Continuous Delivery is a collection of principles and practices aimed at addressing the problems teams typically face when releasing changes to production. By applying rigorous automation, testing and configuration management, teams are able to confidently and consistently deploy changes from version control to production without fear.
In this talk, Mike McGarr will provide listeners with an introduction into the world of Continuous Delivery. After an introduction into the concepts and principles of Continuous Delivery, he will discuss many of the techniques for implementing Continuous Delivery and recommend some tools that can be used on your development project.
Over the past 1.5 decade our industry has tried to adopt an increased amount of infrastructure automation. We called it Configuration Management, Infrastructure as Code, infrastructure as Software, Provisioning, Orchestration. We learned about Desired State, Idempotence, etc.. We have seen a number of tools become popular; we have seen a number of tools disappear. But over the years we have seen a number of patterns appear and reappear. Patterns that lead to actually getting great benefits out of automation, or just wasting time while missing out on goals. This talk will explain you a number of these patterns which we have frequently encountered in the wild, with their benefits and caveats. We will try to keep this tool agnostic. Your vision might be Clouded, and you might have to take this with a grain of Salt while you play the Chef from the Muppet show the story, all names, characters, and incidents portrayed in this production are fictitious. No identification with actual persons (living or deceased), places, buildings, and products are intended or should be inferred.
JAX London 2021: Jumpstart Your Cloud Native Development: An Overview of Prac...Daniel Bryant
At a previous JAX event I talked about effective cloud native Java developer workflow. Two years later and many new developer technologies have come and gone, but I still hear daily from cloud developers about the pain and friction associated with building, debugging, and deploying to the cloud. In this talk I’ll share my latest learning on how to bring the fun and productivity back into delivering Kubernetes-based software.
Join this talk to:
Learn why the core tenets of continuous delivery — speed and safety — must be considered in all parts of the cloud native SDLC
Explore how cloud native coding benefits from thinking separately about the inner development loop, continuous integration, continuous deployment, observability, and analysis
Understand how cloud native best practices and tooling fit together. Learn about artifact syncing (e.g. Skaffold), dev environment bridging (e.g. Telepresence), GitOps (e.g. Argo), and observability-focused monitoring (e.g. Prometheus, Jaeger)
Explore the importance of cultivating an effective cloud platform and associated team of experts
Walk away with an overview of tools that can help you develop and debug effectively when using Kubernetes
Ten query tuning techniques every SQL Server programmer should knowKevin Kline
From the noted database expert and author of 'SQL in a Nutshell' - SELECT statements have a reputation for being very easy to write, but hard to write very well. This session will take you through ten of the most problematic patterns and anti-patterns when writing queries and how to deal with them all. Loaded with live demonstrations and useful techniques, this session will teach you how to take your SQL Server queries mundane to masterful.
Web Performance tuning presentation given at http://www.chippewavalleycodecamp.com/
Covers basic http flow, measuring performance, common changes to improve performance now, and several tools and techniques you can use now.
Similar to Continuous Integration, the minimum viable product (20)
Everything I learned about Continuous Integration, I learned from Systems Adm...Julian Simpson
DevOpsDays Gothenburg presentation where we explain how an earlier career in Systems Administration helped us kick ass in running Continuous Integration.
This is my presentation from the DevOps track at QCon 2010, where I attempt to explain what's going wrong with the industry, and what to do at the coalface to fix things
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
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.
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.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
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
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/
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.
11. CI Principles
• Build and test everything, when it changes
• The database schema counts as everything
12. CI Principles
• Build and test everything, when it changes
• The database schema counts as everything
• Tests count as everything
13. CI Principles
• Build and test everything, when it changes
• The database schema counts as everything
• Tests count as everything
• And JavaScript
14. CI Principles
• Build and test everything, when it changes
• The database schema counts as everything
• Tests count as everything
• And JavaScript
• Check in often and early
15. CI Principles
• Build and test everything, when it changes
• The database schema counts as everything
• Tests count as everything
• And JavaScript
• Check in often and early
• Builds are feedback
32. Scaling
• Solid State Disks are your friend
• Scaling tests is a different concern: http://
test-load-balancer.github.com/
33. Scaling
• Solid State Disks are your friend
• Scaling tests is a different concern: http://
test-load-balancer.github.com/
• Don’t fake infrastructure to make it fast
45. DevOps
• most misunderstood meme of recent times
• agile approach to systems admin
http://www.flickr.com/photos/shaggypaul/193098324/
46. DevOps
• most misunderstood meme of recent times
• agile approach to systems admin
• developer-sysadmin collaboration
http://www.flickr.com/photos/shaggypaul/193098324/
47. DevOps
• most misunderstood meme of recent times
• agile approach to systems admin
• developer-sysadmin collaboration
• provides feedback to the business
http://www.flickr.com/photos/shaggypaul/193098324/
51. Production
• Deployment scripts should be rehearsed in
CI
• CI servers should be built the same way as
prod
• Tools like Puppet and Chef help you do
that
53. New server: 45 seconds
knox:infrastructure jsimpson$
rake puppet:remote
bundle exec lib/instance.rb
Node ready at 44.457065
bootstrapping at 44.457127
setting the ssh hostkey at 44.457141
copying the code over at 44.828861
about to make code dir at 44.828986
About to rsync at 45.731777
54. Slowest part? My ISP
Rsync done at 327.996322
bootstrapping rubygems at 327.997617
updating system config
Extracting templates from packages: 100%
Successfully installed bundler-1.0.15
1 gem installed
Building native extensions. This could
take a while...
Successfully installed json-1.5.3
1 gem installed
bootstrapped rubygems at 366.733525
bootstrapping at 366.733569
bootstrapped at 366.733608
bootstrapped at 373.198161
60. Thank you
Any Questions?
@builddoctor
julian@build-doctor.com
Editor's Notes
Explain that chris is not an imaginary friend\nDo the experience check\nExplain the vagueness in pitching\nask them to ask questions\nexplai\n \n\n\n
Explain Chris\nDo the experience check\nAsk for questions\nTake a deep fucking breath\n\n
This is the existing metaphor for CI\n“Toyoda’s automatic loom stopped whenever the thread of the warp was snapped, .. the loom could not produce defectives, because it had an automatic stopping device”\nBut CI is not about machines, it’s about peopl;e\n
\n
This is CM done wrong\n
Which leads to this\n
it should be this\n
The 1840’s called, they want your CI status back\n
1. CI Principles\nBuild everything, whenever it changes\nSingle Source of Truth\nthe database schema counts as everything\nthe tests count as everything\nCheck in frequently\nWe all build together (ie Branching is Bad!)\nFEEDBACK!\n\n
1. CI Principles\nBuild everything, whenever it changes\nSingle Source of Truth\nthe database schema counts as everything\nthe tests count as everything\nCheck in frequently\nWe all build together (ie Branching is Bad!)\nFEEDBACK!\n\n
1. CI Principles\nBuild everything, whenever it changes\nSingle Source of Truth\nthe database schema counts as everything\nthe tests count as everything\nCheck in frequently\nWe all build together (ie Branching is Bad!)\nFEEDBACK!\n\n
1. CI Principles\nBuild everything, whenever it changes\nSingle Source of Truth\nthe database schema counts as everything\nthe tests count as everything\nCheck in frequently\nWe all build together (ie Branching is Bad!)\nFEEDBACK!\n\n
1. CI Principles\nBuild everything, whenever it changes\nSingle Source of Truth\nthe database schema counts as everything\nthe tests count as everything\nCheck in frequently\nWe all build together (ie Branching is Bad!)\nFEEDBACK!\n\n
1. CI Principles\nBuild everything, whenever it changes\nSingle Source of Truth\nthe database schema counts as everything\nthe tests count as everything\nCheck in frequently\nWe all build together (ie Branching is Bad!)\nFEEDBACK!\n\n
\n
\n
AR migrations, dbdeploy, dbdeploy.net, tarantino, dbmigrate, et al\nDML and DDL must never meet\nReference data may depend on a schema\ntest it realistically - test against a real dataset if you can\n\n \n\n
AR migrations, dbdeploy, dbdeploy.net, tarantino, dbmigrate, et al\nDML and DDL must never meet\nReference data may depend on a schema\ntest it realistically - test against a real dataset if you can\n\n \n\n
AR migrations, dbdeploy, dbdeploy.net, tarantino, dbmigrate, et al\nDML and DDL must never meet\nReference data may depend on a schema\ntest it realistically - test against a real dataset if you can\n\n \n\n
AR migrations, dbdeploy, dbdeploy.net, tarantino, dbmigrate, et al\nDML and DDL must never meet\nReference data may depend on a schema\ntest it realistically - test against a real dataset if you can\n\n \n\n
\n
\n
Don’t use email\nIf you use IDE or desktop widgets\nYou need to communicate the state to all\n\n\n
Don’t use email\nIf you use IDE or desktop widgets\nYou need to communicate the state to all\n\n\n
Don’t use email\nIf you use IDE or desktop widgets\nYou need to communicate the state to all\n\n\n
\n
\n\nNext is scaling your tests (Jules can allude to his current client on this one...)\n\nScaling your CI infrastructure:\n\nAOL incident \n\nAfter that you need to make sure your software can scale in production (twitter...) you can \n\nThen comes the feedback loop of testing scaling, and making sure that your test environment reflects all the moving parts of production accurately enough without trying to match the scale...\n\n
\n\nNext is scaling your tests (Jules can allude to his current client on this one...)\n\nScaling your CI infrastructure:\n\nAOL incident \n\nAfter that you need to make sure your software can scale in production (twitter...) you can \n\nThen comes the feedback loop of testing scaling, and making sure that your test environment reflects all the moving parts of production accurately enough without trying to match the scale...\n\n
\n\nNext is scaling your tests (Jules can allude to his current client on this one...)\n\nScaling your CI infrastructure:\n\nAOL incident \n\nAfter that you need to make sure your software can scale in production (twitter...) you can \n\nThen comes the feedback loop of testing scaling, and making sure that your test environment reflects all the moving parts of production accurately enough without trying to match the scale...\n\n
Web application testing is a core driver of CI pain\n
Web application testing is a core driver of CI pain\n
Web application testing is a core driver of CI pain\n
\n
\n
Key message. Have this proportion of tests.\nYou might not use the same tools for each tier\nA tool for testing the DOM is not a general purpose testing tool\nYou can make your application easier to test by disabling GUI features (e.g. ads, painful ajax interactions)\nGUI tests ideally will take a slice of functionality rather than logging in, testing and logging out.\nMost CI builds are slow because of GUI tests.\nParallelizing GUI tests is dangerous unless you attempt to optimise first\nSome browsers are assloads slower than others\n\n\n\n\n\n\n
\n
\n
You’re not a bloody devop\nThese are the people who didn’t want to be left behind\nCollaboration is #1\nPimp our other talk\n
You’re not a bloody devop\nThese are the people who didn’t want to be left behind\nCollaboration is #1\nPimp our other talk\n
You’re not a bloody devop\nThese are the people who didn’t want to be left behind\nCollaboration is #1\nPimp our other talk\n
You’re not a bloody devop\nThese are the people who didn’t want to be left behind\nCollaboration is #1\nPimp our other talk\n
The ultimate scaling - production\n\nThere is a lot we can talk about here about actually getting code in to production. Simple stuff like making sure your deployment scripts are treated as the top level code it is and tested accordingly...\n
The ultimate scaling - production\n\nThere is a lot we can talk about here about actually getting code in to production. Simple stuff like making sure your deployment scripts are treated as the top level code it is and tested accordingly...\n
The ultimate scaling - production\n\nThere is a lot we can talk about here about actually getting code in to production. Simple stuff like making sure your deployment scripts are treated as the top level code it is and tested accordingly...\n
\n
\n
\n
\n
\n
Demo of the build pipeline plugin\nVery engineer-focused approach\nSetting up the CD system is easy, retro-fitting all the tests to your app: hard\nNo excuse not to deploy all the time to staging systems\n\n\n
Focus on driving down cycle time\nGreater emphasis on app releases\nUsing all of the pluming of CD\nYou’re only done when you’re in prod\nvenn diagram?\nsits on pillars of previous\n