[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH 3/4] automation: also specify xen binary as artifact on x86_64
... so that it can be passed on to test stage. Note that xen is only extracted for x86_64 build since others may not have that. Use a directory to account for possibly different file names on Arm. Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> --- .gitlab-ci.yml | 1 + automation/scripts/build | 4 ++++ 2 files changed, 5 insertions(+) diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml index 28152e906d..d11459b117 100644 --- a/.gitlab-ci.yml +++ b/.gitlab-ci.yml @@ -8,6 +8,7 @@ stages: - ./automation/scripts/build 2>&1 | tee build.log artifacts: paths: + - binaries/ - xen-config - '*.log' when: always diff --git a/automation/scripts/build b/automation/scripts/build index a1f9a5da56..d4aceb745f 100755 --- a/automation/scripts/build +++ b/automation/scripts/build @@ -28,6 +28,10 @@ make -j$(nproc) dist # Extract artifacts to avoid getting rewritten by customised builds cp xen/.config xen-config +mkdir binaries +if [[ "x${XEN_TARGET_ARCH}" == "xx86_64" ]]; then + cp xen/xen binaries/xen +fi # Build all the configs we care about case ${XEN_TARGET_ARCH} in -- 2.11.0 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |