Skip to content

Updated .release:staging to stage device-plugin images in nvstaging#1230

Merged
cdesiniotis merged 1 commit intoNVIDIA:mainfrom
JunAr7112:migrate_ngc_changes
Apr 14, 2025
Merged

Updated .release:staging to stage device-plugin images in nvstaging#1230
cdesiniotis merged 1 commit intoNVIDIA:mainfrom
JunAr7112:migrate_ngc_changes

Conversation

@JunAr7112
Copy link
Contributor

In order to publish projects with NGC Publishing Configs, the images will need to be staged in the nvstaging registry. This change updates the variables in .release:staging to refer to the NGC registry.

@copy-pr-bot
Copy link

copy-pr-bot bot commented Apr 10, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@JunAr7112 JunAr7112 force-pushed the migrate_ngc_changes branch from 039730a to 23cd8aa Compare April 10, 2025 21:11
@JunAr7112 JunAr7112 changed the title Updated .release:staging to stage device-plugin images in the nvstaging registry Updated .release:staging to stage device-plugin images in nvstaging Apr 10, 2025
@cdesiniotis
Copy link
Contributor

cdesiniotis commented Apr 10, 2025

@JunAr7112 the DCO is failing. Please sign off your commit.

Copy link
Contributor

@tariq1890 tariq1890 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

.common-ci.yml Outdated
OUT_REGISTRY_USER: "${NGC_REGISTRY_USER}"
OUT_REGISTRY_TOKEN: "${NGC_REGISTRY_TOKEN}"
OUT_REGISTRY: "${NGC_REGISTRY}"
OUT_IMAGE_NAME: "${NGC_REGISTRY_STAGING_IMAGE}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: should this be:

Suggested change
OUT_IMAGE_NAME: "${NGC_REGISTRY_STAGING_IMAGE}"
OUT_IMAGE_NAME: "${NGC_REGISTRY_STAGING_IMAGE_NAME}"

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we have checks in place to ensure that OUT_IMAGE_NAME is not set? Can we repeat the check we do for the OUT_IMAGE_VERSION:

'echo Version: ${OUT_IMAGE_VERSION} ; [[ -n "${OUT_IMAGE_VERSION}" ]] || exit 1'

to ensure that we don't run this with an empty image name?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alright, I added a check for OUT_IMAGE_NAME as well.

@JunAr7112 JunAr7112 force-pushed the migrate_ngc_changes branch 2 times, most recently from 531acd2 to 07d4cb5 Compare April 14, 2025 17:22
Signed-off-by: Arjun <arjun.gadiyar@gmail.com>
@JunAr7112 JunAr7112 force-pushed the migrate_ngc_changes branch from 07d4cb5 to 099def1 Compare April 14, 2025 17:26
@cdesiniotis
Copy link
Contributor

/ok to test

@copy-pr-bot
Copy link

copy-pr-bot bot commented Apr 14, 2025

/ok to test

@cdesiniotis, there was an error processing your request: E1

See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/1/

@cdesiniotis
Copy link
Contributor

/ok to test 099def1

@cdesiniotis cdesiniotis merged commit bafe5af into NVIDIA:main Apr 14, 2025
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants