Mostly, no-one is doing that - it is an automatic feature of the board, presumably to prevent necroposting. If you see an old post that is closed, you can create a new post and link to the old one.
The /// looks suspect to me. Are there meant to be two null/empty values in here?
@mt-micky - one thing to check first is whether you turn on the “build processing” feature under “Advanced Settings” on your project settings page – that’s required for the new build triggering endpoint. If that’s the issue, we can make the error message better. If that’s not the issue, let us know.
p.s. Whatever is documented over here does not tell us where to specify the workflow and looks nothing like the commands people are using in this thread.
All my metaphors today take on a Harry Potter theme. For example, if something unpleasant jumps out at me and catches me by surprise, I use humour to defeat it, and send it scurrying away. That’s why there are no Boggarts in this thread.
Configuration errors: 2 errors occurred:
* Configuration version 2.1 requires the "Enable Build Processing" project setting. Enable Build Processing under Project Settings -> Advanced Settings. In order to retrigger build processing, you must push a new commit.
* Cannot find a job named `build` to 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:'
version: 2.1 is set.
“Enable Build Processing” is enabled.
build exists under jobs:.
If I give a workflow name it errors just the same. (including still talking about build job rather than the workflow name)
For a version 2.1 project, using orbs and workflows.
https://circleci.com/api/v1.1/project/:vcs/:username/:repo/build, passing {"branch":"branchname"} as payload works as expected.
https://circleci.com/api/v1.1/project/:vcs/:username/:repo/tree/:branch, passing {"build_parameters":{"VAR":"true"}} doesn’t work, fails with the exact same error as @yellow encountered.
This seems to happen because my configuration is not being processed: if I navigate to the “Configuration” tab, I see that my orbs haven’t been resolved.
The reason I can’t use the former request is that I need to provide a custom environment variable to my workflow but that’s not supported.
The latter form does support it, but it doesn’t seem to process my configuration before running.
My specific use case is that I want to trigger a subset of my workflow.
I could declare another workflow in my configuration, just like I do for scheduled workflow runs, but there’s no API to trigger a specific workflow, I can only trigger my main workflow from an API.
My attempted workaround was to pass an environment variable and abort early on steps I don’t want to run, which is very rudimentary but would work given the current API constraints.
That’s why there are no Boggarts in this thread.