James Strachan

then at a glance from the jenkins UI we can see which versions were created when etc so it'd be good if the pipeline library did the equivalent of the...

I had a job waiting on the approval step that I left for 11 hours on DevTools OSO and the Proceed & Abort links in the jenkins console didn't seem...

the current `isCI()` and `isCD()` functions should now delegate to a `getPipeline()` helper method which should lazily invoke this code: https://github.com/fabric8io/fabric8/blob/master/components/kubernetes-api/src/main/java/io/fabric8/kubernetes/api/pipelines/Pipelines.java#L34 and cache the Pipeline object (transiently!) around for the...

we should use a different PV location for snapshot builds (dev builds / CI / PRs) to releases (CD)

2

e.g. we don't want to pollute the CD release mvn repo with snapshots; we only want fixed releases. Whereas for snapshots we may wanna use a separate location

When using OSO we're gonna be restricting builds to 1 concurrent build per user. In which case its safe to have a write once PV for the local mvn repo...

if planner (work item tracker) is running we should POST an update to the REST API when we have promoted a build

1

for background see this issue: https://github.com/almighty/almighty-core/issues/726 essentially if we can detect planner / workitem-tracker is running (e.g. via a kubernetes Service being present or via a configuration as per this...

rolling upgrades seem to have stopped working

3

the old version is scaled down too quickly before the new version is ready. Not sure why but it seems a regression

it'd be awesome to create milestones every time we do a release where there are closed issues which are not associated with a milestone Then we can easily see what...

we define the environments for a team in the `fabric8-environments` `ConfigMap` Rather than having lots of different jobs that include Staging and/or Production, it might be just nice to have...