Tags: NVIDIA/nvcf
Tags
feat(notary): import service and enable Bazel (#447) Import Notary under src/control-plane-services and add Bazel build, CI, Docker, NOTICE, runtime inventory, and OSRB integration. Align the shared Java runtime closure while preserving Maven/Bazel parity. Closes #446 Verified: - Maven baseline and Bazel build pass on Java 25. - All 63 tests and NOTICE/license checks pass. - Docker readiness, JWKS, and packaged JAR identity pass. Signed-off-by: Sanjay Saxena <sasaxena@nvidia.com>
feat(notary): import service and enable Bazel (#447) Import Notary under src/control-plane-services and add Bazel build, CI, Docker, NOTICE, runtime inventory, and OSRB integration. Align the shared Java runtime closure while preserving Maven/Bazel parity. Closes #446 Verified: - Maven baseline and Bazel build pass on Java 25. - All 63 tests and NOTICE/license checks pass. - Docker readiness, JWKS, and packaged JAR identity pass. Signed-off-by: Sanjay Saxena <sasaxena@nvidia.com>
feat(notary): import service and enable Bazel (#447) Import Notary under src/control-plane-services and add Bazel build, CI, Docker, NOTICE, runtime inventory, and OSRB integration. Align the shared Java runtime closure while preserving Maven/Bazel parity. Closes #446 Verified: - Maven baseline and Bazel build pass on Java 25. - All 63 tests and NOTICE/license checks pass. - Docker readiness, JWKS, and packaged JAR identity pass. Signed-off-by: Sanjay Saxena <sasaxena@nvidia.com>
feat(notary): import service and enable Bazel (#447) Import Notary under src/control-plane-services and add Bazel build, CI, Docker, NOTICE, runtime inventory, and OSRB integration. Align the shared Java runtime closure while preserving Maven/Bazel parity. Closes #446 Verified: - Maven baseline and Bazel build pass on Java 25. - All 63 tests and NOTICE/license checks pass. - Docker readiness, JWKS, and packaged JAR identity pass. Signed-off-by: Sanjay Saxena <sasaxena@nvidia.com>
fix(workers): pin Bazel version for the four worker subtrees (#433) The release image is built from an isolated subtree snapshot, where the subtree's own MODULE.bazel is the workspace root, so bazelisk resolves .bazelversion from the subtree and never sees the umbrella's root pin. The four worker subtrees ship no .bazelversion, so their release builds run whatever bazelisk considers latest: the worker-llm-credentials v1.0.6 release build downloaded Bazel 9.2.0 while the repo pins 9.1.1 and the other 15 releasable subtrees pin their own version. That makes those builds non-reproducible and lets an upstream Bazel release break them with no change in this repo. Pin all four to 9.1.1, matching the root .bazelversion. Same root cause as the missing subtree .bazelrc fixed in #432 (the snapshot does not carry umbrella root files); that PR covers .bazelrc for worker-llm-credentials only, so .bazelversion is still needed for all four. Verified: worker-utils builds clean under USE_BAZEL_VERSION=9.1.1 (bazel build //..., 2115 actions).
fix(workers): pin Bazel version for the four worker subtrees (#433) The release image is built from an isolated subtree snapshot, where the subtree's own MODULE.bazel is the workspace root, so bazelisk resolves .bazelversion from the subtree and never sees the umbrella's root pin. The four worker subtrees ship no .bazelversion, so their release builds run whatever bazelisk considers latest: the worker-llm-credentials v1.0.6 release build downloaded Bazel 9.2.0 while the repo pins 9.1.1 and the other 15 releasable subtrees pin their own version. That makes those builds non-reproducible and lets an upstream Bazel release break them with no change in this repo. Pin all four to 9.1.1, matching the root .bazelversion. Same root cause as the missing subtree .bazelrc fixed in #432 (the snapshot does not carry umbrella root files); that PR covers .bazelrc for worker-llm-credentials only, so .bazelversion is still needed for all four. Verified: worker-utils builds clean under USE_BAZEL_VERSION=9.1.1 (bazel build //..., 2115 actions).
fix(workers): pin Bazel version for the four worker subtrees (#433) The release image is built from an isolated subtree snapshot, where the subtree's own MODULE.bazel is the workspace root, so bazelisk resolves .bazelversion from the subtree and never sees the umbrella's root pin. The four worker subtrees ship no .bazelversion, so their release builds run whatever bazelisk considers latest: the worker-llm-credentials v1.0.6 release build downloaded Bazel 9.2.0 while the repo pins 9.1.1 and the other 15 releasable subtrees pin their own version. That makes those builds non-reproducible and lets an upstream Bazel release break them with no change in this repo. Pin all four to 9.1.1, matching the root .bazelversion. Same root cause as the missing subtree .bazelrc fixed in #432 (the snapshot does not carry umbrella root files); that PR covers .bazelrc for worker-llm-credentials only, so .bazelversion is still needed for all four. Verified: worker-utils builds clean under USE_BAZEL_VERSION=9.1.1 (bazel build //..., 2115 actions).
fix(workers): pin Bazel version for the four worker subtrees (#433) The release image is built from an isolated subtree snapshot, where the subtree's own MODULE.bazel is the workspace root, so bazelisk resolves .bazelversion from the subtree and never sees the umbrella's root pin. The four worker subtrees ship no .bazelversion, so their release builds run whatever bazelisk considers latest: the worker-llm-credentials v1.0.6 release build downloaded Bazel 9.2.0 while the repo pins 9.1.1 and the other 15 releasable subtrees pin their own version. That makes those builds non-reproducible and lets an upstream Bazel release break them with no change in this repo. Pin all four to 9.1.1, matching the root .bazelversion. Same root cause as the missing subtree .bazelrc fixed in #432 (the snapshot does not carry umbrella root files); that PR covers .bazelrc for worker-llm-credentials only, so .bazelversion is still needed for all four. Verified: worker-utils builds clean under USE_BAZEL_VERSION=9.1.1 (bazel build //..., 2115 actions).
feat(self-managed): bump nvcf-ui charts (#436) * chore(self-managed): bump nvcf-ui charts Signed-off-by: vrv3814 <vemireddyv@nvidia.com> * Update manifest.md Signed-off-by: vrv3814 <vemireddyv@nvidia.com> --------- Signed-off-by: vrv3814 <vemireddyv@nvidia.com>
fix(workers): pin Bazel version for the four worker subtrees (#433) The release image is built from an isolated subtree snapshot, where the subtree's own MODULE.bazel is the workspace root, so bazelisk resolves .bazelversion from the subtree and never sees the umbrella's root pin. The four worker subtrees ship no .bazelversion, so their release builds run whatever bazelisk considers latest: the worker-llm-credentials v1.0.6 release build downloaded Bazel 9.2.0 while the repo pins 9.1.1 and the other 15 releasable subtrees pin their own version. That makes those builds non-reproducible and lets an upstream Bazel release break them with no change in this repo. Pin all four to 9.1.1, matching the root .bazelversion. Same root cause as the missing subtree .bazelrc fixed in #432 (the snapshot does not carry umbrella root files); that PR covers .bazelrc for worker-llm-credentials only, so .bazelversion is still needed for all four. Verified: worker-utils builds clean under USE_BAZEL_VERSION=9.1.1 (bazel build //..., 2115 actions).
PreviousNext