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>
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.
The recent update to Tekton Pipeline v0.36.0 (https://github.com/tektoncd/pipeline/releases/tag/v0.36.0) appears to cause an error when executing the build tasks in the buildpacks pipeline.
This change removes task parameters that should be automatically propagated when using Pipeline v0.36.0+
Signed-off-by: Brad Beck <bradley.beck@gmail.com>
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>
These changes introduce the Buildpacks Pipeline. This pipeline
builds source into a container image using Cloud Native Buildpacks.
To do that, it uses builders to run buildpacks against your application source.
It relies on git-clone, buildpacks, and buildpacks-phases tasks to perform
it's tasks.
Signed-off-by: Javier Romero <rjavier@vmware.com>
Few task's README contains some url links which had
invalid directory path and was pointing to a invalid page
Signed-off-by: Shiv Verma <shverma@redhat.com>
This patch includes-
Currently we have a file called `build-push-gke-deploy`
which has multiple resources in one file, this patch moves
the pipeline to the pipeline directory and it's corresponding
task to the support directory
Signed-off-by: Puneet Punamiya <ppunamiy@redhat.com>
This commit represents a complete update of the OpenWhisk to Knative pipeline from v1alpha1 level to v1beta1 resource levels. This pipeline also adds conditional logic to support additional "branches" of the pipeline to sequence tasks that can detect and build serverless applications for not only NodeJS (previously the only lang. supported), but also Python and Java. In addition, this pipeline utilizes a workspace for sharing data/state across tasks. Each language branch has its own sample functions with instructions for users to build and test on knative the services they build.
