Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: Run GitHub actions on release-* branches #299

Closed
wants to merge 8 commits into from
Closed

Conversation

ckadner
Copy link
Member

@ckadner ckadner commented Jan 7, 2023

Motivation

When we create a new release we need the GitHub actions to run for

  • Lint
  • Unit test
  • FVT
  • Image build and push

Modifications

Update the Github workflow definitions to include any release-.. branches.

Result

The GitHub action run on PR and pushed to the release branch.

As can be seen in this PR targeting the release-0.10 branch:
#298

/cc @njhill @rafvasq

Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
@ckadner
Copy link
Member Author

ckadner commented Jan 7, 2023

Oh, interesting. Seems like the FVT got triggered even though there are no functional changes that should warrant that.

Maybe we need to update the path-ignore expressions 🤔

@ckadner
Copy link
Member Author

ckadner commented Jan 7, 2023

Oh, interesting. Seems like the FVT got triggered even though there are no functional changes that should warrant that.

Maybe we need to update the path-ignore expressions 🤔

Ah, nevermind. The FVTs want to be run when the FVT workflow file gets changed :-)

@ckadner ckadner changed the title Run GitHub actions on release-* branches test: Run GitHub actions on release-* branches Jan 7, 2023
ckadner and others added 2 commits January 8, 2023 14:01
#### Motivation
Fix vulnerabilities in the ModelMesh Controller image.

#### Modifications
1. Remove dependencies to any packages in the runtime. 
2. Updated Go version to the latest version.

#### Result 
The feature is functionally working, I have tested it on my own cluster.

Signed-off-by: JasmondL <Jasmond.Ming.Quan.Loh@sap.com>

Co-authored-by: JasmondL <Jasmond.Ming.Quan.Loh@sap.com>
Co-authored-by: Jasmond L <120363110+JasmondL@users.noreply.github.com>
* release: Update image tags for v0.10.0-rc0

Also update KServe go dependency to v0.10.0-rc1

* Update release process doc

* Update links in release process doc

* Restore RELEASE_PROCESS.md

Will update it in main after this release is done

* Update go.sum

Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
#### Motivation

Missed to update on doc in previous round.

#### Modifications

Edit the `docs/quickstart.md` file, updating the `RELEASE` variable in the "Get the latest release" section to the new release branch name.

#### Result

Correct version of release branch in Quickstart guide

/cc @njhill 
/assign @njhill 


Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
@kserve-oss-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ckadner, rafvasq
To complete the pull request process, please assign njhill after the PR has been reviewed.
You can assign the PR to them by writing /assign @njhill 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:

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

#### Motivation

Quickstart should use namespace scope mode for simplicity. In current version there is an inconsistency wrt `ServingRuntimes` vs `ClusterServingRuntimes`.

#### Modifications

- `docs/install/install-script.md` (correct a typo)
- `docs/quickstart.md` (change install command for ns scope mode and add missing `torchserv` serving runtime)
- `scripts/install.sh` (fix `sed -i` commands)

#### Result

Quickstart install steps work like a charm again :-)

#### TODOs

Once merged into `main`, we will need to update the `release-0.10` branch as well

---

/cc @njhill
/assign @njhill

Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
(cherry picked from commit fbd8c62)
@ckadner ckadner added the test testing related bugs and fixes label Jan 11, 2023
@ckadner
Copy link
Member Author

ckadner commented Jan 11, 2023

I will open a new PR with just the workflow file changes. The unrelated merge commits should not be in here and might overwrite changes that were done after this PR was created.

@ckadner
Copy link
Member Author

ckadner commented Jan 11, 2023

New (and improved) PR: #310

kserve-oss-bot pushed a commit that referenced this pull request Jan 11, 2023
#### Motivation

When we create a new release we need the GitHub actions to run for 
- Lint
- Unit test
- FVT
- Image build and push

#### Modifications

Update the Github workflow definitions to include any `release-..` branches.

#### Result

The GitHub action run on PR and pushed to the release branch.

As can be seen in this PR targeting the `release-0.10` branch:
#298

---

**Note**: same (intended) changes as in PR #299 -- but without the merge commits

/cc @njhill @rafvasq 
/assign @njhill 

Signed-off-by: Christian Kadner <ckadner@us.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
test testing related bugs and fixes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants