When comparing with the previous commit, we can't use the TFM for the
stable version of .NET, since it may not be the same TFM used in the
previous commit.
Instead fetch the actual TFM from the checkout, and use that during the
api comparison.
Co-authored-by: Manuel de la Pena <mandel@microsoft.com>
Co-authored-by: GitHub Actions Autoformatter <github-actions-autoformatter@xamarin.com>
Azure pipelines has this terrible design in which the path of the
checkout is different depending if you checkout a single repo or
several.
In this case, we have no issues on macios because we do know we have not
been checkout with anyother repo in the upload step, that is not the
case when working on the unified pipeline. Rather than adding some
complicated logic, we are going to be checking out the yaml templates so
that we have the same working directory structure.
It's often desired to run the install-workloads.sh script locally, in order to
diagnose problems with it.
So improve it a bit by:
* Adding a few comments explaining things.
* Don't assume we're in the correct directory.
* Figure out BUILD_SOURCESDIRECTORY if it's not already set.
* Validate a bit and show more helpful errors.
Hopefully future me will be grateful!
The template can be run by a diff pipeline, that means that the project
and the commit wont point to xmarin/xamarin-macios. We use the URI to
calculate the org and the repo to be passed to the pwh objects.
Fixes https://github.com/xamarin/sdk-insertions/issues/43
This makes sure we're at the right maccore hash before adding provisioning
profile (in particular we want to be at the hash where the PR branch is at,
not the tip of main (which is the default)).
Move to use a template to perform the checkout. The new template allows
to perform the checkout using a resource alias, which later can be used
to use the template outside this repo.
Partial fix for https://github.com/xamarin/sdk-insertions/issues/41
Co-authored-by: TJ Lambert <50846373+tj-devel709@users.noreply.github.com>
In an attempt to unify the build of all the SDKs we need to be rename
all shared resources between the CIs to all use the same name.
This commit renames the resource to use the pattern used by MAUI.
Partial fix for https://github.com/xamarin/sdk-insertions/issues/39
Don't disable compact unwind info in the native linker, it may break C++
exception handling.
We originally disabled compact unwind info to fix a warning from the native
linker, this will have to be solved another way (in any case extra build
warnings is preferrable compared to an app crashing at runtime due to broken
C++ exception handling).
This partially reverts c05e774612.
Fixes https://github.com/xamarin/xamarin-macios/issues/16546.
In an attempt to unify the build of all the SDKs we need to be rename all shared resources between the CIs to all use the same name.
This commit renames the resource to use the pattern used by MAUI.
Partial fix for xamarin/sdk-insertions#39
* Read the enabled platforms from the build configuration.
* Iterate over each platform, and only push the enabled ones to maestro.
* Iterate over each platform again, and only add the enabled ones to the default
channel (for the current branch).
* This makes it much easier to maintain the code, since it's possible to run it locally.
* Add tests!
* Add a DOTNET_PLATFORMS variable to the build configuration to list all the
enabled .NET platforms.
* Add INCLUDE_DOTNET_<platform> variables to the build configuration for each
enabled .NET platform. These new variables will be used in a future pull request.
Update the download of API references to:
* Use `dl.internalx.com` links instead of `bosstoragemirror.blob.core.windows.net`
links (the relative path stays the same).
* Require a GitHub PAT in order to download from dl.internalx.com. This PAT
can either be provided through a file (recommended for local use) or through
the environment.
* Document these changes.
Rolf Bjarne Kvinge
Manuel de la Pena
Alex Soto
Rui Marinho
GitHub Actions Autoformatter