From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [143.182.124.21]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 3311BE006C2 for ; Wed, 5 Jun 2013 10:15:24 -0700 (PDT) Received: from azsmga002.ch.intel.com ([10.2.17.35]) by azsmga101.ch.intel.com with ESMTP; 05 Jun 2013 10:14:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.87,808,1363158000"; d="scan'208";a="251083608" Received: from unknown (HELO helios.localnet) ([10.252.121.228]) by AZSMGA002.ch.intel.com with ESMTP; 05 Jun 2013 10:14:46 -0700 From: Paul Eggleton To: "Dragomir, CalinX L" Date: Wed, 05 Jun 2013 18:14:44 +0100 Message-ID: <5116417.al1Mo7JSpa@helios> Organization: Intel Corporation User-Agent: KMail/4.10.2 (Linux/3.8.0-23-generic; KDE/4.10.2; i686; ; ) In-Reply-To: <27CEE5FF4D395E43B04459808802ADB7013EFFE0@IRSMSX106.ger.corp.intel.com> References: <27CEE5FF4D395E43B04459808802ADB7013EFFE0@IRSMSX106.ger.corp.intel.com> MIME-Version: 1.0 Cc: "Zhang, Jessica" , "webhob@yoctoproject.org" Subject: [Webhob] Django models X-BeenThere: webhob@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Jun 2013 17:15:24 -0000 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Hi Calin, On Wednesday 05 June 2013 11:23:57 Dragomir, CalinX L wrote: > I've updated the Django models information based on this. > The outcome is now limited only to these five options discussed. > Please find my changes here: > https://wiki.yoctoproject.org/wiki/Django_models Some feedback on the models: * I understand task_history is meant to capture where BitBake could have accelerated the task using sstate but was unable to for some reason. Can we have a choice field which indicates this directly (e.g. sstate_result - not applicable, unavailable, failed, restored)? * I agree we want to have a sequence number to allow us to easily show the order tasks ran in within the UI where needed (is that task_number in the current model? If so do we need the order field which is also listed?) * I wonder if task_type should instead be an boolean value indicating if the task executed or not; I can't think of any other value we'd want here that isn't already covered by task_outcome. * What is the "code" field? * "py_sh" should probably be named "script_type" or similar Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre