Task #10834 (closed)
Opened 11 years ago
Closed 11 years ago
Fix OMERO virtualbox artifacts overwriting
| Reported by: | sbesson | Owned by: | sbesson |
|---|---|---|---|
| Priority: | major | Milestone: | OMERO-4.4.9 |
| Component: | General | Version: | 4.4.8 |
| Keywords: | n.a. | Cc: | jamoore, khgillen |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Currently the OMERO-stable-virtualbox and OMERO-trunk-virtualbox jobs are both copying the created ova to necromancer as /ome/data_repo/virtualbox/omero-vm-latest-build.ova
The problem is that the latest vm is overwritten by any of these 2 jobs. This is a major issue especially during release process. For 4.4.8 release, OMERO-trunk-virtualbox has been temporarily disabled to fix this issue.
A possible solution is to use the same strategy as for the other release artifacts, namely copy artifacts to /ome/data_repo/releases as a promotion step. Then prep.sh under ome-release.git would have to be modified to symlink this promoted artifact during release process.
Change History (2)
comment:1 Changed 11 years ago by jamoore
- Owner set to sbesson
- Version set to 4.4.8
comment:2 Changed 11 years ago by sbesson
- Resolution set to fixed
- Status changed from new to closed
Fixed as part of the 5.0.0-beta1 release process
Sebastien: this can be closed now, no?