Build pipelines with TeamCity

Oct 7, 20181 like1,583 views

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
@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

В докладе я расскажу, как был организован запуск автоматических тестов (appium/javascript) в gitlab CI для нативного Android приложения на каждый Merge Request. Опишу, как можно встроить автотесты в существующий процесс сборки, как правильно настроить запуск тестов в docker image (тесты бегут в TestObject облаке), как произошла интеграция с клаудом и какие результаты это принесло. Tech stack: Gitlab CI, kubernetes, android, appium, javascript, testobject.

Wax on, wax offBol.com Techlab

Testing MicroservicesNathan Jones

At Findly we know test automation is key for continuous delivery. However, in the context of a microservices architecture, our monolithic end-to-end test suites have still been limiting our ability to achieve a truly "continuous" pace of delivery. This talk will explain the principles, processes and techniques we are now using to build test suites for microservices and enable continuous delivery at Findly. Presented at Auckland Continuous Delivery meetup, May 2016 (http://www.meetup.com/Auckland-Continuous-Delivery/events/230864194/).

Roman Iovlev. Comaqa Spring 2018. Архитектура Open Source решений для автомат...COMAQA.BY

Мы поговорим о новых возможностях Open Source фреймворка JDI для Автоматизации UI Тестирования и не только на языках Java, C# .Net и Python. Архитектор проекта расскажет «всю правду» о своем детище, а мы послушаем, сделаем выводы и, возможно, используем это решение для нашего следующего проекта.

Beautiful Builds - Roy Osherove at Microsoft SwitRoy Osherove

The Road to Continuous Delivery - JAX DevOps 2018Tommy Tynjä

Follow on a journey about how a successful Swedish company revamped their organization to implement a completely new distributed system running on the Java platform and using Continuous Delivery. Today, autonomous development teams can push code to production as frequently as they like with fully automated delivery pipelines. We take a look at high-performing teams, their ways-of-working, and the technologies used to deliver quality software at a high pace. We also take a look at the future and what challenges lie ahead. Presented at JAX DevOps & Finance, London, United Kingdom on April 10th 2018.

A Second Look at Unit Testing by Roy OsheroveRoy Osherove

Otto MVP Presentationjeeves24

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.

Integration Testing with Docker Containers with DockerComposeMike Holdsworth

Belajar Postman test runnerFachrul 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.

RESTful API Testing using Postman, Newman, and JenkinsQASymphony

INCLUDE AUTOMATED RESTFUL API TESTING USING POSTMAN, NEWMAN, AND JENKINS If you’re going to automate one kind of tests at your company, API testing is the perfect place to start! It’s fast and simple to write as well as fast to execute. If your company writes an API for its software, then you understand the need and importance of testing it. In this webinar, we’ll do a live demonstration of how you can use free tools, such as Postman, Newman, and Jenkins, to enhance your software quality and security. Elise Carmichael will cover: Why your API tests should be included with your CI Real examples using Postman, Newman and Jenkins + Newman An active Q&A where you can get your automated testing questions answered, live! To get the most out of this session: Download these free tools prior to the webinar: Postman, Newman (along with node and npm) and Jenkins Read up on how to parse JSON objects using javascript *Can’t attend the webinar live? Register and we will send the recording after the webinar is over.

How to Automate API TestingBruno Pedro

Delivery With Chef - ChefConf 2015 Chef

Product update aug_29🌍 Job van der Voort

The document outlines new features and improvements for versions 9.5, 10.0, and beyond of an unnamed product. Version 9.5 focuses on commit verification, navigation improvements, and project templates. Version 10.0 introduces group issue boards, high availability for servers, and integration with JIRA. Future versions will include portfolio management, high availability, disaster recovery, continuous delivery, and authentication improvements.

PostmanIgor Shubovych

Postman is an API development tool that allows users to design, manage, run, test, document, and share APIs. It provides features like request building, documentation, environments, test automation, and collaboration. Alternatives include Paw, Insomnia, command line tools like cURL, and services from Apigee and Apiary. The document recommends using any tool that helps share APIs, especially for complex projects and team collaboration.

4 Major Advantages of API TestingQASource

20180828 QA meetupSadaaki Emura

Build Automation in AndroidAngelo Rüggeberg

This document discusses build automation for mobile applications. It recommends using Jenkins for continuous integration to run tests and analyze code quality after each code push. The document outlines a sample build pipeline in Jenkins that would compile, run linting, tests, static analysis with Sonar, and monkey testing before distributing builds. It also discusses using Git, Git Flow, Gradle flavors for testing, and services like Crashlytics for beta distribution to reliably deliver high quality apps. Frequent testing, code analysis, and build automation are emphasized to catch issues early and ensure only stable releases are distributed.

API Test Automation Using Karate (Anil Kumar Moka)Peter Thomas

Jenkins as the Test Reporting FrameworkNitin Sharma

Test Reporting Framework are the ultimate utilities reached by very few companies in the world likes of google & facebook. It require significant investment in terms money and resources. To optimize on both we tried the approach of extending Jenkins for the same purpose. We like to share our experiences with respect to this journey. We will talk about different cahllenges we faced in doing so and how we solved them. We strongly believe that other startup can use our experience and get benefit from this immensely.

Api TestingVishwanath KC

This document provides an overview of API testing tools and methods. It defines APIs and REST, describes how API testing works, lists common API testing tools like Postman, and outlines different types of API tests including functionality, reliability, load, and security testing. Examples are given of the GET, POST, PUT, and DELETE HTTP methods along with response status codes. A live demo of an API is presented at the end.

API Testing: The heart of functional testing" with Bj RollisonTEST Huddle

View webinar: http://www.eurostarconferences.com/community/member/webinar-archive/webinar-81-api-testing-the-heart-of-functional-testing An API, or Application Programming Interface, is a collection of functions that provide much of the functional capabilities in complex software systems. Most customers are accustomed to interacting with a graphical user interface on the computer. But, many customers do not realize the much of the functionality of a program comes from APIs in the operating system or program's dynamic-link libraries (DLL). So, if the business logic or core functionality is exposed via an API call then and if we want to find functional bugs sooner than API testing may be an approach that provides additional value in your overall test strategy. Additionally, API testing can start even before the user interface is complete so functional capabilities can be tested while designers are hashing out the "look and feel." API testing will not replace testing through the user interface, but it can augment your test strategy and provide a solid foundation of automated tests that increase your confidence in the functional quality of your product.

Continuous delivery from the trenchesMichael Medin

Automation testing API in JavaWix.com

This document discusses automating API testing in Java. It covers key topics like what an API is, different types of web services like SOAP and REST, how HTTP works with request methods and status codes, and different approaches to API testing including using software, command line tools, and programming. API testing ensures proper functioning of application programming interfaces and is important for machine-to-machine communication.

Continuous testingBrandon Raines

Build pipelines with TeamCityAnton 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 TeamCityAnton 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.

Build pipelines with TeamCity and Kotlin DSLAnton 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

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

More Related Content

What's hot (18)

Otto MVP Presentationjeeves24

Integration Testing with Docker Containers with DockerComposeMike Holdsworth

Belajar Postman test runnerFachrul Choliluddin

RESTful API Testing using Postman, Newman, and JenkinsQASymphony

How to Automate API TestingBruno Pedro

Delivery With Chef - ChefConf 2015 Chef

Product update aug_29🌍 Job van der Voort

PostmanIgor Shubovych

4 Major Advantages of API TestingQASource

20180828 QA meetupSadaaki Emura

Build Automation in AndroidAngelo Rüggeberg

API Test Automation Using Karate (Anil Kumar Moka)Peter Thomas

Jenkins as the Test Reporting FrameworkNitin Sharma

Api TestingVishwanath KC

API Testing: The heart of functional testing" with Bj RollisonTEST Huddle

Continuous delivery from the trenchesMichael Medin

Automation testing API in JavaWix.com

Continuous testingBrandon Raines

Otto MVP Presentationjeeves24

Integration Testing with Docker Containers with DockerComposeMike Holdsworth

Belajar Postman test runnerFachrul Choliluddin

RESTful API Testing using Postman, Newman, and JenkinsQASymphony

How to Automate API TestingBruno Pedro

Delivery With Chef - ChefConf 2015 Chef

Product update aug_29🌍 Job van der Voort

PostmanIgor Shubovych

4 Major Advantages of API TestingQASource

20180828 QA meetupSadaaki Emura

Build Automation in AndroidAngelo Rüggeberg

API Test Automation Using Karate (Anil Kumar Moka)Peter Thomas

Jenkins as the Test Reporting FrameworkNitin Sharma

Api TestingVishwanath KC

API Testing: The heart of functional testing" with Bj RollisonTEST Huddle

Continuous delivery from the trenchesMichael Medin

Automation testing API in JavaWix.com

Continuous testingBrandon Raines

Similar to Build pipelines with TeamCity (20)

Build pipelines with TeamCityAnton Arhipov

Build pipelines with TeamCity and Kotlin DSLAnton Arhipov

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

Concource CI/CDKnoldus Inc.

Let’s start Continuous Integration with jenkinsTomohide Kakeya

Scaling pipelinesGeekNightHyderabad

Pipeline based deployments on JenkinsKnoldus Inc.

Knolx _ ConcourseKnoldus 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 IntegrationRodrigo 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 GoCDAroj 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-IuraITCamp

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.pptxUiPathCommunity

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 Deliveryanistar sung

OVerview of Jenkins - A WIP pPT that needs to be refinedremoved_7e30d0915f14b559919f338a71e486d1

Continous integration and delivery for single page applicationsSunil Dalal

OpenShift-Build-Pipelines: Build -> Test -> Run! @JavaForumStuttgartTobias 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

Build pipelines with TeamCityAnton Arhipov

Build pipelines with TeamCity and Kotlin DSLAnton Arhipov

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

Concource CI/CDKnoldus Inc.

Let’s start Continuous Integration with jenkinsTomohide Kakeya

Scaling pipelinesGeekNightHyderabad

Pipeline based deployments on JenkinsKnoldus Inc.

Knolx _ ConcourseKnoldus Inc.

QConSP 2014 - Continuous Delivery - Part 03 - Continuous IntegrationRodrigo Russo

Continuous Delivery with Chef and GoCDAroj George

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

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

Azure CICD - Day1.pptxUiPathCommunity

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

MOPCON 2015 - Tips of Mobile Continuous Deliveryanistar sung

OVerview of Jenkins - A WIP pPT that needs to be refinedremoved_7e30d0915f14b559919f338a71e486d1

Continous integration and delivery for single page applicationsSunil Dalal

OpenShift-Build-Pipelines: Build -> Test -> Run! @JavaForumStuttgartTobias Schneck

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

More from Anton Arhipov (20)

JavaZone 2022 - Building Kotlin DSL.pdfAnton Arhipov

The document discusses Kotlin DSL and provides examples of using Kotlin as a domain specific language. It demonstrates how to build type-safe builders using Kotlin, including defining DSL blocks, extension functions and properties, infix notation, lambda receivers, and context receivers to define internal and external DSLs. Code samples are provided of building clients and dates using DSL syntax and context requirements.

Idiomatic kotlinAnton Arhipov

TechTrain 2019 - (Не)адекватное техническое интервьюAnton Arhipov

Devoxx Ukraine 2018 - Kotlin DSL in under an hourAnton Arhipov

GeeCON Prague 2018 - Kotlin DSL in under an hourAnton Arhipov

JavaDay Kiev 2017 - Integration testing with TestContainersAnton Arhipov

This document introduces TestContainers, an open source Java library that supports integration testing for applications that depend on external resources like databases. It allows tests to use real Docker containers to manage these dependent services. Tests run quickly and are portable across environments because the containers are started and stopped for each test. The document provides examples of using TestContainers with Spring Boot tests to launch containers for PostgreSQL and Redis, and to configure a MockServer container to handle external API dependencies. It suggests TestContainers is useful for testing microservices and Java agents that depend on external services or APIs.

GeeCON Prague 2017 - TestContainersAnton Arhipov

JavaOne 2017 - The hitchhiker’s guide to Java class reloadingAnton Arhipov

This document discusses different techniques for reloading Java classes at runtime: - HotSwap allows reloading individual statements but is limited. Class loaders allow reloading entire classes but each class loader isolates its classes. - More advanced techniques like Java agents and bytecode instrumentation allow redefining classes in-place and reloading methods, fields, and class hierarchies in a binary-compatible way. - Demonstrations show reloading an entire "region" of related classes like a service class and its dependencies, allowing a live application thread to see the changes immediately without restarts. Java agents in particular provide a powerful but complex way to implement class reloading.

JavaOne 2017 - TestContainers: integration testing without the hassleAnton Arhipov

This document introduces TestContainers, an open source tool for running Docker containers as part of integration tests. It discusses why integration testing is important for reproducibility, isolation, and realism. TestContainers allows setting up Docker containers programmatically and automatically cleaning them up after tests complete. It supports starting individual containers, Docker Compose environments, and custom container types. Examples are given for testing services that depend on databases, caches, and external APIs using TestContainers without complex test environment configuration. The document also describes how to use TestContainers to test Java agents by modifying bytecode at runtime within a container during tests.

JavaOne 2017 - The hitchhiker’s guide to Java class reloadingAnton Arhipov

In Java, a typical workflow involves restarting the application with (almost) every class change. For some applications, it is not a problem at all; for others, it is a disaster, from HotSwap to agent-based reloading. This session takes a look at the options available for Java class reloading. There are plenty of tools you can use for this task: rely on standard JVM HotSwap, redesign your application to rely on dynamic class loaders, comprehend the Zen of OSGi, or integrate a reloading agent. Every option has its own drawbacks and benefits, and the presentation takes a deep dive into the subject. Come get a better understanding of class reloading technologies and become a more productive Java developer.

JavaZone 2017 - The Hitchhiker’s guide to Java class reloadingAnton Arhipov

This document discusses techniques for reloading Java classes at runtime, including using class loaders to load updated classes, Java agents to instrument classes, and frameworks like HotSwap that utilize these techniques. It provides examples of how class loaders can be used to reload specific parts of an application while a program is running. The goal is to achieve hot reloading that is binary compatible and allows updating code without restarting the Java virtual machine.

JUG.ua 20170225 - Java bytecode instrumentationAnton Arhipov

Riga DevDays 2017 - The hitchhiker’s guide to Java class reloadingAnton Arhipov

This document discusses techniques for reloading Java classes at runtime, known as hot reloading or hot swapping. It begins with an introduction and overview of class loaders, Java agents, and instrumentation which can be used to dynamically modify classes. Specific techniques are then presented for reloading classes, fields, methods and code using custom class loaders and bytecode manipulation. The goal is to allow reloading parts of an application without restarting the Java Virtual Machine.

GeeCON 2017 - TestContainers. Integration testing without the hassleAnton Arhipov

JEEConf 2017 - The hitchhiker’s guide to Java class reloadingAnton Arhipov

In Java, a typical workflow involves restarting the application (almost) with every class change. For some applications it is not a problem at all, for some – it is a disaster. From HotSwap to agent-based reloading. In this session, we are going to take a look at the options available for Java class reloading. There is plenty of tools that you can use for this task: rely on standard JVM HotSwap, redesign your application to rely on dynamic class loaders, to comprehend the Zen of OSGi, or to integrate a reloading agent. Every option has its own drawbacks and benefits and we’re going to take a deep dive on the subject. Finally, there are also the conceptual challenges in reloading Java classes. What to do with the state? What should happen with the static initialisers? What if super class changes? Join this session to gain a better understanding of class reloading technologies and become more productive Java developer.

JEEConf 2017 - Having fun with JavassistAnton Arhipov

Javassist makes Java bytecode manipulation simple. At ZeroTurnaround we use Javassist a lot to implement the integrations for our tools. In this talk we will go through the examples of how Javassist can be applied to alter the applications behavior and do all kind of fun stuff with it. Why is it interesting? Because while trying to do unusual things in Java, you learn much more about the language and the platform itself and learning about Javassist will actually make you a better Java developer!

Devclub 01/2017 - (Не)адекватное Java-интервьюAnton Arhipov

Joker 2016 - Bytecode 101Anton Arhipov

JPoint 2016 - Etudes of DIY Java profilerAnton Arhipov

JPoint 2016 - BytecodeAnton Arhipov