Change Details

Ideally make that happen through the ci. swh organization on dockerhub: softwareheritage inspiration: https://forge.softwareheritage.org/source/swh-docker/browse/master/images/build_images.sh To be able to login, one user should be part of the organization.

We want to: - make the ci build the image (through [1] which sounds sensible enough) - out of a tag (like we do the other modules either swh or swh-dependency package) - out of a commit on master (tests ok then push with tag "latest") Note: - We may want to use a Jenkinsfile at first in the repository for faster feedback loop - Then once, ready move the job declaration in swh-jenkins-jobs Requisite: - Figure out how to create a swh-ci account and register it to the organization (email: swh-ci@softwareheritage.org; login: swh-ci, ...) [1] https://www.jenkins.io/doc/book/pipeline/docker/#building-containers swh organization on dockerhub: softwareheritage inspiration: https://forge.softwareheritage.org/source/swh-docker/browse/master/images/build_images.sh To be able to login, one user should be part of the organization.

Ideally make that happen through the ci.We want to: - make the ci build the image (through [1] which sounds sensible enough) - out of a tag (like we do the other modules either swh or swh-dependency package) - out of a commit on master (tests ok then push with tag "latest") Note: - We may want to use a Jenkinsfile at first in the repository for faster feedback loop - Then once, ready move the job declaration in swh-jenkins-jobs Requisite: - Figure out how to create a swh-ci account and register it to the organization (email: swh-ci@softwareheritage.org; login: swh-ci, ...) [1] https://www.jenkins.io/doc/book/pipeline/docker/#building-containers swh organization on dockerhub: softwareheritage inspiration: https://forge.softwareheritage.org/source/swh-docker/browse/master/images/build_images.sh To be able to login, one user should be part of the organization.