From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alice Ferrazzi <alice.ferrazzi@miraclelinux.com>,
cip-dev@lists.cip-project.org
Subject: Re: [isar-cip-core][PATCH 02/11] Rename initrd with the gz suffix
Date: Mon, 15 Nov 2021 19:32:04 +0100 [thread overview]
Message-ID: <fc1d7cc4-680f-3f8e-599b-38c1d5d6bbc3@siemens.com> (raw)
In-Reply-To: <20211115161724.19516-3-alice.ferrazzi@miraclelinux.com>
On 15.11.21 17:17, Alice Ferrazzi wrote:
> Generated initrd are actually gz compressed and KernelCI need
> the initrd image filename to contain the gz suffix for work.
>
> Signed-off-by: Alice Ferrazzi <alice.ferrazzi@miraclelinux.com>
> ---
> scripts/deploy-kernelci.py | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/scripts/deploy-kernelci.py b/scripts/deploy-kernelci.py
> index 931504c..c2341a6 100755
> --- a/scripts/deploy-kernelci.py
> +++ b/scripts/deploy-kernelci.py
> @@ -18,6 +18,10 @@ extension=sys.argv[3]
>
> rootfs_filename="cip-core-image-"+extension+"-cip-core-"+release+"-"+target+".tar.gz"
> initrd_filename="cip-core-image-"+extension+"-cip-core-"+release+"-"+target+"-initrd.img"
> +
> +# initrd is actually gz compressed
> +initrd_gz_filename="cip-core-image-"+extension+"-cip-core-"+release+"-"+target+"-initrd.img.gz"
> +
> input_dir="build/tmp/deploy/images/"+target
> upload_path="/images/rootfs/cip/"+cdate+"/"+target+"/"
> rootfs=input_dir+"/"+rootfs_filename
> @@ -44,5 +48,5 @@ if os.path.exists(rootfs) and os.path.exists(initrd):
> print("uploading rootfs to KernelCI")
> upload_file(api, token, upload_path, rootfs, rootfs_filename)
> print("uploading initrd to KernelCI")
> - upload_file(api, token, upload_path, initrd, initrd_filename)
> + upload_file(api, token, upload_path, initrd, initrd_gz_filename)
> print("uploaded to: https://storage.staging.kernelci.org"+upload_path)
>
Why not fold that into patch 1 directly? Fixing new files right after
introducing them is not an optimal pattern.
Jan
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2021-11-15 18:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 16:17 [isar-cip-core][PATCH 00/11] cip-core-image-kernelci Alice Ferrazzi
2021-11-15 16:17 ` [isar-cip-core][PATCH 01/11] Deploy tarballs and initrd to kernelci Alice Ferrazzi
2021-11-15 16:17 ` [isar-cip-core][PATCH 02/11] Rename initrd with the gz suffix Alice Ferrazzi
2021-11-15 18:32 ` Jan Kiszka [this message]
2021-11-15 16:17 ` [isar-cip-core][PATCH 03/11] Add latest folder to the storage fileserver Alice Ferrazzi
2021-11-15 16:17 ` [isar-cip-core][PATCH 04/11] Create kernelci build step Alice Ferrazzi
2021-11-15 18:32 ` Jan Kiszka
2021-11-15 16:17 ` [isar-cip-core][PATCH 05/11] Ignore extension argument when not set Alice Ferrazzi
2021-11-15 18:36 ` Jan Kiszka
2021-11-15 16:17 ` [isar-cip-core][PATCH 06/11] Enable KernelCI build step also for arm and arm64 Alice Ferrazzi
2021-11-15 16:17 ` [isar-cip-core][PATCH 07/11] Create cip-core-image-kernelci Alice Ferrazzi
2021-11-15 18:49 ` Jan Kiszka
2021-11-15 16:17 ` [isar-cip-core][PATCH 08/11] Remove root password Alice Ferrazzi
2021-11-15 18:44 ` Jan Kiszka
2021-11-15 16:17 ` [isar-cip-core][PATCH 09/11] Set the profile for KernelCI Alice Ferrazzi
2021-11-15 16:17 ` [isar-cip-core][PATCH 10/11] dmesg.sh is needed " Alice Ferrazzi
2021-11-15 16:17 ` [isar-cip-core][PATCH 11/11] Upload to KernelCI production Alice Ferrazzi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fc1d7cc4-680f-3f8e-599b-38c1d5d6bbc3@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=alice.ferrazzi@miraclelinux.com \
--cc=cip-dev@lists.cip-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).