codequality | Codequality jobs in pipelines https | MLOps library

I need my pipeline to produce a SNAPSHOT or release artifact, and then also produce a Docker image tagged with latest, or with the version number of the release. I am using the fabric8 plugin and taking advantage of the feature that will produce a tag based on the version field of the POM file.

Due to the order of the stages the tag will always be latest, regardless of whether its a snapshot or a release. I need some help to determine the proper way to do this as I cant see a way to put them in a different order.

The tools involved are Maven + fabric8, Jenkins, Artifactory, and SVN.

After the Maven release and prepare steps the POM will have a SNAPSHOT version, so the stage "Create Docker Image" will always produce a tag of 'latest'.

I could do something like figure out what the SVN tag url is for the released version and check it out and then do my build. That feels wrong though, but maybe not. There has to be a more "official" way of doing this.

I have a DLL addressing the .NET 4.7.1 library.

Probably irrelevant, but it's written in C# and consumes NuGet packages using the "packages.config" pattern, rather than the newer PackageReference configuration.

I publish this as a NuGet package (have been doing this for several years). But now when I execute the following:

I'm trying to build an ASP.NET-Core 3.1 (netcoreapp3.1) application which has a dependency on a NuGet library that is .NET-Standard 2.0 which uses MSBuild SDK "Microsoft.NET.Sdk.Razor".

This builds and runs fine from Visual Studio (2019) but when I run dotnet build I get the following error:

I followed the official guid deploied a pipline to analyse my code quality. Although the pipline passed and the job successed, the json file didn't generated by docker. And these notis displaied:

WARNING: A new version (v0.83.0) is available. Upgrade instructions are available at: https://github.com/codeclimate/codeclimate#packages Uploading artifacts... WARNING: gl-code-quality-report.json: no matching files ERROR: No files to upload
Job succeeded

And this is my /etc/gitlab-runner/config.toml file:

I am a bit confused about the various code analyzers for .NET Core.

If you create a default .NET Core web project, you get the Microsoft.CodeAnalysis.Analyzers.

In addition, on NuGet, there is Microsoft.CodeQuality.Analyzers (note the slight difference in the name). After installing it, I see that it contains a lot more rules.

And finally, there is also Microsoft.CodeAnalysis.FxCopAnalyzers, which appears to contain Microsoft.CodeQuality.Analyzers.

So what exactly is the relationship between Microsoft.CodeAnalysis.Analyzers, Microsoft.CodeQuality.Analyzers and Microsoft.CodeAnalysis.FxCopAnalyzers? What should my project have?

P.S. After creating a new project, I search NuGet for Microsoft.CodeAnalysis.Analyzers package (which already exists in my project). It finds it and states my project has v1.1 and that it needs to upgrade it to v2.9.4. However, according to NuGet, v1.1 was released in 2015. This makes no sense as I am using VS2019 and there have been plenty of releases of this analyzer between 2015 and 2019.

However, when I upgrade the package to 2.9.4 - the analyzer has the same 3 rules that v1.1 had. So what exactly am I upgrading?

My ci configuration isn't working with code quality stage:

I'm unable to get CA1062 (validate arguments of public methods) to evaluate.

I've created a .Net Standard 2.0 C# class library and installed Microsoft.CodeQuality.Analyzers and several others nuget packages as per this screenshot:

I've also enabled CA1062 in the ruleset for the project, as per the image:

I've created this class to test if CA1062 (validate arguments of public methods) does evaluate:

On this project: https://gitlab.com/tyvain/parcoursup/tree/master

I have a code quality stage:

I'm testing Gitlab AutoDevOps with my project. My problem is that AutoDevOps do a quality check, it passes, but I don't know where to find the result, is says it upload an artifact, but doesn't say where.

Here are the logs: