# molecule job refactorings

Summary of discussions made with rfolco around ci-config molecule jobs.

Note about action items: they are supposed to implemented gradually, job by job.

# First POC job

The first job that already uses this newer setup is `mol-promoter`:

* [build history](https://review.rdoproject.org/zuul/builds?job_name=mol-promoter)
* [declaration](https://github.com/rdo-infra/ci-config/blob/master/zuul.d/jobs-mol.yaml)
* [periodic definition](https://github.com/rdo-infra/ci-config/blob/master/zuul.d/layout.yaml#L61-L63)

# Action items
* move all molecule scenarios to repository ./molecule
* convert all jobs not based on "mol" job to inherit from them
* Periodic mol jobs are to be defined in the same location as their check and gate ones, not in other repos (rdo-jobs). Cross-repo dependencies hinders refactoring
* Assure voting is never specified in job declaration,
and is only accepted in definition (gate/check/...)

# Reasoning

* Given a job name `mol-foo`, developer would be sure it can run the same scenario locally using `molecule test -s foo`
* Removing `default` scenario as it proved to cause confusions

# Current changes (in merge order)

* https://review.rdoproject.org/r/#/c/28455/ - remove rdo-tox-molecule-ci-config jobs
* https://review.rdoproject.org/r/#/c/28454/ - add mol-get_hash