-
Notifications
You must be signed in to change notification settings - Fork 38
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
Refine testing GitHub Action workflow dispatch functionality #2816
Open
5 of 20 tasks
JohnHalleyGotway opened this issue
Feb 23, 2023
· 2 comments
· Fixed by #2818 · May be fixed by #2829
Open
5 of 20 tasks
Refine testing GitHub Action workflow dispatch functionality #2816
JohnHalleyGotway opened this issue
Feb 23, 2023
· 2 comments
· Fixed by #2818 · May be fixed by #2829
Labels
component: testing
Software testing issue
priority: medium
Medium Priority
reporting: NRL METplus
Naval Research Laboratory METplus Project
type: enhancement
Improve something that it is currently doing
Comments
JohnHalleyGotway
added
type: enhancement
Improve something that it is currently doing
component: testing
Software testing issue
priority: medium
Medium Priority
alert: NEED ACCOUNT KEY
Need to assign an account key to this issue
labels
Feb 23, 2023
JohnHalleyGotway
changed the title
Refine testing workflow dispatch GitHub Action
Refine testing GitHub Action workflow dispatch functionality
Feb 23, 2023
Does this issue belong in the METplus repository? |
For (1): I believe this code gets the main_vX.Y truth data for branches that contain main_vX.Y in the name, otherwise it uses develop. For (2): It looks like |
JohnHalleyGotway
added
the
alert: NEED CYCLE ASSIGNMENT
Need to assign to a release development cycle
label
Oct 3, 2024
JohnHalleyGotway
removed
alert: NEED ACCOUNT KEY
Need to assign an account key to this issue
alert: NEED CYCLE ASSIGNMENT
Need to assign to a release development cycle
labels
Nov 11, 2024
georgemccabe
added
the
reporting: NRL METplus
Naval Research Laboratory METplus Project
label
Dec 9, 2024
georgemccabe
added a commit
that referenced
this issue
Dec 9, 2024
…ay the repo that triggered the workflow on workflow_dispatch events. Preserve the behavior of pull_request and push events by displaying the PR title or head commit message respectively
16 tasks
github-project-automation
bot
moved this to 🩺 Needs Triage
in METplus-Wrappers-6.1.0 Development
Dec 11, 2024
georgemccabe
moved this from 🩺 Needs Triage
to 🔎 In review
in METplus-Wrappers-6.1.0 Development
Dec 11, 2024
georgemccabe
added a commit
that referenced
this issue
Dec 13, 2024
* per #2816, update title of workflow displayed in Actions tab to display the repo that triggered the workflow on workflow_dispatch events. Preserve the behavior of pull_request and push events by displaying the PR title or head commit message respectively * fix logic for run-name * Update event info to note that the workflow was triggered manually if the repo/title was not provided. Update description of workflow_dispatch argument to describe what it can be used for when triggering manually. Only run step to build URL to commit that triggered workflow if it was triggered from an external repo * add optional argument for workflow_dispatch to specify the title of the workflow run * revert change to repository argument description since title argument was added to handle custom workflow run titles
georgemccabe
added a commit
that referenced
this issue
Dec 13, 2024
* per #2816, update title of workflow displayed in Actions tab to display the repo that triggered the workflow on workflow_dispatch events. Preserve the behavior of pull_request and push events by displaying the PR title or head commit message respectively * fix logic for run-name * Update event info to note that the workflow was triggered manually if the repo/title was not provided. Update description of workflow_dispatch argument to describe what it can be used for when triggering manually. Only run step to build URL to commit that triggered workflow if it was triggered from an external repo * add optional argument for workflow_dispatch to specify the title of the workflow run * revert change to repository argument description since title argument was added to handle custom workflow run titles
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
component: testing
Software testing issue
priority: medium
Medium Priority
reporting: NRL METplus
Naval Research Laboratory METplus Project
type: enhancement
Improve something that it is currently doing
Describe the Enhancement
This was intially discussed during the METplus 5.0 Release Retrospective. In GitHub actions for METplus the testing.yml workflow has a
workflow dispatch
feature. This enable you to manually trigger runs of that workflow for any feature branch you choose. This issue is to enhance that functionality in 2 ways:Specify the reference branch. All manually triggered workflow runs are diffed against the
develop-ref
truth data. Enhance this to let the user pick the reference truth dataset (i.e.develop-ref
,main_v11.0-ref
, and so on). Alternatively, you could enhance the script logic to automatically pick the right reference dataset.Improve the GHA run name. Currently, all manually triggered testing workflow runs are simply named
Testing
, like this:Enhance this to include the name of the branch being run at a minimum. Consider also including the reference dataset name, if that's made to be configurable.
Remember to migrate this functionality to the other METplus repos.
Time Estimate
1 day?
Sub-Issues
Consider breaking the enhancement down into sub-issues.
None needed.
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
NRL METplus 7730022
Define the Metadata
Assignee
Labels
Projects and Milestone
Define Related Issue(s)
Consider the impact to the other METplus components.
Once happy with these changes, recommend migrating them to the other METplus repos as well.
Enhancement Checklist
See the METplus Workflow for details.
Branch name:
feature_<Issue Number>_<Description>
Pull request:
feature <Issue Number> <Description>
Select: Reviewer(s) and Development issues
Select: Repository level development cycle Project for the next official release
Select: Milestone as the next official version
The text was updated successfully, but these errors were encountered: