List of simple jobs returns: no job defined in config

[rkirimov]

Describe the problem

When I configure a list of simple jobs without parameters, it fails with no job defined in config: jenkins.jobs. Running with -show-config option returns

jenkins:
    host: https://jenkins.example.com
    username: my_user
    password: 123
    jobs: {}

config.yaml

jenkins:
  host: https://jenkins.example.com
  username: my_user
  password: 123
  jobs:
    JOB1:
    JOB2:

If I add parameters or trigger field, for example, the jobs are parsed correctly and I'm able to trigger the jobs.

I tried something like

jenkins:
  jobs:
    JOB1: {}
    JOB2: {}

But with the same result.

[brainexe]

ah...dejavu. we had the same issue when having jobs without parameters. I remember there are some restrictions or strange behavior inside the mapstruture which does not add empty elements in this case.

We added a dummy key there to make it work as a "temporary fix"...works since 3 years now 🤡

jenkins:
  jobs:
    SomeJenkinsJob:
      foo: bar

[rkirimov]

Thanks for confirming the possible workaround heh. I wonder if this PR has anything to do with this issue: mitchellh/mapstructure#183