bumping release is necessary for deployment about cf-deployment-concourse-tasks HOT 5 CLOSED

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

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

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

from cf-deployment-concourse-tasks.

Hey @medvedzver, thanks for opening this issue.

I think it could make sense to create a new task, or extend the existing ones, to accommodate this workflow. I'm curious to see what else other teams need as they start to use these tasks, so I'll wait on this for a while to get more input.

from cf-deployment-concourse-tasks.

The CAPI team has a similar situation in that we make commits to cloud_controller_ng which is a submodule for our capi-release.

The way we solved this problem was to bosh create-release our capi-release from a separate task/job and upload the release on our own. We also created an ops-file to have cf-deployment use the latest version of the release that's been uploaded. We used the bosh-deploy task instead of bosh-deploy-with-created-release.

from cf-deployment-concourse-tasks.

Hey @medvedzver and @aashah.

I'm trying to think how this would be accommodated. The task interface might look like this:

inputs:
- name: bbl-state
- name: cf-deployment
- name: cf-deployment-concourse-tasks
- name: ops-files
- name: release
- name: vars-store

outputs:
- name: updated-vars-store

params:
  BBL_STATE_DIR:
  MANIFEST_FILE: cf-deployment.yml
  OPS_FILES:
  SYSTEM_DOMAIN:
  VARS_STORE_FILE: deployment-vars.yml
  REGENERATE_VARS_STORE: false

# ^^ Existing configuration

  BUMP_SUBMODULE: false
  SUBMODULE_PATH: ~
  SUBMODULE_TARGET_BRANCH: ~

This would be the default, which keep the existing behavior. If you wanted to bump a submodule, you'd update configure your pipeline:

BUMP_SUBMODULE: true
SUBMODULE_PATH: src/uaa
SUBMODULE_TARGET_BRANCH: develop

Before the bosh deploy actually happens, the task would do the equivalent of

pushd $SUBMODULE_PATH
  git co $SUBMODULE_TARGET_BRANCH
popd

Would that cover your use case?

(I realize that this looks like an implementation, but I'm actually trying to discover the desired behavior/interface here.)

from cf-deployment-concourse-tasks.

Closing due to inactivity.

from cf-deployment-concourse-tasks.