This page outlines the process for running the Policy Daily Scrum. We will rotate the person responsible for this duty every month. This page is designed to help those who are new to the process. A meeting invite should be sent out to developers for the Monday, Tuesday and Thursday of each week. The Policy Scrum Page can be found here → Policy R9 Istanbul Team ScrumsR10 Jakarta Release Planning. (This may change depending on release)
...
- Gating results: To check the gating results follow this link → https://logs.onap.org/onap-integration/daily/. From here, access and check the onap_daily_pod4_master/ and onap_daily_pod4_honolulu/ result sections. Update today's date. As of today , there is an issue with the Honolulu gating. It has not ran in over a month or so. Frankfurt and Guilin gating has not ran in some time, so we can ignore these.
This is an example of the health-check for all branches report. If the policy healthcheck is failing, click on the link. There are two healthchecks in policy → Enhanced Policy New Healthcheck and the Basic Policy Health Check. If one is failing, click to link to find the cause and report it in the scrum call.
2. Jenkins Jobs: To check the jenkins jobs follow this link → https://jenkins.onap.org/view/policy/. From here, sort the jobs to see failing jobs first (in red). Update the date to today's date.
Ctril + F to find all the stage jobs. Staging jobs can be ignored during this process. Report the remaining jobs in the policy scrum call.
...