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

✨ e2e tests for the latest release #1967

Merged
merged 1 commit into from
Mar 28, 2024

Conversation

effi-ofer
Copy link
Contributor

Summary

Add e2e tests for the latest release.

Related issue(s)

Fixes #1590

@kcp-ci-bot kcp-ci-bot added dco-signoff: yes Indicates the PR's author has signed the DCO. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Mar 27, 2024
@effi-ofer effi-ofer added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 27, 2024

- name: show workstatuses
if: always()
run: kubectl --context imbs1 get workstatuses -A -o yaml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see less red in GitHub when there is a terminal linebreak.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean that red symbol that resembles a do not enter sign? Adding a terminal linebreak avoids that symbol in github?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

added a blank line.

@effi-ofer
Copy link
Contributor Author

Note to @MikeSpreitzer - I am not sure how to go about testing this? I would like to try the implementation of the action workflow in this PR as well as a variant of it that uses the following trigger:

on:
  release:
    types: [published]

@effi-ofer effi-ofer removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 28, 2024
@effi-ofer
Copy link
Contributor Author

Note to @MikeSpreitzer - I am not sure how to go about testing this? I would like to try the implementation of the action workflow in this PR as well as a variant of it that uses the following trigger:

on:
  release:
    types: [published]

Tested locally on my fork by merging into main and then creating a release named 'release-mike'.

Comment on lines 12 to 14
paths-ignore:
- 'docs/**'
- '**/*.md'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect that this may cause us problems by suppressing activation for a commit that only changes docs. It is not uncommon for the last commit in a release to be one that only changes docs (e.g., fixing self-reference(s)).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You're right. And my bad for letting this one slip in.


- name: Run test
env:
TEST_FLAGS: ${{ github.event.inputs.testFlags }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is broken and unused stuff copied from some other workflow, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean the TEST_FLAGS right? I removed them now.


- name: Run test
env:
TEST_FLAGS: ${{ github.event.inputs.testFlags }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Junk

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed

@effi-ofer effi-ofer force-pushed the release-test branch 2 times, most recently from 46f37be to 40cffd5 Compare March 28, 2024 18:37
Signed-off-by: Effi Ofer <effi.ofer@gmail.com>
Copy link
Contributor

@MikeSpreitzer MikeSpreitzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve
Thanks!

@kcp-ci-bot kcp-ci-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 28, 2024
@kcp-ci-bot
Copy link
Contributor

LGTM label has been added.

Git tree hash: 35f4b99d8b01b724cdb2e67674049a150393d0e9

@kcp-ci-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MikeSpreitzer

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

The pull request process is described 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

@kcp-ci-bot kcp-ci-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 28, 2024
@kcp-ci-bot kcp-ci-bot merged commit f3ea8f3 into kubestellar:main Mar 28, 2024
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has signed the DCO. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Add CICD tests for user examples running from images
3 participants