Ci Presentacion

•

0 recomendaciones•1,242 vistas

OpenSource Connections

English version of a presentation on the benefits, and challenges, of using CI.

Tecnología

CI Presentation

Richmond
Eric Pugh
January 14th, 2009

¿Who am I?

 Principal of OpenSource Connections
Contributer to CruiseControl
Member of Apache Software Foundation
Presenter at many conferences
including OSCON, ApacheCON, jTDS
Fascinated by the art of software
development

Continuous Integration RICHMOND, January 14th, 2009

¿What are we talking about?

¿What is CI?
¿Why does it matter to me?
¿What do I need to use CI?
Demonstration of Hudson
¡Questions!

3
Continuous Integration RICHMOND, January 14th, 2009

¿What is Continous Integracion?

From Martin Fowler:

“a fully automated and reproducible build,
including testing, that runs many times a day”.

http://martinfowler.com/articles/continuousIntegration.html

4
Continuous Integration RICHMOND, January 14th, 2009

Rapid Feedback

< 10 minutos

Continuous Integration RICHMOND, January 14th, 2009

¿How is CI important to different members of a team?

6
Continuous Integration RICHMOND, January 14th, 2009

Life of a programmer without CI...

 Unstable code, integration is difficult
Many build errors reported
Only one person on the team can build the entire
project
Demonstrations require extensive planning
Feedback cycle is long

Every day is a struggle to be productive

7
Continuous Integration RICHMOND, January 14th, 2009

Life of a programmer with IC...

 The build process is simple and repeatable
Elimination of Human Error
Demo’s are quick and easy
Feedback cycle is very rapid

¡Every day you know you can code!

8
Continuous Integration RICHMOND, January 14th, 2009

For a tester

control


 ¿What is in the build?
¿What has changed between builds?
¿How do I verify functionality?

9
Continuous Integration RICHMOND, January 14th, 2009

For a Project Manager

Visibility


10
Continuous Integration RICHMOND, January 14th, 2009

For a Project Manager

11
Continuous Integration RICHMOND, January 14th, 2009

For a development team

security


12
Continuous Integration RICHMOND, January 14th, 2009

For a development team

13
Continuous Integration RICHMOND, January 14th, 2009

For a development team

14
Continuous Integration RICHMOND, January 14th, 2009

For a development team

15
Continuous Integration RICHMOND, January 14th, 2009

¿What is needed to get started?

 A dedicated machine
Source Control
Automated Build Script
Method of notification

16
Continuous Integration RICHMOND, January 14th, 2009

¿ What are the challenges to using CI?

17
Continuous Integration RICHMOND, January 14th, 2009

Challenge One: Cultural Change

 CI needs a champion who acts as the ambassador to the leaders of the
organization.
Thoughtleaders in the organization who can help encourage
developers to accept the process changes that CI brings

 A very successful test case
¿A greenfield project if possible?

18
Continuous Integration RICHMOND, January 14th, 2009

Challenge Two: Environmental Difficulties

 All the tests should be true unit tests, not
integratin tests
 Few or no external dependencies
 A beefy build server...
 A strategy for deploying code into the CI
environment
Database changes are SIMPLE

19
Continuous Integration RICHMOND, January 14th, 2009

Challenge Three: Project Characteristics

 Fewer branches to the code makes life easier
Many small code changes. Code is committed throughout the day.
There are good unit test coverage.
The code is ready for deployment, not in pieces.

20
Continuous Integration RICHMOND, January 14th, 2009

Challenge Four: Stability of CI Tool

X
 The CI system must be as well maintained as
the Source Control system.
THe CI system can do builds very quickly.
¿Who has responsibility for CI? It’s very
important to have a “throat to choke”.
No false alarms. If there are false alarms
then the developers lose confidence in the CI

✓
system.

21
Continuous Integration RICHMOND, January 14th, 2009

Demo of Hudson

22
Continuous Integration RICHMOND, January 14th, 2009

¿Where to next?

 Continuous Integration: Improving Software Quality
and Reducing Risk
CIGuys.com (??)
CITConf is the conference for CI. This year April 24,
25 in Minneapolis, MN.

23
Continuous Integration RICHMOND, January 14th, 2009

Matrix of 22 differences in CI systems

http://confluence.public.thoughtworks.org/display/CC/CI+Feature+Matrix

24
Continuous Integration RICHMOND, January 14th, 2009

¿Why CI?

Eliminate human errors
Tests that run frequently are more valuable
A CI system is the foundation of a project status dashboard
¡Eliminate integration problems!

25
Continuous Integration RICHMOND, January 14th, 2009

RICHMOND
Eric Pugh epugh@opensourceconnections.com
January 14th, 2009

Más contenido relacionado

Similar a Ci Presentacion

Un sistema di Continuous Integration fra progetti eterogenei Continuos Integration si riferisce alla pratica di aggiungere nuove feature nel codice e di testarlo non solo in modo isolato ma anche in piena integrazione con gli altri progetti durante il ciclo di sviluppo del software. Implementare un sistema automatizzato di CI prevede un repository con il codice sorgente utilizzato durante la fase di sviluppo ed uno strumento di CI che continui a fare polling del codice e controllarlo tramite i test in integrazione. Ma non basta quando ci sono progetti eterogenei che collaborano fra di loro, in questo talk vedremo specificatamente questo aspetto.

Continuous integration CloudParty 21 may 2014 - Milan

Simone Pasquini

What Is Visualization?

OneSpring LLC

Flusso Continuous Integration & Continuous Delivery

Joost van der Griendt

Unicom Software Corporate Profile

Alexander A. Grygoruk

IBM UrbanCode Deploy: Automates and manages the deployments of business applications made of many component pieces such as web services, databases, content, CICS and mobile apps. Through automation, costly errors and manual labor are drastically reduced. UrbanCode Deploy also eliminates a common bottleneck between agile development teams and slower operations groups thereby speeding time to market. UrbanCode Deploy excels at driving down cost and reducing risk. IBM UrbanCode Deploy with Patterns: A leading edge offering that combines all the great capabilities of UrbanCode Deploy with additional capabilities for designing and deploying full-stack environments on cloud and updating configurations for existing cloud environments. IBM UrbanCode Release: A robust collaborative release management tool that helps you handle the growing number and complexity of releases. You can plan, execute, and track a release through every stage of the delivery lifecycle. IBM UrbanCode Build: An enterprise continuous integration server used for managing builds, build artifacts and the dependancies inherent with them. UrbanCode Build specializes in reducing errors and speeding handoffs through a managed self-service build infrastructure.

Urban code - DevOps - cost reduction

Chris Sparshott

Lean Thinking in IT by Marie-Pia Ignace, Lean IT Summit 2014

Institut Lean France

jenkins.pptx

Orco1

20 Practical tips for a successful internationalisation project

ecomplexx

Videocon

Durgesh Vaish

From Continuous Integration to Continuous Delivery and DevOps

Luca Minudel

How Automation Reveals Technical Debt

IBM UrbanCode Products

LSU Nordic 2015 - Agile development on system z

Flemming Petersen

The state of Plone performance

Interaktiv

Innovate at speed with Devops

Eric Cattoir

Manual application deployment processes tend to be error prone and inefficient and can make achieving consistent deployments seem impossible. There is good news. You don’t need to choose between a careful, rigorous approach and a speedy but haphazard one. It’s possible to implement an automated deployment solution that provides consistency and audit trails while improving productivity for your release engineers, operations personnel, and testers. See how! Learn more about UrbanCode: http://ibm.biz/learnurbancode

Death to Manual Deployments

IBM UrbanCode Products

Realizing Parallelism and Transparency in Applications through Idempotence

Karthik Sankar

Why Agile

Hillel Glazer

Lean manufacturing

Hammaduddin

Ibm business partner connect 2015 long fong yee v1 (read-only)

Fong Yee Long

Presentacion eglc 2013 valencia_spain

Juan Felipe Pons Achell

Similar a Ci Presentacion (20)

Continuous integration CloudParty 21 may 2014 - Milan

What Is Visualization?

Flusso Continuous Integration & Continuous Delivery

Unicom Software Corporate Profile

Urban code - DevOps - cost reduction

Lean Thinking in IT by Marie-Pia Ignace, Lean IT Summit 2014

jenkins.pptx

20 Practical tips for a successful internationalisation project

Videocon

From Continuous Integration to Continuous Delivery and DevOps

How Automation Reveals Technical Debt

LSU Nordic 2015 - Agile development on system z

The state of Plone performance

Innovate at speed with Devops

Death to Manual Deployments

Realizing Parallelism and Transparency in Applications through Idempotence

Why Agile

Lean manufacturing

Ibm business partner connect 2015 long fong yee v1 (read-only)

Presentacion eglc 2013 valencia_spain

Más de OpenSource Connections

Encores

OpenSource Connections

Test driven relevancy

OpenSource Connections

Smarter search drives value to your business. Delivering search that matches users to the right content is what you care about. But organizations often get stuck getting there. It turns out that you need quite a number of very different ingredients to deliver tremendous search. It can make your head spin! To help you think through where your team is on its road to smarter search, Pugh introduces the maturity model used by OpenSource Connections and walks you through a very concrete method to inventory needed skills and translate that into search roles for your team. He shows how to measure your capabilities in key areas of search to drive better ROI from search.

How To Structure Your Search Team for Success

OpenSource Connections

The right path to making search relevant - Taxonomy Bootcamp London 2019

OpenSource Connections

Payloads and OCR with Solr

OpenSource Connections

Haystack 2019 Lightning Talk - The Future of Quepid - Charlie Hull

OpenSource Connections

Haystack 2019 Lightning Talk - State of Apache Tika - Tim Allison

OpenSource Connections

Haystack 2019 Lightning Talk - Relevance on 17 million full text documents - ...

OpenSource Connections

Haystack 2019 Lightning Talk - Solr Cloud on Kubernetes - Manoj Bharadwaj

OpenSource Connections

Haystack 2019 Lightning Talk - Quaerite a Search relevance evaluation toolkit...

OpenSource Connections

Over the past year, the POLITICO team has developed a recommendation system for our users, which recommends not only news content to read but also news topics to subscribe to. This talk will discuss our development path, including dead-ends and performance trade-offs. In the end, the team produced a system based on search technology (in our case, Elasticsearch) and refined by machine learning techniques to achieve a balance between personalization and serendipity.

Haystack 2019 - Search-based recommendations at Politico - Ryan Kohl

OpenSource Connections

With the advent of deep learning and algorithms like word2vec and doc2vec, vectors-based representations are increasingly being used in search to represent anything from documents to images and products. However, search engines work with documents made of tokens, and not vectors, and are typically not designed for fast vector matching out of the box. In this talk, I will give an overview of how vectors can be derived from documents to produce a semantic representation of a document that can be used to implement semantic / conceptual search without hurting performance. I will then describe a few different techniques for efficiently searching vector-based representations in an inverted index, including LSH, vector quantization and k-means tree, and compare their performance in terms of speed and relevancy. Finally, I will describe how each technique can be implemented efficiently in a lucene-based search engine such as Solr or Elastic Search.

Haystack 2019 - Search with Vectors - Simon Hughes

OpenSource Connections

To optimally interpret most natural language queries, it is necessary to understand the phrases, entities, commands, and relationships represented or implied within the search. Knowledge graphs serve as useful instantiations of ontologies which can help represent this kind of knowledge within a domain. In this talk, we'll walk through techniques to build knowledge graphs automatically from your own domain-specific content, how you can update and edit the nodes and relationships, and how you can seamlessly integrate them into your search solution for enhanced query interpretation and semantic search. We'll have some fun with some of the more search-centric use cased of knowledge graphs, such as entity extraction, query expansion, disambiguation, and pattern identification within our queries: for example, transforming the query "bbq near haystack" into { filter:["doc_type":"restaurant"], "query": { "boost": { "b": "recip(geodist(38.034780,-78.486790),1,1000,1000)", "query": "bbq OR barbeque OR barbecue" } } } We'll also specifically cover use of the Semantic Knowledge Graph, a particularly interesting knowledge graph implementation available within Apache Solr that can be auto-generated from your own domain-specific content and which provides highly-nuanced, contextual interpretation of all of the terms, phrases and entities within your domain. We'll see a live demo with real world data demonstrating how you can build and apply your own knowledge graphs to power much more relevant query understanding within your search engine.

Haystack 2019 - Natural Language Search with Knowledge Graphs - Trey Grainger

OpenSource Connections

For e-commerce applications, matching users with the items they want is the name of the game. If they can't find what they want then how can they buy anything?! Typically this functionality is provided through search and browse experience. Search allows users to type in text and match against the text of the items in the inventory. Browse allows users to select filters and slice-and-dice the inventory down to the subset they are interested in. But with the shift toward mobile devices, no one wants to type anymore - thus browse is becoming dominant in the e-commerce experience. But there's a problem! What if your inventory is not categorized? Perhaps your inventory is user generated or generated by external providers who don't tag and categorize the inventory. No categories and no tags means no browse experience and missed sales. You could hire an army of taxonomists and curators to tag items - but training and curation will be expensive. You can demand that your providers tag their items and adhere to your taxonomy - but providers will buck this new requirement unless they see obvious and immediate benefit. Worse, providers might use tags to game the system - artificially placing themselves in the wrong category to drive more sales. Worst of all, creating the right taxonomy is hard. You have to structure a taxonomy to realistically represent how your customers think about the inventory. Eventbrite is investigating a tantalizing alternative: using a combination of customer interactions and machine learning to automatically tag and categorize our inventory. As customers interact with our platform - as they search for events and click on and purchase events that interest them - we implicitly gather information about how our users think about our inventory. Search text effectively acts like a tag and a click on an event card is a vote for that clicked event is representative of that tag. We are able to use this stream of information as training data for a machine learning classification model; and as we receive new inventory, we can automatically tag it with the text that customers will likely use when searching for it. This makes it possible to better understand our inventory, our supply and demand, and most importantly this allows us to build the browse experience that customers demand. In this talk I will explain in depth the problem space and Eventbrite's approach in solving the problem. I will describe how we gathered training data from our search and click logs, and how we built and refined the model. I will present the output of the model and discuss both the positive results of our work as well as the work left to be done. Those attending this talk will leave with some new ideas to take back to their own business.

Haystack 2019 - Search Logs + Machine Learning = Auto-Tagging Inventory - Joh...

OpenSource Connections

Recently Elasticsearch has introduced a number of ways to improve search relevance of your documents based on numeric features. In this talk I will present the newly introduced field types of "rank_feature", "rank_features" ,"dense_field", and "sparse_vector" and discuss in what situations and how they can be used to boost scores of your documents. I will also talk about the inner workings of queries based on these fields, and related performance considerations.

Haystack 2019 - Improving Search Relevance with Numeric Features in Elasticse...

OpenSource Connections

With an increasing amount of relevancy factors, relevancy fine-tuning becomes more complex as changing the impact of factors produces increasingly more unintended side effects. In recent years, there has been a lot of discussion about how learning algorithms can replace manual relevancy fine-tuning in order to manage this complexity. However, discussions about the challenge of relevancy should additionally consider architectural aspects. Especially microservice-based architectures provide many ways to encapsulate and to separate complexities of search solutions, which facilitates optimizing the search as well as locating and fixing problems. Generally, relevancy factors can be assigned to three different groups, each handled at a different stage of the search request processing. The first group contains contextual factors that depend on certain characteristics of a query, such as query-related boosts lifting up top-sellers for queries or category-related boosts to distinguish products from their accessories. Such contextual factors can be handled as a step of the preprocessing of queries. The respective boosting information can simply be appended to the query before it is actually sent to the search engine. Ideally, the normalization of the query is done beforehand. The second group contains factors that are considered for all queries in more or less the same way, e. g. a ranking function basing on keyword occurrences, product topicality or sales in total. Factors related to this group can be handled directly by configuring the search engine. The third group contains situational factors. For instance, a certain product might be a good match for a certain query in general, but for situational circumstances it should not appear among the top five products (e. g. because it is out of stock). Such situational factors can be handled by resorting result sets, after they were returned by the search engine. The handling of the different factors within successive stages of search request processing will be discussed from an architectural perspective. Implications for applying learning algorithms and the implementation of a personalized search will be considered.

Haystack 2019 - Architectural considerations on search relevancy in the conte...

OpenSource Connections

Does your search application include a custom query syntax with various search operators such as Booleans, proximity, term or phrase frequency, capitalization, quoted text or as-is operator, and other advanced operators? Although most search applications offer a natural language-oriented search box, some advanced applications may also offer a custom query syntax for advanced users or automated tasks. The Lucene "classic" query operators that are supported by the Solr edismax query parser (Boolean, phrase with slop, wildcard, etc.) cover a good amount of use cases, but they only get you so far. In this talk, we will explore various strategies to support a custom and advanced query syntax in Solr, covering a spectrum of options from leveraging the out-of-the-box Solr query DSL, to a custom Solr query parser, and hybrid solutions in between. We will identify the options' pros and cons, discuss relevancy considerations, and illustrate the options in Java.

Haystack 2019 - Custom Solr Query Parser Design Option, and Pros & Cons - Ber...

OpenSource Connections

For a relevance engineer one of the most difficult tasks in the tuning process is to convince others in the organization that this is a joint effort. Even the brightest search guru doesn't get very far when working in isolation, so establishing cross-collaboration through the organization is essential. But how to get there? On top of that, in a large organization a relevance engineer often works on multiple seemingly unrelated search projects. The challenge is not to get drowned in building custom solutions for each project, but to design generic and re-usable strategies which solve many problems at once. In this session we'll discuss how to build a widely supported basis for search quality improvements in an organization. It is full of practical tips and examples which could help you in establishing a cross-functional culture that is optimal for relevance tuning. It also zooms in on an holistic approach of solving multiple equivalent search issues at once.

Haystack 2019 - Establishing a relevance focused culture in a large organizat...

OpenSource Connections

Haystack 2019 - Solving for Satisfaction: Introduction to Click Models - Eliz...

OpenSource Connections

The New York Times has had search for a long time but 2018 was the year in which the company engaged with relevance in a deep way. The aim of this talk is to share what we've learned as we've increased our search sophistication and some of the challenges we still face. Some of the techniques we've adopted in this past year include offline metrics testing, reflective testing, and user engagement metrics. We now have a process in place to quickly get mappings changes out to production. As a team we now also have a vocabulary for talking about relevance and can use it to discuss trade-offs and goals in conjunction with our metrics. We hope this talk is of use to those who've put off working on search relevance due to fear, uncertainty, or ambivalence. We will talk about how we went from working on everything but search relevance to finally pulling back the curtain on the search system. We hope what we've learned can help others get started.

2019 Haystack - How The New York Times Tackles Relevance - Jeremiah Via

OpenSource Connections

Más de OpenSource Connections (20)