search

cloudfoundry / cf-for-k8s

The open source deployment manifest for Cloud Foundry on Kubernetes
Apache License 2.0
300 stars 115 forks source link

Migrate capi-k8s-release pipeline #615

Closed jspawar closed 3 years ago

jspawar commented 3 years ago

WHAT is this change about?

Migrate the capi-k8s-release pipeline into our CI and refactor it a bit to use our pools instead of a single, semi-persistent cluster.

Any unique tasks that pipeline used have been moved into a new directory: ci/tasks/cake to make clear they are separate from our more general tasks for cf-for-k8s.

Once this is merged, will have to update the cf-for-k8s-ci resource in this pipeline to point at develop instead of the branch this PR is coming from.

Does this PR introduce a change to config/values.yml?

No

Acceptance Steps

  1. Run ./ci/configure cf-api and observe that Fly believes there are no changes to apply (since these change have already been applied to the pipeline)
cf-gitbot commented 3 years ago

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/176645544

The labels on this github issue will be updated when the story is started.

acosta11 commented 3 years ago

Quick update: it looks like the file extension update may have missed a few references. See https://release-integration.ci.cf-app.com/teams/main/pipelines/cf-api/jobs/cc-unit-tests/builds/33 

Backend error: Exit status: 500, message: {"Type":"ExecutableNotFoundError","Message":"exec failed: container_linux.go:367: starting container process caused: exec: \"cf-for-k8s-ci/ci/tasks/cake/run_cc_unit_tests\": stat cf-for-k8s-ci/ci/tasks/cake/run_cc_unit_tests: no such file or directory","Handle":"","ProcessID":"","Binary":""}

I think we just need to update a few more task config files to also refer to the scripts with the .sh file extension. Birdrock and I will go ahead and make that change so we can get this merged.