Ni package Builder requires TSENV with relativ paths !

[MaximeR]

hello,

i'm using environment for my TS Bench. The file generated by TestStand when creating my tsenv file store absolute path.

When trying to use this tsenv file in NI Package Builder, I have a message saying that I must have a relatov path.

I need to edit the tsenvs file by myself in a notepad application to be able to use it !!!!

Do I really to do that or it's just don't work ?

For info, I'm using TestStand 2022 Q4 and NI Package Builder 2022 Q3 Patch 1 both in 32 bits

[Oli_Wachno]

Maxime,

Unfortunately, TestStand creates tsenv files always using absolute paths. 

Cheers 

Oli

[MaximeR]

Thnaks for your reply. It just looks crazy!

How is it possible that NI is not able to allow direct interaction between software. tsenv with relativ folder is working in TS, but I don't have to do it by myself.

TestStand and Package Builder have to support the default behavior at first point.

[Scott_Richardson]

Maxime -

I do not know why NI Package Builder has this limitation, but I suspect it was required for NIPB to properly support TestStand environment files. I have captured this as something to investigate in the future. Thank you for sharing this feedback.

For customers that rarely change the environment file between deployments, creating a static copy to include in deployments would be an available mitigation, and if not, scripting something to modify the file prior to build might be possible.

[MaximeR]

Hi Scott,

Thanks again for your quick reply.

So it's a bug because it doesn't work with files generated by TestStand so it doesn't support properly TS Envirnment files.
Does someone tested it ? Have you planend to create an issue about that ?

If this option is global to NIPB and not from each solution, it's an issue too. I didn't test it.

I refer to my Idea Exchange about configuration specific for each and not global to NIPB.

Best regards.