open-toolchain / tekton-catalog Goto Github PK

When using containerize task in a pipeline to create docker image - https://github.com/open-toolchain/tekton-catalog/blob/master/container-registry/task-containerize.yaml - , recently we're receiving this error:

error: failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to read dockerfile: failed to mount /home/user/.local/tmp/buildkit-mount136740543: [{Type:bind Source:/tekton/home/.local/share/buildkit/runc-native/snapshots/snapshots/1 Options:[rbind ro]}]: operation not permitte

It would be useful to have tasks to drive a schematics workspace (new/plan/apply/destroy/output support)

I found some in https://github.com/open-toolchain/schematics-toolchain/tree/master/.tekton but moving them to the catalog would be a better option

Conditional branching of paths is hard to achieve in Tekton, so I propose that this task looks at the trigger of the pipeline and simply returns successfully if executed within the context of the pipeline being triggered by something like a timed or manual trigger.

additional-tags-script parameter for https://github.com/open-toolchain/tekton-catalog/tree/master/container-registry#icr-containerize is not took in account/working well when there is some ' in the script/parameter value

Setting status to pending in gitlab when status is already pending causes a HTTP 400
Can we check the status if we are in gitlab AND we want to set to pending - and if already pending, then do not attempt to set the status ?
@jauninb FYI

https://github.com/open-toolchain/tekton-catalog/tree/master/kubernetes-service/sample
is missing a README and a sample for the iks-deploy-to-kubernetes

Scenario:
Creating a release/tag in github, results in a git reference of refs/tags/v0.0.2

Issue:
With the git clone task, the references are checked for the format refs/heads/xxx but not tags. Therefore any tagged release fails.

Will create a PR :-)

the tasks defined under kubernetes-service use the command ibmcloud ks cluster config and a parameter --export. That parameter is not documented here: https://cloud.ibm.com/docs/containers?topic=containers-cli-plugin-kubernetes-service-cli#cs_cluster_config

When trying that command locally on version 1.x, that parameter causes an error. Is it still valid?

https://github.com/open-toolchain/tekton-catalog/blob/master/container-registry/sample/README.md has these duplicate lines:

It also contains a buildkit-no-resources EventListener definition which is the providing the same example but without the needs to define PipelineResources for image as it uses the task's parameter image-url to provide the information.

It also contains a buildkit-no-resources EventListener definition which is the providing the same example but without the needs to define PipelineResources for image as it uses the task's parameter image-url to provide the information.

Most likely you wanted to document buildkit-no-resources and buildkit-no-image-url, but the latter is missing.

The README does not contain any instructions on how to (re)use the assets in this catalog. It would be great to have at least some links to outside documentation on how to install and use an asset.

The linked Continuous Delivery service and its Tekton section do not have any discussion of this catalog.

I followed the tutorial https://www.ibm.com/cloud/architecture/tutorials/develop-kubernetes-app-with-code-risk-analyzer, but pipeline fails on deploy-to-kubernetes and check-health steps due to not being authenticated to cluster, with the following messages:

Check ability to get a kubernetes deployment in test-proj using kubectl CLI
error: EOF

After I added some additional testing commands I noticed that user is not authenticated to cluster:

++ echo 'Check ability to create a kubernetes deployment in test-proj using kubectl CLI #### TESTING'
++ oc projects
Check ability to create a kubernetes deployment in test-proj using kubectl CLI #### TESTING
Error from server (Forbidden): namespaces is forbidden: User "system:anonymous" cannot list resource "namespaces" in API group "" at the cluster scope

I had to add scripts from commons repo to my app and change them to include the following code that authenticates to OCP, which I took from your other tutorial:

ibmcloud ks cluster config -c "${PIPELINE_KUBERNETES_CLUSTER_NAME}";
if which oc > /dev/null && ibmcloud ks cluster get -c "${PIPELINE_KUBERNETES_CLUSTER_NAME}" --json | jq -e '.type=="openshift"' > /dev/null; then oc login -u apikey -p "${PIPELINE_BLUEMIX_API_KEY}" ; fi;

So looks like task definition is missing proper authentication to cluster that it is deploying to....

May I suggestion running tekton-lint on every commit and PR?

If could also be used for branch protection.

You can use this to run it via docker:

# using docker
docker run \
    --rm \
    --tty \
    "--env=TERM=${TERM}" \
    "--volume=${PWD}:/src:ro" \
    "--workdir=/src" \
    node \
    npx tekton-lint --format=stylish "**/*.yaml"

or if you have node installed:

# using node 12+
npx tekton-lint --format=stylish "**/*.yaml"

I can submit a PR for a script/lint and/or for the CI system of your choice.