* first submission
* changed to non npm source repo
* added params to the hugo task
* added readme
* removed platform restriction doc
* updated task and readme
* added task description
* used fully qualified registry name for docker image
* updated OWNERS
* tagged image with digest
* updated `apiVersion` to `v1` from `v1beta1`
This PR deprecates the old and broken Tasks because
they are now throwing errors. They are old and not
actively maintained which is why we decided to deprecate them.
Since with recent version of pipelines, affinity-assistant is enabled by
default and 2pvc cannot be bound to a pipeline at the same time hence
the task was failing
Remove the binding of optional workspace
few Tasks still uses PipelineResources which is no longer available
in latest version of pipelines hence marking them as deprecated
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
E2E tests were running an older version of pipelines ie v0.45.0.
Bumping it to use the latest version v0.51.0 so that current tasks in
catalog can be tested against latest version
Also remove pipelineresources check while doing installation of latest
version of pipelines
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
With git-clone version 0.8 and onwards, it started running as non-root
and GKE clusters were having some issues, so, we temporarily moved all
tasks to use git-clone version 0.7. Ref: https://github.com/tektoncd/catalog/pull/1079
Since we have now moved to kind clusters in our CI, this issue is now
resolved and thus moving all tasks to use latest version of git-clone
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
The previous tag, quay.io/skopeo/stable:v1.9.0, no longer exists. This
commit updates the image reference to use the `v1` floating tag.
Signed-off-by: Luiz Carvalho <lucarval@redhat.com>
This will bump jib-maven to 0.5
to handle the case where permission to
add certs to javacacerts is no there
we just create a new store with default certs and
add provided certs to that and use that cert
in mvn command
later delete the store on exit
Some tasks were referencing absolute paths for `results`. It is recommended
to use variable replacement syntax in the API spec. This PR migrates the
absolute paths for results to variable syntax notation.
