Hi, I have some suggestions / queries. I package Xen using GitLab CI for my use: https://gitlab.com/archlinux-packages-johnth/xen/pipelines My examples here are just mock-ups and not tested.
On Fri, 16 Mar 2018, at 04:21, Doug Goldstein wrote: > Example run: https://gitlab.com/cardoe/xen/pipelines/18968075 - You probably want to set "XEN_TARGET_ARCH". The example build misses tools. job: variables: ... XEN_TARGET_ARCH: x86_64 - Is it worth storing the resultant built files as artifacts? This way they can be downloaded or tested later. artifacts: paths: - 'dist' > Currently the example uses one stage called build and all the different > distros are different jobs. - Is is worth caching and artifacting the build (tools) dependencies as a job, so that each CI job does not hit the dependency Xen repos and websites for the same data, and you have an easily accessible pre-build state? This may need an empty job for collect stage where not wanted? I am unsure if you can skip a first stage. stages: - collect - build collect:tools: stage: collect script: - Clone all tools dependency repos & downloads - Move files into place, and set repo URLs (example; QEMU_UPSTREAM_URL) to the local copies. artifacts: untracked: true cache: untracked: true build-job-example: ... dependencies: - collect:tools - My build log exceeds the GitLab CI Job limit. You may not hit this limit, then you can ignore this. It looks like this, at the end of the GitLab CI log, but mid-way through the job log: ... "Job's log exceeded limit of 4194304 bytes." To work around this, I log to a file, then store this file as an artifact. These can then be downloaded later. This could be something like: artifacts: paths: - '*.log' when: always job: ... script: - ./scripts/travis-build 2>&1 | tee build.log Cheers, -- John Thomson _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
