Make PipelineRun support parameterized trigger

[JohnNiang]

What this PR dose

Make PipelineRun support parameterized trigger.

Why we need it

For now, we can use this feature to test against kubesphere/ks-devops#210. In the future, we can trigger a parameterized Pipeline conveniently using this CLI.

How to use it

ks pip run -b -p demo-pipeline -n default -P name=johnniang,debug=true

[JohnNiang]

/kind feature

[LinuxSuRen]

Please check the following erorrs:

➜  bin git:(feat/pipelinerun-with-param) ./ks pip create
? Please select workspace name: test
? Please select project name: test
? Please select : simple
? Please input the Pipeline name ridgemoor
➜  bin git:(feat/pipelinerun-with-param) ./ks pip run
? Please select workspace name: test
? Please select project name: testlrjmw
? Please select pipeline name: ridgemoor
Usage:
  ks pipeline run [flags]

Flags:
  -b, --batch                       Run pipeline as batch mode
  -h, --help                        help for run
  -n, --namespace string            The namespace of target Pipeline
  -P, --parameters stringToString   The parameters that you want to pass, example of single parameter: name=value (default [])
  -p, --pipeline string             The Pipeline name that you want to run

failed create PipelineRun, error: PipelineRun.devops.kubesphere.io "ridgemoor6wpkt" is invalid: spec.parameters: Invalid value: "null": spec.parameters in body must be of type array: "null"

I guess that you forget to take care of those Pipelines which does not have parameters.

[JohnNiang]

hi @LinuxSuRen , I've noticed the issue. If the problem is empty, there will be a problem. Refer to the BlueOcean RESTful API.

[LinuxSuRen]

hi @LinuxSuRen , I've noticed the issue. If the problem is empty, there will be a problem. Refer to the BlueOcean RESTful API.

I didn't get your point.

[JohnNiang]

My bad. Please see below:

I've noticed the issue. If the parameters are empty, there will be a problem. Refer to the BlueOcean RESTful API.

[LinuxSuRen]

I've noticed the issue. If the parameters are empty, there will be a problem. Refer to the BlueOcean RESTful API.

So, how to fix that problem? Not intend to fix it?

[JohnNiang]

So, how to fix that problem? Not intend to fix it?

Currently, we have to pass at least one parameters explicitly.

[LinuxSuRen]

Currently, we have to pass at least one parameters explicitly.

Must pass a parameter even if there are no parameters in a Pipeline? I don't think this is acceptable. This is a breaking change.

[JohnNiang]

Must pass a parameter even if there are no parameters in a Pipeline? I don't think this is acceptable. This is a breaking change.

Agree. I've resolved the breaking change. Please have a look at it.

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@25b55c3). Click here to learn what that means.
The diff coverage is n/a.

❗ Current head f2397fc differs from pull request most recent head 1c0c0bd. Consider uploading reports for the commit 1c0c0bd to get more accurate results

@@           Coverage Diff            @@
##             master    #187   +/-   ##
========================================
  Coverage          ?   8.84%           
========================================
  Files             ?      32           
  Lines             ?    1311           
  Branches          ?       0           
========================================
  Hits              ?     116           
  Misses            ?    1185           
  Partials          ?      10           

Flag	Coverage Δ
unittests	8.84% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 25b55c3...1c0c0bd. Read the comment docs.