TLDR; Upgrading YouTrack to 7.0 and getting a “Failed to execute refactoring for entity type: Event” memory error in the Hub upgrade? Add more physical RAM, then add some more, with maybe a little more on top. YT 7.0 upgrade process is memory hungry.
If you’ve read the previous posts on this site, scrolled through my Twitter feed, or spoken to me about issue management, continuous integration, delivery or deployment, then you’ll have probably heard me talk about the Jetbrains product, YouTrack. Heck, I even used it to ticket-manage my wedding back in 2014!
YouTrack is, in a nutshell:
Easy-to-use, fully customisable issue tracking and agile project management tool your development team will love.
(Those are Jetbrain’s words) – and they’re right. It is easy to use and your dev team will love it. Especially if you’ve made them use other management tools, especially that one beginning with a ‘J’. Ouch.
Anyhow, We’ve been running YouTrack 6.5 as a standalone JAR instance, on a linux box, for quite some time. The recent announcement of YouTrack 7.0 with it’s enhanced agile boards and other wonderful improvements meant I was quite looking forward to updating. Along comes the fateful day and having taken another backup (never hurts to have multiple backups) we took the service down and started the upgrade.
UPDATE: The book I mentioned, Continuous Delivery with Windows and .NET, by Chris O’Dell and Matthew Skelton, can be found here.
On a lovely warm Thursday evening in May I returned to the speaker’s floor and presented a great session on Continuous Integration, Delivery and Deployment, to a fantastic group of developers at DevSouthCoast in Southampton.
The main takeaways from the session are all about how easy CI, CDel and CDep can be to get going, as well as how you can start the process off for free using popular, industry-used products. One of the most exciting parts of this session for me is that everything about the session is live. Using two VMs I replicate a standard setup – installing and configuring the applications right there on the session floor. Whilst the progress bars load I talk about how the applications I’ve chosen will help the process flow and what they bring to the Continuous party, Continue reading →
“Once in every show there comes a song like this..”
My personality means I am always wanting to push myself further by learning new things, pushing my boundaries and taking on new challenges. This was, in part, the reason why I took on the challenge of presenting at DDD events many years ago and a major part in the difficult decision to leave my current position as Development Director at Morning Data. It is an inevitable decision once you realise you’re not pushing yourself as much as you should, much like the inevitable emotion-rousing song in musical theatre.
When I joined the company back in February 2003 I was the very first employee and the first to introduce the company to the world of the Microsoft .NET Framework. Bring us forward to the current day and I leave the company as their Development Director having risen through the roles of Senior Developer and Head of Development. I leave behind me a fantastic team of excellent, talented, first-rate developers and co-workers whom I have had the pleasure of calling my colleagues and will continue to call my friends.
With the company we broke the golden rule of rewriting software and successfully proved that it is possible if managed and handled properly within the team. Between us we introduced Continuous Integration, Build Radiators, Continuous Deployment, Unit Testing, TDD, Kanban boards, morning stand-ups, the infamous WAT board and as much agile as we could stomach. The company is now poised for many, many great things and wish them all the success in the world. For me its onto a brand new challenge and it all starts tomorrow.
Before the blog starts to whitter on about new tech, new application purchases, features and functionality found and how use of tech has helped or hindered me it’s probably useful to get a baseline written of what tech I currently have and what I use day to day.
First off, desktop computers.
At home it’s a 27″ Apple Mac.
At work, a Dell Optiplex running Windows 7
The Mac also runs Parallels, which through the use of a Watchguard VPN allows me to connect Outlook to my work mailbox. My own personal mail is collected in Mail on the Mac. At work I’m a Development Director for a software company so most of my time is spent in Visual Studio 2010 and now 2012, Outlook and YouTrack, our bug tracking/ticket software from JetBrains.
As almost all developers will know, in a commercial development team, work is handed out in the form of tickets. Each ticket, in my view, represents a single piece of work and no ticket should cross the streams (or subsystems.) ie; the ticket shouldn’t contain requirements for changes to both the code and the database, as this is, in my opinion, two separate tickets that are related to each other (or, the code ticket depends on the database ticket – see the logic?)
Up until recently we’ve been assigning tickets to devs and discussing with them which tickets are next on their list, going by priority, ticket-type etc. Whilst this worked in some cases, in others it didn’t as the priority wasn’t clear enough and developers tended to cherry pick the best tickets first, as opposed to the most important, or they hadn’t written them down or something else came up that was more important and the list was thrown out the window.