# Multiple images with same MENDER\_ARTIFACT\_NAME

**URL:** <https://hub.mender.io/t/multiple-images-with-same-mender-artifact-name/7438>\
**Category:** General Discussions\
**Tags:** yocto, mender-server, tegra\
**Created:** [January 8, 2025, 8:24am UTC](https://hub.mender.io/t/multiple-images-with-same-mender-artifact-name/7438 "2025-01-08T08:24:05Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mwestgaard](https://avatars.discourse-cdn.com/v4/letter/m/a9a28c/32.png) [@mwestgaard](https://hub.mender.io/u/mwestgaard)\
**Post date:** [January 8, 2025, 8:24am UTC](https://hub.mender.io/t/multiple-images-with-same-mender-artifact-name/7438/1 "2025-01-08T08:24:05Z")

</div>

Hi,

We are currently doing changes to our BSP, these changes are purely on a hardware level, and we want to install the same image on these devices.

After reading some posts on this forum I get the impression that we can build two different artifacts, one for each BSP (and thus different device type) but with the same image, and keep the MENDER\_ARTIFACT\_NAME the same. Then we should be able to upload these two artifact to Mender, and the web UI should show it as 1 release. Forum posts I’m basing this on:

> [@Image with multiple device types](https://hub.mender.io/t/image-with-multiple-device-types/3570):
>
> Hi, We are running Mender / Yocto on jetson TX2 based on meta-tegra. We are currently facing the situation where we need to have a split in our fleet. Some of them will be running on Warrior and others will be running on Dunfell. Currently meta-tegra / mender doesn’t support branche rootfs updates due to partition layout changes more details [here](https://github.com/OE4T/meta-mender-community/issues/14#issue-860449752). How can I prevent mender from upgrading machines that are running on warrior ? I was planning to create a new device type eg TX2-V2. Is it possible…

> [@Question on multi device Mender artifacts](https://hub.mender.io/t/question-on-multi-device-mender-artifacts/3273):
>
> Hi, I’m using Mender with Yocto and have several machines and images. On the Mender server this results in one artifact for each machine/image combination, which can grow pretty fast. I wanted to reduce the amount of artifacts by grouping machine/image combinations into one artifact. Short version of the question: From the artifacts documentation I read I can specify several machines for one artifact (but they have to be compatible), but an artifact can only hold one image. Is that correct? …

Is this supposed to work as I think it is?

I.e. we can upload several images with the same artifact name as long as the device type and actual file name is different, Mender will treat it as one Release in the web UI, and install the correct image based on the device type when doing a OTA update.

The problem we are seeing with this is that I get the following error in the web UI when trying to access this release from the Releases tab:

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/mender/original/2X/f/f6170d06c1ebd98baa12861773d089640f27d6cd.png)

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [January 8, 2025, 2:12pm UTC](https://hub.mender.io/t/multiple-images-with-same-mender-artifact-name/7438/2 "2025-01-08T14:12:54Z")

</div>

Hi @mwestgaard,

Yes, it works exactly as you expect. What your screenshot is showing is actually an unrelated bug concerning accessing uploaded releases. It already has a fix in the pipeline, but no timeline that I can commit to yet, sorry.

I’ll keep you posted once I learn something new on this.

Greetz,  
Josef

---

<div class="post-metadata">

**Author:** ![mwestgaard](https://avatars.discourse-cdn.com/v4/letter/m/a9a28c/32.png) [@mwestgaard](https://hub.mender.io/u/mwestgaard)\
**Post date:** [January 8, 2025, 2:45pm UTC](https://hub.mender.io/t/multiple-images-with-same-mender-artifact-name/7438/3 "2025-01-08T14:45:59Z")

</div>

Thanks @TheYoctoJester!  
Then we will ignore this error for now.
