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

remove build helpers from api packages #20399

Merged
merged 2 commits into from
Jul 25, 2018

Conversation

deads2k
Copy link
Contributor

@deads2k deads2k commented Jul 23, 2018

Trying to switch oc to externals leads to trying to switch helpers to externals, leads to finding api helpers (no other deps) in an api package that needs to be pulled out.

@bparees @mfojtik @juanvallejo @soltysh

@openshift-ci-robot openshift-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 23, 2018
}
return sourceType
}

// LabelValue returns a string to use as a value for the Build
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This method is highly questionable. It's being used on an already compressed name and if the field it's setting cannot be set it would actually be better to fail since we really don't want to compress that value-space.

Copy link
Contributor

Choose a reason for hiding this comment

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

it's not an already compressed name in the case that we've taken the name and appended a sequence number to it, which i'm pretty sure is how we ended up needing this.

(someone has a buildconfig w/ a maxed out name. Without this logic we then append "-1" to it and fail to create the label).

@bparees
Copy link
Contributor

bparees commented Jul 23, 2018

Trying to switch oc to externals leads to trying to switch helpers to externals, leads to finding api helpers (no other deps) in an api package that needs to be pulled out.

not entirely sure i understand the motivation. Don't you need to create new external versions of these helpers (in an appropriate location)? so what good does moving them do? I can imagine that some of them might not be needed anymore once you create external versions of them for oc requirements, but not sure why the internal versions need to be moved out of the internal api package?

I'm not against it per se, just trying to understand.

@deads2k
Copy link
Contributor Author

deads2k commented Jul 23, 2018

not entirely sure i understand the motivation. Don't you need to create new external versions of these helpers (in an appropriate location)? so what good does moving them do? I can imagine that some of them might not be needed anymore once you create external versions of them for oc requirements, but not sure why the internal versions need to be moved out of the internal api package?

You can't do it with a sed or anything mechanical until you've split this out. Otherwise you end up with cross API version deps in the internal package. Also, that PR is enormous, so this is snipping the links ahead of time where possible

@deads2k
Copy link
Contributor Author

deads2k commented Jul 23, 2018

/test extended_builds

@openshift-bot openshift-bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 24, 2018
@openshift-bot openshift-bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 24, 2018
@juanvallejo
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 24, 2018
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, juanvallejo

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@deads2k
Copy link
Contributor Author

deads2k commented Jul 24, 2018

/retest

@juanvallejo
Copy link
Contributor

/test gcp

@deads2k
Copy link
Contributor Author

deads2k commented Jul 24, 2018

/retest

@deads2k
Copy link
Contributor Author

deads2k commented Jul 25, 2018

/test all

@deads2k
Copy link
Contributor Author

deads2k commented Jul 25, 2018

/retest

@openshift-merge-robot openshift-merge-robot merged commit f370159 into openshift:master Jul 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants