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,
One question that has been coming my way recently is how would those that are interested in InfoSec actually get started in this field of white-hat hacking. This page is a collection of suggestions that have been given to me by friends and colleagues in an attempt to answer that question. It is in no way supposed to be a concise list, nor would I want it to be. Start with what’s below and then reach out and find more.
Pluralsight is a fantastic collection of online courses covering many topics. They have a great collection of Ethical Hacking courses.
This site is a fantastic collection of games and challenges. They start off assuming no knowledge at all with the great Bandit game. It teaches you the basics needed through a series of 26 levels, each one teaching you something new.
The New Year comes round so fast! Too fast for my liking. Mostly because it means that we have to stop buying new board games until we’ve played through our library.
For those of you who are new to the blog, or to the idea of a Board Game Truce, it is quite simply a single rule that Amy and I force ourselves to live by each and every New Year. That rule is as follows:
We shall not purchase any more board games until we have played all the board games we own, at least once.
Games themselves count once, then each expansion pack also counts, unless it makes sense to combine the packs (judges final decision etc.) For something like Carcassonne we would play the two expansion packs we have separately, for Escape: Curse of the Temple we put the two expansion packs we have together into one game as it makes more sense to play them together as a single expansion. However we would still play Escape twice. Once without the expansions and secondly with both expansions.
Escape, Curse of the Temple: You can’t have more fun in 10 minutes!
Those of us who work in a client-focused bespoke-software development arena know the joys of working on multiple platforms for multiple-clients, all wanting their own work first.
In such an arena it’s difficult to keep account holders updated with sprint plans and priorities. It’s even more difficult explaining how sprints work and why sprints have to stop on specific days and why work that doesn’t fit can’t just roll over a sprint and push everything back by a day or two. Keeping clients and account managers happy, keeping track of what’s booked into specific sprints, all with client deadlines and delivery dates, quickly becomes a nightmare task. Continue reading