I am trying to setup CI pipeline for .net core app with VSTS.
I am confused with Copy Files Over SSH step. Server is defined not by deployment group but by endpoint host.
How should I copy my deployment artifacts to ALL servers in deployment group with this tool?
Actually, same applies to "SSH" - it also get executed only on host from Endpoint definition.
Any ideas?
If you're using deployment groups, you don't need to SSH anything to them. The build artifacts will be automatically downloaded to them, since the build/release agent is already running on them and talking directly to VSTS.
Related
I have deployed my application running on my local server # http://localhost:8048/myservice?day=xx&month=yy&year=zzzz , it works succesfully on my local machine, in that it downloads a file from the http site. However when I deploy to Mule Management console . I understand that the default port is 8585. When I change the URL to MMC & give the default port with the same path, it does not download the file . Am I missingsomething
The MMC is a utility for managing and monitoring Mule Standalone Runtimes.
One of its functions is to deploy apps to a Runtime. You are not actually deploying to the MMC.
Does this help clarify the situation or do you want any further help on want The MMC is used for and how to do it?
Please check the logs inside MMC.It stores the logfiles date wise.See if your application has been deployed in MMC successfully and if yes then do the following things:
1)If you are using any path to download the file then cross check the path details.You can put a logger to crosscheck that.
2)Put a logger before the business logic and after the business logic and follow what it is logging in the log file.
3)In case your server is Linux then check the path separator pattern
MMC is a Mule Management Console which is used (provides provision) to deploy, undeploy, manage, monitor application and server both. From the statement you mentioned in your query it seems you are trying to deploy the app in the MMC - MMC is not a server its a console where you can register your ESB Runtimes -or- API Gateways (on-Prem) servers so that you can deploy the applications to the server/runtimes (which will go to the runtimes location $MULE_HOME/apps).
Please check if you have registered the server under MMC's Server tab - if not then you have to do this first and then it will allow you to perform application deployment using the MMC's APplication tab where you can upload your deployment archive/artifacts/build to the mmc repo and then you can deploy through the deployment options by selecting your server (which you have registered).
If I am missing something from your statement then please clarify more and will try to help you out here.
I installed multiple rabbitmq Services on our dev environment and enabled the management plugin and gave them different ports. This works fine, now I installed 3 rabbit MQ nodes on another machine and installed the management plugin. Of course I adjusted the configs and gave the management tools different ports. Unfortunately I can only access the management plugin from rabbitmq 1, 2 and 3 are not working.
I checked and see that some folders are missing in the setup.
C:\Users\myuser\AppData\Roaming\RabbitMQ1\db
inside of this folder I am missing the plugins folder which I have in the rabbitmq1 setup. I tried to cheat and copy the folders and rename them, but as soon as I start the service it recognizes this and delete the folder.
Re-installing the management plugin does not work, whenever I try to install I get the message that I already have it.
Any idea?
I finally found the issue. When you create the rabbit-mq and you don't have a config in the AppData\Roaming/YourRabbitInstance than there will be no config parameter created in the registry. Meaning your config will never be picked up, whatever details you provide. I have added the config parameter to the registry and the queue immediately started listing on the ports defined in the cfg.
-config "C:\\Users\\myuser\\AppData\\Roaming\\myrabbit\\myrabbit"
I have configured web application on server1. In configuration I choosed my cluster(server1 and server2) as target servers. What I want to learn is Do also need to configure a deployment on server2? There is no war file in server2 and I am a little curious about how this application will run also on server2.
Deployments process can be done in three ways...
1.Stage
2.Nostage
3.ExtenalStage
This is an explanation of the staging modes in WebLogic:
Stage mode—
The Administration Server copies the archive files from their source location to a location on each of the targeted Managed Servers that deploy the archive. For example, if you deploy a J2EE Application to three servers in a cluster, the Administration Server copies the application archive files to each of the three servers. Each server then deploys the J2EE Application using its local copy of the archive files.
Stage mode is the default mode when deploying to more than one WebLogic Server instance.
Nostage mode—
The Administration Server does not copy the archive files from their source location. Instead, each targeted server must access the archive files from a single source directory for deployment. For example, if you deploy a J2EE Application to three servers in a cluster, each server must be able to access the same application archive files (from a shared or network-mounted directory) to deploy the application.
Nostage mode is the default mode when deploying only to the Administration Server (for example, in a single-server domain). You can also select nostage mode if you run a cluster of server instances on the same machine.
External_stage mode—
External_stage mode is similar to stage mode, in that the deployment files must reside locally to each targeted server. However, the Administration Server does not automatically copy the deployment files to targeted servers in external_stage mode; instead, you must manually copy the files, or use a third-party application to copy the files for you.
Hope it helps you.
No, weblogic will handle deployment to both managed servers automatically.
Multiple TFS 2010 MSBuilds are not triggering Web Deploy to publish the web application to the IIS website.
This is for multiple different software products, multiple different build configurations, 2 different build agents (on 2 different servers), multiple IIS web site instances on multiple different servers.
3 different continuous deployment setups were previously working.
So hopefully this rules out miss-configuration of the build/build servers/hosting servers/web deploy and IIS.
According to the network manager nothing has changed on the network (all servers are local), and port 8172 is not blocked by any security configurations.
All builds succeed, web deploy fails silently (no error, nothing in the logs). It appears that web deploy is no longer being triggered.
Are there any other ports that are used here?
What else could be blocking the communication between MSBuild and Web Deploy?
Would you expect it to fail silently (nothing in the logs or passed back to MSBuild)?
UPDATE
This is a similar question How to determine if MSBUILD Arguments were executed for TFS Build Definition
Assuming you are using vs2012, on your build server make sure the following two folders exist: Web & WebApplications in
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0
If these dont exist then need to be copied from a machine your do development on. This worked for me, and solved all of my problems with the Deployment of projects.
I have an application that needs to be deployed to two different servers (environments).
I have two environments on two separate servers, server1 and server2.
Both servers have different IIS Manager user accounts and passwords configured.
The builds however all happen on server1 and it appears that no matter what settings I pass via the build definition, everything gets deployed to server 1.
I can publish to server2 manually from the Publish command in VS2010 but this needs to be automated in TFS.
This used to work fine but then started happening a couple of weeks ago.
How can I correct this problem?
In the end, although I followed the IIS generated settings file, I had to set the MSDeployPublishMethod to WMSVC (it was set to MSDeploy). I can't tell you why this works and the other doesn't but this is how I solved it. If anyone has any details on where one can find out more about the various Web Deploy settings please advise!