Catch all issue to improve the BM routine
Update the BM documentation so that the existing BM sends a report to the eng@ describing:
- what's the status of the builds
- what's red and why
- make sure all the breaks are tracked
- add a screenshot of the BM dashboard
The new buildmeister responds to the email acknowledging that things are clear.
When running dev_scripts_helpers/update_devops_packages/notebooks/Master_buildmeister_dashboard.ipynb
@dremdem @gpsaggese
repo_list = [
"cryptokaizen/cmamp",
"cryptokaizen/orange",
"cryptokaizen/lemonade",
"causify-ai/kaizenflow",
]
workflow_df = hlitagh.gh_get_details_for_all_workflows(repo_list)
# Reorder columns.
columns_order = ["repo_name", "workflow_name", "conclusion", "url"]
workflow_df = workflow_df[columns_order]
# Make URL values clickable.
workflow_df["url"] = workflow_df["url"].apply(make_clickable)
_LOG.info(hpandas.df_to_str(workflow_df, log_level=logging.INFO))
Output:
==
'5'
Continuing as per user request with only_warning=True
WARNING Not enough runs to compute status for 'Test GH Action permission - Superslow tests', repo 'cryptokaizen/cmamp', skipping the workflow
WARNING * Failed assertion *
'0'
==
'5'
Continuing as per user request with only_warning=True
WARNING Not enough runs to compute status for 'Test GH Action permission - Test coverage', repo 'cryptokaizen/cmamp', skipping the workflow
WARNING * Failed assertion *
'0'
==
'5'
Continuing as per user request with only_warning=True
WARNING Not enough runs to compute status for 'Test OIDC', repo 'cryptokaizen/cmamp', skipping the workflow
WARNING * Failed assertion *
'0'
==
'5'
Continuing as per user request with only_warning=True
WARNING Not enough runs to compute status for 'Tests base with Slack', repo 'cryptokaizen/cmamp', skipping the workflow
PR: https://github.com/causify-ai/helpers/pull/763
When running
It's usual behavior.
Take a look: https://github.com/causify-ai/helpers/blob/0387ed7fa93653b9ca98396fb3580a7fa7a19ba3/helpers/lib_tasks_gh.py#L642-L659
-
The email is: https://docs.google.com/document/d/1eZikNlvqrbOjmrukNtlaCkHyhh-hBAJqpNAURAucKW8/edit?tab=t.0
-
We should create a Gdoc in https://drive.google.com/drive/folders/1u53FGm3X5zcAcmAYUAN3vByvYuvoNgv- where everybody can publish the emails and we can keep a log
We should create a Gdoc in https://drive.google.com/drive/folders/1u53FGm3X5zcAcmAYUAN3vByvYuvoNgv- where everybody can publish the emails and we can keep a log
So we should mail to @eng and paste the emails here in the doc every morning?
@gpsaggese https://docs.google.com/document/d/1eZikNlvqrbOjmrukNtlaCkHyhh-hBAJqpNAURAucKW8/edit?tab=t.0
- Can you review the mail and we can start with the routine asap
Doc to log emails: https://docs.google.com/document/d/12fm9068JwAEHjn2CE1H29cV9R7plAD_4NAGLoZJoBrY/edit?usp=sharing
@gpsaggese We can close the issue if the process is working well?
Lets leave this issue until: - https://github.com/causify-ai/csfy/issues/6204 - https://github.com/causify-ai/csfy/issues/5870