Skip to content

Conversation

@Alexey-Rivkin
Copy link
Contributor

@Alexey-Rivkin Alexey-Rivkin commented Oct 28, 2025

What?

Consolidates NIXL build procedures by using contrib/Dockerfile multi-stage build for both CI and customer workflows.

Why?

  • Alignment: CI now uses the same Docker image build process as customers
  • Consolidation: Single source of truth for NIXL builds across all environments

How?

Multi-stage Dockerfile

  1. Stage 1 (nixl-base): Dependencies (libfabric, etcd, aws-sdk, DOCA, rust)
  2. Stage 2 (nixl-build): UCX and NIXL compilation (default target)

CI Changes

  • Jenkins uses ci-demo auto-build with Harbor registry caching
  • build.sh simplified to NIXL-only compilation

Backward Compatibility

  • build-container.sh unchanged, defaults to full build

@github-actions
Copy link

👋 Hi Alexey-Rivkin! Thank you for contributing to ai-dynamo/nixl.

Your PR reviewers will review your contribution then trigger the CI to test your changes.

🚀

@Alexey-Rivkin
Copy link
Contributor Author

/build

@Alexey-Rivkin
Copy link
Contributor Author

/build

Consolidates NIXL build procedures by using contrib/Dockerfile
multi-stage build for both CI and customer workflows.

Signed-off-by: Alexey Rivkin <[email protected]>
Signed-off-by: Alexey Rivkin <[email protected]>
Signed-off-by: Alexey Rivkin <[email protected]>
Signed-off-by: Alexey Rivkin <[email protected]>
@Alexey-Rivkin
Copy link
Contributor Author

/build

Signed-off-by: Alexey Rivkin <[email protected]>
@Alexey-Rivkin
Copy link
Contributor Author

/build

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.

2 participants