Skip to content

Conversation

@wking
Copy link
Member

@wking wking commented Jul 6, 2018

Catching up with d61abd4 (coreos/tectonic-installer#3137), which removed the root Makefile.

Catching up with d61abd4 (*: cleanup bazel rules, 2018-03-26,
coreos/tectonic-installer#3137), which removed the root Makefile.
@coreosbot
Copy link

Can one of the admins verify this patch?

@openshift-ci-robot
Copy link
Contributor

Hi @wking. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

I understand the commands that are listed here.

Details

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.

@openshift-ci-robot openshift-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 6, 2018
## Developer experience

The developer workflow is reflective of how often clusters will be created and destroyed. This project makes heavy use of `make` to make these repetitive actions easier.
The developer workflow is reflective of how often clusters will be created and destroyed. This project makes heavy use of [Bazel][] to make these repetitive actions easier.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This reference to make has nothing to do with building the project but rather the developer workflow we used to have for quickly creating and destroying clusters using make apply and make destroy. It is unrelated to Bazel as we never use bazel to automate building or destroying clusters. We should remove this line wholesale or replace with one describing the new dev workflow.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should remove this line wholesale or replace with one describing the new dev workflow.

Sounds good to me. I'll leave that to someone who actually knows what the new dev workflow is ;). Should I leave this PR open as a reminder? Or should I close it (with or without filing a placeholder issue)?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for understanding. Please close and file an issue 👍

@squat squat closed this Jul 6, 2018
@wking wking deleted the make-to-bazel branch July 6, 2018 23:44
stbenjam pushed a commit to stbenjam/installer that referenced this pull request Feb 10, 2021
Add bmh as a relatedobject in the clusteroperator
mkumatag pushed a commit to mkumatag/installer that referenced this pull request Aug 17, 2021
Currently TFVars only generates powervs_region. This patch
introduces a map between regions used by the PowerVS provider with
regions used by the VPC provider and sets powervs_vpc_region
using it. Additionally, removes powervs_zone and powervs_vpc_zone
as they are not required currently.
clnperez pushed a commit to clnperez/installer that referenced this pull request Sep 2, 2021
Currently TFVars only generates powervs_region. This patch
introduces a map between regions used by the PowerVS provider with
regions used by the VPC provider and sets powervs_vpc_region
using it. Additionally, removes powervs_zone and powervs_vpc_zone
as they are not required currently.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants