Add reproducible builds support in OHCL-Linux-Kernel by namancse · Pull Request #115 · microsoft/OHCL-Linux-Kernel

namancse · 2026-01-30T09:56:07Z

OHCL-Linux-Kernel has Microsoft/build-hcl-kernel.sh script which is used to build kernel. However, in build pipelines, that script is not used and similar code in pipeline code itself is used.
To implement reproducible builds, add this support in both local build script (Microsoft/build-hcl-kernel.sh) and the pipeline code. Instead of adding the support in pipeline directly, move the kernel build code from pipeline to a new script "Microsoft/build-hcl-kernel-pipeline.sh" and ad reproducible builds changes in it. With that, buddy/official pipeline would then call this script to build kernel.

saurabh-sengar

Can we upstream Linux kernel changes in this PR ?
Is there no way reproducibitly builds are supported by Linux kernel today ?
Ref: https://docs.kernel.org/kbuild/reproducible-builds.html

arch/arm64/kernel/vdso/Makefile

Microsoft/build-hcl-kernel-pipeline.sh

flake.nix

Copilot

Pull request overview

Adds Nix-based tooling and pipeline script refactors to support reproducible OHCL-Linux-Kernel builds, aligning local and CI build paths/metadata normalization.

Changes:

Introduces a Nix flake (flake.nix/flake.lock) to provide a pinned, reproducible kernel build environment.
Adds local helper scripts (Microsoft/nix-setup.sh, Microsoft/nix-build.sh, Microsoft/nix-clean.sh) to run builds in a fixed-path sandbox with reproducibility env vars.
Updates Microsoft/build-hcl-kernel.sh and adds Microsoft/build-hcl-kernel-pipeline.sh to normalize debug paths/versioning and reduce non-determinism (e.g., debuglink CRC).

Reviewed changes

Copilot reviewed 6 out of 7 changed files in this pull request and generated 14 comments.

Show a summary per file

File	Description
flake.nix	Defines Nix devShell/package/app for reproducible kernel build environment
flake.lock	Pins Nix inputs for reproducibility
Microsoft/nix-setup.sh	Bootstraps Nix + enables flakes for local reproducible workflow
Microsoft/nix-clean.sh	Cleans build artifacts for the Nix-based workflow
Microsoft/nix-build.sh	Runs local reproducible builds in a fixed build path and syncs outputs back
Microsoft/build-hcl-kernel.sh	Adds reproducibility flags (debug prefix map, LOCALVERSION, debuglink behavior) and cross-arch handling tweaks
Microsoft/build-hcl-kernel-pipeline.sh	New pipeline build script with optional Nix-based reproducible mode and artifact packaging

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-11T10:08:54Z

flake.nix

+            echo ""
+
+            # Export reproducible environment variables
+            # SOURCE_DATE_EPOCH is set by nix-build.sh before entering this shell


This comment says SOURCE_DATE_EPOCH is set by nix-build.sh before entering this shell, but nix-build.sh re-execs into nix develop and only sets SOURCE_DATE_EPOCH afterwards. Update the wording (or set SOURCE_DATE_EPOCH prior to nix develop) to avoid misleading users.

Suggested change

# SOURCE_DATE_EPOCH is set by nix-build.sh before entering this shell

# SOURCE_DATE_EPOCH is typically set by nix-build.sh (based on the git commit)

Copilot · 2026-03-11T10:08:54Z

Microsoft/build-hcl-kernel-pipeline.sh

+        # Clean and create fixed build path
+        rm -rf "${FIXED_BUILD_PATH}"
+        mkdir -p "${FIXED_BUILD_PATH}"
+


setup_fixed_build_path deletes ${FIXED_BUILD_PATH} via rm -rf without validating the path. Add a guard to ensure it’s a safe, expected temp directory (and refuse to remove /, empty, or unexpectedly short paths) to avoid accidental data loss when FIXED_BUILD_PATH is overridden.

Copilot · 2026-03-11T10:08:55Z

Microsoft/build-hcl-kernel-pipeline.sh

+cleanup_fixed_build_path() {
+    if [[ -n "$REPRODUCIBLE_BUILD" ]] && [[ -n "${FIXED_BUILD_PATH:-}" ]] && [[ -d "${FIXED_BUILD_PATH:-}" ]]; then
+        echo ">>> Cleaning up temporary build directory: ${FIXED_BUILD_PATH}"
+        rm -rf "${FIXED_BUILD_PATH}"
+    fi


The EXIT trap deletes ${FIXED_BUILD_PATH} via rm -rf without validating the path. Add a safety check (expected prefix/allowlist) so overriding FIXED_BUILD_PATH can’t accidentally remove an unrelated directory.

Copilot · 2026-03-11T10:08:55Z

flake.nix

+              SOURCE_DATE_EPOCH
+              LANG
+              LC_ALL
+              KBUILD_BUILD_TIMESTAMP
+              KBUILD_BUILD_USER
+              KBUILD_BUILD_HOST
+              KBUILD_BUILD_VERSION
+              TZ;
+


reproducibleEnv does not define SOURCE_DATE_EPOCH or KBUILD_BUILD_TIMESTAMP, but the derivation tries to inherit them. This will fail flake evaluation/build. Define these attributes (or remove them from the inherit list and compute SOURCE_DATE_EPOCH in Nix, e.g., from self.lastModified/src.lastModified).

Suggested change

SOURCE_DATE_EPOCH

LANG

LC_ALL

KBUILD_BUILD_TIMESTAMP

KBUILD_BUILD_USER

KBUILD_BUILD_HOST

KBUILD_BUILD_VERSION

TZ;

LANG

LC_ALL

KBUILD_BUILD_USER

KBUILD_BUILD_HOST

KBUILD_BUILD_VERSION

TZ;

# Compute reproducible timestamps within the derivation

SOURCE_DATE_EPOCH = builtins.toString self.lastModified;

KBUILD_BUILD_TIMESTAMP = SOURCE_DATE_EPOCH;

Copilot · 2026-03-11T10:08:55Z

Microsoft/nix-build.sh

+esac
+
+# Build configuration
+BUILD_OUTPUT="${BUILD_OUTPUT:-${KERNEL_ROOT}/build}"


BUILD_OUTPUT defaults to ${KERNEL_ROOT}/build (i.e., /tmp/ohcl-kernel-build/src/build), but build-hcl-kernel.sh writes to a sibling build dir ($LINUX_SRC/../build → /tmp/ohcl-kernel-build/build). As a result, the clean command won’t remove the actual build artifacts. Align BUILD_OUTPUT with the build script’s output location (e.g., ${FIXED_BUILD_PATH}/build) or plumb the path into build-hcl-kernel.sh.

Suggested change

BUILD_OUTPUT="${BUILD_OUTPUT:-${KERNEL_ROOT}/build}"

BUILD_OUTPUT="${BUILD_OUTPUT:-${FIXED_BUILD_PATH}/build}"

Copilot · 2026-03-11T10:08:56Z

Microsoft/build-hcl-kernel-pipeline.sh

+    make_args+=("ARCH=$KERNEL_ARCH")
+    make_args+=("LOCALVERSION=")
+    make_args+=("CC=$COMPILER")


LOCALVERSION= is forced for all builds, while build-hcl-kernel.sh only sets it in reproducible mode. If non-reproducible pipeline builds should preserve the default + suffix/version string behavior, make this conditional on --reproducible to avoid changing kernel release naming.

Copilot · 2026-03-11T10:08:57Z

Microsoft/nix-build.sh

+# Reproducible build environment
+# Always use timestamp of the top commit for SOURCE_DATE_EPOCH
+# Override any value set by Nix itself
+export SOURCE_DATE_EPOCH="$(git log -1 --pretty=%ct)"


SOURCE_DATE_EPOCH is computed via git log before cd-ing into the kernel repo. If the script is invoked from outside a git worktree, this will fail (and with set -e will abort). Use git -C "$KERNEL_ROOT_ORIGINAL" log -1 --pretty=%ct (or cd into KERNEL_ROOT_ORIGINAL first) to make it robust.

Suggested change

export SOURCE_DATE_EPOCH="$(git log -1 --pretty=%ct)"

export SOURCE_DATE_EPOCH="$(git -C "${KERNEL_ROOT_ORIGINAL}" log -1 --pretty=%ct)"

Copilot · 2026-03-11T10:08:57Z

Microsoft/nix-build.sh

+
+# Build configuration
+BUILD_OUTPUT="${BUILD_OUTPUT:-${KERNEL_ROOT}/build}"
+MAKE_JOBS="${MAKE_JOBS:-$(nproc)}"


MAKE_JOBS is computed but never used (the build uses build-hcl-kernel.sh, which hardcodes nproc). Either wire MAKE_JOBS through to the underlying make invocation or drop it to avoid misleading configuration knobs.

Suggested change

MAKE_JOBS="${MAKE_JOBS:-$(nproc)}"

Copilot · 2026-03-11T10:08:57Z

Microsoft/nix-build.sh

+cleanup_build_path() {
+    if [ -n "${FIXED_BUILD_PATH}" ] && [ -d "${FIXED_BUILD_PATH}" ]; then
+        log_info "Cleaning up temporary build directory: ${FIXED_BUILD_PATH}"
+        rm -rf "${FIXED_BUILD_PATH}"
+    fi


cleanup_build_path unconditionally rm -rfs whatever FIXED_BUILD_PATH is set to. A user could accidentally point this at a non-temporary directory and lose data. Add a safety guard (e.g., require it to match an expected prefix like /tmp/ohcl-kernel-build and refuse to delete /, empty, or very short paths).

Copilot · 2026-03-11T10:08:57Z

Microsoft/build-hcl-kernel-pipeline.sh

+if [[ -n "$REPRODUCIBLE_BUILD" ]]; then
+    # Always use timestamp of the top commit for SOURCE_DATE_EPOCH
+    # Override any pre-set value to ensure consistency
+    export SOURCE_DATE_EPOCH="$(git log -1 --pretty=%ct)"


SOURCE_DATE_EPOCH is computed with git log before the script cds into SOURCE_DIR (the cd happens later). If the pipeline’s working directory isn’t the kernel repo, this will fail. Use git -C "$SOURCE_DIR" log -1 --pretty=%ct (or cd "$SOURCE_DIR" before calling git).

Suggested change

export SOURCE_DATE_EPOCH="$(git log -1 --pretty=%ct)"

export SOURCE_DATE_EPOCH="$(git -C "$SOURCE_DIR" log -1 --pretty=%ct)"

Add NixOS flake configuration and helper scripts for reproducible kernel builds. Files added: - flake.nix: Nix environment with pinned toolchain (GCC 13.2.0, binutils, etc.) - flake.lock: Locked package versions for reproducibility - Microsoft/nix-setup.sh: One-time Nix installation helper - Microsoft/nix-clean.sh: Build artifact cleanup - .gitignore: Add Nix-related entries This establishes the foundation for bit-reproducible kernel builds across different machines by providing a hermetic build environment with pinned dependencies. Signed-off-by: Naman Jain <namjain@linux.microsoft.com>

Add nix-build.sh that orchestrates reproducible kernel builds using the Nix environment established in the previous commit. Features: - Pure Nix environment with --ignore-environment flag - Fixed build paths for reproducible absolute path embeddings - Reproducible environment variables: - SOURCE_DATE_EPOCH= timestamp of top git commit embedded - KBUILD_BUILD_USER=builder - KBUILD_BUILD_HOST=nixos - KBUILD_BUILD_VERSION=1 - Copies source to fixed path to ensure identical embedded paths - Invokes build-hcl-kernel.sh within the controlled environment - Copies artifacts back to original location - Cleanup on exit Usage: ./Microsoft/nix-build.sh x64 # Build x64 kernel ./Microsoft/nix-build.sh arm64 # Build arm64 kernel ./Microsoft/nix-build.sh x64 cvm # Build x64 cvm kernel ./Microsoft/nix-build.sh arm64 cvm # Build arm64 cvm kernel Signed-off-by: Naman Jain <namjain@linux.microsoft.com>

Enhance build-hcl-kernel.sh to support reproducible builds when invoked from nix-build.sh or other reproducible environments. Changes: - Detect host architecture to avoid unnecessary cross-compilation - Set CC explicitly to gcc/cross-compiler for Nix toolchain - Add LOCALVERSION= to prevent '+' suffix in version string - Add KCFLAGS=-fdebug-prefix-map to normalize debug paths - Add SHA256 checksum output of vmlinux for verification - Remove KBUILD_BUILD_ID=none (not needed) When REPRODUCIBLE_BUILD=1: - Uses Nix's gcc instead of system gcc for native builds - Only uses cross-compiler when actually cross-compiling - Ensures consistent compiler identification in kernel binary Otherwise, let users continue using this script for dev work as before. Signed-off-by: Naman Jain <namjain@linux.microsoft.com>

Add build-hcl-kernel-pipeline.sh for Azure DevOps CI integration with reproducible build support. Features: - Supports amd64 and arm64 architectures - CVM config merge support via merge_cvm_config() - Optional reproducible build mode (--reproducible flag) - Generates kernel, headers, modules, and debug symbols - Progress indicators for build stages [1/5] through [5/5] - SHA256 checksum output for reproducibility verification Key differences from build-hcl-kernel.sh: - Standalone script that doesn't depend on nix-build.sh wrapper - Implements complete build workflow in one script - Uses KBUILD_OUTPUT=$BUILD_DIR/linux subdirectory structure - Handles CVM config merging inline - Moves artifacts from /linux subdirectory to BUILD_DIR root for pipeline - When --reproducible: sets up Nix environment and reproducible variables Build directory structure: - $BUILD_DIR/linux/ # KBUILD_OUTPUT during build - $BUILD_DIR/vmlinux # Final artifacts at root - $BUILD_DIR/linux-headers/ - $BUILD_DIR/debug_symbols/ Usage: ./build-hcl-kernel-pipeline.sh -s <source> -b <build> -c <config> -a <arch> ./build-hcl-kernel-pipeline.sh ... --reproducible ./build-hcl-kernel-pipeline.sh ... --cvm-config <config> Signed-off-by: Naman Jain <namjain@linux.microsoft.com>

Copilot

Pull request overview

Copilot reviewed 6 out of 7 changed files in this pull request and generated 7 comments.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-03-27T17:13:33Z

Microsoft/build-hcl-kernel-pipeline.sh

+# Build script for HCL kernel in Azure DevOps pipeline
+# This script mirrors the structure of Microsoft/build-hcl-kernel.sh
+# but implements the same functionality as the pipeline's inline build steps.
+#
+# This script is called ONLY for OHCL product builds.
+#


The PR description says the buddy/official pipeline will call this new script, but the pipeline YAML in this repo (e.g. .pipelines/OneBranch.PullRequest.yml) still invokes Microsoft/build-hcl-kernel.sh. If the intent is to switch pipelines to this script, the wiring change is missing from this PR (or needs clarification).

Copilot · 2026-03-27T17:13:33Z

Microsoft/nix-setup.sh

+    if curl -L https://nixos.org/nix/install | sh -s -- --no-daemon; then
+        echo ""
+        echo "✓ Nix installed successfully!"
+        echo ""
+        # Source nix profile immediately for current session
+        if source_nix_profile; then
+            echo "✓ Nix environment loaded"
+        else
+            echo "⚠️  Could not source Nix profile"
+        fi
+        # Continue with setup instead of exiting
+    else
+        echo ""
+        echo "❌ Nix installation failed!"
+        echo ""
+        echo "You can try manually installing with:"
+        echo "  curl -L https://nixos.org/nix/install | sh"
+        echo ""
+        echo "Or for multi-user installation:"
+        echo "  curl -L https://nixos.org/nix/install | sh -s -- --daemon"


This script installs Nix via curl ... | sh, which is a supply-chain risk (it executes network content directly). Prefer downloading the installer to a file and verifying it (signature/hash) before executing, or at least pinning to a specific installer release/version and validating TLS/expected checksum.

Suggested change

if curl -L https://nixos.org/nix/install | sh -s -- --no-daemon; then

echo ""

echo "✓ Nix installed successfully!"

echo ""

# Source nix profile immediately for current session

if source_nix_profile; then

echo "✓ Nix environment loaded"

else

echo "⚠️ Could not source Nix profile"

fi

# Continue with setup instead of exiting

else

echo ""

echo "❌ Nix installation failed!"

echo ""

echo "You can try manually installing with:"

echo " curl -L https://nixos.org/nix/install | sh"

echo ""

echo "Or for multi-user installation:"

echo " curl -L https://nixos.org/nix/install | sh -s -- --daemon"

INSTALLER_URL="https://nixos.org/nix/install"

INSTALLER_PATH="$(mktemp /tmp/nix-install-XXXXXX.sh)"

if curl -L "$INSTALLER_URL" -o "$INSTALLER_PATH"; then

chmod +x "$INSTALLER_PATH"

if "$INSTALLER_PATH" --no-daemon; then

echo ""

echo "✓ Nix installed successfully!"

echo ""

# Source nix profile immediately for current session

if source_nix_profile; then

echo "✓ Nix environment loaded"

else

echo "⚠️ Could not source Nix profile"

fi

# Continue with setup instead of exiting

else

echo ""

echo "❌ Nix installation script failed!"

echo ""

echo "You can try manually installing with:"

echo " curl -L https://nixos.org/nix/install -o install-nix.sh"

echo " sh install-nix.sh --no-daemon"

echo ""

echo "Or for multi-user installation:"

echo " curl -L https://nixos.org/nix/install -o install-nix.sh"

echo " sh install-nix.sh --daemon"

echo ""

exit 1

fi

else

echo ""

echo "❌ Failed to download Nix installer!"

echo ""

echo "You can try manually installing with:"

echo " curl -L https://nixos.org/nix/install -o install-nix.sh"

echo " sh install-nix.sh --no-daemon"

echo ""

echo "Or for multi-user installation:"

echo " curl -L https://nixos.org/nix/install -o install-nix.sh"

echo " sh install-nix.sh --daemon"

Copilot · 2026-03-27T17:13:34Z

Microsoft/nix-build.sh

+# Auto-detect and enter Nix environment if not already in one
+if [ -z "${IN_NIX_SHELL:-}" ]; then
+    # Check if nix is available
+    if ! command -v nix &> /dev/null; then
+        # Try to source nix profile
+        if [ -f ~/.nix-profile/etc/profile.d/nix.sh ]; then
+            . ~/.nix-profile/etc/profile.d/nix.sh
+        else
+            echo "Error: Nix is not installed or not in PATH"
+            echo "Please run: ./Microsoft/nix-setup.sh"
+            exit 1
+        fi
+    fi
+
+    # Re-execute this script inside nix develop with experimental features enabled
+    # Use --ignore-environment (-i) to create a pure shell that excludes system packages
+    # Keep essential variables: HOME (for temp files), USER (for build metadata), TERM (for output)
+    # Keep SOURCE_DATE_EPOCH for reproducible builds
+    exec nix --extra-experimental-features "nix-command flakes" develop \
+        --ignore-environment \
+        --keep-env-var HOME \
+        --keep-env-var USER \
+        --keep-env-var TERM \
+        --keep-env-var SOURCE_DATE_EPOCH \
+        --command "$0" "$@"
+fi


nix develop is executed before the script cds to the kernel root, so it depends on the user’s current working directory containing flake.nix. If this script is invoked via an absolute/relative path from outside the repo root, nix develop will fail to find the flake and the build won’t start. Recommend cding to the kernel root (derived from SCRIPT_DIR) before the exec nix ... develop call, and re-invoking the script via an absolute path to avoid $0 resolution issues.

Copilot · 2026-03-27T17:13:34Z

flake.nix

+              make -j$NIX_BUILD_CORES \
+                KBUILD_BUILD_TIMESTAMP="$KBUILD_BUILD_TIMESTAMP" \
+                KBUILD_BUILD_USER="$KBUILD_BUILD_USER" \
+                KBUILD_BUILD_HOST="$KBUILD_BUILD_HOST" \
+                KBUILD_BUILD_VERSION="$KBUILD_BUILD_VERSION"


In packages.kernel the build passes KBUILD_BUILD_TIMESTAMP="$KBUILD_BUILD_TIMESTAMP", but the derivation doesn’t set KBUILD_BUILD_TIMESTAMP (or SOURCE_DATE_EPOCH). As a result, nix build .#kernel likely won’t be reproducible due to timestamp embedding. Recommend computing and exporting a stable timestamp explicitly (e.g., from flake metadata) within the derivation.

Copilot · 2026-03-27T17:13:34Z

Microsoft/nix-setup.sh

+    # Create nixbld group and users for sandboxed builds (required for Nix sandbox)
+    if ! getent group nixbld > /dev/null 2>&1; then
+        echo "Creating nixbld group and users for sandbox..."
+        groupadd -r nixbld || sudo groupadd -r nixbld
+
+        # Create 10 build users (Nix uses these for parallel isolated builds)
+        for i in $(seq 1 10); do
+            useradd -r -g nixbld -G nixbld \
+                -d /var/empty -s /sbin/nologin \
+                -c "Nix build user $i" \
+                "nixbld$i" 2>/dev/null || \
+            sudo useradd -r -g nixbld -G nixbld \
+                -d /var/empty -s /sbin/nologin \
+                -c "Nix build user $i" \
+                "nixbld$i" 2>/dev/null || true
+        done
+        echo "✓ Created nixbld group and 10 build users"


The script attempts groupadd/useradd for nixbld users even though it’s doing a --no-daemon (single-user) install. On machines without sudo/root this will fail under set -e and prevent installation. Consider skipping the nixbld user/group creation for single-user installs, or gracefully continuing when privileges aren’t available.

Suggested change

# Create nixbld group and users for sandboxed builds (required for Nix sandbox)

if ! getent group nixbld > /dev/null 2>&1; then

echo "Creating nixbld group and users for sandbox..."

groupadd -r nixbld || sudo groupadd -r nixbld

# Create 10 build users (Nix uses these for parallel isolated builds)

for i in $(seq 1 10); do

useradd -r -g nixbld -G nixbld \

-d /var/empty -s /sbin/nologin \

-c "Nix build user $i" \

"nixbld$i" 2>/dev/null || \

sudo useradd -r -g nixbld -G nixbld \

-d /var/empty -s /sbin/nologin \

-c "Nix build user $i" \

"nixbld$i" 2>/dev/null || true

done

echo "✓ Created nixbld group and 10 build users"

# Create nixbld group and users for sandboxed builds (typically used for multi-user installs).

# For single-user (--no-daemon) installs this is optional and may require root/sudo.

if ! getent group nixbld > /dev/null 2>&1; then

if [ "${EUID:-$(id -u)}" -ne 0 ] && ! command -v sudo >/dev/null 2>&1; then

echo "⚠️ Skipping nixbld group/user creation (no root or sudo; not required for --no-daemon install)."

else

echo "Creating nixbld group and users for sandbox..."

groupadd -r nixbld 2>/dev/null || sudo groupadd -r nixbld 2>/dev/null || true

# Create 10 build users (Nix uses these for parallel isolated builds)

for i in $(seq 1 10); do

useradd -r -g nixbld -G nixbld \

-d /var/empty -s /sbin/nologin \

-c "Nix build user $i" \

"nixbld$i" 2>/dev/null || \

sudo useradd -r -g nixbld -G nixbld \

-d /var/empty -s /sbin/nologin \

-c "Nix build user $i" \

"nixbld$i" 2>/dev/null || true

done

echo "✓ Created nixbld group and 10 build users"

fi

Copilot · 2026-03-27T17:13:35Z

Microsoft/nix-build.sh

+    arm64|aarch64)
+        ARCH_TYPE="arm64"
+        KERNEL_ARCH="arm64"
+        CROSS_COMPILE="aarch64-linux-gnu-"


CROSS_COMPILE is assigned for the arm64 case but never used anywhere in this script. This looks like leftover logic and can mislead readers into thinking cross-compilation is configured here. Either remove the variable or wire it into the build invocation (if intended).

Suggested change

CROSS_COMPILE="aarch64-linux-gnu-"

Copilot · 2026-03-27T17:13:35Z

Microsoft/build-hcl-kernel-pipeline.sh

+# Resolve paths first (needed by setup_reproducible_build)
+SOURCE_DIR=$(realpath "$SOURCE_DIR")
+BUILD_DIR=$(realpath "$BUILD_DIR")
+
+# Call reproducible build setup before anything else
+setup_reproducible_build


BUILD_DIR=$(realpath "$BUILD_DIR") will fail if the provided build directory doesn’t already exist (common in clean pipeline workspaces), causing the script to exit due to set -e. Create the directory before resolving it, or use realpath -m/an equivalent that tolerates non-existent paths.

saurabh-sengar reviewed Jan 31, 2026

View reviewed changes

arch/arm64/kernel/vdso/Makefile Outdated Show resolved Hide resolved

justus-camp-microsoft reviewed Feb 3, 2026

View reviewed changes

Microsoft/build-hcl-kernel-pipeline.sh Show resolved Hide resolved

Microsoft/build-hcl-kernel-pipeline.sh Show resolved Hide resolved

flake.nix Outdated Show resolved Hide resolved

flake.nix Outdated Show resolved Hide resolved

namancse force-pushed the user/namjain/reprobuild-pipeline-golden-working branch from 2ac6268 to 6d4613e Compare February 9, 2026 09:04

namancse force-pushed the user/namjain/reprobuild-pipeline-golden-working branch from 6d4613e to aaa90d1 Compare March 11, 2026 10:01

namancse marked this pull request as ready for review March 11, 2026 10:02

Copilot AI review requested due to automatic review settings March 11, 2026 10:02

Copilot started reviewing on behalf of namancse March 11, 2026 10:04 View session

Copilot AI reviewed Mar 11, 2026

View reviewed changes

Naman Jain added 4 commits March 11, 2026 11:43

namancse force-pushed the user/namjain/reprobuild-pipeline-golden-working branch from aaa90d1 to a256190 Compare March 11, 2026 11:51

benhillis requested a review from Copilot March 27, 2026 17:04

Copilot started reviewing on behalf of benhillis March 27, 2026 17:07 View session

Copilot AI reviewed Mar 27, 2026

View reviewed changes

	# SOURCE_DATE_EPOCH is set by nix-build.sh before entering this shell
	# SOURCE_DATE_EPOCH is typically set by nix-build.sh (based on the git commit)

	BUILD_OUTPUT="${BUILD_OUTPUT:-${KERNEL_ROOT}/build}"
	BUILD_OUTPUT="${BUILD_OUTPUT:-${FIXED_BUILD_PATH}/build}"

	export SOURCE_DATE_EPOCH="$(git log -1 --pretty=%ct)"
	export SOURCE_DATE_EPOCH="$(git -C "${KERNEL_ROOT_ORIGINAL}" log -1 --pretty=%ct)"

	export SOURCE_DATE_EPOCH="$(git log -1 --pretty=%ct)"
	export SOURCE_DATE_EPOCH="$(git -C "$SOURCE_DIR" log -1 --pretty=%ct)"

Conversation

namancse commented Jan 30, 2026

Uh oh!

saurabh-sengar left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Mar 27, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants