During the METplus 6.0.0 beta4 development cycle, a SonarQube scanning workflow (.github/workflows/sonarqube.yml) was added to the METplus repositories. While the MET logic is complex and requires running the SonarQube build wrapper in a Docker container, the logic for the Python-based METplus repositories is straight-forward. As of beta4, the same set of 5 workflow steps (checkout, branch name, configure, run scan, check quality gate) is repeated in the METplus, METplotpy, METcalcpy, and METdataio repositories. Note that the SonarQube workflow has not yet been added to METviewer, and the logic for doing so has not yet beed defined.
This issue is define a custom action in a new dtcenter/metplus-action-sonarqube repository. That action should perform the 5 steps defined above: checkout, branch name, configure, run scan, check quality gate
Then update the existing sonarqube.xml workflows to call that custom action instead. This should provide a more maintainable solution.
Time Estimate
2 days.
Sub-Issues
Consider breaking the enhancement down into sub-issues.
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
METplus Air Force key (2771024)
Define the Metadata
Assignee
[x] Select engineer(s) or no engineer required
[ ] Select scientist(s) or no scientist required
Labels
[x] Select component(s)
[x] Select priority
[x] Select requestor(s)
Projects and Milestone
[x] Select Repository and/or Organization level Project(s) or add alert: NEED CYCLE ASSIGNMENT label
[x] Select Milestone as the next official version or Future Versions
Define Related Issue(s)
Consider the impact to the other METplus components.
[ ] Submit a pull request to merge into develop.
Pull request: feature <Issue Number> <Description>
[ ] Define the pull request metadata, as permissions allow.
Select: Reviewer(s) and Development issues
Select: Repository level development cycle Project for the next official release
Select: Milestone as the next official version
[ ] Iterate until the reviewer(s) accept and merge your changes.
Describe the Enhancement
During the METplus 6.0.0 beta4 development cycle, a SonarQube scanning workflow (
.github/workflows/sonarqube.yml
) was added to the METplus repositories. While the MET logic is complex and requires running the SonarQube build wrapper in a Docker container, the logic for the Python-based METplus repositories is straight-forward. As of beta4, the same set of 5 workflow steps (checkout, branch name, configure, run scan, check quality gate) is repeated in the METplus, METplotpy, METcalcpy, and METdataio repositories. Note that the SonarQube workflow has not yet been added to METviewer, and the logic for doing so has not yet beed defined.This issue is define a custom action in a new
dtcenter/metplus-action-sonarqube
repository. That action should perform the 5 steps defined above: checkout, branch name, configure, run scan, check quality gateThen update the existing
sonarqube.xml
workflows to call that custom action instead. This should provide a more maintainable solution.Time Estimate
2 days.
Sub-Issues
Consider breaking the enhancement down into sub-issues.
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
METplus Air Force key (2771024)
Define the Metadata
Assignee
Labels
Projects and Milestone
Define Related Issue(s)
Consider the impact to the other METplus components.
Enhancement Checklist
See the METplus Workflow for details.
feature_<Issue Number>_<Description>
feature <Issue Number> <Description>