From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 7026321669488640000 X-Received: by 2002:adf:f7d2:: with SMTP id a18mr22425225wrq.354.1637167177459; Wed, 17 Nov 2021 08:39:37 -0800 (PST) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a1c:1943:: with SMTP id 64ls162813wmz.0.gmail; Wed, 17 Nov 2021 08:39:36 -0800 (PST) X-Google-Smtp-Source: ABdhPJyziaQB1VqrB5hYH6LuRRCwHEXlMMXmNOJLGDDs4kPEzKqC3IvQ5bCels6lcdoObNWU4+10 X-Received: by 2002:a1c:cc0f:: with SMTP id h15mr1208326wmb.37.1637167176532; Wed, 17 Nov 2021 08:39:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1637167176; cv=none; d=google.com; s=arc-20160816; b=Eqz0qGSNFND5GPd33Ait5kTVlSWZJMVQFREsYbMjt6Dyi3P2ptFR69P4Pzz0jo5Tkq 4L62se6GZ/wJHDPUPdlbuMYYxCVHWHvbPtRF1RzNilQU8nuTxcXUz9G3jHUjiuDlOM7A kKX7GsJ7LGrOAHlTziuVUIzkkaQY5blvQX+1dSgrEukgZs6+MqrZjmKyqfYD3t4ZvOSa RkfsqXlvT0uT9MiRaU5S2Y75stDwYlwtMpfkwzvHRyZn8meiKAaPcYHlmwJn/SgcHuxJ YJkQD2CUyy5G7GjBWYgOEVzWSGN3pyfvBgZnqp+gAjpbq6z/21keJHK1pMKvz7CiWzBO qdNw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :mail-followup-to:message-id:subject:cc:to:from:date; bh=SSOcMmL1ZcsE6NUttMCbIK92PpN9rGcR2PTusVOoANw=; b=ZuBRsmIdx9jhJNI6U4XiXjLMm0aWerCOvIlUKWGnH0WuOGn96B/r8Bk2V3KoxEQO9e 2BV1I91NSbmYTl/6EmEyly9EXaj+TtFrVyIbf/eKxXv4GuYK93vt/RUWDJp76NY8v1Fc itOhQP9AiSxVrmbl4TNN8Xhge5SpE5pTA3h5uidJ0WnbSM5+tdig886WAZh50wlMV5q/ oUOfoD6rOSHlWCnwYh4oR3oZNFW3b3BzOsBUg6Fxlpe0fH6+Lhwab9Z9zZHUu9B9CutO YBd9eJpRtabFhExJaltcmEVyO57aH7Ga2La8ycwZ77kUJHnhHZm8QKaoOyBZEk+SQKAb IIvg== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Return-Path: Received: from shymkent.ilbers.de (shymkent.ilbers.de. [85.214.156.166]) by gmr-mx.google.com with ESMTPS id 201si22438wma.1.2021.11.17.08.39.36 for (version=TLS1_2 cipher=ECDHE-ECDSA-CHACHA20-POLY1305 bits=256/256); Wed, 17 Nov 2021 08:39:36 -0800 (PST) Received-SPF: neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) client-ip=85.214.156.166; Authentication-Results: gmr-mx.google.com; spf=neutral (google.com: 85.214.156.166 is neither permitted nor denied by best guess record for domain of ibr@radix50.net) smtp.mailfrom=ibr@radix50.net Received: from yssyq.m.ilbers.de (host-80-81-17-52.static.customer.m-online.net [80.81.17.52]) (authenticated bits=0) by shymkent.ilbers.de (8.15.2/8.15.2/Debian-8) with ESMTPSA id 1AHGdKka012575 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 17 Nov 2021 17:39:35 +0100 Date: Wed, 17 Nov 2021 17:39:19 +0100 From: Baurzhan Ismagulov To: isar-users@googlegroups.com Cc: "Moessbauer, Felix" , Anton Mikanovich , "henning.schild@siemens.com" , "Schmidt, Adriaan" Subject: Re: [PATCH v4 0/2] Improve handling of ISAR_RELEASE_CMD Message-ID: <20211117163919.GA22100@yssyq.m.ilbers.de> Mail-Followup-To: isar-users@googlegroups.com, "Moessbauer, Felix" , Anton Mikanovich , "henning.schild@siemens.com" , "Schmidt, Adriaan" References: <20211104110507.2358692-1-felix.moessbauer@siemens.com> <4bf7b75d-f431-9a07-96f0-a1168af073d3@ilbers.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on shymkent.ilbers.de X-TUID: LNQSCmX0uGOd On Wed, Nov 17, 2021 at 03:57:53PM +0000, Moessbauer, Felix wrote: > > Default ISAR_RELEASE_CMD can be found in meta/classes/image.bbclass as: > > ISAR_RELEASE_CMD_DEFAULT = "git -C ${LAYERDIR_core} describe --tags -- > > dirty --match 'v[0-9].[0-9]*'" > > which results in something like `v0.7-534-g6752a45` This issue is reproduced > > inside Jenkins only, but not locally or in gitlab/kas. > > Then it's likely that Jenkins modifies files in the source tree. > One thing you could try is to explicitly make the git "dirty", or simply try a static ISAR_RELEASE_CMD. > > Anyways, how should we proceed here? This does point to some environment issue around our CI. That said, as yet I doubt it's specifically Jenkins. I also think that in any case, we should understand what is going on. As the issue is only reproducible on our side, I suggest that we look at it tomorrow and let you know. With kind regards, Baurzhan.