CI/CD - part 1

[davidnixon]

https://en.wikipedia.org/wiki/CI/CD

https://www.ibm.com/cloud/architecture/tutorials/introduce-develop-cloud-foundry-app-toolchain

• [ ] Understand the above documentation
• [ ] Deploy a new version of the UI part of this code to ibm cloud This will need a new manifest file like this:

  ---
  applications:
    - name: fivefifthsvoter-preprod
      random-route: true
      memory: 512M
      buildpacks:
        - https://github.com/cloudfoundry/nginx-buildpack

  Using that manifest with proper credentials, a cf push from the ui dir will create a new app in the cloud foundry account. cf push -f preprod.yml

• [ ] Create a new toolchain for fivefifthsvoter-preprod Unlike the tutorial above I think you should start with an empty toolchain instead of starting with a pattern. That will allow you to use this existing github as the source instead of cloning this repo into IBM cloud github. I also suggest you trigger a new build based on updates to a branch. I suggest a branch named "preprod" @upkarlidder may have a different suggestions
• [ ] Test the build/deploy by triggering manually and by triggering with a change to the "preprod" branch.

Next steps to be documented in other issues:

• repeat above steps for a new fivefifthsvoter-services-preprod
• attach the new services preprod to needed services (cloudant etc.)
• attach the preprod ui to the url for fivefifthsvoter-services-preprod
• attach the toolchain steps such that build ui -> build services -> deploy service -> deploy ui
• more steps here :-)

[davidnixon]

Working on this now I have the toolchain create and currently testing the deployment. I am not using preprod. Instead I am working on the prod deployment from the stable branch.

[upkarlidder]

Thanks @davidnixon. The other option is to use Github actions and push a build on merge on github release. I believe the IBM pipeline uses Tekton, similar to the actions conceptually. Any interest in looking into Github actions? We have jobs that install and use IBM cloud CLI.

[davidnixon]

I am not opposed to that. I actually did not think of github actions because they are not available in our enterprise github. 😄 But they are of course available here.

[davidnixon]

The above toolchain is invoked by a commit to the stable branch.

[davidnixon]

@upkarlidder For tomorrow I would like to leave the above toolchain in place. After that, I really like the idea of containing the deployment here in github as you suggest. What do you think? Stay with toolchain on IBM Cloud or create a toolchain here with git actions? I found this with support for IBM cloud foundry https://github.com/IBM/cloudfoundry-deploy

[upkarlidder]

Agree. Let's leave as is for now but move over to Github actions next. You can have the Tekton scripts in the repo as well from what I understand, but GitHub actions seem simpler to me at this point. I also want to talk about non Cloud Foundry deployment, container based options with you and the team.