DevOpsDaysRiga 2018: Anton Arhipov - Build pipelines with TeamCity

•

0 likes•94 views

Build engineering is fun, especially with the awesome choice of tools we have today! In this showcase I’m building a build pipeline with TeamCity. You are going to learn why build pipelines are useful (yes, not only for the sake of eye candy!), and how the CI server can optimise when properly configured. In this talk I’m going to start with the simple scenarios and gradually introduce the complexity: scaling the project by adding constraints and requirements. This will result in changing the build process and revealing the tips & tricks alongside.

Technology

Build Pipelines
with TeamCity
@antonarhipov

Build pipeline
Step 4Step 2 Step 3Step 1

Build pipeline
Step 4Step 2 Step 3Step 1 Result

Build pipeline
Step 4Step 2 Step 3Step 1
More
steps
Result

CI/CD pipeline
AuditTest PackageCompile
Test
Build pipeline a.k.a CI pipeline
TEST PRODDEV
CD pipeline
.rpm SW

Check out sources
Compile
Run tests
Generate report
Publish the results

Looks
simple!
Check out sources
Compile
Run tests
Generate report
Publish the results

Looks
simple!Why do
I need a
“pipeline”?
Check out sources
Compile
Run tests
Generate report
Publish the results

Check out sources
Compile
Run fast tests
Generate report
Publish the results

Check out sources
Compile
Run fast tests
Generate report
Publish the results
Run
integration,
UI
tests

Check out sources
Compile
Run fast tests
Generate report
Publish the results
Run
integration,
UI
tests
Pipeline!!

Build Test
Check out sources
Compile
Run fast tests
Generate report
Publish the results
Run
integration,
UI
tests

UI-testing
Reports &
notiﬁcations
Build
Integration
testing
More
integration
testing

Tests
Reports &
notiﬁcations
Build Tests
Tests
Build

Tests
Reports &
notiﬁcations
Build Tests
Tests
Build
Dependencies

TeamCity @ JetBrains
1800+ projects
10000+ build conﬁgurations
500+ agents
Average build time ~25 mins
est 2006

Step 1
Step 2
Step 3
Step 4
rev 1
rev 2
rev 3

Step 1
Step 3
Step 4
rev 1
rev 3
rev 3
Step 2

rev 1
rev 3
rev 3
Step 1
Step 3
Step 2
Step 4

rev 3
“snapshot dependency”
Step 1
Step 3
Step 2
Step 4
rev 1
rev 3

B
rev1
A
rev1
C
rev1
D
rev1
1 2 3 4
…
B
rev2

@antonarhipov
?anton.arhipov@jetbrains.com

A build pipeline refers to the automated process of building software by breaking it down into discrete steps. This document discusses how TeamCity, a build management and continuous integration tool, can be used to create build pipelines. It provides an example pipeline with steps for checking out sources, compiling code, running tests at different stages, generating reports, and publishing results. The benefits of a pipeline include running different test types in parallel and tracking dependencies between steps to speed up the overall build process.

Build pipelines with TeamCity

Anton Arhipov

TeamCity is a build management and continuous integration tool created by JetBrains that allows building pipelines of steps. It supports over 2000 projects with 12,000 build configurations running on 500 agents. Key features include a Kotlin DSL, HA read-only servers, Docker runner improvements, templates for step ordering, enforced settings, .NET Core support, and plugins. Pipelines allow breaking up builds into sequential steps like compiling, running tests, and publishing results to improve efficiency.

Continuous Integration for Titanium

Denver Sessink

TiCalabash and TiMocha: The keys to Better & More Stable Titanium Apps

Andrew McElroy

Simple Unit Testing in Appcelerator Titanium Alloy

Aaron Saunders

Devops practice

Bryan Huang

The document describes DevOps practices for continuous integration and delivery which includes code review and unit testing, building and packaging code, deploying to test environments, conducting continuous verification testing and functional verification testing, promoting builds to staging environments for further testing, and finally promoting golden builds to production environments. The process involves collecting logs at each stage to track progress, detect failures for defect tracking, and allow for log analysis to improve the process.

Continuous testing

Brandon Raines

Ci tools Introduce

Yin-Hong Hsu

This document discusses continuous integration tools and automated testing tools. It describes the continuous integration workflow of committing code to a version control system like Git, which then triggers an automated build and test via a continuous integration tool like Jenkins. These CI tools can be configured to generate reports on the build and test results and deploy builds if they pass. Popular CI tools mentioned include Jenkins, Travis CI, and Bamboo. The document also discusses automated testing tools for acceptance testing and unit/white box testing on various platforms like Android, iOS, and web.

The document discusses software development terminology related to continuous integration, delivery, and deployment. It defines these terms and diagrams the processes. Continuous integration means integrating code changes frequently through automated builds and tests. Continuous delivery means software can be released at any time through automated processes. Continuous deployment means all code changes that pass tests are automatically deployed to production. DevOps means development and operations teams work together using the same tools and methods.

Testing, CI and CD in the real world

Roc Boronat

The document discusses different types of software testing including unitary tests, integration tests, and instrumentation tests. It provides examples of how unitary tests can be used to develop regular expressions, parse deep links, improve an invoice generator, and refactor legacy code. Tips are provided on following a given-when-then style for unitary tests and testing one thing at a time. Integration tests and instrumentation tests are discussed for developing APIs and testing apps end-to-end. Continuous integration and continuous delivery are also summarized.

Speed up your Titanium app development with automated tests - TiConf EU 2014

Emanuele Rampichini

Continuous delivery of your legacy application

ColdFusionConference

This document discusses continuous delivery of legacy applications. It begins with introductions and definitions of key terms like continuous delivery, legacy code, and types of testing. It then discusses challenges like refactoring legacy code without tests and proposes solutions like using Selenium for GUI testing and TestBox for unit testing. The document recommends strategies for continuous integration and delivery pipelines to enable one click deployments. It concludes by providing resources for learning more about topics like Cucumber and Selenium WebDriver.

DockerCon'15: Shipping Containers to Enterprise Customers

Weihan Wang

While many businesses adopt Docker for in-house operations, we wrap our apps in containers as a way to deliver them to enterprise customers. In this talk, I'll discuss our experiences with Docker, and the techniques we used to containerize the entire AeroFS virtual appliance. I will also describe an open source tool we developed, that allows application vendors to build and deliver containerized virtual appliances at ease.

An Introduction To Automated API Testing

Sauce Labs

As more and more apps are being assembled from a rapidly expanding array of microservices, APIs are the key to accessing these new architectures. That new feature you’re working on will often rely on upstream services that can only be accessed via APIs - so to test the functionality of the new component you’ll need to simulate those services. While APIs are the backbone of the websites and apps we rely on today, automated testing of them is only starting to grow. Join Patrick Poulin, CEO of API Fortress, as he provides an introduction to API testing, the best ways to test your own APIs using popular tools available today, and demonstrates the orchestration of API tests and Sauce Labs tests as part of a Jenkins build process. Key takeaways: -Clearly understand what API testing means. -Learn about best practices. -See demonstrations of popular testing tools. -See API and UI/UX testing implemented as part of a Jenkins build.

Otto MVP Presentation

jeeves24

The document discusses Otto, an autograding platform created by Mark Isaacson, Ben Mehne, and Rajeev Vadhavkar. It outlines that setting up an autograder is difficult but setting up Otto is easy. Using an autograder is also difficult as it involves repeatedly uploading and checking submissions, but using Otto simplifies the process and allows viewing results in real time. The document concludes with a demo and discusses upcoming features like Cosign login and supporting multiple programming languages.

Sane Plugin Updates - WordCamp New York City, 2014

Pippin Williamson

This document provides tips and best practices for updating WordPress plugins, including releasing beta versions, tagging releases, using version control, writing clear change logs, tracking issues, releasing often, using deploy scripts, including auto-updaters, and thanking contributors. Key steps outlined are releasing beta versions for testing, tagging releases in version control, writing detailed change logs, tracking bugs and features leading up to a release, and including automatic updating capabilities in commercial plugins.

Belajar Postman test runner

Fachrul Choliluddin

This document discusses various types of API testing including functionality, usability, reliability, load, creativity, security, proficiency, and documentation testing. It provides two examples of API tests - one to test getting a list of countries and another to test getting details of a single country. Key aspects covered include generating test data, preparing variables, using prepared variables in tests, running test collections, and reviewing test results. The overall document provides guidance on developing comprehensive API tests.

10x Test Coverage, Less Drama: Shift Left Functional & Performance Testing

Sauce Labs

Shifting left means starting testing earlier in the development cycle by writing tests alongside code development within small teams. This eliminates surprises from late-discovered problems and ensures code meets expectations before being declared "done". To achieve superior test coverage, teams must test more by shifting left and testing as code is committed so developers get immediate feedback and bugs are fixed early. Shifting left embeds quality into every step of development and allows for continuous testing and integration to produce higher quality, shippable features faster.

Automate REST API Testing

TechWell

As an organization grows, the body of code that needs to be regression tested constantly increases. However, to maintain high velocity and deliver new features, teams need to minimize the amount of manual regression testing. Eric Smith shares his lessons learned in automating RESTful API tests using JMeter, RSpec, and Spock. Gain insights into the pros and cons of each tool, take back practical knowledge about the tools available, and explore reasons why your shop should require RESTful automation as part of its acceptance test criteria. Many decisions must be made to automate API tests: choosing the platform; how to integrate with the current build and deploy process; and how to integrate with reporting tools to keep key stakeholders informed. Although the initial transition caused his teams to bend their traditional roles, Eric says that ultimately the team became more cross-functionally aligned and developed a greater sense of ownership for delivering a quality product.

How to Automate API Testing

Bruno Pedro

Production - Designing for Testability

Michael Bryzek

The document discusses designing software for testability in production. It recommends removing staging environments and running automated tests and a subset of code in production to gain confidence in software quality. Specific techniques include using sandbox accounts to test functionality without affecting real users, running integration tests that create and delete sandbox environments, and monitoring databases and logs in real-time to detect issues. Designing systems with isolation, well-defined interfaces, and the ability to restrict access and trace effects can help make testing in production safer and more effective. Tools like API documentation generators and mocks can also help improve quality.

Git workflow step by step

Binh Quan Duc

This document outlines the Git workflow steps for developers, team leads, testers, and quality managers. It involves: 1. Creating issues and a develop branch for new features. 2. Developers create feature branches from develop and add commits with reviews. 3. Pull requests are made from feature branches to develop, which are reviewed and merged by the team lead. Key steps include code reviews, testing, creating release branches and tags, and reverting changes if live issues occur. The workflow aims to integrate quality control throughout the development process.

CI/CD 101

djdule

The document discusses continuous integration (CI) and continuous delivery (CD), which are software engineering practices. It recommends ways to implement CI/CD, including creating a single source of truth repository, enabling on-demand environment creation, making infrastructure easier to rebuild than repair, modifying the definition of done, and amplifying feedback through automated testing and logging.

Continuous delivery - tools and techniques

Mike McGarr

A Second Look at Unit Testing by Roy Osherove

Roy Osherove

40 square's git workflow

Ruben Tan

This document summarizes a software company's migration from Mercurial to Git for source control and their new workflow using Git. They implemented Vincent Driessen's branching model with long-running branches for master, staging, and development. Developers work in their own forks, rebase regularly, and submit pull requests to integrators for review and merging into staging or development. This standardized process aims to reduce merge conflicts and enable predictable integration and deployment between branches.

Speed up your regression and reduce cost load with Selenoid + K8s + ReportPortal

Danylo Kuvshynov

4 Major Advantages of API Testing

QASource

Build pipelines with TeamCity

Anton Arhipov

TeamCity is a great tool for Continuous Integration with a lot of advanced features provided out-of-the-box. In this session, we will go through how TeamCity helps the software development with the daily routine; what was added to the product in the latest releases; and what features are coming next. You will learn why build pipelines are useful, and how the CI server can be optimized when properly configured. I will also demonstrate how to configure the builds using the special Kotlin DSL provided with TeamCity.

Build pipelines with TeamCity and Kotlin DSL

Anton Arhipov

- TeamCity allows building software projects and managing build pipelines for continuous integration and delivery (CI/CD) - A build pipeline in TeamCity refers to the sequence of build steps such as compiling code, running tests, and deploying artifacts that are automatically triggered by code changes - The document demonstrates how to define a build pipeline in TeamCity using Kotlin DSL that compiles and packages a Java application project and its dependency library project

What's hot

Software development terminology

jstack

Testing, CI and CD in the real world

Roc Boronat

Speed up your Titanium app development with automated tests - TiConf EU 2014

Emanuele Rampichini

Continuous delivery of your legacy application

ColdFusionConference

DockerCon'15: Shipping Containers to Enterprise Customers

Weihan Wang

An Introduction To Automated API Testing

Sauce Labs

Otto MVP Presentation

jeeves24

Sane Plugin Updates - WordCamp New York City, 2014

Pippin Williamson

Belajar Postman test runner

Fachrul Choliluddin

10x Test Coverage, Less Drama: Shift Left Functional & Performance Testing

Sauce Labs

Automate REST API Testing

TechWell

How to Automate API Testing

Bruno Pedro

Production - Designing for Testability

Michael Bryzek

Git workflow step by step

Binh Quan Duc

CI/CD 101

djdule

Continuous delivery - tools and techniques

Mike McGarr

A Second Look at Unit Testing by Roy Osherove

Roy Osherove

40 square's git workflow

Ruben Tan

Speed up your regression and reduce cost load with Selenoid + K8s + ReportPortal

Danylo Kuvshynov

4 Major Advantages of API Testing

QASource

What's hot (20)

Software development terminology

Testing, CI and CD in the real world

Speed up your Titanium app development with automated tests - TiConf EU 2014

Continuous delivery of your legacy application

DockerCon'15: Shipping Containers to Enterprise Customers

An Introduction To Automated API Testing

Otto MVP Presentation

Sane Plugin Updates - WordCamp New York City, 2014

Belajar Postman test runner

10x Test Coverage, Less Drama: Shift Left Functional & Performance Testing

Automate REST API Testing

How to Automate API Testing

Production - Designing for Testability

Git workflow step by step

CI/CD 101

Continuous delivery - tools and techniques

A Second Look at Unit Testing by Roy Osherove

40 square's git workflow

Speed up your regression and reduce cost load with Selenoid + K8s + ReportPortal

4 Major Advantages of API Testing

Similar to DevOpsDaysRiga 2018: Anton Arhipov - Build pipelines with TeamCity

Build pipelines with TeamCity

Anton Arhipov

Build pipelines with TeamCity and Kotlin DSL

Anton Arhipov

How do you implement Continuous Delivery? Part 3: All about Pipelines

ThoughtWorks Studios

Concource CI/CD

Knoldus Inc.

Let’s start Continuous Integration with jenkins

Tomohide Kakeya

Scaling pipelines

GeekNightHyderabad

Pipeline based deployments on Jenkins

Knoldus Inc.

Knolx _ Concourse

Knoldus Inc.

Concourse CI is an open-source pipeline-based CI/CD system built to scale complex automation pipelines using containers. It uses resources, tasks, and jobs to define automation workflows. Key features include configuring pipelines as code, visualizing pipelines, running builds in containers for reproducibility, and integrating with other tools via pluggable resources. The presentation demonstrated setting up Concourse using the Fly CLI, defining a sample pipeline in YAML, and triggering jobs.

QConSP 2014 - Continuous Delivery - Part 03 - Continuous Integration

Rodrigo Russo

The document discusses principles of continuous integration including version control, automation, and testing. It describes a basic continuous integration/continuous delivery (CI/CD) pipeline with stages for committing code, compiling, testing, and deploying to environments like acceptance, capacity, and production. Jenkins is presented as a tool for implementing CI/CD pipelines through automated jobs that can pull code, build, test, analyze, and deploy software.

Continuous Delivery with Chef and GoCD

Aroj George

In my last project, I led the team that setup the Continuous Delivery infrastructure for the product marketing and publishing platform of a major consumer electronics giant. This platform was based on Scala and the Play framework and used a non-blocking architecture to achieve scale. Here, I want to share some of the key highlights of this project from a Devops and Continuous Delivery point of view. Read more here: http://arojgeorge.ghost.io/a-continuous-delivery-example/ Video @ https://youtu.be/tPcmnx6UOlw

Migrating to Continuous Delivery with TFS 2017 - Liviu Mandras-Iura

ITCamp

The presentation will talk about Continuous Delivery best practices and how one can migrate from not doing CI/CD at all to a proper CD process while acknowledging that there are so much many intermediary states that still bring value. The presentation will have the main focus on the journey from one state to the other infused with the speaker’s own experience on the process. There will be a showcase of a demo project that will exemplify how to implement a simple automated deployment pipeline using TFS 2017. This will show the general capabilities of TFS 2017 which is now quite a capable tool as opposed to previous versions. The presentation will target Architects, Team Leads, DevOps engineers or anyone that has to implement Continuous Integration/Delivery practices in a team.

Manchester Expert Talks (April 2017) - Breaking Down Your Build: Architectura...

Abraham Marin-Perez

Azure CICD - Day1.pptx

UiPathCommunity

This document provides information about a webinar on CI/CD pipelines for UiPath process deployment using Azure DevOps. The webinar will include introductions to Azure DevOps and setting up a UiPath environment with it, building CI/CD pipelines for UiPath automation, and a demo. It defines CI/CD and discusses how it applies to RPA tool UiPath. It also outlines the key components of Azure pipelines like triggers, jobs, stages, and artifacts. Finally, it mentions there will be hands-on configurations of agents and creating pipelines and releases in Azure DevOps.

How to set up an ASP.NET 5 Continuous Delivery Pipeline using IBM Bluemix Dev...

Richard Johansson

The document provides instructions for setting up a Continuous Delivery pipeline in IBM Bluemix for an ASP.NET 5 application using IBM DevOps Services. Key steps include: 1. Configuring four stages in the Delivery Pipeline - Build, Test, Staging, and Production. 2. Setting up the Build stage to manually build and run unit tests of the ASP.NET application. 3. Adding a Test stage to run integration tests against a Cloudant database. 4. Configuring the Staging and Production stages to deploy the application to Bluemix environments for testing and production. The instructions explain how to set up each stage of the pipeline, including adding necessary jobs, scripts, dependencies and credentials

MOPCON 2015 - Tips of Mobile Continuous Delivery

anistar sung

Continous integration and delivery for single page applications

Sunil Dalal

OpenShift-Build-Pipelines: Build -> Test -> Run! @JavaForumStuttgart

Tobias Schneck

Stabile und skalierbare Continuous-Integration-Umgebungen sind seit jeher schwer aufzusetzen und zu pflegen. Besonders in Zeiten von Containern und Cloud-Native-Apps, wird der nächste Schritt hin zur voll-automatisierten Build-Pipeline eingefordert. Sowohl der Aufbau des automatisierten Deployments als auch die Ausführung von automatisierten Integration- und UI-Tests stellen die DevOps-Teams vor neue Hürden. Einen eleganten Ausweg bieten Container-basierte CI/CD-Umgebungen, die dynamisch zum Build-Zeitpunkt bereitgestellt werden. An diesen Punkt setzt die Open-Source-Container-Plattform "OpenShift" an. Durch den Infrastructure-as-Code-Ansatz wird sowohl der CI-Server als auch der komplette Build-Lifecycle vom Bau der Artefakte bis zum Testen der Anwendung in den Container-Cluster verschoben. Der Talk zeigt auf wo die Unterschiede von OpenShift zur Kubernetes-API liegen, wie durch Jenkins-Build-Pipelines Artefakte gebaut, in Docker Images verpackt, getestet und deployed werden können. In mehreren Live-Demos wird aufgezeigt, wie mit geschickten Einsatz von Open-Source-Tools sowohl Server-APIs als auch grafische Web- und Rich-Client-Oberflächen in Container-Clustern als Black-Box getestet werden können. Eine abschließende, kritische Bewertung der gesammelten Erfahrungen, zeigt wo das Potenzial dieses Ansatz liegt, aber auch welche Fallstricke derzeit (noch) zu meistern sind.

Enterprise E-commerce Webinar Series, Episode 2: Deploying and Monitoring You...

Kin Lane

Note: This webinar is the second in Postman's three-part webinar series on implementing an API-first strategy in enterprise e-commerce. The series, hosted by Postman Chief Evangelist Kin Lane, will walk you through key topics and how-to content via a hypothetical e-commerce enterprise, Union Fashion (see it on GitHub). Continuing with our series, the second webinar will dive into actually deploying and monitoring an API using the Postman platform. We will take the API we developed as part of our previous API-first webinar, and actually bring it to life by focusing on the following areas: - Versions - Monitors - Mocks - Environment - Documentation - Feedback Loops The full video for this session can be found at: https://www.youtube.com/watch?v=jO2M_kqb-jo&t=1659s

CICD Pipeline - AWS Azure

Ratan Das

Continous Delivery Toronto Presentation

XebiaLabs

This document discusses continuous deployment with Jenkins. It begins with introductions and defines continuous integration as continuously building and testing software. It then discusses moving beyond CI to continuous delivery by automating deployment and testing on target platforms. Common enterprise challenges to continuous delivery are outlined such as standardizing jobs, access control, and handling different environments. A sample continuous delivery pipeline is presented with stages like build, test, deploy. Finally, 5 steps are provided to work towards continuous delivery, such as defining the pipeline extent and automating triggers.

Similar to DevOpsDaysRiga 2018: Anton Arhipov - Build pipelines with TeamCity (20)

Build pipelines with TeamCity

Build pipelines with TeamCity and Kotlin DSL

How do you implement Continuous Delivery? Part 3: All about Pipelines

Concource CI/CD

Let’s start Continuous Integration with jenkins

Scaling pipelines

Pipeline based deployments on Jenkins

Knolx _ Concourse

QConSP 2014 - Continuous Delivery - Part 03 - Continuous Integration

Continuous Delivery with Chef and GoCD

Migrating to Continuous Delivery with TFS 2017 - Liviu Mandras-Iura

Manchester Expert Talks (April 2017) - Breaking Down Your Build: Architectura...

Azure CICD - Day1.pptx

How to set up an ASP.NET 5 Continuous Delivery Pipeline using IBM Bluemix Dev...

MOPCON 2015 - Tips of Mobile Continuous Delivery

Continous integration and delivery for single page applications

OpenShift-Build-Pipelines: Build -> Test -> Run! @JavaForumStuttgart

Enterprise E-commerce Webinar Series, Episode 2: Deploying and Monitoring You...

CICD Pipeline - AWS Azure

Continous Delivery Toronto Presentation

More from DevOpsDays Riga

DevOpsDaysRiga 2017: Mark Smalley - Kill DevOps

DevOpsDaysRiga 2018: Anton Arhipov - Build pipelines with TeamCity

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to DevOpsDaysRiga 2018: Anton Arhipov - Build pipelines with TeamCity

Similar to DevOpsDaysRiga 2018: Anton Arhipov - Build pipelines with TeamCity (20)

More from DevOpsDays Riga

More from DevOpsDays Riga (20)

Recently uploaded

Recently uploaded (20)

DevOpsDaysRiga 2018: Anton Arhipov - Build pipelines with TeamCity