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.

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

docs(waiting-executions): Add waiting execution with branches changes to the Spinnaker 1.30 release preview #309

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
10 changes: 10 additions & 0 deletions content/en/docs/releases/next-release-preview/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,16 @@ In this example, even though each trigger has its own artifact(s) defined, when

Once the parameter has been configured and the value is set to true then orca retrieves the events back from clouddriver. Be aware that the size of the pipeline execution context may (significantly) increase by including events.

### Waiting executions with branches following FIFO order
If the Pipeline execution has branches and concurrent executions disabled.
When one branch completes and the running Pipeline execution is waiting for other branches to complete, the sequence of waiting executions is not following FIFO order. This is [fixed](https://github.com/spinnaker/orca/pull/4356) in Spinnaker 1.30 to follow waiting executions in FIFO order.

In the screenshot below, Started Manual Executions for every half a minute, so that the executions are waiting in the same line they arrived from top to bottom and they should run in the same order after the two branches of the execution are completed.
![Waiting executions with branches](Waiting_Executions_with_Branches.png)

As shown below, the execution with longest wait time has triggered when the first execution with two branches has completed after a Minute.
![Executions following FIFO order](Executions_Following_FIFO.png)

### Kubectl output

With https://github.com/spinnaker/clouddriver/pull/5846 and https://github.com/spinnaker/orca/pull/4374, it's now possible to include kubectl output in the pipeline execution context, by setting `kubernetes.jobExecutor.persistTaskOutput` to true and then setting `kubernetes.jobExecutor.enableTaskOutputForAllAccounts` to true to include it for all accounts, or setting the debug property to true for individual accounts.
Expand Down