| Table of Contents |
|---|
...
2. Check all scheduled jobs status: Map jobs = [
Karate: https://jenkins-aws.indexdata.com/job/Testing/job/Scheduled%20Karate%20Tests/
Cypress: https://jenkins-aws.indexdata.com/job/folioRancher/job/folioScheduledTesting/job/runNightlyCypressTests/
MamagePods: https://jenkins-aws.indexdata.com/job/folioRancher/job/folioNamespaceTools/job/managePods/
createDailySnapshotECS: https://jenkins-aws.indexdata.com/job/folioRancher/job/folioNamespaceTools/job/createDailySnapshotECS/
] → Jenkins pipelines views
2. Monitor & respond to All incoming requests: Slack & Teams
3. Prepare a list of created tasks during shift day
4. Announce previously created tasks list on a daily standaUp
5. Rancher: check at least twice a day the statuses of environments
6. Monitor MSTeams chats: Map chats = [
chat_name_1: 'FOLIO - cypress tests in CI'
chat_name_2: 'Sprint testing env questions'
]
7. AWS infra: Kafka, RDS, OpenSearch (check statuses: CPU, RAM, etc.) at the beginning of shift working day
8. Jenkins: check slaves at the beginning of the shift working day for any technical issues: Status, Free space, availability | us-east-1 AWS region
9. Create a Jira ticket for any implementation incoming requests & share its' number with the reporter (if any)
10. ReportPortal: review the last scheduled tests results, analyze and perform initial investigation & inform the responsible team about the issue
11.Update sprint testing environment | 1st priority item, when shift started! | FISRT ITEM IN THE ROW!!! → (After Backend was updated, please build new UIs for the following tenants: fs09000000, cs00000int(Consortia enabled), fs09000003 via this pipeline: ui-bundle-deploy