Testing cloud and kubernetes applications - ElasTestMicael Gallego
Kubernetes applications are complex distributed systems composed by several microservices. When some end to end test is failing in these kind of applications, root cause is difficult without good observability tools. In this presentation, several tools are presented to make easier root cause analysis of cloud and kubernetes applications. One of the most interesting ones is ElasTest, a platform that integrates several open source tools to provide observability to e2e testing of complex distributed systems.
Jenkins is an open source tool that automates the continuous integration process. It monitors source code repositories for changes, automatically builds the code, runs tests, and provides feedback to developers. Before CI tools like Jenkins, software delivery was slow and locating bugs after integration was difficult. With Jenkins, every code change triggers an automatic build and test, improving feedback and release frequency while reducing bug fixing time. Jenkins has over 1000 plugins and alternatives include Travis CI, Buildbot, Bamboo, and JetBrains TeamCity.
Software Delivery in 2016 - A Continuous Delivery ApproachGiovanni Toraldo
The speech "Software Delivery in 2016" was held by Giovanni Toraldo (Lead Developer at ClouDesire) on July 1st 2016 in Pisa, Italy.
Event: Apericoder
Organizer: Coders TUG
Advantages and disadvantages of a monorepoIanDavidson56
A monorepo is a single repository that contains all code for a company, team, or product rather than having separate repositories. Key advantages of a monorepo include consistency across language versions, dependencies, and code style which makes upgrades and refactors easier. However, a monorepo also has disadvantages such as a more complex build process, inability to version internal libraries, and difficulty searching and managing the large codebase. While a monorepo provides benefits like easy code reuse and setup, the tradeoff is less flexibility and potential slowdowns from the large size.
Continuous Delivery: 5 years later (Incontro DevOps 2018)Giovanni Toraldo
Continuous delivery is a software engineering approach where teams produce software in short cycles to ensure the software can be reliably released at any time. This allows for more incremental updates to applications in production. The document discusses the tools and processes used by Cloudesire to implement continuous delivery practices, including GitHub for issue tracking, CircleCI for continuous integration, Docker for packaging, Chef for configuration management, and various other tools for monitoring, logging, and metrics.
The New York Times: Sustainable Systems, Powered by PythonAll Things Open
The document discusses Python tools and techniques for building sustainable systems at the New York Times. It describes applications they build using a Python-based microservices framework called Photon for ingesting and managing photos. It then summarizes several Python packages they use for installation and running applications, ensuring code quality, adding features, providing resilient runtimes, and generating automated documentation.
Managing JavaScript projects in a MonoRepo
(Zacky Pickholz)
Managing a large front end project with multiple npm packages can be overwhelming sometimes. During this session we cover popular tools that help us maintain this project much more easily.
This document summarizes recent developments in JavaScript including:
- Angular 5 improvements like progressive web apps and code optimization.
- Machine learning capabilities in browsers using TensorFire and Google's Deeplearn.js.
- New features in Firefox 55 and 56 like screenshots and CSS Grid updates.
- The Bootstrap 4 Beta release overhauling components and dropping older browser support.
- Updates to Yarn, Atom IDE, WebKit, CoffeeScript, and React as well as experiments with WebAssembly and creating Word documents with React.
Testing cloud and kubernetes applications - ElasTestMicael Gallego
Kubernetes applications are complex distributed systems composed by several microservices. When some end to end test is failing in these kind of applications, root cause is difficult without good observability tools. In this presentation, several tools are presented to make easier root cause analysis of cloud and kubernetes applications. One of the most interesting ones is ElasTest, a platform that integrates several open source tools to provide observability to e2e testing of complex distributed systems.
Jenkins is an open source tool that automates the continuous integration process. It monitors source code repositories for changes, automatically builds the code, runs tests, and provides feedback to developers. Before CI tools like Jenkins, software delivery was slow and locating bugs after integration was difficult. With Jenkins, every code change triggers an automatic build and test, improving feedback and release frequency while reducing bug fixing time. Jenkins has over 1000 plugins and alternatives include Travis CI, Buildbot, Bamboo, and JetBrains TeamCity.
Software Delivery in 2016 - A Continuous Delivery ApproachGiovanni Toraldo
The speech "Software Delivery in 2016" was held by Giovanni Toraldo (Lead Developer at ClouDesire) on July 1st 2016 in Pisa, Italy.
Event: Apericoder
Organizer: Coders TUG
Advantages and disadvantages of a monorepoIanDavidson56
A monorepo is a single repository that contains all code for a company, team, or product rather than having separate repositories. Key advantages of a monorepo include consistency across language versions, dependencies, and code style which makes upgrades and refactors easier. However, a monorepo also has disadvantages such as a more complex build process, inability to version internal libraries, and difficulty searching and managing the large codebase. While a monorepo provides benefits like easy code reuse and setup, the tradeoff is less flexibility and potential slowdowns from the large size.
Continuous Delivery: 5 years later (Incontro DevOps 2018)Giovanni Toraldo
Continuous delivery is a software engineering approach where teams produce software in short cycles to ensure the software can be reliably released at any time. This allows for more incremental updates to applications in production. The document discusses the tools and processes used by Cloudesire to implement continuous delivery practices, including GitHub for issue tracking, CircleCI for continuous integration, Docker for packaging, Chef for configuration management, and various other tools for monitoring, logging, and metrics.
The New York Times: Sustainable Systems, Powered by PythonAll Things Open
The document discusses Python tools and techniques for building sustainable systems at the New York Times. It describes applications they build using a Python-based microservices framework called Photon for ingesting and managing photos. It then summarizes several Python packages they use for installation and running applications, ensuring code quality, adding features, providing resilient runtimes, and generating automated documentation.
Managing JavaScript projects in a MonoRepo
(Zacky Pickholz)
Managing a large front end project with multiple npm packages can be overwhelming sometimes. During this session we cover popular tools that help us maintain this project much more easily.
This document summarizes recent developments in JavaScript including:
- Angular 5 improvements like progressive web apps and code optimization.
- Machine learning capabilities in browsers using TensorFire and Google's Deeplearn.js.
- New features in Firefox 55 and 56 like screenshots and CSS Grid updates.
- The Bootstrap 4 Beta release overhauling components and dropping older browser support.
- Updates to Yarn, Atom IDE, WebKit, CoffeeScript, and React as well as experiments with WebAssembly and creating Word documents with React.
Slow, Flaky and Legacy Tests: FTFY - Our New Testing Strategy at Net-A-Porter...Sauce Labs
As part of a recent replatforming exercise, Net-A-Porter has worked hard not only to refresh their technology, but to create a great testing culture. As a result, they have come a long way from “throwing tests over the wall.” Testing concerns are now part of their NFRs and technical decisions. Developers are responsible for unit and functional tests, working alongside test specialists who are part of every delivery team for guidance.
In this SauceCon 2018 session, Adela Mosincat and James Collins will walk attendees through how Sauce Labs has helped in this process. She will review how the “test-runner” was born to facilitate the consistent and seamless running of their tests on Sauce Labs across teams. The test-runner is a Docker image, whose purpose is to handle the running of the tests both locally and in their CI pipeline. It parallelizes the tests as much as possible, executes intelligent waiting for VMs and retrying for flaky tests, supports test tagging and quarantining and handles reporting to both Sauce Labs and Jenkins.
In addition to the test-runner, Adela and Jim will review how Net-A-Porter improved their dev/test culture and CI pipeline, and share what they learned along the way.
Presented by: Lin Sun, IBM
Presented at All Things Open 2020
Abstract: Do you really need microservices? The Istio team have made an architecture decision to change the Istio control plane components from microservices to monolithic to simplify Istio. Come and hear why we did it and how it simplifies Istio operation experience, along with many other changes we made to simplify Istio.
Preventing Supply Chain Attacks on Open Source SoftwareAll Things Open
Supply chain attacks on open source software increased 650% in 2021. Software supply chain attacks occur when adversaries manipulate third-party code to compromise downstream applications. Organizations must map dependencies, monitor for vulnerabilities, and quickly patch issues. A Software Bill of Materials (SBOM) provides visibility into components. OWASP Dependency Track helps generate SBOMs and identify vulnerabilities and license risks in dependencies. Implementing standards like the Supply Levels for Software Artifacts (SLSA) can help secure software supply chains and prevent tampering of artifacts.
This document discusses software-defined networking (SDN), network functions virtualization (NFV), network virtualization (NV), and open networking. It provides definitions of these concepts and compares the hardware-defined data center and software-defined data center approaches. Diagrams show the network overlay and underlay in NV. Open networking organizations and initiatives like OpenFlow, Open Network Install Environment (ONIE), Open Network Linux (ONL), OpenNSL, and OPNFV are also mentioned. Lastly, the benefits of different approaches are noted.
1) DevOps in real time discusses challenges of maintaining 24/7 operations for multiple online projects and teams spread across different geographies.
2) The plan is to use tools like Chef, continuous integration, monitoring, backups, and team communication to improve processes around deployment cycles, server configuration, and working with many teams.
3) Chef is highlighted as a tool to help with automatic server configuration, continuous delivery, simplifying testing, controlling monitoring and backups. Templates, autoscaling, and single naming rules are also discussed to help manage infrastructure.
Talk by David Jorm on the state of Security in Java frameworks, and more specifically OpenDaylight. He also talks about his vision for where the platform should get to for delivering on the SDN promise.
The document provides an overview of Git and GitHub. It discusses version control systems and the differences between centralized (CVCS) and distributed (DVCS) version control systems. Git is introduced as a DVCS that allows for complex merges and fast collaboration. The document then covers Git concepts, commands, workflows and how to use GitHub for hosting Git repositories and collaborating on projects.
This document provides an overview of QtWebEngine and its relationship to QtWebKit. It notes that QtWebKit was removed in Qt 5.6 and replaced by QtWebEngine, which is based on Chromium and uses the Blink rendering engine. QtWebEngine has a multi-process architecture compared to the single process of QtWebKit. It also introduces QtWebChannel for communication between Qt and JavaScript applications.
CodiLime Tech Talk - Dawid Trzebiatowski i Wojciech Urbański: Opening the Flo...CodiLime
Tech Talk CodiLime 22.04.2020.
YT: https://youtu.be/66S5LFM12JQ
In this talk, we’re going to introduce the general public to our approach to simplified Spinnaker management using Floodgate, our open-source tool as well as Spinnaker-provided components, such as Sponnet.
This document summarizes the development process used by XWiki. It describes the main projects, open source license, development environment including source control and build management. It also outlines the process for adding new features including roadmapping, implementation, code reviews, releases, testing, documentation and maintenance. The development follows an iterative process with yearly major releases and bi-monthly minor releases to gather early feedback.
The document discusses options for testing software including manual testing with Vagrant and Robot Framework as well as automated testing. It recommends using OpenShift for automated testing as it provides a reliable solution with Kubernetes that is scalable and controllable while Docker provides speed and high density. Open vSwitch enables network connectivity in OpenShift. Workflow and reference details are also included.
OSDC 2017 - Dr. Udo Seidel - VMwares (open source) Way of ContainerNETWAYS
This document discusses VMware's approach to containers using open source software. It begins with an introduction to containers and VMware's products in this space. The main part analyzes VMware's "Photon Platform", which includes the Photon OS, Photon Controller, Lightwave, and Harbor open source projects. It describes the software architecture and licensing models. In conclusion, the author notes the promising early steps but also missing vision, focus on individual projects rather than a cohesive platform, and lack of enterprise readiness compared to competitors like Docker and Kubernetes.
The document provides tips for developing automated tests for the Boot to Gecko (B2G) mobile operating system. It outlines components of B2G like the emulator and build environment. It demonstrates starting the emulator, sending commands, and debugging. An existing WebAPI test is code walked through and run in the emulator. Participants are instructed to develop a new automated WebAPI test for B2G using Marionette that runs in the emulator. Contact information is provided for those interested in contributing.
This document provides an introduction to the Gradle build automation tool. It discusses Gradle's advantages over other build tools like Ant and Maven, including its use of Groovy build scripts, convention over configuration approach, and support for multi-project builds through a directed acyclic graph model. Key features of Gradle highlighted include its declarative build style, dependency management capabilities, build daemon for improved performance, and available plugins.
The document discusses automated testing inside Openshift including the contour of automated testing, dynamic configurations of Openshift, and integration with TestLink. It outlines pros and cons of automated testing using lightweight containers across a variety of operating systems. It describes how to dynamically configure tests by variables like project, branch, product name and version, and OS. It also covers how to create, execute, verify and delete configurations as well as generate reports and artifacts from test runs. Finally, it discusses integrating test results with TestLink for reporting.
Рассмотрим что же изменилось с технической части новой версии ReportPortal. Обсудим текущие проблемы, пути их решения и планы по развитию приложения на ближайшее будущее.
CodiLime Tech Talk - Wojciech Urbański: Cloud NativeCodiLime
The document discusses the 12 Factor App methodology for building cloud-native applications. It provides three stories that show how the 12 factors can be applied: 1) Containerizing a legacy application to make it cloud-native, 2) Using serverless computing and how the 12 factors still apply, and 3) Open sourcing a SaaS product using the GitLab model. In each story, the 12 factors are listed and it's explained how they relate to the cloud-native approaches and best practices discussed. The document concludes that the 12 factors provide good guidance but should not limit developers' creativity in building cloud applications.
ETICS supporting compliance and interoperability, Gabriele Giammatteo, Engine...OW2
ETICS is a service-oriented system which supports its users in building, testing and in verifying the quality of the software produced. With ETICS it is possible to define, execute and analyse a large range of software testing cases, from static code analysis (e.g. documentation coverage, PMD metrics) to unit testing, to compliance testing, to deployment and functional testing in a multi-node environment created specifically for the test execution. ETICS build, testing and quality verification tools are offered as a service to open source projects within the OCEAN project. In this context ETICS mainly simplifies and supports testing activities improving the quality of the software being produced, verifying its compliance to standards and its interoperability features. This presentation can be seen as a continuation of ETICS presentation given last year at OW2 conference 2012. It aims at showing results from the use of ETICS as one of OCEAN services and at illustrating the approach developed to support software compliance and interoperability for the verification of the compatibility to OCCI and CDMI standards.
The document discusses hardware accelerators and startups. It notes that hardware startups face long development cycles traditionally but that hardware accelerators can help optimize the process. It then discusses a Taiwanese accelerator called South Star Xelerator that helps projects reach product market fit and provides post-accelerator support connecting startups to corporations and investors. The accelerator generates revenue by helping corporations with open innovation projects.
Digital Dealer is a branch of Argus Group that analyzes new automotive business models and organizes meetings on digital automotive innovations around the world. It is managed by Eric Saint-Frison, a former Ford CEO, and works with a network of automotive leaders. Digital Dealer wishes to meet with Beepi to learn about their original used car sales idea, share ideas that can help both companies, and potentially feature Beepi in Argus Group publications to spread their brand name. They request contact with Beepi to arrange a meeting during their business trip to the US in late March 2016.
Slow, Flaky and Legacy Tests: FTFY - Our New Testing Strategy at Net-A-Porter...Sauce Labs
As part of a recent replatforming exercise, Net-A-Porter has worked hard not only to refresh their technology, but to create a great testing culture. As a result, they have come a long way from “throwing tests over the wall.” Testing concerns are now part of their NFRs and technical decisions. Developers are responsible for unit and functional tests, working alongside test specialists who are part of every delivery team for guidance.
In this SauceCon 2018 session, Adela Mosincat and James Collins will walk attendees through how Sauce Labs has helped in this process. She will review how the “test-runner” was born to facilitate the consistent and seamless running of their tests on Sauce Labs across teams. The test-runner is a Docker image, whose purpose is to handle the running of the tests both locally and in their CI pipeline. It parallelizes the tests as much as possible, executes intelligent waiting for VMs and retrying for flaky tests, supports test tagging and quarantining and handles reporting to both Sauce Labs and Jenkins.
In addition to the test-runner, Adela and Jim will review how Net-A-Porter improved their dev/test culture and CI pipeline, and share what they learned along the way.
Presented by: Lin Sun, IBM
Presented at All Things Open 2020
Abstract: Do you really need microservices? The Istio team have made an architecture decision to change the Istio control plane components from microservices to monolithic to simplify Istio. Come and hear why we did it and how it simplifies Istio operation experience, along with many other changes we made to simplify Istio.
Preventing Supply Chain Attacks on Open Source SoftwareAll Things Open
Supply chain attacks on open source software increased 650% in 2021. Software supply chain attacks occur when adversaries manipulate third-party code to compromise downstream applications. Organizations must map dependencies, monitor for vulnerabilities, and quickly patch issues. A Software Bill of Materials (SBOM) provides visibility into components. OWASP Dependency Track helps generate SBOMs and identify vulnerabilities and license risks in dependencies. Implementing standards like the Supply Levels for Software Artifacts (SLSA) can help secure software supply chains and prevent tampering of artifacts.
This document discusses software-defined networking (SDN), network functions virtualization (NFV), network virtualization (NV), and open networking. It provides definitions of these concepts and compares the hardware-defined data center and software-defined data center approaches. Diagrams show the network overlay and underlay in NV. Open networking organizations and initiatives like OpenFlow, Open Network Install Environment (ONIE), Open Network Linux (ONL), OpenNSL, and OPNFV are also mentioned. Lastly, the benefits of different approaches are noted.
1) DevOps in real time discusses challenges of maintaining 24/7 operations for multiple online projects and teams spread across different geographies.
2) The plan is to use tools like Chef, continuous integration, monitoring, backups, and team communication to improve processes around deployment cycles, server configuration, and working with many teams.
3) Chef is highlighted as a tool to help with automatic server configuration, continuous delivery, simplifying testing, controlling monitoring and backups. Templates, autoscaling, and single naming rules are also discussed to help manage infrastructure.
Talk by David Jorm on the state of Security in Java frameworks, and more specifically OpenDaylight. He also talks about his vision for where the platform should get to for delivering on the SDN promise.
The document provides an overview of Git and GitHub. It discusses version control systems and the differences between centralized (CVCS) and distributed (DVCS) version control systems. Git is introduced as a DVCS that allows for complex merges and fast collaboration. The document then covers Git concepts, commands, workflows and how to use GitHub for hosting Git repositories and collaborating on projects.
This document provides an overview of QtWebEngine and its relationship to QtWebKit. It notes that QtWebKit was removed in Qt 5.6 and replaced by QtWebEngine, which is based on Chromium and uses the Blink rendering engine. QtWebEngine has a multi-process architecture compared to the single process of QtWebKit. It also introduces QtWebChannel for communication between Qt and JavaScript applications.
CodiLime Tech Talk - Dawid Trzebiatowski i Wojciech Urbański: Opening the Flo...CodiLime
Tech Talk CodiLime 22.04.2020.
YT: https://youtu.be/66S5LFM12JQ
In this talk, we’re going to introduce the general public to our approach to simplified Spinnaker management using Floodgate, our open-source tool as well as Spinnaker-provided components, such as Sponnet.
This document summarizes the development process used by XWiki. It describes the main projects, open source license, development environment including source control and build management. It also outlines the process for adding new features including roadmapping, implementation, code reviews, releases, testing, documentation and maintenance. The development follows an iterative process with yearly major releases and bi-monthly minor releases to gather early feedback.
The document discusses options for testing software including manual testing with Vagrant and Robot Framework as well as automated testing. It recommends using OpenShift for automated testing as it provides a reliable solution with Kubernetes that is scalable and controllable while Docker provides speed and high density. Open vSwitch enables network connectivity in OpenShift. Workflow and reference details are also included.
OSDC 2017 - Dr. Udo Seidel - VMwares (open source) Way of ContainerNETWAYS
This document discusses VMware's approach to containers using open source software. It begins with an introduction to containers and VMware's products in this space. The main part analyzes VMware's "Photon Platform", which includes the Photon OS, Photon Controller, Lightwave, and Harbor open source projects. It describes the software architecture and licensing models. In conclusion, the author notes the promising early steps but also missing vision, focus on individual projects rather than a cohesive platform, and lack of enterprise readiness compared to competitors like Docker and Kubernetes.
The document provides tips for developing automated tests for the Boot to Gecko (B2G) mobile operating system. It outlines components of B2G like the emulator and build environment. It demonstrates starting the emulator, sending commands, and debugging. An existing WebAPI test is code walked through and run in the emulator. Participants are instructed to develop a new automated WebAPI test for B2G using Marionette that runs in the emulator. Contact information is provided for those interested in contributing.
This document provides an introduction to the Gradle build automation tool. It discusses Gradle's advantages over other build tools like Ant and Maven, including its use of Groovy build scripts, convention over configuration approach, and support for multi-project builds through a directed acyclic graph model. Key features of Gradle highlighted include its declarative build style, dependency management capabilities, build daemon for improved performance, and available plugins.
The document discusses automated testing inside Openshift including the contour of automated testing, dynamic configurations of Openshift, and integration with TestLink. It outlines pros and cons of automated testing using lightweight containers across a variety of operating systems. It describes how to dynamically configure tests by variables like project, branch, product name and version, and OS. It also covers how to create, execute, verify and delete configurations as well as generate reports and artifacts from test runs. Finally, it discusses integrating test results with TestLink for reporting.
Рассмотрим что же изменилось с технической части новой версии ReportPortal. Обсудим текущие проблемы, пути их решения и планы по развитию приложения на ближайшее будущее.
CodiLime Tech Talk - Wojciech Urbański: Cloud NativeCodiLime
The document discusses the 12 Factor App methodology for building cloud-native applications. It provides three stories that show how the 12 factors can be applied: 1) Containerizing a legacy application to make it cloud-native, 2) Using serverless computing and how the 12 factors still apply, and 3) Open sourcing a SaaS product using the GitLab model. In each story, the 12 factors are listed and it's explained how they relate to the cloud-native approaches and best practices discussed. The document concludes that the 12 factors provide good guidance but should not limit developers' creativity in building cloud applications.
ETICS supporting compliance and interoperability, Gabriele Giammatteo, Engine...OW2
ETICS is a service-oriented system which supports its users in building, testing and in verifying the quality of the software produced. With ETICS it is possible to define, execute and analyse a large range of software testing cases, from static code analysis (e.g. documentation coverage, PMD metrics) to unit testing, to compliance testing, to deployment and functional testing in a multi-node environment created specifically for the test execution. ETICS build, testing and quality verification tools are offered as a service to open source projects within the OCEAN project. In this context ETICS mainly simplifies and supports testing activities improving the quality of the software being produced, verifying its compliance to standards and its interoperability features. This presentation can be seen as a continuation of ETICS presentation given last year at OW2 conference 2012. It aims at showing results from the use of ETICS as one of OCEAN services and at illustrating the approach developed to support software compliance and interoperability for the verification of the compatibility to OCCI and CDMI standards.
The document discusses hardware accelerators and startups. It notes that hardware startups face long development cycles traditionally but that hardware accelerators can help optimize the process. It then discusses a Taiwanese accelerator called South Star Xelerator that helps projects reach product market fit and provides post-accelerator support connecting startups to corporations and investors. The accelerator generates revenue by helping corporations with open innovation projects.
Digital Dealer is a branch of Argus Group that analyzes new automotive business models and organizes meetings on digital automotive innovations around the world. It is managed by Eric Saint-Frison, a former Ford CEO, and works with a network of automotive leaders. Digital Dealer wishes to meet with Beepi to learn about their original used car sales idea, share ideas that can help both companies, and potentially feature Beepi in Argus Group publications to spread their brand name. They request contact with Beepi to arrange a meeting during their business trip to the US in late March 2016.
This document summarizes research on the effects of temperature on longevity in C. elegans. Microarray analysis identified lysosomal protease genes that are differentially expressed at 15°C vs 25°C. Follow up experiments showed that lysosome structure and number are altered at elevated temperatures. RNAi of temperature-regulated proteases caused progressive paralysis specifically at 15°C, indicating a role in neuronal health. Further experiments traced this paralysis to dysfunction of motor neurons rather than muscles. The research suggests that proteostasis, particularly lysosomal function, is important for neuronal health under cool temperatures and influences longevity.
This document summarizes a workshop on building a culture of trust. It discusses how trust impacts speed and costs in organizations. It contrasts organizations where trust is low, with information hoarding and blame, to those with high trust, where people are loyal, accountable, and authentic. The workshop addresses changing behaviors to increase trust through integrity, competence, and character. It presents Covey's model of the four cores of credibility and five waves of trust building in organizations. Attendees participate in exercises on self-trust, managing trust accounts, and the 13 behaviors of high-trust organizations.
Today, nearly 43% of the world is connected to the internet1, enabling us to talk, share photos, and conduct business halfway across the globe. As a result, we have seen more technological advancements in the past 10 years than we’ve witnessed in the past 10,000 years. And in the next five years, we’ll see even more advancements.
In this overview provided by BI Intelligence, Business Insider’s premium subscription research service, we identify the key trend in each of our top vertical areas including Mobile, E-Commerce, Digital Media, Digital Financial Services, and the Internet of Things.
O documento discute como as joaninhas trazem sorte por se alimentarem de pragas em plantações e como a sorte é na verdade resultado de oportunidade, competência e bons resultados. Também fala sobre como entender mudanças ambientais e tendências é essencial para o crescimento de empresas.
This document discusses the benefits and challenges of responsive web design, which uses fluid grids and media queries to automatically adjust webpages to display well on different screen sizes. Responsive design improves the user experience across devices, helps websites reach wider audiences, and is more future-proof and search engine optimized compared to separate mobile sites. While retrofitting existing sites can be difficult, responsive design is supported by modern browsers and content management systems.
Poverty is a global issue that affects over one-fifth of the world's population. Poverty means lacking the basic needs for survival, such as food, shelter, water, and clothing. It is more than just the lack of money - in developing countries, poverty also means not having access to employment, healthcare, education, and other resources needed to meet basic human needs. Money alone is not the solution to poverty; sustainable development projects and access to education and job opportunities are also needed to help lift people out of poverty.
Lean Manufacturing Is Not Like Software DevelopmentDarren Duarte
Presented at LAST (Lean Agile Systems Thinking) Conference Melbourne 2016.
“You don’t add value, the Operators are the only ones who add value,” was a statement said to me as an Engineer while launching a commercial airplane into production. We often compare software development to Lean manufacturing. Lean is about maximising value, but what about us who don’t code?
This presentation touches on the perception change that I went through, exploring non-value added work and how this influences work in software development today, from cloud to mobile. This topic aimed at those in digital who don’t code, and that software development more than just coding.
Kent Nichols, "Downshifting Your Life to Rev Up Your Creativity"WebVisions
Kent Nichols left his six-figure job in Los Angeles to move with his family to Bend, Oregon in search of a better quality of life with less stress and more time. While the pay cut was significant, the cost of living is much lower in Bend and they no longer spend hours commuting each day. Nichols works remotely on creative projects and takes occasional gigs in LA while enjoying outdoor activities and a creative community in Bend. The lifestyle change has benefited his health, relationships and mental well-being despite some challenges in being accepted by locals and missing live city amenities.
At a recent in-house CLE event, John Sganga, Partner and the firm's Litigation Practice Group Chair, presented an intellectual property year in review discussing important cases throughout 2015.
Karim Hamir has extensive education and professional experience in law, business, finance, and teaching. He holds degrees including a JD from the University of Ottawa, an MBA from the University of Phoenix, and a BA from York University. Currently he works as a Commercial Account Manager at RBC Royal Bank and has received numerous awards for his performance. He has also taught law and business courses as a faculty member at Meritus University.
This handout is an accompaniment to my keynote presentation on my new book "Monster Loyalty: How Lady Gaga Turns Followers into Fanatics." More on the book here: http://jackiehuba.com/books/monster-loyalty/
San Diego Partner Boris Zelkind presented on the Defend Trade Secrets Act (DTSA) to the San Diego Intellectual Property Law Association.
These slides are intended to convey information and should not be regarded as legal advice. No attorney-client relationship is formed through the viewing of these slides. Should you have questions regarding the topics covered in these slides or require legal advice regarding a specific matter, please contact the presenter or another attorney.
Lessons from Contributing to WebKit and BlinkBruno Abinader
Being one of the most successful open source projects to date, WebKit development process consists of a series of protocols and strict policies in order to obtain committer and reviewer status. Blink follows a similar approach with committers and scoped code owners, in a similar fashion as Linux Kernel does with its subsystem maintainers. Their open source success is due to not only solid support from major technology companies, but also to the high quality and automated testing performed on patches before submission. In this presentation, Bruno explains how the development process of both WebKit and Blink projects are - from submitting well-tested patches with strict policies to check, get review from community, and commit upstream via commit-queue system (including early warning system bots). This is a very practical talk with live demonstrations of patch submissions on both projects.
Learn about how the core NuGet team the NuGet Client project. The project has challenges related to:
- Open Source
- Hard Deadlines
- Very Large Backlog
- Many Conflicting Requirements
- Git
We'll talk about our strategies for:
- Issue tracking - Branching
- Continuous integration
- Testing
- Release sign-off
Webinar: From Development to Production with Docker and MongoDBMongoDB
In this talk we review what Docker is and why it's important to Developers, Admins and DevOps.
We also cover the following topics:
- Using Docker to Orchestrate a multi container application (Flask + MongoDB)
- Injecting HAProxy and other production requirements as we deploy to production
- Scaling the Web and MongoDB cluster to grow to meet demand
This presentation includes an interactive demo showcasing the core Docker components (Machine, Engine, Swarm and Compose) as well as some of Docker's new components (libnetowrk, runC) from the experimental branch along with MongoDB. We hope you will see how much simpler Docker can make building and deploying multi-node applications.
<hr>
<b>What's next?</b>
See how you can push MongoDB performance to meed the needs of your mission-critical app with our best practices for MongoDB operations.
<a>Read the guide</a>
This document provides an overview of Ant and Maven build tools. It discusses what Ant and Maven are, their key features and differences. Ant is a build tool that uses XML files and custom tasks to automate software build processes. Maven is a build tool that standardizes project structures and dependencies and handles builds through a defined lifecycle of phases. The document compares their dependency management, configuration requirements and other technical differences.
Creating An App for 650 million customers v.2.pdfDmitry Osipa
This document summarizes AnchorFree's approach to developing a unified architecture and codebase for their multiple mobile apps. Some key points:
- AnchorFree has 50M monthly active users across 6+ cross-platform apps and was experiencing issues like dependency problems and duplicated code from using separate code repositories for each app.
- They implemented a monorepo to allow for better code reuse and refactoring. This helped improve consistency, reduce bugs, and speed up release cycles.
- They also adopted a unified VIPER architectural approach to standardize development and improve testability. This provided benefits like isolated modules, easier team scaling, and enabling A/B testing across apps.
- While there were initial
This document provides an introduction to the Git distributed revision control system. It discusses that Git is an open source DVCS that was created by Linus Torvalds in 2005 to manage kernel development. It highlights key Git features like distributed development, branching, fast performance, and tooling. It also provides overviews of Git concepts like the staging area, diverging and merging branches, and rebasing. The document recommends software for using Git and points to further reading materials.
Achieving Full Stack DevOps at Colonial Life DevOps.com
In an ever more competitive marketplace, organizations have turned to Agile and DevOps practices to deliver software innovations to market more quickly and with high quality. Across industries, companies are making heavy investments in tools and process improvements around automated build, test, continuous integration and delivery, and release automation and orchestration. However, despite these investments, many organizations are still struggling to bring the necessary speed and quality to their software delivery. In many cases, this is because Agile and DevOps improvements have not been applied to the entire software stack and are often limited to application code delivery.
This webinar will explore the transformation that Colonial Life made in bringing DevOps to the entire software stack. Specifically, beyond automating and accelerating the validation and delivery of application code, this webinar will focus on the critical role that data and the database play in modern software delivery and the tools and processes that can bring the same automation to database code.
After this webinar, you will understand:
* What holds organizations back despite an Agile application development process
* The benefits of automating the validation and deployment of database changes
* A template for bringing DevOps to the entire software stack
Topics of this presentation:
- Basics and best practices of developing single-page applications (SPA) and Web API Services on Microsoft .NET -
- Core with Docker and Linux.
- PowerShell Core automated builds.
- Markdown/PDF documentation.
- Documentation of public interfaces with Swagger/OAS/YAML.
- Automated testing of SPA on Protractor and testing the Web API on Postman/Newman.
This presentation by Sergii Fradkov (Consultant, Engineering), Andrii Zarharov (Lead Software Engineer, Consultant), Igor Magdich (Lead Test Engineer, Consultant) was delivered at GlobalLogic Kharkiv .NET TechTalk #1 on May 24, 2019.
Использование AzureDevOps при разработке микросервисных приложенийVitebsk Miniq
Презентация подготовлена по материалам выступления Игоря Сычёва на витебском MiniQ#17, который был проведен 25 июля 2019:
https://vk.com/miniq17;
https://communities.by/events/miniq-vitebsk-17.
Про доклад:
Мы реализуем CI/CD на базе Azure DevOps для нашего приложения в МикроСервисном стиле, которое хостим на Azure Kubernetes Services на протяжении более чем 6 месяцев. Мы хотим поделиться нашими успехами и ошибками в CI/CD с разработчиками и DevOps инженерами. Мы продемонстрируем наши подходы и реализации к Build/Release, созданию сред тестирования с использованием ARM шаблонов, согласования установки приложения на рабочие среды и эволюцию этих процессов со временем.
Continuous Integration with Cloud Foundry Concourse and Docker on OpenPOWERIndrajit Poddar
This document discusses continuous integration (CI) for open source software on OpenPOWER systems. It provides background on CI, OpenPOWER systems, and the Cloud Foundry platform. It then describes using the Concourse CI tool to continuously build a Concourse project from a GitHub repository. Key steps involve deploying OpenStack, setting up a Docker registry, installing BOSH and Concourse, defining a Concourse pipeline, and updating the pipeline to demonstrate the CI process in action. The document emphasizes the importance of CI for open source projects and how it benefits development on OpenPOWER systems.
FASTEN presentation at OSS2021, by Michele Scarlato, Endocode, May 12, 2021, ...Fasten Project
The FASTEN project wants to support DevOps teams and help developers tracking, managing and mastering dependencies. FASTEN’s goal is to develop a toolchain that is provisioning and collecting project information, security alerts, and repositories from well-known and widely used services. It merges this information into a data stream, performs analysis, stores it, and, consequently, builds a call-graph for each analyzed project. The gathered information is made available through a REST API and Web UI and performs continuous integration to provide developers with updated and sanitized versions of their dependencies. One part of this toolchain will be an Open Source license analysis. This analysis should perform a verification and compatibility check on licenses used in Open Source projects and facilitate development from a user perspective as well as create industry-relevant information on license infringements. This functionality shall be presented in this talk.
FASTEN has received funding from the European Union's Horizon 2020 research and innovation programme. It is carried out by a Consortium composed of AUEB, TUDelft, University of Milan-Bicocca, Endocode, OW2, SIG, and XWIKI.
The document discusses static analysis tools for finding bugs in source code. It summarizes the Coverity Scan service, which allows open source projects to have their code scanned for defects free of charge. The document outlines how to integrate Coverity Scan into a project's workflow, including using the cov-build wrapper to package code for analysis and submitting builds through services like Travis CI. It also provides tips for fine-tuning scans and examples of how the Linux and EFL projects use Coverity Scan in their development.
Microservices Architecture and Containers.imjacobclark
This document discusses microservices architecture and how containers can help solve problems with monolithic architectures. It describes how microservices break applications into independent, scalable services that communicate over standard protocols. Containers provide standardized, isolated environments for microservices. Using containers for microservices allows for easier deployment and management of distributed applications across infrastructure.
Ant and Maven are both build tools for Java projects. Ant uses XML files and requires defining tasks and their dependencies manually. Maven uses a standard convention that includes a common project structure and lifecycle phases like compile and test. It also handles dependency management automatically. While Maven has a learning curve, it simplifies the build process and makes projects easier to work with for new developers.
This document discusses Angular (2), including its history, architecture, and use at Meshcloud. It notes that Angular has undergone significant changes through beta releases. Key aspects highlighted include its simplified component-based structure, TypeScript integration, and use of Observables and services. Meshcloud's single page application was built with Angular CLI and uses lazy loading, AOT compilation, and HATEOAS for its REST APIs. Challenges discussed include debugging, performance analysis, and CORS configuration complexities.
The merge window is a period of time directly after a software release when many patches are merged. This allows patches a long time to be scrutinized and tested before the next release. During the merge window, which typically lasts two weeks for the Linux kernel, maintainers focus on quickly reviewing and merging new patches, while testing of the new patches occurs in the following release candidates period. Aligning development work with merge windows helps ensure patches are reviewed and integrated efficiently.
Lana Kalashnyk presented on transitioning to Java microservices on Docker. Key points included:
- Microservices involve breaking applications into small, independent services that communicate via APIs. Docker containers help deploy and manage microservices.
- The presentation demonstrated a Java microservice that polls a Bitcoin node for block height updates. It was packaged into a Docker container using Wildfly Swarm and exposed via REST APIs.
- A React web page displayed the data from the microservice. This illustrated how microservices and containers could replace outdated .NET web services.
- Benefits of microservices include independent deployability, fault isolation, and infrastructure automation using containers. Challenges include managing transactions and data
Platform - Depends on the size of the project and the type of its development, developers, and kind of platform.
Both the platforms Golang and Node.js were developed for different use & distinct purposes.
visit: https://www.forcebolt.com/
Using a revision control system that tracks changes in source code with ways to manage your code in separate branches and tag revisions as releases is a bare minimum for developers.
This presentation highlights the importance of using a version control system Subversion.
Similar to Dealing with large code bases. cd ams meetup (20)
Takashi Kobayashi and Hironori Washizaki, "SWEBOK Guide and Future of SE Education," First International Symposium on the Future of Software Engineering (FUSE), June 3-6, 2024, Okinawa, Japan
Introducing Crescat - Event Management Software for Venues, Festivals and Eve...Crescat
Crescat is industry-trusted event management software, built by event professionals for event professionals. Founded in 2017, we have three key products tailored for the live event industry.
Crescat Event for concert promoters and event agencies. Crescat Venue for music venues, conference centers, wedding venues, concert halls and more. And Crescat Festival for festivals, conferences and complex events.
With a wide range of popular features such as event scheduling, shift management, volunteer and crew coordination, artist booking and much more, Crescat is designed for customisation and ease-of-use.
Over 125,000 events have been planned in Crescat and with hundreds of customers of all shapes and sizes, from boutique event agencies through to international concert promoters, Crescat is rigged for success. What's more, we highly value feedback from our users and we are constantly improving our software with updates, new features and improvements.
If you plan events, run a venue or produce festivals and you're looking for ways to make your life easier, then we have a solution for you. Try our software for free or schedule a no-obligation demo with one of our product specialists today at crescat.io
Atelier - Innover avec l’IA Générative et les graphes de connaissancesNeo4j
Atelier - Innover avec l’IA Générative et les graphes de connaissances
Allez au-delà du battage médiatique autour de l’IA et découvrez des techniques pratiques pour utiliser l’IA de manière responsable à travers les données de votre organisation. Explorez comment utiliser les graphes de connaissances pour augmenter la précision, la transparence et la capacité d’explication dans les systèmes d’IA générative. Vous partirez avec une expérience pratique combinant les relations entre les données et les LLM pour apporter du contexte spécifique à votre domaine et améliorer votre raisonnement.
Amenez votre ordinateur portable et nous vous guiderons sur la mise en place de votre propre pile d’IA générative, en vous fournissant des exemples pratiques et codés pour démarrer en quelques minutes.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
What is Augmented Reality Image Trackingpavan998932
Augmented Reality (AR) Image Tracking is a technology that enables AR applications to recognize and track images in the real world, overlaying digital content onto them. This enhances the user's interaction with their environment by providing additional information and interactive elements directly tied to physical images.
Revolutionizing Visual Effects Mastering AI Face Swaps.pdfUndress Baby
The quest for the best AI face swap solution is marked by an amalgamation of technological prowess and artistic finesse, where cutting-edge algorithms seamlessly replace faces in images or videos with striking realism. Leveraging advanced deep learning techniques, the best AI face swap tools meticulously analyze facial features, lighting conditions, and expressions to execute flawless transformations, ensuring natural-looking results that blur the line between reality and illusion, captivating users with their ingenuity and sophistication.
Web:- https://undressbaby.com/
Graspan: A Big Data System for Big Code AnalysisAftab Hussain
We built a disk-based parallel graph system, Graspan, that uses a novel edge-pair centric computation model to compute dynamic transitive closures on very large program graphs.
We implement context-sensitive pointer/alias and dataflow analyses on Graspan. An evaluation of these analyses on large codebases such as Linux shows that their Graspan implementations scale to millions of lines of code and are much simpler than their original implementations.
These analyses were used to augment the existing checkers; these augmented checkers found 132 new NULL pointer bugs and 1308 unnecessary NULL tests in Linux 4.4.0-rc5, PostgreSQL 8.3.9, and Apache httpd 2.2.18.
- Accepted in ASPLOS ‘17, Xi’an, China.
- Featured in the tutorial, Systemized Program Analyses: A Big Data Perspective on Static Analysis Scalability, ASPLOS ‘17.
- Invited for presentation at SoCal PLS ‘16.
- Invited for poster presentation at PLDI SRC ‘16.
Neo4j - Product Vision and Knowledge Graphs - GraphSummit ParisNeo4j
Dr. Jesús Barrasa, Head of Solutions Architecture for EMEA, Neo4j
Découvrez les dernières innovations de Neo4j, et notamment les dernières intégrations cloud et les améliorations produits qui font de Neo4j un choix essentiel pour les développeurs qui créent des applications avec des données interconnectées et de l’IA générative.
Utilocate offers a comprehensive solution for locate ticket management by automating and streamlining the entire process. By integrating with Geospatial Information Systems (GIS), it provides accurate mapping and visualization of utility locations, enhancing decision-making and reducing the risk of errors. The system's advanced data analytics tools help identify trends, predict potential issues, and optimize resource allocation, making the locate ticket management process smarter and more efficient. Additionally, automated ticket management ensures consistency and reduces human error, while real-time notifications keep all relevant personnel informed and ready to respond promptly.
The system's ability to streamline workflows and automate ticket routing significantly reduces the time taken to process each ticket, making the process faster and more efficient. Mobile access allows field technicians to update ticket information on the go, ensuring that the latest information is always available and accelerating the locate process. Overall, Utilocate not only enhances the efficiency and accuracy of locate ticket management but also improves safety by minimizing the risk of utility damage through precise and timely locates.
Top Features to Include in Your Winzo Clone App for Business Growth (4).pptxrickgrimesss22
Discover the essential features to incorporate in your Winzo clone app to boost business growth, enhance user engagement, and drive revenue. Learn how to create a compelling gaming experience that stands out in the competitive market.
Zoom is a comprehensive platform designed to connect individuals and teams efficiently. With its user-friendly interface and powerful features, Zoom has become a go-to solution for virtual communication and collaboration. It offers a range of tools, including virtual meetings, team chat, VoIP phone systems, online whiteboards, and AI companions, to streamline workflows and enhance productivity.
2. viktor@jv-ration.com | @sadovnikov
Viktor Sadovnikov
● 1985 - first keyboard touch
● 1988 - first line of code
● 1993 - first computer at home
● 1994 - first paid line of code
● 2001 - first code to test another code
● 2005 - first build server run
● 2007 - first automated deployments
2
@sadovnikov
4. viktor@jv-ration.com | @sadovnikov
Common Build Project
Initial Scope
4
Source Repository From CVS to SVN
Build Tool From mix of Maven, Ant and Eclipse to Maven;
Dependencies from Nexus
Artifacts Repository From “something” to Nexus; deployable from Jenkins only;
Build Server From “something” to Jenkins;
Automate creation of builds jobs
Migration Done by projects themselves or (mainly stale) by us;
Extensive migration checklist
5. viktor@jv-ration.com | @sadovnikov
Common Build Project
“Bonus” Scope
5
Platform Moving builds from Windows to Linux
Upgrades Upgrading JDK during migration
Packaging 2 tailored packaging types
Deployment Number of applications shared dependencies at runtime
6. viktor@jv-ration.com | @sadovnikov
Common Build Project
Volumes
6
Maven modules
(artifacts)
3.500 (trunks only): 1.760 jars, 250 wars
External dependencies 2.200 libraries
Build jobs +/- 4.000 jobs (including branches)
Jenkins installations 12 instances;
later moved to 4 masters with pool of slaves
8. viktor@jv-ration.com | @sadovnikov
#1. Finding the Code
● Finding code of a dependency in SVN to check available tags (versions), to
find out correct group and artifact IDs, to contact developers;
● Enquiries about existing projects
8
● FishEye from Atlassian… works only on SVN
● SonarQube from SonarSource… finds everything
Solutions:
9. viktor@jv-ration.com | @sadovnikov
#2. Changing Shared Libraries
● Can I stop compiling for JDK 5?
● How much effort will my change cause?
● Do they use correct (after migration) and recent versions?
● What is used? How is used?
9
● NoneSolutions:
10. viktor@jv-ration.com | @sadovnikov
#3. Conflicts of Versions
● Direct dependency does not match transitive dependency
● What needs to be released before I can use changed shared library?
● Why do I get “entire world” as my compile dependency?
● (WRONG) Why do my builds pick-up old SNAPSHOT?
10
● Manual execution of Maven Dependency plugin (-Dverbose)
● Parsing the results
● On level of modules, not projects
Solutions:
11. viktor@jv-ration.com | @sadovnikov
#4. Finding the Builds
● 12 Jenkins instances and 4.000 build jobs
● Hard requirement of every project migration
11
● grep on build job configuration files… on all 12 servers
● Ctrl+F on Jenkins “all” page… unless the builds are renamed
● Referencing builds in pom.xml… gets obsolete quickly
Solutions:
13. viktor@jv-ration.com | @sadovnikov
Evolution of deCrex
deCrex - Development Environment Cross Examiner - scanner and analyzer of
source repositories and build servers
13
main() to
generate
JSON.
Running from
IntelliJ
Daily triggered
from Jenkins to
publish JSON
An intranet
application,
running
internally
Publically
available
installation to
scan OSS
Started simple... ...and could not stop
https://ossa.jv-ration.com
15. viktor@jv-ration.com | @sadovnikov
#2. Changing Shared Libraries
● List of direct dependees
● Versions direct
dependees depend on
● Quick access to details
of dependees
15
16. viktor@jv-ration.com | @sadovnikov
#3. Conflicts of Versions
● Build Jobs you project
depends on
● 7 Releases to push
changes in “Spring Data
Build” to “Spring Boot
Build”
● There are cycle
dependencies among
builds
16
20. viktor@jv-ration.com | @sadovnikov
Two Approaches
20
OSS Approach. Many-repos
● Every logically complete unit
(project) is in its own repo with
its own release cycle
● Build tools resolve
dependencies using artifact
repositories
● Most familiar approach, heavily
used in OSS projects
Monolithic Repos. Monorepos
● Single repository with all code
● No version constraints for
internal code
● All internal code is a part of the
build
● Used by companies like
Google, Facebook, Deis.io,
Twitter, Salesforce...
21. viktor@jv-ration.com | @sadovnikov
Many-repos Approach
● Clean boundaries between
projects
● Easier reusable in other contexts
code
● Fine-tuned access control
● Lighter, faster builds
21
● Refactoring becomes an
incompatible change
● Diamond dependencies and
interdependencies in internal code
● Loss of atomicity of commits
● Temptation to pick a version and
“stabilize” - stagnate
● Not fixing bugs in “not my code”
● Growth of obsolete and deprecated
code
22. viktor@jv-ration.com | @sadovnikov
Monorepos Approach
● Refactoring enabler: changing
APIs, removing obsolete code
● Atomic commits for large changes
● No switching between repos
● Collaboration among teams
● Less management (CI and repo)
● Code Management: search,
moving files around
22
● Ownership of the code is
detached from repo authorization
● Implementation problems: pulling
too much, mixed commit logs, etc
● Fully distributed SCM is
problematic
● Latency and requirements of
builds
23. viktor@jv-ration.com | @sadovnikov
Recognitions of Many-Repos Shortcomings
● Semantic Versioning
contract between me and you: since I can't know what you're doing, I promise not to do certain
things with my library so that you can use it with some confidence
● GIT Submodules and Subtrees
“you want to be able to treat the two projects as separate yet still be able to use one from within the
other”
● GitLab
Issues, Milestones and Merge Requests combined on group level
● @depricated
● Spring Boot
79 modules under one aggregator
23
24. viktor@jv-ration.com | @sadovnikov
deCrex - Wrapper for Many-repos
Enables use of many-repos with clean project boundaries and code ownership,
lighter builds and distributed SCM by adding
● insights on dependees of every project,
● reporting on
○ stagnated dependencies and interdependencies in internal code,
○ projects without dependees - either a “delivery” or an obsolete code,
● Build Plan to ease CI setup,
● searching through “monorepo”
24
25. viktor@jv-ration.com | @sadovnikov
Upcoming Changes
● Ease of installation on premises
● UI improvements
● Extending support for build tools (Gradle) and servers
(Travis CI), SCM (puur GIT)
25
● Configuring “Monorepo members”
● Managing “ownership” of the code
● Notifying code owners about stagnated dependencies
● Interested in scanning your code?