UBT containers use non-UBT package
Summary
As mentioned in !8855 (comment 2911112079) - currently when UBT packages are being built they do not seem to be used by Docker containers.
Looking at Build::Info.Docker.release_file_contents():
repo = Gitlab::Util.get_env('PACKAGECLOUD_REPO') # Target repository
download_urls = {}.tap do |urls|
urls[:amd64] = Build::Info::CI.package_download_url(job_name: 'Ubuntu-24.04')
urls[:arm64] = Build::Info::CI.package_download_url(job_name: 'Ubuntu-24.04', arch: 'arm64')
end
#...
contents << "DOWNLOAD_URL_amd64=#{download_urls[:amd64]}\n"
contents << "DOWNLOAD_URL_arm64=#{download_urls[:arm64]}\n"it sounds like packages are downloaded from PackageCloud, and since we didn't change name of the package for UBT pipelines - likely we're overwriting packages creating ambiguous situation.
Steps to reproduce
- Run Pipeline
- Trigger ee pipeline
- Trigger ee-ubt pipeline
What is the current bug behavior?
Docker containers for UBT and non-UBT containing the same package deployed.
What is the expected correct behavior?
We need differentiation between UBT and non-UBT containers and packages.