Azure pipeline How to use bigger server for hosted agent builds? - macos

I don't understand but how do I set in the hosted azure pipeline build server to be a bigger machine with more ram and more CPU's?
i want to avoid installing a self-hosted agent on one of the Azure VM's I just want to use more stronger hosted agent, where can i configure this?
I'm using a hosted MAC agent.

This is not possible. Please check this documentation
If Microsoft-hosted agents don't meet your needs, then you can deploy your own self-hosted agents or use scale set agents.

Related

How to determine if an asp.net app is running on an azure vm

We have an asp.net app that gets deployed to both On-Prem and on Azure VMs. We are trying to figure out how to configure the app so that when deployed on an Azure VM it will use Azure App Configuration Service, but when deployed On-Prem it will continue to use the settings in the config files?
How can we know on app start up whether or not we are deployed on an Azure VM?
If you can, I would recommend you add a special environment variable when you provision your Azure VM or deploy your application. If not, you may use Azure Instance Metadata Service to tell the code is running in Azure VMs.

Use AWS Spot instances for build agents?

Use AWS Spot instances for build agents?
Our infra setup is in AWS but we use Azure DevOps for repo, boards & pipelines. To run automated tests like cucumber, we need private agent. if there's a way to utilize spot instances for builds instead of having to have agents always on?
or
can we have a Master slave setup, like how Jenkins has?
In the self-hosted agent configuration, we can set the agent to run as service, If you configured the agent to run as a service, it starts automatically. You can view and control the agent running status from the services snap-in.
If we configured the agent to run interactively, open org settings->Agent pools->select agent pool and click the tab Agents, we can see the agent status is Offline if we do not open the run.cmd, if we need to use the agent, we can open the agent file run.cmd to run the agent.
Please refer this link for more details: Self-hosted Windows agents

Deploying from Azure Devops to AWS machine behind VPN

We have our machines that we want to deploy to on AWS private subnet and we connect to them via VPN.
We want to use Azure Devops to build and deploy our code. Is there a way to deploy from Azure Devops to AWS machines through VPN?
Make sure your machine can access dev.azure.com, then you can try AWS Toolkit for Azure DevOps extension to work with AWS services.
Also, you can install one self-agent on your machine so that you can run the pipeline in your local environments.

Windows Server Containers in Google Kubernetes Engine (GKE)

I'd like to run Windows containers in GKE.
Is it possible to use Windows Server Containers OS in Google Kubernetes Engine?
I see Windows Server Containers OS is available in Compute Engine and seems that Kubernetes support is available for Windows.
It is possible to run Windows containers, but only as a container in a Compute Engine VM instance.
I would refer you to this article in the GCP blog. Please be aware that there a few known issues that you should read before deploying Windows containers in Windows VM instances.
For GKE, there is currently a Feature Request. Other customers have asked to include future support for Windows containers in GKE. This is a request through official means. Google will consider the need based on its feasibility, or the number of customers who ask for it, but they can't guarantee an implementation or provide you with an ETA for it.

Kubernetes windows agent

Hey I'm running a Kubernetes cluster on Azure using ACS.
My question is if there is any way to add a Windows agent to the cluster without completely rebuilding the cluster?
I know this is possible for Linux distro's depending on what you use but I wonder if anyone knows a way to do this for Windows agents?
If you have deployed your cluster using the Azure portal then you can simply follow the instructions here https://learn.microsoft.com/en-us/azure/container-service/container-service-scale
But if you have deployed using the ACS engine and ARM template then currently there is an issue that it does not creates the acs resource.

Resources