Any idea why
'DotNetCorePublishSettings' does not contain a definition for 'PublishSingleFile' ? docs say it should be there https://cakebuild.net/api/Cake.Common.Tools.DotNetCore.Publish/DotNetCorePublishSettings/8EA20DA4 :/
DotNetCorePublishSettings screams:'DotNetCorePublishSettings' does not contain a definition for 'PublishSingleFile' ? docs say it should be there https://cakebuild.net/api/Cake.Common.Tools.DotNetCore.Publish/DotNetCorePublishSettings/8EA20DA4 :/
Hello, anybody could help? I have dotnet 3.1 installed and am trying to use cake to build a project of targeting both netstandard2.0 and netcoreapp3.1, and it just raise error that said cannot use dotnet core 2.1 to build .netcoreapp3.1 library, and it shows an c#7 language syntax error about the
ref keyword.
i have multiple projects for which i have to write build scripts, can i use the build.cake as nuget package and supply the variables from my each project
Hello all! Some days ago we've encountered an issue that using xmlpeek causes files to be unavailable for other processes to read in case there are intersections during build process or another build works with the same file. I did a kind of research and found that cake's xmlpeek does a filestream with
FileShare.None property. The question is - can we create a bug for this and change to FileShare.Read? As we have a large amount of builds per day these intersections became very common for us, so it will be great to be fixed inside the root tool instead of doing workarounds and I believe will help others who face such issue.
@Asemirski interesting what's the use case to have multiple processes read and modify same file simultaneously on CI?
FileShare.None could be a feature rather than bug.
The case is that we do a xmlpeek to super-secret variables placed in a file on build agents. As it was described above we have a lot of builds during the day so some of them can do this peek at one time causing "file is used". Additionally this file is used in some other activities while cake is peeking inside.
Raise an issue.
And maybe send PR if possibleš
Hi there :) I have a problem with xamarin and gitlab CI (running on linux). I read that cake is a good option to build xamarin projects on linux so I tried. I built my project according to https://servocode.com/blog/gitlab-continuous-integration-configuration-xamarin and now I get an exception, you can see it there: https://servocode.com/blog/gitlab-continuous-integration-configuration-xamarin ... Do you know what I'm doing wrong or if there is missing something?
sry
I don't see any constructor parameter called "value" in https://github.com/cake-build/cake/blob/develop/src/Cake.NuGet/NuGetPackageInstaller.cs#L58
Oh, sry ... I googled again with another keywords and get this: cake-build/cake#2636 so my issue is a duplicate, will close it.
That's my call:
mono /builds/app/tools/Cake/Cake.exe /builds/app/tools/build.cake -verbosity=diagnostic -configuration=Release -target=Restore-NuGet
mono /builds/app/tools/Cake/Cake.exe /builds/app/tools/build.cake -verbosity=diagnostic -configuration=Release -target=Restore-NuGet
for those who have the same problem: https://github.com/chiticariu/xamarin-android
NET Core using global tool Cake.Tool
When specifying the
I've only gotten this to work by specifying
runtime for the DotNetCoreBuildSettings are we allowed to use any? According to this anyis a valid value, isn't it? https://github.com/dotnet/runtime/blob/master/src/libraries/pkg/Microsoft.NETCore.Platforms/runtime.jsonI've only gotten this to work by specifying
win-x64, but I would like this assembly to be available for .netcore3.1 projects running on Linux as well. Do I have to produce two separate nuget packages?
Another question. Where does artefacts published by BuildSystem.TeamCity.PublishArtefacts(...) end up? We have a nuget repo set up in TC but canāt see that PublishArtefacts places them there. What are we missing?
Unsure but
PublishArtifacts should be done in background, TeamCity docs at https://www.jetbrains.com/help/teamcity/build-script-interaction-with-teamcity.html#BuildScriptInteractionwithTeamCity-PublishingArtifactswhiletheBuildisStillinProgress
On our build server I have registered a new package source as well as set the api key for said source. When running our cake.build script the build fails because the build process only looks in the existing nuget sources (TeamCity in-built repo + nuget.org). Why isn't cake and/or the build picking up the new nuget source? What can we do to solve this problem?
DirectoryHashCalculator
Is an implementation in Cake.Common.Security useful for creating a hash of an entire directory? The usage would be about the same as the FileHashCalculator, just that a DirectoryPath is specified instead of a FilePath. The implementation should return a DirectoryHash instead of a FileHash. The GetHashAlgorithm function in FileHashCalculator should be outsourced for common use. Is the described DirectoryHashCalculator implementation in Cake.Common.Security interesting and useful for the Cake Team?
Or use VSWhere to find specific version and set ToolPath on msbuildsettings.