Looking for step-by-step guide or best practices on how to migrate from Octopus deploy to Azure pipeline. Similar to the documentation Microsoft has on Travis migration to Azure pipelines.
Regarding this issue,as far as I know, there is no clear document to introduce the migration from Octopus to azure pipeline. The existing documents are all about two technologies work together as part of a pipeline:Octopus Integration with Azure DevOps. The reason why the two need to work together is because they have their own advantages, you can refer to this case about this.
If you decide to deprecate Octopus and only use azure devops,then I think you can first understand how to use pipeline to deploy through the official documentation. Here are some document you can refer to :
Azure Pipelines documentation
Release pipelines
Deploy applications using Azure DevOps
Related
I am working on a project and developing with react. I need somewhere to keep my datas. Where do you suggest? I use json-server while I'm following my course. But I'm open for any suggestion. Ofcourse it would be better if it is free at least while working on prototype.
What about mysql, nosql or postgresql? Probably I choose postgre because of it's support which comes with it's popularity
I have used Heroku to deploy production applications and hobby projects. It has a free tier, and it is fast and easy to setup. Databases are supported via addons (including Postgres), some of which have free tiers. Heroku recognizes many applications automatically, but if are using create-react-app, you need to use a buildpack for the deployment.
Need ideas for TFS - Jenkins integration.
Using TFS for Sql server database - Database objects such as table,views, SP & functions. Got 3 environments.
Now planning to implement Jenkins continuous integration.
Can someone provide an idea to implement jenkins with TFS for SQL DB objects for 3 environment(DEV/QA/PROD).
According to your tag, seems you are still stay with the old XAML build definition on TFS2013.
Your question is too board. If you are moving to the new web-based vNext system. Either upgrade your TFS version or directly use VSTS. It' not hard to achieve the TFS/VSTS and Jenkins Integration. Details please refer below two blogs:
TFS and Jenkins Integration
Visual Studio Team Services Integration with Jenkins
Add a section:
Team Services integration with Jenkins allows using both CI systems
with traceability through a single DevOps platform. This post
summarizes Team Services’ initial capabilities of integrating with
Jenkins. Supported scenarios include:
Using Jenkins for continuous integration of Team Services Git repositories
Using Jenkins to validate Team Services pull requests
Mixing Jenkins and Team Services to perform builds and releases
Providing traceability between Jenkins and Team Services; linking builds, pull requests, commits, and stories
For 3 environment(DEV/QA/PROD), you could use TFS Release Management to do the Continuous Integration and Delivery.
I assume the source projects are in TFS and you want to do build in Jenkins.
You just need to add TFS-plugin to Jenkins, then you can specify TFS source in job configuration.
jenkinsci/tfs-plugin
I've created my first application using Openshift Tech. It's a Java Web Application running on a JBoss at Openshift and uses MySQL 5.5 as its database. And I have to deploy by it using the war file (I don't know how to do it the normal way).
So anyone can tell me: Should I create a local database or use online database? And is there another way to deploy my Java app not using the war file?
I would suggest that you check out the OpenShift Developer Center (https://developers.openshift.com), specifically this link (https://developers.openshift.com/en/jbossas-overview.html) about using jboss. Make sure you read all of the sections, specifically the Deployment Options, and the Datasources links. If you are interested in just being able to do a "git push" to deploy your code, you should create a new jboss application on OpenShift, and do a "git clone" of the code and check out how it's setup, it is using the Maven project structure, which is pretty common.
We have this issue.
We want to automate the deployment of our Continuous Delivery Build Server Tool chain using a Configuration Management tool such us Puppet, Chef or Ansible.
More precisely we have a bunch of tools (e.g. nuget, NUnit, MSBuild etc) that we use in our Continuous Delivery infrastructure. These tools are deployed to Several Build Servers. Maintaining the configuration of them is time consuming and error prone (i.e. different configuration in different Server resulting is error when building our solution using the Continuous Delivery tools).
We want to automate the maintenance of their configurations and we were thinking to use the Configuration Management tools such us Puppet, Chef or Ansible.
The question is: Are these the right tools for achieving the Configuration Management of our Build Server toolchain?
Anyone having experienced the same issue and how do you solve it?
Thanks in Advance
Alberto
Yes. All of these 3 can help you with that. Which one is better is highly opinion-based.
Yes, convergent configuration management tools such as the ones you listed are a widely used and powerful way to manage servers. The question is still very vague so that's about the best I can say.
We want to have scalable Reporting services. And we need to install Custom Rendering Extensions on this scalable Reporting Services. This is the main requirement for us. SQL Azure Reporting doesn't suite the requirements, because it is impossible to extend this service with custom rendering extension. We had an idea to install Reporting Services on each instance separated from SQL Azure and Azure Reporting, but Rendering Extensibility is not available in free editions of SQL Server and it costs too much to use paid edition. The database of these reporting services instances will be stored in SQL Azure and we will be able to leverage scalable Reporting Services tool with the required rendering extension. The problem is price, complexity and no benefits from SQL Azure Reporting. So, we got stuck with Microsoft clouds. And don't see any reasonable solution with Microsoft clouds.
So we considered Reporting Services on EC2 as they have special cloud license. And we are not quite sure whether it is possible to achieve what we need or not.
We've found that it's possible to install SQL Server2008R2 on EC2 so that the data of the database will be stored in EBS which is available to all the instances. So we have scalable Reporting Services in that case.
The question is lying in the Amazon Virtual Images:
We suppose that we need to install predefined configuration with Windows OS and SQL Server 2008R2 and we wonder if it (1) includes Reporting Services, (2)is it possible to install some more software on this predefined virtual machine (rendering extension), (3)is it possible to organize such scalable Reporting Services with Custom Rendering extensions and to leverage load balancing and etc.?
You don't have to use the AWS provided SQL Server 2008 R2 AMI if you don't want to.
If you bring your own licenses, you could go with a base EC2 install, and then install whatever software you want over the top of it.
ie - install the Windows AMI, and then run the SQL Server installation of your choice. The second step then is to install any additional extensions you require.
I would also recommend that once you complete the installation that you create an AMI of it so that you can repeat the installation at a later date.