Continuous Delivery su progetti Java: cosa abbiamo imparato facendoci del male

•

2 j'aime•579 vues

In questa presentazione io e Paolo D'Incau condividiamo esperienze reali tratte da progetti dove applichiamo pratiche di Continous Delivery. Raccontiamo di come si può far evolvere iterativamente una pipeline partendo da semplici task (build e deploy mono-ambiente) fino ad arrivare ad unica pipeline multi-ambiente ispirata allo stato dell'arte e alle lezioni che abbiamo imparato facendoci del male. Forniamo esempi concreti, focalizzandoci sugli aspetti relativi al codice, all'infrastruttura e rapporto con gli stakeholders. Autori: Paolo D'Incau, Pietro Di Bello

Technologie

Continuous
Delivery
in Java
Cose che abbiamo imparato
facendoci del male
Codemotion Milano ‘15

“Continuous Delivery is a software development discipline where you
build software in such a way that the software can be released to
production at any time.”
Martin Fowler*
* martinfowler.com/bliki/ContinuousDelivery.html

“Continuous Delivery is nothing more than reducing the
stress you get when you deliver business value to the customer ”
My Team*
* Come and ask!

Deploy any specific working version to
production with confidence

No tests
Manual deploy
Snowflake environments
Non predictable outcome
Few or very little collaboration

Fast Feedback
Done is released
Shared responsibility
Everything is automated
Repeatable and reliable process

Previous deployment process was painful
Database continuously change
Different environments

Environment replica on AWS
Manual build
Manual DB migrations
Deploy with scp to remote JBoss

No automation at all
When was our last deploy?

Set up a basic Jenkins installation
Test and build triggered on push
DB migration using Liquibase
Task to deploy on AWS

Errors in MyBatis DB mappers
Wrong/Missing wirings

New Jenkins job to run integration tests
Track slowest tests
First official deploy an all environments

Incorrect use of mvn profiles
N-builds for N-environments
Long build and deploy time

Got rid of configurations using JBoss
*Unique* artefact for all environments
Deploy version X.Y.Z from Nexus

But QA were not so happy
Branches, branches everywhere!

An environment for QA
Tags over branches
Track deployed version

Explained values and
motivations to Product Owner

Remove Candidate
Clean Up
Clean Up
Build it...
Migrate
!
Database
Fetch
Unit Tests
Build
Build
Integration Test
!
Integration
Deploy
Publish
UAT
QA and Publish

Frontend Angular
!
Web
...and deliver it
Deploy ESB
!
ESB
Deploy staging
!
Deploy Staging
Deploy API
Deploy Core
Backend
Migrate
!
Database

Parallelization
Environments Provisioning
Jenkins under git
Squash migrations to snapshot

Pipeline with “placeholders”
Extract configurations asap
Explain at the beginning the values behind

Build the pipeline iteratively
Share pipeline responsibility
Use the tool that best fit your needs

Take a look at these
Real-World Strategies for Continuous Delivery
with Maven and Jenkins
https://www.youtube.com/watch?v=McTZtyb9M38
Visualizations of Continuous Delivery
http://continuousdelivery.com/2014/02/visualizations-of-continuous-delivery/

https://creativecommons.org/licenses/by-nc-sa/3.0/
Thanks!

Contenu connexe

Tendances

What does it mean to 'do' Continuous Integration? It used to be enough to execute your unit tests in CI. But the bar is steadily raising for engineering practices. In the last decade we've seen tremendous improvements inacceptance testing. JavaScript is now a platform in it's own right. Cloudcomputing is now vital. There's growing interest in deployment to prod.So Continuous Integration is under more pressure than ever. As the bar slowly raises for engineering practices, we ll present 2011's minimum viable feature set for Continuous Integration

Continuous Integration, the minimum viable product

Julian Simpson

Continuous Integration, Build Pipelines and Continuous Deployment

Christopher Read

Configuration as Code in Bamboo

Atlassian

e2e testing with cypress

Tomasz Bak

Continuous integration

hugo lu

Continuous Integration at T3CON08

Sebastian Kurfürst

Just kill it

pwhitdog

Introducing Continuous Delivery practices to a team in trouble can be daunting. Where do you start ? What do you do first ? Which battle do you pick first ? I’ll share my experience of guiding a team to achieve a higher degree of delivery maturity. This is a journey from a troublesome, struggling start of chaotic manual deployments, merge hell, regular production roll backs and lost code, to deliver a single commit to trunk automatically and reliably, under an hour, many times a day.

Merge hells!! feature toggles to the rescue

Leena N

Walking Skeleton

hepphep

In this SauceCon 2019 presentation, Mario describes the practices that ABN AMRO adopted in mobile teams when it comes to testing native applications on real devices. Since using Espresso and XCUITest is still relatively uncommon for large apps and there are various unique challenges due to being in an EU-regulated industry with various security restrictions, Mario will share the ABN AMRO team’s experiences, including: - A brief architectural overview of the Mobile Banking app: why it is all native (Objective-C/Swift and Java/Kotlin), how it communicates with other apps and websites - Why ABN AMRO choose to adopt Espresso and XCUITest: the advantages and the limitations of this choice - How ABN AMRO runs their test pipelines to spread them across time and devices and prevent teams from being blocked

Closer To the Metal - Why and How We Use XCTest and Espresso by Mario Negro P...

Sauce Labs

Sencha Roadshow 2017: Sencha Upgrades - The Good. The Bad. The Ugly - Eva Luc...

Sencha

Sencha Roadshow 2017: What's New in Sencha Test

Sencha

Agile Testing

Sargis Sargsyan

Dockerizing react app

Malang QA Community

Cypress report

Adarsh

End to end test automation with cypress

Kushan Shalindra Amarasiri - Technical QE Specialist

Continuous integration / deployment can be a daunting task. Especially if you are a team of one, or one among a small team. TeamCity is "continuous integration for everyone" It's a self hosted CI build server that is highly customizable for just about any project. I've built RocketFuel's CI/CD system on a spare box with TeamCity and customized it to handle legacy PHP applications and modern framework based projects. We'll cover install and configuration and all of the flexibility of setting up projects at that build, test, report errors, and trigger deployments for various application scenarios.

Continuous Integration: How I stopped guessing if that merge was bad

Joe Ferguson

2014 was the year of Docker. The container-based world exploded on the scene with the promise to reinvent how you think about distributed applications. But is it just hype or are there immediate benefits to be realized? Join us to explore Continuous Integration/Continuous Delivery leveraging containers, one of the early use cases proving successful with Docker, resulting in reduced Dev/Test cycle times and lower infrastructure costs. We'll walk through the end-to-end CI/CD workflow, highlighting the big wins containers have introduced, as well as discuss common challenges to avoid. Lastly, we'll look ahead, identifying the next set of use cases to likely achieve real-world benefits from containers.

Modern devOps with Docker

Avi Cavale

Continuous integration

Andrey Zhupanenko

Continuous Integration - What even is it?

Rob Jacoby

Tendances (20)

Continuous Integration, the minimum viable product

Continuous Integration, Build Pipelines and Continuous Deployment

Configuration as Code in Bamboo

e2e testing with cypress

Continuous integration

Continuous Integration at T3CON08

Just kill it

Merge hells!! feature toggles to the rescue

Walking Skeleton

Closer To the Metal - Why and How We Use XCTest and Espresso by Mario Negro P...

Sencha Roadshow 2017: Sencha Upgrades - The Good. The Bad. The Ugly - Eva Luc...

Sencha Roadshow 2017: What's New in Sencha Test

Agile Testing

Dockerizing react app

Cypress report

End to end test automation with cypress

Continuous Integration: How I stopped guessing if that merge was bad

Modern devOps with Docker

Continuous integration

Continuous Integration - What even is it?

En vedette

Bib Manager Tutorial

Swati_UWM

Informatyka

pawelpyrzak

AAM 205th

Garland Diamond Sr

DisposaCone B2B Offer

DisposaCone

Certificate Barista

Nuno Silva

Mobile Ad Study

Daniel Arbizu

“La educación en la familia”

Alma Malagon

Авторская разработка тренинг-центра "1000 идей". Интернет-магазин http://market.1000-ideas.ru/ Психологические карты, понятные каждому. В ЧЕМ ВАША ИСТИННАЯ СИЛА И ГДЕ ИСКАТЬ ИСТОЧНИК РЕСУРСОВ, КАКИХ ЦЕЛЕЙ ВЫ МОЖЕТЕ ДОБИТЬСЯ УЖЕ СЕЙЧАС, НЕ "ЛОМАЯ" СЕБЯ, РЕАЛЬНО ДОСТИЖИМЫЕ РЕЗУЛЬТАТЫ В ДАННОЙ СИТУАЦИИ.

Лук и стрелы (ситуационный расклад с картами "1000 идей")

1000 идей тренинг-центр

Da anni, nei diversi team con i quali mi sono trovato a collaborare, ho proposto sempre questa pratica: tenere un diario di bordo, da scrivere a fine giornata, per raccontare come è andata, cosa abbiamo imparato, cosa ci manca per chiudere il task sul quale stiamo lavorando e quali ostacoli o dubbi abbiamo incontrato. Pensatela come un vero specchio dello stand-up meeting: con questo apro la giornata, mentre con il daily journal la chiudo. Il journal ha tantissimi effetti benefici! Il mio obiettivo è darvi uno spunto per valutare e provare anche voi questa pratica.

Vivere per raccontarla: l’importanza del daily journal in un team agile

Pietro Di Bello

Inspiring words from Mr.Suresh Narayanan, Chairman & MD, Nestle India Ltd- Le...

Great Lakes Institute of Management

Работа со страхами (упражнение с картами "1000 дорог")

1000 идей тренинг-центр

Symbolic execution is an important and popular technique used in several software engineering tools for test case generation, debugging and program analysis. As such improving the performance of symbolic execution can have huge impact on the effectiveness of such tools. In this paper, we present a technique to systematically introduce undefined behaviors during compilation to speed up the subsequent symbolic execution of the program. We have implemented our technique inside LLVM and tested with an existing symbolic execution engine (Pathgrind). Preliminary results on the SIR repository benchmark are encouraging and show 48% speed up in time and 30% reduction in the number of constraints.

Exploiting undefined behaviors for efficient symbolic execution

Asankhaya Sharma

Your team is up and running with Splunk. Now you want to maximize your investment and solve additional business problems. Attend this session led by a Splunk expert on how to expand beyond the initial use case. Learn how to how to capture, document and present Splunk's data and present impactful ways to calculate ROI using concrete metrics; cost savings, time savings, efficiency gains, and competitive advantage.

Taking Splunk to the Next Level - Management

Splunk

En vedette (13)

Bib Manager Tutorial

Informatyka

AAM 205th

DisposaCone B2B Offer

Certificate Barista

Mobile Ad Study

“La educación en la familia”

Лук и стрелы (ситуационный расклад с картами "1000 идей")

Vivere per raccontarla: l’importanza del daily journal in un team agile

Inspiring words from Mr.Suresh Narayanan, Chairman & MD, Nestle India Ltd- Le...

Работа со страхами (упражнение с картами "1000 дорог")

Exploiting undefined behaviors for efficient symbolic execution

Taking Splunk to the Next Level - Management

Similaire à Continuous Delivery su progetti Java: cosa abbiamo imparato facendoci del male

Deploy & Continunous Integration - TDC Floripa 2015

Júnior Rocha

Today’s cutting-edge companies have software release cycles measured in days instead of months. This agility is enabled by the DevOps practice of continuous delivery, which automates building, testing, and deploying all code changes. This automation helps you catch bugs sooner and accelerates developer productivity. In this session, we’ll share the processes that Amazon’s engineers use to practice DevOps and discuss how you can bring these processes to your company by using a new set of AWS tools (AWS CodePipeline and AWS CodeDeploy). These services were inspired by Amazon's own internal developer tools and DevOps culture.

DevOps on AWS: Deep Dive on Continuous Delivery and the AWS Developer Tools

Amazon Web Services

As software teams transition to cloud-based architectures and adopt more agile processes, the tools they need to support their development cycles will change. In this session, we'll take you through the transition that Amazon made to a service-oriented architecture over a decade ago. We will share the lessons we learned, the processes we adopted, and the tools we built to increase both our agility and reliability. We will also introduce you to AWS CodeCommit, AWS CodePipeline, and AWS CodeDeploy, three new services born out of Amazon's internal DevOps experience.

DevOps at Amazon: A Look at Our Tools and Processes

Amazon Web Services

Into the cloud

Tomas Riha

DevOps on AWS: Deep Dive on Continuous Delivery and the AWS Developer Tools

Amazon Web Services

by Nick Brandaleone, Solutions Architect AWS Join us to learn about continuous integration, continuous delivery, and DevOps. The AWS Developer Tools have been designed based on the tools used by Amazon engineers to rapidly and reliably deliver products and features to customers. We’ll provide overviews of the services and best practices followed by a hands-on workshop to help you learn how to automate your software release processes, deploy application code, and monitor your application and infrastructure performance.

DevOps on AWS - Building Systems to Deliver Faster

Amazon Web Services

Today’s cutting-edge companies have software release cycles measured in days instead of months. This agility is enabled by the DevOps practice of continuous delivery, which automates building, testing, and deploying all code changes. This automation helps you catch bugs sooner and accelerates developer productivity. In this session, we’ll share the processes that Amazon’s engineers use to practice DevOps and discuss how you can bring these processes to your company by using a new set of AWS tools (AWS CodeCommit, AWS CodePipeline, and AWS CodeDeploy). These services were inspired by Amazon's own internal developer tools and DevOps culture.

DevOps on AWS: Deep Dive on Continuous Delivery and the AWS Developer Tools

Amazon Web Services

Continuous Delivery - Voxxed Days Cluj-Napoca 2017

Rafał Leszko

TYPO3 Camp Stuttgart 2015 - Continuous Delivery with Open Source Tools

Michael Lihs

Práticas, Técnicas e Ferramentas para Continuous Delivery com ALM

Marcelo Sousa Ancelmo

This session is designed to teach security engineers, developers, solutions architects, and other technical security practitioners how to use a DevSecOps approach to design and build robust security controls at cloud-scale. This session walks through the design considerations of operating high-assurance workloads on top of the AWS platform and provides examples of how to automate configuration management and generate audit evidence for your own workloads. We’ll discuss practical examples using real code for automating security tasks, then dive deeper to map the configurations against various industry frameworks. This advanced session showcases how continuous integration and deployment pipelines can accelerate the speed of security teams and improve collaboration with software development teams.

Automating Security in Cloud Workloads with DevSecOps

Amazon Web Services

DevOps on AWS: Deep Dive on Continuous Delivery and the AWS Developer Tools

Amazon Web Services

DevOps on AWS: Deep Dive on Continuous Delivery and the AWS Developer Tools

Amazon Web Services

Gozengo sauce presentation

Daniel Straus

How Gozengo Implemented a Continuous Deployment Culture from Day One

Sauce Labs

Deploy Angular to the Cloud

Simona Cotin

Continuous delivery @wcap 5-09-2013

David Funaro

Software release cycles are now measured in days instead of months. Cutting edge companies are continuously delivering high-quality software at a fast pace. In this session, we will cover how you begin your DevOps journey by sharing best practices and tools by the "two pizza" engineering teams at Amazon. We will showcase how you can accelerate developer productivity by implementing continuous integration and delivery workflows. We will also cover an introduction to AWS CodeCommit, AWS CodeBuild, AWS CodePipeline, and AWS CodeDeploy, the services inspired by Amazon's internal devloper tools and DevOps practice.

ENT201 A Tale of Two Pizzas: Accelerating Software Delivery with AWS Develope...

Amazon Web Services

Security as Code: DOES15

Ed Bellis

DevOps - Boldly Go for Distro

Paul Boos

Similaire à Continuous Delivery su progetti Java: cosa abbiamo imparato facendoci del male (20)

Deploy & Continunous Integration - TDC Floripa 2015

DevOps on AWS: Deep Dive on Continuous Delivery and the AWS Developer Tools

DevOps at Amazon: A Look at Our Tools and Processes

Into the cloud

DevOps on AWS: Deep Dive on Continuous Delivery and the AWS Developer Tools

DevOps on AWS - Building Systems to Deliver Faster

DevOps on AWS: Deep Dive on Continuous Delivery and the AWS Developer Tools

Continuous Delivery - Voxxed Days Cluj-Napoca 2017

TYPO3 Camp Stuttgart 2015 - Continuous Delivery with Open Source Tools

Práticas, Técnicas e Ferramentas para Continuous Delivery com ALM

Automating Security in Cloud Workloads with DevSecOps

DevOps on AWS: Deep Dive on Continuous Delivery and the AWS Developer Tools

Gozengo sauce presentation

How Gozengo Implemented a Continuous Deployment Culture from Day One

Deploy Angular to the Cloud

Continuous delivery @wcap 5-09-2013

ENT201 A Tale of Two Pizzas: Accelerating Software Delivery with AWS Develope...

Security as Code: DOES15

DevOps - Boldly Go for Distro

Plus de Pietro Di Bello

Lessons learned in surviving to Technical Debt

Pietro Di Bello

We share our lessons learned on how to regain control of a legacy codebase written in Java (https://github.com/xpepper/fifty-shades-of-legacy-goose-game/tree/master/goose-game-two). This codebase shows some classic design problems but more than that, badly expresses the domain of the problem we want to solve. During the session we will tackle the code the XP way: it will be a live refactoring in pair programming; we will show how the quality and expressiveness of the code can be progressively improved if we apply some good development practices with the help of some effective tools.

Surviving to a Legacy Codebase - Codemotion Berlin 2018 Edition

Pietro Di Bello

Surviving a legacy codebase: tactics and tools to keep the right path We will show you how to regain control of a legacy codebase written in Java. This codebase (https://github.com/xpepper/fifty-shades-of-legacy-goose-game/tree/master/goose-game-two) shows some classic design problems but more than that, badly expresses the domain of the problem we want to solve. During the session we will tackle the code the XP way: it will be a live refactoring in pair programming; we will show how the quality and expressiveness of the code can be progressively improved if we apply some good development practices with the help of some effective tools. Made by Paolo D'Incau and Pietro Di Bello

Surviving to a Legacy Codebase - Voxxed Days Ticino Edition

Pietro Di Bello

Getting the right people will help create a great team, and will let it grow healthy. Moreover, it will keep it rooted in your company culture, and sustaining that same culture in turn. Nevertheless, too often recruiting is overlooked or completely delegated to HR or external recruiting agencies. In this session I’ll share our experience in building our actual recruitment process, how we got to this recruitment workflow, what lessons we’ve learned and what are the key elements of a recruitment process. I’ll also examine some differences compared to a more “traditional” way of selecting and assessing people. My goal is to help attendees reflect on their own recruitment process and on the value they (and their companies) are getting from it, so that they can find improvement opportunities and ideas to get more value from the recruitment process and “be able to transform your organization”.

Hiring Great People: how we improved our recruiting process to build and grow...

Pietro Di Bello

Hiring Great People: how we improved our recruiting process to build and grow...

Pietro Di Bello

Scrum In A Nutshell

Pietro Di Bello

La nostra esperienza ha mostrato che esistono alcune pratiche “rompighiaccio” che, con un costo di introduzione relativamente basso, permettono di far prendere coscienza alle persone di alcune problematiche e dinamiche tipiche dei progetti software e che ne minano il successo. La presa di coscienza di queste problematiche e dinamiche è il primo passo per comprendere e abbracciare valori e principi dei metodi agili. Le pratiche di cui vorremmo parlare e che definiamo “ice breakers” per quel che riguarda le metodologie agili sono: lavagna, standup meeting, retrospective, build automatica, test automatici di accettazione. A cascata poi queste pratiche se ne portano dietro altre più difficili da adottare fin da subito, ma più facili da far adottare quando le persone prendono coscienza dei problemi che gli impediscono di lavorare in modo efficace (pair, tecnica del pomodoro, user stories, TDD, CI, simple design, daily journal, etc) e abbracciano i principi dell’agile. Per ogni pratica “ice breakers”, a partire dalla nostra esperienza, illustreremo il motivo per cui secondo noi sono tali, le dinamiche secondo noi migliori per proporne l’introduzione, anti-pattern e resistenze al cambiamento che abbiamo incontrato e come le abbiamo affrontate.

Breaking the ice with agile - cinque strade per rompere il ghiaccio e introdu...

Pietro Di Bello

TDD reloaded - JUGTAA 24 Ottobre 2012

Pietro Di Bello

A brief intro to TDD for a JUG-TAA event

Pietro Di Bello

"Il dilettevole giuoco dell'oca" coding dojo

Pietro Di Bello

Retrospective, StandUp Meeting e Daily Journal

Pietro Di Bello

Plus de Pietro Di Bello (11)

Lessons learned in surviving to Technical Debt

Surviving to a Legacy Codebase - Codemotion Berlin 2018 Edition

Surviving to a Legacy Codebase - Voxxed Days Ticino Edition

Hiring Great People: how we improved our recruiting process to build and grow...

Scrum In A Nutshell

Breaking the ice with agile - cinque strade per rompere il ghiaccio e introdu...

TDD reloaded - JUGTAA 24 Ottobre 2012

A brief intro to TDD for a JUG-TAA event

"Il dilettevole giuoco dell'oca" coding dojo

Retrospective, StandUp Meeting e Daily Journal

Dernier

ICT role in 21st century education and its challenges

rafiqahmad00786416

CNIC Information System with Pakdata Cf In Pakistan

danishmna97

Artificial Intelligence Chap.5 : Uncertainty

Khushali Kathiriya

Keynote 2: APIs in 2030: The Risk of Technological Sleepwalk Paolo Malinverno, Growth Advisor - The Business of Technology Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - APIs in 2030: The Risk of Technological Sleepwalk by ...

apidays

Boost Fertility New Invention Ups Success Rates.pdf

sudhanshuwaghmare1

Webinar Recording: https://www.panagenda.com/webinars/why-teams-call-analytics-is-critical-to-your-entire-business Nothing is as frustrating and noticeable as being in an important call and being unable to see or hear the other person. Not surprising then, that issues with Teams calls are among the most common problems users call their helpdesk for. Having in depth insight into everything relevant going on at the user’s device, local network, ISP and Microsoft itself during the call is crucial for good Microsoft Teams Call quality support. To ensure a quick and adequate solution and to ensure your users get the most out of their Microsoft 365. But did you know that ‘bad calls’ are also an excellent indicator of other problems arising? Precisely because it is so noticeable!? Like the canary in the mine, bad calls can be early indicators of problems. Problems that might otherwise not have been noticed for a while but can have a big impact on productivity and satisfaction. Join this session by Christoph Adler to learn how true Microsoft Teams call quality analytics helped other organizations troubleshoot bad calls and identify and fix problems that impacted Teams calls or the use of Microsoft365 in general. See what it can do to keep your users happy and productive! In this session we will cover - Why CQD data alone is not enough to troubleshoot call problems - The importance of attributing call problems to the right call participant - What call quality analytics can do to help you quickly find, fix-, and prevent problems - Why having retrospective detailed insights matters - Real life examples of how others have used Microsoft Teams call quality monitoring to problem shoot problems with their ISP, network, device health and more.

Why Teams call analytics are critical to your entire business

panagenda

presentation ICT roal in 21st century education

jfdjdjcjdnsjd

MINDCTI Revenue Release Quarter One 2024

MIND CTI

Effective data discovery is crucial for maintaining compliance and mitigating risks in today's rapidly evolving privacy landscape. However, traditional manual approaches often struggle to keep pace with the growing volume and complexity of data. Join us for an insightful webinar where industry leaders from TrustArc and Privya will share their expertise on leveraging AI-powered solutions to revolutionize data discovery. You'll learn how to: - Effortlessly maintain a comprehensive, up-to-date data inventory - Harness code scanning insights to gain complete visibility into data flows leveraging the advantages of code scanning over DB scanning - Simplify compliance by leveraging Privya's integration with TrustArc - Implement proven strategies to mitigate third-party risks Our panel of experts will discuss real-world case studies and share practical strategies for overcoming common data discovery challenges. They'll also explore the latest trends and innovations in AI-driven data management, and how these technologies can help organizations stay ahead of the curve in an ever-changing privacy landscape.

TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery

TrustArc

AWS Community Day CPH - Three problems of Terraform

Andrey Devyatkin

Corporate and higher education. Two industries that, in the past, have had a clear divide with very little crossover. The difference in goals, learning styles and objectives paved the way for differing learning technologies platforms to evolve. Now, those stark lines are blurring as both sides are discovering they have content that’s relevant to the other. Join Tammy Rutherford as she walks through the pros and cons of corporate and higher ed collaborating. And the challenges of these different technology platforms working together for a brighter future.

Corporate and higher education May webinar.pptx

Rustici Software

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Product Anonymous

The Good, the Bad and the Governed - Why is governance a dirty word? David O'Neill, Chief Operating Officer - APIContext Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...

apidays

Whatsapp Number Escorts Call girls 8617370543 Available 24x7 Mcleodganj Call Girls Service Offer Genuine VIP Model Escorts Call Girls in Your Budget. Mcleodganj Call Girls Service Provide Real Call Girls Number. Make Your Sexual Pleasure Memorable with Our Mcleodganj Call Girls at Affordable Price. Top VIP Escorts Call Girls, High Profile Independent Escorts Call Girls, Housewife Women Escorts Call Girl, College Girls Escorts Call Girls, Russian Escorts Call girls Service in Your Budget.

Mcleodganj Call Girls 🥰 8617370543 Service Offer VIP Hot Model

Deepika Singh

Six Myths about Ontologies: The Basics of Formal Ontology

johnbeverley2021

Join our latest Connector Corner webinar to discover how UiPath Integration Service revolutionizes API-centric automation in a 'Quote to Cash' process—and how that automation empowers businesses to accelerate revenue generation. A comprehensive demo will explore connecting systems, GenAI, and people, through powerful pre-built connectors designed to speed process cycle times. Speakers: James Dickson, Senior Software Engineer Charlie Greenberg, Host, Product Marketing Manager

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

DianaGray10

💥 You’re lucky! We’ve found two different (lead) developers that are willing to share their valuable lessons learned about using UiPath Document Understanding! Based on recent implementations in appealing use cases at Partou and SPIE. Don’t expect fancy videos or slide decks, but real and practical experiences that will help you with your own implementations. 📕 Topics that will be addressed: • Training the ML-model by humans: do or don't? • Rule-based versus AI extractors • Tips for finding use cases • How to start 👨‍🏫👨‍💻 Speakers: o Dion Morskieft, RPA Product Owner @Partou o Jack Klein-Schiphorst, Automation Developer @Tacstone Technology

DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam

UiPathCommunity

Strategies for Landing an Oracle DBA Job as a Fresher

Remote DBA Services

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 the deployment of external web forms using Jotform for Bonterra Impact Management. This solution can be customized to your organization’s needs and deployed to support the common use cases below: - Intake and consent - Assessments - Surveys - Applications - Program registration Interested in deploying web form automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.

Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...

Jeffrey Haguewood

Architecting Cloud Native Applications

WSO2

Dernier (20)

ICT role in 21st century education and its challenges

CNIC Information System with Pakdata Cf In Pakistan

Artificial Intelligence Chap.5 : Uncertainty

Apidays New York 2024 - APIs in 2030: The Risk of Technological Sleepwalk by ...

Boost Fertility New Invention Ups Success Rates.pdf

Why Teams call analytics are critical to your entire business

presentation ICT roal in 21st century education

MINDCTI Revenue Release Quarter One 2024

TrustArc Webinar - Unlock the Power of AI-Driven Data Discovery

AWS Community Day CPH - Three problems of Terraform

Corporate and higher education May webinar.pptx

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Apidays New York 2024 - The Good, the Bad and the Governed by David O'Neill, ...

Mcleodganj Call Girls 🥰 8617370543 Service Offer VIP Hot Model

Six Myths about Ontologies: The Basics of Formal Ontology

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam

Strategies for Landing an Oracle DBA Job as a Fresher

Web Form Automation for Bonterra Impact Management (fka Social Solutions Apri...

Architecting Cloud Native Applications

Continuous Delivery su progetti Java: cosa abbiamo imparato facendoci del male

1. Continuous Delivery in Java Cose che abbiamo imparato facendoci del male Codemotion Milano ‘15

2. @pdincau Here We Are @pierodibello

3. Continuous Delivery? What is

4. “Continuous Delivery is a software development discipline where you build software in such a way that the software can be released to production at any time.” Martin Fowler* * martinfowler.com/bliki/ContinuousDelivery.html

5. “Continuous Delivery is nothing more than reducing the stress you get when you deliver business value to the customer ” My Team* * Come and ask!

6. n t Continuous Delivery... What is

7. Continuous Integration

8. Continuous Deployment

9. “Safety” Deploy rules

10.

11. Technically Speaking

12. Deploy any specific working version to production with confidence

13. 3 ways

14. Rodeo Style

15. No tests Manual deploy Snowflake environments Non predictable outcome Few or very little collaboration

16. Rodeo Style

17. By the book

18. Fast Feedback Done is released Shared responsibility Everything is automated Repeatable and reliable process

19. Start small and iterate

20. Once upon a time...

21. We did know...

22. Previous deployment process was painful Database continuously change Different environments

23. Iterationn.1 No Automation

24. Environment replica on AWS Manual build Manual DB migrations Deploy with scp to remote JBoss

25. It was our own choice...

26. ...but we felt like this

27. No automation at all When was our last deploy?

28. A taste of Automation Iterationn.2

29. Set up a basic Jenkins installation Test and build triggered on push DB migration using Liquibase Task to deploy on AWS

30. This worked for a while

31. Errors in MyBatis DB mappers Wrong/Missing wirings

32. Meanwhile...

33. Yay! Environments are ready!

34. Deploy Everywhere Iterationn.3

35. New Jenkins job to run integration tests Track slowest tests First official deploy an all environments

36. …with different DB drivers !#$?!

37. Duplication

38. Incorrect use of mvn profiles N-builds for N-environments Long build and deploy time

39. Single Artefact Iterationn.4

40. Got rid of configurations using JBoss *Unique* artefact for all environments Deploy version X.Y.Z from Nexus

41. We started getting fast

42. But QA were not so happy Branches, branches everywhere!

43. Make them happy Iterationn.5

44. An environment for QA Tags over branches Track deployed version

45. Devs love QAs

46. Acceptance tests

47. Explained values and motivations to Product Owner

48. Self-service deploy

49. Remove Candidate Clean Up Clean Up Build it... Migrate ! Database Fetch Unit Tests Build Build Integration Test ! Integration Deploy Publish UAT QA and Publish

50. Frontend Angular ! Web ...and deliver it Deploy ESB ! ESB Deploy staging ! Deploy Staging Deploy API Deploy Core Backend Migrate ! Database

51. Things we are experimenting

52. Parallelization Environments Provisioning Jenkins under git Squash migrations to snapshot

53. What we would do differently...

54. Pipeline with “placeholders” Extract configurations asap Explain at the beginning the values behind

55. Things we will keep doing...

56. Build the pipeline iteratively Share pipeline responsibility Use the tool that best fit your needs

57. Recommended reading

58. Take a look at these Real-World Strategies for Continuous Delivery with Maven and Jenkins https://www.youtube.com/watch?v=McTZtyb9M38 Visualizations of Continuous Delivery http://continuousdelivery.com/2014/02/visualizations-of-continuous-delivery/

59.

60.

61.

62.

63. That’s all!

64. @pdincau@pierodibello

65. https://creativecommons.org/licenses/by-nc-sa/3.0/ Thanks!

Continuous Delivery su progetti Java: cosa abbiamo imparato facendoci del male

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (13)

Similaire à Continuous Delivery su progetti Java: cosa abbiamo imparato facendoci del male

Similaire à Continuous Delivery su progetti Java: cosa abbiamo imparato facendoci del male (20)

Plus de Pietro Di Bello

Plus de Pietro Di Bello (11)

Dernier

Dernier (20)

Continuous Delivery su progetti Java: cosa abbiamo imparato facendoci del male