Added build-catalog-tool-timeout parameter to install command.

[valdar]

Added build-catalog-tool-timeout parameter to the install command.
Added CAMEL_K_BUILD_CATALOG_TOOL_TIMEOUT to e2e tests scripts to leverage the new install parameter.
Updated doc.
Small addition to .gitignore

This is useful in environment where the default timeout of 2 minutes is not sufficient.

Release Note

NONE

[github-actions]

🐫 Thank you for contributing!

Code Coverage Report ✔️ - Coverage unchanged.

[gansheer]

I might be missing something, but I am not sure this is a good idea to add a flag on a deprecated field :

camel-k/pkg/apis/camel/v1/integrationplatform_types.go

Lines 127 to 129 in 75fd59d

	// the timeout (in seconds) to use when creating the build tools container image
	// Deprecated: no longer in use
	BuildCatalogToolTimeout *metav1.Duration `json:"buildCatalogToolTimeout,omitempty"`

[squakez]

The field is deprecated. It is already not used in version 2.1 where we got rid off dynamic builder catalog.

[oscerd]

If 2.0.x is going to have patch releases, we need to merge this one.

[squakez]

If 2.0.x is going to have patch releases, we need to merge this one.

In case we should do on release-2.x branch only.

[oscerd]

We are still publishing the nightly for 2.0.2

[oscerd]

If 2.0.x is not going to be released anymore, we should avoid publishing nightly. This PR is not dangerous and I think the target is the nightly release, so we could merge and in case there will be any future release it will be there, in case not, there is always the nightly.

[squakez]

If 2.0.x is not going to be released anymore, we should avoid publishing nightly. This PR is not dangerous and I think the target is the nightly release, so we could merge and in case there will be any future release it will be there, in case not, there is always the nightly.

Yes. The target of this PR is main. If we want it on release branch it should be created another PR targeting it.

[oscerd]

If 2.0.x is not going to be released anymore, we should avoid publishing nightly. This PR is not dangerous and I think the target is the nightly release, so we could merge and in case there will be any future release it will be there, in case not, there is always the nightly.

Yes. The target of this PR is main. If we want it on release branch it should be created another PR targeting it.

Ah, maybe I should check the branch before commenting nonsense!

[github-actions]

🐫 Thank you for contributing!

Code Coverage Report ✔️ - Coverage unchanged.

[github-actions]

🐫 Thank you for contributing!

Code Coverage Report ✔️ - Coverage unchanged.

[valdar]

Ok thank to @squakez I figured out that for some days this PR is actually irrelevant for main due to #4764 .
I have ported it to release-2.0.x and opened against that branch here #4827 if it can be useful.