OfficialBuildId on non-Azure Pipelines CI environments

Preamble: I’m totally aware that Arcade was designed to be primarily used in Microsoft projects, but we’re interested in adopting it for the aspnet-contrib repositories as it perfectly suits our needs.

Unlike Microsoft projects, the aspnet-contrib repositories use AppVeyor and Travis. While Arcade works like a charm there, we’re a bit blocked by the versioning mechanism of official builds, that requires a very specific format for OfficialBuildId that doesn’t work well with the ever-increasing build identifiers (that are not reset at the end of the day). It wouldn’t be a problem if the r part of OfficialBuildId was not limited to 2 digits, but sadly, that’s not the case.

So, my question is: what’s the recommendation in this case? 😄

/cc @martincostello

(more context: https://github.com/aspnet-contrib/AspNet.Security.OAuth.Providers/pull/335)

[tmat]

@PinpointTownes Migrate to Azure DevOps 😃?

[kevinchalet]

Thanks for the explanation. I will wait a bit before closing this ticket in case @tmat would like to add details.

In the meantime, we’ll likely opt for the mod 100 option and pray we don’t produce more than 100 builds a day 😄