we have a cli tool that ulitimately uses a url like :
function getPipelineUrl({ user, vcs, repo }) {
return `https://circleci.com/api/v2/project/${vcs}/${user}/${repo}/pipeline/`;
}
// gets called with cli flags like --user, --vcs, --repo, --token etc.
we end up calling it like :
- reckon/trigger_workflows:
branch: <<pipeline.git.branch>>
commit_ref_stash: ./development_commit
enable_workflow_parameter: enable_development_build
packagename_parameter: build_packagename
packageroot_parameter: build_packageroot
commitref_parameter: build_commitref
tag_pattern: "^(@somereponame.*)@v.*-dev$"
vcs_type: <<pipeline.project.type>>
requires:
- reckon/process_changesets
which ends up calling :
yarn deploy-tags
--token=${<<parameters.token>>}
--user=${<<parameters.user>>}
--repo=${<<parameters.repo_name>>}
--vcs=<<parameters.vcs_type>>
--tags.pattern="<<parameters.tag_pattern>>"
--workflow.params.enable=<<parameters.enable_workflow_parameter>>
--workflow.params.package=<<parameters.packagename_parameter>>
--workflow.params.root=<<parameters.packageroot_parameter>>
--workflow.params.commit=<<parameters.commitref_parameter>>
heres some parameter specs for this job:
token:
description: What is the VCS for this project
type: env_var_name
default: CIRCLE_TOKEN
repo_name:
type: env_var_name
description: The repo to trigger the workflow on
default: CIRCLE_PROJECT_REPONAME
user:
description: Username for the Project
type: env_var_name
default: CIRCLE_PROJECT_USERNAME
vcs_type:
description: What is the VCS for this project
type: string
default: ''
These all get filled in nicely.
but for the last two days, a POST request with a correct CIRCLE_TOKEN
to https://circleci.com/api/v2/project/${vcs}/${user}/${repo}/pipeline/
results in a 404 project not found.
Urgently need assistance here.