Remove hidden tag for latest Fuse builders #11292

[apupier]

it will allow to use them with odo

Signed-off-by: Aurélien Pupier apupier@redhat.com

NOTICE

Master branch is closed! A major refactor is ongoing in devel-40.
Changes for 3.x should be made directly to the latest release branch they're
relevant to and backported from there.

[openshift-ci-robot]

Hi @apupier. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[papr-bot]

Can one of the admins verify this patch?
I understand the following commands:

• bot, add author to whitelist
• bot, test pull request
• bot, test pull request once

[apupier]

@patrickdillon is it possible for you to review this PR too, please? it is the same than the one you reviewed on 3.10 branch.

[patrickdillon]

/ok-to-test

[patrickdillon]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: apupier, patrickdillon

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:

• OWNERS [patrickdillon]

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

[patrickdillon]

@apupier Sure!

If you do this sort of change often, you can create your PR against the latest branch (in this case release-3.11) and then /cherrypick release-3.10 and so on for earlier branches.

[apupier]

If you do this sort of change often, you can create your PR against the latest branch (in this case release-3.11) and then /cherrypick release-3.10 and so on for earlier branches.

thanks for the info!

[patrickdillon]

/retest

[openshift-bot]

/retest

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