DOCSLIB.ORG

Buildbot Documentation Release 0.9.15

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Buildbot Documentation Release 0.9.15 Buildbot Documentation Release 0.9.15 Brian Warner Jan 02, 2018 Contents 1 Buildbot Tutorial 3 1.1 First Run.................................................3 1.2 First Buildbot run with Docker......................................6 1.3 A Quick Tour...............................................9 1.4 Further Reading............................................. 17 2 Buildbot Manual 23 2.1 Introduction............................................... 23 2.2 Installation................................................ 29 2.3 Concepts................................................. 45 2.4 Secret Management........................................... 56 2.5 Configuration............................................... 58 2.6 Transition to “worker” terminology................................... 245 2.7 Customization.............................................. 250 2.8 New-Style Build Steps.......................................... 275 2.9 Command-line Tool........................................... 278 2.10 Resources................................................. 289 2.11 Optimization............................................... 289 2.12 Plugin Infrastructure in Buildbot..................................... 289 2.13 Deployment............................................... 290 3 Buildbot Development 293 3.1 General Documents........................................... 293 3.2 APIs................................................... 377 3.3 Python3 compatibility.......................................... 470 3.4 Classes.................................................. 473 4 Release Notes 509 4.1 Buildbot 0.9.15 ( 2018-01-02 ).................................. 509 4.2 Buildbot 0.9.14 ( 2017-12-08 ).................................. 510 4.3 Buildbot 0.9.13 ( 2017-11-07 ).................................. 511 4.4 Buildbot 0.9.12.post1 ( 2017-10-10 ).............................. 512 4.5 Buildbot 0.9.12 ( 2017-10-05 ).................................. 512 4.6 Buildbot 0.9.11 ( 2017-09-08 ).................................. 513 4.7 Buildbot 0.9.10 ( 2017-08-03 ).................................. 514 4.8 Buildbot 0.9.9.post2 ( 2017-07-06 ).............................. 515 4.9 Buildbot 0.9.9.post1 ( 2017-07-01 ).............................. 515 i 4.10 Buildbot 0.9.9 ( 2017-06-29 )................................... 515 4.11 Buildbot 0.9.8 ( 2017-06-14 )................................... 516 4.12 Buildbot 0.9.7 ( 2017-05-09 )................................... 517 4.13 Buildbot 0.9.6 ( 2017-04-19 )................................... 518 4.14 Buildbot 0.9.5 ( 2017-03-18 )................................... 519 4.15 Buildbot 0.9.4 ( 2017-02-08 )................................... 520 4.16 Buildbot 0.9.3 ( 2017-01-11 )................................... 521 4.17 Buildbot 0.9.2 ( 2016-12-13 )................................... 522 5 Older Release Notes 525 5.1 Release Notes for Buildbot 0.9.1 ................................... 525 5.2 Release Notes for Buildbot 0.9.0 ................................... 528 5.3 Release Notes for Buildbot 0.9.0rc4 ................................. 538 5.4 Release Notes for Buildbot 0.9.0rc3 ................................. 539 5.5 Release Notes for Buildbot 0.9.0rc2 ................................. 539 5.6 Release Notes for Buildbot 0.9.0rc1 ................................. 541 5.7 Release Notes for Buildbot 0.9.0b9................................... 542 5.8 Release Notes for Buildbot 0.9.0b8................................... 544 5.9 Release Notes for Buildbot 0.9.0b7................................... 551 5.10 Release Notes for Buildbot 0.9.0b6................................... 552 5.11 Release Notes for Buildbot 0.9.0b5................................... 553 5.12 Release Notes for Buildbot 0.9.0b4................................... 553 5.13 Release Notes for Buildbot 0.9.0b3................................... 554 5.14 Release Notes for Buildbot 0.9.0b2................................... 555 5.15 Release Notes for Buildbot 0.9.0b1................................... 556 5.16 Release Notes for Buildbot 0.8.11.................................... 563 5.17 Release Notes for Buildbot 0.8.10.................................... 566 5.18 Release Notes for Buildbot 0.8.9..................................... 567 5.19 Release Notes for Buildbot v0.8.8.................................... 574 5.20 Release Notes for Buildbot v0.8.7.................................... 576 5.21 Release Notes for Buildbot v0.8.6p1................................... 580 6 Indices and Tables 585 7 Copyright 587 Buildmaster Configuration Index 589 Scheduler Index 591 Change Source Index 593 Build Step Index 595 Reporter Target Index 597 Configurator Target Index 599 Build Worker Index 601 Command Line Index 603 Data API Event Index 605 REST/Data API Resource Type Index 607 ii REST/Data API Path Index 609 REST/Data API Actions Index 611 Python Module Index 613 iii iv Buildbot Documentation, Release 0.9.15 This is the Buildbot documentation for Buildbot version 0.9.15. If you are evaluating Buildbot and would like to get started quickly, start with the Tutorial. Regular users of Buildbot should consult the Manual, and those wishing to modify Buildbot directly will want to be familiar with the Developer’s Documentation. Contents 1 Buildbot Documentation, Release 0.9.15 2 Contents CHAPTER 1 Buildbot Tutorial Contents: 1.1 First Run 1.1.1 Goal This tutorial will take you from zero to running your first buildbot master and worker as quickly as possible, without changing the default configuration. This tutorial is all about instant gratification and the five minute experience: in five minutes we want to convince you that this project works, and that you should seriously consider spending time learning the system. In this tutorial no configuration or code changes are done. This tutorial assumes that you are running Unix, but might be adaptable to Windows. Thanks to virtualenv (https://pypi.python.org/pypi/virtualenv), installing buildbot in a standalone environment is very easy. For those more familiar with Docker (https://docker.com), there also exists a docker version of these instructions. You should be able to cut and paste each shell block from this tutorial directly into a terminal. 1.1.2 Getting ready There are many ways to get the code on your machine. We will use the easiest one: via pip in a virtualenv (https://pypi.python.org/pypi/virtualenv). It has the advantage of not polluting your operating system, as everything will be contained in the virtualenv. To make this work, you will need the following installed: • Python (https://www.python.org/) and the development packages for it • virtualenv (https://pypi.python.org/pypi/virtualenv) 3 Buildbot Documentation, Release 0.9.15 Preferably, use your distribution package manager to install these. You will also need a working Internet connection, as virtualenv and pip will need to download other projects from the Internet. Note: Buildbot does not require root access. Run the commands in this tutorial as a normal, unprivileged user. 1.1.3 Creating a master The first necessary step is to create a virtualenv for our master. We will also use a separate directory to demonstrate the distinction between a master and worker: mkdir -p ~/tmp/bb-master cd ~/tmp/bb-master On Python 2: virtualenv --no-site-packages sandbox source sandbox/bin/activate On Python 3: python3 -m venv sandbox source sandbox/bin/activate Now that we are ready, we need to install buildbot: pip install --upgrade pip pip install 'buildbot[bundle]' Now that buildbot is installed, it’s time to create the master: buildbot create-master master Buildbot’s activity is controlled by a configuration file. We will use the sample configuration file unchanged: mv master/master.cfg.sample master/master.cfg Finally, start the master: buildbot start master You will now see some log information from the master in this terminal. It should end with lines like these: 2014-11-01 15:52:55+0100 [-] BuildMaster is running The buildmaster appears to have (re)started correctly. From now on, feel free to visit the web status page running on the port 8010: http://localhost:8010/ Our master now needs (at least) a worker to execute its commands. For that, head on to the next section! 1.1.4 Creating a worker The worker will be executing the commands sent by the master. In this tutorial, we are using the buildbot/hello- world project as an example. As a consequence of this, your worker will need access to the git (https://git-scm.com/) 4 Chapter 1. Buildbot Tutorial Buildbot Documentation, Release 0.9.15 command in order to checkout some code. Be sure that it is installed, or the builds will fail. Same as we did for our master, we will create a virtualenv for our worker next to the other one. It would however be completely ok to do this on another computer - as long as the worker computer is able to connect to the master one: mkdir -p ~/tmp/bb-worker cd ~/tmp/bb-worker On Python 2: virtualenv --no-site-packages sandbox source sandbox/bin/activate On Python 3: python3 -m venv sandbox source sandbox/bin/activate Install the buildbot-worker command: pip install --upgrade pip pip install buildbot-worker # required for `runtests` build pip install setuptools-trial Now, create the worker: buildbot-worker create-worker worker localhost example-worker pass Note: If you decided to create this from another computer, you should replace localhost with the name of the computer where your master is running. The username (example-worker), and password (pass) should be the same as those
Load more

Recommended publications
  • Buildbot: a Continuous Integration System
    Buildbot: A continuous integration system Krzysztof Voss January, 2013 Outline • Testing and Continuous Integration • Introduction to Buildbot • BuildMaster • BuildMaster components • BuildSlave • Installation and Usage 1 Testing and continuous integration Tests: • the best specification • safety-net for refactoring • bug identification Tests are the most effective if we: • run them often • run them on different machines/environments • can easily see their results 2 The most straightforward approach would entail: • logging in to different machines • fetching the newest source code • running tests • analyzing their output In case we want to test a few environments, repeating the above steps is tedious. Developers do not focus on the code, instead they run tests. A continuous integration system performs all of these steps for us, so developers can focus on their code. 3 Introduction to Buildbot: Features • run builds on a variety of BuildSlave platforms • arbitrary build process: handles projects using C, Python, . • minimal host requirements: python and Twisted • BuildSlave can be behind a firewall if they can still do checkout • status delivery through web page, email, IRC, other protocols • track builds in progress, provide estimated completion time • flexible configuration by subclassing generic build process classes 4 • debug tools to force a new build, submit fake Changes, query BuildSlave status • released under the GPL source: http://buildbot.net/buildbot/docs/current/manual/introduction.html 5 Introduction to Buildbot: Overview system overview source: http://buildbot.net/buildbot/docs/0.8.1/full.html 6 BuildMaster BuildMaster components source: http://buildbot.net/buildbot/docs/0.8.1/full.html 7 BuildMaster BuildMaster: • holds the configuration of the entire system.
    [Show full text]
  • Analysis of Devops Tools to Predict an Optimized Pipeline by Adding Weightage for Parameters
    International Journal of Computer Applications (0975 – 8887) Volume 181 – No. 33, December 2018 Analysis of DevOps Tools to Predict an Optimized Pipeline by Adding Weightage for Parameters R. Vaasanthi V. Prasanna Kumari, PhD S. Philip Kingston Research Scholar, HOD, MCA Project Manager SCSVMV University Rajalakshmi Engineering Infosys, Mahindra City, Kanchipuram College, Chennai Chennai ABSTRACT cloud. Now-a-days more than ever, DevOps [Development + Operations] has gained a tremendous amount of attention in 2. SCM software industry. Selecting the tools for building the DevOps Source code management (SCM) is a software tool used for pipeline is not a trivial exercise as there are plethora’s of tools development, versioning and enables team working in available in market. It requires thought, planning, and multiple locations to work together more effectively. This preferably enough time to investigate and consult other plays a vital role in increasing team’s productivity. Some of people. Unfortunately, there isn’t enough time in the day to the SCM tools, considered for this study are GIT, SVN, CVS, dig for top-rated DevOps tools and its compatibility with ClearCase, Mercurial, TFS, Monotone, Bitkeeper, Code co- other tools. Each tool has its own pros/cons and compatibility op, Darcs, Endevor, Fossil, Perforce, Rational Synergy, of integrating with other tools. The objective of this paper is Source Safe, and GNU Bazaar. Table1 consists of SCM tools to propose an approach by adding weightage to each with weightage. parameter for the curated list of the DevOps tools. 3. BUILD Keywords Build is a process that enables source code to be automatically DevOps, SCM, dependencies, compatibility and pipeline compiled into binaries including code level unit testing to ensure individual pieces of code behave as expected [4].
    [Show full text]
  • Studying Routing Issues in Vanets by Using NS-3 Bachelor Thesis on Informatics
    Studying Routing Issues in VANETs by Using NS-3 Bachelor Thesis on Informatics by Christos Profentzas Thesis supervisor Dr. Periklis Chatzimisios Alexander Technological Educational Institute of Thessaloniki Department of Informatics A.T.E.I. of Thessaloniki P.O. Box 141 GR -547 00 Thessaloniki, Macedonia, Greece November 2012 i Acknowledgements This research project would not have been possible without the sup- port of many people. The author wishes to express his gratitude to his supervisor, Assistant Professor Periklis Chatzimisios (Alexan- der TEI of Thessaloniki, Greece) and Assistant Professor Gennaro Boggia (Politecnico di Bari, Italy) who was abundantly helpful and offered invaluable assistance, support and guidance. Deepest grati- tude are also due to the members of the supervisory committee, Assis- tant Professor Luigi Alfredo Grieco and Ph.D Student Giuseppe Piro without whose knowledge and assistance this study would not have been successful. Special thanks also to all group members of Telematics Lab at the Electrical & Electronics Engineering Depart- ment of Politecnico di Bari, for sharing the literature, invaluable assis- tance and laboratory facilities. The author would also like to convey thanks to the Office of Erasmus Program and Faculty of Alexander Technological Educational Institution of Thessaloniki for providing the financial means. Abstract A Vehicular Ad-hoc Network (VANET) is a system of nodes (vehi- cles) that are being connected with each other by wireless technolo- gies. Usually the nodes are moving with very high speeds and, thus, the topology is unpredictable and frequently changing. Such networks can be stand alone and making paths along vehicles or may be con- nected by an infrastructure internet.
    [Show full text]
  • This Book Doesn't Tell You How to Write Faster Code, Or How to Write Code with Fewer Memory Leaks, Or Even How to Debug Code at All
    Practical Development Environments By Matthew B. Doar ............................................... Publisher: O'Reilly Pub Date: September 2005 ISBN: 0-596-00796-5 Pages: 328 Table of Contents | Index This book doesn't tell you how to write faster code, or how to write code with fewer memory leaks, or even how to debug code at all. What it does tell you is how to build your product in better ways, how to keep track of the code that you write, and how to track the bugs in your code. Plus some more things you'll wish you had known before starting a project. Practical Development Environments is a guide, a collection of advice about real development environments for small to medium-sized projects and groups. Each of the chapters considers a different kind of tool - tools for tracking versions of files, build tools, testing tools, bug-tracking tools, tools for creating documentation, and tools for creating packaged releases. Each chapter discusses what you should look for in that kind of tool and what to avoid, and also describes some good ideas, bad ideas, and annoying experiences for each area. Specific instances of each type of tool are described in enough detail so that you can decide which ones you want to investigate further. Developers want to write code, not maintain makefiles. Writers want to write content instead of manage templates. IT provides machines, but doesn't have time to maintain all the different tools. Managers want the product to move smoothly from development to release, and are interested in tools to help this happen more often.
    [Show full text]
  • Expert Python Programming Third Edition
    Expert Python Programming Third Edition Become a master in Python by learning coding best practices and advanced programming concepts in Python 3.7 Michał Jaworski Tarek Ziadé BIRMINGHAM - MUMBAI Expert Python Programming Third Edition Copyright © 2019 Packt Publishing All rights reserved. No part of this book may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embedded in critical articles or reviews. Every effort has been made in the preparation of this book to ensure the accuracy of the information presented. However, the information contained in this book is sold without warranty, either express or implied. Neither the authors, nor Packt Publishing or its dealers and distributors, will be held liable for any damages caused or alleged to have been caused directly or indirectly by this book. Packt Publishing has endeavored to provide trademark information about all of the companies and products mentioned in this book by the appropriate use of capitals. However, Packt Publishing cannot guarantee the accuracy of this information. Commissioning Editor: Kunal Chaudhari Acquisition Editor: Chaitanya Nair Content Development Editor: Zeeyan Pinheiro Technical Editor: Ketan Kamble Copy Editor: Safis Editing Project Coordinator: Vaidehi Sawant Proofreader: Safis Editing Indexer: Priyanka Dhadke Graphics: Alishon Mendonsa Production Coordinator: Shraddha Falebhai First published: September 2008 Second edition: May 2016 Third edition: April 2019 Production reference: 1270419 Published by Packt Publishing Ltd. Livery Place 35 Livery Street Birmingham B3 2PB, UK. ISBN 978-1-78980-889-6 www.packtpub.com To my beloved wife, Oliwia, for her love, inspiration, and her endless patience.
    [Show full text]
  • Design and Implementation of a Continuous Integration System
    Prakash Acharya DESIGN AND IMPLEMENTATION OF A CONTINUOUS INTEGRATION SYSTEM DESIGN AND IMPLEMENTATION OF A CONTINUOUS INTEGRATION SYSTEM Prakash Acharya Bachelor’s Thesis Spring 2019 Information Technology Oulu University of Applied Sciences ABSTRACT Oulu University of Applied Sciences Information Technology, Internet Services Author: Prakash Acharya Title of the bachelor’s thesis: Design and Implementation of a Continuous Integration System Supervisor: Lasse Haverinen Term and year of completion: Spring 2019 Number of pages: 43 Not having an automated test system in the software development process leaves space for errors to go unnoticed in code review, which can break a codebase if integrated. The aim of the Bachelor’s thesis was to design and implement a Continuous Integration system where tests and build tasks could be automated. The Buildbot framework was used as a Continuous Integration and automation framework. The Ansible playbook was used for automating the deployment of Buildbot configuration. The Buildbot configuration was created in such a way that it allows Buildbot instances to be created easily and in a configurable manner. In addition, automation of the Python static code analysis tool, Prospector, was added to the Continuous Integration system. The result of having a configurable Buildbot system was that the developers could start adding automation tasks and test and verify their change without affecting the production instance. Having an automated static code analysis run on changes brings into attention potential problems and error before they are integrated. Even though the Buildbot system is not taken into use, it was tested in a test environment and it is shown to work.
    [Show full text]
  • Driving and Virtualizing Control Systems: the Open Source Approach Used in Whiterabbit
    Driving and virtualizing control systems: the Open Source approach used in WhiteRabbit Javier Muñoz Mellid & Samuel Iglesias Gonsalvez Academia-Industry Matching event on Technology of Controls for Accelerators and Detectors November 2013 Agenda Knowing Igalia The value of the Open Source approach Open Source approach in WhiteRabbit A walk on technical details and demo Driving and virtualizing control systems: the Open Source approach used in WhiteRabbit Javier Muñoz Mellid & Samuel Iglesias Gonsalvez What is Igalia? Open Source Company 40 engineers and hackers working around the globe Hacking upstream in different technologies and communities kernel (Linux) virtualization (QEMU/KVM) browsers/multimedia (WebKit, Blink, GStreamer...) compilers (V8, JavaScriptCore...) UI (GTK+,...) documents (Evince, LibreOffice...) distros (Debian, Tizen...) automotive/IVI 13 years old now! www.igalia.com Driving and virtualizing control systems: the Open Source approach used in WhiteRabbit Javier Muñoz Mellid & Samuel Iglesias Gonsalvez Partnering Linux Foundation www.linuxfoundation.org/news- media/announcements/2011/04/igalia-joins-linux- foundation W3C www.igalia.com/nc/igalia-247/news/item/igalia-joins- the-world-wide-web-consortium Tizen Association www.igalia.com/nc/igalia-247/news/item/igalia-joins- the-tizen-association-partner-program/ ... Driving and virtualizing control systems: the Open Source approach used in WhiteRabbit Javier Muñoz Mellid & Samuel Iglesias Gonsalvez What services and solutions provides Igalia? We are experts in Open Source
    [Show full text]
  • Splash Documentation Release 3.5
    Splash Documentation Release 3.5 Scrapinghub Jun 16, 2020 Contents 1 Documentation 3 1.1 Installation................................................3 1.2 Splash HTTP API............................................6 1.3 Splash Scripts Tutorial.......................................... 18 1.4 Splash Lua API Overview........................................ 24 1.5 Splash Scripts Reference......................................... 26 1.6 Response Object............................................. 67 1.7 Request Object.............................................. 69 1.8 Element Object.............................................. 71 1.9 Working with Binary Data........................................ 87 1.10 Available Lua Libraries......................................... 88 1.11 Splash and Jupyter............................................ 95 1.12 FAQ.................................................... 97 1.13 Contributing to Splash.......................................... 102 1.14 Implementation Details......................................... 103 1.15 Changes................................................. 105 i ii Splash Documentation, Release 3.5 Splash is a javascript rendering service. It’s a lightweight web browser with an HTTP API, implemented in Python 3 using Twisted and QT5. The (twisted) QT reactor is used to make the service fully asynchronous allowing to take advantage of webkit concurrency via QT main loop. Some of Splash features: • process multiple webpages in parallel; • get HTML results and/or take screenshots; • turn
    [Show full text]
  • Automating Build, Test, and Release with Buildbot
    Automating Build, Test, and Release with Buildbot Dustin J. Mitchell Mozilla, Inc. Email: [email protected] Tom Prince Email: [email protected] Abstract—Buildbot is a mature framework for building con- to support a variety of deployments. Schedulers react to new tinuous integration systems which supports parallel execution of data from change sources, external events, or triggers based jobs across multiple platforms, flexible integration with version- on clock time (e.g., for a nightly build), and add new build control systems, extensive status reporting, and more. Beyond the capabilities it shares with similar tools, Buildbot has a number requests to the queue. of unique strengths and capabilities, some of them particu- Each build request comes with a set of source stamps larly geared toward release processes. This paper summarizes identifying the code from each codebase used for a build. A Buildbot’s structure, contrasts the framework with related tools, source stamp represents a particular revision and branch in a describes some advanced configurations, and highlights ongoing source code repository. Build requests also specify a builder improvements to the framework.1 that should perform the task and a set of properties, arbitrary I. INTRODUCTION key-value pairs giving further detail about the requested build. Buildbot is a continuous integration (CI) framework which Each builder defines the steps to take in executing a particular has been in use for well over 10 years[13]. While it began type of build. Once the request is selected for execution, the as a simple build-and-test tool, it has grown into an advanced steps are performed sequentially.
    [Show full text]
  • Mining Software Repositories for Release Engineers - Empirical Studies on Integration and Infrastructure-As-Code
    UNIVERSITÉ DE MONTRÉAL MINING SOFTWARE REPOSITORIES FOR RELEASE ENGINEERS - EMPIRICAL STUDIES ON INTEGRATION AND INFRASTRUCTURE-AS-CODE YUJUAN JIANG DÉPARTEMENT DE GÉNIE INFORMATIQUE ET GÉNIE LOGICIEL ÉCOLE POLYTECHNIQUE DE MONTRÉAL THÈSE PRÉSENTÉE EN VUE DE L’OBTENTION DU DIPLÔME DE PHILOSOPHIÆ DOCTOR (GÉNIE INFORMATIQUE) AOÛT 2016 c Yujuan Jiang, 2016. UNIVERSITÉ DE MONTRÉAL ÉCOLE POLYTECHNIQUE DE MONTRÉAL Cette thèse intitulée: MINING SOFTWARE REPOSITORIES FOR RELEASE ENGINEERS - EMPIRICAL STUDIES ON INTEGRATION AND INFRASTRUCTURE-AS-CODE présentée par: JIANG Yujuan en vue de l’obtention du diplôme de: Philosophiæ Doctor a été dûment acceptée par le jury d’examen constitué de: M. GAGNON Michel, Ph. D., président M. ADAMS Bram, Doctorat, membre et directeur de recherche M. GUÉHÉNEUC Yann-Gaël, Doctorat, membre Mme BAYSAL Olga, Ph. D., membre externe iii DEDICATION To my grandpa Who has become a star in the heaven iv ACKNOWLEDGMENTS Many people I met, many things happened, are hidden as part of this thesis. First of all, I want to thank my parents, for their endless and unconditional love. You respect my every single choice and impractical dream. You always hold the faith in me, even when I myself had lost it. Exclusive thanks are dedicated to my supervisor, Dr.Bram Adams. Humble, enthusiastic and hard-working, for work and for life, you show me what should be like as a researcher and an individual person. You lead me through all the way up here, with enormous patience and kindness. In past four years, what I gained was not only professional skills, but also the will to face new challenges, the courage of learning from failures and the belief in hard working.
    [Show full text]
  • Buildbot This Is the Buildbot Manual
    BuildBot This is the BuildBot manual. Copyright (C) 2005, 2006, 2009, 2010 Brian Warner Copying and distribution of this file, with or without modification, are permitted in any medium without royalty provided the copyright notice and this notice are preserved. i Table of Contents 1 Introduction..................................... 1 1.1 History and Philosophy ........................................ 1 1.2 System Architecture............................................ 2 1.2.1 BuildSlave Connections.................................... 3 1.2.2 Buildmaster Architecture .................................. 4 1.2.3 Status Delivery Architecture............................... 6 1.3 Control Flow ................................................... 6 2 Installation ...................................... 8 2.1 Requirements .................................................. 8 2.2 Installing the code ............................................. 8 2.3 Creating a buildmaster ......................................... 9 2.4 Upgrading an Existing Buildmaster............................ 10 2.5 Creating a buildslave.......................................... 10 2.5.1 Buildslave Options ....................................... 12 2.6 Launching the daemons ....................................... 13 2.7 Logfiles ................................................... .... 14 2.8 Shutdown ................................................... 14 2.9 Maintenance .................................................. 15 2.10 Troubleshooting.............................................
    [Show full text]
  • Qtwebkit Layout Tests DRT and Tools
    UNIVERSITAS SCIENTIARUM SZEGEDIENSIS UNIVERSITY OF SZEGED Department of Software Engineering QtWebKit layout tests DRT and Tools András Bécsi (bbandix) <[email protected]> 09/12/09 UNIVERSITAS SCIENTIARUM SZEGEDIENSIS UNIVERSITY OF SZEGED Department of Software Engineering Outline Monitoring the buildbot Update toQt 4.6 on theBuildBot ■ ■ ■ ■ ■ ■ BuildBotMiner BuildBot logs manual-tester layout tests Progress of the port measured by passing DumpRenderTree issues Font metric issues » » Brokentests Flakeytests AndrásBécsi (bbandix) @ Nokia WebKit Code Camp 2 09/12/09 UNIVERSITAS SCIENTIARUM SZEGEDIENSIS UNIVERSITY OF SZEGED Department of Software Engineering Qt 4.6 issues Issueswith fonts ■ ■ metricsdo only work on our BuildBot howeverwe got feedback thatthese After the update of the expected files tests (~ 500) experienced pixel differencesin many After the update to Qt 4.6 we » are correct on the bot layout on developers machines but More than 300tests have incorrect AndrásBécsi (bbandix) @ Nokia WebKit Code Camp 3 09/12/09 UNIVERSITAS SCIENTIARUM SZEGEDIENSIS UNIVERSITY OF SZEGED Department of Software Engineering Qt 4.6 font metric issues the 306 failing tests found onlyminor differences(5-10 tests) On my laptop managedI to reproduce We testedother major distributions, but ■ the same usewe on the buildbot We tried the default configuration of Qt 4.6, – buildbot and and my machine: buildbot differencesthe between package Suspicious to Default /usr/localinstall echo yes|./configure–opensource-no-webkit » » » libxext1.0.4→ 1.1.1
    [Show full text]