|
[
Permlink
| « Hide
]
Riaz Khanmohamed added a comment - 25/Sep/06 03:02 AM
In fact I can't seem to roll back to working version either, no idea what's going on
Scratch that last one. I can return the home page and continue config, but it won't upgrade from a previous version of it's own build file for some reason. Won't read that file - might it have been removed by 0.4.2 or should it ever have been in that original folder?
Ok, here goes
No idea what's going on but it's trying to conver my entire new build dir based on bamboo to the beetlejuice layout, and so it's screwing up midway. The allbuilds used to have it's own folder for beetlejuice, while now it's combined under the build-dir for bamboo. hence the upgrade looks in, thinks allbuilds is a project, converts it to project0 and falls over. Personally, I think your upgrade needs to recognise new and old build dirs, or everyone is going to have problems. I'm somehow going to have to roll back the build directory to the bamboo layout if i remember it, otherwise i'm going to have to start from scratch. I'm glad you have added the ability to upgrade old beetlejuice builds, but perhaps removing the upgrade for new bamboo builds wasn't so wise.... I'll see what i can fix Riaz,
From the looks of it, it seems that Bamboo is trying to re-upgrade your data when it's actually already been upgraded. So it's causing pretty hefty issues. I'll give you an explanation as to why it happened down the bottom in case you're interested. But first, the fix. Do you have a backed up copy of your Bamboo 0.3 data? Are you upgrading from that or directly from the old BeetleJuice data? I'll walk through the install with the data you gave me for BAM-219. The steps here are for upgrading from a previous version of Bamboo (ie. Bamboo 0.3, not Beetlejuice) My directory structure looks like: riaz -> xml-data -> projects -> projects.xml
-> allbuilds -> etc
-> CPJ -> project.xml
-> etc.
-> version.txt (a text file with text "31" in it)
with the folder riaz being the Bamboo home. When you start up, you should specify the the fields as: Configuration Directory: riaz/xml-data/configuration (will be created) Build Directory: riaz/xml-data/projects (existing build data) The description for the Build directory field ("The build directory is where Bamboo checks out the build files") is actually incorrectly and very badly misleading. I've fixed that up now for 0.5. Sorry for the confusion. After adding a new admin user, you'll be asked for the usual admin stuff. Confusingly, there's also a "Build DirectorY" on this screen. This refers to the place where Bamboo checks out the files to, and in your case should be riaz\xml-data\build-dir. And that should be it. Since you're upgrading from Bamboo 0.3, there shouldn't be any upgrade tasks you need to run. The key here is the version.txt file needs to be in the directory above your "Build Directory" (i.e. riaz/xml-data/). Otherwise, Bamboo will assume that your data needs to be upgraded and die a horrible death. Future UpgradesFor future upgrades, you should simply be able to point your new version of Bamboo (say 0.5) to the current Bamboo home (e.g. the folder riaz) and start up Bamboo. It should then be able to handle any upgrades it needs to do on the fly. For the 0.5 release we'll draw up a more detailed pathway to upgrading Bamboo versions ( Cheers, Mark C Long winded technical explanationThis is really just FYI, in case you're interested. Beetlejuice used the version.txt to store the current version information, and it was assumed that this file would sit in the directory above the Project Directory. This file is used to determine whether or not BJ runs various upgrade tasks. Unfortunately, the behaviour is that if the file is not found, the version is assumed to be 1, and all upgrade tasks are run. I'll change this behaviour in Bamboo 0.5, so that no upgrade tasks are run if the file doesn't exist. With Bamboo, we're deprecating this in favour of storing the a new Bamboo version inside the bamboo.cfg.xml and using our own Upgrade framework. So the transition is a little flaky at the moment, but hopefully this will become less and less of a problem as times goes on. Riaz,
Just to follow up, do not use the data that's been partially upgraded to Bamboo 0.4 if possible. Please try the upgrade steps above on a backed up version of Bamboo 0.3 data, as I'm not sure if the faulty upgrade process would've caused your data to be in a bad state or not. Cheers, Mark C Also as a side note, if you're upgrading from Beetlejuice 0.5, there should be a version.txt with the correct version of your BJ instance.
if you're upgrading from Beetlejuice rather than Bamboo, you should use that file instead of the dummy version.txt with 31 in it. cool. We managed to recover the build anyway. I'm going to try and upgrade a standalone beetlejuice 0.5 instance today as it's the final day before the licence runs out so we'll see how that goes.
Don't worry, I always take a backup of everything before upgrading seemed ok upgrading to 0.5 so can probably close this issue now
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Resolved
Major
New instance of bamboo, error upgrading allbuild.xml
