#TFS – Goodbye to TFS Team Rooms

Hello!

I remember when I used Team Foundation Server Team Rooms for the first time. The idea was just great. I even wrote a post about this feature (link) and used Team Rooms for a long time.

 

image

These days, everyone is a self-proclaimed expert on collaboration tools, I won’t get into this category however I need to recognize TFS Team Rooms has been quite behind in the collaboration tools race. There is no point of comparison with a large and popular tool as Slack, or even with one of the latest developments in the world Microsoft: Microsoft Teams. Visual Studio Team System now includes integration supports with Microsoft Teams (link).

And here arises one of the problems we see in the Microsoft ecosystem: the duplicity of tools for a common task. There are certain scenarios where we have 2 or more different ways to approach a single problem.

As well, a few days ago Microsoft ALM Team confirmed the decommissioning of Team Rooms in Team Services and TFS (link). Team Services will be the closure of functionality during the year 2017 and if you have TFS, TFS 2017 1 update will remove this functionality. The TFS team says, there are different alternatives and they are quite varied. It is time to choose one, and take advantage of it to the maximum.

 

 

The Team room is used both for a notification hub as well as for chat. TFS and Team Services already integrate with many other collaboration products including Microsoft Teams, Slack, HipChat, Campfire and Flowdock. You can also use Zapier to create your own integrations, or get very granular control over the notifications that show up.

And my personal thoughts on this.

Some people wrote “Microsoft is killing a product again!”, “What we do now?” and more. I have to admit that I never met a team that really hold his work in Team Rooms. IMHO I think is a good idea that the ALM team discard the source code of this functionality and focus their efforts on more productive tasks for the product and for the community. (In example, improve the integration of Visual Studio and Unity). Finally, if you are still disgruntled – angry about this, for sure you’ve never tried Slack or MS Teams, not only change is fabulous as a tool, but is also highly productive!

That Yes, I have already read and surely will read complaints in this regard.

Greetings @ Cordoba

El Bruno

References

Advertisements

#TFS – Adios a TFS Team Rooms

Hola !

Recuerdo cuando probé por primera vez Team Rooms en Team Foundation Server, la idea me pareció simplemente genial. Inclusive escribí algún post al respecto (link) y las utilicé durante mucho tiempo.

image

En estos días, donde todo el mundo habla y se autoproclama experto en herramientas de collaboración, hay que reconocer que TFS Team Rooms ha quedado bastante detrás en la carrera. No hay punto de comparación con un grande como Slack, o inclusive con una de las últimas novedades en el mundo Microsoft: Microsoft Teams. Inclusive Visual Studio Team System soporta una integración muy potente e interesante con Microsoft Teams (link).

Y aquí surge uno de los problemas que vemos en el ecosistema Microsoft: la duplicidad de herramientas. Hay determinados escenarios donde nos encontramos con 2 o más formas diferentes de enfocar un flujo de trabajo.

Pues bien, hace unos días el equipo de ALM de Microsoft confirmó el cierre definitivo de Team Rooms en Team Services y en TFS (link). En Team Services el cierre de la funcionalidad se dará durante el año 2017 y si tienes TFS, el update 1 de TFS 2017 eliminará esta funcionalidad.

Como bien comenta el equipo de TFS, hay diferentes alternativas y son bastante variadas. Es momento de elegir una, y sacar provecho de ella al máximo.

The Team room is used both for a notification hub as well as for chat. TFS and Team Services already integrate with many other collaboration products including Microsoft Teams, Slack, HipChat, Campfire and Flowdock. You can also use Zapier to create your own integrations, or get very granular control over the notifications that show up.

Y por último una opinión personal al respecto.

Si bien algunos comentarán “otra vez MS matando un producto!”, “y ahora que hacemos”, etc. Tengo que reconocer que nunca conocí un equipo que realmente sostente su trabajo en Team Rooms. Es mejor que el equipo de ALM descarte el código de esta funcionalidad y centre sus esfuerzos en tareas más productivas para el producto y para la comunidad. (Por ejemplo mejorar la integración con Unity). Y finalmente, si sigues mosqueado – enfadado al respecto, pues será que nunca has probado Slack o MS Teams, el cambio no solo es fabuloso a mejor, sino que además es altamente productivo!

Eso sí, ya he leído y seguramente leeré quejas al respecto.

Saludos @ Córdoba

El Bruno

References

#ALM – #TFS 15 RC2 available, your TFS on premises side-by-side with VS Team Services (almost!)

Hello!

During the ALM training with my LemonCode friends, one of the questions which I was waiting it related to the differences between the capabilities and features between Team Foundation Server and Visual Studio Team Services.

Although, initially the both have the main base features, VS Team Services receives updates each a couple of weeks. And, usually we need to wait a couple of days / weeks to have them available for TFS.

In example, now that the TFS15 RC2 has been released, we can find some cool features already available in VS Team Services.

Based on original MSDN post, I share the list of this Release Candidate 2 main features:

  • Follow a work item – makes it super easy to track the progress on work that you care about.
  • Code search – Makes it easy to find code anywhere across your project.
  • Package management – Improves your ability to reuse components across your projects (both OSS and internally produced)
  • Improved Git web experiences, including revamped pull requests and branches pages – pull requests include a new auto-complete feature
  • Docker support – in build and release management.
  • Release management – the number of significant improvements and new capabilities is very large.
  • Parity between MTM and web TCM – We almost have parity now where all the things you are used to using MTM for, you can now use the web experience for.
  • Paid extensions – You can now purchase and install extensions in TFS

Greetings @ Toronto

El Bruno

References

#ALM – #TFS 15 RC2 ya está disponible, tu TFS puede competir con VS Team Services (o casi!)

Hola !

Durante el curso de ALM con los amigos de LemonCode, una de las preguntas que estaba esperando era la relacionada a las diferencias entre las capacidades y funcionalidades que tienen Team Foundation Server y Visual Studio Team Services.

Si bien, inicialmente las funcionalidades básicas son las mismas, VS Team Services recibe actualizaciones cada un par de semanas. Por lo general, luego hay que esperar un par de días / semanas hasta tener las mismas disponibles para TFS.

Por ejemplo, ahora que se ha liberado la RC2 de TFS15, en la misma podemos encontrar algunas funcionalidades que ya tenemos disponibles desde hace tiempo en VS Team Services.

A modo de ejemplo, dejo el listado de esta Release Candidate 2:

  • Seguir un WorkItem, ahora es fácil seguir el progreso en los WorkItems que nos interesan.
  • Búsqueda de Código fuente, ahora es más fácil encontrar código en cualquier lugar.
  • Mejor en la experiencia web para Git, incluyendo mejoras en las vistas de las branches y la gestión de Pull Requests, por ejemplo con la capacidad de autocompletar
  • Soporte para Docker, en Build y Release Management.
  • Release Management, en este aspecto hay muchas mejoras importantes.
  • Paridad entre MTM y TCM (web) , la paridad entre ambos productos está casi completa. Casi todas las funcionalidades de MTM están implementadas en TCM.
  • Soporte para extensiones de pago, ahora se puede comprar e instalar extensiones en TFS

Saludos @ Toronto

El Bruno

References

#TeamServices – Prueba las extensiones de pago en en forma gratuita por 30 días !!!

Hola !

Ho toca una buena noticia para los usuarios de Visual Studio Team Services y Team Foundation Server. Ahora tenemos la posibilidad de probar las extensiones de pago del Marketplace por 30 días. La verdad es que la idea está muy bien, porque 1 mes es un buen periodo de tiempo para evaluar si una herramienta (o extensión) se adapta y aporta valor en un equipo de trabajo, después de este tiempo ya podemos tomar la decisión correspondiente.

El proceso para probar una extensión de PAGO es similar al siguiente:

Acceder al Marketplace

image

En este punto podemos ver las extensiones gratis (FREE), las que están en modo pre visualización (PREVIEW) y también las de pago (PAID). El post original utiliza la extensión Test Manager como el ejemplo de una extensión.

image

Una vez que accedemos al detalle de la extensión de pago, podremos ver la opción de comprar o de comenzar el período de prueba por 30 días.

image

Y a partir de comenzar este período, queda todo en nuestras manos. Eso sí, al finalizar el período no deberemos pagar o nada parecido, si nos “pasamos de largo”. El servicio se descontinua automáticamente y si queremos tenerlo online, es momento de sacar la tarjeta de crédito.

Saludos @ Toronto

El Bruno

References

#TeamServices – Try paid extensions for 30 days for Free !

Hi !

Some good news for the Visual Studio Team Services and Team Foundation Server users. Now we can browse and test the paid extensions in the Marketplace for a 30 days trial period. This is very cool, as in a team testing mode, 1 month is a good enough piece of time to try some of this extensions and make a choice.

The process to try a PAID extension is similar to this one:

Go to the Marketplace

image

And now we can see the FREE extensions and also the ones in PREVIEW mode. The original post uses the Test Manager as a sample for a PAID one

image

Once we are in the Paid extension, we can start a 30 days trial to try and test the extension.

image

Once you have installed / deployed the extension, you’ll start a 30 days trial and get notified once the trial period is over.

Greetings @ Toronto

El Bruno

References

#VS2015 – Pull Request from VS IDE ? in the near future …

Hola!

For sure, you already know what is a Pull Request. For the ones working with Git, is a key piece for the collaboration process. The most basic definition could be: A user requests that the changes made in a fork of a repository, are implemented in the original repository.

GitHub Pull Request interface Is very popular

Team Foundation Server also allows us to work with Pull Request using web interface

However, as a string Visual Studio user, I miss this feature inside the IDE. If you are used to work in a single tool, you try to perform most of your tasks inside this tool. The good news is that, a few days ago, Jeremy Epling, on the Visual Studio ALM blog, wrote some of the features that are working both for Visual Studio Team Foundation Server. One of them related to the ability to work with Pull Requests in the IDE.

Pull Requests in Visual Studio

A major part of most Git workflows is reviewing code submissions using pull requests. The current experience in Visual Studio is a link to the website, but we’re updating it so you can accomplish more of the pull request workflow inside Visual Studio. You’ll be able to create a new pull request, and view active pull requests assigned to you or created by you. Later, we’ll bring an improved experience for pull requests to Team Explorer Everywhere.

Pull Requests are easier to find and review

No one wants to dig through a long list to find a pull request. To make it easier, the pull requests relevant to you will be grouped together and sorted to the top. You can still get to all pull requests, as well as filter them by their status and who they’re assigned to.

When you get to the pull request you want, the new details page will make it easy to find the status and act on it. Reviewers will have a clear way to provide feedback and approve the pull request. Owners will have an easy way to see the status and merge. When the pull request is complete, you can customize the merge message and a merge commit will always be created so it’s easier to view the repositories history.

Let’s hope for the implementation in this feature does not take long to become public. And then we can start give our Feedback and thus improve the experience of Visual Studio

Saludos @ Madrid

/El Bruno

References

· GitHub Using Pull Requests https://help.github.com/articles/using-pull-requests/

· Git Experience Features http://blogs.msdn.com/b/visualstudioalm/archive/2015/08/27/git-experience-futures.aspx

#VS2015 – Pull Request en el IDE ? dentro de poco tiempo …

Hola!

Seguro que ya sabes lo que es un Pull Request, es una de las piezas clave cuando trabajas con Git. Es una de las formas más básicas de colaboración, donde un usuario pide que los cambios que ha realizado en un fork de un repositorio, se apliquen en el repositorio original desde el que se creó el fork.

Uno de los sitios donde más se trabaja con Pull Request es en GitHub, y la interfaz para crear un Pull Request es bastante conocida

Team Foundation Server también nos permite trabajar con Pull Requests desde la interfaz web

Sin embargo, echamos de menos esta funcionalidad en el IDE. Cuando te acostumbras a trabajar en una única herramientas, pues lo mejor es no salir de ella. Hace unos días, Jeremy Epling, en el blog de Visual Studio ALM, comentaba algunas de las funcionalidades en las que están trabajando tanto para Visual Studio como para Team Foundation Server. Una de ellas relacionada con la capacidad de trabajar con Pull Requests en el IDE.

Pull Requests in Visual Studio

A major part of most Git workflows is reviewing code submissions using pull requests. The current experience in Visual Studio is a link to the website, but we’re updating it so you can accomplish more of the pull request workflow inside Visual Studio. You’ll be able to create a new pull request, and view active pull requests assigned to you or created by you. Later, we’ll bring an improved experience for pull requests to Team Explorer Everywhere.

Pull Requests are easier to find and review

No one wants to dig through a long list to find a pull request. To make it easier, the pull requests relevant to you will be grouped together and sorted to the top. You can still get to all pull requests, as well as filter them by their status and who they’re assigned to.

When you get to the pull request you want, the new details page will make it easy to find the status and act on it. Reviewers will have a clear way to provide feedback and approve the pull request. Owners will have an easy way to see the status and merge. When the pull request is complete, you can customize the merge message and a merge commit will always be created so it’s easier to view the repositories history.

Esperemos que la implementación no tarde mucho en llegar al público, para que podamos comenzar a dar nuestro Feedback y así continuar mejorando la experiencia de Visual Studio

Saludos @ Madrid

/El Bruno

References

· GitHub Using Pull Requests https://help.github.com/articles/using-pull-requests/

· Git Experience Features http://blogs.msdn.com/b/visualstudioalm/archive/2015/08/27/git-experience-futures.aspx