Skip to main content

Jenkins [DSP2017 #06]


In this entry I want to introduce tool which should be used in each projects. It covers how to install and configure a simple job.


First of all I started from installation of jenkins in my local machine (Ubuntu). You can download installation package from official page or use jenkins wiki. As like always I met some problem:
 The following packages have unmet dependencies:
 jenkins : Depends: daemon but it is not installed


As a resolving of it I used command apt-get -f install and next apt-get upgrade.

Then we should be able see the page like below on address http://localhost:8080





After unlock and installation some pluggins we should be able to see something like below.






Next I added simple job which will check the repository and run command gradle -p nany-server test. The result is on an image below.

I think that few of us met with lost jobs definitions. What then? We need to define each job manually again. From my point of view the better option is to keep configurations of job as a file on version control. I think that one option can be Jenkins job DSL.


So lets do the same think with DSL. Our current job just check-out code and run command gradle -p nany-server test. The same job can be defined by script like here:






job('DSP-Nany') {
  scm {
    git {
      remote {
      github('SebJak/nanny_dsp')
      credentials('github_sjak')
      }
    }
  }

  triggers {
   scm('H/15 * * * *')
  }
  steps {
   gradle{
     useWrapper(false)
     gradleName('Gradle 3.5')
     tasks('test')
     switches('-p nany-server')}
   }
 }

We can put this code in our repository like here and define a job where this script file will be taken and run for define DSP-Nany job.

After run a defined job probably your receive error:



 
Processing DSL script dspNanyDSL.groovy
ERROR: script not yet approved for use
Finished: FAILURE

The solution of it is to approve the script in Manage Jenkins -> In-process Script Approval. Next build should work and the result should be a new job named DSP-Nany.



Thanks for reading :)

Comments

Popular posts from this blog

Types of tests [DSP2017 #04]

As a java developer with more than 3 years of experience I had opportunity of participating in few projects. To be honest only in a last one a testing strategy is on high level.  I encourage you for introduce and put more pressure on testing strategy during a delivery process. As with all new things the beginnings are difficult but I'm sure that it is worth. As almost testers know undermentioned pyramid I need to put it for people who have not seen it. In a big amount of projects we can meet this pyramid in inverted order. What can impact of quality of a system. For example when we have a lot of manual tests it is boring for users and sometimes they can be skipped what can missed bug. So in the lowest level we see the Unit tests and the count of this should be the bigger and on the highest level, there are manual tests. As we can expect the count should of them should be the lowest. A few words about each of them: Unit tests - should be quick and small. They check jus...

Oracle Certified Associate Java SE 8 Programmer I: Exam 1Z0-808 [DSP2017 #05]

  Hello and sorry for absence during last weeks. This time was very busy because I had to prepare myself for OCA certification. In this post I want to write few word about: what I've done how it looks what I will improve next time  I've read one book from beginning to the end. It was   OCA Java SE 8 Programmer I Certification Guide MALA GUPTA   I think that it is good book for gain knowledge about base java. There is a lot of examples, very detail description. Form point of exam just reading and making the tests is not enough. The test inside this book are not so easy but they don't cover real exam. Next books which were only source of mock tests: OCA / OCP Java SE 8 Programmer Practice Tests OCA: Oracle Certified Associate Java SE 8 Programmer I Study Guide: Exam 1Z0-808   The mocks in the first position are very easy and so short. In real exam the examples of code was so longer and requires more concentration. During the preparation I was...

How to start with Android development [DSP2017 #07]

In this part I want to show how I started with a first app. My previous experience with creating an Android application was about 4-5 years ago. I've created one or two simple applications during my studies and forgot about this topic. Today when I wanted to create a new app I needed to start from beginning. First of all I need to install tools: Android Studio (I use Intellij with Android extension). Android SDK - I used the sdkmanager but during Android Studio installation sdk should be installed. If you have 64 bits system you need to check: Required libraries for 64-bit machines . If you have installed all above tools you should be able to create simple Android project and run it on your phone. Yes, like always I met few problems with run the application on my phone. #1 The adb can not find my device. Solution : turn phone as MTP mode. 2# Error:Execution failed for task ':app:processDebugResources'. > com.android.ide.common.process.ProcessException:...