On Montag, 27. Mai 2024, 12:10:31 CEST Dan Čermák wrote:

Hi Johannes,

On May 24, 2024 11:39:52 PM GMT+02:00, Johannes Kastl wrote:

...

Hi all,

when building containers, one can use #!RemoteAssetUrl: together with the download_assets service, so OBS downloads the files when uploading a new package version.

Very handy, but one thing seems to not work:

Can I use variables or RPM macros in the URLs? If so, how?

I can use prjconf to set docker build args aka "ARG". Would be great if this worked for the assets, too...

I think this is conceptually problematic as macros can be set on a repository basis, but that would mean that you end up with potentially different assets per repo.

indeed. It could work in theory for things like architectures, where we know mostly all of possible values and can execute the download for each of them. But zero chance for a free text variable... -- Adrian Schroeter Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev

Good evening Dan, On 27.05.24 12:10 Dan Čermák wrote:

On May 24, 2024 11:39:52 PM GMT+02:00, Johannes Kastl wrote:

...

Can I use variables or RPM macros in the URLs? If so, how?

I can use prjconf to set docker build args aka "ARG". Would be great if this worked for the assets, too...

I think this is conceptually problematic as macros can be set on a repository basis, but that would mean that you end up with potentially different assets per repo.

That was the idea. Having separate projects for e.g. different versions of a software. I can use ARG for setting things like that in a Dockerfile, but if this does not work with the remote assets, then this might pull in the wrong version of e.g. a file. Kind Regards, Johannes