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
Related
We normally use on-premises Azure DevOps Server to maange our build pipelines, using YML files. We have build agents running on one or more build servers.
A specific piece of R&D would be made far easier if we could install VS and a build-agent on a standalone box which is not linked to the Azure DevOps server, and manually 'run an YML build' against the build agent locally.
We don't have access to DevOps server from this machine and the alternative is rescripting an alternative to our YML in Powerscript or similar.
Is there any realistic way to do this?
Is it possible to manually run a build on a local Azure build agent without a DevOps server?
I am afraid there is no such way to manually run a build on a local Azure build agent without a DevOps server.
That's because azure devops services/server is equivalent to an interpreter and trigger. Agent itself is not a program that can be executed independently like MSBuild.exe, it does not have the ability to parse YAML grammar, it can only execute the parsed command passed by the server.
I totally understand your needs and approve of it, so I recommend you add your request for this feature on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions：
I have an Octopus Deployment Project in which I am doing some changes in settings files like appsettings.json. So in different steps lots of changes been done. So at the end I am deploying it into Azure. But my question is, is there is any way to download a package just before pushing into Azure.
I know there are option to download package from Library. But those are not processed. So I need the altered package to be download.
How are you deploying to Azure? Is it an Azure Web App? In a lot of steps, you can use custom deployment scripts and variable substitution to update the package prior to its installation.
For example, in the Deploy an Azure Web App step, you can click on Configure Features and enable Custom Deployment Scripts and JSON Configuration Variables.
I need to use visual studio services (on cloud) to automate integration and release process.
I have 3 environments dev, test and deployment. I am planning to use only one branch the Dev that promotes the changes to next Env (TEST) and then to release.
Question 1:
Can I do it using one branch (Main Dev) or i need to create separate branch for each one? and how?
As far as i know that when using TFS server on premise, we should install release manager on the same machine and deployment agents on the different environments.
Question 2:
How can I automate release management using visual studio cloud services, taking into consideration that test and production environment don't use Azure services, they just use IIS to host our websites.
For the first question, the answer is YES and usually there should be only one branch for one release. The release/build that been deployed to the three environments in the release should be the same. Use the build from different branches in three environments does not make sense.
For the second question, you can use web deploy or Adding FTP Publishing to a Web Site in IIS 7 and then deploy via FTP.
You start using Release Management by creating a release definition in the RELEASE hub of your team project. A release definition specifies What to deploy - the set of artifacts that constitutes a new release, and How to deploy - the series of automation tasks that should be run in each environment. Each environment is simply a named logical entity that represents a deployment target for your release.
It seems you want to change project between environment in one release definition, which is not supported. A typical use case for Release Management:
You can get more information of Release Management at website https://msdn.microsoft.com/en-us/library/vs/alm/release/overview
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.
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