-
Suggestion
-
Resolution: Unresolved
-
None
Currently we can't pass pipeline variables for custom pipelines to schedule jobs, so if that functionality can be added that would be great.
If that we can do by with the API only like below:-
curl -X POST -is -u UID:PWD \
-H 'Content-Type: application/json' \
https://api.bitbucket.org/2.0/repositories/repo1/slack/pipelines_config/schedules/ \
-d '
",
"enabled":true,
"target":{
"type":"pipeline_ref_target",
"ref_type":"branch",
"ref_name":"test",
"selector":
,
"variables": [
]
},
"cron_pattern":"15 * * * * ? *",
"created_on":"2020-07-23T15:17:10.661Z",
"updated_on":"2020-07-23T16:32:11.13Z"
}'
- mentioned in
-
Page Failed to load
[BCLOUD-20328] Pass Pipeline Variables to schedule jobs
This would be really nice to have, I could just change two variables in the schedule instead of copying half of the pipeline... There is already the variable assignment form when running the pipeline manually, why is it not in the schedule dialog too?
Tuning the default values to scheduled runs is awkward and possibly not viable (if different schedules need different values).
This is a must have feature. How many lines in the pipeline can be saved by not requiring to create another job for the same purpose but with different variables.
This is a must have feature. It is much easier and safer to pass variables to schedules than actually change bitbucket-pipelines.yml or even the scripts to use default values. If you run by mistake the job / script with default values then you may create undesired results.
My company was thinking about moving from Jenkins to Bitbucket and we saw this feature isn't available. Voting!
Guys, it's been almost three years and you still can't add this feature for scheduled custom pipelines. Is it really that difficult to implement? Why is it already available for regular custom pipelines? Why isn't there an implementation of this functionality for scheduled pipelines? So many questions and so few answers... You're falling further behind the competition of other CI/CD solutions. Don't you realize it?
+