uptimer

uptimer copied to clipboard

New feature: Allow to specify failure threshold in percentages

2

Currently the Uptimer configuration only allows absolute numbers for failure thresholds. The time a CF upgrade deployment takes can however vary significantly. A new stemcell version takes very long as...

jochenehret

Bumps [github.com/onsi/ginkgo/v2](https://github.com/onsi/ginkgo) from 2.17.3 to 2.19.0. Release notes Sourced from github.com/onsi/ginkgo/v2's releases. v2.19.0 2.19.0 Features Label Sets allow for more expressive and flexible label filtering. v2.18.0 2.18.0 Features Add --slience-skips...

dependabot[bot]

Support running uptimer against an isolation segment

1

Adds a new `isolation_segment` config option, to set the isolation segment used on the org/space for pushing + querying apps.

geofffranks

We hardcoded version `0.8.0` 6 years ago, and return that anytime anyone runs `uptimer -v`. Obviously, this is not a good practice. Possible solutions: 1. Remove the version flag option...

ctlong

Add Windows app availability test

3

Sometimes I need the ability to test changes that involve Windows diego cells. Perhaps we can add an additional test that can be optionally invoked via: ``` "optional_tests": { "run_windows_availbility":...

sneal

When an instance of uptimer's pushability measurement fails it should continue to delete the pushed app

3

When uptimer is targeting a foundation that `cf push` fails consistently on, it does not clean up the pushability measurement app that it pushed. The [`cmdRunner.RunInSequenceWithContext`](https://github.com/cloudfoundry/uptimer/blob/06d836998c62ae84986179ea1585e5676c4b4db8/cmdRunner/cmdRunner.go#L42-L50) method will return early...

sunjayBhatia

When uptimer fails to push its app - it should not run its `while`

5

Had this happen today, our CF is misconfigured and our app failed to push. Even though the app broke uptimer still went into its run of `while`. I guess I...

zachgersh