Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #1437 (closed)

Opened 10 years ago

Closed 9 years ago

Separate out integration tests (OmeroPy, etc.) into separate build

Reported by: jamoore Owned by: jamoore
Priority: minor Milestone: OMERO-Beta4.2
Component: Deployment Version: 3.0-M1
Keywords: n.a. Cc:
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: 0.0d
Sprint: 2010-04-16 (7)

Description

So it's easier to see when a particular components (OmeroPy, OmeroCpp) is failing, component integration tests need to have their own builds.

Change History (3)

comment:1 Changed 10 years ago by jmoore

  • Milestone changed from OMERO-Beta4.1 to OMERO-Beta4.2

There is now an omero-integration-py26 job but more are needed. Pushing.

comment:2 Changed 9 years ago by jmoore

  • Remaining Time set to 0.5

comment:3 Changed 9 years ago by jmoore

  • Remaining Time changed from 0.5 to 0
  • Resolution set to fixed
  • Sprint set to 2010-04-16 (7)
  • Status changed from new to closed

Done over the weekend. Have sent an email to ola/carlos about getting OmeroWeb also listed.

Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.77785 sec.)

© 2000-2014 University of Dundee & Open Microscopy Environment. Creative Commons Attribution 3.0 Unported License
OME source code is available under the GNU General public license or through commercial license from Glencoe Software

We're Hiring!