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>
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.
With git-clone version 0.8, Task now runs as non-root and with this change I
guess it's not working well with our GKE clusters and tests started
failing in nightly runs.
For now changing the version of git-clone to use 0.7 so that for now CI
is unblocked 😅
Signed-off-by: vinamra28 <jvinamra776@gmail.com>
Prior to this change, the installation instructions directly use the resource urls in the Catalog repo, which results in tight coupling between the organization and how users fetch resources (as described in TEP-0110). This commit updates the installation guide to install Tekton Catalog resources via Tekton Hub Api: https://github.com/tektoncd/hub/pull/539
This change decouples the Tekton Catalog organization from resouces resolution, which enables Tekton Catalog reorganization.
This will fix the issue of jib-maven task not passing digest to results
if the clone has happened in sub-directory and directory passed to
jib-maven task
It is because the directory param is not handled in path creation for digest
It will not break the existing the behaviour but fixing the issue for directory scenario
so doing the change in latest version
At this moment all tasks which can be executed on linux/s390x or
linux/ppc64le are tested and labelled accordingly.
The rest of the tasks can be labelled as `linux/amd64`, which
is default platform and where tasks are already tested via
default PR testing cycle.
Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
- Initially all tags were mapped to categories in Hub,
for e.g. config.yaml: https://github.com/tektoncd/hub/blob/master/config.yaml,
so whenever a new tag was added in a task it was mapped to a category called `others`.
Hence before every release we had to manually map these new tags to some category,
hence after the discussion in Catalog and Hub WG, a proposal was created for adding
a category as an annotation.
- PR to update the TEP-0003-Tekton Catalog Organization: https://github.com/tektoncd/community/pull/352
Signed-off-by: Puneet Punamiya <ppunamiy@redhat.com>
