Limited Time Offer!

For Less Than the Cost of a Starbucks Coffee, Access All DevOpsSchool Videos on YouTube Unlimitedly.
Master DevOps, SRE, DevSecOps Skills!

Enroll Now

Bug Tracking Tool in TFS

geethusri26 created the topic: Bug Tracking Tool in TFS
Hi,

Can anyone please share your ideas and experiences using Bug tracking tool in TFS.

We are in process of migrating from Quality center to TFS so I need to know the pros/cons of using TFS bug tracking tool.

If anyone has any documentation please share it.

rajeshkumar replied the topic: Re:Bug Tracking Tool in TFS
TFS is a real power house when it comes to tracking issues, impediments, etc. in terms of a Team Project solution, but using the process templates that ship in the box you may not necessarily find all the features you are looking for, i.e. time management and tracking.

You can have a look on these links… msdn.microsoft.com/en-us/library/ms181268%28VS.80%29.aspx

www.scmgalaxy.com/component/content/arti…tracking-system.html
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Hudson CI for TFS projects?

pankaj2252369@gmail.com created the topic: Hudson CI for TFS projects?
Does any one had experience on HUDSON & TFS Integration?
more light would be helpful.

rajeshkumar replied the topic: Re: Hudson CI for TFS projects?
I have not done so but this might be helpful for you.

wiki.hudson-ci.org/display/HUDSON/Team+Foundation+Server+Plugin

if you are facing any specific issues, do share with me.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

Tagged :

Top 10 Continuous Integration Tools | List of Best CI Tools | scmGalaxy

continuous-integration-tools
Today we are present here with another interesting article which will help you to know about the best tools which are used for continuous integration in DevOps practices.
Continuous Integration has become a mainstream technique for software development. Which makes it mandatory to implement it in your software development lifecycle (SDLC). But implementation of CI required best selection of tools to achieve good results and there is still a confusion amongst beginners and even in vetrans of software industry while choosing the best tools. So keep reading, I have done some research and compile a list of CI tools which will definitely going to help you.
Before going further, let’s first see what is Continuous Integration?
Continuous Integration is a practice in DevOps software development process which improves the quality of the code. In this practice all the developers who are related and working on the project integrate there codes into a central repository frequently for several times in a day. After which automated build and automated tests run, which verify each integrations in the repository. The main objective of the continuous integration is to provide rapid feedback when any defect is found in the code base and correct it as soon as possible.
Now we know about continuous Integration but one question arises here, Why we do Continuous Integration?
So, Now let’s see the benefits of CI
  • Earlier finding & addressing of Bugs – By implementing continuous integration you can do frequent testings which helps to find bugs and error quickly before they ruin your whole efforts later.
  • Improve software quality – Early finding issues in the codes, developers can act on them early before they grow into larger problems later,  which ultimately improves the quality of the software.
  • Reduce the time it takes to validate – CI immensely reduce the waiting time to find out if your code’s going to work or not.
  • Release new software updates – Doing frequently and numbers of time automated build and test of codes helps teams to deliver the new updates to the user more often and faster.
So, these are the major benefits of CI. Now back to the point and purpose of this article, as I said earlier continuous intergation needs various tools to implement the process and choosing amongst the available tools for your purpose can be a daunting task, especially when you are going to select for the first time.
So, without further wasting any time let’s check out the top 10 Continuous integration tools.

1. Jenkins

jenkins
Jenkins is a Java written Continuous Integration tool, which was initiated as the fork of Hudson after conflict with oracle. It is a cross platform tool which allow GUI interface and console commands configuration. It available under MIT license which make it free to use. It supports rich plugins that integrates with virtually every existing software configuration management [SCM] or builds tool.

Features:- 

  • Open Source
  • Easy installation
  • Easy configuration
  • Rich plugin ecosystem
  • Extensibility
  • Distributed builds
  • Platform: Cross-platform

2. TeamCity

teamcity

 

TeamCity is one of the mature and wise java based continuous integration server which is belongs to JetBrains labs. It is available in free and paid license for users. It’s free version offers almost all the features but for up to 20 build configurations and 3 free Build Agents. Teamcity also supports different tools and frameworks and also it’s available with wide variety of plugins. It’s also support .Net features which makes it suitable for .Net projects.

Features :- 

  • Free and Paid
  • Gated Commits (prevents developers from breaking sources in a version control system by running the build remotely for local changes prior to commit)
  • Build Grid. Allows running multiple builds and tests under different platforms and environments simultaneously
  • Integrated code coverage, inspections and duplicates search
  • Integration with IDEs: Eclipse, IntelliJ IDEA, Visual Studio
  • Platforms supported: Java, .NET and Ruby
  • Supports cloud integration

3. Travis CI

travis ci

 

Travis CI is an open source continuous integration tool which is written in RUBY. It’s easily get sync with GitHub. It’s supports platforms like Linux, Mac or iOS and also supports many languages in which Node js, php, Xcode, python, java, are few of them. It also performs parallel test runs using their great APIs and command line tools.
  • Open source
  • Supports pull request and branch build flow
  • Parallel test runs
  • Easily synchronize with GitHub
  • Flexible plans for every size project
  • Platforms: Hosted
  • Supports Many Languages like Node js, php, Xcode, python and many more.

4. Microsoft Team Foundation Server

tfs
Team foundation server which is also abbreviated to TFS is a product of microsoft. It is a collaborative tool that consists the code repositories, continuous integration, and bug or task tracking. TFS perform in environment like Eclipse, Xcode, Visual Studio or in Git client. It’s also support languages like Python, C#, HTML, Java and various others too. It is available for free downloading but under trialware license.

  • Trial-ware
  • Supports many languages like Python, C#, HTML, Java and various others
  • Work in any environment like Visual Studio, Xcode, Eclipse, or any Git client
  • Extensible tool can work effectively for all shapes and sizes

5. Bamboo

bamboo

Bamboo is also one of the top continuous integration tool which is developed by Atlassian. This is available with free trial license. Bamboo is written in Java and it is easily works with JIRA & Bitbucket. It’s also allow you to import jenkins data to Bamboo easily. Bamboo also supports others tools like AWS, Amazon S3, Ant, Docker, codeDeploy, Maven, Git & SVN.

Features:- 

  • Paid and Free trial
  • Cross platform
  • Allow to Import data from Jenkins
  • Works with JIRA and Bitbucket
  • Works with others tools like CodeDeply, Ducker, Maven, Git, SVN, Mercurial, Ant, AWS, Amazon S3 buckets
  • Support many languages
  • Can run multiple builds parerally
  • customization of triggers and variables
  • Very fast and easy to use

6. UBuild-UDeploy-URelease

ubuild-udeploy-urelease
UBuild-UDeploy-URelease is also known as Urbancode deploy is a collaborative product of IBM. It provides continuous delivery, self-service, speedy feedback and progressive updates within the agile development and automates the applying deployments during a consistent manner. With urbancode You can systemise the changes you pushed on servers, tiers and components and also restore the applications.

Features:- 

  • Licensing plans
  • Hosted service
  • Server virtualization
  • Integrated with middle-ware
  • Clear visibility: what is deployed where and who changed what
  • Configuration and security differences across environments
  • Orchestration of changes across servers, tiers and components
  • Automated provisioning, updating, and de-provisioning of cloud environments
  • Automated, consistent deployments and rollbacks of applications

7. Go CD

go cd


Go CD
 is a free of charge (excluding commercial support) tool written in Java and Ruby which belongs to ThoughtWorks. This tool works on Linux, Windows and Mac Platforms. It’s also supports many languages but which makes it stand out among-st the tools is the Pipeline concept which makes build process easy and it eliminate the file-handle leak errors and fix the OOM on agents when parsing large xml test artifacts.

Features:- 

  • Availability: Free with paid support
  • Platform: Windows, Linux, Mac
  • Pipeline Concept
  • Parallel execution of the tasks
  • Support Many languages
  • Easily compare builds
  • Clearly visualize workflow
  • Promote trusted artifacts
  • Plugins availability
8. GitLab CI

gitlab ci

GitLab CI is an open source and also comes with commercial licesnse continuous integration tool. It belongs to Gitlab inc. which is written in Ruby and Go. This tool support platforms like Windows, OSX , Linux, Unix and various others which supports Go. Gitlab work with languages like Java, PHP, Ruby, C and with various others too.

Features:- 

  • Platform: Hosted
  • Availability: Free and paid with trial
  • Easy to learn
  • GitLab CI is fully integrated with GitLab
  • Docker support
  • Pipeline Concept
  • Supports multi-languages – Java, PHP, Ruby, C etc..
  • Parallel builds
  • Autoscaling
  • Build artifacts

9. CircleCI

circleci
CircleCI is also belongs to Gitlab Inc, free and paid with trail option which runs in any environment like cross platform mobile app too. Circle ci supports languages such as Python, Ruby/Rails, Node.js, PHP, Haskell, Skala and Java. This tool is scalable which minimize the errors and improves application quality. Circle CI also supports Docker.

Features:- 

  • Availability: Free and paid with trial
  • Platform: Cross platform
  • Supported languages includes Java, Ruby/Rails, Python, Node.js, PHP, Haskell, and Skala
  • Supports Docker
  • Flexible pricing model

10. Codeship

codeship

Codeship is also an powerful hosted CI tool which is available with free and paid support options. This tool is very easy to set up and it automatically deploy the passed tests results. This tool works on GitHub and Bitbucket, but you can use it with docker platform too by opting packages. This tool support langusges such as Java, PHP, Ruby (Rails), Node.js, Python, and Go.

Features:- 

  • Availability: Free and paid
  • Platform: Hosted
  • ParallelCI feature
  • Supported languages Go Ruby on Rails, Node.js, PHP, Java, Go, Dart etc..
  • Flexible Pricing
  • Docker Supported (by upgrading)
  • Easy to setup, fast and reliable
So, this is my list of top continuous integrations tools. Hope my efforts will help you in your Continuous integration process. One more thing, I would like to add here is that, if you want to learn the continuous integration process or you need support to get started with these tools in your work environment than scmGalaxy offers support from industry experts. And, If you think that any others tools deserves place in this list than feel free to share with us in the comment section.
Tagged : / / / / / / / / / / / / / / / / / / / / / / /

Software Development with Team Foundation Server 2015

Introduction
  • Understanding the Feature Path from TFS 2013
  • Introduction
  • Overview
  • TFS 2013 Update Timeline
  • Agile Tools
  • Demo: Agile Tools
  • Git
  • Demo: Git Improvements
  • Demo: Git CodeLens
  • Demo: Pull Requests
  • Testing
  • Demo: Testing Features
  • Summary
Installing and Configuring TFS 2015
  • Introduction
  • Install Options
  • TFS Pre-upgrade Tool
  • Demo: Pre-upgrade Process
  • Upgrading to TFS 2015
  • Demo: Upgrade from TFS 2013 to TFS 2015 Update2
  • Demo: Verify the Upgrade
  • Demo: Project Rename
  • Summary
Working with New Kanban Board Features
  • Introduction
  • Portfolio Management
  • Demo: Epics
  • Demo: Features
  • Product Backlog
  • Demo: Product Backlog
  • Kanban
  • Demo: Kanban Board Intro
  • Demo: Kanban Columns
  • Demo: Kanban Swimlanes
  • Demo: Kanban – Working with Tasks
  • Customizations
  • Demo: Customizing the Cumulative Flow Diagram
  • Demo: Customizing Working Days
  • Demo: Customizing Bugs on the Backlog
  • Productivity
  • Demo: Creating Work Item Templates
  • Demo: Quick Search
  • Sprint Planning
  • Demo: Capacity Planning
  • Demo: Sprint Planning
  • Demo: Sprint Progress
  • Tracking Work
  • Demo: Charts and Alerts
  • Dashboards
  • Demo: Working with Dashboards
  • Summary
Working with New Version Control Features
  • Introduction
  • Version Control Enhancements
  • Demo: Git Branching Enhancements
  • Demo: Working with Git Branches
  • Git Rebase
  • Demo: Git Rebase
  • Git Branch Policies
  • Demo: Configure Branch Policies
  • Demo: Create a Pull Request
  • Demo: Resolve Branch Policy Issues
  • Quick Code Edit
  • Demo: Quick Code Edit
  • Summary
Building Software
  • Introduction
  • Build Agent
  • Demo: Configure a Build Agent
  • Demo: Build Capabilities
  • Build Definition
  • Demo: Create a Build Definition
  • Running a Build
  • Demo: Running a Build
  • Build Customization
  • Demo: Customize a Build and View Test Results
  • Demo: Customize with Build Steps
  • Demo: Multiple Configurations and Parallel Builds
  • Demo: Build Triggers – Continuous Integration and Pull Requests
  • Demo: Capabilities and Demands
  • Demo: Build Definition History
  • Demo: Build Definition Templates
  • Summary
Testing Software
  • Introduction
  • Test Hub1
  • Demo: Create a Test Plan
  • Demo: Create Test Suites
  • Demo: Create Test Cases
  • Demo: Create Test Cases from the Grid View
  • Demo: Shared Steps
  • Demo: Test Parameters
  • Demo: Shared Parameters
  • Demo: Running Tests
  • Demo: Test Run Analysis
  • Demo: Export Test Plans
  • Exploratory Testing Extension
  • Demo: Install Exploratory Testing Extension
  • Demo: Exploratory Testing
  • Demo: Exploratory Testing Results
  • Kanban Integration
  • Demo: Creating Test Cases from the Kanban Board
  • Summary
Integrating with TFS 2015
  • Introduction
  • Marketplace
  • Demo: Installing Marketplace Extensions
  • Demo: Working with Extensions
  • Demo: Manage Extensions
  • Creating Extensions
  • Demo: Create an Extension
  • Demo: Packaging Extensions
  • Demo: Install an Extension
  • TFS 2015 API
  • Demo: TFS 2015 API
  • Service Hooks
  • Demo: Service Hooks
  • Summary
Tagged : / / / / / / / / / / /

Top 25 TFS Interview Questions and Answers

tfs-interview-questions-and-answers

TFS Interview Questions

1) What is Team  Foundation Server? What does it cover – version control? build processes? bug tracking? task management?

Team Foundation Server is defined in the documentation as:

Team Foundation is a collection of collaborative technologies that support a team effort to deliver a product. While the Team Foundation technologies are typically employed by a software team to build a software product, they can also be used on other types of projects.

As the customer already noted three of the core deliverables of Team Foundation Server:

1. Build Process

2. List/Work item Tracking

3. Source Control

This is leaving off probably the two most import features of Team Foundation Server. By integrating the build process, source control,policy and work item tracking you can get a deep insight into what teams are doing and some analytics for future trends which leads to the 4th core deliverable of Team Foundation Server

4. Reporting

Having insight into how a team is tracking is really only half the answer their also needs to a mechanism to share this information which brings us to the last feature of Team Foundation Server:

5. Collaboration (Typically enabled through the Team Portal, Team Project and Process Guidance)

Interestingly it is the two missing categories that set Team Foundations Server apart from other offerings.

2) List out the functionalities provided by team foundation server?

– Project Management

– Tracking work items

– Version Control

– Test case management

– Build Automation

– Reporting

– Virtual Lab Management

3) Explain TFS in respect to GIT?

t

4) Explain how you can create a Git-TFS in Visual Studio 2013 express?

To create a Git-TFS in Visual Studio 2013 express

– Create an account with MS TFS service if you don’t have inhouse TFS server

– After that, you will be directed to TFS page, where you will see tow option for creating project, one with new team project and another with a new team project+Git

– The account URL will be found right below “Getting Started.”

– Click on create git project and it will take you to a new window, where you specify details about the project like project name, description, the process template, version control, etc. and once completed click on create project.

– Now you can create a local project in team foundation server by creating a new project in Visual studio and do not forget to mark the check box that says “Add to source control”

– In the next window, select mark Git as your version control and click ok, and you will be able to see the alteration made in the source code

– After that, commit your code, right click a file in team explorer and you can compare version differences

5) Mention whether all of the team foundation service features are included into the Team foundation server?

TFS service is updated every 3 weeks while Team Foundation Server “on-premise” is updated every 3 months.  So, the on-premise version will always remain a little behind. However, TFS on-premise has got something that the TFS service does not.

– You can use TFS Lab

– Customize work items/process templates

6) Explain what kind or report server you can add in TFS?

TFS uses SQL for its data storage, so you have to add SQL server reporting services to provide a report server for TFS.

7) How one would know whether the report is updated in TFS?

For each report, there will be an option “Date Last Updated” in the lower light corner, when you click or select that option, it will give details about when it was last updated.

8) Explain how you can restore hidden debugger commands in Visual Studio 2013?

To restore the debugger feature that is hidden, you have to add the command back to the command

– Open your project, click on Tools menu and then click customize

– Tap the command tab in the customize dialog box

– In the menu bar, drop down, choose the debug menu for which you want to contain the restored command

– Tap on the Add command button

– In the Add command box, choose the command you want to add and click OK

– Repeat the step to add another command

9) Explain how you can track your code by customizing the scroll bar in Visual Studio 2013?

To show the annotations on the scroll bar

– You can customize the scroll bar to display code changes, breakpoints, bookmarks and errors

– Open the scroll bar options page

– Choose the option “show annotations over vertical scroll bar”, and then choose the annotations you want to see

– You can replace anything in the code that frequently appears in the file which is not meant to be

10) Can I install the TFS 2010 Build Service on my TFS 2008 build machine? 

Yes, you can. Even though they both default to the same port (9191), they can share that port without any problems.

11) Can we disable the “Override CheckIn Policy Failure” checkbox? Can that be customized based on User Login, Policy Type of File type?

No. It is designed it to be fully auditable by including policy compliance data in the changeset details and in the checkin mail that is delivered, but left it up to the developer to determine whether they have a good reason for overriding.

12) What are the different events available in the event model and is there any documentation on them?

There is really only one SCC event and that is the one that is raised on checkin. Subscription is via the general event model that is discussed in the extensibility kit.

13) Are Deletes you make in TFS 2010 Source Control physical or logical? Can accidental deletes be recovered?

Deletes are fully recoverable with the “undelete” operation. You wouldn’t want to do a SQL restore because that would roll back every change to the TFS in the time since the file was deleted.

14) Can different CheckIn Policies be applied on different branches? E.g. Can they have QA specific policies applied on CheckIn in a QA branch?

No.

15) How do I redisplay source control explorer?

Selecting View > Other Windows > Source Control Explorer will display the Source Control Explorer window within the IDE.

16) Why doesn’t source control detect that I have deleted a file/folder on my local disk?

The main scenario here is deleting a file (by mistake or intentionally) outside of Team Foundation and then trying the get that file back from source control. If the file version has not changed the server thinks the user already has the file and does not copy it over. This is because the server keeps a list of files that the user already has and when activities are made outside of source control this list becomes out of date. Team Foundation Version Control does have a force get option which will provide the functionality needed to obtain the desired version but it is currently partially hidden under the Get Specific Version Dialog window as a check box item.

17) Can I compare directory structures in TFS Source Control?

No, you cannot compare Directory Structures in TFS Source Control

18) Can we configure SCC to not check-in the binary files? Where are such configurations done?

Team Foundation Version Control provides a way to limit check-ins by setting up check-in policies that are evaluated before a check-in can take effect. The easiest way to do this is by authoring a policy that checks if the user is trying to check-in a binary file from a given folder structure and reject or accept it in accordance.

19) How can I add non-solution items to source control?

This can be achieved by either clicking the Add icon or by going to File > Source Control and selecting the Add To Source Control menu item.

20) When a user “edits” a file in a “source controlled” project, it gets checked out automatically. Is this configurable? Can we change this behavior?

Yes it can be done by configuring TFS by going to Tools > Options > Source Control > Environment provides an option where a user can change the settings to not checkout files automatically on edit.

21) What plugin / extensibility API does it expose?

The Team Foundation Server component model for modifying both the Process Template and creating plugins is built on to be entirely open(in many cases the entry points are defined in XML configuration files). In addition to the having this the development team and community is quite active in supplying samples of this:

Brian Harry

Buck Hodges

Rob Caron

This open platform has also enabled a ecosystem of add-ons like Teamlook, Teamprise, Teamplain, Teamword, TFSPermission Manager.

22)  How does it integrate with other non-MS platforms?

Team Foundation Server uses Web Services for cross machine communication therefore the Team Foundation Server functionality can be made available to any computer. (see MSDN Team System Article on how to use these web services) This is exactly how companies likeTeamprise, Teamplain, have built their clients to run on non windows computers.

23) How does it integrate with other software (eg custom task management software etc)?

In addition to the integration methods mentioned above Team Foundation is also a popular platform for other software manufacturers to host themselves in. Examples of this is Borland with their Together and Caliber Products and Compuware Testing with DevPartner.

24) How does the version control compare to Perforce? Branching, merging, change lists etc?

Team Foundation Server supports all normally expected Source Control features such as branching, merging, exclusively locking, remote disconnected scenarios, labeling, searching on various properties high fidelity reporting (how much code churn per person per project per iteration etc) plus a couple of newer paradigms like shelving and optimization for things like branching scenarios (many version control systems do a full copy for branches). I would have some performance comparisons but most systems don’t allow this.

25)  Automated build system?

Yes Team Foundation Server includes an Automated Build System. This system is based on MSBUILD and offers the additional functionality of automatically running tests, profiling, code analysis, verifying policies, collating the changesets and workitems for reporting.

26) Any support for distributed build tools? Eg integrating our custom data build tools into the system throughout a network?

MSbuild was written to be extensible and integrate with existing tools through easy to use XML configuration files. Many of the commercial build utilities are already using and/or integrated with MSBuild –such as Cruisecontrol.net. In addition to making these actions part of the build script I have found the generic tests set to run as part of the build to do just as good a job with a rich user interface and support for managing/filtering etc.

27) Documentation support – eg integrating documentation with code check-ins etc?

This would typically be done through an entry to a work item (to be either associated or resolved) on time of check in and linked with this work item.

The links to the documentation can exist in a couple of ways.

1. Checked in as Files (ie doc, HTML etc) Team Foundation Server makes it trivial to link all object checked in (as well as other workitems.)

2. Process guidance files that exist on the Windows Sharepoint Site – Again making it easy for linking.

3. External files once again to linked in a Workitem entry.

28) Does it send data compressed over the network?

Team Foundation uses Web Services for cross machine communication and by default automatically configures IIS use Compression.

29) Working from home / remote location?

Since cross machine communication is accomplished through web services remote access is vastly simplified.

30) Working offline? If the server is offline?

Yes, you need to change the file property to offline via a command utility called TFPT and save changes your local workspace. Any subsequent check-in does a get latest which would resolve if there are conflicts to be merged.

Tagged : / / / / / / / / / / / / /