Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

New deployments freeze on first launch #29

Closed
o-orand opened this issue Sep 26, 2017 · 3 comments
Closed

New deployments freeze on first launch #29

o-orand opened this issue Sep 26, 2017 · 3 comments
Labels
bug on-demand-pipelines

Comments

@o-orand
Copy link
Member

o-orand commented Sep 26, 2017

When a new deployment is added, it freezes until the first pipeline step is executed.
Due to first pipeline step (update-pipeline-xxx-depls-generated), the pipeline auto-update. After auto-update, the new deployment is added with new dependencies. But theses dependencies haven't passed first step, so pipeline freeze.

pipeline-freeze

@poblin-orange
@o-orand o-orand added the bug label Sep 26, 2017
@o-orand
Copy link
Member Author

o-orand commented Oct 27, 2017

cc @aveyrenc

@o-orand
Copy link
Member Author

o-orand commented Oct 27, 2017

A workaround is to execute manually the first pipeline step.

o-orand added a commit that referenced this issue Dec 15, 2017
@o-orand
pipeline(depls): introduces a new staging branch on paas-templates
818ea7d 
To allow pipeline auto update, we introduce a new staging branch called
`pipeline-current-((paas-templates-branch))`.

`update-pipeline-<%= depls %>-generated` job is now scanning `paas-templates-wip`
for changes, is updating pipeline and committing to `paas-templates-full`.
All other jobs are still scanning `paas-templates-full`. Using this
mechanism, reduces dependencies on `update-pipeline-<%= depls %>-generated`
 and reduces inputs.

It should help to fix #19 and #29, but we probably need to introduce a
staging branch for secrets using similar mechanism.
o-orand added a commit that referenced this issue Dec 15, 2017
@o-orand
pipeline(depls): introduces a new staging branch on paas-templates
1d81cb8 
To allow pipeline auto update, we introduce a new staging branch called
`pipeline-current-((paas-templates-branch))`.

`update-pipeline-<%= depls %>-generated` job is now scanning `paas-templates-wip`
for changes, is updating pipeline and committing to `paas-templates-full`.
All other jobs are still scanning `paas-templates-full`. Using this
mechanism, reduces dependencies on `update-pipeline-<%= depls %>-generated`
 and reduces inputs.

It should help to fix #19 and #29, but we probably need to introduce a
staging branch for secrets using similar mechanism.
@o-orand
Copy link
Member Author

o-orand commented Jan 17, 2018

fixed as expected with 1d81cb8

@o-orand o-orand closed this as completed Jan 17, 2018
lucaspinto pushed a commit that referenced this issue Jul 11, 2018
@o-orand
pipeline(depls): introduces a new staging branch on paas-templates
ab0c669 
To allow pipeline auto update, we introduce a new staging branch called
`pipeline-current-((paas-templates-branch))`.

`update-pipeline-<%= depls %>-generated` job is now scanning `paas-templates-wip`
for changes, is updating pipeline and committing to `paas-templates-full`.
All other jobs are still scanning `paas-templates-full`. Using this
mechanism, reduces dependencies on `update-pipeline-<%= depls %>-generated`
 and reduces inputs.

It should help to fix #19 and #29, but we probably need to introduce a
staging branch for secrets using similar mechanism.
@o-orand o-orand moved this to Done in CF OPS Automation Aug 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug on-demand-pipelines
Projects
CF OPS Automation
Status: Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@o-orand @gberche-orange