Lab: Application Lifecycle Management (ALM) Across Heterogeneous Platforms (Java/.NET)

Transcription

1 Lab: Application Lifecycle Management (ALM) Across Heterogeneous Platforms (Java/.NET) Published: March 2010 Abstract This Lab showcases how software developers using different languages and tools can work together using a single Application Lifecycle Management (AML) system with the aid of the Teamprise Plug-in for Eclipse. 1

2 Table of Contents Lab: Application Lifecycle Management (ALM) Across Heterogeneous Platforms (Java/.NET)... 1 Abstract... 1 Introduction... 3 Lab overview... 3 Lab Scenarios... 5 Lab Products and Solutions... 6 Eclipse IDE... 6 Microsoft Team Foundation Server Teamprise Client (will become Microsoft Visual Studio Team Explorer 2010)... 6 Lab Execution... 7 Scenario #1: Connecting Eclipse to TFS with the Teamprise Plug-in and getting the project assets to your working folder... 7 Scenario #2: Application Lifecycle Management with Eclipse Using the Teamprise Plug-in11 Scenario #3: Running a Build on the TFS Server via the Teamprise Plug-in for Eclipse Conclusions The Interop Vendor Alliance

3 Introduction There are projects that require the use of multiple technologies such as.net and Java. One of the challenges in these environments is to provide a unified infrastructure for Application Lifecycle Management (AML): source code management, bug tracking, reporting, work item management, and build process. The ability to use a single system to manage all these aspects is critical for a project s success. Lab overview This Lab showcases how software developers using different languages and tools, such as Java with Eclipse and.net with Visual Studio, can work using a single Application Lifecycle Management (AML) system to manage source code, track bugs and work items, and build of heterogeneous components. The benefit of using a single repository is that there is a controlled, unified way to track work items, issues, and tests between development teams working on different platforms or languages. For example, let s pretend that there is a company developing a.net application that is required to access a Java service. Microsoft Team Foundation Server (TFS) can be used to define all of the requirements of the project, such as specifications of the interfaces and protocols for all of the.net and Java components in one single location making it easier for the developers ensure a consistent implementation for the project. When developers switch from one language/tool to another they will recognize the same concepts, while having the features completely embedded into their Integrated Development Environment (IDE). Developers working on the Java or the.net components in a project can rely upon having the same functions and support from TFS. 3

4 Figure 1: overview of the lab Application Lifecycle Management (ALM) across heterogeneous platforms (Java/.NET) From a project management perspective, the project lead can have a uniform view across all projects whether they build with one technology or another. For example, this technology can greatly enhance a cross-platform interoperability project as Apache Stonehenge where the goal is to develop applications with multiple underlying platform technologies by using currently defined W3C and OASIS standard protocols. Some of the ways the Teamprise Plug-in for Eclipse could help this sort of project include: Project managers can monitor tasks across different development teams from multiple platforms in one location assuring consistent and accurate information about the project. Development Teams and Project Managers can quickly respond to bugs and red flags across platform developer teams in a single location that provides the same consistent experience for all of the developers regardless of platform. Developers can run builds for their application that combines components created in different languages such as.net and Java. 4

5 Lab Scenarios The following scenarios are using code from the Apache Stonehenge project, to illustrate a really world scenario: Connecting Eclipse to TFS with the Teamprise Plug-in: o This scenario shows how to get ready with the project assets. Application Lifecycle Management with Eclipse Using the Teamprise Plug-in o This scenario follows a basic step by step process that allows developers using Eclipse to manage source code and work items. Running a Build on the Microsoft Team Foundation Server (TFS) from Teamprise Plug-in for Eclipse o This scenario showcases a step by step process that allows developers to log-on to the TFS server and then create and run a build process to create a single application with different components in different languages. Note: The lab does not include the details of the scenario where a.net developer uses Visual Studio with Team Foundation Server, as the focus is to demonstrate interoperability between heterogeneous features. 5

6 Lab Products and Solutions Eclipse IDE Eclipse is an integrated development environment (IDE) with an extensible plug-in system. It can be used to develop applications in Java and, by means of the various plug-ins many other languages. For this lab we use the Eclipse IDE for Java EE Developers. More information at Microsoft Team Foundation Server 2008 Microsoft Visual Studio Team System 2008 Team Foundation Server is a team collaboration platform that combines team portal, version control, work-item tracking, build management, process guidance, and business intelligence into a unified server. More information at Teamprise Client (will become Microsoft Visual Studio Team Explorer 2010) Microsoft has acquired the Teamprise-related technology assets of SourceGear, and is working on incorporating the Teamprise-based technology into the Visual Studio product line. This lab was design the current release of the Teamprise plug-in for Eclipse, which allows a developer to perform source control and work item tracking operations from within the Eclipse IDE using Microsoft Team Foundation Server (TFS). Microsoft has released a beta version of the Microsoft Visual Studio Team Explorer 2010 here, which includes the new Team Foundation Server Plug-in for Eclipse as well as the Team Foundation Server Cross Platform Command Line Client. It works on Windows, Mac, Linux, and multiple flavors of UNIX, providing access to the same source control, work item tracking, build automation, and reporting features. More details about the transition: 6

7 Lab Execution Scenario #1: Connecting Eclipse to TFS with the Teamprise Plug-in and getting the project assets to your working folder 1. Open Eclipse and Select Import, and pick Teamprise as the source: 2. Provide TFS server login information, and select a Workspace: = 7

8 3. Select the project tree you want to add to your local workspace: 4. Now you need to add the project to your Teamprise explorer. Click the Add Existing Team Project icon in the upper left panel as shown below. 8

9 5. Select the desired Team Project and then click Finish. 6. From this view, you have to the TFS server Work Items, Bug reports, Documents, Reports and Builds 9

10 7. Switch to the Java view to access your source code. 10

11 Scenario #2: Application Lifecycle Management with Eclipse Using the Teamprise Plug-in 1. Check the work items that have been assigned: 2. There s a new work item: 11

12 3. Get the latest version of the source code from TFS 4. Now open the source file, and navigate to the code to edit. 5. When edits are make, time to Check-in. The corresponding work item is assigned at check-in time: 12

13 Scenario #3: Running a Build on the TFS Server via the Teamprise Plugin for Eclipse Note: The steps in this scenario assume that you have already completed the steps in covered in #2. Your screen should look something like the example above. 1. Right-click on the Builds folder and select Mange Build Agents. This will allow you to create a build process. 13

14 2. For the purpose of this lab, we have already created a build agent. Select testbuildagent1 and click Edit to review the build agent. 3. Change Working directory as needed. Click OK to continue. 14

15 4. Open the Builds folder. Right-click on testservice and select Edit Build Definition. 5. Click on Project File. 15

16 6. Verify that you have the proper version control folder. Click Build Defaults. 7. Verify that the builds will be staged to the correct share and then click OK. 16

17 8. Right-click on the Builds folder and select Queue New Build. 9. Verify that you have the correct drop folder for the build and then click Queue. 17

18 10. Depending upon the size of the application, the build process may take several minutes to an hour to complete. 11. When completed, the in-process icon will change into a checkmark as seen below. 12. Click on the build testservice for information about the build. 18

19 13. Developers can drill down into as much information about the build as desired. The build will automatically be dropped in your pre-selected location and available for use. 19

20 Conclusions Based on a real use case scenario, this lab shows how software developers using different languages and tools can work using a single Application Lifecycle Management (AML) system to manage source code, track bugs and work items, and build management of heterogeneous components. The lab highlighted how the Teamprise Plug-in enables interoperability between Microsoft Team Foundation Server, Visual Studio and Eclipse. Developers working with Java or.net can rely upon the same access and features. 20

21 The Interop Vendor Alliance The Interop Vendor Alliance is an industry group working to identify and share opportunities to better connect people, data, and diverse systems through better interoperability with Microsoft systems and to jointly market the interoperability solutions of its members. The organization serves as a collaborative forum for developing and sharing common technology models, facilitating scenario-based testing of multivendor solutions, and communicating additional best practices to customers and partners. Since its formation in 2006, alliance membership has more than doubled as the IVA has developed multiple interoperability labs, including System Management, Centralized Directory, Federated Identity, Content Management, and Open XML. You can learn more by visiting 21

22 This document is provided as-is. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. You may modify this document for your internal, reference purposes. Distributed under Creative Commons Attribution-Noncommercial-No Derivative Works