From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=96.73.9.1; helo=muon.bluestop.org; envelope-from=rebecca@bluestop.org; receiver=edk2-devel@lists.01.org Received: from muon.bluestop.org (muon.bluestop.org [96.73.9.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 0200821191F29 for ; Tue, 27 Nov 2018 14:23:49 -0800 (PST) Received: from muon.bluestop.org (localhost [127.0.0.1]) by muon.bluestop.org (Postfix) with ESMTP id 54CF930920; Tue, 27 Nov 2018 15:24:36 -0700 (MST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluestop.org; s=mail; t=1543357476; bh=dBBTbxu2HUWYqhdQCK9+/e6o0PKb8PPp2DE/CQkaIKE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=guoxIpKFLePsbj6xKQ3onebvq4Ts6djJQ5CPQSuoDNW2ecXQzHWjQSfeNDmCqWjtb S4t8oMhKFcHQxgWT7cWx6MP8CkJrPYvoKS/mXyZYmq3HVT5R1nfGeuEFqTic2Yrp6z 8x4OS+Pq6t2/Zul7zaBNKVLpBPjRm4OXWDS0D/aY= Received: from muon.bluestop.org ([127.0.0.1]) by muon.bluestop.org (muon.bluestop.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XXbkQ421ohTg; Tue, 27 Nov 2018 15:24:36 -0700 (MST) Received: from photon.int.bluestop.org (gw.bluestop.org [96.73.9.3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by muon.bluestop.org (Postfix) with ESMTPSA; Tue, 27 Nov 2018 15:24:36 -0700 (MST) From: Rebecca Cran To: edk2-devel@lists.01.org, Jeremiah Cox Date: Tue, 27 Nov 2018 15:23:48 -0700 Message-ID: <5160554.8gLySxXtyI@photon.int.bluestop.org> In-Reply-To: References: <4330857f-4e27-632f-6f82-6fc6ec636b2e@linux.intel.com> <01F0790E56F0534D8DCAD4AC5838792F618A554A@irsmsx111.ger.corp.intel.com> MIME-Version: 1.0 Subject: Re: [edk2-announce] Research Request X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2018 22:23:50 -0000 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Tuesday, 27 November 2018 14:16:18 MST Jeremiah Cox via edk2-devel wrote: > Do we have data on what it takes to deploy and operate Phabricator with > Harbormaster or Jenkins? The up front development/deployment > activity/costs and then also the ongoing patching/servicing/maintenance > costs? Is Intel planning to provide this? I haven't integrated Harbormaster or Jenkins, but for just Phabricator the patching/servicing has ben really simple for the year+ I've been running it. I'd not consider it 'production' since I'm the only person using it and I'm running from Git master, not a stable branch - but maintenance has been as simple as the following (which could of course be put in a script to reduce the number of steps!): # Stop the Phabricator daemon ./bin/phd stop # Update Phabricator git pull # Update libphputil cd ../libphputil && git pull # Upgrade arcanist (commandline interface) cd ../arcanist && git pull # Upgrade database schema ./bin/storage upgrade # Start Phabricator daemon ./bin/phd start # Reload web server service nginx restart service php-fpm restart The "storage upgrade" command goes through the database looking for any inconsistencies - missing keys, wrong data types etc., and offers to fix them. -- Rebecca