The post title is the message I see when looking at the ‘workflows’ section of the ui having added my fork of a project which already has a working v2 config. Why is the config’s ‘workflows:’ section not used / or ignored?
Builds fail with:
- Cannot find a job named
buildto run in the
jobs:section of your configuration file.
If you expected a workflow to run, check your config contains a top-level key called ‘workflows:’
but then clearly visible under the online UI’s configuration tab for the failed build is:
workflows: version: 2 build_and_test: jobs:
…so it appears to using the expected config.yml at least, just ‘ignoring’ this part.
Again, this config is in a fork of an established os project where the workflows appear to be working just fine, so why not in my repo I wonder? Any ideas please?