-
Notifications
You must be signed in to change notification settings - Fork 8
Add a milestone CLOSED validator #229
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
__main__.py
Outdated
| handle_bitrise_builds, | ||
| ) | ||
|
|
||
| """ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
commenting this out for now only because its throwing an error locally
__main__.py
Outdated
| 'bugzilla-meta-bugs': handle_bugzilla_meta_bugs, | ||
| 'bugzilla-qe-verify': handle_bugzilla_qe_verify, | ||
| 'bugzilla-query-by-keyword': handle_bugzilla_query_by_keyword, | ||
| #'bugzilla-desktop-bugs': handle_bugzilla_desktop_bugs, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same as above
api/testrail/report_milestones.py
Outdated
| pl.extract_build_version | ||
| ) | ||
|
|
||
| import sys |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DIAGNOSTIC only
|
|
||
|
|
||
| def handle_testrail_milestones_closed(args): | ||
| milestone_validate_closed = True |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doing it this way, we don't have to make the COMMAND_MAP more complex with additional input params. We simply use a different function name and pass in an optional variable which will trigger an alternate path for the report module we already have in place for milestones
api/testrail/report_milestones.py
Outdated
| # =================================================================== | ||
|
|
||
| def report_milestones_insert(projects_id, payload): | ||
| def _db_upsert(projects_id, payload): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
upsert is a stand name for an insert / update / upload operation.
| # =================================================================== | ||
|
|
||
| def testrail_milestones(project): | ||
| def run(project, milestone_validate_closed: bool = False): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is only 1 entry point to this module (and all report modules). Standard practice in this case is to use an entry function called: run.
Other new standards here are using: _fetch for fetching external API data
and _upsert for remote update / upload / insert operations
| @@ -0,0 +1,88 @@ | |||
| name: Testops - TestRail Milestone CLOSED - polling | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
introducing a new workflow environment: demo for PRs
Once the PR has passed review, demo can change to either staging or production
Purpose
The purpose of this PR is to add a TestRail Milestone CLOSED trigger. i.e. When someone closes a Milestone, some follow on actions would be performed.
Follow-on Actions
Notes
ChatGPT