conda-smithy
conda-smithy copied to clipboard
[WIP] Generate Jenkinsfiles from conda-forge.yaml
xref: conda-forge/conda-forge.github.io#695
Can't you use the jnlp slave image and run the run_docker_build.sh
file? It removes duplicating of scripts
The problem with docker_build is that it assumes the slaves have access to docker, which in what I have available is not true. For example, we might have Jenkins slaves running directly on kubernetes or other hosted platform without "volume mount" support.
Do you have other suggestions to remove duplication?
let me look into build_steps.sh.tmpl. I think I can make it work if I make it a little bit more generic.
@sodre conda-forge's longer term approach is to try and run everything we possibly can on azure. We have substantially higher build capacity there than in all our other CI platforms combined. We currently have all of our feedstocks registered on there and building. There is no perceptible delay in starting any of our builds given our current build load.
Other consumers of conda-forge might be able to use this, but i think this may unfortunatly be a bit of a dead-end for us.
A similar but probably easier approach that we could use that integrates well with this strategy is that instead of running jenkins agents somewhere we could run azure build agents on those machines and use our existing azure things (see here https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/agents?view=vsts for details on how that works).