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
oc new-app/oc new-build parameter for not auto triggering build process: oc new-(app|build) --suppress-build #22468
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
This issue is as fresh as the morning dough. |
B.t.w. closing issues with a bot because there is no activity on them is IMHO bad practice: this can lead to suppressing critical problems just because nobody in the project's takes over responsibility. |
/remove-lifecycle stale We use the similar bots as upstream Kubernetes - the feature lifecycle bot ensures that old issues get triaged. @openshift/openshift-team-developer-experience |
@adambkaplan Doh, reading GH comments on mobile devices leads to ignorance of hints like "commenting /remove-lifecycle stale" for me. Sorry. Thanks for adding the comment. Regarding the bot: Especially when issues come in from the wild, this procedure might be quite risky as devs who submitted a valid issue could move along/pass away/loose focus/whatever. IMHO a better approach would be to allow the bot adding the labels (and finally closing the issue) after sbdy (maybe to be defined more specifically) from the project team has added a label like e.g. "lifecycle/acknowledged" or else. If I wanted attacking Kubernetes installations, now I knew where I had to look. |
Problem description
When running
oc new-app
oroc new-build
, this automatically triggers a build creation.Especially Quarkus (and golang) tooling makes patching the BuildConfig necessary, see https://github.com/quarkusio/quarkus/blob/master/docs/src/main/asciidoc/openshift-s2i-guide.adoc
Both waiting for the first build to fail (could take 15 mins or more) or combining
oc create ...
with&& oc cancel-build
(can fail if build hasn't started yet) aren't really useful approaches.In the spirit of the abandoned #15429, I suggest adding a parameter
--suppress-build
that just cancels the first build execution.
Alternatively, the documentation could be enhanced in a way that shows how to patch the build config with the create commands (if possible).
Version
v3.11
Steps To Reproduce
oc new-app quay.io/quarkus/centos-quarkus-native-s2i~{quickstarts-clone-url} --context-dir=getting-started --name=quarkus-quickstart-native
Current Result
You cannot prevent OCP from building.
Expected Result
You can disable the build trigger with a parameter.
Especially for a good Quarkus adoption this is IMHO a crucial topic.
The text was updated successfully, but these errors were encountered: