Continuous Integration
•Download as PPTX, PDF•
0 likes•333 views
This document provides an introduction to continuous integration (CI). It discusses how CI automates the manual processes of building, testing, and deploying code. The document explains that CI aims to keep the main development branch always green by quickly identifying and fixing any issues. It describes how a CI server works by monitoring code repositories, running jobs on agents to build, test and deploy code, and notifying developers of failures. Finally, it compares open-source CI tools like Jenkins in terms of their pros and cons.
Report
Share
Report
Share
Recommended
Continuous integration & deployment
The document discusses options for setting up continuous integration for native iOS applications. It explores unit testing libraries like Sentest and gh-unit, functional testing options like UIAutomation, iCuke, and Frank, and static analysis tools like scan-build. While many existing tools were found lacking or difficult to use in a CI environment, Frank was identified as an actively maintained and easy to run functional testing option. The document also mentions concerns about testing push notifications and API interactions that may break with changes.
Zero to the Cloud with @NetflixOSS
Getting started on AWS is easy, but building a scalable, reliable and performant product in the cloud can be a challenge for startups and enterprises alike. Netflix has famously migrated all our services to the cloud. Along the way, we have open sourced large portions of our platform that helped make this a reality. In this talk, Mike McGarr (Manager, Netflix Build Tools) will provide a survey of the @NetflixOSS products available. Mike will also share patterns and lessons Netflix learned migrating to the cloud. Lastly, Mike will leave you with a roadmap for how to get started with @NetflixOSS on your cloud today. This talk will cover the following @NetflixOSS products, and more!
Implementing DevOps
The document discusses implementing DevOps. It begins with an introduction of the speaker and an agenda that includes why organizations need DevOps, understanding DevOps culture, and DevOps prescriptions. Some key points made include that DevOps aims to shorten development cycles, increase collaboration between development and operations, and embrace automation, infrastructure as code, and monitoring.
Continuous delivery with open source tools
These slides are about my personal experience from creating a continuous delivery process in the last 2 years.
The main focus lies in the tools I used and my experience with them.
WebVisions: ISITE Design and CCLI on Platformication
George Ross, CIO at CCLI, and Kam Figy, Solution Architect at ISITE Design spoke at WebVisions 2012 in Portland, Oregon on the topic of “Platformification” and the SongSelect development experience.
Git basics, Team Workflows (Ciro Miranda)
The document discusses different version control workflows including local, centralized, and distributed systems. It focuses on Git and describes common Git commands like clone, status, add, commit, pull and push. Different Git workflows for teams are presented, including feature branches to isolate work and release branches to integrate completed features. The Git Flow model is described using main branches for production (master) and integration (develop), plus branches for features, releases and hotfixes.
Tanner Ellen - Forcelandia 2016 - Dev Stack.pptx
Forcelandia SalesForce session on the dev stack we use to develop SalesForce Canvas apps and web apps using Vagrant and ngrok.
https://appexchange.salesforce.com/listingDetail?listingId=a0N30000000qp64EAA
Practical Continuous Deployment - Atlassian - London AUG 18 Feb 2014
The document discusses practical approaches to implementing continuous deployment. It describes converting an organization's internal systems to continuous delivery and deployment over six months to address integration issues. Continuous deployment aims to release features, not unfinished work, through automation that makes releasing repeatable. Stakeholders benefit from faster delivery of features to customers and clearer progress signals. The document outlines a development workflow involving tracking requests, branching per feature, automated testing, code reviews, merging to a release branch, and deploying to staging and production. It also addresses challenges of automation and coordination across servers for the "last mile" of deployment.
Recommended
Continuous integration & deployment
The document discusses options for setting up continuous integration for native iOS applications. It explores unit testing libraries like Sentest and gh-unit, functional testing options like UIAutomation, iCuke, and Frank, and static analysis tools like scan-build. While many existing tools were found lacking or difficult to use in a CI environment, Frank was identified as an actively maintained and easy to run functional testing option. The document also mentions concerns about testing push notifications and API interactions that may break with changes.
Zero to the Cloud with @NetflixOSS
Getting started on AWS is easy, but building a scalable, reliable and performant product in the cloud can be a challenge for startups and enterprises alike. Netflix has famously migrated all our services to the cloud. Along the way, we have open sourced large portions of our platform that helped make this a reality. In this talk, Mike McGarr (Manager, Netflix Build Tools) will provide a survey of the @NetflixOSS products available. Mike will also share patterns and lessons Netflix learned migrating to the cloud. Lastly, Mike will leave you with a roadmap for how to get started with @NetflixOSS on your cloud today. This talk will cover the following @NetflixOSS products, and more!
Implementing DevOps
The document discusses implementing DevOps. It begins with an introduction of the speaker and an agenda that includes why organizations need DevOps, understanding DevOps culture, and DevOps prescriptions. Some key points made include that DevOps aims to shorten development cycles, increase collaboration between development and operations, and embrace automation, infrastructure as code, and monitoring.
Continuous delivery with open source tools
These slides are about my personal experience from creating a continuous delivery process in the last 2 years.
The main focus lies in the tools I used and my experience with them.
WebVisions: ISITE Design and CCLI on Platformication
George Ross, CIO at CCLI, and Kam Figy, Solution Architect at ISITE Design spoke at WebVisions 2012 in Portland, Oregon on the topic of “Platformification” and the SongSelect development experience.
Git basics, Team Workflows (Ciro Miranda)
The document discusses different version control workflows including local, centralized, and distributed systems. It focuses on Git and describes common Git commands like clone, status, add, commit, pull and push. Different Git workflows for teams are presented, including feature branches to isolate work and release branches to integrate completed features. The Git Flow model is described using main branches for production (master) and integration (develop), plus branches for features, releases and hotfixes.
Tanner Ellen - Forcelandia 2016 - Dev Stack.pptx
Forcelandia SalesForce session on the dev stack we use to develop SalesForce Canvas apps and web apps using Vagrant and ngrok.
https://appexchange.salesforce.com/listingDetail?listingId=a0N30000000qp64EAA
Practical Continuous Deployment - Atlassian - London AUG 18 Feb 2014
The document discusses practical approaches to implementing continuous deployment. It describes converting an organization's internal systems to continuous delivery and deployment over six months to address integration issues. Continuous deployment aims to release features, not unfinished work, through automation that makes releasing repeatable. Stakeholders benefit from faster delivery of features to customers and clearer progress signals. The document outlines a development workflow involving tracking requests, branching per feature, automated testing, code reviews, merging to a release branch, and deploying to staging and production. It also addresses challenges of automation and coordination across servers for the "last mile" of deployment.
Progressive Enhancement using WSGI
This document discusses WSGI (Web Server Gateway Interface), a Python standard for building web applications and APIs. WSGI allows web applications to be composed together through middleware. Middleware can modify requests and responses to add features like theming, error handling, and URL rewriting. The document advocates for using middleware to progressively enhance applications with features like CAPTCHAs in a reusable way across multiple frameworks and projects. An example is given of a WSGI middleware that inserts CAPTCHAs into forms on the fly without requiring changes to the underlying applications.
Jenkins Pipeline on your Local Box to Reduce Cycle Time
A case study on how to reduce continuous delivery cycle time by using your local resources as the starting point for the continuous delivery Jenkins Pipeline. Your local box has spare CPU, memory and a Git repo to be used with a local Jenkins Pipeline. You get fast feedback and create lots of precious artifacts.
#spsclt18 vincent biret #spfx #devops
Vincent Biret presents on how to implement DevOps practices with the SharePoint Framework. He discusses using Visual Studio Team Services for source control, automated builds, testing, and deployments. Biret demonstrates configuring a build definition, running unit tests, and integrating with SonarQube for technical debt management on a sample SPFx web part project. He advocates for automating processes and increasing quality to save time and money.
Git branching model
Session on Branching model with Git, and main differencies between a centralized version control system like TFVC.
20161103 Serverless Italy Meetup
This document summarizes a meetup about serverless technologies. It introduces the organizer and details that the meetup group was started as an experiment and has grown to 140 members who meet monthly. The key aspects of serverless technologies highlighted are that they are fast evolving and poorly documented. The most important things about the meetup are to join online discussions, present topics, provide contributions and ideas, and help spread awareness of serverless technologies.
Development Processes and Tooling
My tech talk topic for Hack the North hackathon at University of Waterloo. Easily build MVPs with the right development processes and tooling support.
Go with the flow!
Using Microsoft Flow to automate our workflows, automatically retweet based on certain hash tags and how powershell.cool was built entirely by content collected and generated by Microsoft Flow. Also Sheep.
Implementing Continuous Integration in .NET for Cheapskates
Using Continuous Integration in your project is a great way to significantly reduce integration problems, identify and resolve issues quickly, and develop cohesive software more rapidly. In this session, you'll learn how to implement Continuous Integration in your .NET project using a combination of team practices, free or open source tools, and scripts. In particular, we'll discuss various best practices, environment setup, package management (NuGet), source control (Git), automated build tools (NAnt, MSBuild, PowerShell), build servers (Cruise Control .NET), automated testing tools (MSTest, Moq, Selenium, Specflow), and code coverage (Open Cover).
Forcelandia Salesforce CI
The document discusses team development and continuous integration on the Force.com platform. It recommends critical components for success like issue tracking, source control, code review, and continuous integration. It provides examples of tools that can be used for these components, such as JIRA for issue tracking, GitHub for source control, and Snap CI for continuous integration. Regularly deploying code changes to a staging sandbox and conducting code reviews allows teams to catch errors early and ensure high quality code.
Serverless On Stage - Serverless URL Shortener
Slides for the first Serverless On Stage Meetup, discussing Microservices architectures and introduction to SLS 1.0
Continuous Integration and Delivery
- Continuous integration (CI) is the practice of merging developer working copies into a shared mainline repository multiple times per day. CI aims to integrate code early and often to prevent "integration hell" and make it easier to track down issues. Continuous delivery extends CI by automating and improving the software delivery process to allow for frequent deployments to any environment. The goal is to increase quality and decrease cycle times by putting release schedules in the hands of business rather than IT.
SGCE 2015 REST APIs
This document provides an overview of building REST APIs for distributed systems. It discusses motivation for APIs and the importance of an API contract. The document then covers tools for defining the API contract like RAML and code generation. It presents microservices architecture and implementation options using Spring Boot, Spring Cloud, and Netflix OSS frameworks. The talk concludes with a demo of a microservices application deployed with Docker.
Distribute your code with NUget and build vNext
This document discusses semantic versioning, GitFlow branching model, and how to automate versioning and packaging of code using GitVersion, NuGet, and Chocolatey. It recommends:
- Using semantic versioning (MAJOR, MINOR, PATCH) to manage versions in a Git repository.
- Implementing GitFlow branching model with main branches for development (develop) and releases (master).
- Leveraging GitVersion tool to determine semantic versions based on branches and commits.
- Automating builds to modify version numbers, compile code, run tests, create NuGet packages, and publish packages.
- Packaging and distributing applications using Chocolatey by creating NuGet packages containing
Deploy applications with TFS Build
This document discusses how to deploy .NET applications with TFS Build including:
- Deploying web applications to Azure or IIS using TFS build and Azure publishing
- Deploying SQL Server databases using database projects
- Deploying click-once applications and NuGet packages from TFS builds
It provides demonstrations of deploying to Azure, IIS, databases, and publishing NuGet packages and emphasizes the value of continuous deployment and testing for fast failure detection.
AgileLINC Continous Slides by Daniel Harp
This document discusses continuous integration practices. It defines continuous integration as an attitude rather than a tool. Key practices of continuous integration include: maintaining a single source repository, automating builds, keeping builds fast, making builds self-testing through automated tests, committing to the mainline daily to avoid branches, triggering a build on every commit through a build server, making every commit potentially shippable, ensuring binary integrity, testing in a clone of production, making the latest executable easily available, and enabling everyone to see what's happening. The document emphasizes focusing on organizational, architectural and process changes over tools when adopting continuous integration.
Implementation of the Continuous Integration based on Atlassian Bamboo
This document discusses continuous integration with Atlassian Bamboo. It describes using Bamboo to automatically run tests, build, and deploy code. It outlines the common CI process and how to configure a Bamboo project and plan mapped to a code repository. Bamboo is used to unify the deployment process across environments and minimize human errors during production deployments. Benefits of Bamboo include integrating unit tests, building/deploying without direct server access, and permission control.
Automate everything with PowerShell
The signs are on the wall, scripting and coding is becoming increasingly important for any role in IT. PowerShell is a crucial component in your toolkit and in this session we will cover the basics of PowerShell and how you can get started and be successful, how we can secure systems running PowerShell and what benefits can it bring.
In this session Jaap will talk about what PowerShell is, the language, the console, the editors and how PowerShell came to be. Recently PowerShell has been made open source and multi-platform. We will look at what the implications are and what benefits this brings along.
As security is increasingly a more important consideration for every company, we will take a look at what capabilities PowerShell has and how we can use these tools to create a more secure scripting environment.
This session contains multiple real-world examples and applications of this technology. There will be time for questions during the session and if you have any specific PowerShell related questions that are not answered in the presentation Jaap will be available for questions all day.
Flex and .NET Integration
Flex is an open source framework for building interactive web applications that run consistently across browsers and platforms. It uses MXML for declarative UI layouts and ActionScript for client logic. Flex includes a rich library of predefined UI controls like datagrids and charts. It can be used for both web and desktop development via AIR, adding features like file access.
Jenkins CI in Action
Jenkins CI in Action discusses Continuous Integration (CI) and the Jenkins platform. It provides an overview of what CI is, who Jenkins is as a platform for CI, and why you might want to use Jenkins. It also briefly discusses the Gerrit alternative and common Jenkins workflows like using Gerrit as a trigger or running builds on a schedule. Tips are provided for optimizing Jenkins performance.
Ci & proServer
This document discusses how continuous integration (CI) and continuous delivery (CD) can help software teams automatically merge code changes, deploy updates, and reduce errors. It recommends a simple stack using Gitlab for version control and CI, TYPO3 Surf for automated deployments and testing, and Ansible for infrastructure automation. The document argues that the proServer is well-suited for CI/CD with these tools and that the company punkt.de can help organizations set up and improve their CI/CD processes.
Introduction to Continuous Integration
The document discusses continuous integration (CI) and build pipelines. Some key points covered include:
- CI involves automating the build, testing, and deployment processes to integrate code changes frequently and minimize errors.
- Benefits of CI include fewer errors, fast feedback, reduced manual testing, and greater confidence in the product.
- Common CI practices involve maintaining a single code repository, automating builds, making builds self-testing, committing code daily, building every commit, keeping builds fast, and automating deployments.
- A build pipeline automates the stages of the CI/CD process from code changes to deployment to production.
Continuous Integration (& Mr Jenkins)
This document discusses continuous integration and the Jenkins continuous integration server. It defines continuous integration as integrating code changes frequently, usually daily, and verifying them through automated builds and tests to detect errors quickly. The benefits of CI include efficiency, reproducibility, and keeping the mainline code always ready for release. It also discusses best practices like source control, testing everything, and visibility. Jenkins is introduced as a popular open source CI server written in Java that is easy to use, extensible with over 1100 plugins, and enables continuous delivery through flexibility.
More Related Content
What's hot
Progressive Enhancement using WSGI
This document discusses WSGI (Web Server Gateway Interface), a Python standard for building web applications and APIs. WSGI allows web applications to be composed together through middleware. Middleware can modify requests and responses to add features like theming, error handling, and URL rewriting. The document advocates for using middleware to progressively enhance applications with features like CAPTCHAs in a reusable way across multiple frameworks and projects. An example is given of a WSGI middleware that inserts CAPTCHAs into forms on the fly without requiring changes to the underlying applications.
Jenkins Pipeline on your Local Box to Reduce Cycle Time
A case study on how to reduce continuous delivery cycle time by using your local resources as the starting point for the continuous delivery Jenkins Pipeline. Your local box has spare CPU, memory and a Git repo to be used with a local Jenkins Pipeline. You get fast feedback and create lots of precious artifacts.
#spsclt18 vincent biret #spfx #devops
Vincent Biret presents on how to implement DevOps practices with the SharePoint Framework. He discusses using Visual Studio Team Services for source control, automated builds, testing, and deployments. Biret demonstrates configuring a build definition, running unit tests, and integrating with SonarQube for technical debt management on a sample SPFx web part project. He advocates for automating processes and increasing quality to save time and money.
Git branching model
Session on Branching model with Git, and main differencies between a centralized version control system like TFVC.
20161103 Serverless Italy Meetup
This document summarizes a meetup about serverless technologies. It introduces the organizer and details that the meetup group was started as an experiment and has grown to 140 members who meet monthly. The key aspects of serverless technologies highlighted are that they are fast evolving and poorly documented. The most important things about the meetup are to join online discussions, present topics, provide contributions and ideas, and help spread awareness of serverless technologies.
Development Processes and Tooling
My tech talk topic for Hack the North hackathon at University of Waterloo. Easily build MVPs with the right development processes and tooling support.
Go with the flow!
Using Microsoft Flow to automate our workflows, automatically retweet based on certain hash tags and how powershell.cool was built entirely by content collected and generated by Microsoft Flow. Also Sheep.
Implementing Continuous Integration in .NET for Cheapskates
Using Continuous Integration in your project is a great way to significantly reduce integration problems, identify and resolve issues quickly, and develop cohesive software more rapidly. In this session, you'll learn how to implement Continuous Integration in your .NET project using a combination of team practices, free or open source tools, and scripts. In particular, we'll discuss various best practices, environment setup, package management (NuGet), source control (Git), automated build tools (NAnt, MSBuild, PowerShell), build servers (Cruise Control .NET), automated testing tools (MSTest, Moq, Selenium, Specflow), and code coverage (Open Cover).
Forcelandia Salesforce CI
The document discusses team development and continuous integration on the Force.com platform. It recommends critical components for success like issue tracking, source control, code review, and continuous integration. It provides examples of tools that can be used for these components, such as JIRA for issue tracking, GitHub for source control, and Snap CI for continuous integration. Regularly deploying code changes to a staging sandbox and conducting code reviews allows teams to catch errors early and ensure high quality code.
Serverless On Stage - Serverless URL Shortener
Slides for the first Serverless On Stage Meetup, discussing Microservices architectures and introduction to SLS 1.0
Continuous Integration and Delivery
- Continuous integration (CI) is the practice of merging developer working copies into a shared mainline repository multiple times per day. CI aims to integrate code early and often to prevent "integration hell" and make it easier to track down issues. Continuous delivery extends CI by automating and improving the software delivery process to allow for frequent deployments to any environment. The goal is to increase quality and decrease cycle times by putting release schedules in the hands of business rather than IT.
SGCE 2015 REST APIs
This document provides an overview of building REST APIs for distributed systems. It discusses motivation for APIs and the importance of an API contract. The document then covers tools for defining the API contract like RAML and code generation. It presents microservices architecture and implementation options using Spring Boot, Spring Cloud, and Netflix OSS frameworks. The talk concludes with a demo of a microservices application deployed with Docker.
Distribute your code with NUget and build vNext
This document discusses semantic versioning, GitFlow branching model, and how to automate versioning and packaging of code using GitVersion, NuGet, and Chocolatey. It recommends:
- Using semantic versioning (MAJOR, MINOR, PATCH) to manage versions in a Git repository.
- Implementing GitFlow branching model with main branches for development (develop) and releases (master).
- Leveraging GitVersion tool to determine semantic versions based on branches and commits.
- Automating builds to modify version numbers, compile code, run tests, create NuGet packages, and publish packages.
- Packaging and distributing applications using Chocolatey by creating NuGet packages containing
Deploy applications with TFS Build
This document discusses how to deploy .NET applications with TFS Build including:
- Deploying web applications to Azure or IIS using TFS build and Azure publishing
- Deploying SQL Server databases using database projects
- Deploying click-once applications and NuGet packages from TFS builds
It provides demonstrations of deploying to Azure, IIS, databases, and publishing NuGet packages and emphasizes the value of continuous deployment and testing for fast failure detection.
AgileLINC Continous Slides by Daniel Harp
This document discusses continuous integration practices. It defines continuous integration as an attitude rather than a tool. Key practices of continuous integration include: maintaining a single source repository, automating builds, keeping builds fast, making builds self-testing through automated tests, committing to the mainline daily to avoid branches, triggering a build on every commit through a build server, making every commit potentially shippable, ensuring binary integrity, testing in a clone of production, making the latest executable easily available, and enabling everyone to see what's happening. The document emphasizes focusing on organizational, architectural and process changes over tools when adopting continuous integration.
Implementation of the Continuous Integration based on Atlassian Bamboo
This document discusses continuous integration with Atlassian Bamboo. It describes using Bamboo to automatically run tests, build, and deploy code. It outlines the common CI process and how to configure a Bamboo project and plan mapped to a code repository. Bamboo is used to unify the deployment process across environments and minimize human errors during production deployments. Benefits of Bamboo include integrating unit tests, building/deploying without direct server access, and permission control.
Automate everything with PowerShell
The signs are on the wall, scripting and coding is becoming increasingly important for any role in IT. PowerShell is a crucial component in your toolkit and in this session we will cover the basics of PowerShell and how you can get started and be successful, how we can secure systems running PowerShell and what benefits can it bring.
In this session Jaap will talk about what PowerShell is, the language, the console, the editors and how PowerShell came to be. Recently PowerShell has been made open source and multi-platform. We will look at what the implications are and what benefits this brings along.
As security is increasingly a more important consideration for every company, we will take a look at what capabilities PowerShell has and how we can use these tools to create a more secure scripting environment.
This session contains multiple real-world examples and applications of this technology. There will be time for questions during the session and if you have any specific PowerShell related questions that are not answered in the presentation Jaap will be available for questions all day.
Flex and .NET Integration
Flex is an open source framework for building interactive web applications that run consistently across browsers and platforms. It uses MXML for declarative UI layouts and ActionScript for client logic. Flex includes a rich library of predefined UI controls like datagrids and charts. It can be used for both web and desktop development via AIR, adding features like file access.
Jenkins CI in Action
Jenkins CI in Action discusses Continuous Integration (CI) and the Jenkins platform. It provides an overview of what CI is, who Jenkins is as a platform for CI, and why you might want to use Jenkins. It also briefly discusses the Gerrit alternative and common Jenkins workflows like using Gerrit as a trigger or running builds on a schedule. Tips are provided for optimizing Jenkins performance.
Ci & proServer
This document discusses how continuous integration (CI) and continuous delivery (CD) can help software teams automatically merge code changes, deploy updates, and reduce errors. It recommends a simple stack using Gitlab for version control and CI, TYPO3 Surf for automated deployments and testing, and Ansible for infrastructure automation. The document argues that the proServer is well-suited for CI/CD with these tools and that the company punkt.de can help organizations set up and improve their CI/CD processes.
What's hot (20)
Jenkins Pipeline on your Local Box to Reduce Cycle Time
Jenkins Pipeline on your Local Box to Reduce Cycle Time
Implementing Continuous Integration in .NET for Cheapskates
Implementing Continuous Integration in .NET for Cheapskates
Implementation of the Continuous Integration based on Atlassian Bamboo
Implementation of the Continuous Integration based on Atlassian Bamboo
Similar to Continuous Integration
Introduction to Continuous Integration
The document discusses continuous integration (CI) and build pipelines. Some key points covered include:
- CI involves automating the build, testing, and deployment processes to integrate code changes frequently and minimize errors.
- Benefits of CI include fewer errors, fast feedback, reduced manual testing, and greater confidence in the product.
- Common CI practices involve maintaining a single code repository, automating builds, making builds self-testing, committing code daily, building every commit, keeping builds fast, and automating deployments.
- A build pipeline automates the stages of the CI/CD process from code changes to deployment to production.
Continuous Integration (& Mr Jenkins)
This document discusses continuous integration and the Jenkins continuous integration server. It defines continuous integration as integrating code changes frequently, usually daily, and verifying them through automated builds and tests to detect errors quickly. The benefits of CI include efficiency, reproducibility, and keeping the mainline code always ready for release. It also discusses best practices like source control, testing everything, and visibility. Jenkins is introduced as a popular open source CI server written in Java that is easy to use, extensible with over 1100 plugins, and enables continuous delivery through flexibility.
Continuous integration
The document discusses continuous integration and automated builds. It defines continuous integration as decreasing integration times to speed up software delivery. It outlines 5 steps to continuous integration: using a source control repository, automating builds, integrating continuously rather than just daily, using tools like Team Foundation Server, MSBuild and CruiseControl.NET, and following a development process of frequent check-ins and merges. Benefits include reduced risk and improved team collaboration and morale. Anti-patterns include delaying check-ins and ignoring broken builds.
Enter the Team City
Continuous integration (CI) with TeamCity automates the software building and testing process. It allows developers to check in code frequently and have builds run automatically to detect issues early. TeamCity monitors source code repositories for changes, builds the code, and runs tests on each change. This helps ensure all code components work together, coding standards are followed, and tests are passing. CI with TeamCity provides benefits like reduced risks from early defect detection, increased visibility into the project, and confidence in the software.
DBmaestro's State of the Database Continuous Delivery Survey- Findings Revealed
DBmaestro's State of the Database Continuous Delivery Survey- Findings RevealedDBmaestro - Database DevOps
The document summarizes findings from a survey on continuous delivery practices. The survey found that while 81% of organizations practiced some form of continuous delivery for their code, only around 50% did so for their databases. Key challenges included a lack of database version control, manual scripting processes prone to errors, and a lack of trust and communication between developers and database administrators. Adopting database version control, automated deployments informed by version control data, and making DBAs responsible for continuous delivery processes could help address these challenges and barriers to fully implementing continuous delivery for databases.Continuous integration, delivery & deployment
A presentation on Continuous Integration, Delivery and Deployment. This presentation was used as an introduction to the subject.
Continuous integrations - Basics
The document discusses continuous integration, which is a software engineering practice where a project is built and tested frequently, such as each time a change is committed to the main code repository. It recommends using a revision control system, a dedicated build server, and getting an open-minded team. Key aspects of continuous integration include automated building, testing, code quality analysis, and having the project always be in a deployable state. Tools mentioned that can help with continuous integration include Jenkins for building and testing, Gerrit for code reviews, and SonarQube for code quality analysis.
Git Branching – the battle of the ages
Comparison of two common git workflows - trunk based and git-flow workflow.
Shared presentation by Jasmin Fluri and Gianni Ceresa.
Continuous integration sql in the city
Ike Ellis discusses continuous integration (CI), which involves automatically building and testing software applications whenever code changes are committed to source control. CI aims to prevent integration issues by catching errors early. Key aspects of CI include source control, build triggers, build agents, notifications, and correction of broken builds. CI tools like Jenkins and TeamCity can help implement CI processes. While CI requires setup effort, it offers benefits like higher code quality, easier deployments, and reduced "works on my PC" issues.
PHP Unconference Continuous Integration
Presentation for PHP Unconference 2011 - unfortunately I did not get enough votes so never did the talk :(
Continuos Integration and Delivery: from Zero to Hero with TeamCity, Docker a...
A journey from the beginning of software deployment to the latest technologies for high availability.
Continuous integration
Continuous integration (CI) is a software engineering practice where developers regularly merge code changes into a central repository, and automated builds and tests are run on every change. This helps prevent integration problems and allows teams to easily identify issues. CI benefits teams by reducing risk through more automated testing, improving deployment speed and reliability, and making it easier to identify when problems arise. Popular tools for implementing CI include Git repositories for code management and Jenkins for running automated builds and tests on every code change.
Continuous Delivery
Continuous Delivery
What it takes to move to continuous integration and Continuous Delivery/Deployment model.
www.scmtechblog.net
SanDiego_DevOps_Meetup_9212016-v8
Mitchell International has been providing property and casualty claims services for 70 years. Raj Makkar and Richard Fong discuss Mitchell's journey to continuous integration and delivery over the past 7 years. They moved from a slow "big build" process controlled by one team to a componentized approach where developers control builds. Today, builds occur on every check-in with immediate feedback. They use tools like Jenkins and Artifactory to manage over 1400 jobs per day across many platforms. Their goal is rapid, quality software delivery through a culture of automation, testing, and collaboration across teams.
Constinuous Integration
What's the hype about continuous integration? Learn the right way you should be using it inside your team to deliver software at scale with quality and confidence.
August Webinar - Water Cooler Talks: A Look into a Developer's Workbench
The webinar covered tools and techniques used by several developers in their work with Domino and XPages. Howard Greenberg discussed using SourceTree and BitBucket for version control of XPages applications. Jesse Gallagher presented his toolchain including Eclipse, Maven, and Jenkins for plugin and application development. Serdar Basegmez outlined his development environment including configuring Eclipse to develop OSGi plugins for the Domino runtime. All emphasized the importance of source control, testing, and documentation in their processes.
CI
Continuous Integration (CI) is a software development practice where developers regularly merge their work into a central repository. This allows for automated builds and tests which catch errors early. CI helps reduce integration problems, improves code quality, and allows for more frequent deployments. The document discusses implementing CI with tools like Jenkins, build scripts, unit testing, code analysis, and notifications to improve the development process.
Beautiful Builds - Roy Osherove at Microsoft Swit
more info at http://BeautifulBuilds.com
Roy Osherove speaks at Microsoft SWIT conference in Ukraine about build patterns, build tools, continuous integration, continuous delivery, and how to make it all work.
A Business Case for Git - Tim Pettersen
So you want to go Git, but other stakeholders in your organization aren't quite convinced it's worth the effort? This talk will explain why migrating to Git is a win for the whole business – not just developers. We'll give you the ammunition you need to convince your team that the switch to Git is a no-brainer.
GR Dev Day Presentation, March 21 2015
The document discusses automating various tasks through code generation, testing automation, continuous integration/deployment, and tools that automate tasks in daily life. It provides examples of automating safety critical applications using SCADE, test automation using Selenium and Pex/Code Digger, and continuous integration using Jenkins. It concludes with practical advice for automating such as using the right tools, embracing the command line, and automating recurring tasks without permission.
Similar to Continuous Integration (20)
DBmaestro's State of the Database Continuous Delivery Survey- Findings Revealed
DBmaestro's State of the Database Continuous Delivery Survey- Findings Revealed
Continuos Integration and Delivery: from Zero to Hero with TeamCity, Docker a...
Continuos Integration and Delivery: from Zero to Hero with TeamCity, Docker a...
August Webinar - Water Cooler Talks: A Look into a Developer's Workbench
August Webinar - Water Cooler Talks: A Look into a Developer's Workbench
More from Sergio Shevchenko
Gestione dell'economia nelle reti di Self Sovereign Identity con Algorand Sm...
Dalla Blockchain al Bitcoin, ormai questi sono i termini che riempiono volenti o nolenti la stragrande maggioranza delle nostre giornate. Applicazioni di trading, misurazioni di valore, corrispettivi su monete reali: la tecnologia ha investito appieno l’intoccabile, ergendosi a baluardo dei gruppi comunitari, tagliando in modo netto la necessità di organismi terzi, intermediari che fino a oggi sono stati satelliti piuttosto discussi attorno a cui gira la nostra economia.
In questi termini è lampante che la Blockchain sia una vera e propria rivoluzione. Questa tecnologia che si presenta come un registro decentralizzato che contiene ogni transazione, nel caso specifico di Bitcoin trattasi di un trasferimento monetario, ma è evidente che, in un caso generico e con un po’ di astrazione, sia possibile applicarla a qualsiasi campo in cui ciò si voglia trasmettere assume il significato di valore. Grazie a una serie di protocolli innovativi, si presenta come un’infrastruttura efficiente, accurata e sicura.
Alla Blockchain è affidato il compito di gestire, trasferire e conservare, ma Cosa?
Più o meno tutto: è parso molto chiaro, infatti, che codesta tecnologia può essere utilizzata per documentare il trasferimento di qualsiasi tipo di asset digitale, registrare proprietà, siano esse di natura fisica o intellettuale, creare nuove tipologie di contratti quali gli Smart Contracts, operando sostanzialmente in maniera più rapida e con costi nettamente ridotti.
In conformità a ciò che è un database, la Blockchain lavora come un registro distribuito gestito da una rete peer-to-peer che promette sicurezza basandosi su complessi e avanzati algoritmi crittografici che la stessa comunità è chiamata a risolvere.
Tuttavia, considerando la sua architettura, non è applicabile su larga scala. Questo ha portato allo sviluppo di altre tipologie di Blockchain, dove l’approccio di prova di partecipazione, prova di lavoro e il protocollo di accordo cambiano ripetutamente.
Un esempio specifico e pratico è stata la rete di criptovaluta Algorand, focalizzata e rivolta sui pagamenti e sugli Smart Contracts. Algorand è una risposta diretta all’inefficienza computazionale e alla tendenza della Proof of Work (prova di lavoro) di Bitcoin che potrebbe condurre e portare alla centralizzazione del mining.
In Algorand oltre ad introdurre una prova di lavoro innovativa e di Smart Contracts flessibili è possibile creare una sua criptovaluta stabile. Algorand Smart Contracts e Algorand Standard Assets sono stati dei mattoncini necessari per portare uno strato di economics all’interno della rete Self-Sovereign-Identity anch’essa basata sulla blockchain, introducendo brillantemente un ponte tra i vari partecipanti sotto forma di un servizio.
Kubernetes - from sketch to production
The document provides an overview of the key building blocks that make up Kubernetes, including:
- Deployments to manage replicated applications and roll out updates.
- Services for load balancing and exposing applications using labels.
- Jobs and CronJobs for running periodic or one-time tasks.
- Volumes for persistent storage and sharing data between containers.
- StatefulSets for managing stateful applications.
- Ingresses for external access to applications via an load balancer.
The document outlines the purpose and usage of each building block at a high level through diagrams and YAML examples. It aims to explain the fundamental components that can be composed to build and run applications on Kubernetes.
Meltdown & spectre
This document discusses the Meltdown and Spectre vulnerabilities that were discovered in modern CPUs. Meltdown allows reading kernel memory from user space by exploiting out-of-order execution and speculative execution. Spectre attacks exploit speculative execution to access sensitive information through side channels. The document explains speculative execution, how Meltdown works by reading kernel memory speculatively, and the two variants of Spectre attacks - bound check bypass and branch target injection. Mitigations like KPTI and inserting speculative execution blocking instructions are discussed. The vulnerabilities are considered some of the greatest in computer history due to their fundamental exploitation of CPU designs.
The Google file system
The Google File System was designed by Google to store and manage large files across thousands of commodity servers. It uses a single master to manage metadata and track file locations across chunkservers. Chunks are replicated for reliability and placed across racks to improve bandwidth utilization. The system provides high throughput for concurrent reads and writes through leases to maintain consistency and pipelining of data flows. Logs and replication are used to provide fault tolerance against server failures.
μ-Kernel Evolution
Mach was an early microkernel-based operating system from the 1980s that served as the basis for several later systems. It employed asynchronous inter-process communication (IPC) which led to significant performance penalties compared to monolithic kernels. The L3 and L4 microkernels from the 1990s improved IPC performance by an order of magnitude through techniques like synchronous IPC and architecture-specific optimizations. This helped validate that microkernels could achieve adequate performance. L4Linux brought the Linux kernel to run as a user process on top of L4 microkernels like Fiasco.OC. It required paravirtualizing portions of Linux to interface with the microkernel but typically incurred only 5-10% performance penalties compared to native
Burrows-Wheeler transform for terabases
We describe how BWT works, how it can be useful for compression of DNA reads. In second part, we talk about indexing and querying data transformed with BWT
Design patterns: Creational patterns
Creational patterns are main building blocks in software development. Here are shown some key-concept and simple examples
Bitcoin and blockchain
Presentation describes main concepts of bitcoin and some concepts of blockchain technology
Qt Multiplatform development
This document provides an overview of communicating between Qt and native platforms like Android and iOS. It discusses using facades and abstractions to provide a platform-independent API for features like vibration. For Android, it describes using the Java Native Interface to export C++ functions and ensure the Java code can safely access the Android UI thread. It also addresses starting Qt and checking it has initialized before calling into C++ code. The document provides examples of integrating Qt into mobile projects for cross-platform development.
Qt for beginners
This document provides an overview and introduction to Qt for beginners. It covers the key features of Qt including writing code once to target multiple platforms. The agenda includes a C++ refresher on core concepts like objects, classes and signals/slots. It demonstrates a basic "Hello World" application in both C++ and QML. Core Qt classes covered are containers, iterators, QObject and signals/slots. The document looks ahead to covering more advanced Qt topics in future parts.
Mobile Factor App
Presentation of mobile factor concept, app which allows to store all credentials inside iPhone SecureEnclave.
More from Sergio Shevchenko (12)
Gestione dell'economia nelle reti di Self Sovereign Identity con Algorand Sm...
Gestione dell'economia nelle reti di Self Sovereign Identity con Algorand Sm...
Recently uploaded
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
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.
AWS Cloud Cost Optimization Presentation.pptx
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
FREE A4 Cyber Security Awareness Posters-Social Engineering part 3
Free A4 downloadable and printable Cyber Security, Social Engineering Safety and security Training Posters . Promote security awareness in the home or workplace. Lock them Out From training providers datahops.com
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
A Comprehensive Guide to DeFi Development Services in 2024
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
dbms calicut university B. sc Cs 4th sem.pdf
Its a seminar ppt on database management system using sql
Trusted Execution Environment for Decentralized Process Mining
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
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.
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 .
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
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).
Astute Business Solutions | Oracle Cloud Partner |
Your goto partner for Oracle Cloud, PeopleSoft, E-Business Suite, and Ellucian Banner. We are a firm specialized in managed services and consulting.
Choosing The Best AWS Service For Your Website + API.pptx
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
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.
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Recently uploaded (20)
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
FREE A4 Cyber Security Awareness Posters-Social Engineering part 3
FREE A4 Cyber Security Awareness Posters-Social Engineering part 3
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
A Comprehensive Guide to DeFi Development Services in 2024
A Comprehensive Guide to DeFi Development Services in 2024
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
WeTestAthens: Postman's AI & Automation Techniques
WeTestAthens: Postman's AI & Automation Techniques
Trusted Execution Environment for Decentralized Process Mining
Trusted Execution Environment for Decentralized Process Mining
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
Astute Business Solutions | Oracle Cloud Partner |
Astute Business Solutions | Oracle Cloud Partner |
Choosing The Best AWS Service For Your Website + API.pptx
Choosing The Best AWS Service For Your Website + API.pptx
Continuous Integration
- 1. Continuous Integration Introduction to Sergio Shevchenko
- 2. Without CI
- 3. Everything “handmade” and “irregularly” • Build • Deploy in test • Testing • Deploy in production
- 6. A lot of handwork!
- 9. Main idea: Always green develop branch
- 10. Target: Quickly understand and repair
- 11. CI server!
- 12. Allows you to automate or not automate …☺
- 15. Important: In case of failure - STOP!
- 16. Notifications! is always accused☺ The last committer
- 17. How the CI server Works
- 18. Server (master)
- 19. Agents (slaves)
- 20. Jobs (tasks)
- 21. Plugins
- 22. The Essence: run jobs •By cron •By event •By request
- 25. •Free •Support different SCM: git, svn •Support maven from the box
- 26. •Open source •Big community •A lot of different plugins Pros
- 27. •Open source ☺ •Interface… •Difficult to scale Cons
- 29. •Pre-commit build&test •Integrated code coverage&analysis •Integration with IDEA, Eclipse, VS •Free for no-commercial use
- 30. •Customer Support •Beautiful UI •Low entry threshold Pros
- 32. CI tools
- 33. Configuring CI Together with Jenkins
- 34. Job
- 36. Simplest case Run a shell script
- 39. Plugins
- 41. Reports
- 43. Notifications
- 44. Conveyor
- 46. Demo