I am setting up continuous deployment in Windows and it works with self-hosted runner as I have installed Web Deploy in my server but how can I access it using cloud runners?
Related
I am using Bitbucket CI/CD for our deployment in our AWS Elastic beanstalk environment. Now Elastic beanstalk saves the application version before deployment and if your application version exceeds 1000 then it will throw error. Is it possible in CI/CD to delete the oldest application version before deployment?
I have enabled application lifecycle on elastic beanstalk but still, I am getting those errors.
I am just wondering if we can use the Release pipeline service to deploy the build on our clients' on-prem servers or the services are restricted to use within the organization?
Can we use release pipeline to deploy app on client's on-premises server?
Yes.
If you are using the classic UI release pipeline, firstly, you need to create a deployment group on your client's on-premises server and use it in your release pipeline.
Then you can use some tasks to deploy, such as IIS Web App Deploy task, Copy Files task.
If you are using the yaml pipeline, you need to create a self-hosted agent on client's on-premises server.
You can click Self-hosted Windows agents for creating Windows agents, Self-hosted Linux agents for Linux and Self-hosted macOS agents for macOS.
The following steps are similar to those in the classic UI pipeline.
I am having trouble trying to figure out how to get the .ZIP archive which is produced in a build pipeline for a Desktop App.
I would like to get the .ZIP archive deployed to one or more VMs in my test lab (not in the azure cloud).
I have seen tutorials on how to do this for Websites, but none for deploying a .NET Winforms Applications which is produced as a .zip artifact in my pipeline.
Any help in pointing me to some guidance on how to make this happen would be greatly appreciated.
You'll need to install an agent to a machine on your network and put it into an agent pool.
https://social.technet.microsoft.com/wiki/contents/articles/53386.azure-devops-create-configure-agent.aspx
Once you've done this, you'll be able to deploy to machines on your network the same way that an Azure Build Agent can deploy to a machine in Azure.
I am trying to deploy my asp.net mvc application to another server but getting this error:
Error 101 Web deployment task failed. (Could not connect to the remote computer ...
I have installed the Web Management service on the server and it is running?
I have also tried to queue a build in tfs which builds fine on the buildserver however the deployment is not happening:
/p:DeployOnBuild=True
/p:DeployTarget=MSDeployPublish
/p:CreatePackageOnPublish=True
/p:MsDeployServiceUrl=https://myserver:8172/msdeploy.axd
/p:MsDeployPublishMethod=WMSVC
/p:UserName=myserver\myadmin
/p:Password=mypassword
/p:AllowUntrustedCertificate=True
/p:DeployIisAppPath="Default Web Site/myappname"
You need to install the Web Deploy package from WebPI and ensure that you have ports 443 and 8172 open on your firewall.
Web Deploy Download if you don't PI
I noticed an error in my event log today that states:
The SQL Server Integration Services 10.0 service failed to start due
to the following error: The service did not start due to a logon
failure.
The service is configured to use ./sqluser but I cannot find this login with the domain.
What exactly is this services used for? What login should I be using for this service and what rights/privileges does the user need for this service to function properly. I am using SQL 2008 under Windows Server 2008 r2.
What exactly is this services used for
Managing Integration Services
Microsoft SQL Server Integration Services includes the Integration
Services service, a Windows service for managing Integration Services
packages. The Integration Services service is available only in SQL
Server Management Studio.
Running the Integration Services service provides the following
management capabilities:
Starting remote and locally stored packages
Stopping remote and locally running packages
Monitoring remote and locally running packages
Importing and exporting packages
Managing package storage
Customizing storage folders
Stopping running packages when the service is stopped
Viewing the Windows Event log
Connecting to multiple Integration Services servers
The Integration Services service is installed when you install the
Integration Services component of SQL Server. By default, the
Integration Services service is started and the startup type of the
service is set to automatic. The service must be running to monitor
the packages that are stored in the SSIS Package Store. The SSIS
Package Store can be either the msdb database in an instance of SQL
Server or the designated folders in the file system.
The Integration Services service is not required if you only want to
design and execute Integration Services packages. However, the service
is required to list and monitor packages using SQL Server Management
Studio.
What login should I be using for this service and what rights/privileges
Managing the Integration Services Service
By default, the Integration Services service runs in the context of
the NETWORK SERVICE account.
I have not found a simplified list of what is required for the service to run correctly but this article describes how to connect to a remote SSIS service.
I'll keep browsing MSDN articles