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

Opened 7 years ago

Closed 7 years ago

4.4.9 release setup

Reported by: jamoore Owned by: jamoore
Priority: blocker Milestone: OMERO-4.4.9
Component: General Version: 4.4.8
Keywords: n.a. Cc: rleigh, khgillen, mlinkert, pwalczysko, sbesson
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description (last modified by jamoore)

General TODOs

  • Add a sync job which pushes tags from gh:ome/* to gh:snoopy/* (UNNEEDED)
  • Setup proper directory permissions for the hudson user (#11523)

Ideal job

The ideal job for performing a release would be runnable via: %build OME-release now version=4.4.8. It would perform the following steps:

  • Checkout the latest ome/ome code (Don)
  • Update all submodule pointers similar to OMERO-submods-{stable,develop} (Done)
  • Push that branch to snoopy (Done: pushes a tag)
  • Open a PR (Note: when this commit is pushed back to ome/ome, the PR will be autoclosed) (Not needed)
  • Kick off the ice33 and ice34 builds. (Done; as matrix job)
  • ...
  • Once all other activities are finished, there are 2 options:
    • Either delete the job executions, in which case there's no evidence of the tag that snoopy created; or
    • Sign the snoopy commit and push it to ome/ome and promote the builds. The release was a success!

Larger tasks (ticketable)

  • Remove need for version PRs in bioformats (Mostly done; not maven - see #11523)
  • Move release notes into source (See From Roger: "Being able to update the release notes with the PR to implement a feature/fix a bug would be very nice, then it's always in a "ready to release" state ahead of the release. " (#11523)

Change History (5)

comment:1 Changed 7 years ago by jamoore

  • Cc rleigh khgillen mlinkert added
  • Description modified (diff)

comment:2 Changed 7 years ago by sbesson

  • Cc pwalczysko added
  • Milestone changed from OMERO-4.4.x to OMERO-4.4.9
  • Summary changed from 4.4.8 release setup to 4.4.9 release setup
  • Version set to 4.4.8

PRs have been opened against Bio-Formats to get rid of the version number (

The release process is tested on the develop branch for the Bio-Formats component with the following job:
The current workflow of the job is the following:

Next steps for this task are the following

comment:4 Changed 7 years ago by sbesson

  • Cc sbesson added
  • Owner changed from sbesson to jamoore

Recent progress on this blocker can be checked under the Release tab of the CI server:

  • OMERO-stable-release is a multi-configuration jobs which checks out the head of dev_4_4, runs scc tag-relase RELEASE, builds the OMERO artifacts and copies them under with the same .htaccess and a .htpasswd file as above. Three configurations are currently defined for this job corresponding to the supported Ice versions i.e. 3.3, 3.4 and 3.5. The Ice environment is installed from the ICE-setup under hudson's $HOME and the desired environment is activated for each matrix job.

Current blockers of the 4.4.9 release process are the following:

  • Downloads page generation: these downloads pages were generated using repository and the OME-release-stable job. Assuming we still want to expose 4.4.9 on these pages,
    • the OMERO page needs to be amended to include the 3.5 server: (Done)
    • the Bio-Formats page needs to be amended to include the Matlab zip bundle (Done)
    • the generation logic needs to be revisited: the step can be skipped since all artifacts are copied under a well-defined location, SNAPSHOT_PATH default value needs to be modified (Deleted)
    • the OME-release-stable job should be renamed to be more meaningful and potentially set as a downstream of OMERO-stable-release and BIOFORMATS-stable-release e.g. using the Joint plugin (Deleted; further renaming in #11523)

Re-assigning this ticket to Josh while away at meeting in Edinburgh.

Last edited 7 years ago by jamoore (previous) (diff)

comment:5 Changed 7 years ago by jamoore

  • Description modified (diff)
  • Resolution set to fixed
  • Status changed from new to closed

Follow-on #11523 opened.

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.182004 sec.)

We're Hiring!