1. Jenkins docker-pipeline

    in a previous blog post I talked about setting up a dockerized jenkins master/slave setup and setting up a private docker registry using nexus.

    The next thing on the roadmap was to use this jenkins setup to actually build new docker images for specific software. Before going to the different teams and talking how they now build their software and how this could be done using this new containerized setup I setted up a new jenkins job.

    This jenkins job will build a generic jenkins slave docker container which will be used by the jenkins master to build some …

  2. Jenkins gradle build succeeded with failure

    Today we bumped into an interesting issue in the jenkins builds of some android based applications. The gradle commands succeeded but then suddenly failed the build with this most cryptic message ever:

    Total time: 1 mins 20.492 secs
    FAILURE: Build failed with an exception.
    * What went wrong:
    Already finished
    * Try:
    Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
    [Pipeline] }

    Since this came out of nowhere without any modification on the build servers we where flabbergasted since the builds ran fine on our local machines.

    So …

  3. Dockerized jenkins master/slave setup

    started at a new customer we were looking for a more flexible way of having jenkins spinning up slaves on the fly. This in a way a slave is only started and consuming resources when a specific job is running. That way those resources could be used more efficient.

    Also the fact that developers could take control over their build servers by managing the Dockerfiles themselves is a great advantage too. But that's for a later phase. Let's start at the beginning.

    For the docker host a CentOS 7 server has been provisioned and prepared to run the docker daemon …

Page 1 / 1