Welcome to mirror list, hosted at ThFree Co, Russian Federation.

github.com/mono/linker.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2022-11-03Enable CodeQL with TSAmdh1418
2022-10-04Update docker to the latest tagging schema (#3057)Djuradj Kurepa
2022-09-27Use new build images (#3051)Sven Boemer
2022-09-08Fix lint command (#3027)Tlakaelel Axayakatl Ceja
Use new version of MicrosoftCodeAnalysisVersion in linker (Copy from runtime) to fix the dotnet format command Run the dotnet format command Reenable Lint check in ci pipelines
2022-08-09Build with preview5 SDK (#2954)Sven Boemer
dede5f58dc9b7296de884ed62688b35d5b154b78 didn't fix the dependency flow, because the packages for some reason are still being produced with a preview7 in the runtimeconfig. Lacking better workarounds, this change builds with the preview5 SDK that was selected in #2884 before we decided to update to preview7 (due to a dotnet-format bug). This disables the lint job to prevent those failures. We should turn it back on once we can use preview7 (once dotnet/runtime and dotnet/sdk are on preview7).
2022-02-04Fix lint job in CI (#2581)Vitek Karas
It did run linter, but didn't fail if any changes were to be applied, instead it actually applied them (and then dropped). So the job would actually never fail.
2022-02-01Use internal machine pool for src build (#2570)Andy Gocke
* Use internal machine pool for src build * Update azure-pipelines.yml
2021-12-09Fix the pool name for main after incorrect merge from 6.0.2xx (#2436)Vitek Karas
2021-12-04Switch to 1ES servicing pools on release/6.0.2xx (#2381)Jon Fortescue
2021-12-02Use non-deprecated Windows pool in Azure Pipelines (#2393) (#2413)Vitek Karas
See https://github.com/dotnet/core-eng/issues/14783. Also switch to latest macOS/Ubuntu/Windows vmImage. Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
2021-10-19Switch to ubuntu 20.04 agents (#2322)Sven Boemer
The Ubuntu 16.04 agents were removed from Azure DevOps: https://github.com/actions/virtual-environments/issues/3287
2021-10-07Migrate to 1ES hosted pools (#2309)Łukasz Patalas
2021-09-16Change occurrences of 'mono/linker' to 'dotnet/linker' (#2277)Mateo Torres-Ruiz
2021-03-11Fix lint to avoid generating binlog file (#1879)Vitek Karas
Latest lint writes formatDiagnosticLog.binlong next to the solution file when running with --verbosity diagnostic. There's no way to redirect or disable this - https://github.com/dotnet/format/issues/1041. So this change disables --verbosity diagnostic for local runs of lint and adds it only to the CI (where the machine will clean the enlistment anyway).
2021-02-24Enable source-build through arcade (#1823)Omair Majid
Co-authored-by: Marek Safar <marek.safar@gmail.com>
2021-02-24Don't publish test results in official build (#1848)Alexander Köplinger
We don't run tests there so we get a warning about missing test result files in the official build.
2021-02-05Complete branch moveJoseph Shields
2021-02-04Build based on changes to main branch tooJoseph Shields
2021-01-19Remove monolinker build support (#1760)Marek Safar
Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
2020-11-25Remove deprecated dotnet-format options (#1646)Mateo Torres-Ruiz
2020-10-22Switch to correct test results format (#1578)Marek Safar
2020-10-08Enable warnAsError on CI to match dev environmentMarek Safar
2020-09-30[release/5.0] Onboarding to v3 publishing (#1519)Matt Mitchell
2020-05-11[master] Update dependencies from dotnet/arcade (#1180)dotnet-maestro[bot]
* Update dependencies from https://github.com/dotnet/arcade build 20200506.5 - Microsoft.DotNet.ApiCompat: 5.0.0-beta.20228.4 -> 5.0.0-beta.20256.5 - Microsoft.DotNet.Arcade.Sdk: 5.0.0-beta.20228.4 -> 5.0.0-beta.20256.5 * Add restore to lint.sh/cmd * Remove lint restore from azure-pipelines.yml * Make sure the Lint step fails on violations * Disable https listening in WebApiTest.cs It doesn't play nice with CI environments. * Disable WebApi test on CI on macOS Co-authored-by: dotnet-maestro[bot] <dotnet-maestro[bot]@users.noreply.github.com> Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
2020-05-06Fix build and improve auto-formatting (#1172)Vitek Karas
Fixes command line build on windows in the analyzer project (latest Arcade has conflicts when building net core and net desktop projects at the same time. since we don't need desktop I removed it) Fixes editorconfig to correctly specify LF as EOL character so that it works on Windows. Added running the lint (auto-formatter) in command line (lint.sh/lint.cmd). CI now runs this command in a `--dry-run` mode so using it before submitting a PR should guarantee correct formatting.
2020-04-24Ensure consistent sources formatting (#1138)Marek Safar
* Apply consistent formatting based on .editorconfig ``` dotnet format -f <path> ``` * Add lint step to the CI * Use local tool * Suppress publish logs warning * Fix more style errors * Fixes bad merge * Write something to log dir * Move lint job to global scope So it doesn't get the arcade publish logs/test steps injected. * Split sources and tests reporting * Include also src folder in the run * Exclude cecil sources * Remove duplicate line * Trigger notification * Format more code Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
2020-03-17Enable CI in the feature/dataflow branch (#1010)Michal Strehovský
* Enable CI in the feature/dataflow branch #1004 turned off the CI on all but select branches. * Update eng/azure-pipelines.yml Co-Authored-By: Marek Safar <marek.safar@gmail.com> Co-authored-by: Marek Safar <marek.safar@gmail.com>
2020-03-16Update azure-pipelines.ymlAlexander Köplinger
2020-03-16Workaround Azure DevOps PR trigger issueAlexander Köplinger
2020-02-06Fix warnings in arcade build (#939)Alexander Köplinger
- Move Mono build out of common arcade template to get rid of missing xunit test results warning. - Use Microsoft copyright for Mono.Linker.csproj, it is required by arcade.
2020-02-06Run illink tests on CI (#937)Marek Safar
* Set ILLink.Tasks.Tests to be test project * Unconditionally use arcade * Fix ILLink.Tasks test project - Renamed to ILLink.Tasks.IntegrationTests because it depends on the .nupkg and arcade schedules Test projects before Pack - Fixed path to nupgk in nuget config - Move override of Test target for NUnit project from root Directory.Build.targets. For some reason Condition doesn't work there so the target would always be overriden. - Disabled MusicStore tests They were already disabled in https://github.com/mono/linker/commit/04eb53822f98749bdf6ab47009ba7c269f504eae because of https://github.com/mono/linker/commit/04eb53822f98749bdf6ab47009ba7c269f504eae but looks like that got reverted somehow * Make arcade enabled builds the default and remove special illink_ configs Mono builds can be done with /p:MonoBuild=true * Remove .net framework targets from netcore build * Update ILLink.Tasks to netcore3.0 * Fix netcore condition * More netcore3.0 updates * Try to mimic weird arcade behaviour * Enable test results publishing in arcade * Remove DisableArcadeImport property and use temp folder for ILLink.Tasks test projects instead * Fix net471 build on Unix * Use a temp folder in the repo and write empty Directory.Build.props/targets instead This works better with arcade temp folder overrides. * Revert "Try to mimic weird arcade behaviour" This reverts commit 3923c5410bf2d17073373924dc53020c91fea346. * Force always downloading a local dotnet We need this for the ILLink.Tasks tests. Co-authored-by: Alexander Köplinger <alex.koeplinger@outlook.com>
2019-12-20Disable test on official buildAlexander Köplinger
2019-12-20Only run official build on WindowsAlexander Köplinger
We don't need assets from other platforms.
2019-12-20Switch to yaml stages for arcade publishingAlexander Köplinger
2019-12-14Add Linux Mono build to Azure PipelineAlexander Köplinger
We can easily replace the Jenkins build with one on Azure Pipelines now.
2019-10-10Only trigger AzDO pipeline build for master or release/ branchesAlexander Köplinger
2019-09-10Stop using Int pool providerMatt Galbraith
2019-04-11Use PoolProvider for internal buildsMatt Galbraith
2019-03-29Publish asset manifestsSven Boemer
2019-03-28Add displayName for macOS jobSven Boemer
2019-03-28Fix official build numberSven Boemer
Delay expansion of Build.BuildNumber. This variable is not available during the static evaluation phase.
2019-03-26Enable unit tests on .NET Core (#489)Sven Boemer
This enables the unit tests to run on .NET Core. CodeDom compilation doesn't exist on core, so I've added the ability to compile in-process with Roslyn APIs. This still uses NUnit, using a recent version of NUnit package references with "dotnet test". This doesn't change how tests run on mono. Finding the right reference assemblies for compilation is a bit different on .NET Core. As described in https://github.com/dotnet/roslyn/wiki/Runtime-code-generation-using-Roslyn-compilations-in-.NET-Core-App, they can either be found using packages (what the SDK does), or we can just compile against the implementation assemblies. In this change, I'm compiling against implementation assemblies, since that's fairly similar to what the tests do on mono, where they find them in the GAC. For mono, the common references only included mscorlib. For .NET Core, I'm getting the common references from the "Trusted Platform Assemblies" (TPA) of the test process. As a result, package references of the test project become references during testcase compilation. Explicit references specified via `ReferenceAttribute` in a testcase are looked for alongside the host process's implementations as well (since we have no way to resolve a reference from just the filename since there is no GAC). Other changes: - Roslyn outputs the `DebuggableAttribute` by default but mcs does not, so when running on .NET Core, we don't check for the `DebuggableAttribute`. - Check for core types in `System.Private.CoreLib` instead of `mscorlib`. - There are some more edge cases that I'm in the process of cleaning up and will update soon. At the moment, I'm trying to get the tests up and running, and I'm using plenty of compile-time conditions to modify the behavior on core. It would be nice not to have to do this - I haven't given it much thought, but maybe we could provide an abstraction that contains knowledge of the platform libraries, so that we don't have to have a hard dependency on `"mscorlib.dll"` and `"System.Private.CoreLib.dll"` everywhere? @mrvoorhe please let me know if you have any thoughts. Does the approach I'm taking so far seem sane to you? @marek-safar
2019-03-19Fix public build definition (#490)Sven Boemer
* Fix public build definition * Specify DotNetSignType * Don't pass official build ID to public jobs Use new azure-pipelines syntax to reduce duplication of conditions
2019-03-01Set up Azure Pipelines to build illink (#476)Sven Boemer
* Add .yml build definition * Add linux linker build * Remove left-over pool section * Set helixRepo for telemetry * Add windows build, and use recommended pool * Add dotnet-core blob feed * Add helix variable group * Checkout submodules * Remove dependency on NuGet.ProjectModel * Specify release configuration * Sign with 3rd-party certs * Fix signing props * Publish build logs * Set _DotNetPublishToBlobFeed * Use new variable syntax * Use _BuildConfig variable for arcade templates * Set msbuild variable for blob feed publish * Add blob feed url * Add blob feed token and pass build id * Add _TeamName for microbuild * Fix syntax * Set DotNetSignType from _SignType * Publish only on windows * Only publish build asset manifest on windows * Only pass signing variables to windows * Add displayName for build command * Put publish args in a variable * Remove Nuget.ProjectModel dependency * Use jobs.yml template and add ci build * Disable custom certificate for ILLink.CustomSteps signing * Generate assembly info for ILLink.CustomSteps * Remove unnecessary properties from ILLink.CustomSteps project * Clean up Signing.props