Improving teams with #Agile and #DevOps principles
Yes! For all customers that are still on TFS2017 update 3 (or earlier…?!) or TFS 2018 update 1…You should upgrade to get access to all cool new features in TFS2018 update 2. Read all about it in the blog post from Microsoft.
Source: Team Foundation Server 2018 Update 2 is now available – Microsoft DevOps Blog
Heel interessant artikel om te lezen hoe VSTS wordt ontwikkeld en gedeployed qua branching in Git. Mooi om te zien hoe ook Microsoft open is over hun manier van werken en hier blog artikelen over schrijft.
Source: Release Flow: How We Do Branching on the VSTS Team – Microsoft DevOps Blog
Het gaat nu toch echt gebeuren. Na ruim 18 jaar medewerker van Caesar te zijn geweest ga ik aan een nieuwe uitdaging beginnen bij Delta-N.
Middels deze weg wil ik iedereen bij Caesar, die ik niet al persoonlijk bedankt heb, bedanken voor de fijne samenwerking aan mooie opdrachten voor zowel Caesar als de klanten van Caesar. Ik heb heel veel geleerd van jullie allemaal en ik ben trots dat ik bij zo’n mooi bedrijf heb gewerkt!
Bij Delta-N kan ik mijn ambitie als DevOps consultant verder gaan invullen in een team met mede DevOps consultants met passie.
De IT wereld is niet zo groot dus we zien en spreken elkaar vast. Ik blijf bereikbaar onder hetzelfde mobiele nummer. Neem gerust contact op!
Update from MS: https://blogs.msdn.microsoft.com/devops/2018/03/28/deadline-extended-for-connecting-vsts-accounts-to-azuread/
Vanaf eind maart (2018) kunnen er geen personal Microsoft accounts meer aangemaakt worden waarvan het domein gebacked is als een business Azure Active Directory. Ik krijg veel vragen over wat dit voor een gevolgen heeft voor VSTS gebruik i.c.m. personal accounts (MSA) en (MSDN) Subscriptions die hier mogelijk aan gekoppeld zitten.
Het gaat in zoverre niet zoveel invloed hebben is mijn verwachting, omdat de meeste van ons met 1 van de 2 onderstaande scenario’s te maken hebben.
A: De MSDN Subscription is op een prive Microsoft account (MSA) geactiveerd. In dat geval kunnen ze de alternate email adres gebruiken voor toegang op VSTS omgevingen die geconnect zijn met een AAD. Voorbeeld: mijn subscription staat geactiveerd op gebruikersnaam@outlook.com. Als alternate email gebruik ik voornaam.achternaam@bedrijfsnaam.nl
B: De MSDN Subscription is op het zakelijk email adres geactiveerd. Hiermee kan toegang verkregen worden op elke VSTS die geconnect is met een AAD. Hiervoor dient de gebruiker wel uitgenodigd te worden via de AAD van het bedrijf of de klant als quest account. Voor de klanten die nog op MSA alleen zitten, kan weer het alternate email adres worden gebruikt. Hier dient dan ook een MSA account voor te worden aangemaakt als iemand die nog niet heeft.
In andere gevallen, kan altijd nog de Subscription aan iemand ingetrokken worden, en opnieuw uitgegeven worden voor scenario B, bij voorkeur. Dit is toch the-way-to-go en is de meeste nette van de 2. Either way. Zorg dat je een personal account hebt die niet gerelateerd is aan een bedrijf, dan kan je altijd bij elke VSTS omgeving.
Nice new blog post from Alex Nichols, Senior Program Manager on the Visual Studio Team Services team at Microsoft:
“We recently published an update to the “Features under development” roadmap on our Features timeline. This feature list, although subject to change and not comprehensive, provides visibility into our key investments in the medium term. We update the feature list as part of our agile planning rhythms, about every 9 weeks. Some of the features link to deep dive blog posts or articles where you can find out more. We also denote the version of on-premises TFS we expect the feature to be included in, often after getting mileage on VSTS. Here are a few features that are particularly noteworthy.
You’ll soon be able to get a little more specific in pull requests. In Q1 we plan to allow pull request contributors to add required reviewers instead of merely relying on branch policies.
In repositories with a lot of branches and activity it can be difficult to focus in on the important pull requests in progress. In Q2 we plan to add filters to the pull request list for target branch and labels to get you collaborating sooner.
While GVFS got it starts in supporting the development of Windows, the largest Git repository on earth, that isn’t the only massive repository at Microsoft. Office also has a lot of code, as you can imagine, and shares a lot of it between their macOS/iOS and Windows products. Based on our work with the Office team, in Q2 we plan to bring GVFS for Mac back out to the community as well in public preview.
We are in the middle of a big refresh to our core hubs in Work. In Q2 you’ll see consistent filter and favoriting experiences across the board to help you get to the work items you care about with ease. As you build the list of favorites you’ll find it handy to quickly jump between the work of various teams or sets of related work.
Last Fall we announced the availability of YAML builds to give you another option for defining and evolving your CI as your code evolves. In Q2 we look forward to bringing that out of preview and making it generally available. In Q3 we look forward to bringing YAML to releases in public preview so that your deployments can evolve with your code as well.
Coming off the release of Azure DevOps Projects last Fall, we’re planning to add additional support to cover even more situations you may have to start a new project. In Q1 we plan to add virtual machines as a new target service option and both the Go and Ruby language options.
Maven artifacts can be set up as a feed in Package Management to share them with your team and organization. In Q2 we plan to make this type of feed generally available and also bring upstream support so you can setup Maven feeds stored in a variety of locations.
As more teams use VSTS for their projects and create accounts, we’ve heard clear scenarios from organizations that have driven focused investments starting with the thoughtful relationship of accounts (known as “Team Project Collections” in on-premises TFS) under a single organization umbrella. We’ve made key progress internally on this current #3 top requested idea on UserVoice and plan to bring this public this year after adopting it for ourselves.
We appreciate your feedback, which helps us prioritize. If you have new ideas or changes you’d like to see, provide a suggestion on UserVoice or vote for an existing one.”
Source: VSTS/TFS Roadmap update for 2018 Q1 and Q2 – Microsoft DevOps Blog
A nice list of improvements and features in the next VSTS release! Check out the below link!
Interessant artikel over de never ending story over accounts en subscriptions in VSTS.
Source: VS Subscriptions and linking your VSTS account to AzureAD – Microsoft DevOps Blog
Nice article about .Net, .Net Core and .Net Framework for clearification in the differences and relations between them.
Source: .NET Standard – Demystifying .NET Core and .NET Standard
Op 26 en 27 september geef ik in samenwerking met Microsoft een tweedaagse Practical DevOps workshop bij Caesar Experts! Deelname is gratis, voor meer info en aanmelden: https://lnkd.in/g6vuQEF
26 September 2017 9:00 – 27 September 2017 17:00
Caesar Experts
Janssoniuslaan 80, 3528 AJ Utrecht
Software engineering practices have changed drastically in the last few years. Agile practices, DevOps, Cloud Computing, Open Source and similar developments have proven their effectiveness. Microsoft’s platforms for software development and cloud computing have also embraced these concepts and are at the leading edge in their domain.
In this two-day training you will learn how software development works with Microsoft’s tools and languages. Based on a consistent sample, you will learn how to
Training Structure
The training is a combination of approx. 50% presentations with embedded demos and 50% hands-on time where you have your fingers on the keyboard and try what you have learned. Those who are new to the topics can follow a provided hands-on lab guide step by step. In areas you are already familiar with, you can put the guides to the side and create an individual sample with the latest tools and technologies. Attendees should already have basic knowledge about Visual Studio, .NET, C#, HTML and JavaScript. Detailed knowledge about the latest versions of these tools, frameworks and languages is not required.
Prerequisites
You will need your own laptop to do the hands-on labs. Ideally, you have the latest version of Visual Studio installed (detailed instructions about the necessary Visual Studio configuration will be provided) and you have access to your own Microsoft Azure subscription. If you do not have access to Visual Studio and/or a Microsoft Azure account, Microsoft will provide a limited number (first come, first served) of free Azure Passes that you can use to run a VM with Visual Studio in it. In that case you just need internet access and a remote desktop client on your laptop.
For the labs about build- and test-automation, you need your own Visual Studio Team Services subscription (free edition available).
Day 1
Day 2
This feature list is a peek into our roadmap. It identifies some of the significant features we are currently working on and a rough timeframe for when you can expect to see them. It is not comprehensive but is intended to provide some visibility into key investments. Most features are linked to a blog post and/or UserVoice entry where you can learn more and comment. These features and dates are the current plans at this time and are subject to change. The “Planned Date” reflects when the feature will be available on VSTS and the “Server” column reflects when it will be available in TFS on-premises, if applicable.
Source: Team Services Feature Updates