SET-570 Automate updating CCI worker VMs in Gitlab.

[RanabirChakraborty]

Issue: https://issues.redhat.com/browse/SET-570

it can do the following ->

• Clone your forked csb-jenkins-definition from gitlab.
• rebase it with changes with the upstream repo.
• Updated the newly formed image name
• create the PR

Zeus vars PR: https://gitlab.cee.redhat.com/jboss-set/zeus-vars/-/merge_requests/80

[RanabirChakraborty]

@spyrkob I check thoroughly but there is no way to create PR from a different branch other than the master branch using the command module. I even checked the git module but there is no way to send a PR. In my mind there are three solutions -

1. If we can get the admin access (or the credentials) then we can directly send the push request to csb-jenkins-definition and at the same time can reload Jenkins with the new changes. In this way, we can achieve full automation.
2. We can maintain a duplicate branch in csb-jenkins-definition which will be an exact copy of the master branch and can send the PR using that and we can merge it manually. [ Issue - eventually too many branches will form in the main repo]
3. Clone the personal fork repo and using that send the PR and we can merge it manually. [ Issue - Fork repo has to be there beforehand]

[spyrkob]

@RanabirChakraborty, thanks for the summary. I think option 3 sounds best - it should be a safe to assume a user has a fork if they're doing changes. And it allows for users without write permissions to main repo to still prepare the update

[spyrkob]

@RanabirChakraborty do you know if this molecule failure is related to the PR or something wrong with the env?

[RanabirChakraborty]

There is a recent change in the GitHub Ubuntu image, that's why molecule 5.0 is failing. Here is the listed issue - ansible/molecule#3883

The previous molecule[podman] will not work now. As a fix, we need to move from molecule[podman] to molecule-plugins[podman]. Logged a new SET issue here. I'm working on it.

[spyrkob]

LGTM