User Story #1034 (closed)
Opened 16 years ago
Closed 10 years ago
Prepare working Ivy-over-HTTP integration between server and insight
| Reported by: | jamoore | Owned by: | jamoore |
|---|---|---|---|
| Priority: | minor | Milestone: | 5.0.5 |
| Component: | Deployment | Keywords: | n.a. |
| Cc: | wmoore, jburel, cxallan, bwzloranger | Story Points: | n.a. |
| Sprint: | n.a. | Importance: | n.a. |
| Total Remaining Time: | n.a. | Estimated Remaining Time: | n.a. |
Description
An initial implementation would make it easier to see whether or not Ivy would be a good choice for the various products.
Change History (7)
comment:1 Changed 16 years ago by jburel
- Cc callan added; chris removed
comment:2 Changed 16 years ago by jmoore
Not really necessary. It'd most likely be optimal to let hudson manage a single repository. But having multiple (more than two for release, QA, public/private etc.) wouldn't be an issue.
comment:3 Changed 16 years ago by jmoore
- Milestone changed from 3.0-Beta3.1 to 3.0-Beta4
Non-critical. Pushing.
comment:4 Changed 15 years ago by jmoore
- Milestone changed from OMERO-Beta4 to OMERO-Beta4.1
Build fixes hopefully coming in 4.1
comment:5 Changed 15 years ago by jmoore
- Milestone changed from OMERO-Beta4.1 to OMERO-Beta4.2
comment:6 Changed 14 years ago by jmoore
- Milestone changed from OMERO-Beta4.2 to Unscheduled
Dependent on the number of repos we had.
comment:7 Changed 10 years ago by jamoore
- Milestone changed from Unscheduled to 5.0.5
- Resolution set to fixed
- Status changed from new to closed
This now works.
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Question: Do we keep two separate repositories?