DevOps | smiley DevOps System heart devEops heart | Configuration Management library

Kubernetes is a container orchestrator that may use Docker as its container runtime. So, they are quite different things—essentially, different levels of abstraction.

You could theoretically run an application at both of these abstraction levels. Here's a comparison:

Docker

You can run an application as a Docker container on any machine that has Docker installed (i.e. any OS or cloud provider instance that supports Docker). However, you would need to implement any operations-related features that are relevant for production, such as health checks, replication, load balancing, etc. yourself.

Kubernetes

Running an application on Kubernetes requires a Kubernetes cluster. You can run a Kubernetes cluster either on-premises, in the cloud, or use a managed Kubernetes service (such as Amazon EKS, Google GKE, or Azure AKS). The big advantage of Kubernetes is that it provides all the production-relevant features mentioned above (health checks, replication, load balancing, etc.) as part of the platform. So, you don't need to implement them yourself but just use the primitives that Kubernetes provides to you.

Regarding your two requirements, Kubernetes provides both of them, while using Docker alone does not provide easy production-readiness (requirement 2). So, if you're opting for production stability, setting up a Kubernetes cluster is certainly worth the effort.

Yes, this is correct. Because failed is equivalent of eq(variables['Agent.JobStatus'], 'Failed') status. But partially succeeded is eq(variables['Agent.JobStatus'], 'SucceededWithIssues').

Please check here.

You may try custom conditions like :

There is no extension like "Cypress GitHub app" in azure devops, so it is impossible to achieve exactly the same function as in github pull request.

As a workaround , you can try to add status policy.

Using status alone, details from an external service can be provided to users within the PR experience. Sometimes, sharing information about a PR is all that is necessary, but in other cases PRs should be blocked from merging until requirements are met. Like the in-box policies, the Status policy provides a way for external services to block PR completion until requirements are met. If the policy is required, it must pass in order to complete the pull request. If the policy is optional, it is informational only, and a status of succeeded is not required in order to complete the pull request.

External services can use the PR Status API to post detailed status to your PRs. The branch policy for external services brings the ability for those 3rd party services to participate in the PR workflow and establish policy requirements. This article guides you through the process of configuring a branch policy for a service that is posting PR status.

In addition, here is a ticket about how to create required pull request status check, you can refer to it.

Sure, you can use the API "Test Point - Update" to update the outcome of test points.

For example, I have two test points (id are 22 and 23) are 'Active'.

I can use this API to update one to be 'Passed' and another one to be 'Failed'.

• Request URI:

You will find your artifacts here:

You got single file because you have in VSBuild /p:PackageAsSingleFile=true

Also you may consider using a newer task Publish Pipeline Artifact. If not please check DownloadBuildArtifacts task here

This error is because the build task is not configured. You can try to put the below YAML code at the last to make it work.

You can't ever rely on the workspace being the same between jobs, period -- jobs may run on any one of the available agents, which are spread across multiple working folders and possibly even on different physical machines.

Have your jobs publish artifacts.

i.e.

Try using the filename in variable as shown below. Notice the {} around variable. Ensure that your ls command returns only 1 file. For multiple files use multiple -F arguments.

Sample test data:

This is an feature in Project Settings. I checked the related REST API and Azure CLI for Team Projects, however I did not find any available interface can list the info about enabled / disabled services, also no available interface to enabled / disabled services.

So, I think your question is more like a feature request. I recommend that you can report the feature request to Developer Community.

[UPDATE]

I found below API from the Network logs of the web browser (press F12). I have tested this API on my side, it should be the one you are looking for.

• Request URI: