Skip to content

Conversation

@mfojtik
Copy link
Contributor

@mfojtik mfojtik commented Jun 4, 2015

No description provided.

@mfojtik mfojtik force-pushed the defining-buildconfig branch from f5d2d3f to 4b5adea Compare June 4, 2015 09:46
@mfojtik
Copy link
Contributor Author

mfojtik commented Jun 4, 2015

@bparees @soltysh still tweaking this out and trying to match deploymentConfig... but any early feedback appreciated :)

Copy link
Contributor

Choose a reason for hiding this comment

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

STI should be first :)

and should be spelled out as Source-To-Image.

Copy link
Contributor

Choose a reason for hiding this comment

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

also those need to be links or something... "overview: there are 3 types of builds" and then saying nothing about them and moving on to buildconfig isn't very helpful. They are defined over here:
http://docs.openshift.org/latest/architecture/core_objects/builds.html#build-strategies

(the fact that we have two places for build information is a bit of a challenge)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@bparees
Copy link
Contributor

bparees commented Jun 4, 2015

@soltysh after @mfojtik is done, this is probably where you can add discussion of incremental builds (and the other buildconfig parameters). That's why i was confused this morning..... @soltysh has this other build doc related issue: #424

@mfojtik mfojtik force-pushed the defining-buildconfig branch from 4b5adea to f7ee1b9 Compare June 5, 2015 13:05
@mfojtik mfojtik changed the title [WIP] Defining a buildConfig Defining a buildConfig Jun 5, 2015
@mfojtik
Copy link
Contributor Author

mfojtik commented Jun 5, 2015

@bparees comments addressed

@mfojtik
Copy link
Contributor Author

mfojtik commented Jun 5, 2015

@soltysh
Copy link

soltysh commented Jun 5, 2015

Hmmm, maybe we should move entire contents into the doc you're updating, do the same with routing and leave in Core Objects just the two describing origin and k8s model.

@bparees
Copy link
Contributor

bparees commented Jun 5, 2015

@soltysh @mfojtik did you guys not read my email? :)

@bparees
Copy link
Contributor

bparees commented Jun 5, 2015

@mfojtik go ahead and get rid of the BuildConfig in the architecture section as part of this PR. You can move the secrets discussion over too.

@soltysh
Copy link

soltysh commented Jun 5, 2015

@bparees yeah, but only after reaching this PR 😉

Copy link

Choose a reason for hiding this comment

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

Now in our api it's called just source, I'd rename it to match.

@mfojtik mfojtik force-pushed the defining-buildconfig branch from f7ee1b9 to 2f03963 Compare June 8, 2015 12:01
@mfojtik
Copy link
Contributor Author

mfojtik commented Jun 8, 2015

@soltysh @bparees updated, PTAL

@rhcarvalho
Copy link

@bparees
Copy link
Contributor

bparees commented Jun 8, 2015

good catch @rhcarvalho

Copy link

Choose a reason for hiding this comment

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

Please update to v1, I'll be taking care of the rest.

Copy link
Contributor

Choose a reason for hiding this comment

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

v1!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@soltysh @bparees this is kubernetes resource, do we have v1 for kubernetes as well?

Copy link
Contributor

Choose a reason for hiding this comment

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

v1beta3! :) (I don't know, probably not since they haven't cut v1 yet)

@mfojtik mfojtik force-pushed the defining-buildconfig branch from 44b2071 to 37de006 Compare June 8, 2015 18:38
Copy link
Contributor

Choose a reason for hiding this comment

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

you're calling it source build here. so the arch doc lost a change or something.

@mfojtik mfojtik force-pushed the defining-buildconfig branch from bf48199 to 6b5784e Compare June 8, 2015 20:17
@bfallonf
Copy link

bfallonf commented Jun 9, 2015

@soltysh @mfojtik @bparees A lot of these changes are what I was getting to in my PR #443 (moving the example file and the procedures out of here), so I'll wait for this to merge before I go through it any more.

One thing: a lot of the cases of STI have been changed to S2I (which I think is infinitely better), but is there a reason not all of them have changed? It'd be great to get this consistent across all of the docs, so making them consistent here is a start.

@bparees
Copy link
Contributor

bparees commented Jun 9, 2015

@bfallonf apologies for any conflicts we're causing you.

as for the sti/s2i naming... yeah we're probably getting to the point where we can search and replace, we've been trying to dip our toes into it. I think i'm just not 100% certain STI isn't used legitimately in our api anywhere so i'm wary of screwing up our docs with a global search/replace, but I don't think that is the case.

@bfallonf
Copy link

bfallonf commented Jun 9, 2015

@bparees I can manage :) I'll wait for this to go through then make my edits to the procedures.

As for sti/s2i, who would I ask about that then? Understandable that it might break something. I'm asking for the sake of docs consistency.

@bparees
Copy link
Contributor

bparees commented Jun 9, 2015

@bfallonf myself, @mfojtik or @soltysh are good people to check with.

Choose a reason for hiding this comment

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

In v1 this should be "GitHub" and below "Generic".

@rhcarvalho
Copy link

This excerpt was not touched by this PR, but since we're improving the docs in general:

https://github.com/openshift/openshift-docs/pull/444/files#diff-6226fa3a4f1691fffcba49d8c9e13a0cR181

"A valid *ref* is a SHA1 hash, a tag or a branch name."

Choose a reason for hiding this comment

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

STI → S2I or Source-to-Image?!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i prefer Source-To-Image

@mfojtik
Copy link
Contributor Author

mfojtik commented Jun 9, 2015

@rhcarvalho I would rather have this merged now and then follow up with @soltysh and you updating the triggers... this PR is holding off another PR's we have here and causing people to do nasty rebases against this.

@mfojtik mfojtik force-pushed the defining-buildconfig branch from 6b5784e to 3f98218 Compare June 9, 2015 08:48
@mfojtik
Copy link
Contributor Author

mfojtik commented Jun 9, 2015

@adellape @bparees can we merge this now and follow up with other changes?

@soltysh
Copy link

soltysh commented Jun 9, 2015

I'm ok with merging this as is, since I'm waiting for this PR to merged as well. All the cleaning can be done as a follow-up either by @mfojtik or others interested parties.

@bparees
Copy link
Contributor

bparees commented Jun 9, 2015

@mfojtik sounds good.. @adellape can we get this merged and then iterate?

@adellape
Copy link
Contributor

adellape commented Jun 9, 2015

Surely.

adellape added a commit that referenced this pull request Jun 9, 2015
@adellape adellape merged commit a0f6de3 into openshift:master Jun 9, 2015
@mfojtik mfojtik deleted the defining-buildconfig branch August 25, 2015 09:39
sbeskin-redhat pushed a commit to sbeskin-redhat/openshift-docs that referenced this pull request Oct 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants