kiegroup / kie-ci

Various scripts for use with our Jenkins

KIE-CI (former kie-jenkins-scripts)

This repository is used to store KIE either provisioned machines ansible configuration and job DSLs for jenkins.

Provisioned Machines ansible configuration

We have different kind of machines:

• KIE RHEL
• smee client
• verdaccio service

To test ansible playbooks

Just execute

docker run --name ansible-managed-node --privileged -p 2222:22 -d -it chusiang/ansible-managed-node:centos-7 /usr/sbin/init
ansible-playbook -e ansible_ssh_pass=root -e encrypted_password=root_pass -e rhel_version=7 kie-rhel.yml

kie-ci's Issues

Add jobs for new repo jbpm-work-items

We need to create jobs for https://github.com/kiegroup/jbpm-work-items please.

Replace internal URLs with variables

There are few places in the jenkins-slaves dir where we use internal URLs. It would be preferable to replace those with variables which are then set from Jenkins/local env when actually running the packer/ansible scripts.

Mark the builds as unstable (instead of failed) when there are checkstyle violations

The deploy and PR builds will currently fail (with a result 'red') in case there are checkstyle violations. As discussed with @hasys this is probably too strict. We should just mark the build as unstable instead and let it finish, so that we have also the test results.

A new jenkins job is kindly requested for drlx-parser repository in kiegroup

Store commitIds of repositories being build as part of the PR builds

It may be sometimes useful to see the specific list of commits the PR was build from (e.g. all the upstream repos and all the downstream repos). This info could be store in a simple text file and archived for the build.

Add jobs for new kie-soup repo

We will need deploy and PR jobs for this new repo: https://github.com/kiegroup/kie-soup. It is supposed to be built before uberfire.

Deploy new SNAPSHOTs only if there was a change in git repo

Currently the deploy job will always deploy new SNAPSHOTs, even in cases when the code actually did not change (e.g. the build is started by an upstream job). We should investigate if it is possible to deploy the artifacts only in case the SCM changed. This would speed-up the jobs a bit in most cases and would save quite a lot of bandwidth.

Replace Maven jobs with Freestyle jobs

The standard 'deploy' jobs are still using the Maven job. It adds a lot of hooks into the build and sometimes even changes the way a build is being executed. This sometimes leads to an unexpected failures, where the build works fine with just "mvn clean install", but fails in the job. These jobs need to be replaced with the Freestyle jobs, which do the Maven build exactly as expected. We can not simply update the config, Jenkins won't accept that. The old jobs first need to be deleted and new ones then re-created. We will loose the build history, but that's not a big issue.

List of issues with the Maven job type:

• it partially ignores the MAVEN_OPTS settings. When parsing the POMs is simply does it as part of the slave.jar process. This results in OOME for big projects.