Skip to main content

Integrate JAVA development in your Team Foundation Environment

At our company, we are integrating JAVA development on our Team Foundation Server 2010 environment. Thanks to Team Explorer Everywhere and the nice Eclipse integration, this is very easy to do. So our JAVA developers can benefit from all the rich features offered by TFS.

There was only one step left to configure, integrating the JAVA build environment with TFS. Turns out, that this is very easy to achieve thanks to the Team Foundation Build Extensions. It provides the ability to execute Ant or Maven 2 builds from Team Foundation Server and publish the results of the build along with any associated JUnit test results back to Team Foundation Server.  This not only works for Team Foundation Server 2010, but also for Team Foundation Server 2005 and Team Foundation Server 2008.

How to get this done?

First install the JAVA JDK, Ant (if Ant support is required) or Maven 2 (if Maven support is required) on your build server. Afterwards install the build extensions on the build machine. In addition, you should configure the appropriate environment variables (i.e. JAVA_HOME, ANT_HOME, M2_HOME) as per the relevant install guidance for Ant and Maven. These environment variables should point to the correct install locations.

As a last step, you must create a build definition which makes use of them.  The easiest way to do this is to use a Microsoft Visual Studio Team Explorer Everywhere client to create the build definition.

That’s all!

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more