Getting in touch with Liquibase Migration Tool

Have you experienced a situation, when you had a database in your system, and you needed to migrate all it’s structure, to, say, another database ? Of course, you faced such situations and, of course, you manually copied all data from one server instance to another ? Something familiar ? Alternative approach How about idea of writing high-level instructions on how to deal with your database ? For example, you say “Create this table, and add this column , and insert this index, …” only once and all subsequent times you will just reuse this instructions ? Such idea is called “Database migration tool”, there is several migration frameworks for java, but I will show how to work with single tool - liquibase. The idea is that you store this instructions in xml files and when you run your liquibase migration script for the first time, liquibase will create two tables in your database databasechangelog and databasechangeloglock, where all information about running migrations kept. Say, you have only one migration changeset To run such script I use maven, here is pom.xml,as usual mvn liquibase:update If you wish, you can run liquibase from command line, the only thing you need is...

How to integrate Jenkins with Bitbucket

Recently I had an issue with integrating Jenkins CI with Bitbucket CVS. My goal was to trigger jenkins to start running job, when commit to bitbucket will be pushed. Steps I made to made jenkins trigger job: Install Bitbucket plugin Set the Jekins job’s Build trigger to Poll SCM, but do not specify a schedule Create a github post-receive trigger to notify the URL http://yourserver/git/notifyCommit?url= example[email protected]:nick/project.git This will tell Jenkins to trigger whenever code in bitbucket will be changed. Note, that Jenkins will check whether changes were made and will start only in case of new changes in repository.

Gatling integration tool - making more flexibility

I recently had a chance to investigate how to increase flexibility of my integration test, written on gatling and scala. I have already written around 50 test cases, and I need couple of improvements: Be able to change url of my web service. By default, it should run on localhost, but as soon as I will configure continuous delivery, I will need to change web service url to some remote ip. For that needs I am planning to use maven preferences. More precise configuration of my setup function. By this time, I had no assertion strategies and I was confused that my tests go green even if some test case failed. Dynamic web service url I was hoping that gatling has something like Spring has - placeholders, but it occurs that the only way I can get property from maven is by system property val host = System.getProperty(“”) You also need to add additional configuration on your gatling plugin in maven <jvmArgs> <jvmArg>${integration.url}</jvmArg> </jvmArgs> Where ${integration.url} is taken from maven module properties Here is full pom.xml After this modification, You will be able to change your basicUrl mvn test -Dintegration.url=http:${REMOTE_IP}:8080/…. and my test scenarios will run on dedicated server. Such...

Java, Jenkins and UnsatisfiedLinkError

Today I experienced issue with Jenkins - After some system modifitcation I received failed build with message Caused by: java.lang.UnsatisfiedLinkError: > /home/${user}/tools/jdk1.7.0_71/jre/lib/i386/xawt/ cannot open shared object file: No such file or directory So I search in the internet and found the solution sudo apt-get install libxrender-dev sudo apt-get install libxtst-dev I’m really not sure what it was, I guess it could be because I accidentally installed openjdk instead of oracle jdk. In fact, It helped me.

Setting up continuous delivery with Jenkins, Maven and Tomcat

Sometimes it’s hard for me to deploy your application each time when you chang something in your code. Truly, if it is important for you to deploy your application at least twice per day, and the process of deployment will take up to 10 minutes, then it will result to +- 200 minutes per month and 2400 minutes per year!!! That’s almost 2 days. So, instead of doing deployment each time manually, I propose you to do that with your Continuous Integration tool. The process of continuous deploy is called continuous delivery, which includes Build -> Deploy -> Test -> Release. Required tools In this article you will need a couple of tools to succed Continuous Integration tool. It is important to trigger every change you made in your code. For that needs you can use Jenkins continuous integration server. Build tool. It is a common knowledge that nowadays we don’t need to build our apps manually, now we build them by ready tools, that simplifies our development process. I will be using maven for that.It helps me to manage my dependencies, split my application into several modules, has many plugins, can check the quality of my code. Application server....