Opened 15 years ago

Closed 13 years ago

#108 closed enhancement (fixed)

Building of release files should be automated

Reported by: Jiri Svoboda Owned by: Jiri Svoboda
Priority: major Milestone: 0.4.3
Component: helenos-build Version: mainline
Keywords: Cc:
Blocker for: Depends on:
See also: #124


There should be a script to build the release files. This should be easy to do and has the following advantages:

  • Faster, easier building is good especially when releasing in quick succession (e.g. bugfix release).
  • More deterministic, less prone to errors.
  • More transparent (anyone can see how the builds are made, so they know exactly what they are getting)
  • Susceptible to testing.

Basically it should be possible to configure HelenOS from one of the preset files via command line (this is very useful itself). Then, the script would just select the proper configuration for each release file and then copy it it from the build directory.

Change History (8)

comment:1 by Jakub Jermář, 14 years ago

Component: unspecifiedbuild

comment:2 by Jakub Jermář, 13 years ago

See also: #124

comment:3 by Jakub Jermář, 13 years ago

Owner: set to Jakub Jermář
Status: newassigned

comment:4 by Jakub Jermář, 13 years ago

Type: proposalenhancement

comment:5 by Jakub Jermář, 13 years ago

Status: assignedaccepted

comment:6 by Jakub Jermář, 13 years ago

Owner: changed from Jakub Jermář to Jiri Svoboda
Status: acceptedassigned

comment:7 by Jiri Svoboda, 13 years ago

With the integration of changeset:mainline,863 and changeset:mainline,879 most of this problem is solved. Still we need to figure out what additional tuning should be applied by the release Makefile so that the release files are fit for release.

  • for example, the Bazaar revision should not be compiled in

comment:8 by Jiri Svoboda, 13 years ago

Resolution: fixed
Status: assignedclosed

In changeset:mainline,881, changeset:mainline,882 and changeset:mainline,883 I made the release Makefile first export the source from Bazaar and then build a source tarball and build the release images. This also ensures the Bazaar revision is not built into the release images. I consider this ticket resolved.

In the future it would be nice to unify 'make check' and 'make release' to avoid duplication.

Note: See TracTickets for help on using tickets.