Sprint plan for OSIO Build: # 147

[krishnapaparaju]

Work item tracker
https://github.com/orgs/fabric8io/projects/2

Integration testing

• OSIO tenant space

• Jenkins Proxy

• Jenkins Idler

Collect metrics around OSIO builds #2778

• An instance is to be idled, is actually getting idled ?

• An instance is to be unidled, is actually getting unidled ?

• How many times web hooks are being received, store the source for these webhooks (& check if build / required action got started with success)

Tenant Jenkins

• Lots of config errors on jenkins startup #2608 - Tenant Jenkins boots up with way too many config issues.

• If a user has multiple builds running at the same time, one or both will fail ("Unable to build the image using the OpenShift build service") #2729 - Do not start parallel builds for a OSIO user, notify user

• Jenkins trying to spin up multiple slaves at the same time #2384 - Jenkins trying to spin up multiple slaves at the same time

• TODO add more

Pipeline library

• Auto update of planner version to fabric8-ui is broken #2825 - Fix the readonly mount + chmod issue across pipeline library

UI

• Incorrect build URLs
  Build urls from pipelines widget and pipelines page is sometimes wrong #2744

Proxy

• Replay incoming requests, might be part of Metrics collection work
  Have a way to inspect and delete individual replay request from the request table fabric8-services/fabric8-jenkins-proxy#201

• Code refactoring and Add Unit Tests
  Refactor Proxy.handleJenkinsUIRequest fabric8-services/fabric8-jenkins-proxy#179

• Have incoming webhooks at a queue, for better visibility, scale with more proxies , plays into collecting metrics work
  Allow to run multiple proxy instances in parallel fabric8-services/fabric8-jenkins-proxy#175

• Refactor Proxy.handleJenkinsUIRequest fabric8-services/fabric8-jenkins-proxy#179

• Integration tests Integration tests for proxy fabric8-services/fabric8-jenkins-proxy#208

• Jenkins Proxy load testing Get insights about builds failures fabric8-services/fabric8-jenkins-proxy#214

Idler

• https://github.com/fabric8-services/fabric8-jenkins-idler/milestone/1

• Estimate memory requirements for Idler
  Estimate memory requirements for Idler fabric8-services/fabric8-jenkins-idler#161

• Idler retaining state
  Jenkins idler is retaining stale data on active builds  fabric8-services/fabric8-jenkins-idler#143

• Build would not start for OISO user
  Build Pipeline won't talk to un-idled Jenkins #2600

• Build pipeline fails
  Jenkins is idle, pipeline build fails #2690

• Integration tests
  Integration tests for idler fabric8-services/fabric8-jenkins-idler#176

Auth

• Intermittent auth issue to reach jenkins.openshift.io
  unauthorized_error on accessing jenkins.openshift.io fabric8-services/fabric8-jenkins-proxy#205

Fabric8 Builds

• [ ]

• [ ]

Fabric8 Maven Plugin

• Use a released version in place of master for boosters fabric8io/fabric8-maven-plugin#1245
• Revert default image name back to "latest" for snapshots fabric8io/fabric8-maven-plugin#1093
• Deployments cancelled fabric8io/fabric8-maven-plugin#1243
• Fix CI setup of fabric8 maven plugin fabric8io/fabric8-maven-plugin#1198

Fabric8 Kubernetes Java Client

• Implement waitUntilCondition fabric8io/kubernetes-client#989
• RejectedExecutionException in WatchHTTPManager fabric8io/kubernetes-client#1035
• Failure in update while operating on CRUD mode on Kubernetes mock server fabric8io/kubernetes-client#957
• retrieval of imagestreamtags do not appear to work with the v3.x client fabric8io/kubernetes-client#1046

I also see that you have a lot of issues outside of openshift.io repo. You can move them to this repo with https://github-issue-mover.appspot.com/. We need them all in one place so that we can track them.

[pradeepto]

@krishnapaparaju

FMP and FKC are also owned by build team. Those are upstream projects that we maintain for now and make sure they work for OpenShift and OSIO bits. We need to add the following issues to the sprint that @pgarg and @rohanKanojia will take care of.

Fabric8 Maven Plugin

fabric8io/fabric8-maven-plugin#1245
fabric8io/fabric8-maven-plugin#1093
fabric8io/fabric8-maven-plugin#1243

Fabric8 Kubernetes Client

fabric8io/kubernetes-client#1035
fabric8io/kubernetes-client#957
fabric8io/kubernetes-client#1046

[pradeepto]

@krishnapaparaju Echoing what I said on MM. There are far too many proxy and idler issues in the list above. There are two people who work on that (by design) - @chmouel and @kishansagathiya . We can't possibly doing 10+ issues of those in one sprint. We need to reduce those.

[chmouel]

We need tasks for Jenkins and Builds, I would advise strongly to look over the backlogs on https://github.com/orgs/fabric8io/projects/2

[joshuawilson]

@krishnapaparaju To avoid more then one person working on an issue, please assign the person working on it and set the Milestone Sprint ###. At least one of these was picked up in the Platform planning.

I also see that you have a lot of issues outside of openshift.io repo. You can move them to this repo with https://github-issue-mover.appspot.com/. We need them all in one place so that we can track them.

[maxandersen]

I also see that you have a lot of issues outside of openshift.io repo. You can move them to this repo with https://github-issue-mover.appspot.com/. We need them all in one place so that we can track them.

what issues is it you believe should be moved over ?

[joshuawilson]

@maxandersen if you look at the main description, there are a lot of links to external repo. i.e. fabric8-services/fabric8-jenkins-proxy#201

[chmouel]

@joshuawilson what's the point of having to move all the issues from the individual repositories to openshiftio ?

[joshuawilson]

@chmouel everything is being tracked by PM in https://github.com/openshiftio/openshift.io/projects/3

And if everything is in one place we can export it to planner (when we are ready to).

[kishansagathiya]

This issue was created for sprint planning. I don't see a reason to keep it open once the sprint is done.
Closing it.

[bartoszmajsak]

@kishansagathiya before closing it would be good to update the status of the checklist in the description