search

cloudfoundry / bosh-deployment-resource

Apache License 2.0
12 stars 26 forks source link

final bosh release should not be force uploaded if present in the director #63

Closed poblin-orange closed 3 years ago

poblin-orange commented 5 years ago

Using this resource in a CD concourse pipeline. The dependent bosh releases are in final version. We experience slowness due to resource uploading the bosh releases even if previously updated.

eg:

Task 4658099 | 22:35:34 | Extracting release: Extracting release (00:00:00)
Task 4658099 | 22:35:34 | Verifying manifest: Verifying manifest (00:00:00)
Task 4658099 | 22:35:34 | Resolving package dependencies: Resolving package dependencies    
Task 4658099 | 22:35:34 | Processing 5 existing packages: Processing 5 existing packages    
Task 4658099 | 22:35:34 | Processing 1 existing job: Processing 1 existing job (00:00:00)
Task 4658099 | 22:35:34 | Release has been created: binary-buildpack/1.0.33 (00:00:00)

This loses time on big deployment (eg: cf-deployment) and put useless load on the director most of the time.

Could the resource be optimized for this use case ?

bosh-admin-bot commented 3 years ago

This issue was marked as Stale because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale label or comment below.

bosh-admin-bot commented 3 years ago

This issue was closed because it has been labeled Stale for 7 days without subsequent activity. Feel free to re-open this issue at any time by commenting below.