Context Navigation

← Previous Ticket
Next Ticket →

Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.

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 #11617 (closed)

Opened 11 years ago

Closed 10 years ago

Rationalize job-priorities

Reported by:	jamoore	Owned by:	jamoore
Priority:	critical	Milestone:	5.0.0-rc1
Component:	Deployment	Version:	4.4.9
Keywords:	n.a.	Cc:	omero-team@…
Resources:	n.a.	Referenced By:	n.a.
References:	n.a.	Remaining Time:	n.a.
Sprint:	n.a.

Description

After an over-allocation on gretzky35, it was suggested that some jobs (like the merge builds which we are all waiting on) should be prioritized above less-used (e.g. daily) jobs.

This follows on from #11527 in which the time to keep build artifacts and logs was rationalized by Sebastien.

References

Change History (2)

comment:1 Changed 11 years ago by jamoore

Owner set to jamoore
Status changed from new to accepted

Current proposal (open to discussion):

Value    Category/Example
-----    ----------------
5000     Short, important jobs (git sync, venv, xelatex, IO, etc)
1000     Daily merge builds for PR review
 500     Anything for release
 250     Integration testing (incl. robotframework)
 100     Everything else

See http://hudson.openmicroscopy.org.uk/slicing/jobpriority/

comment:2 Changed 10 years ago by jamoore

Resolution set to fixed
Status changed from accepted to closed

No further comments received. Closing for the moment.

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

Download in other formats: