Task #11339 (closed)
Opened 11 years ago
Closed 11 years ago
Cleanup omero-setup so that it can be deployed to all CI servers
| Reported by: | spli | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | Testing and Docs |
| Component: | Deployment | Version: | 4.4.8 |
| Keywords: | n.a. | Cc: | jamoore, sbesson |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | Testing and Docs (2) |
Description (last modified by spli)
Follow-up from discussion on build servers- intended workflow for each daily build:
- Create virtualenv
- pip install omero-setup
- Use the omero-setup tools for common downloading/installation/configuration tasks instead of writing duplicate code for every Jenkins job.
Change History (4)
comment:1 Changed 11 years ago by spli
- Cc jamoore sbesson added
- Component changed from General to Deployment
- Description modified (diff)
- Priority changed from minor to major
comment:2 Changed 11 years ago by jamoore
comment:3 Changed 11 years ago by spli
Might as well just go for it... rename omero-setup to omego and deal with the consequences. If necessary make the current master a branch so its just a matter of changing the repo names in any jobs.
comment:4 Changed 11 years ago by jamoore
- Resolution set to fixed
- Status changed from new to closed
PR opened. Simon, let me know if https://github.com/ome/omero-setup/pull/10 doesn't support anything listed here.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Note:
I need to look into migrating omero-setup to ome/, or we just leave it with the name omero-setup for a while, in which case I can open a PR with all of these changes against it. What jobs will need to be updated right away?