From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6667884636140470272 X-Received: by 2002:a19:c502:: with SMTP id w2mr2638116lfe.15.1552487871133; Wed, 13 Mar 2019 07:37:51 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:9799:: with SMTP id y25ls253315lji.11.gmail; Wed, 13 Mar 2019 07:37:50 -0700 (PDT) X-Google-Smtp-Source: APXvYqy0l7nkUyTRJvIMeL17h1K7cdqo2ofoOYPt3YRucFAiUm5uoPOaSwhXfwq8fBfA6lQdLazw X-Received: by 2002:a2e:91c4:: with SMTP id u4mr2490198ljg.29.1552487870474; Wed, 13 Mar 2019 07:37:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1552487870; cv=none; d=google.com; s=arc-20160816; b=Rxs6nMWGeduo8HHExKQXNaCUyxgrQg8hnEVF4efOHlGf1eo2sOD5dOsfk0HVheB8FZ JaUKYmGUJWgLW1ceyoGWuS8CWvddW/MsM8iAsQ9pJxKRpsW3zl9AK642TjbZZ+Bv93oF CJadeglorpLyvpnEIkLC1Zm4QrNBfZEgpN3ROkQl7vm5swCHCxn/xNOpYdUPm5ZDhDiu saclUzMSkDV8CLKcUaJuKZuyIXyg56ydGaBaudsEWIuWTtXNjFLcN4RQPUAmrJfoKCAr Buryt+SfgXzTov0PE3ywv7zw7xDAF7PKQnbBjSwSrO4YpzwvHTvonBcV0y8KLVPFrU6m gmew== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:mime-version:user-agent :date:message-id:subject:from:to; bh=kaaFYxsGcL1+9r+koXFztX/4J6BuslZ1VZhsr7KjP4s=; b=X4tRyggho/9rDhFPGMz6kVN/1vciPu8OUwCYYj5twKI/WAMxK3y0TFCl+vwQjxn/9+ KW9hkb9s0BaIvyuhzMg2fSWOI7jCKTXu1hHmtW19M5rAC8USLLI05ZY8xCpl6m2tmjj7 1iw5EpnoWZ+c/IpNCWcxReSO7+tVIdJYN1PeeRZPXzJ/zbaGXkh4hS0tWks9Gybk63MS 8BfQ3jBhY4opsZsij7D7zdOf5LwvJLmI1lJEuygideIKDbJC1O3dDgOSL/HGlk+WQjNz v7vkJ8hYoNzxtdDo1xiBlabms5ZxfGW1F8W2oWhKPa7DMaANG63sE+oTjQg/AOxTgxFu puWw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id i21si63571ljj.0.2019.03.13.07.37.50 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Mar 2019 07:37:50 -0700 (PDT) Received-SPF: pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of claudius.heine.ext@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=claudius.heine.ext@siemens.com Received: from mail2.sbs.de (mail2.sbs.de [192.129.41.66]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id x2DEbnUv031742 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Wed, 13 Mar 2019 15:37:49 +0100 Received: from [139.25.69.232] (linux-ses-ext02.ppmd.siemens.net [139.25.69.232]) by mail2.sbs.de (8.15.2/8.15.2) with ESMTP id x2DEbnTE028589 for ; Wed, 13 Mar 2019 15:37:49 +0100 To: isar-users From: Claudius Heine Subject: [RFC] Define task pipeline Message-ID: Date: Wed, 13 Mar 2019 15:37:49 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: WwFDkJW7yIJL Hi, I opened an issue for discussion on the github issue tracker[1]. Please post comments there. Here is the content for reference: Currently we don't have a clearly define pipeline of the tasks, especially for image recipes. This makes it difficult to introduce new tasks that should be run at certain points of the build process. For image recipes I would like to propose the following pipeline: 1. `do_rootfs` a (virtual) task after which the `rootfs` directory contains the desired root file system with all packages installed, etc. 2. `do_rootfs_postprocess` a (virtual) task after which all post processing steps that can not be defined in a package are done. 3. `do_image` a virtual task after which the images are created in the work directory of the image. 4. `do_deploy` a (virtual) task after which the output artifacts of the recipe are deployed to the deploy directory. 5. `do_build` a virtual task that defines the default build process. This way it should be simpler to order custom and currently implemented task better into the structure. Hopefully lines like these ``` addtask ubi_image before do_build after do_copy_boot_files do_install_imager_deps do_unpack do_transform_template ``` can be reduced to this ``` addtask ubi_image before do_image after do_rootfs_postprocess ``` I have not looked into optimizing the package build pipeline and other recipe types. [1] https://github.com/ilbers/isar/issues/46 -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de