DOCSLIB.ORG

Buildbot Documentation Release 0.8.9

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Buildbot Documentation Release 0.8.9 BuildBot Documentation Release 0.8.9 Brian Warner June 14, 2014 Contents 1 Buildbot Tutorial 3 1.1 First Run...............................................3 1.2 First Buildbot run with Docker....................................6 1.3 A Quick Tour.............................................8 1.4 Further Reading........................................... 15 2 Buildbot Manual 21 2.1 Introduction............................................. 21 2.2 Installation.............................................. 26 2.3 Concepts............................................... 38 2.4 Configuration............................................. 47 2.5 Customization............................................ 173 2.6 New-Style Build Steps........................................ 189 2.7 Command-line Tool......................................... 192 2.8 Resources............................................... 202 2.9 Optimization............................................. 202 3 Buildbot Development 203 3.1 Master Organization......................................... 203 3.2 Definitions.............................................. 204 3.3 Buildbot Coding Style........................................ 204 3.4 Buildbot’s Test Suite......................................... 207 3.5 Configuration............................................. 212 3.6 Utilities................................................ 217 3.7 Database............................................... 226 3.8 Build Result Codes.......................................... 242 3.9 File Formats............................................. 243 3.10 Web Status.............................................. 243 3.11 Master-Slave API........................................... 244 3.12 String Encodings........................................... 251 3.13 Metrics................................................ 251 3.14 Classes................................................ 253 4 Release Notes for Buildbot 0.8.9 271 4.1 Master................................................ 271 4.2 Slave................................................. 277 4.3 Details................................................ 277 4.4 Older Versions............................................ 277 5 Indices and Tables 295 6 Copyright 297 i Buildmaster Configuration Index 299 Scheduler Index 301 Change Source Index 303 Build Step Index 305 Status Target Index 307 Command Line Index 309 Python Module Index 311 ii BuildBot Documentation, Release 0.8.9 This is the BuildBot documentation for Buildbot version 0.8.9. 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.8.9 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 slave 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 some more time learning the system. In this tutorial no configuration or code changes are done. This tutorial assumes that you are running on Unix, but might be adaptable easily to Windows. For the fastest way through in Linux, you can use Docker, the linux container engine. Docker automates all the deployment steps for you. For a more manual approach, you should be able to cut and paste each shell block from this tutorial directly into a terminal. 1.1.2 Getting the code There are many ways to get the code on your machine. For this tutorial, we will use easy_install to install and run buildbot. While this isn’t the preferred method to install buildbot, it is the simplest one to use for the purposes of this tutorial because it should work on all systems. (The preferred method would be to install buildbot via pip.) To make this work, you will need the following installed: • Python (http://www.python.org/) and the development packages for it • virtualenv (http://pypi.python.org/pypi/virtualenv/) • Git (http://git-scm.com/) Preferably, use your package installer to install these. You will also need a working Internet connection, as virtualenv and easy_install 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. Let’s dive in by typing at the terminal: 3 BuildBot Documentation, Release 0.8.9 cd mkdir -p tmp/buildbot cd tmp/buildbot virtualenv --no-site-packages sandbox source sandbox/bin/activate easy_install sqlalchemy==0.7.10 easy_install buildbot Note: The requirement to install SQLAlchemy-0.7.10 is due to a conflict between newer versions of SQLAlchemy and SQLAlchemy-Migrate. 1.1.3 Creating a master At the terminal, type: buildbot create-master master mv master/master.cfg.sample master/master.cfg Now start it: buildbot start master tail -f master/twistd.log You will now see all of the log information from the master in this terminal. You should see lines like this: 2011-12-04 10:04:40-0600 [-] Starting factory <buildbot.status.web.baseweb.RotateLogSite instance at 0x2e36638> 2011-12-04 10:04:40-0600 [-] Setting up http.log rotating 10 files of 10000000 bytes each 2011-12-04 10:04:40-0600 [-] WebStatus using (/home/dustin/tmp/buildbot/master/public_html) 2011-12-04 10:04:40-0600 [-] removing 0 old schedulers, updating 0, and adding 1 2011-12-04 10:04:40-0600 [-] adding 1 new changesources, removing 0 2011-12-04 10:04:40-0600 [-] gitpoller: using workdir ’/home/dustin/tmp/buildbot/master/gitpoller-workdir’ 2011-12-04 10:04:40-0600 [-] gitpoller: initializing working dir from git://github.com/buildbot/pyflakes.git 2011-12-04 10:04:40-0600 [-] configuration update complete 2011-12-04 10:04:41-0600 [-] gitpoller: checking out master 2011-12-04 10:04:41-0600 [-] gitpoller: finished initializing working dir from git://github.com/buildbot/pyflakes.git at rev 1a4af6ec1dbb724b884ea14f439b272f30439e4d 1.1.4 Creating a slave Open a new terminal and enter the same sandbox you created before: cd cd tmp/buildbot source sandbox/bin/activate Install the buildslave command: easy_install buildbot-slave Now, create the slave: buildslave create-slave slave localhost:9989 example-slave pass The user:host pair, username, and password should be the same as the ones in master.cfg; verify this is the case by looking at the section for c[’slaves’] and c[’slavePortnum’]: cat master/master.cfg Now, start the slave: buildslave start slave 4 Chapter 1. Buildbot Tutorial BuildBot Documentation, Release 0.8.9 Check the slave’s log: tail -f slave/twistd.log You should see lines like the following at the end of the worker log: 2009-07-29 20:59:18+0200 [Broker,client] message from master: attached 2009-07-29 20:59:18+0200 [Broker,client] SlaveBuilder.remote_print(buildbot-full): message from master: attached 2009-07-29 20:59:18+0200 [Broker,client] sending application-level keepalives every 600 seconds Meanwhile, in the other terminal, in the master log, if you tail the log you should see lines like this: 2011-03-13 18:46:58-0700 [Broker,1,127.0.0.1] slave ’example-slave’ attaching from IPv4Address(TCP, ’127.0.0.1’, 41306) 2011-03-13 18:46:58-0700 [Broker,1,127.0.0.1] Got slaveinfo from ’example-slave’ 2011-03-13 18:46:58-0700 [Broker,1,127.0.0.1] bot attached 2011-03-13 18:46:58-0700 [Broker,1,127.0.0.1] Buildslave example-slave attached to runtests You should now be able to go to http://localhost:8010, where you will see a web page similar to: Click on the Waterfall Display link (http://localhost:8010/waterfall) and you get this: 1.1. First Run 5 BuildBot Documentation, Release 0.8.9 That’s the end of the first tutorial. A bit underwhelming, you say? Well, that was the point! We just wanted to get you to dip your toes in the water. It’s easy to take your first steps, but this is about as far as we can go without touching the configuration. You’ve got a taste now, but you’re probably curious for more. Let’s step it up a little in the second tutorial by changing the configuration and doing an actual build. Continue on to A Quick Tour. 1.2 First Buildbot run with Docker Docker (http://www.docker.io) is an tool that makes building and deploying custom environments a breeze. It uses lightweight linux containers (LXC) and performs quickly, making it a great instrument for the testing community. The next section includes a Docker pre-flight check. If it takes more that 3 minutes to get the ‘Success’ message for you, try the Buildbot pip-based first run instead. 1.2.1 Current Docker dependencies • Linux system, with at least kernel 3.8 and AUFS support. For example, Standard Ubuntu, Debian and Arch systems. • Packages: lxc, iptables, ca-certificates, and bzip2 packages • Local clock on time or slightly in the future for proper SSL communication • Download, launch and test docker is happy in your linux enviroment: mkdir tmp; cd tmp wget -O docker http://get.docker.io/builds/Linux/x86_64/docker-latest chmod 755 docker; sudo ./docker -d & sudo ./docker run -i busybox /bin/echo Success 6 Chapter 1. Buildbot Tutorial BuildBot Documentation, Release 0.8.9 1.2.2 Building and running Buildbot # Download Buildbot Dockerfile. wget https://raw.github.com/buildbot/buildbot/master/master/contrib/Dockerfile # Build the Buildbot container (it will take a few minutes
Load more

Recommended publications
  • Evaluation of WYSIWYG Extensions for Mediawiki
    Evaluation of WYSIWYG Extensions for Mediawiki Projektpraktikum aus Projekt- und Qualitätsmanagement 188.235 (im Ausmaß von 4 SWS) Betreuer: Dipl. – Ing. Dr. Wolfgang Aigner Florian Mayrhuber [email protected] November 2007 Table of Content 1. Wikis and Mediawiki ...................................................................................................................................................... 1 2. Motivation ............................................................................................................................................................................ 1 2.1. MediaWiki Markup ................................................................................................................................................ 1 2.2. More Userfriendly Approaches ....................................................................................................................... 1 3. Objectives and Structure .............................................................................................................................................. 2 4. WYSIWYG Editors ............................................................................................................................................................ 2 4.1. FCKeditor ................................................................................................................................................................... 2 4.2. Wikiwyg .....................................................................................................................................................................
    [Show full text]
  • Project Management Software March 2019
    PROJECT MANAGEMENT SOFTWARE MARCH 2019 Powered by Methodology CONTENTS 3 Introduction 5 Defining Project Management Software 6 FrontRunners (Small Vendors) 8 FrontRunners (Enterprise Vendors) 10 Runners Up 22 Methodology Basics 2 INTRODUCTION his FrontRunners analysis minimum qualifying score of 3.96 Tis a data-driven assessment for Usability and 3.91 for User identifying products in the Project Recommended, while the Small Management software market that Vendor graphic had a minimum offer the best capability and value qualifying score of 4.55 for Usability for small businesses. For a given and 4.38 for User Recommended. market, products are evaluated and given a score for Usability (x-axis) To be considered for the Project and User Recommended (y-axis). Management FrontRunners, a FrontRunners then plots 10-15 product needed a minimum of 20 products each on a Small Vendor user reviews published within 18 and an Enterprise Vendor graphic, months of the evaluation period. based on vendor business size, per Products needed a minimum user category. rating score of 3.0 for both Usability and User Recommended in both In the Project Management the Small and Enterprise graphics. FrontRunners infographic, the Enterprise Vendor graphic had a 3 INTRODUCTION The minimum score cutoff to be included in the FrontRunners graphic varies by category, depending on the range of scores in each category. No product with a score less than 3.0 in either dimension is included in any FrontRunners graphic. For products included, the Usability and User Recommended scores determine their positions on the FrontRunners graphic. 4 DEFINING PROJECT MANAGEMENT SOFTWARE roject management software and document management, as well Phelps organizations manage as at least one of the following: time and deliver projects on time, on tracking, budgeting, and resource budget and within scope.
    [Show full text]
  • Greater Customization of Ghci Prompt
    Greater customization of GHCi prompt Author: Nikita Sazanovich Mentor: Nikita Kartashov SPb AU, spring 2016 GHC[i] The Glasgow Haskell Compiler, or simply GHC, is a state-of-the-art, open source, compiler and interactive environment for the functional language Haskell. GHCi is GHC’s interactive environment. GHC is heavily dependent on its users and contributors. GHC Ticket #5850 Most shells allow arbitrary user customization of the prompt. The bash prompt has ​ numerous escape sequences for useful information, and if those aren't enough, it allows ​arbitrary command calls. GHCi should gain similar customization abilities. Ways to implement this may include: 1. addition of more escape sequences. 2. addition of a single extra escape sequence with one parameter (an external command call). 3. redesigning the :set prompt option to take a Haskell function. Implementing the feature 1. Haskell Language. 2. Looking for inspiration: bash escape sequences. 3. Understanding the GHC codebase. 4. Refactoring the existing GHC code. 5. Writing the code: parsing the prompt, lazy evaluation, cross-platform. 6. Testing the feature locally. Details: Parsing the prompt :set prompt "%t %w: ghci> " set prompt "%t %w: ghci> " prompt "%t %w: ghci> " "%t %w: ghci> " %t %w: ghci> q%w: ghci> %w: ghci> : ghci> qghci> ... Details: Lazy evaluation Eager evaluation. :set prompt "%t %w: ghci> " READ AND STORE IN PROMPT_STRING IF NEED_TO_PRINT_PROMPT THEN PARSE_AND_PRINT PROMPT_STRING Lazy evaluation. :set prompt "%t %w: ghci> " CREATE_FUNC MAKE_PROMPT = CURRENT_TIME + " " + CURRENT_DIRECTORY + ": ghci> " IF NEED_TO_PRINT_PROMPT THEN PRINT MAKE_PROMPT Details: Cross-platform getUserName :: IO String getUserName = do #ifdef mingw32_HOST_OS getEnv "USERNAME" `catchIO` \e -> do putStrLn $ show e return "" #else getLoginName #endif Contributing the patch to GHC ● Communicating with GHC developers.
    [Show full text]
  • Atlassian Is Primed to Widen Its Appeal Beyond IT
    Seth Agulnick, [email protected] REPORT Atlassian Is Primed to Widen Its Appeal Beyond IT Companies: CA, CRM, GOOG/GOOGL, HPE, IBM, JIVE, MSFT, NOW, ORCL, TEAM, ZEN February 11, 2016 Report Type: Initial Coverage ☐ Previously Covered Full Report ☐ Update Report Research Question: Will Atlassian’s workflow tools continue to grow quickly with software development teams while also expanding into new use cases? Summary of Findings Silo Summaries . Atlassian Corp. Plc’s (TEAM) tracking and collaboration tools, widely 1) Atlassian Software Users considered the best-in-class for software development, are gaining JIRA and Confluence are both effective tools for team traction among nontechnical teams. collaboration. JIRA can be customized to suit nearly any team’s development process, though setup is . The company’s two flagship products, JIRA and Confluence, are complicated. Confluence is much easier to use and slowly being rolled out in departments like human resources, sales, tends to be deployed more widely. Atlassian’s biggest customer support and product management. These represent a advantage is the way all of its software pieces work together. Atlassian products—which already are being much larger market than Atlassian’s traditional core in IT. branched out beyond software development—can grow . JIRA was praised for its flexibility and advanced customization even further with business teams. options, though the latter trait makes setup and maintenance a challenge. It has great potential for sales growth with any business 2) Users of Competing Software Three of these five sources said Atlassian’s JIRA is not team that needs to track numerous tasks through a multistage the right fit for every company.
    [Show full text]
  • Full Stack Developer / Architect London £470/Day Years of Experience: 17+ Latest Contract: Senior Full-Stack Developer, Leading Social Media App
    Full Stack Developer / Architect London £470/day Years of experience: 17+ Latest contract: Senior Full-stack Developer, Leading Social Media App. For the past 17 years, gaining exposure to cutting edge technologies and applying them to creative ends has been my passion. From the early Web to contemporary Interactive / New Media, I have been following a path which has brought more ambitious & challenging projects each time. Working with content from Film, TV, Visual Effects &Journalism and applying such as multi-platform storytelling, machine learning, gamification & altered reality, I have been involved in creating interactive experiences which entertain, inform & inspire. I am actively seeking projects which allow me to continue to expand my knowledge of cutting-edge technology and surpass past challenges in terms of creativity, scale and impact. Expertise - Interaction design, Full-Stack Application Architecture, Object Oriented Design Patterns, Relational Data Modelling, Proprietary Scripting Languages, Automation, Microservices - Natural Language Processing, Semantic Neural Networks & the employment of Ontologies (in particular SUMO) for Machine Learning - Development of proprietary suites of Tools & Frameworks for RAD in particular dealing with Abstract Data Types, Game-state Management, Multilingual Data, REST/API interactions, Content Creation, Editing & Delivery - R&D and Rapid Prototyping, Concept Development, Technical Writing for R&D credits, Project Specification - Project Management, Roll Out, Development Team Management,
    [Show full text]
  • Guide to Open Source Solutions
    White paper ___________________________ Guide to open source solutions “Guide to open source by Smile ” Page 2 PREAMBLE SMILE Smile is a company of engineers specialising in the implementing of open source solutions OM and the integrating of systems relying on open source. Smile is member of APRIL, the C . association for the promotion and defence of free software, Alliance Libre, PLOSS, and PLOSS RA, which are regional cluster associations of free software companies. OSS Smile has 600 throughout the World which makes it the largest company in Europe - specialising in open source. Since approximately 2000, Smile has been actively supervising developments in technology which enables it to discover the most promising open source products, to qualify and assess them so as to offer its clients the most accomplished, robust and sustainable products. SMILE . This approach has led to a range of white papers covering various fields of application: Content management (2004), portals (2005), business intelligence (2006), PHP frameworks (2007), virtualisation (2007), and electronic document management (2008), as well as PGIs/ERPs (2008). Among the works published in 2009, we would also cite “open source VPN’s”, “Firewall open source flow control”, and “Middleware”, within the framework of the WWW “System and Infrastructure” collection. Each of these works presents a selection of best open source solutions for the domain in question, their respective qualities as well as operational feedback. As open source solutions continue to acquire new domains, Smile will be there to help its clients benefit from these in a risk-free way. Smile is present in the European IT landscape as the integration architect of choice to support the largest companies in the adoption of the best open source solutions.
    [Show full text]
  • WHY USE a WIKI? an Introduction to the Latest Online Publishing Format
    WHY USE A WIKI? An Introduction to the Latest Online Publishing Format A WebWorks.com White Paper Author: Alan J. Porter VP-Operations WebWorks.com a brand of Quadralay Corporation [email protected] WW_WP0309_WIKIpub © 2009 – Quadralay Corporation. All rights reserved. NOTE: Please feel free to redistribute this white paper to anyone you feel may benefit. If you would like an electronic copy for distribution, just send an e-mail to [email protected] CONTENTS Overview................................................................................................................................ 2 What is a Wiki? ...................................................................................................................... 2 Open Editing = Collaborative Authoring .................................................................................. 3 Wikis in More Detail................................................................................................................ 3 Wikis Are Everywhere ............................................................................................................ 4 Why Use a Wiki...................................................................................................................... 5 Getting People to Use Wikis ................................................................................................... 8 Populating the Wiki................................................................................................................. 9 WebWorks ePublisher and Wikis
    [Show full text]
  • E-BUG TRACKING SYSTEM GUIDE: Mrs
    E-BUG TRACKING SYSTEM GUIDE: Mrs. Sathya Priya R1 R.B. Babu2, R. Marimuthu3, G. Gowtham4, V. Prakash5 1Assistant Professor, KSR Institute for Engineering and Technology, Tiruchengode. 2,3,4,5Department of Computer Science And Engineering, KSR Institute for Engineering and Technology, Tiruchengode. ABSTRACT This is the world of information. The ever-growing field Information Technology has its many advanced notable features which made it what it was now today. In this world, the information has to be processed, clearly distributed and must be efficiently reachable to the end users intended for that. Otherwise, we know it led to disastrous situations. The other coin of the same phase is it is absolutely necessary to know any bugs that are hither-to face by the end users. The project “e-bug tracking system” aims to provide the solution for that. The Bug Tracker can be made from any two types. The first one being the system side, the other being the services side. Our project deals with the second one. The paper is wholly dedicated to tracking the bugs that are hither- by arise. The administrator maintains the master details regarding to the bugs id, bugs type, bugs description, bugs severity, bugs status, user details. The administrator too has the authority to update the master details of severity level, status level, etc, modules of the paper. The administrator adds the users and assign them responsibility of completing the paper. Finally, on analysing the paper assigned to the particular user, the administrator can track the bugs, and it is automatically added to the tables containing the bugs, by order of severity and status.
    [Show full text]
  • Awesome Selfhosted - Software Development - Project Management
    Awesome Selfhosted - Software Development - Project Management Software Development - Project Management See also: awesome-sysadmin/Code Review Bonobo Git Server - Set up your own self hosted git server on IIS for Windows. Manage users and have full control over your repositories with a nice user friendly graphical interface. ( Source Code) MIT C# Fossil - Distributed version control system featuring wiki and bug tracker. BSD-2-Clause- FreeBSD C Goodwork - Self hosted project management and collaboration tool powered by Laravel & VueJS. (Demo, Source Code) MIT PHP Gitblit - Pure Java stack for managing, viewing, and serving Git repositories. (Source Code) Apache-2.0 Java gitbucket - Easily installable GitHub clone powered by Scala. (Source Code) Apache-2.0 Scala/Java Gitea - Community managed fork of Gogs, lightweight code hosting solution. (Demo, Source Code) MIT Go GitLab - Self Hosted Git repository management, code reviews, issue tracking, activity feeds and wikis. (Demo, Source Code) MIT Ruby Gitlist - Web-based git repository browser - GitList allows you to browse repositories using your favorite browser, viewing files under different revisions, commit history and diffs. ( Source Code) BSD-3-Clause PHP Gitolite - Gitolite allows you to setup git hosting on a central server, with fine-grained access control and many more powerful features. (Source Code) GPL-2.0 Perl GitPrep - Portable Github clone. (Demo, Source Code) Artistic-2.0 Perl Git WebUI - Standalone web based user interface for git repositories. Apache-2.0 Python Gogs - Painless self-hosted Git Service written in Go. (Demo, Source Code) MIT Go Kallithea - Source code management system that supports two leading version control systems, Mercurial and Git, with a web interface.
    [Show full text]
  • Bug Tracker Net Documentation
    Bug Tracker Net Documentation Piscatorial and platelike Jean-Pierre backwash rigorously and immerge his pup pausingly and qualmishly. Glaucescent and nicotinic Sayers meditates anachronistically and reregulating his Bruges redolently and unemotionally. Jurassic Miguel befool whitely while Stevie always dedicating his squeezers marauds unthankfully, he miring so monumentally. The targeted project issue date. The predefined values should put left alone. Default user preference to enable filtering based on issue severity. Your comment has been received. Mantis Bug Tracker REST API Postman. It might been released, settings, you create and wade a script. NET Framework XML classes to steep and manipulate the data assess them. Compare to other products or configurations, take their moment to browse these introductory docs. Try upgrading to the latest stable version. The consider of filter fields to buy per row. We erect not, schedules, an object will be flagged. Alternatively, hence, we to submit a report back soon please report cannot be displayed on to main window. Automate data source between Sheets and Tracker. NET, remainder of the bugs are readable, their description etc in the cemetery of reports from time start time. It will no longer if possible login using this account. Then what problem behavior be solved more promptly. Someone hijacked my Google account. Kanban board for visualizing your project timeline. Default value list ON. The default value somewhere ON. Google users are affected. Specifies the LDAP or Active Directory server to key to. You can afford click the Updated column heading to which most recently updated issues at our top along the search results.
    [Show full text]
  • Modern Open Source Java EE-Based Process and Issue Tracker
    MASARYK UNIVERSITY FACULTY}w¡¢£¤¥¦§¨ OF I !"#$%&'()+,-./012345<yA|NFORMATICS Modern open source Java EE-based process and issue tracker DIPLOMA THESIS Monika Gottvaldová Brno, 2014 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Monika Gottvaldová Advisor: doc. RNDr. Tomáš Pitner, Ph.D. ii Acknowledgement I would like to thank Ing. OndˇrejŽižka for his advice and help during the creation of this thesis. iii Abstract This thesis deals with the topic concerning issue tracking systems, their functionality and features. It compares several issue tracking systems, their advantages and disadvantages. It describes a development of such a sys- tem and the use of modern Java EE technologies – JPA, Wicket, and CDI. The main motivation for creating a new issue tracking system and the sub- sequent development is also described. The thesis analyses its basic design and implementation. iv Keywords Issue tracking system, Wicket, modern Java EE, issue, bug, workflow, cus- tomization v Contents 1 Introduction ...............................1 2 Issue Tracking Systems ........................3 2.1 Bugzilla . .4 2.2 Trac . .6 2.3 JIRA . .7 2.4 Mantis . .8 2.5 BugTracker.NET . .9 2.6 Redmine . 10 2.7 FogBugz . 11 3 Analysis of Relevant Processes in Red Hat ............. 14 3.1 RHEL 6 QE . 14 3.1.1 Process Phases Description . 14 3.1.2 Bugzilla Process . 15 3.2 Fedora QE . 16 3.2.1 Process Phases Description .
    [Show full text]
  • Rootcore < Atlascomputing < Twiki
    Table of Contents RootCore.............................................................................................................................................................1 Introduction........................................................................................................................................................2 If Something Goes Wrong......................................................................................................................2 Individual Build Commands.............................................................................................................................4 Setting up RootCore................................................................................................................................4 Setting up Root on Lxplus and Tier 3 Sites......................................................................................5 Setting up RootCore on MacOS.......................................................................................................5 Compilation Commands.........................................................................................................................5 Package Management.............................................................................................................................6 Code Commit and Tag Creation.......................................................................................................8 Miscellaneous Commands......................................................................................................................8
    [Show full text]