Modify your ‘index.htm’ using html editor to look something like this:

19. Start up your project in tomcat. The page should display current time!


Additional Comments:
I know that this is just a quickfix, and I just cannot belive that there is no proper eclipse plugin using the latest click framework, which would be up to date, if you know any, than please comment and save me and my readers precious time.

Thank you.

In fact you don’t have to even know object properties to generate the report, we will use Apache DynaBeans for that:

This is a simple example code snipped showing you how to get started with the simplest and most dynamic reporting library ever (as well as lacking features probably but we hope its enough for simple projects)

This example assumes the following:

1. You want simple report
2. You dont have to know the object which properties you want to display in advance, by this I mean you can create report columns dynamically, and by using apache dyna beans your objects don’t have to even exists. You just dynamically create them and inject them into the report.

Here is an example test class showing you how to use jasperberry, for more info please contact us directly at softberries.com
Code:

You should find similar snippet in a test suite of the project.
The project itself is licensed under LGPL and its available from sourceforge here

Enjoy!

So, how do you set up your own? Well, actually its not that difficult but looks scary at the frist sight. First of all of course, you would have to download and install all software needed, and this is:

Visual Studio 2008
Subversion
Tortoise or Ankh SVN(recommended)
CruiseControl .NET

That should be it on the server side! While installing just follow the defaults and you should be fine. I do install Cruise Control directly on the C: drive which ends up as C:CruiseControl.NET but you can install it wherever you want, I do it this way as its easier for me to write scripts if neccessary (short pathes instead of long ones).

Once CC.NET is installed you should be able to run it. You have two options, first one run it as a console app or run it as a service. For the setup, I would recommend running it as a console, make sure that CC.NET service is not running and double click ccnet.exe file inside C:CruiseControl.NETserver directory or any other ’server’ directory depending on your installation path.
If all went fine you can see the CC.NET dashboard in your browser. Just browse to the url ‘http://localhost/ccnet’ where ‘ccnet’ is a virtual directory created by Cruise Control application setup.

Ok then, once all is runnning and installed we can start configuring our CC server. To do that you would need to open ccnet.config file in your favourite text editor. Inside ccnet.config you will be able to set your project which should be build and tested by Cruise Control. The ccnet.config file consist of a number of project sections. You can have as many ‘project sections as you wish, all contained inside the root element of the document.

Lets configure one of the projects, all elements described above would be a subnodes of the project element. First of all we need to specify a working directory for our project. Simply create a dir on your drive somewhere and add a path to it between ‘workingDirectory’ elements. This directory will be used to download the subversion sources.

After we specify ‘workingDirectory’ we have to specify a trigger which will call updates on our source code, checked out form the subversion. Right here we specify that CC.NET should check the subversion repo every 60 seconds and if it finds any modifications it should run the whole continuous integration process.

To allow cruise controll download/update your sources, we need to specify the adress of the subversion repository as well as username and password

This section was pretty easy, after we specify working directory, trigger and subversion settings we are ready to add sections responsible for building, testing and publishing our results.
All of the mentioned should happen inside the ‘tasks’ section so, just after the ’sourcecontrol’ element add the following:

Inside the ‘tasks’ we will add the elements for building the project/solution (msbuild element), unit testing (2 times ‘exec’ element), publishing our work to a separate directory (‘buildpublisher’ element) as well as publish our test results to CC.NET dashboard (‘publishers’ element).

To do all that, we need to first build our project. We are going to use MSBuild.exe which you should be able to find in C:WINDOWSMicrosoft.NETFrameworkv3.5 if you are using .NET 3.5 version. Instead of building single project we are going to build a whole solution. To build a solution you need to specify the place where the solution file exists as well as the name of the solution file itself. Depending on the project size and characteristics you have to set the timeout option to suit your needs and to prevent CC.NET to timeout before the project have a chance to actually build.

Ok, so we are already able to automatically build our project and this is really cool but what would be continuous integration without executing unit tests . As it makes development easier, for my projects, wherever possible I use built in Unit Test functionality in Visual Studio 2008.In my opinion, VS Unit Tests are a bit more tricky to set up than NUnit on CC.NET, especially publishing results part of it) but the developmnet on the other hand is easier and I will stick to it.
We need to do the following three things to properly execute tests. First of all we need to run tests using MSTest.exe, this part is pretty easy but before doing that we need to delete previous test results or otherwise our MSTest would complain. Therefore you have to add into your tasks the two following ‘exec’ sections.
First one to delete any previouse test results using bat file (deleteTestLog.bat) with single command:

Second ‘exec’ section running the actual unit tests:

Right now our server builds and tests our solution automatically. If we want to publish the build results somewhere else, lets say to another virtual directory or web site we can copy the files using ‘buildPublisher’. This way, if its a web application, after each build you can browse to the web site url and see the latest changes in place, all freshly build and tested.

At this point we have a continuous integration server running which automatically update our solution if it detects any changes on subversion server, builds the sources, runs unit tests and publish the build results. This is great, one problem though, MSTest is not well integrated into CC.NET so we won’t be able to see our tests results, if any fails for e.g. on our CC dashboard.
To publish your test results into cruise control dashboard you would need to add the following section inside your ‘project’, just after ‘exec’ or ‘buildPublisher’ sections:

This will merge your test results into the dashboard.

I hope you will enjoy having continuous integration as part of your project building flow. Have fun.

public ThreeSharpWrapper(String awsAccessKeyId, String awsSecretAccessKey)

        {

            this.config = new ThreeSharpConfig();

            this.config.AwsAccessKeyID = awsAccessKeyId;

            this.config.AwsSecretAccessKey = awsSecretAccessKey;



            this.service = new ThreeSharpQuery(this.config);

        }

and then use it having the following methods:

/// Adds a bucket to an S3 account

public void AddBucket(String bucketName);



 /// Returns a string of XML, describing the contents of a bucket

public String ListBucket(String bucketName);



/// Adds a string to a bucket, as an object

public void AddStringObject(String bucketName, String keyName, String data);



/// Streams a file to a bucket as an object

public void AddFileObject(String bucketName, String keyName, String localfile);



/// Streams a file to a bucket as an object, with encryption

public void AddEncryptFileObject(String bucketName, String keyName, String localfile, String encryptionKey, String encryptionIV);



/// Gets a string object from a bucket, and returns it as a String

public String GetStringObject(String bucketName, String keyName);



/// Gets a file object from a bucket, and streams it to disk

public void GetFileObject(String bucketName, String keyName, String localfile);



/// Gets a file object from a bucket, streaming it to disk, with decryption

public void GetDecryptFileObject(String bucketName, String keyName, String localfile, String encryptionKey, String encryptionIV);



/// Copies an object from a source location to a destination location

public void CopyObject(String sourceBucketName, String sourceKey, String destinationBucketName, String destinationKey);



/// Generates a URL to access an S3 object in a bucket

public String GetUrl(String bucketName, String keyName);



/// Deletes an object from a bucket

public void DeleteObject(String bucketName, String keyName);



/// Deletes a bucket from an S3 account

public void DeleteBucket(String bucketName);



/// Changes the request payer value for the specified bucket

public String PaymentChange(String bucketName, PaymentChangeRequest.Payer payer);



/// Gets the request payer value for the specified bucket

public String PaymentGet(String bucketName);

The library is dead easy to use and most importantly it works (comparing to other S3 libraries I’ve found). Great work Joel!
You can download the solution zip from here or directly from the codeplex hosting the project here

1. remove any earlier backup dirs and create new empty one
2. create mysql dump for the applications you want to backup
3. create tar.gz of the entire home directory
4. create tar.gz of the apache director to preserve settings
5. create tar.gz of everything I’ve created earlier to place everything in a single file
6. ftp the file to a backup server

Lets start with the first task. Removing and creating dirs is pretty simple:

rm -Rf /root/temp_bckp

mkdir /root/temp_bckp

Creating mysql backup we can do the easiest using mysqldump utility. The command for this is:

mysqldump --user=your_db_user your_db_name > /root/temp_bckp/your_Db_name.sql --password=your_db_password

echo 'sql dump finished'

Once we got all dumps in place we can start compressing home and apache directories directory:

tar -zcvf /root/temp_bckp/home_bckp.tar.gz /home

echo 'tar of home finished'



tar -zcvf /root/temp_bckp/etcapache.tar.gz /etc/apache2/

echo 'tar of etc/apache finished'

Somwhere at the top of the script we store current date as a variable and we use it to name the final backup archive:

DATEX=`date +%d%m%y`

Final backup archive:

tar -zcvf /root/temp_bckp_$DATKA.tar.gz /root/temp_bckp

echo 'tar of all finished'

When we have all zipped together we are ready to send it over to the ftp backup server, I use ncftp utility which you can easily get on debian based distros using apt-get install ncftp or aptitude install ncftp.

ncftpput -u ftp_user -p ftp_password your-ftp-domain.com . temp_bckp_$DATKA.tar.gz

echo 'ftp finished'

For ftp server I personally use Linode services which are very cheap in the basic package, you can check their offers here

Complete shell script you can download from storage43 under this link
Happy backuping

Number 1. Google Analitycs

Number 2. Quantcast
Number 3. Compete

Number 4. Alexa

I guess there are many more and I’m still going blind. If anyone wants to share, the comments section is waiting.

1. Download the tool itself from sourceforge.net link,
2. Extract the zip file
3. Read the readme.txt
4. Check out your sources
5. Run ’svn log –xml -v > svn.log’ inside your project directory
6. Run java -jar statsvn.jar path_to_your_project_folder\svn.log path_to_your_project_folder
7. Wait
8. Go to the folder where statsvn.jar is and launch index.html
9. Feel guilty when you see no commits for a few days in a month

The reprots consists mostly of the diagrams and the table stating the developer of the month which I like the most as I’m the only one working on the project ))

Simply wonderful!