Fix jib-gradle task

[piyush-garg]

This wil fix the issue jib gradle task
gettng failed on security constrained
environments like OpenShift

Fix #198

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

• Includes docs (if user facing)
• Commit messages follow commit message best practices
• Yaml file complies with yamllint rules.

See the contribution guide
for more details.

[hrishin]

/lgtm

[piyush-garg]

/test pull-tekton-catalog-integration-tests

[vdemeester]

/meow

[tekton-robot]

@vdemeester:

In response to this:

/meow

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.

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hrishin, vdemeester

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 [vdemeester]

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

[loosebazooka]

@piyush-garg I can't see how this actually helps. The gradle home is already defined using the system property: https://github.com/tektoncd/catalog/pull/199/files#diff-218c88f355db45e8a7a0e2bc9e76ac0eR48

Can you provide an explanation as to how this works? and why it's necessary? Is ~/.gradle not an appropriate home path?

gradle-user-home seems rather arbitrary, is it a constraint of the base image you're using?

[chanseokoh]

And this actually breaks caching. I don't think this is the right fix. We should revert it.

    - name: $(inputs.params.CACHE)
      mountPath: /tekton/home/.gradle/caches
      subPath: gradle-caches
    - name: $(inputs.params.CACHE)
      mountPath: /tekton/home/.gradle/wrapper

[loosebazooka]

This comment: gradle/gradle#8107 (comment) seems to indicate that it's a problem with the permissions of the .gradle directory. The solution in that comment is meant to diagnose the problem, not as a permanent solution.