Support actions in publishChecks Step

[XiongKezhi]

Solve issue: #74

[codecov]

Codecov Report

Merging #85 (76fc732) into master (24dcafe) will increase coverage by 0.38%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##             master      #85      +/-   ##
============================================
+ Coverage     86.82%   87.21%   +0.38%     
- Complexity      140      142       +2     
============================================
  Files            16       16              
  Lines           630      649      +19     
  Branches         49       49              
============================================
+ Hits            547      566      +19     
  Misses           65       65              
  Partials         18       18              

Impacted Files	Coverage Δ	Complexity Δ
...va/io/jenkins/plugins/checks/api/ChecksAction.java	100.00% <100.00%> (ø)	5.00 <1.00> (ø)
...enkins/plugins/checks/steps/PublishChecksStep.java	90.47% <100.00%> (+2.78%)	19.00 <2.00> (+2.00)

---

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 24dcafe...05e909c. Read the comment docs.

[timja]

shouldn't there be some docs updates? or help file updates?

[timja]

Can you try avoid force pushing while under review please, it makes it harder for me to tell what changed so I have to review from the beginning

[timja]

is this still needed? I think you adjusted the implementation?

[XiongKezhi]

no, still needed, since we still add new field to PublishChecks step.

[INFO] API problems found.
[INFO] If you're using the semver-ignore extension, update your module's version to one compatible with the current changes (e.g. mvn package revapi:update-versions). If you want to explicitly ignore these changes or provide justifications for them, add the json snippets to your Revapi configuration for the "revapi.differences" extension.

{
  "code": "java.field.serialVersionUIDUnchanged",
  "old": "field io.jenkins.plugins.checks.steps.PublishChecksStep.serialVersionUID",
  "new": "field io.jenkins.plugins.checks.steps.PublishChecksStep.serialVersionUID",
  "serialVersionUID": "1",
  "justification": "ADD YOUR EXPLANATION FOR THE NECESSITY OF THIS CHANGE"
  /*  "package": "io.jenkins.plugins.checks.steps",
  "classQualifiedName": "io.jenkins.plugins.checks.steps.PublishChecksStep",
  "classSimpleName": "PublishChecksStep",
  "fieldName": "serialVersionUID",
  "elementKind": "field",
  "oldArchive": "io.jenkins.plugins:checks-api:hpi:1.5.0",
  "oldArchiveRole": "primary",
  "newArchive": "io.jenkins.plugins:checks-api:hpi:1.6.0-SNAPSHOT",
  "newArchiveRole": "primary",
  "breaksSemanticVersioning": "true",
  */
},

[XiongKezhi]

Can you try avoid force pushing while under review please, it makes it harder for me to tell what changed so I have to review from the beginning

Sorry, my bad 😅