ibm-cloud-architecture / devops-demo-pipelines

Sample Tekton Pipelines and Tasks to manage application pipelines

devops-demo-pipelines's Issues

Remove manifest file

A pull request included a manifest file and broke the process of updating the kabanero custom resource.

When using /bin/sh the create-release-for-git-task breaks

Instead of using bash if a user decides to use sh the script breaks

/bin/sh: syntax error: unexpected redirection

Create a new pipeline to deploy applications on cloud foundry

Ibmcloud cf install layer not sticking in docker

The RUN command ibmcloud cf install is not working as intended. Current workaround is including this command in the tekton scripts.

Infinite pipeline runs get created when using the pipeline manager

When the user triggers a pipeline run via a web-hook, pipeline runs continue to get generated because the event-type of the webhook is too generic. A new pipeline run gets triggered because the pipeline run has a task that is responsible for creating releases on the same repository. And a new Github release by definition is a push

When the user uploads a zip file to the release URL using bad/illegal

The user gets a response of
curl: (3) URL using bad/illegal format or missing URL

However, it is important to note, the zip file does get upload successfully with no defects.

gitops.yaml task is currently causing the pipeline to break

package-release-update-pl is not passing because of daemon issue

Because of the following error cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

Update default Kabanero pipelines to include additional stages

Currently the "*-build-deploy-pl" kabanero pipelines out of the box will execute the following tasks:

• validate-stack-task
• build-push-task
• image-scan-task
• deploy-task

Create a custom stack to include additional tasks so the order will be the following:

• validate-stack-task
• test-task
• build-push-task
• image-scan-task
• deploy-task
• health-check-task
• java-pact-test-task
• gitops

Refer to this link for more info (https://kabanero.io/guides/working-with-pipelines/#creating-and-updating-your-own-tasks-and-pipelines).

When the product operator activates the CRD, it associates the pipelines in the pipelines archive with each of the stacks in the stack hub. The default pipelines are intended to work with all the stacks in the stack hub in the previous example. All of the pipeline-related resources (such as the tasks, trigger bindings, and pipelines) prefix the name of the resource with the keyword StackId. When the operator activates these resources, it replaces the keyword with the name of the stack it is activating.

Unable to upload a tar file to a specific release via ssh

If you do a git clone via ssh, the user is unable to upload releases to a specific tag version. It appears that this protocol has not been implemented yet.

if org name has dashes, the sed is not getting the url of the repo name

Add section on how to bound pipelines onto kabanero stacks

We can extend this document by also including a new section,

How to bound your custom pipelines onto the default kabanero stacks

Unable to patch the kabanero instance

The current issue is that we are deleting the kabanero custom resource.

oc delete kabanero kabanero -o json

Include a problem statement in the README.md file

Got feedback from @hollisc and the README should include a problem statement on the problem the repo is trying to solve. For example, users may want to extend the kabanero pipelines to do certain tasks and we must version control these pipelines to helps teams solve these kinds of problems.

step 6 is not working and the user is not able to add pipelines to the Kabenero CR

Given a set of pipelines, such as

  pipelines:
      - https:
          url: https://github.com/kabanero-io/kabanero-pipelines/releases/download/0.6.1/default-kabanero-pipelines.tar.gz
        id: default
        sha256: 64aee2805d36127c2f1e0e5f0fc6fdae5cef19360c1bb506137584f3bd0988cc
      - https:
          url: https://github.com/oiricaud/pipelines/releases/download/v60.0/default-kabanero-pipelines.tar.gz
        id: package-release-update-pl
        sha256: 86b1902f9f7ce0911f759bbe9e11c27075a3b1f7cca40de59df19eab9afca45d
      repositories:
      - https:
          url: https://github.com/kabanero-io/kabanero-stack-hub/releases/download/0.6.3/kabanero-stack-hub-index.yaml

The run.sh script file is not allowing users to add pipelines to the kabanero.yaml file

Include tutorial on how to use git-package-release-pl

Move the git-package-release-pl from experimental to incubator to

Test in the old OCP cluster to validate the requirement of deploying pipelines in different environments.

step 5 updating kabanero CR is not updating correctly

Given:

 stacks:
      pipelines:
      - https:
          url: https://github.com/kabanero-io/kabanero-pipelines/releases/download/0.6.1/default-kabanero-pipelines.tar.gz
        id: default
        sha256: 64aee2805d36127c2f1e0e5f0fc6fdae5cef19360c1bb506137584f3bd0988cc
      - https:
          url: https://github.com/oiricaud/pipelines/releases/download/v60.0/default-kabanero-pipelines.tar.gz
        id: package-release-update-pl
        sha256: 86b1902f9f7ce0911f759bbe9e11c27075a3b1f7cca40de59df19eab9afca45d
      repositories:
      - https:
          url: https://github.com/kabanero-io/kabanero-stack-hub/releases/download/0.6.3/kabanero-stack-hub-index.yaml

the run.sh file is not updating a pipeline instance correctly.

Add section how to create a custom stack with kabanero

Generate gitops task for flat file kubernetes deployment.yaml

The current gitops task (https://github.com/ibm-cloud-architecture/devops-demo-kabanero-pipelines/blob/master/ci/assets/default-kabanero-pipelines/mcm-pipelines/tasks/gitops.yaml) is specific to kabanero deployments, using the appsodyapplication CRD.

We will need to create a task to update flat file deployment yaml.

ie.
sed -i "/image: /c\ image: $(inputs.resources.image.url)" deployment.yaml

For mcm pipeline, Kabanero CRD wrapped as deployable is deleted after a pipeline run

Actual:
MCM will initially deploy Kabanero (Appsody) application to target cluster successfully. Upon the execution of the MCM pipeline, the Deployable for the Kabanero application CRD is deleted and not updated to use the new image.

Expected:
MCM pipeline will update existing Appsody application to use newly built image.

Unable to create a release

If the user uses ssh protocol to clone this repository the user is unable to create a release from running the ./run.sh script