Continuous integration
•
0 likes•411 views
This document discusses the practices of continuous integration for building software features. It lists the key practices as maintaining a single source repository, automating builds, making builds self-testing, committing to the mainline daily, building every commit on an integration machine, keeping builds fast, testing in a clone of the production environment, and ensuring all work is visible to everyone. Continuous integration allows for more frequent integration and testing of code changes, which helps reduce the likelihood and impact of bugs.
Report
Share
Report
Share
Download to read offline
Recommended
MOTIVATE YOUR SELF.
This document provides 5 video links and encourages the reader to watch them before taking any action, in order to keep their mind strong and remember that they matter. The document lists 5 video links numbered 1 through 5 without any other context about the content or purpose of the videos.
MOVATIONAL LIFE
This document provides links to live streams about motivating yourself like never before. It contains three hyperlinks to live stream videos on the topics of motivation and self-improvement from Universal Income Institute. The first link calls the topic "IT IS MINDBLOWING!!!" and encourages watching a live stream over on their website.
Spring MVC
This document discusses the Model-View-Controller (MVC) framework and provides an example Spring MVC application structure. It shows the typical flow of an MVC app including the WEB-INF configuration files, controllers, and JSP view pages. It also includes the author's social media links.
Webpy
This document contains information about Jéferson Machado, including his social media links and areas of expertise in software design. It also references code and files for a Python web application, including an index.html file and questions about what the application is, how to install it, and who uses it. The document provides links to GitHub pages for the application code and a sandbox repository.
Gradle
This document provides an overview of Gradle, an open-source build automation tool. It discusses how Gradle offers flexibility and convention-based dependency management powered by Groovy. The document also covers installing Gradle, build phases, common plugins for languages and software development, and includes examples of using Gradle with Java projects. It concludes by inviting questions.
GROW
This document provides coaching tips for structuring a coaching session. It recommends using the tool as a map to focus the conversation. It also suggests asking open questions, listening well, enjoying silence, reflecting on goals, and preparing with notes. The document concludes by sharing the coach's social network information.
1 jeferson (grow)
This document provides coaching tips for structuring a coaching session. It recommends using the tool as a map to focus the conversation. It also suggests asking open questions, listening well, enjoying silence, reflecting on goals, and preparing with notes. The document concludes by sharing the coach's social network information.
Recommended
MOTIVATE YOUR SELF.
This document provides 5 video links and encourages the reader to watch them before taking any action, in order to keep their mind strong and remember that they matter. The document lists 5 video links numbered 1 through 5 without any other context about the content or purpose of the videos.
MOVATIONAL LIFE
This document provides links to live streams about motivating yourself like never before. It contains three hyperlinks to live stream videos on the topics of motivation and self-improvement from Universal Income Institute. The first link calls the topic "IT IS MINDBLOWING!!!" and encourages watching a live stream over on their website.
Spring MVC
This document discusses the Model-View-Controller (MVC) framework and provides an example Spring MVC application structure. It shows the typical flow of an MVC app including the WEB-INF configuration files, controllers, and JSP view pages. It also includes the author's social media links.
Webpy
This document contains information about Jéferson Machado, including his social media links and areas of expertise in software design. It also references code and files for a Python web application, including an index.html file and questions about what the application is, how to install it, and who uses it. The document provides links to GitHub pages for the application code and a sandbox repository.
Gradle
This document provides an overview of Gradle, an open-source build automation tool. It discusses how Gradle offers flexibility and convention-based dependency management powered by Groovy. The document also covers installing Gradle, build phases, common plugins for languages and software development, and includes examples of using Gradle with Java projects. It concludes by inviting questions.
GROW
This document provides coaching tips for structuring a coaching session. It recommends using the tool as a map to focus the conversation. It also suggests asking open questions, listening well, enjoying silence, reflecting on goals, and preparing with notes. The document concludes by sharing the coach's social network information.
1 jeferson (grow)
This document provides coaching tips for structuring a coaching session. It recommends using the tool as a map to focus the conversation. It also suggests asking open questions, listening well, enjoying silence, reflecting on goals, and preparing with notes. The document concludes by sharing the coach's social network information.
Of innovation and impatience - Future Decoded 2015
It is easy to think what we have as developers is what people use and that lead us to make the web bloated.
Design for Multitouch
This document discusses design considerations for multi-touch interfaces. It covers different touchscreen technologies, how the type of device impacts design choices, and principles for optimizing interfaces for touchscreens. Examples of touch-optimized websites are provided. The document concludes with references and credits for included images.
Designing the Priority, Performance ist User Experience
The document discusses designing for performance and priority user experience. It emphasizes that performance should be a priority from the beginning in concept, design, and development. It provides tips for setting performance budgets, prototyping early, and designing responsively with a mobile-first approach. The overall message is that performance is everyone's responsibility and needs to be a collaborative effort across teams.
The convergence of all things (wdu keynote)
The document discusses the evolution and future of web experiences across different devices and platforms. It notes how early web platforms lacked capabilities for rich experiences compared to native apps, but how modern web standards now provide access to device sensors, graphics, and other features. This allows the web to deliver more engaging experiences. The document advocates for building experiences that are responsive across different environments and devices, and pushing the capabilities of the web platform to better deliver digital services anywhere.
Chaos engineering - The art of breaking stuff in production on purpose
This document discusses chaos engineering, which is the practice of experimenting on a distributed system in production to build confidence in its ability to withstand failures. It describes introducing controlled failures or experiments to test a system's resilience. The key aspects covered are defining hypotheses about potential failures before experiments, designing and executing small experiments initially, learning from the results to identify issues, fixing any problems found, and embedding chaos engineering into the development process and culture. Patterns for building resilient systems like parallelism, async communication, and circuit breakers are also overviewed.
Single Page Web Apps
The document discusses single page web apps, which allow a web app to exist on a single page without reloading the DOM. Key points made include:
- Single page apps only update parts of the page rather than reloading the entire page, improving performance.
- They allow for immediate feedback and smooth transitions between states within the app.
- While they break links and expose business logic to users who inspect elements, they reduce server load and improve mobile experiences.
- Popular tools for building single page apps include Backbone.js, SammyJS, and Brunch.
Docker 101 - DevOps at EMC May 2015
This document introduces Docker containers as a way to deploy microservices applications. It begins by discussing how monolithic applications do not scale well and how microservices break applications into loosely coupled components. Containers are presented as a way to deploy one microservice component per container, providing isolation. Containers allow running many applications on the same host using fewer resources than virtual machines. The Docker ecosystem supports running many programming languages and frameworks in containers, and containers can be deployed anywhere due to their portability.
Aleksandar Vacić - iOS App Development iz Srbije
This document provides an overview of iOS app development from Serbia. It discusses the necessary hardware (Mac computer or Hackintosh), registering for the Apple Developer program, skills needed (Objective-C, Cocoa Touch), software tools (Xcode, Instruments), resources for learning and inspiration, potential for earning money, and finding contract work developing apps. Examples are given of successful apps that have earned millions of dollars. Rates for contract work are estimated at $100-150 per hour.
C# Powered Robots, C# Powered Mobile Apps
Have you ever wanted to build a robot? How about powering it and controlling it completely with C# and .NET? With Monkey.Robotics it is now completely possible. Come learn how Monkey.Robotics simplifies the tasks of building complex .NET Microframework power robots and how you can communicate with them from iOS and Android apps powered by Xamarin. We will take a look at the process of building a robot from start to finish. Then we will implement the microcontroller stack to communicate with sensors and other hardware on a Netduino. Then we will build out a full iOS and Android app in C# to control it!
From Zero to App-Super-Hero with Titanium
In this presentation Liz Myers shares the design strategy that went into building her app, 2Scoops, and demonstrates how to get started building mobile apps with Appcelerator Titanium. Also included here are Liz's favourite resources for app design & development.
Hybrid Apps with Ionic Framework
Want the slides with presenter notes? Get them here: https://www.bram.us/talks/2015/11/hybrid-apps-with-ionic-framework-withnotes.pdf
Faster Secure Software Development with Continuous Deployment - PH Days 2013
This document discusses moving to a continuous deployment model to improve software security. It argues that the traditional release-based model is harmful, especially for security, as it results in long delays between when code is written and deployed. Continuous deployment aims to deploy small changes frequently, with developers pushing their own code to production. This gets developers more invested in the quality and security of the code they write. It also allows faster fixing of bugs and security issues when they are found. The document outlines steps to gradually implement continuous deployment and address common concerns about its impact on quality, compliance, and customers.
[Wroclaw #4] Fuzzing - underestimated method of finding hidden bugs
This document discusses different types of fuzzing techniques to discover software vulnerabilities. It covers dumb, mutation-based fuzzing which randomly modifies sample input to test for crashes. It also covers smarter, instrumented fuzzing which requires recompiling software to track code coverage and generate new test cases. Generation-based or model-based fuzzing is explained where valid input models and states are defined to generate structured test cases. The document advocates adding fuzzing to the software development lifecycle as a complement to other security testing methods like static analysis and penetration testing. Fuzzing is presented as an effective way to find bugs through automated testing with invalid inputs.
Optimizing for Change (Henrik Joreteg)
1. Web development used to be simple but has become increasingly complex over time as new technologies and frameworks have emerged.
2. The document argues that there is a distinction between native web apps that run entirely in the browser using JavaScript and server-side web apps, and that both have valid uses.
3. It advocates for building single-page apps as native web apps using modern browser capabilities and deploying them as static sites for performance and simplicity while relying on external services for backend functionality.
4Developers 2015: Under the dome (of failure driven pipeline) - Maciej Lasyk
Speaker: Maciej Lasyk
Language: English
One day you woke up in a new reality and realized, that you live in a world of constant and unpredicted failure. Any closet you open you find a dead body - residue of unfinished projects, badly designed ideas etc. All this summed up gives you the real continuous disaster.
Fortunately your stamina bar is full and you have some super powers - it's time for the change. This will be a multithreaded story of getting from point A (stiff, old & depressing state) to point B (a bit closer to DevOPS Nirvana); I'll discuss here multiple elements of the journey: trust & collaboration, changing the work - environment culture, guerilla capacity planning, redesigning infrastructure architecture (w/Mikado help), automating leadership tasks, choosing between IaaS and PaaS (embracing virtualization / containers technologies and making those work for you), designing developer's environments, working with Kanban/Lean, automation and ITIL, and finally - joining this all into one big - picture. Archeological elements included. With real - life scenarios :)
4Developers: http://4developers.org.pl/pl/
Under the Dome (of failure driven pipeline)
The document discusses various topics related to DevOps including:
1. Different types of shells (login, non-login, interactive, non-interactive, su, sudo su, sudo -i, sudo /bin/bash, sudo -s) and how they affect environment variables and profile files.
2. Stories of organizational "anti-types" that go against DevOps principles like not seeing the need for operations teams.
3. How automation, consistency, and reducing errors leads to stable environments and less unplanned work, allowing teams to focus on delivery.
Fuzzing underestimated method of finding hidden bugs
Fuzzing is a method of discovering software faults by providing unexpected input and monitoring for exceptions. There are two main types of fuzzers: mutation-based fuzzers which mutate valid samples, and generation-based fuzzers which require samples to be defined. Fuzzing discovers bugs by providing invalid input to any software, so it should always be considered as a testing method. A fuzzer contains an input generator, history of generated inputs, and a process monitor.
Leah Culver @ FOWA 08
The document discusses the future of web services and social messaging applications like Pownce. It notes that Pownce started as a desktop application but later became a website, mobile site, and supported various third-party integrations through APIs. The key aspects that define an application are said to be the code, technology, infrastructure, features, rules, and limitations, not the interfaces. The future of applications is predicted to involve simple, hosted environments and cloud computing, moving away from traditional web pages. APIs will continue to be important for interoperability between applications.
No more excuses left - let's build great things - Christian Heilmann - Codemo...
Codemotion Rome 2015 - As developers, we know things break. We also know how to fix them. What we don't do is do this efficiently. Instead we seem to have a perverse fascination telling one another and the world how broken things are. If you look, however, how cool technology is these days, what tools we have at our disposal and the latest changes in the last excuse we had: "What about IE?" it is time to stop complaining and get to work. Our job is to build things that people want to use. Not to complain about our tools. This is what people looking for excuses do. We're better than that.
JavaZone 2014: En realitetsorientering om Tingenenes Internett, og hvordan du...
Video: http://vimeo.com/105851449
Tingenes Internet - eller Internet of Things - er et av de mest hypede trendene akkurat nå. Utfordringen er å forstå hva som er hype, og hva som virkelig kan gi verdi. I tillegg er det en rivende teknologisk utvikling, med mange aktører som "kapper land". Nye allianser inngås hele tiden.
Fagsystemer kan også dra nytte av denne utviklingen, under helt andre forutsetninger. Du kan få forståelse for alt dette gjennom å prøve deg på litt hobbyelektronikk og noen enkle standarder og verktøy som MQTT og Node.red, som er ypperlig for å drive prototyping av Internet of Things systemer i bedrifter. Du vil dermed kunne få idéer til hvordan du kan involvere fysiske sensorer og indikatorer for å øke utstrekningen og verdiene av de fagsystemene du jobber med.
Først vil jeg gjennom en liten science-fiction fortelling vise hvordan IoT virkelig kan tjene oss i fremtiden. Og vi har en vei å gå innenfor sikkerhet, forretningsmodeller, personvern og standardisering før vi kommer dit!
Så går jeg over til å beskrive de mest lovende teknologiene og standardene, før jeg viser en live demo med en en sonar, Arduino, Raspberry PI, node.red MQTT, en snakkende hodeskalle, sensorer og Minecraft!
Jeg kommer til å gå detaljert gjennom MQTT og Node.red - teknologier som blant annet brukes av IBM for å raskt kunne lage prototyper på Internet-of-things prosjekter for store bedrifter. Dette kan være relevant for deg, da de fleste konsulentselskaper og firmaer etterhvert vil komme borti tingenes internett.
Jeg kommer til å vise meldingsflyt, kildekode og hvordan du selv kan komme i gang. Og om du rekker det, kan du i likhet meg meg lage en liten animatronics-velkomst som skremmer barna på Halloween...
druid.io
Druid.io presentation to show how druid.io works and how can he provide 100% of uptime through his Architecture.
Apache Spark Internals - Part 2
The idea of this presentation is to understand more about Apache Spark internals.
How it deals with resilience for each component, how Shard allocation works using RDD and how it abstract data partitioning and cluster distribution complexity.
More Related Content
Similar to Continuous integration
Of innovation and impatience - Future Decoded 2015
It is easy to think what we have as developers is what people use and that lead us to make the web bloated.
Design for Multitouch
This document discusses design considerations for multi-touch interfaces. It covers different touchscreen technologies, how the type of device impacts design choices, and principles for optimizing interfaces for touchscreens. Examples of touch-optimized websites are provided. The document concludes with references and credits for included images.
Designing the Priority, Performance ist User Experience
The document discusses designing for performance and priority user experience. It emphasizes that performance should be a priority from the beginning in concept, design, and development. It provides tips for setting performance budgets, prototyping early, and designing responsively with a mobile-first approach. The overall message is that performance is everyone's responsibility and needs to be a collaborative effort across teams.
The convergence of all things (wdu keynote)
The document discusses the evolution and future of web experiences across different devices and platforms. It notes how early web platforms lacked capabilities for rich experiences compared to native apps, but how modern web standards now provide access to device sensors, graphics, and other features. This allows the web to deliver more engaging experiences. The document advocates for building experiences that are responsive across different environments and devices, and pushing the capabilities of the web platform to better deliver digital services anywhere.
Chaos engineering - The art of breaking stuff in production on purpose
This document discusses chaos engineering, which is the practice of experimenting on a distributed system in production to build confidence in its ability to withstand failures. It describes introducing controlled failures or experiments to test a system's resilience. The key aspects covered are defining hypotheses about potential failures before experiments, designing and executing small experiments initially, learning from the results to identify issues, fixing any problems found, and embedding chaos engineering into the development process and culture. Patterns for building resilient systems like parallelism, async communication, and circuit breakers are also overviewed.
Single Page Web Apps
The document discusses single page web apps, which allow a web app to exist on a single page without reloading the DOM. Key points made include:
- Single page apps only update parts of the page rather than reloading the entire page, improving performance.
- They allow for immediate feedback and smooth transitions between states within the app.
- While they break links and expose business logic to users who inspect elements, they reduce server load and improve mobile experiences.
- Popular tools for building single page apps include Backbone.js, SammyJS, and Brunch.
Docker 101 - DevOps at EMC May 2015
This document introduces Docker containers as a way to deploy microservices applications. It begins by discussing how monolithic applications do not scale well and how microservices break applications into loosely coupled components. Containers are presented as a way to deploy one microservice component per container, providing isolation. Containers allow running many applications on the same host using fewer resources than virtual machines. The Docker ecosystem supports running many programming languages and frameworks in containers, and containers can be deployed anywhere due to their portability.
Aleksandar Vacić - iOS App Development iz Srbije
This document provides an overview of iOS app development from Serbia. It discusses the necessary hardware (Mac computer or Hackintosh), registering for the Apple Developer program, skills needed (Objective-C, Cocoa Touch), software tools (Xcode, Instruments), resources for learning and inspiration, potential for earning money, and finding contract work developing apps. Examples are given of successful apps that have earned millions of dollars. Rates for contract work are estimated at $100-150 per hour.
C# Powered Robots, C# Powered Mobile Apps
Have you ever wanted to build a robot? How about powering it and controlling it completely with C# and .NET? With Monkey.Robotics it is now completely possible. Come learn how Monkey.Robotics simplifies the tasks of building complex .NET Microframework power robots and how you can communicate with them from iOS and Android apps powered by Xamarin. We will take a look at the process of building a robot from start to finish. Then we will implement the microcontroller stack to communicate with sensors and other hardware on a Netduino. Then we will build out a full iOS and Android app in C# to control it!
From Zero to App-Super-Hero with Titanium
In this presentation Liz Myers shares the design strategy that went into building her app, 2Scoops, and demonstrates how to get started building mobile apps with Appcelerator Titanium. Also included here are Liz's favourite resources for app design & development.
Hybrid Apps with Ionic Framework
Want the slides with presenter notes? Get them here: https://www.bram.us/talks/2015/11/hybrid-apps-with-ionic-framework-withnotes.pdf
Faster Secure Software Development with Continuous Deployment - PH Days 2013
This document discusses moving to a continuous deployment model to improve software security. It argues that the traditional release-based model is harmful, especially for security, as it results in long delays between when code is written and deployed. Continuous deployment aims to deploy small changes frequently, with developers pushing their own code to production. This gets developers more invested in the quality and security of the code they write. It also allows faster fixing of bugs and security issues when they are found. The document outlines steps to gradually implement continuous deployment and address common concerns about its impact on quality, compliance, and customers.
[Wroclaw #4] Fuzzing - underestimated method of finding hidden bugs
This document discusses different types of fuzzing techniques to discover software vulnerabilities. It covers dumb, mutation-based fuzzing which randomly modifies sample input to test for crashes. It also covers smarter, instrumented fuzzing which requires recompiling software to track code coverage and generate new test cases. Generation-based or model-based fuzzing is explained where valid input models and states are defined to generate structured test cases. The document advocates adding fuzzing to the software development lifecycle as a complement to other security testing methods like static analysis and penetration testing. Fuzzing is presented as an effective way to find bugs through automated testing with invalid inputs.
Optimizing for Change (Henrik Joreteg)
1. Web development used to be simple but has become increasingly complex over time as new technologies and frameworks have emerged.
2. The document argues that there is a distinction between native web apps that run entirely in the browser using JavaScript and server-side web apps, and that both have valid uses.
3. It advocates for building single-page apps as native web apps using modern browser capabilities and deploying them as static sites for performance and simplicity while relying on external services for backend functionality.
4Developers 2015: Under the dome (of failure driven pipeline) - Maciej Lasyk
Speaker: Maciej Lasyk
Language: English
One day you woke up in a new reality and realized, that you live in a world of constant and unpredicted failure. Any closet you open you find a dead body - residue of unfinished projects, badly designed ideas etc. All this summed up gives you the real continuous disaster.
Fortunately your stamina bar is full and you have some super powers - it's time for the change. This will be a multithreaded story of getting from point A (stiff, old & depressing state) to point B (a bit closer to DevOPS Nirvana); I'll discuss here multiple elements of the journey: trust & collaboration, changing the work - environment culture, guerilla capacity planning, redesigning infrastructure architecture (w/Mikado help), automating leadership tasks, choosing between IaaS and PaaS (embracing virtualization / containers technologies and making those work for you), designing developer's environments, working with Kanban/Lean, automation and ITIL, and finally - joining this all into one big - picture. Archeological elements included. With real - life scenarios :)
4Developers: http://4developers.org.pl/pl/
Under the Dome (of failure driven pipeline)
The document discusses various topics related to DevOps including:
1. Different types of shells (login, non-login, interactive, non-interactive, su, sudo su, sudo -i, sudo /bin/bash, sudo -s) and how they affect environment variables and profile files.
2. Stories of organizational "anti-types" that go against DevOps principles like not seeing the need for operations teams.
3. How automation, consistency, and reducing errors leads to stable environments and less unplanned work, allowing teams to focus on delivery.
Fuzzing underestimated method of finding hidden bugs
Fuzzing is a method of discovering software faults by providing unexpected input and monitoring for exceptions. There are two main types of fuzzers: mutation-based fuzzers which mutate valid samples, and generation-based fuzzers which require samples to be defined. Fuzzing discovers bugs by providing invalid input to any software, so it should always be considered as a testing method. A fuzzer contains an input generator, history of generated inputs, and a process monitor.
Leah Culver @ FOWA 08
The document discusses the future of web services and social messaging applications like Pownce. It notes that Pownce started as a desktop application but later became a website, mobile site, and supported various third-party integrations through APIs. The key aspects that define an application are said to be the code, technology, infrastructure, features, rules, and limitations, not the interfaces. The future of applications is predicted to involve simple, hosted environments and cloud computing, moving away from traditional web pages. APIs will continue to be important for interoperability between applications.
No more excuses left - let's build great things - Christian Heilmann - Codemo...
Codemotion Rome 2015 - As developers, we know things break. We also know how to fix them. What we don't do is do this efficiently. Instead we seem to have a perverse fascination telling one another and the world how broken things are. If you look, however, how cool technology is these days, what tools we have at our disposal and the latest changes in the last excuse we had: "What about IE?" it is time to stop complaining and get to work. Our job is to build things that people want to use. Not to complain about our tools. This is what people looking for excuses do. We're better than that.
JavaZone 2014: En realitetsorientering om Tingenenes Internett, og hvordan du...
Video: http://vimeo.com/105851449
Tingenes Internet - eller Internet of Things - er et av de mest hypede trendene akkurat nå. Utfordringen er å forstå hva som er hype, og hva som virkelig kan gi verdi. I tillegg er det en rivende teknologisk utvikling, med mange aktører som "kapper land". Nye allianser inngås hele tiden.
Fagsystemer kan også dra nytte av denne utviklingen, under helt andre forutsetninger. Du kan få forståelse for alt dette gjennom å prøve deg på litt hobbyelektronikk og noen enkle standarder og verktøy som MQTT og Node.red, som er ypperlig for å drive prototyping av Internet of Things systemer i bedrifter. Du vil dermed kunne få idéer til hvordan du kan involvere fysiske sensorer og indikatorer for å øke utstrekningen og verdiene av de fagsystemene du jobber med.
Først vil jeg gjennom en liten science-fiction fortelling vise hvordan IoT virkelig kan tjene oss i fremtiden. Og vi har en vei å gå innenfor sikkerhet, forretningsmodeller, personvern og standardisering før vi kommer dit!
Så går jeg over til å beskrive de mest lovende teknologiene og standardene, før jeg viser en live demo med en en sonar, Arduino, Raspberry PI, node.red MQTT, en snakkende hodeskalle, sensorer og Minecraft!
Jeg kommer til å gå detaljert gjennom MQTT og Node.red - teknologier som blant annet brukes av IBM for å raskt kunne lage prototyper på Internet-of-things prosjekter for store bedrifter. Dette kan være relevant for deg, da de fleste konsulentselskaper og firmaer etterhvert vil komme borti tingenes internett.
Jeg kommer til å vise meldingsflyt, kildekode og hvordan du selv kan komme i gang. Og om du rekker det, kan du i likhet meg meg lage en liten animatronics-velkomst som skremmer barna på Halloween...
Similar to Continuous integration (20)
Of innovation and impatience - Future Decoded 2015
Of innovation and impatience - Future Decoded 2015
Designing the Priority, Performance ist User Experience
Designing the Priority, Performance ist User Experience
Chaos engineering - The art of breaking stuff in production on purpose
Chaos engineering - The art of breaking stuff in production on purpose
Faster Secure Software Development with Continuous Deployment - PH Days 2013
Faster Secure Software Development with Continuous Deployment - PH Days 2013
[Wroclaw #4] Fuzzing - underestimated method of finding hidden bugs
[Wroclaw #4] Fuzzing - underestimated method of finding hidden bugs
4Developers 2015: Under the dome (of failure driven pipeline) - Maciej Lasyk
4Developers 2015: Under the dome (of failure driven pipeline) - Maciej Lasyk
Fuzzing underestimated method of finding hidden bugs
Fuzzing underestimated method of finding hidden bugs
No more excuses left - let's build great things - Christian Heilmann - Codemo...
No more excuses left - let's build great things - Christian Heilmann - Codemo...
JavaZone 2014: En realitetsorientering om Tingenenes Internett, og hvordan du...
JavaZone 2014: En realitetsorientering om Tingenenes Internett, og hvordan du...
More from Jéferson Machado
druid.io
Druid.io presentation to show how druid.io works and how can he provide 100% of uptime through his Architecture.
Apache Spark Internals - Part 2
The idea of this presentation is to understand more about Apache Spark internals.
How it deals with resilience for each component, how Shard allocation works using RDD and how it abstract data partitioning and cluster distribution complexity.
Apache Spark
Apache Spark presentation showing how Spark works internally and how it deals with distributed data.
A comparison with Apache Hadoop is made in order to show the advantages that Apache Spark.
Node.js, is it the solution for every problem?
Presentation that try to explain how Node.js works, how can it deal with millions of concurrent users using just a single thread. Also there are some slides to talk about which problems it helps to solve.
Plano de carreira, isso funciona ? Me consegue uma bússola por favor. (Agile...
O documento discute práticas para o desenvolvimento de carreira de funcionários de forma mais efetiva, mencionando problemas comuns em abordagens tradicionais e propondo alternativas como acompanhamentos semanais, feedback 360, retrospectivas e métricas de retenção.
How to innovate ?
The document provides tips on how to innovate, noting that innovation is necessary for organizational survival and growth. It identifies common barriers to innovation like fear of failure and an unwillingness to take risks. The document recommends cultivating a culture that encourages risk-taking and accepts both success and failure. It also suggests techniques for generating new ideas like brainstorming, design thinking, and using Google's design sprint process to take ideas from conception to prototyping in just five days.
Management 3.0 (TDC 2015)
This document discusses different approaches to management and how organizations can evolve to focus more on people. It describes management 1.0 as hierarchical with top-down decision making, while management 2.0 introduced some improvements. Management 3.0 focuses on complexity and networks with an emphasis on people. Various views on leadership and motivation are presented, as well as how to develop skills, define values, create self-organizing teams, and use systems thinking to continuously improve and adapt the organization.
Management 3.0, como evoluir pessoas em conjunto com sua organização.
O documento discute a evolução da gestão de pessoas em organizações, da Gestão 1.0 hierárquica para a Gestão 2.0 de soluções pontuais e agora para a Gestão 3.0 focada nas pessoas e sistemas complexos. A Gestão 3.0 requer gerentes como jardineiros, times auto-organizados e valores compartilhados, desenvolvendo competências por meio do modelo Shu-Ha-Ri e crescendo estruturas de forma sustentável usando o modelo de Panarchy.
Business model generation
This document provides links to resources about business model canvases and the lean canvas model. It includes links to the Business Model Generation website which has information on the business model canvas template and a downloadable poster version. Another link discusses why the lean canvas model is useful. Additional links direct to the LeanStack website and various social media profiles of someone named Jefersonm that may provide further information on canvases and lean startup methodologies.
Lean & T.O.C
This document contains contact information for Jéferson Machado, including social network URLs and links to resources about agile coaching, lean production, theory of constraints, quality management, and lean manufacturing. It lists Jéferson's Twitter, Facebook, GitHub, and SlideShare profiles, as well as several websites containing information on lean principles and practices.
Kanban metrics
This document provides links to resources about creating cumulative flow diagrams with Google Spreadsheets, including a specific spreadsheet document and links to the author's profiles on SlideShare, Twitter, and GitHub. The spreadsheet allows users to easily make cumulative flow diagrams visualizing project progress over time directly in a Google Sheets file.
Python - basics
Python was created in 1980 by Guido Van Rossum. There are differences between Python versions 2.x and 3.x related to compatibility, understandability, maturity, and robustness. Some frameworks like Twisted and gevent have not yet migrated to Python 3.x, while others like NumPy, Django, Flask, CherryPy, Pyramid, PIL, cx_Freeze, and Py2exe have migrated. The document also includes code examples and information about a Python developer.
Apache Pig
Pig is an extensible platform for analyzing large datasets that allows both local and MapReduce execution. It features a simple language called Pig Latin for loading, filtering, transforming, and storing data. Pig Latin scripts can be debugged using commands like DUMP, DESCRIBE, EXPLAIN, and ILLUSTRATE and allows working with data through operations like FILTER, FOREACH, GROUP, UNION, and SPLIT.
Apache HBase
HDFS provides a distributed file system that integrates seamlessly with Hadoop, offering features like fault tolerance, load balancing, and easy addition or removal of nodes. It is well suited for problems involving hundreds of millions or billions of rows of data where the full functionality of an RDBMS is not required, as long as sufficient hardware is available. The history of HDFS includes its origins in Google's BigTable paper in 2006 and its evolution as a Hadoop sub-project in 2008 before becoming a top-level Apache project in 2010.
Scala
Scala is a general-purpose programming language that was created in 2003 by Martin Odersky and began life as a research project. It combines object-oriented and functional programming paradigms, with static typing and pattern matching, to enable the development of robust and scalable applications.
Management 3.0
Marse focuses on managing emergent and higher goals, not using targets or financial motivation. He believes that if you offer rewards, the goal becomes obtaining the reward rather than the goal itself. Marse also advocates making people's jobs dynamic to keep them engaged.
Theory of constraints
This document provides resources for learning about constraints, the five focusing steps, and using the theory of constraints with lean including links to websites explaining these topics and a video. It also includes contact information for Jéferson Machado including his social media profiles on Twitter, Facebook, GitHub, and SlideShare.
Padrino
The document introduces Sinatra, a Ruby web application framework that allows quick creation of web apps with minimal effort. It discusses Sinatra's routes, views, templates, filters, and testing capabilities. It also provides the presenter's social media links and invites questions from the audience.
Haskell scala exercises presentation
This document contains contact information and links to projects for Jéferson Machado, a software designer. It lists his Twitter, GitHub, Facebook, and SlideShare profiles and links to calculator and FizzBuzz programs he created in Haskell and Scala.
RabbitMQ
This document discusses RabbitMQ, an open source message broker. RabbitMQ uses queues to buffer messages and allow asynchronous message passing between producers and consumers. It supports multiple programming languages and common patterns like work queues, publish/subscribe, routing, and remote procedure calls. Exchanges in RabbitMQ support different routing strategies like direct, topic-based, and fanout messaging between queues and producers/consumers.
More from Jéferson Machado (20)
Plano de carreira, isso funciona ? Me consegue uma bússola por favor. (Agile...
Plano de carreira, isso funciona ? Me consegue uma bússola por favor. (Agile...
Management 3.0, como evoluir pessoas em conjunto com sua organização.
Management 3.0, como evoluir pessoas em conjunto com sua organização.
Recently uploaded
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Tomaz Bratanic
Graph ML and GenAI Expert - Neo4j
Taking AI to the Next Level in Manufacturing.pdf
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Northern Engraving | Nameplate Manufacturing Process - 2024
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
Mutation Testing for Task-Oriented Chatbots
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
Dandelion Hashtable: beyond billion requests per second on a commodity server
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Introduction of Cybersecurity with OSS at Code Europe 2024
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
"Choosing proper type of scaling", Olena Syrota
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Apps Break Data
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
5th LF Energy Power Grid Model Meet-up Slides
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
AppSec PNW: Android and iOS Application Security with MobSF
Mobile Security Framework - MobSF is a free and open source automated mobile application security testing environment designed to help security engineers, researchers, developers, and penetration testers to identify security vulnerabilities, malicious behaviours and privacy concerns in mobile applications using static and dynamic analysis. It supports all the popular mobile application binaries and source code formats built for Android and iOS devices. In addition to automated security assessment, it also offers an interactive testing environment to build and execute scenario based test/fuzz cases against the application.
This talk covers:
Using MobSF for static analysis of mobile applications.
Interactive dynamic security assessment of Android and iOS applications.
Solving Mobile app CTF challenges.
Reverse engineering and runtime analysis of Mobile malware.
How to shift left and integrate MobSF/mobsfscan SAST and DAST in your build pipeline.
The Microsoft 365 Migration Tutorial For Beginner.pptx
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/how-axelera-ai-uses-digital-compute-in-memory-to-deliver-fast-and-energy-efficient-computer-vision-a-presentation-from-axelera-ai/
Bram Verhoef, Head of Machine Learning at Axelera AI, presents the “How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-efficient Computer Vision” tutorial at the May 2024 Embedded Vision Summit.
As artificial intelligence inference transitions from cloud environments to edge locations, computer vision applications achieve heightened responsiveness, reliability and privacy. This migration, however, introduces the challenge of operating within the stringent confines of resource constraints typical at the edge, including small form factors, low energy budgets and diminished memory and computational capacities. Axelera AI addresses these challenges through an innovative approach of performing digital computations within memory itself. This technique facilitates the realization of high-performance, energy-efficient and cost-effective computer vision capabilities at the thin and thick edge, extending the frontier of what is achievable with current technologies.
In this presentation, Verhoef unveils his company’s pioneering chip technology and demonstrates its capacity to deliver exceptional frames-per-second performance across a range of standard computer vision networks typical of applications in security, surveillance and the industrial sector. This shows that advanced computer vision can be accessible and efficient, even at the very edge of our technological ecosystem.What is an RPA CoE? Session 1 – CoE Vision
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Skybuffer SAM4U tool for SAP license adoption
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Recently uploaded (20)
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
GraphRAG for LifeSciences Hands-On with the Clinical Knowledge Graph
Northern Engraving | Nameplate Manufacturing Process - 2024
Northern Engraving | Nameplate Manufacturing Process - 2024
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor Ivaniuk
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
AppSec PNW: Android and iOS Application Security with MobSF
AppSec PNW: Android and iOS Application Security with MobSF
The Microsoft 365 Migration Tutorial For Beginner.pptx
The Microsoft 365 Migration Tutorial For Beginner.pptx
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
Continuous integration
- 1. CONTINUOUS INTEGRATION Social network informa0on http://twitter.com/jefersonm https://github.com/jefersonm/ Jéferson Machado So#ware Design http://facebook.com/jefe.machado http://slideshare.net/jefersonm
- 2. BUILDING A FEATURE WITH CONTINUOUS INTEGRATION
- 3. PRACTICES OF CONTINUOUS INTEGRATION • MAINTAIN A SINGLE SOURCE REPOSITORY. • AUTOMATE THE BUILD • MAKE YOUR BUILD SELF-TESTING • EVERYONE COMMITS TO THE MAINLINE EVERY DAY • EVERY COMMIT SHOULD BUILD THE MAINLINE ON AN INTEGRATION MACHINE • KEEP THE BUILD FAST • TEST IN A CLONE OF THE PRODUCTION ENVIRONMENT • EVERYONE CAN SEE WHAT'S HAPPENING
- 4. MAINTAIN A SINGLE SOURCE REPOSITORY.
- 5. AUTOMATE THE BUILD RAKE
- 6. MAKE YOUR BUILD SELF-TESTING
- 7. EVERYONE COMMITS TO THE MAINLINE EVERY DAY COMMIT FREQUENTLY (HOURS) SPLIT YOUR WORK INTO TASKS
- 8. EVERY COMMIT SHOULD BUILD THE MAINLINE ON AN INTEGRATION MACHINE TWO OPTIONS: 1- MANUALLY 2- AUTOMATICALLY
- 9. KEEP THE BUILD FAST TWO STAGE BUILDS: 1- UNIT TESTS 2- INTEGRATION TESTS
- 10. TEST IN A CLONE OF THE PRODUCTION ENVIRONMENT TEST ENV PROD ENV - OPERATIONAL SYSTEM - OPERATIONAL SYSTEM - DATABASE SOFTWARE - DATABASE SOFTWARE - LIBRARIES - LIBRARIES - IP ADDRESS - IP ADDRESS - PORTS - PORTS
- 11. EVERYONE CAN SEE WHAT'S HAPPENING
- 12. BENEFITS OF CONTINUOUS INTEGRATION
- 13. If you break the build I’ll charge you!!! Thank you.. Bééé!! Social network informa0on http://twitter.com/jefersonm https://github.com/jefersonm/ Jéferson Machado So#ware Design http://facebook.com/jefe.machado http://slideshare.net/jefersonm