[TRTLLM-17014][infra] migrate build artifacts to artifactory.nvidia.com

[sharabeshj-nvda]

Publish build_info.txt, the packaged builds (*.tar.gz) and waive_list/ to sw-tensorrt-llm-generic-local on artifactory.nvidia.com instead of sw-tensorrt-generic on urm.nvidia.com, and read them from there first.

• Readers fall back to urm only when a file is absent (HTTP 404), so builds published before the switch stay readable. A rejected credential fails fast with a message that names the credential, and never falls back.
• jenkins/scripts/fetch_build_artifact.sh is the read helper for the pipelines, the Slurm launcher, the image build and BOLT profile generation; jenkins/scripts/check_artifactory_access.sh checks the CI identities in each environment.
• LLM_ARTIFACTS_PRIMARY=urm on the Jenkins controllers returns publishing and first reads to urm without a code change. A parent pipeline passes its value to the jobs it starts.
• Build reuse copies within one instance, and rebuilds when the earlier build is only on the other one.
• While under test, jenkins/L0_MergeRequest.groovy loads trtllm-jenkins-shared-lib from the branch of the library change that adds the artifactory.nvidia.com destination to uploadArtifacts.
• specs/001-migrate-builds-aws-artifactory/ carries the design documents for review while the pull request is a draft. They are removed before it is marked ready.

@coderabbitai summary

Description

Test Coverage

PR Checklist

Please review the following before submitting your PR:

• PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.

• PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.

• Test cases are provided for new code paths (see test instructions)

• If PR introduces API changes, an appropriate PR label is added - either api-compatible or api-breaking. For api-breaking, include BREAKING in the PR title.

• Any new dependencies have been scanned for license and vulnerabilities

• CODEOWNERS updated if ownership changes

• Documentation updated as needed

• Update tava architecture diagram if there is a significant design change in PR.

• The reviewers assigned automatically/manually are appropriate for the PR.

• Please check this after reviewing the above items as appropriate for this PR.

GitHub Bot Help

To see a list of available CI bot commands, please comment /bot help.

[sharabeshj-nvda]

/bot run

[tensorrt-cicd]

PR_Github #78560 [ run ] triggered by Bot. Commit: 950dc53 Link to invocation

[tensorrt-cicd]

PR_Github #78560 [ run ] completed with state FAILURE. Commit: 950dc53

Link to invocation

[sharabeshj-nvda]

/bot run

[tensorrt-cicd]

PR_Github #78588 [ run ] triggered by Bot. Commit: fddf303 Link to invocation

[tensorrt-cicd]

PR_Github #78588 [ run ] completed with state FAILURE. Commit: fddf303
/LLM/main/L0_MergeRequest_PR pipeline #64744 completed with status: 'FAILURE'

CI Report

⚠️ Action Required:

• Please check the failed tests and fix your PR
• If you cannot view the failures, ask the CI triggerer to share details
• Once fixed, request an NVIDIA team member to trigger CI again

CI Agent Failure Analysis

Link to invocation