At SMEx Digital we have a distributed Scrum development team with resources in Australia and South Africa. Typically at the start of the day in Australia, the QA resource logs into Octopus deploy and pushes that latest version from Dev to QA to perform integration tests, as there would be new commits coming overnight from the team in South Africa.
So to save the tester roughly 10 minutes each morning waiting for environments to be deployed to QA, I decided to automate this process using Octopus Deploy and Azure Functions
At SSW, we are currently migrating our SQL Server Reporting Services 2008 R2 reports to our new SQL Server Reporting Services 2016 server.
If you haven't decided to make the move to SSRS 2016 you should check out What's New in Reporting Services (SSRS). The main features we care about are:
- Better Portal
- Mobile Reports
- PowerBI integration
- Better HTML5 report rendering
Recently we've been getting the following error for our TFS build agents which caused all our builds to fail
The error reported is "The job has been abandoned because agent <agent name> did not renew the lock. Ensure agent is running, not sleeping, and has not lost communication with the service."
Investigating the _diag folder of the build agent itself reveals the actual error.
For the last month or so I've been living with my Visual Studio 2015 hanging for up to two minutes when simply right clicking on the web project and selecting Publish.
Well today I got fed up with waiting and went to search for solutions. I stumbled across this Stack Overflow answer from Mike.
One of my pet peeves is having differently versioned NuGet packages across my projects. Previously I would just dig around in the packages.config of each project and check if the versions are consistent and install the right versioned package. Never again!