Skip to content

Commit

Permalink
failing to set the appveyor version should not be a fatal build error
Browse files Browse the repository at this point in the history
  • Loading branch information
ghuntley committed Feb 4, 2017
1 parent 3ab7f14 commit 01760e9
Showing 1 changed file with 12 additions and 0 deletions.
12 changes: 12 additions & 0 deletions build.cake
Original file line number Diff line number Diff line change
Expand Up @@ -287,6 +287,18 @@ Task("UpdateAppVeyorBuildNumber")
.Does(() =>
{
AppVeyor.UpdateBuildVersion(buildVersion);

}).ReportError(exception =>
{
// When a build starts, the initial identifier is an auto-incremented value supplied by AppVeyor.
// As part of the build script, this version in AppVeyor is changed to be the version obtained from
// GitVersion. This identifier is purely cosmetic and is used by the core team to correlate a build
// with the pull-request. In some circumstances, such as restarting a failed/cancelled build the
// identifier in AppVeyor will be already updated and default behaviour is to throw an
// exception/cancel the build when in fact it is safe to swallow.
// See https://github.com/reactiveui/ReactiveUI/issues/1262

Warning("Build with version {0} already exists.", buildVersion);
});

Task("UpdateAssemblyInfo")
Expand Down

0 comments on commit 01760e9

Please sign in to comment.