I am unable to install the VSTS Agent Azure VM extension on an Azure VM. I tried both the Install extension blade in the Azure portal and the Powershell option. When I try from the portal it just gets stuck at transitioning. If I run the Powershell script it gets stuck trying to connect to server.
I was able to install it on another server without any issues. The 2 servers are part of a web farm so they are exact images.
I am following the steps detailed at this url https://learn.microsoft.com/en-us/vsts/build-release/concepts/definitions/release/deployment-groups/howto-provision-deployment-group-agents?view=vsts .
I am trying to deploy from VSTS to an Azure VM.
This is the screen when I try to run the powershell script.
Run the config file directly (from C:/vstsagent folder) in cmdline and try again with dev.azure.com/{organisation name} url.
Related
Need to install LibreOffice to my Azure App Service.
1. Azure DevOps
I used powershell Start-Process to silent install but getting Permission denied.
Start-Process: /home/vsts/work/_temp/5cc8c99d-ed13-4b1b-823b-3cd9b56fdd1b.ps1:5
Line |
5 | Start-Process /home/vsts/work/1/s\LibreOffice_7.4.0_Win_x64.msi -Argu …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| An error occurred trying to start process
| '/home/vsts/work/1/s/LibreOffice_7.4.0_Win_x64.msi' with
| working directory '/home/vsts/work/1/s'. Permission denied
2. Kudu terminal
Getting Access Denied error when trying to run Start-Process manually.
Are there any alternatives to achieve this?
Not possible to install something on the host. The alternative is to use a docker container which has it already installed.
https://azure.github.io/AppService/windows-containers/
App Service supports Windows Containers! Deploying your application in a Windows Container enables you to bring along dependencies such as custom fonts, cultures and GAC deployed assemblies. When deploying a containerized application, the Windows Container is an isolation and security boundary. As a result, calls to libraries that would normally be blocked by the Azure App Service will instead succeed when running inside of a Windows Container.
I'm trying to deploy RestAPI with https port for .net core 3.1 project.
I can run it manually by Powershell.
But when I try to run Powershell in Azure DevOps Release Pipeline.
Below is setup steps:
Stop Current RestAPI process + Delete all current file.
Extract new release to target deploy folder
Start Rest API process with port defined:
Start-Process -FilePath $env:WebsiteLocation\$env:ProcessName --urls="$env:PortNumber" -WorkingDirectory $env:WebsiteLocation
If PortNumber is http://... it work. new process start in deploy agent
If PortNumber is https://... it didn't work. no any process is started
Could you please help share with the reason why i got this issue.
Thanks a lot.
Actual i have installed a self hosted agent on my local machine
now my issue is when i am running a release pipeline for a client machine i have a powershell task in which i have a command that runs an exe file located in client machine which displays a message box .
but when I am checking at client machine i am able to see the exe is running in task Manger during the execution of my release pipeline but show how i am not able to see the interface of the application .
You can try adding -Wait to your powershell command. For below example.
Start-Process -FilePath "path to programm.exe" -Wait
You also need to make sure the deployment agent(the agent installed on client machine) is running in interactive mode.
To configure the agent in deployment group to run in interative mode. You need to change the Registration script you copied in azure devops. Remove --runasservice when you run the registration script on the client machine
Then you will be asked to set the agent to run as service or not as below screenshot(Please enter or type N to select interative mode) during the setup.
Check Interactive vs. service for more information.
We are migrating from Jenkins to Azure and in our deployment we used Powershell scripts, for our initial move we are trying not to adjust our Powershell scripts and just change the bare minimum to get them working.
On the running of command:
az webapp deployment source config-zip --name Name --resource-group RG --src Path/To/Zip.zip
When we used this command before we got the warning:
WARNING: Getting scm site credentials for zip deployment
We now get this warning as an Error:
[error]WARNING: Getting scm site credentials for zip deployment
I have adjust the settings to try continue past errors but it falls out anyway. Anyone know how to fix this?
I am using version 2.0.60 of Azure-cli. I have tried with az webapp deployment source config-zip command, I also got the warning. But the webapp was deployed successfully.
You can also deploy the zip file via browser.
1.In the browser, navigate to https://<app_name>.scm.azurewebsites.net/ZipDeployUI.
2.Drag the zip file to the file explorer area on the web page
I've an App Service running in Azure, it's only a simple node.js app.
I wanted to use a custom deployment script (because I've to execute npm install in a subdirectory) as it is described here:
https://github.com/projectkudu/kudu/wiki/Customizing-deployments
https://github.com/projectkudu/kudu/wiki/Custom-Deployment-Script
https://medium.com/#premchandrasingh/custom-continuous-deployment-script-kudu-for-azure-75217ddcebc5
After uploading the deployment package (via .zip file), the execution of the script "fails".
Reason:
/opt/Kudu/bin/Scripts/starter.sh: line 2: /tmp/zipdeploy/extracted/deploy.sh: Permission denied
There must be any problem with kudu or the VM of the webapp.
Any idea?