Version 1 vs 4
Version 1 vs 4
Content Changes
Content Changes
We're using Docker containers to build project code on Jenkins. It allows building procedures to use lightweight linux environment, well suited for reproducible builds. Docker containers have a change history that makes it easy to link to a particular build, roll back and ship software. Images are built using dependencies, and thus are easy to upgrade system wide and application wide without impacting final software so much.
## Build with docker
* Jenkins automatically spawns a fresh container for you, based on our **jenkins-1** image
* You can commit your image if the build is successfull and thus examine it and ship it at a particular release with the software stack that built it
* You can provide a custom image yourself from an external repository, every GNU/Linux distribution are supported
### Commit successfull builds
{F353, size=full}
## What others do
* Docker containers for Genome assembly http://nucleotid.es/
WARNING: This feature is being re done for 2018 and will come back soon. It will be much easier to use.
We're using Docker containers to build project code on Jenkins. It allows building procedures to use lightweight linux environment, well suited for reproducible builds. Docker containers have a change history that makes it easy to link to a particular build, roll back and ship software. Images are built using dependencies, and thus are easy to upgrade system wide and application wide without impacting final software so much.
## Build with docker
TODO
We're using Docker containers to build project code on Jenkins. It allows building procedures to use lightweight linux environment, well suited for reproducible builds. Docker containers have a change history that makes it easy to link to a particular build, roll back and ship software. Images are built using dependencies, and thus are easy to upgrade system wide and application wide without impacting final software so much.
## Build with docker
* Jenkins automatically spawns a fresh container for you, based on our **jenkins-1** image
* You can commit your image if the build is successfull and thus examine it and ship it at a particular release with the software stack that built it
* You can provide a custom image yourself from an external repository,ARNING: This feature is being re done for 2018 and will come back soon. every GNU/Linux distribution are supported
### Commit successfull buildsIt will be much easier to use.
{F353We're using Docker containers to build project code on Jenkins. It allows building procedures to use lightweight linux environment, well suited for reproducible builds. Docker containers have a change history that makes it easy to link to a particular build, roll back and ship software. Images are built using dependencies, size=full}and thus are easy to upgrade system wide and application wide without impacting final software so much.
## What others do## Build with docker
* Docker containers for Genome assembly http://nucleotid.es/TODO
c4science · Help