I have the following configuration in Continuous Integration CI
Build runs successfully but the publish part is not working. My publish profile using a web deploy to deploy on server directly. Web deploy working fine if i run it from the normal publish.
Any suggestion on solving this issue?
I had the same problem, the reason of my-- the PublishUrl isn't used. Workaroud for me change the webdeploy to xcopy.
Related
I have an devops project assignment that I am required to create a maven project and also create a CI/CD pipeline for it. I am quiet newbie in devops and struggling to understand some concepts.
I created a maven project and pushed it into bitbucket. By the way, I have 3 main branches which are master, test and development that I need to deploy them prod, qa and dev environments, respectively. Via Jenkins, I successfully created build automation.
However, I could not deploy the project because I am confused. Can I also deploy my project with Jenkins? Or do I need a something like Virtualbox to deploy? Also do I have to use Docker to deploy? I searched for web but could not make it clear.
Could you please help me understand the deployment process in this project?
Thanks in advance.
Deployment processes are depends on your infrastructure. What do you use?
There are tons of deployment strategies according to business/development models. You can deploy your projects with Jenkins or any CI/CD tools that you chose. It doesn't matter at the end.
Here it's a good deployment strategies reading by Google.
https://cloud.google.com/solutions/application-deployment-and-testing-strategies
I am trying to get an Azure App Service to recognize my Web Job - meaning to show it in the portal under "Web Jobs" in the App Service. And to also run it on the schedule defined with a TimerTrigger attribute.
It is a .NET Core 2.2 Console Application with multiple web job classes in it. The App Service it runs within is a separate project and web site. I am able to publish it from Visual Studio and it shows as it should under Web Jobs in the Web App. But if I delete it and try the publish from Octopus to the same place WITHOUT doing the VS 2017 publish first, it won't show up.
My issue is that in a new environment, the Web Job does not get created when I use Octopus to deploy the Web Job files as described here:
http://blog.amitapple.com/post/74215124623/deploy-azure-webjobs
by setting the physical path in my Octopus package deployment:
App_Data\jobs\continuous\myjob
This is the same path as when I publish from Visual Studio 2017.
Related to this question, but there seems to be a step missing since the files are in the right place, but the web job does not appear in the portal.
How to deploy azure webjob using Octopus
Is there some additional ssetup or registration step for the Web Job to run or should the App Service just recognize the web job is there when the files appear in the correct place? Restarting the app service does not help.
Since you have a web app along with a web job, I would follow the steps outlined at https://octopus.com/docs/deployment-examples/azure-deployments/deploying-a-package-to-an-azure-web-app/deploying-web-jobs. You can build your project using .nuspec to get your .npkg and push/upload the package to Octopus.
Hope that helps.
I am looking to run some automated RestSharp API tests in Continuous integration.
Right now, the application API is running in it's own project, which is set as a Startup Project. The Web App is running in a separate project. And when they are both run manually from Visual Studio, the app's UI can be manually tested against the locally running API (That's just for reference, I only need the API project to run for my tests to work).
So right now, to run my automated API tests as I script them, I start the API project to get the API up and running locally, then open a new window of Visual Studio, and run my MSTests from there.
My question is, how do I get the API project up and running automatically, so the tests can be run against the API? Can I start tests, while the API project is actively running in Visual Studio?
Mainly, how can I run these API tests in Continuous Integration, if the API needs to be started up in a separate VS window every time?
Sorry for the fairly broad question, I am a test automation engineer, and not an API developer. A pointer in the right direction would be great.
You can deploy the Web API to IIS (or IIS Express). In that way, it would be running in the background rather than launched from Visual Studio. The CI tool would then update the deployment after it creates a new build, but before it runs the tests. I would start with the documentation for whatever CI/CD system you are using, but assuming you're using TFS, here is a reasonable starting point: https://www.visualstudio.com/en-us/docs/build/apps/. There are links from that page for deployment and CI.
I am using
msbuild D:\SVN\QM\QMsln\QM.sln /p:DeployOnBuild=true;PublishProfile=Prof.pubxml
where publish prof Prof.pubxml deploys the web app in my local machine.
It works fine. But now I want to deploy it on remote server. I created a ftp server in my remote machine. And while I tried publishing using VS2012. It throws an error
FTP Passive mode is not available
I googled the issue and inserted
<FtpPassiveMode>True</FtpPassiveMode>
in the Prof.pubxml. But still the problem persists.
Also If I use msbuild it says
This specific web publishing is not yet supported on msbuild command line.
Any idea?
I would like to be able to select the build agent to use to deploy my web application. When the code is being built for testing I would like for it to use a certain build agent and deploy to our test server and when the code is being built for production I would like for it to use another build agent and deploy it to our production server, Automatically! Does anyone have experience in doing this?
Please help.
This has been resolved by tweeking my ports and using MSDeploy