(video) "Fast Site Creation" 4.1 Why software is different from making a car, why software is bound to have bugs-build devops integration

This article is the 9th of the fast-track creation series, and if you have not read the previous content, it is recommended that you click on the chapters in the following directory to read the other content before returning to this article. To access this catalogue, please click on: http://anb.io/blog/tag/wordpress-on-azure/

1. Website management platform WordPress and cloud computing Platform Azure Introduction (6-minute video)
2.1 Creating websites and Web site operations on Azure (13-minute video)
2.2 Domain binding operations and Azure load Balancing mechanism (12-minute video)
2.3 WordPress initialization and website management features (11-minute video)
3.1 WordPress Data import (12-minute video)
3.2 WordPress Multi-site support and Azure online Code Editor (14-minute video)
3.3 WordPress Multi-language support multisite Language switcher (15-minute video)
3.4 WordPress Theme Installation and configuration to beautify your website (15-minute video)
4.1 Visual Studio Online (VSO) development platform (11-minute video)
4.2 Build a DevOps environment with Visual Studio Online and Azure (13-minute video)

After the first three parts of the content (video), I believe that you can use the cloud platform and WordPress to create a blog site has a more complete understanding. In part fourth, I'll show developers any use of visual Studio online and Azure to build a complete online development platform that allows you to complete project management, requirements management, task management, code management, automated testing and deployment without any local environment. , such a system is called DevOps Integration in the ALM (Application Lifecycle Management) system.

Please read this article in conjunction with the video

Why do we need to develop an operational integration (DEVOPS) system?

The more people engage in software development, the more the consensus is that software development cannot rely on pre-planned and complete requirements to ensure quality and customer satisfaction. This is the biggest difference between software development and traditional manufacturing. In fact, even in the software industry, there are still a lot of people do not recognize this, we feel that the developers have been trained, and we have experienced demand analysts and project managers for the project, there is no reason not to succeed. are manufacturing products, why can't manufacturing software, like cars and televisions, rely on detailed production plans to deliver on a clear timetable?

In fact, everyone in this is ignoring the most basic fact. Industrial products such as Auto/TV are designed and repeatedly produced; in the design of the car/TV, we are still unable to fully foresee all the details of the design process and the delivery time, because it is an "exploration" process, Designers and engineers need to rely on their own experience and knowledge to create a non-existent product, and as far as possible to predict, to ensure that the delivery of products can meet the requirements of users. Once in the production process, all parts of such products, assembly methods will not change, so that we can quickly repeat the production. The SOFTWARE PRODUCT is always in a similar car/TV design process, and there is no duplicate production process (perhaps, but you only need to copy/paste to complete). Therefore, in accordance with the delivery of products such as automobiles are expected to deliver the software PRODUCT is completely wrong, does not conform to the actual; it is as if everyone is asking everyone to design a unique car for each individual, and to ensure that it is delivered on time.

Another reason for this misunderstanding is our education, where the so-called software engineering in the university teaches design-dev-test-delivery, which is similar to the way the pipeline (called Waterfall mode) works in a software project. Let's have this misunderstanding from the moment we leave school.

Since we have no way to predict the delivery time of the software, we cannot predict whether it will meet the needs of the user before delivery, as if we do not need to do the software. Due to on-time delivery, meeting demand is the value of software existence. We must produce such a value, or else everyone will have no food. What to do? Agile, iterative, trial-and-error, these answers are all right, just out of different people's experiences and perceptions of the problem.

Shows the different effects on the likelihood of success of complex projects when using waterfall mode and agile development patterns.

In fact, we just need to remember a word: quick!

• Rapid completion of development, testing, payment to the user to use;
• Quickly get user feedback and adjust the software functionality in the next release;
• Then, quickly complete the development, testing, pay the user to use;

Shows the iterative relationship between development/operations, only to speed up this iteration speed, to let our software products as soon as possible close to the needs of users.

That's why we need to develop operations integration (DEVOPS), because only by opening up the development system and operations, can we get the developers to get the feedback directly and accurately, which may be the monitoring data provided by the operations system, or the problem of direct customer feedback, Or on other social networks/forums, any information that can help a developer to judge a user's needs is something that needs feedback.

From this point of view: In fact, we should call it development operations integration, but it may be too difficult to do this, we will talk about the development of operational integration.

Visual Studio Online development platform

VSO, formerly known as Tfspreview.com, is the online team Foundation Server (TFS) version, operated by Microsoft, to provide the cloud with development management capabilities. VSO mainly includes the following features:

• Work Item Management: Work items represent a variety of requirements, tasks, tests, feedback, bugs, and deployments that need to be tracked during the development process. Can be understood as a work order system. Each work item has a separate type that represents one of the above work items, accessed and managed through a query (list).
• Process Management: Each work item is equipped with a certain workflow, which is controlled by the state and transformation of the work item, and with certain rights management, can help us to organize these work flow. Agile, scrum and CMMI are available in three different templates according to the working model of different teams.
• Source Control: provides code storage, change tracking, comparison, branch merging, and IDE integration capabilities. supports two different modes of centralized (CVCS,TFSVC) and distributed (Dvcs,git) management. Support for code review is also provided.
• Test Management: supports test plans, test cases, test execution, automated testing, and stress test support.
• Build Management: provides automated code compilation, automated testing, packaging, and deployment capabilities.
• Deployment Management: provides orchestration, thread and audit capabilities for the target environment, while supporting the ability to deploy to the cloud and on-premises environments.
• third-party system integration: provides the ability to interact with third-party systems through rest APIs and service hooks.
• Monitoring and Analysis: provides application performance, error collection, and user behavior analysis capabilities that have been transferred to Azure.

As you can see, these features basically cover all the features we need in the development process. In addition, VSO provides a good integration of mainstream Ides, such as Visual Studio and Eclipse.

Cross-platform support

The integration of Visual Studio is certainly beyond doubt, so I'll only list the Java project support for Eclipse:

As you can see, using the Team Explorer Everywhere (TEE) (click to download) plugin, you can use Eclipse to connect to VSO projects, use git code libraries, access work items, or configure automated compilation and packaging in the cloud.

We can refer to this video for specific operation:
http://channel9.msdn.com/Events/Visual-Studio/Connect-event-2014/219

For iOS developers using Mac, you can also use the Git integration provided in Xcode to work with VSO for source code control, see here:
Https://www.visualstudio.com/en-us/get-started/share-your-xcode-projects-vs.aspx

I will also record some videos on these functions separately for everyone to learn.

Agile Development Support

Agile development is an irreversible trend in the software development industry, and in VSO, it also provides good support for agile development. For example, the following Kanban and sprint Leukoplakia support.

This is the kanban I used to plan this blog content and background development.

This is the cumulative flow graph of previous work items tracked out

This is the sprint whiteboard for the current iteration of this blog (you can see that this blog is currently in progress)

Of course, these are just a few of the icebergs in VSO for Agile Development Support, which I'll cover in more detail in an article specifically on Alm.

In this blog video, I showed you how to push the backend code of a WordPress site in Azure into VSO's git code base and correlate it with related tasks. This allows us to use the online IDE in Azure as the development environment in the development process, using VSO as the development platform.

You can see that the changes I've made in the past 2 weeks have been recorded in VSO's code base history:

You can see the changes I made when configuring multi-site support, associating with tasks, and adding code review comments directly:

Free cloud-based development platform

Hopefully this article will help you get a preliminary idea of visual Studio online, but the best way to do this is to register an account now. For independent developers and development teams of less than 5 people, you can use all of the features that VSO provides for free, with no restrictions on the number of projects, the amount of code, or the number of work items, and if you want some project-related members to see the progress of your team, you can add them as stakeholder accounts , there is no limit to the number of such accounts, you can add multiple, as long as they do not access the code base.

Click to start registering http://www.visualstudio.com

In the next section (4.2), I'll show you how to integrate VSO's content with your local development environment, although we can do all the development work in the cloud, but if you like using visual Studio, sublime,notepad++ or any other editor/ide, a local environment is still useful.

Please pay attention to this blog subscription number Anb-io. Push content Weekly, have the technology also has the life, with you to do a have the sentiment program ape.

(video) "Fast Site Creation" 4.1 Why software is different from making a car, why software is bound to have bugs-build devops integration