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

Jump to bottom

Automation of Publishing Artifacts #122

Closed
timothysc opened this issue Sep 27, 2018 · 9 comments · Fixed by #633
Closed

Automation of Publishing Artifacts #122

timothysc opened this issue Sep 27, 2018 · 9 comments · Fixed by #633
Assignees
@chuckha
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Milestone
v1alpha1

Comments

@timothysc
Copy link
Member

Describe the solution you'd like
In an ideal world we would like to publish the following artifacts

--> Containers & AMI [Stable/Testing(alpha/beta/rc)/Periodic(sha)]
@dims - Where do we want to host this stuff.

Annotated Tags applied to the promotion of artifacts
-alpha/beta -> Testing

  • vX.Y.Z -> Stable

NOTE: This will affect test integration with kubeadm

/kind feature
@timothysc timothysc added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Sep 27, 2018
@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Sep 27, 2018
@dims
Copy link
Member

dims commented Sep 27, 2018

Added it to the infra team meeting agenda tomorrow.

@detiber detiber changed the title Publishing Artifacts Automation of Publishing Artifacts Oct 2, 2018
@detiber detiber added this to the v1beta1 milestone Oct 2, 2018
@detiber detiber removed this from the v1beta1 milestone Oct 17, 2018
@liztio
Copy link
Contributor

liztio commented Oct 17, 2018

/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Oct 17, 2018
@liztio liztio mentioned this issue Oct 17, 2018
Closed
@detiber detiber added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. and removed lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Nov 28, 2018
paulfantom pushed a commit to paulfantom/cluster-api-provider-aws that referenced this issue Jan 3, 2019
@openshift-merge-robot
Merge pull request kubernetes-sigs#122 from ingvagabund/unit-test-ins…
e0d0ff3 
…tances

Increase unit test coverage of pkg/cloud/aws/actuators/machine
@timothysc timothysc added priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jan 4, 2019
@timothysc timothysc added this to the v1alpha1 milestone Jan 4, 2019
@timothysc
Copy link
Member Author

@dims can we sync on this topic

@chuckha
Copy link
Contributor

chuckha commented Jan 4, 2019

xref kubernetes-sigs/kind#197

@dims
Copy link
Member

dims commented Jan 4, 2019

@timothysc ack. just waiting for things to get started ... k8s-infra-team meeting is next wed.

@timothysc timothysc added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Jan 7, 2019
@chuckha
Copy link
Contributor

chuckha commented Feb 6, 2019

@dims @timothysc did anything come out of your sync?

@vincepri vincepri removed their assignment Feb 13, 2019
@randomvariable randomvariable mentioned this issue Feb 14, 2019
Merged
@chuckha chuckha assigned chuckha and unassigned liztio Feb 20, 2019
@randomvariable
Copy link
Member

randomvariable commented Feb 20, 2019 •
edited

As of #580, setting the version number in .bazelrc will allow Bazel to be able to push images to a registry and generate /out with the binary artifacts to put on Github.

@detiber detiber removed the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Feb 25, 2019
@chuckha
Copy link
Contributor

chuckha commented Mar 1, 2019

Ok it looks like we have a path forward!

kubernetes/k8s.io#158 (comment)

allows us to join a group and have access to a gcr bucket. We can use that for the images and we can use GitHub for the files & binaries.

/lifecycle active

I'm going to work on getting a release automated for v1alpha1

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Mar 1, 2019
@chuckha
Copy link
Contributor

chuckha commented Mar 1, 2019

The eventual goal will be to learn enough to upstream it back to cluster-api

@chuckha chuckha mentioned this issue Mar 7, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@chuckha chuckha

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Milestone
v1alpha1
Development

Successfully merging a pull request may close this issue.

Adds initial release automator chuckha/cluster-api-provider-aws
8 participants
@dims @chuckha @timothysc @detiber @randomvariable @vincepri @k8s-ci-robot @liztio