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.

Sign up for GitHub

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

Jump to bottom

Release #17

Open
chrislovecnm opened this issue Aug 5, 2020 · 22 comments
Open

Release #17

chrislovecnm opened this issue Aug 5, 2020 · 22 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/testing Categorizes an issue or PR as relevant to SIG Testing.

Comments

@chrislovecnm
Copy link
Contributor

Do we have a release or beta release cut of this? Where can I download it from?
@amwat
Copy link
Contributor

amwat commented Aug 5, 2020

Not as of now, but we plan to cut a tagged release alongside whenever some of the kubernetes CI jobs start using the kubetest2 deployers (which are under construction).
For now you can get the latest binaries by go get sigs.k8s.io/kubetest2@latest and similarly for the deployers and testers.

@chrislovecnm
Copy link
Contributor Author

@amwat any idea on timeframe? I would love an alpha release since I am having to upload a binary to gcs for one of my builds.

@amwat
Copy link
Contributor

amwat commented Sep 9, 2020

We still don't have all the functionality from kubetest yet which I probably want before the first release. Most likely some time in the 1.20 time frame.

Does go get latest work for you currently?

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 8, 2020
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 7, 2021
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@amwat
Copy link
Contributor

amwat commented Mar 9, 2021

/reopen
/remove-lifecycle rotten
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot reopened this Mar 9, 2021
@k8s-ci-robot
Copy link
Contributor

@amwat: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten
/lifecycle frozen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Mar 9, 2021
@amwat amwat mentioned this issue Mar 9, 2021
Closed
@chrislovecnm
Copy link
Contributor Author

Bump. We could use a release 😁

@amwat
Copy link
Contributor

amwat commented Mar 17, 2021

Ack, I'd like to get in a few things and line up v0.1.0 with the alpha milestone of https://github.com/kubernetes/enhancements/tree/master/keps/sig-testing/2464-kubetest2-ci-migration#graduation-criteria

/cc @spiffxp @BenTheElder

@amwat
Copy link
Contributor

amwat commented Mar 19, 2021

/priority important-soon

@k8s-ci-robot k8s-ci-robot added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Mar 19, 2021
@BenTheElder
Copy link
Member

it might be worth trialing with something like v0.0.1 just to exercise the mechanisms intended for use and let users start using fixed tags more easily. we can have many v0.0.Z to test it out.

@chrislovecnm
Copy link
Contributor Author

Can we please have a beta or alpha release?? Pretty please :)

@chrislovecnm
Copy link
Contributor Author

Bump

@amwat
Copy link
Contributor

amwat commented Aug 6, 2021

I was mainly waiting on the node tester changes in #103
there's only 1 last issue to tackle in the milestone https://github.com/kubernetes-sigs/kubetest2/milestone/1

after which I'll cut a v0.1.0

@spiffxp spiffxp added the sig/testing Categorizes an issue or PR as relevant to SIG Testing. label Aug 17, 2021
@chrislovecnm
Copy link
Contributor Author

Any updates??????? Please cut a release

@amwat
Copy link
Contributor

amwat commented Sep 20, 2021

Ah yes, I've fallen a bit behind on this 😅 . All the things that we were mostly waiting on are in now.
Will cut a release this week.

@pseudomuto
Copy link

Is this still something that's going to happen? Any reason to not cut a release?

@BenTheElder
Copy link
Member

amwat moved on and this project is understaffed, I'm currently the only active approver and I have a number of other more urgent things elsewhere

pseudomuto added a commit to pseudomuto/kubetest2 that referenced this issue May 20, 2022
@pseudomuto
Set up GoReleaser to make releases for tags
3bb31d7 
Related: kubernetes-sigs#17

Adding [GoReleaser](https://goreleaser.com/) to handle generating
releases for tags. This will make it so that cutting releases is as
simple as pushing a tag. The result will be a release which includes the
changelog, binaries for Linux/Windows/Darwin, as well as the checksums
for each of the archives.

I've added some light details about how it works in RELEASE.md as well
as the one-time setup step required to make it work (A limited scope
GitHub token).
pseudomuto added a commit to pseudomuto/kubetest2 that referenced this issue May 20, 2022
@pseudomuto
Set up GoReleaser to make releases for tags
ccb1d9a 
Related: kubernetes-sigs#17

Adding [GoReleaser](https://goreleaser.com/) to handle generating
releases for tags. This will make it so that cutting releases is as
simple as pushing a tag. The result will be a release which includes the
changelog, binaries for Linux/Windows/Darwin, as well as the checksums
for each of the archives.

To see what this looks like, I've created a dummy release on my fork.
Because this is the first release, the changelog is massive, but going
forward it should be a little more reasonable.

Sample release:
https://github.com/pseudomuto/kubetest2/releases/tag/v0.1.0

I've added some light details about how it works in RELEASE.md as well
as the one-time setup step required to make it work (A limited scope
GitHub token).
@pseudomuto pseudomuto mentioned this issue May 20, 2022
Closed
@GanjMonk
Copy link

GanjMonk commented Jul 21, 2022 •
edited
Loading

Hello @BenTheElder, it looks like there is a good time to resume discussion :) Right now it is impossible to use latest kubetest2 with ginkgo-tester and --test-package-version flag (when you need some exact test suite version, e.g. v1.22.2) due to preparation for ginkgo v2 in 0d04f94, it seems only master branch contain such changes https://github.com/kubernetes/kubernetes/blob/303f47c0c069c80ec6d2b3879bc879924d555a8a/hack/ginkgo-e2e.sh#L175

I prepared PR to revert this changes, but it could be better to have release at least before and after such global changes (I mean ginkgo and ginkgo v2)

GanjMonk referenced this issue Jul 21, 2022
@k8s-ci-robot
Merge pull request #200 from leonardpahlke/ginkgov2-flag-update
2aac35a 
Update ginkgo flags
@BenTheElder
Copy link
Member

BenTheElder commented Jul 26, 2022 •
edited
Loading

I’m sorry, I’ve been on vacation the past few weeks, I’m back now but I’m changing roles and will probably? step down from this project.

EDIT: #212

My advice for now is to pin the version using @commit with go get, but I agree that releases would be a good idea.

We should probably consider at least extremely lightweight releases that merely provide some named v0.0.Z tags to work with for pinning even if we don’t have release notes, version support policies, binaries etc yet.

cc @MushuEE

@BenTheElder BenTheElder mentioned this issue Jul 29, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/testing Categorizes an issue or PR as relevant to SIG Testing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@spiffxp @chrislovecnm @BenTheElder @pseudomuto @GanjMonk @k8s-ci-robot @amwat @fejta-bot