shell-core | shell functions designed to ease the development | Command Line Interface library

That loader loads nunit projects. You want the VSProjectLoader.

Install with

Solution has been found. Here's how I resolved this for anyone coming across this post:

I discovered a helm chart for Azure Pipeline agents - emberstack/docker-azure-pipelines-agent - and after poking around in the contents, discovered what was staring me in the face the last couple of days: "StatefulSets"

Simple, easy to test, and working well so far. I refactored my k8s manifest as a StatefulSet object and the agents are up and able to run builds concurrently. Still more testing to do, but looking very positive at this point.

There is no XML-RPC functionality built into PowerShell.

Providing such functionality therefore requires third-party code.

In your case, it seems your script requires the XmlRpc module, available from the PowerShell Gallery here (which means you can install it with Install-Module XmlRpc).

However, this module was last updated more than 5 years ago, predating PowerShell's cross-platform edition, PowerShell (Core), so you'll have to find out yourself if it works on a Unix-like platform such as Ubuntu.

Your CI is failing because it doesn't know the credentials for artifactory.example.com when downloading the base image artifactory.example.com:5000/repo/powershell-core:6.3. For you to understand, I'll explain the different steps of the 2 CIs you gave and then I'll give tracks for a solution.

In your first CI (the one using DinD), what happens is :

• The Gitlab-runner executor download the image docker:18.09.8-dind and then it starts the image as a service for your CI
• The Gitlab-runner executor download the base image docker:latest and then it uses it to execute your job run_script
• In your docker docker:latest, the job run_script log in your private repository with your credentials and through the DinD service
• Then it download your image artifactory.example.com:5000/repo/powershell-core:6.3 and run a script using it, all through the DinD service

In this one, you are trying just to execute your image artifactory.example.com:5000/repo/powershell-core:6.3 and run a script using it. You are right, for a simple goal like that no DinD is necessary. Here is the analysis of what your CI is doing :

• The Gitlab-runner executor try to download the base image specified by the job run_script : artifactory.example.com:5000/repo/powershell-core:6.3
• The repository artifactory.example.com ask for credentials
• The executor doesn't know any credentials so it returns an error and it stops

As you can see, in this case, the job run_script was never executed because the executor failed to download the base image specified by the job. The before_script part of the job, which is responsible for the login, is not executed either because the before_script is executed in the base image and this last one couldn't be downloaded by the executor.

Thus, the solution is simply to give the credentials to the executor so it can login and then download the base image of your job. Also, the before_script part of your job should be removed because it is not executed at the time you intended and therefore not necessary.

So what you seek is a way to give the credentials for your repository artifactory.example.com to the Gilab-runner executor your job is using. Sadly, there is no unique way to do such a thing because it depends on the executor that you are using. Since you didn't specify the executor in your question, I'll give the solutions that, I think, are the most used and convenient for Docker and Kubernetes.

One solution which works with several executors is to define a (secret) variable directly in Gitlab as explained in this Gitlab documentation.

Here, I present the second method to prepare your credentials. Adapt the following to generate your own auth fied :