oc new-app/oc new-build parameter for not auto triggering build process: oc new-(app|build) --suppress-build #22468
Both waiting for the first build to fail (could take 15 mins or more) or combining
In the spirit of the abandoned #15429, I suggest adding a parameter
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).
Steps To Reproduce
You cannot prevent OCP from building.
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:
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
@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.