[CI] schedule workflow support workflow dispatch

[liangyuanpeng]

What type of PR is this?

/kind cleanup
/kind failing-test

What this PR does / why we need it:

Let schedule workflow support call normal and we should need the all of job result, so do not fail-fast for APIServer compatibility, Run all of workflow job for all of version.

It's all failed in my fork repo of karmada.

Which issue(s) this PR fixes:
Releated: #4111

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[karmada-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign rainbowmango after the PR has been reviewed.
You can assign the PR to them by writing /assign @rainbowmango in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[liangyuanpeng]

/assign @RainbowMango

[liangyuanpeng]

Run workflow once immediately would be great after this PR is merged.

lan@lan:~/repo/git$ export GITHUB_TOKEN=123
lan@lan:~/repo/git$ cd karmada
lan@lan:~/repo/git/karmada$ gh workflow run -R karmada-io/karmada
? Select a workflow  [Use arrows to move, type to filter]
> APIServer compatibility (ci-schedule-compatibility.yaml)

Choose the APIServer compatibility and run it.

[codecov-commenter]

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (ff433ce) 53.50% compared to head (a3c9d4a) 53.49%.
Report is 4 commits behind head on master.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4115      +/-   ##
==========================================
- Coverage   53.50%   53.49%   -0.01%     
==========================================
  Files         234      234              
  Lines       23281    23281              
==========================================
- Hits        12457    12455       -2     
- Misses      10143    10145       +2     
  Partials      681      681              

Flag	Coverage Δ
unittests	53.49% <ø> (-0.01%)	⬇️

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

see 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[liangyuanpeng]

@RainbowMango

Do you have any concerns about this PR? If you don't want to be able to manually call these two workflows currently, then I think at least APIServer compatibility should not fail quickly, and we need to know all the results, Remind me if i missed something,Thanks,

[jwcesign]

at least APIServer compatibility should not fail quickly

+1

[RainbowMango]

LGTM

[RainbowMango]

The workflow_dispatch can trigger the workflow manually. Does that mean all developers can trigger the workflow at anytime?

[RainbowMango]

Do you have any concerns about this PR? If you don't want to be able to manually call these two workflows currently, then I think at least APIServer compatibility should not fail quickly,

Yes, it makes sense to me that let the scheduled workflow continue to run and avoid canceling due to other job failures.
But manually triggering the workflow is concerning.

[RainbowMango]

kindly ping @liangyuanpeng

[liangyuanpeng]

Hi @RainbowMango I have move the change of fail-fast: false to #4238 and there are fix a problem of timeout.

I want to keep this PR is open and i think let the workflow support workflow dispatch still relevant. Because I have done some exploration on combining this scheduled task with prow, I hope I will have an update on this aspect soon.