devspace
devspace copied to clipboard
ome
Continuous integration tool for OME projects
A single job could loop through all repositories and push them to snoopy. See: gh-72
A couple of fixes to get the docker node running: - Ensure the docker group id inside the container and outside the host are the same (needed since `/var/run/docker.sock` is...
Currently omero-build is the primary repository for checking the build status of downstream PRs, leading it to have a more complicated travis script, see https://github.com/ome/omero-build/blob/master/travis.sh Adding in Bio-Formats to that...
Several jobs make persistent changes to the build environment, e.g. https://github.com/openmicroscopy/devspace/blob/0.10.0/home/jobs/BIOFORMATS-push/config.xml#L78 which installs scc outside of a sandboxed virtualenv. Either these dependencies should be in the Dockerfile, or in a...
Either `git remote prune origin` or `git fetch --prune` should be used so that if `--shallow` is removed from `OMERO-push`, the `OMERO-build` step will not fail on trying to checkout...
Currently devspace is designed to work on a dedicated VM. Due to the overhead in managing VMs it would be a lot easier if multiple devspaces could run on a...
A user coming to a devspace must currently know a number of URLs (possibly with varying ports) that can be confusing. A single landing page could be generated with the...
devspace should have a self-hosted git repository to support running without GitHub. All jobs could push/pull from this internal git repo, and an optional separate job would push this to...