Sometimes I feel like Rose in the Golden Girls. I have all these stories to tell, and everyone tells me to shut up.
Tonight is the premire of Gilmore Girls. I’m very excited about that. 🙂 I hear it’s going to make everyone cry.
I’m going to go camping this weekend, that is as long as I don’t have to help with the builds. I’ve been telling myself that I’d go camping forever. And well, now I’m actually going to do it!
I couldn’t sleep very well last night, I kept thinking about a lot of things. And well, spent some time crying as well. Oh well.
Yesterday at work was OK. I’m starting to put HD documentation into the Wiki, which is an annoying job, but at least it’s giving me a break from coding for a while. Plus we had a meeting about how to speed up the build/deploys. Things we’ve been bitching about forever. It always comes up from the higer-ups though about the time we’re on crunch because they want them out so the QA people have more time to work with each build. It’s understandable, but there’s nothing we as SA’s can do now to speed things up. Here’s the current break down:
* 1-1.5 hours to do the build (Compile) with no problems. This can easily and usually does take much longer because of failures on the developers side, not on the SA side.
* 1 hour to deploy internally. This part could go faster, if we had better dev boxes to deploy to, but can not be skipped. This is where we find out if a script is broken before deploying to the QA sites.
* 2-3 hours to transfer the build to the QA sites (It’s a 460 Meg Zip file… This is where we should be able to cut the most amount of time, by getting a faster connection to the QA sites.
*1 hour to deploy to the QA sites.
So basically if there are NO problems, which is very rare, it’ll take 5 hours. Lately I’ve been having them done by 1 or 2 in the afternoon. Which is still pretty good I think. But that’s just me!