Perform build and packaging on different machines

Bug #1176462 reported by Charlie Poole
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnit Framework
Triaged
High
Unassigned

Bug Description

[Issue now tracked at https://github.com/nunit/nunit-framework/issues/11]

Currently, it's only possible to do a release of NUnitLite on a machine with all the runtimes we support installed. This makes it difficult for contributors to handle releases. It would be better if the builds could be completed on different machines and then aggregated on a separate server.

The main changes needed to the build script to accomplish this are:

1. Provide a remote location to which builds are published
2. Add a target to copy builds to that location.
3. Modify package targets to use that location.

In order to make sure that all the builds for a release are all based on the same source, we will need to tag the published packages with a revision number and/or date.

Tags: github
Changed in nunitlite:
importance: Undecided → High
Changed in nunitlite:
status: New → Triaged
Changed in nunitlite:
milestone: none → 1.0
Changed in nunitlite:
milestone: 1.0 → 3.0
affects: nunitlite → nunit-3.0
Changed in nunit-3.0:
milestone: 3.0 → none
tags: added: github
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.