Fix: Update submodules in jjb-deploy-job 75/72775/2
authorVratko Polak <vrpolak@cisco.com>
Tue, 2 Apr 2024 12:31:49 +0000 (14:31 +0200)
committerVratko Polak <vrpolak@cisco.com>
Tue, 2 Apr 2024 12:31:49 +0000 (14:31 +0200)
commit15d63bded80dd79040bb00085c6194fa8adbd1de
treeb83f1567dd22e2fae386eac5ddf77fdd83dfc359
parente8f821fc46b51176797f91b00b4fdc8a193c648b
Fix: Update submodules in jjb-deploy-job

The jjb-deploy-job can be used to test upgrades
in ci-management related repositories.
Those contain submodules, e.g. global-jjb.

The parent way to checkout the change under test
does not update the submodules,
so the job uses a combination of unmerged main repo
with current master HEAD submodules.
That is unhelpful and dangerous.

This change adds a command
to update the submodules after checkout,
so they match the commit under test.

In the Issue field I am pointing
to otherwise unrelated issue
that prompted me to start verifying
submodule upgrades in Sandbox.
That is because I cannot find a way
to open a new ticket in:
https://jira.linuxfoundation.org/projects/RELENG/issues

Issue: RELENG-5184
Change-Id: I407ccf86e404bd01675439bb4df8c85a804267bc
Signed-off-by: Vratko Polak <vrpolak@cisco.com>
shell/jjb-deploy-job.sh