Comments (6)
tpepper
commented on September 12, 2024
1
There's a few options depending on how we structure this and how distro-like we might become, but my vision at this point is focused on core packages not broader:
- automated builds (eg: nightly) go here, in a specific clearly "nightly" part of a folder hierarchy
- testing happens
- PR to promote an indicated set of those built artifacts to a "testing" place, perhaps with an alpha/beta/rc designation added in the file name?
- testing happens
- PR to promote an indicated set of those built artifacts to a "release" place
I also want to see reaping of existing artifacts as a part of promotion so nightly's age out to archive, testing's age out to archive, and release section holds the current set of preferred/supported packages with prior ones moved out to archive.
I want all of this to happen from automation driven by auditable PRs. No parallel, slightly different builds. No rebuild for publication. No building from any non-committed code (today all packages are built using non-committed package spec files with manual edits made before building). I want to see a set of makefiles with "bump" target commands that increment build metadata, commit it, and then build/promote the next 1.13.N, or the next 1.13.1-R packaging, from that committed code.
This bucket would be use to prototype all of that.
(emails coming via DM)
from k8s.io.
dims
commented on September 12, 2024
from k8s.io.
thockin
commented on September 12, 2024
I'm a little uncomfortable making one-off experiments without a clean way to track it, but I can do this one.
Do we consider this a "staging" repo that needs a PR to "promote" artifacts or is it a real thing that people push to and store forever?
I'll need emails for people to add to a googlegroup to grant access to anything. I created "[email protected]" . I create a project "k8s-sig-release-prototype" and a public-readable bucket of the same name. I gave that group "Storage admin" privs to that bucket.
I did all of this by hand.
from k8s.io.
thockin
commented on September 12, 2024
The vision is grand. We are establishing "staging" repos (GCR and GCS) for
various sub-projects. This sounds similar but a little different. We'll
need to rationalize the differences and see how we want to set this up in
the end. For now, you have your playground (once you join the group)
…On Fri, Apr 26, 2019 at 3:05 PM Tim Pepper ***@***.***> wrote:
There's a few options depending on how we structure this and how
distro-like we might become, but my vision at this point is focused on core
packages not broader:
- automated builds (eg: nightly) go here, in a specific clearly
"nightly" part of a folder hierarchy
- testing happens
- PR to promote an indicated set of those built artifacts to a
"testing" place, perhaps with an alpha/beta/rc designation added in the
file name?
- testing happens
- PR to promote an indicated set of those built artifacts to a
"release" place
I also want to see reaping of existing artifacts as a part of promotion so
nightly's age out to archive, testing's age out to archive, and release
section holds the current set of preferred/supported packages with prior
ones moved out to archive.
I want all of this to happen from automation driven by auditable PRs. No
parallel, slightly different builds. No rebuild for publication. No
building from any non-committed code (today all packages are built using
non-committed package spec files with manual edits made before building). I
want to see a set of makefiles with "bump" target commands that increment
build metadata, commit it, and then build/promote the next 1.13.N, or the
next 1.13.1-R packaging, from that committed code.
This bucket would be use to prototype all of that.
(emails coming via DM)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#235 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABKWAVEUZZ6K32IFQDLNLILPSN4BBANCNFSM4HIMFTGA>
.
from k8s.io.
tpepper
commented on September 12, 2024
Forgot to update the issue here. We have this (k8s-sig-release-prototype) as a playground.
/close
from k8s.io.
k8s-ci-robot
commented on September 12, 2024
@tpepper: Closing this issue.
In response to this:
Forgot to update the issue here. We have this (k8s-sig-release-prototype) as a playground.
/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.
from k8s.io.
Related Issues (20)
- N2 Quota changes for Scale Projects HOT 3
- OIDC Provider Count Affecting EFS CSI Driver Test Cluster Provisioning
- AWS: Pod got deleted unexpectedly HOT 13
- VPC Limit Reached in AWS account eks-e2e-boskos-005 HOT 5
- DNS REQUEST: <your-dns-record> HOT 2
- registry.k8s.io: Unauthenticated requests do not have permission for europe-west10 HOT 4
- `Quota 'CPUS' exceeded` error on containerd presubmits HOT 7
- Cluster API Infra Provider AWS (CAPA) e2e tests regularly because the maximum number of EventBridge Rules has been reached HOT 8
- k8s-infra-prow-build: Deploy KubeCost and integrate it with the existing KubeCost installation on EKS HOT 5
- image-promo job is hitting quota limits HOT 9
- Create secret for triage party HOT 3
- eks-prow-build-cluster: Decommission the canary cluster HOT 10
- eks-prow-build-cluster: Replace FluxCD with ArgoCD HOT 5
- peribolos jobs using incorrect token HOT 3
- k8s infra GCE pool is frequently exhausted HOT 6
- Manage the DNS for etcd.io using GitOps
- DNS REQUEST: dash.etcd.io HOT 1
- Umbrella Issue: Kubernetes Infrastructure Tech Debt HOT 3
- Migrate Infra code to separate repo called k/infrastructure HOT 4
- Detected cluster health issues in your AWS account 808842816990 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 k8s.io.