nobuild | Header only library for writing build recipes in C | SDK library
kandi X-RAY | nobuild Summary
kandi X-RAY | nobuild Summary
Header only library for writing build recipes in C.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of nobuild
nobuild Key Features
nobuild Examples and Code Snippets
Community Discussions
Trending Discussions on nobuild
QUESTION
I have source control and pipelines in Azure Devops.
My project has two target frameworks: 3.1 and 6.
While running the pipeline, it throws errors when restoring packages:
##[error]The nuget command failed with exit code(1) and error(Errors in D:\a\1\s\nuget-tst\src\nuget-tst.csproj Package Microsoft.Extensions.Configuration.Json 3.1.3 is not compatible with net60 (.NETFramework,Version=v6.0). Package Microsoft.Extensions.Configuration.Json 3.1.3 supports: - netcoreapp3.1 (.NETCoreApp,Version=v3.1) - netstandard2.0 (.NETStandard,Version=v2.0) Package Microsoft.Extensions.Configuration.FileExtensions 3.1.3 is not compatible with net60 (.NETFramework,Version=v6.0). Package Microsoft.Extensions.Configuration.FileExtensions 3.1.3 supports: - netcoreapp3.1 (.NETCoreApp,Version=v3.1) - netstandard2.0 (.NETStandard,Version=v2.0) Package Microsoft.Extensions.Configuration.EnvironmentVariables 3.1.3 is not compatible with net60 (.NETFramework,Version=v6.0). Package Microsoft.Extensions.Configuration.EnvironmentVariables 3.1.3 supports: - netcoreapp3.1 (.NETCoreApp,Version=v3.1) - netstandard2.0 (.NETStandard,Version=v2.0) One or more packages are incompatible with .NETFramework,Version=v6.0. Package Microsoft.IdentityModel.Tokens 6.5.0 is not compatible with netcoreapp3.1 (.NETCoreApp,Version=v3.1). Package Microsoft.IdentityModel.Tokens 6.5.0 supports: - net45 (.NETFramework,Version=v4.5) - net461 (.NETFramework,Version=v4.6.1) - netstandard2.0 (.NETStandard,Version=v2.0) Package Microsoft.Extensions.FileSystemGlobbing 3.1.3 is not compatible with netcoreapp3.1 (.NETCoreApp,Version=v3.1). Package Microsoft.Extensions.FileSystemGlobbing 3.1.3 supports: netstandard2.0 (.NETStandard,Version=v2.0) One or more packages are incompatible with .NETCoreApp,Version=v3.1.) ##[error]Packages failed to restore
The azure pipelines yaml:
...ANSWER
Answered 2022-Mar-21 at 13:39something similar happened to me. Solved it by adding a nuget tool installer task before the nuget restore step:
QUESTION
I am trying to integrate SonarQube in a CI-pipeline in Azure DevOps. I used the exact configuration that I used in other pipelines where everything runs smoothly. However, this pipeline can't find the analysis in the SonarQube Publish step as shown in the logs below.
...ANSWER
Answered 2022-Feb-26 at 00:04As Mickaël Caro stated on my similar post in the SonarSource community forum:
Unfortunately some characters are not recognized nor parsed correctly when we try to find the report path (We do have this issue filed here : [VSTS-240] Escape regex characters when finding report path file. - SonarSource).
I changed the [ ]
in the name of the build to ( )
, and the analysis runs smoothly.
QUESTION
I am trying to set the Build name/Build description based on the outcome of a shell script. For example, I am executing the following lines in shell:
...ANSWER
Answered 2021-May-20 at 09:19I solved a similar issue by:
BUILD_LOG_REGEX
- email-ext plugin
Here is a tutorial http://siddesh-bg.blogspot.com/2012/04/using-buildlogregex-in-jenkins-email.html .
By BUILD_LOG_REGEX
the above mentioned plugin is able to query and extract parts of the build log.
QUESTION
I have multiple NuGet packages in the same repository. I would like to AutoVersion my packages to $Major.$Minor.$Patch-CI-$DateTimeStamp. $Major.$Minor.$Patch-CI-$rev would also work.
If I know what the original version is, it will make the NuGet package easier to understand. I can also ensure that my dev NuGet packages are a higher version than my master NuGet packages. I don't want to manually set the Major, Minor, and Patch variables because there are multiple NuGet packages in the solution.
The following attempt always has Major.Minor.Patch as 1.0.0
...ANSWER
Answered 2021-Apr-23 at 09:46Azure DevOps pipeline task NetCoreCLI pack. AutoVersion but keep Major.Minor.Patch unchanged
You should defined the Major, Minor, and Patch as variables in the YAML file and pass them as arguments for the task DotNetCoreCLI
:
QUESTION
Brand-new Cake project, build.cake
written as in Setting Up A New Project, added to a net5.0
console application.
When running dotnet cake
, the task Clean is silently skipped by runner.
I ran dotnet cake --target="Clean" --verbosity=normal
and received this:
Error: One or more errors occurred. (Could not reach target 'Clean' since it was skipped due to a criteria.)
No idea what criteria is skipping the task.
My build.cake
:
ANSWER
Answered 2021-Apr-08 at 12:44The Clean
task in your script is defined with criteria, take a look at this line:
QUESTION
Basically, I have a pipeline that is pushing packages to a feed. I have it set to use environment variables to create a pre-release package version if the source is development
branch. Otherwise, it should read the versioning from the .csproj
file if the source branch is master
. According to the logs, the correct steps are running. However, when I get to the push
step, I notice in the logs that it's pushing a pre-release rather than the release to the feed despite the pre-release task not even running. What's going on and how can I fix this? Here are the tasks in question:
ANSWER
Answered 2021-Mar-10 at 06:41when I get to the push step, I notice in the logs that it's pushing a pre-release rather than the release to the feed despite the pre-release task not even running.
Based on my test, I could reproduce this issue when I run the pipeline with your Yaml Pipeline sample.
The root cause of this issue is the name of the environment variable PackageVersion.
When the environment variable name is PackageVersion, this issue will exist.
To solve this issue, you could change the environment variable name.
QUESTION
I am getting the above Compiler Error CS1061 for my ASP.NET web site build using .NET Framework 4.5.2.
I understand the error, but I do not understand why I am getting it.
Here is my StackTrace, showing that the error occurs in Site1.Master.cs
Line 590:
c:\Development\mcl959\Site1.Master.cs(590): error CS1061: 'mcl959.Person' does not contain a definition for 'HasEmail' and no extension method 'HasEmail' accepting a first argument of type 'mcl959.Person' could be found (are you missing a using directive or an assembly reference?)
Source: System.Web
HResult: -2147467259
HelpLink:
StackTrace:
at System.Web.UI.TemplateParser.ProcessException(Exception ex)
at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding)
at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding)
at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath)
at System.Web.UI.TemplateParser.ParseInternal()
at System.Web.UI.TemplateParser.Parse()
at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at
System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider)
at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders()
at System.Web.Compilation.BuildProvidersCompiler.PerformBuild()
at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath)
at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile, Boolean throwIfNotFound, Boolean ensureIsUpToDate)
at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean throwIfNotFound) at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp)
at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath)
at System.Web.UI.PageHandlerFactory.GetHandler(HttpContext context, String requestType, String virtualPath, String path)
at System.Web.HttpApplication.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Below is a screenshot including Line 590, highlighted, with Intelliscence showing the definition of HasEmail:
And below is a screenshot showing project mcl959 with class Person and my two (2) versions of the HasEmail function (the top one never got used):
The CS1061 error is caused when you try to call a method or access a class member that does not exist. As I have shown, it does exist in my code.
Why am I getting this error?
...ANSWER
Answered 2020-Nov-19 at 19:03If your application is an ASP web forms site (not an asp web forms application), it will compile the webpages only at runtime, on demand. That may be the reason that you're getting the error only at runtime, not in compilation time.
As of the error itselft, my guess would be that the lambda function is not executing in the same assembly as the class/method is defined. As it's marked as internal, it will throw that error.
https://docs.microsoft.com/pt-br/dotnet/csharp/language-reference/keywords/internal
QUESTION
I have a project that I would like to turn into a NuGet package in an Azure DevOps CI build. The relevant files in the solution look like this:
...ANSWER
Answered 2020-Nov-01 at 21:05According to the docs, you are missing required parameter for this task
QUESTION
I have the following Azure DevOps task which creates a nuget pack
before it´s pushed to the artifact.
ANSWER
Answered 2020-Oct-12 at 11:33You can add buildProperties: '$description$=mydescription'
to the task:
QUESTION
I was trying to set the package version using the following yml
, however I keep getting the error
##[error]No value was found for the provided environment variable.
when the dotnetcli task is executed.
ANSWER
Answered 2020-Sep-15 at 11:36Because you specified byEnvVar
you just need to give the variable name, when you put it with $()
you give the variable value and not the name.
So, just change it to:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install nobuild
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page