The job update-pipeline-<root deployment> is not triggered as expected #172
Assignees
Labels
Comments
o-orand
added a commit
that referenced
this issue
Jul 17, 2018
o-orand
added a commit
that referenced
this issue
Jul 24, 2018
After we updated resource triggering mechanism, we now need to rename the secrets resource used to trigger jobs to avoid a job triggering burst. related to #172
o-orand
added a commit
that referenced
this issue
Jul 24, 2018
One place forgotten... related to #172
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior
When I commit new artifacts in local configuration/secrets repository of a bosh deployment, I expect the triggering of the job update-pipeline- in order to apply the change (i.e create or update a new deployment).
Observed behavior
The job update-pipeline- is not triggered as expected and the change are not applied oa applied with delay.
Affected release
Develop branch
Traces and logs
Build 734 on integration platform
The text was updated successfully, but these errors were encountered: