Add ODH release workflow

[oksanabaza]

What this PR does / why we need it:

Adding a release workflow in the ODH fork of Training Operator

Which issue(s) this PR fixes (optional, in Fixes #<issue number>, #<issue number>, ... format, will close the issue(s) when PR gets merged):
Fixes #

https://issues.redhat.com/browse/RHOAIENG-13631

This workflow has been tested locally using my personal GH token here

Checklist:

• Docs included if any changes are user facing

[Fiona-Waters]

Looks good. Just a couple of small comments.

[coveralls]

Pull Request Test Coverage Report for Build 11439915191

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 10 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.1%) to 42.785%

---

Files with Coverage Reduction	New Missed Lines	%
pkg/controller.v1/mpi/mpijob_controller.go	10	80.48%

Totals
Change from base Build 11236886062:	-0.1%
Covered Lines:	3745
Relevant Lines:	8753

---

💛 - Coveralls

[Fiona-Waters]

/lgtm

[Fiona-Waters]

/lgtm

[ChughShilpa]

@oksanabaza
Did you try the run this workflow manually? Asking to make sure the github token GITHUB_TOKEN: ${{ secrets.CODEFLARE_MACHINE_ACCOUNT_TOKEN }} works effectively

[oksanabaza]

Hey @ChughShilpa , this is a good point, I haven't as I need a token to test it

[ChughShilpa]

Hey @ChughShilpa , this is a good point, I haven't as I need a token to test it

You can test it by adding a token in your fork and then try running the workflow

[oksanabaza]

@ChughShilpa I tested the workflow with my personal GitHub token in my fork, and it worked fine. However, when I tried to run the workflow in the fork using the CODEFLARE_MACHINE_ACCOUNT_TOKEN from the original repository, I got a 404 error. It seems that the CODEFLARE_MACHINE_ACCOUNT_TOKEN may not have the right permissions to be used in forks

[ChughShilpa]

@ChughShilpa I tested the workflow with my personal GitHub token in my fork, and it worked fine. However, when I tried to run the workflow in the fork using the CODEFLARE_MACHINE_ACCOUNT_TOKEN from the original repository, I got a 404 error. It seems that the CODEFLARE_MACHINE_ACCOUNT_TOKEN may not have the right permissions to be used in forks

Yes right, CODEFLARE_MACHINE_ACCOUNT_TOKEN doesn't work in fork repos

[ChughShilpa]

@ChughShilpa I tested the workflow with my personal GitHub token in my fork, and it worked fine. However, when I tried to run the workflow in the fork using the CODEFLARE_MACHINE_ACCOUNT_TOKEN from the original repository, I got a 404 error. It seems that the CODEFLARE_MACHINE_ACCOUNT_TOKEN may not have the right permissions to be used in forks

Just FYI, it is good to add the workflow link which you ran manually in the description of the PR stating how you tested this PR

[ChughShilpa]

/lgtm

[oksanabaza]

thanks @ChughShilpa, I will update the description

[Fiona-Waters]

/lgtm
/approve