CI:add new builds #449
CI:add new builds #449
Conversation
Signed-off-by: Raluca Groza <[email protected]>
Signed-off-by: Raluca Groza <[email protected]>
azure-pipelines.yml
Outdated
| @@ -117,6 +117,10 @@ stages: | |||
| image: tfcollins/libiio_ubuntu_18_04-ci-arm-ppc:latest | |||
| arch: aarch64 | |||
| artifactName: 'Ubuntu-arm64v8' | |||
| bullseye: | |||
There was a problem hiding this comment.
Can you change name to have the same format: "debian_bullseye_arm64v8"?
And I think you can add a build for 32bit image just by specifying "arch: arm"
azure-pipelines.yml
Outdated
| source: 'specific' | ||
| project: '$(System.TeamProjectId)' | ||
| pipeline: $(libiioPipelineId) | ||
| artifact: 'Ubuntu-arm32v7' |
| @@ -94,6 +94,63 @@ stages: | |||
|
|
|||
| ####################################### | |||
|
|
|||
| - job: RPIBuilds | |||
| pool: | |||
| name: Default | |||
There was a problem hiding this comment.
Is it ok to let the agent connected to "Default" pool?
I'm mean, if there are other jobs that are using "Default Pool" for building things, but without specifying an explicit agent, the build may go on this.
| - script: | | ||
| mkdir build && cd build | ||
| cmake ../ | ||
| make -j9 |
There was a problem hiding this comment.
RPI do not have 9 CPU cores. This kind of builds will just kill it (freeze it) for at least few minutes.
Please check how many cores its CPU has and set make command to use maximum threads.
| - task: PublishPipelineArtifact@1 | ||
| inputs: | ||
| targetPath: '$(Build.ArtifactStagingDirectory)' | ||
| artifactName: 'RPI4-Bullseye' |
There was a problem hiding this comment.
Please add also architecture in the name of artifacts(armhf).
ccraluca
force-pushed
the
staging/add-bullseye
branch
from
31f85b0 to
18defb4
Compare
Signed-off-by: Raluca Groza <[email protected]>
ccraluca
force-pushed
the
staging/add-bullseye
branch
from
18defb4 to
d27fa75
Compare
Signed-off-by: Raluca Groza <[email protected]>
Add bullseye and rpi4 builds on Azure CI.