ci

Continuous Integration

Worth looking at

dotnet-releaser:

dotnet-releaser is an all-in-one command line tool that fully automates the release cycle of your .NET libraries and applications to NuGet and GitHub by building, testing, running coverage, cross-compiling, packaging, creating release notes from PR/commits and publishing.

Gitlab

Documentation Generation

Document generator for Gitlab : from Markdown to PDF

Resources

CI/CD Examples
Pipeline Examples
Medium:
- GitLab CI/CD with .Net Framework
- Continuous Integration with .NET Core and Gitlab

See also: https://www.one-tab.com/page/bkeYdZhaTESMtPXdbHIZvQ

Nuget

Fixing a really common misunderstanding about nuget.exe
- See also: https://github.com/mrlacey/WindowsTestHelpers/blob/main/src/packandsignnupkg.targets
Using GitHub actions and .NET templates: https://rehansaeed.com/the-fastest-nuget-package-ever-published-probably/

Dependabot

Now fully integrated to GitHub, for Azure DevOps, not quite here yet...

Cake

How to build with Cake on Linux using Cake.CoreCLR or the Cake global tool: https://andrewlock.net/how-to-build-with-cake-on-linux-using-cake-coreclr-or-the-cake-global-tool/
A bootstrapper script for the Cake .NET Core Global Tool on Windows: https://andrewlock.net/a-bootstrapper-script-for-the-cake-net-core-global-tool-on-windows/

Example projects

Generating Nuget/Assembly Version info: https://cezarypiatek.github.io/post/setting-assembly-and-package-metadata/
https://github.com/Microsoft/perfview
- Appveyor config: https://github.com/Microsoft/perfview/blob/master/appveyor.yml
- Codecov config: https://github.com/Microsoft/perfview/blob/master/.codecov.yml

Code Coverage

Generate Code Coverage Reports with ReportGenerator in Azure DevOps: https://ardalis.com/generate-code-coverage-reports-with-reportgenerator-in-azure-devops
ReportGenerator
- https://github.com/danielpalme/ReportGenerator
- Supported by cake: https://cakebuild.net/dsl/reportgenerator/
- History: https://github.com/danielpalme/ReportGenerator/wiki/Custom-history-storage

CI/CD

Concourse: https://concourse-ci.org/
- Installation Tricks; in the yaml:
  - set privileged to false (privileged s not supported when Docker is in Windows mode)
  - Per https://github.com/concourse/concourse/issues/3758, append CONCOURSE_WORKER_TSA_WORKER_PRIVATE_KEY: a at the end of the file
- Tuto: http://concoursetutorial.com/
Gocd: https://www.gocd.org/

Github Actions

Articles:
- Publish VSCode extension using GitHub Actions
Series:
- https://abelsquidhead.com/index.php/2019/08/30/github-actions-2-0-is-here/
- https://abelsquidhead.com/index.php/2019/09/02/github-actions-2-0-lets-do-something-a-little-more-involved/; comment from this post:
Azure DevOps Services and Server are still here and going strong. In fact, the office team at microsoft just moved everything over to Azure DevOps Services.

GitHub is a premium offering from Microsoft. They are cloud agnostic and Actions only work with GitHub.

Open source? Code already in GitHub? Makes perfect sense to use Actions (specially when Actions gets more fully fleshed out in terms of features). You’re an enterprise whose code is not in GitHub? Azure DevOps Services work GREAT. And you are now left with a choice. Do you want to pay the premium for GitHub? Is the extra chrome you get with GitHub worth it to you?
- https://abelsquidhead.com/index.php/2019/09/07/writing-my-first-custom-github-action/
Other material fromthe same author:
- Example Github Actions: https://github.com/abelsquidhead/MercuryHealthCore/blob/master/.github/workflows/FullCICD.yml
- https://github.com/abelsquidhead/MercuryHealth
Multiple repo checkout: https://github.com/actions/checkout
Awesome Github Actions: https://github.com/sdras/awesome-actions
Artifacts: https://help.github.com/en/actions/configuring-and-managing-workflows/persisting-workflow-data-using-artifacts
- NB: GitHub does not currently offer a REST API to retrieve uploaded artifacts.
- Retention: Artifacts automatically expire after 90 days
- https://github.com/actions/upload-artifact/issues/45
- https://github.com/actions/upload-artifact/issues/49
- https://github.com/kolpav/purge-artifacts-action

Azure DevOps

Articles
- Azure DevOps Pipelines – Multi-Stage Pipelines and YAML for Continuous Delivery
- Exploring Azure DevOps APIs
Everything as Code with Azure DevOps Pipelines
- Part #1: https://jeremylindsayni.wordpress.com/2019/06/10/everything-as-code-with-azure-devops-pipelines-c-arm-and-yaml-part-1/
- Part #2: https://jeremylindsayni.wordpress.com/2019/06/10/everything-as-code-with-azure-devops-pipelines-c-arm-and-yaml-part-2-multi-stage-builds-in-yaml/
VSTS is now Azure DevOps. What has changed and why? https://www.dotnetcurry.com/devops/1473/vsts-azure-devops-change
Using Secrets in Azure Pipelines: https://www.dotnetcurry.com/devops/1507/azure-key-vault-secrets-pipelines
Azure DevOps - YAML for CI-CD Pipelines: https://www.dotnetcurry.com/devops/1522/azure-devops-yaml-ci-cd-pipelines
Tutos
- Using Azure DevOps for CI / CD of ASP.NET Core application to Azure Kubernetes Service (AKS): https://www.dotnetcurry.com/devops/1518/aspnet-core-cicd-azure-kubernetes-service
- Using Azure DevOps for Build and Deployment of NodeJS application: https://www.dotnetcurry.com/devops/1486/azure-devops-build-deploy-nodejs
- Using Azure DevOps for NodeJS application optimization using Gulp: https://www.dotnetcurry.com/devops/1487/azure-devops-nodejs-optimize-using-gulp
- Azure DevOps to build and deploy ReactJS App: https://www.dotnetcurry.com/devops/1488/azure-devops-build-deploy-reactjs
- Azure DevOps for TypeScript React.JS App: https://www.dotnetcurry.com/devops/1499/azure-devops-typescript-reactjs
- Azure DevOps for Angular Applications: https://www.dotnetcurry.com/devops/1504/azure-devops-angular-app
- Security in Azure DevOps (formerly called VSTS): https://www.dotnetcurry.com/devops/1496/azure-devops-security
- Use REST APIs to access Azure DevOps (formerly VSTS): https://www.dotnetcurry.com/devops/1485/using-rest-api-azure-devops
- https://sibeeshpassion.com/move-git-repositories-from-one-to-other-organization-in-azure-devops/
- shields: https://raw.githubusercontent.com/ngs-lang/ngs/master/readme.md
- Multiple-stage pipelines:
  - https://mohitgoyal.co/2019/07/30/create-multi-stage-pipelines-with-yaml-in-azure-devops/
  - https://mohitgoyal.co/2019/08/21/add-manual-approvers-for-release-stages-in-multi-stage-pipelines-in-azure-devops/
Multiple repo Checkout:
Reuse:
- Task groups: https://docs.microsoft.com/en-us/azure/devops/pipelines/library/task-groups?view=azure-devops&viewFallbackFrom=vsts
- Yaml templates: https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema%2Cparameter-schema#step-templates
Articles:
- Caching and faster artifacts in Azure Pipelines
Admin
- Measuring Concurrent Jobs Over Time
Docker
- How the .NET Team uses Azure Pipelines to produce Docker Images

Azure DevOps vs Github Actions

Essentially, the GitHub Actions feature seems to be Azure Pipelines baked right into GitHub.

From a long term perspective, I'm curious about the future of GitHub as it pertains to Azure DevOps. Several speakers have described the GitHub community as "40 million collaborators to work with", so perhaps Microsoft intends to keep GitHub for open source projects, and Azure DevOps for private industry. We shall see.

Then: https://www.jamesqmurphy.com/blog/2019/11/github-actions-is-not-azure-pipelines

I was wrong about GitHub Actions being just "Azure Pipelines baked right into GitHub".

In my previous post I challenged myself to convert my existing Azure DevOps Pipeline into GitHub Actions. So how did that work out?

What did not work (so well):

Build Numbers: GitHub Actions simply does not have the concept of build numbers.

No Build Variables: In GitHub Actions, there are no build variables per se.

Conclusion:

They do serve different purposes. GitHub is geared for Open Source projects, (...) GitHub will (and must) remain neutral. (...) Azure DevOps can promote the heck out of Microsoft Azure.