Ticket #1065 (closed assessed: fixed)

Opened 7 years ago

Last modified 6 years ago

Report global SVN build number in EwE

Reported by: markh Owned by: jeroens
Priority: normal Milestone: Ecopath 6: release 6.3 BETA
Component: Overall Logistics Version:
Severity: tweak Keywords:
Cc:

Description

it should also be possible to track the svn revision that generated a particular build, and this should probably be mentioned in multiple places. The 'about ewe' splash screen would be a good place, so users can mention it in bug reports. Also, all model outputs should include it as metadata, in case different builds produce slightly different results (this is something we've been uncomfortably aware of with Atlantis for a while, and Sharon Tickell from CSIRO also raised it in the context of EwE). In the case of EwE, judging by this conversation, it should also be included in the database somewhere.

I don't think this is much effort to implement (see http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html), but I do think it's important to include in this kind of discussion.

Change History

comment:1 Changed 7 years ago by jeroens

We can include this into the BuildBot daily build scripts which is fairly easy to implement. The global SVN revision number should be accessible from the core classes so it can be used anywhere in the code.

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

comment:2 Changed 7 years ago by jeroens

Note that we are deliberately confusing 'build number' with 'svn revision number'. I think it is totally fine to use the SVN revision number instead of a build number which we do not have, but I just want to make the point.

comment:3 Changed 6 years ago by jeroens

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.