feat(evaluateVariables stage) Made fetch exec history on evaluateVariables stage configurable

[wooseung-sim]

Evaluate Variables stage on pipeline config view loads previous 100 pipeline execution history to show the evaluated variable values on previous execution.

The size of execution context is too huge if the pipeline is lengthy and it has a lot of artifacts and have a lot of previous executions. One of our pipeline is not accessible evaluate variables stage in the pipeline config as it timed out on executionService.getExecutionsForConfigIds() executions always due to size of the response (~400MB) and slowness of the VPN network.

Spinning circle UI is keep going and then timed out usually due to slowness of the network and size of the http get response.

This change can make the number of fetching history configurable on settings-local.js

window.spinnakerSettings.maxFetchHistoryOnEvaluateVariables = 5;

Default value of it is 100 if it is not defined on settings-local.js.

With this change we can adjust fetch history size for evaluate variable stage config UI, and prevent UI delays and errors.

[spinnakerbot]

The following commits need their title changed:

• 293fe55: Made fetch exec history on evaluateVariables stage configurable

Please format your commit title into the form:

<type>(<scope>): <subject>, e.g. fix(kubernetes): address NPE in status check

This allows us to easily generate changelogs & determine semantic version numbers when cutting releases. You can read more about commit conventions here.

[dbyron-sf]

@wooseung-sim can you run yarn prettier please?

[wooseung-sim]

@wooseung-sim can you run yarn prettier please?

Thank you for letting me know. Ran it and pushed fixed commit.