Publishing and NSPECT Pipeline Changes#53
Conversation
532d19d to
059feba
Compare
|
Thanks @JunAr7112! Let's merge this after either one of @cdesiniotis and @guptaNswati 's approvals |
elezar
left a comment
There was a problem hiding this comment.
As a comment. Does it make sense to switch to a single .nvidia-ci.yml file? (This does not have to block this PR thoug)
I was thinking to keep the nvidia-ci.yml and common-ci.yml separate just to maintain the same format as the other projects. |
rahulait
left a comment
There was a problem hiding this comment.
I see some issues with CI jobs as discussed internally. Lets get them addressed before merging this.
105479b to
d571e42
Compare
I updated this MR to resolve these issues. |
d571e42 to
0a07c2b
Compare
Signed-off-by: Arjun Gadiyar <agadiyar@nvidia.com>
0a07c2b to
e57cf67
Compare
This MR will add a Publishing/NSPECT jobs to the nvidia yaml for publishing. We will get rid of the current release job, and instead use the images that are pushed to staging for publishing.