I’ve started to play around with Jenkins yesterday and I kinda don’t like that it’s default home directory is /var/lib/jenkins so I changed it to /home/jenkins, so I’m throwing the steps needed out here for future reference.

First, stop jenkins:

robert@odin:~$ sudo /etc/init.d/jenkins stop

Create the new home directory and move existing stuff from the old home to the new one:

robert@odin:~$ sudo usermod -m -d /home/jenkins jenkins

Now, I didn’t manage to set the ENV JENKINS_HOME to the new home, it was always using the old one, so I edited the init.d script:

robert@odin:~$ sudo vi /etc/init.d/jenkins

and in the “DAEMON_ARGS=…” line change JENKINS_HOME env to --env=JENKINS_HOME=/home/jenkins. In the end the whole line reads something like:

DAEMON_ARGS="--name=$NAME --inherit --env=JENKINS_HOME=/home/jenkins --output=$JENKINS_LOG --pidfile=$PIDFILE"

Update on September 20th: Vranac blogged about how to change the JENKINS_HOME properly

Start jenkins

robert@odin:~$ sudo /etc/init.d/jenkins start

and go to http://server:port/configure and verify that jenkins works as before and is using the new home.

Happy hackin’!

It’s been a while since I last wrote something; didn’t have anything smart or interesting to say. Not that I do have this time. It’s 4AM and I can’t sleep. Can’t really find the inspiration for work and writing (if you can consider these scribblings as writing). Lots of ssss… stuff happened which had a great impact on my mood and my ability to do something useful. And I just didn’t felt like doing something about it. Until recently…

I was having a couple of beers with a friend of mine, with whom I go to college. After the 3rd beer or so, we came to an idea of submitting a paper to this year’s SISY conference. All I will say for now, that it will include Python, Assembly, microcontrollers, electric motors and lots of other geeky stuff. This project, even while the idea is still only in my head, got my mind running again and might be the way out of this state of indifference. Why? Well, to be able to start this project, I first need to finish my current project, my graduate work. To finish my grad work, I needed to start working on it again (which I did, honest!). I’ll even spend my whole Saturday this week in the college to write/test/debug my app there. If all goes well, the app will be finished this week and I can go onto writing the documentation for the grad work. Everything will go fine, right?

I installed Ubuntu 9.04 on my laptop a few days ago. Loving it! Had only 2 minor issues with the hardware upon the installation. First, the graphic card was messing around, it didn’t want to enable all those funky visual effects. That got sorted out, thanks to @firusvg who suggested to install compiz and @ivan86 who pointed me to this article. Second, when plugged in the headphones, the sound was still coming out on the speakers. @Asgrim sent me this link which helped me to sort this out. Apart from this, everything else works out-of-box. Even the wifi!

OK, enough for now. Here’s to hoping that the bad times are over and the good times are coming. Cheers!

I wrote a Python script for automating the steps required to setup a web project environment on my local dev machine that runs on Ubuntu. Called it pywst: Python, Web, Svn, Trac. That’s the best I could do, sorry :P

The main steps for setting up a new project are:

• Create a virtual host
• Add it to /etc/hosts
• Enable the virtual host
• Import the new project to the SVN repository
• Checkout the project to /var/www
• Create a TRAC environment for the project
• Restart Apache

After these steps I have http://projectName.lh/ which points to /var/www/projectName/public/, SVN repo under http://localhost/repos/projectName/ and the TRAC environment under http://localhost/trac/projectName/.

As I have this ability to forget things, I always forget a step or 2 of this process. Thus, I wrote pywst (note, this is a txt file, to use it, save it to your HDD and rename it to pywst.py). It’s not the best and nicest Python script ever wrote, but gets the job done. All that is need to be done to setup a project with pywst is:

sudo ./pywst.py projectName

2 things are required: to run it with sudo powers and to provide a name for the project.

Future improvements

The first, and the most important is to finish the rollback() method. Now, it only exits pywst when an error occurs, but it should undo all the steps made prior to the error.

Second, to make it work on other distros, not only on Ubuntu. That would require for me getting those other distros, set them up, look where they store Apache and stuff, where’s the default document root, etc. Hmm… This will take a while :)

Third, support PHP frameworks – Zend Framework, CodeIgniter and CakePHP — ZF is a must :P Under support I mean to create the basic file structure for them automagically.

Cheers!

Last night @zsteva shared a link of a free online magazine about Ubuntu called Full Circle Magazine:

Full Circle is a free, independent, magazine dedicated to the Ubuntu family of Linux operating systems. Each month, it contains helpful how-to articles and reader submitted stories.

The current issue is #21. All issues are available on the download page.

The current issue is a 45 page PDF; it contains news, tips on using the console, different how-tos, game reviews, interviews, etc.

Enjoy the reading, cheers!

Today I was messing around with Trac, installing it and doing some basic configuration. While my dev machine gets updated, I want to share my process of installing Trac.

What is Trac?

As said on the Trac homepage:

Trac is an enhanced wiki and issue tracking system for software development projects.

It’s free, it’s open source, it comes under the BSD license and it’s really awesome. You can write a wiki with it, have a ticket system, connect it with SVN, so you can browse the sources from the browser and see all the commit messages, when was something changed, added… It can support one project, it can support multiple projects. It can be viewable/editable by anyone, or you can close it down for your little team…

Trac is big. It has lots of plug-ins, so you can extend and customize your Trac. I haven’t played with them yet, but as soon as I will, you’ll get notified ;)

It’s written in Python. It can run on it’s own server, or it can run under Apache (where there are also several options). It can use SQlite, PostrgeSQL or MySQL databases. Currently it can connect only to SVN.

I’ll show you how to setup a basic Trac 0.11-dot-something-dot-something. It will run under Apache with mod_wsgi, use a SQlite database, connect to the SVN repository and require user authentication.

Continue reading this post…