Task #8307 (closed)
Opened 12 years ago
Closed 12 years ago
Bug: default VM image is unstable as opposed to release version
| Reported by: | jamoore | Owned by: | cmacleod-x |
|---|---|---|---|
| Priority: | critical | Milestone: | OMERO-4.4 |
| Component: | Deployment | Version: | n.a. |
| Keywords: | n.a. | Cc: | cxallan |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
The only virtual box image we provide at the moment is built from trunk and is therefore unstable. There should also be a virtual image which is built from the released code.
Further, all of the images should have a version number in their name.
cf:
- Docs http://www.openmicroscopy.org/site/support/omero4/getting-started/demo point to
- http://hudson.openmicroscopy.org.uk/job/OMERO-trunk-virtualbox/lastSuccessfulBuild/artifact/src/docs/install/VM/omero-vm.ova
Change History (4)
comment:1 Changed 12 years ago by cmacleod-x
- Owner changed from jmoore to cmacleod-x
- Status changed from new to accepted
comment:2 Changed 12 years ago by cmacleod-x
comment:3 Changed 12 years ago by jmoore
There may be a few 4.3 commits coming up, but if you're ok with just generating an image and getting it through the testing cycle, we can definitely just say "here's the 4.3.x virtual image, if you want development go over here -->"
comment:4 Changed 12 years ago by cmacleod-x
- Resolution set to fixed
- Status changed from accepted to closed
Documentation updated and 'release' builds are being pushed to http://cvs.openmicroscopy.org.uk/snapshots/omero/virtualbox/
Release builds contain the version in the release. Mainline builds are marked as 'latest-build'.
PR213 - https://github.com/openmicroscopy/openmicroscopy/pull/213
I can create a new image fairly easily but it sounds like we want the build process shored up so that we can build a vm off a given tag/branch at a given time. It looks like the scripts and job associated are old and not really maintained anymore.
I'm curious to know who is using the vms and what they need out of them to see if it's worth the effort to redo the whole jenkins/build process or just publish a new image off of a stable branch for the time being.