Comments (10)
And even if they are identical, it pushes them separately, which makes it take more time. So there is definitely some time to be saved by being able to only build one release.
from release.
This is by (original) design. It's possible to skip the beta builds in those cases, but we'd have to turn off the consumers too. I believe GKE has some automated rollouts and expect there to be a beta.0 when a new X.Y.Z official release is cut. @alex-mohr @roberthbailey
from release.
1.4.4-beta.0 is a tag that we apply immediately after cutting a 1.4.3 release. This keeps the semantic name on the 1.4 release branch when testing CI builds ahead of 1.4.3 so that everything being tested at that point follows the correct semantic versioning rules. AFAIK it's just a tag applied to git which takes no extra time.
from release.
I think @jessfraz said that the release script pushes the patch release and beta release separately. I might be mis-remembering though.
from release.
It builds the artifacts and pushes them to gcr and gcs for both the major
release and the beta.
On Sun, Oct 16, 2016 at 10:55 PM, David Oppenheimer <
[email protected]> wrote:
I think @jessfraz https://github.com/jessfraz said that the release
script pushes the patch release and beta release separately. I might be
mis-remembering though.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#154 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABYNbAK2dPsdur1aSyKksuaQDpFT7WXgks5q0w3TgaJpZM4KX6x1
.
from release.
That must have changed with the release automation.
from release.
@roberthbailey the betas have always been pushed at the same time as the official.
Before the automation was in place and I was still doing things manually, I forgot to push a beta once and got a stern talking to from Ike. Apparently it broke the GKE CI. I don't know if that requirement is still in place, but if not we certainly could skip building and publishing betas.
from release.
So again, this is a very simple change on the release side. The issue is making sure we're not breaking anyone.
from release.
Closing this. There is the larger issue of what downstream (GKE) expects before anything can happen with this task.
from release.
@ihmccreery Can you add some context here? I remember one time before the automation (anago), we didn't push one of these tagged (but unreleased) releases and something fell over. What was that again and is that still the case today?
from release.
Related Issues (20)
- release-notes (and release-sdk) don't check the remotes when reusing an existing temp dir for repos HOT 8
- CVE reported with distroless-iptables images HOT 9
- Dependency update - Golang 1.21.7/1.20.14 HOT 4
- Automating `krel` binary releases HOT 4
- Dependency update - Golang 1.22.1/1.21.8 HOT 8
- krel/templates: remove kubeadm's dependencies on kubelet and kubectl HOT 7
- E: The repository 'https://apt.kubernetes.io kubernetes-xenial Release' does not have a Release file. HOT 3
- The legacy Kubernetes package repositories are removed as of 2024-03-04
- few days ago the old repo has been turned off and now trying to use the new repo https://pkgs.k8s.io/core:/stable:/ fails for specific version HOT 4
- Instructions to Migrate to the Kubernetes Community-Owned Repositories Not Working HOT 2
- How to upgrade 1.21 clusters HOT 7
- Add a landing page for pkgs.k8s.io HOT 6
- Error encountered during installation using deprecated legacy Google-hosted repositories HOT 16
- new kubernetes el7 repo ? HOT 11
- Edited release notes will logically interfere with mapped values
- No worldwide location for legacy packages HOT 4
- Error install kubernates HOT 2
- Release Notes Collection Picks Up Incorrect Text HOT 7
- The repository 'https://pkgs.k8s.io kubernetes-xenial InRelease' is not signed HOT 5
- Dependency update - Golang 1.22.2/1.21.9 HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from release.