Over the years, I have coached and researched dozens of scrum teams to adapt to “real world” scenarios. Some may call them anti-patterns or some may call them “not scrum”-- but that is okay too because sometimes we have to work with what we have and still find ways to be successful.
The very notion of economies of scale arose during the early industrial age but unfortunately is still prevalent in many industries, including software development. However, that has changed with DevOps but it still isn’t obvious otherwise I would not come across customers that still work in this paradigm.
Unfortunately, many enterprises have multiple organizations and projects in their portfolio and merging them into a single project can seem a daunting task. While there are tools out there that can help, there is no “Single Tool To Rule Them All”.
We experienced many different emotions with what seemed like a daunting task. What made it less daunting, the facilitators reminded us, was that we are not alone - we are team - so, leverage each other.
Coding has evolved from incubators to online hubs which allow for remote coding. The size of applications has become increasingly difficult for a single person to code. Experts in various coding areas, therefore, converge on the virtual platform in order to contribute to the more massive code repository.
The most recent problem revolves around Git 4 Windows (Or any other Git client) and certificate revocation checking against Team Foundation Server (Or other source control) secured with a .mil URL, or any URL secured with a Department of Defense (DoD) signed certificate.
Depending on what version of TFS you intend to migrate and what features you are using, there are a few things that in my opinion are “major” considerations because they have the potential of adding scope to your migration efforts. While you will find out about them as you read through the official migration guide, I believe there is value to knowing these things prior to embarking in such journey.
The reason for this post is to help customers realize how to satisfy the CFR – Code of Federal Regulations, Title 21, PART 11 ELECTRONIC RECORDS; ELECTRONIC SIGNATURES requirements with Team Foundation Server, Azure DevOps Service and Azure DevOps Server.
I was working on a DevOps scenario that involved automating the deployment of batch process files from one server to one or more other servers. To accomplish this, I created a build pipeline to collect certain files from the staging location and store them as Build Artifacts. I then created a release pipeline to ask for deployment approval and then deploy the build artifacts to servers in other environments.
Prior to Team Foundation Server (TFS) 2017, moving or cloning of a TFS instance required manual preparation and configuration of existing instance’s backups. You can now configure your restored databases completely through the application tier.
This blog walks through the new process to demonstrate how to restore and configure an instance of TFS to new hardware.