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

Bump up Kepler-action version #55

Closed
vprashar2929 opened this issue Jul 6, 2023 · 8 comments
Closed

Bump up Kepler-action version #55

vprashar2929 opened this issue Jul 6, 2023 · 8 comments

Comments

@vprashar2929
Copy link
Contributor

Since we added support for Microshift to Kepler-action. In order for Kepler repo and Kepler-Operator repo's CI to work it would be best to have a bump up in the version.

CC: @rootfs @SamYuan1990

@rootfs
Copy link
Contributor

rootfs commented Jul 6, 2023

@SamYuan1990 this looks a good opportunity to merge the open PRs and create a new release

@SamYuan1990
Copy link
Contributor

@rootfs , @vprashar2929 , do we need to wait for #50 ?

@SamYuan1990
Copy link
Contributor

otherwise, I will bump up the version this weekend.

@vprashar2929
Copy link
Contributor Author

IMHO it's still very unclear as to whether ProwCI would be a great fit provided the lack of understanding we have around it and whether it would be easy to integrate it or not. I am also in favor of testing Kepler against different OS and platforms. If it will take more time to come to a consensus with #50 I think we can bump up the version with whatever we have till now as it will be inclined with version to local-dev-cluster. Wdyt?

@SamYuan1990
Copy link
Contributor

IMHO it's still very unclear as to whether ProwCI would be a great fit provided the lack of understanding we have around it and whether it would be easy to integrate it or not. I am also in favor of testing Kepler against different OS and platforms. If it will take more time to come to a consensus with #50 I think we can bump up the version with whatever we have till now as it will be inclined with version to local-dev-cluster. Wdyt?

em... I suppose we need point our CI to v0.0.1 as #57
as the reason, when we try to bump up version of this repo, we want to points to the specific version used for local-dev-cluster. and test it, if the test is passed, we are confidence to apply the change to kepler, operator, and helm chart etc.

@SamYuan1990
Copy link
Contributor

we can bump up version once #57 is merged as a checkpoint.

@SamYuan1990
Copy link
Contributor

ok as #57 is merged, WIP to bump up kepler-action version.

@SamYuan1990
Copy link
Contributor

close with https://github.com/sustainable-computing-io/kepler-action/tree/v0.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants