static slaves: Perform global-jjb init 50/2250/4
authorAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Fri, 21 Feb 2020 12:31:15 +0000 (13:31 +0100)
committerAlexandru Avadanii <Alexandru.Avadanii@enea.com>
Sun, 23 Feb 2020 16:21:30 +0000 (17:21 +0100)
commitdd6df9e26b1af9f6f2a66742d6b78acdb50451f7
tree277481d8dbd271a2be8d1d0ceabe1f3ee1d55460
parentbb1b3d84cda3e7c4bf51427c0d07ef5ba78688de
static slaves: Perform global-jjb init

global-jjb was recently bumped to 0.51, which assumes
jenkins-init-scripts were already executed on the build slave
(e.g. by sourcing ~jenkins/lf-env.sh), which is always true for
Openstack instances dynamically spawned by Jenkins, but not yet
for static slaves like AArch64 dev/build/baremetal PODs.

Add a new job, triggered on ci-management gerrit merge (only if
global-jjb reference is changed) that executes the jenkins-init-scripts
similar to dynamic slaves initialization.

NOTE: Since jenkins-init-scripts are not fully idempotent, some
actions (e.g. id_rsa keypair generation) are executed even though
they are not mandatory (for the id_rsa keypair this means the
private/public keys will be forcefully regenerated each time this new
job runs).

Change-Id: I62433a45c7966aed1d1184fa60e87ee4211996e4
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
jjb/akraino-templates/akraino-jjb-templates.yaml
jjb/ci-management/static-slaves-ci-jobs.yaml [new file with mode: 0644]