Task #11662 (closed)
Opened 11 years ago
Closed 11 years ago
Rationalize use of /OMERO across all jobs
| Reported by: | jamoore | Owned by: | sbesson |
|---|---|---|---|
| Priority: | major | Milestone: | 5.0.0-rc1 |
| Component: | Deployment | Version: | 4.4.9 |
| Keywords: | n.a. | Cc: | bpindelski, cblackburn, sysadmin@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
Use of a hard-coded "/OMERO" in all CI scripts should be discouraged. Instead, an environment variable "$DATA_DIR" should be used which can be configured and even parameterized by all the builds. This will allow the same python or bash script to be used between jobs and thereby reduce the slicing clutter.
The primary reason for doing this, however, is to prevent two scripts purging the same /OMERO directory, since we don't have user isolation between the jobs.
Change History (2)
comment:1 Changed 11 years ago by sbesson
- Owner set to sbesson
- Status changed from new to accepted
comment:2 Changed 11 years ago by sbesson
- Resolution set to fixed
- Status changed from accepted to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
The following environment have been defined (as parameters) across the board in the jobs
Additionally, bin/omero config set omero.data.dir $OMERO_DATA_DIR and bin/omero config set omero.db.name $OMERO_DB_NAME are now explicitly used across the board in the OMERO configuration step (except for the ANALYSIS-OMERO-merge-stable-ice34 job, is it /OMERO ?)
Finally these variables have been reused in the various sheel build steps reducing the variation in the Shell slicer.