RE: [PATCH v3 1/2] always invoke ISAR_RELEASE_CMD to invalidate downstream tasks on change

["Schmidt, Adriaan" <adriaan.schmidt@siemens.com>]

Henning Schild, Mittwoch, 3. November 2021 19:16:
> Am Wed, 3 Nov 2021 15:09:56 +0100
> schrieb "Moessbauer, Felix (T RDA IOT SES-DE)"
> <felix.moessbauer@siemens.com>:
> 
> > Here, the deployed image contains the wrong tag.
> > When building with SState, even deleting the build/tmp folder does
> > not help as everything is already in the cache.
> 
> I know that case, where you build a second time for a tag ... That is a
> good example. While i would personally never build a release in a
> "rebuild" but always on a clean cache. BUT would expect a non-clean
> sstate cache to not cause harm.
> 
> To that point i guess we need a solution and it should be included in
> another round of the sstate series.
> If the solution is along the lines of this patch i would say that an
> API changelog entry will be needed, and maybe revisit the user manual
> what it has to say about the CMD.

I have tested this together with the sstate series, and I can confirm that the dependency on IMAGE_BUILD_ID is registered as expected, so in case the output of ISAR_RELEASE_CMD changes, the image will be rebuilt.

We could pull this into the sstate patches, but I think it's less confusing if we don't. And ideally merge this before the sstate series.

Adriaan