Allow make commands to be run on a single project

[cboffa13]

Description

As the project grows it takes longer to build and install all the packages when running commands like make build or make install. This PR lets us run commands for a single project like make project=project_name build so other teams dont need to wait for other projects to build if they are only working on a specific server.

For example:

• make build - runs the build command on all the folders in the src folder besides the excluded packages
• make project=oci-compute-mcp-server build builds just the compute mcp server and nothing else

Fixes # (issue)

• N/A

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Checkout this branch
• Running the make commands should still work as expected
• Running make commands with a specific project should run on that specific project
• Excluded projects should still be honored

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[irfan-ahmed]

Why not just keep it simple with

SUBDIRS := $(filter-out src/dbtools-mcp-server src/mysql-mcp-server src/oci-pricing-mcp-server src/oracle-db-doc-mcp-server,$(wildcard src/*))
SUBDIRS ?= $(filter-out src/dbtools-mcp-server src/mysql-mcp-server src/oci-pricing-mcp-server src/oracle-db-doc-mcp-server,$(wildcard src/*))

[irfan-ahmed]

You can then run the commands with the following

SUBDIRS=src/oci-api-mcp-server make build

[banderson-oracle]

The complexity here possibly seems a bit overkill, but it's also been about 16 years since I've used Make, so I can't really say much meaningful in terms of what I would suggest to make it simpler.
However, I would prefer something even more simple for consumers, like make project=compute build and have the other parts added.

[shopewf]

I think the benefit to @cboffa13's approach here is you dont have to write src/ on the start of the project you wanna build. Since the src variable was defined at the top of the Makefile to make that happen, he decided to reuse it with the other excluded_projects.

[irfan-ahmed]

There is one issue, though. If you were to run the test target using a project such as oci-cloud-guard-mcp-server where the individual coverage is less than the overall coverage figure of 69, the result is a failure, where it is actually not a failure.

 $ make project=oci-cloud-guard-mcp-server test
Testing src/oci-cloud-guard-mcp-server
warning: `VIRTUAL_ENV=/Users/irahmed/development/projects/oci-console/fork-oracle-mcp/.venv` does not match the project environment path `.venv` and will be ignored; use `--active` to target the active environment instead
========================================== test session starts ===========================================
platform darwin -- Python 3.13.7, pytest-9.0.2, pluggy-1.6.0
rootdir: /Users/irahmed/development/projects/oci-console/oracle-mcp/src/oci-cloud-guard-mcp-server
configfile: pyproject.toml
plugins: anyio-4.12.0, asyncio-1.3.0, cov-7.0.0
asyncio: mode=Mode.STRICT, debug=False, asyncio_default_fixture_loop_scope=None, asyncio_default_test_loop_scope=function
collected 7 items

oracle/oci_cloud_guard_mcp_server/tests/test_cloud_guard_tools.py .......                          [100%]

============================================ warnings summary ============================================
.venv/lib/python3.13/site-packages/pydantic/json_schema.py:2442
  /Users/irahmed/development/projects/oci-console/oracle-mcp/src/oci-cloud-guard-mcp-server/.venv/lib/python3.13/site-packages/pydantic/json_schema.py:2442: PydanticJsonSchemaWarning: Default value typing.Literal['OPEN', 'RESOLVED', 'DISMISSED', 'DELETED', 'UNKNOWN_ENUM_VALUE'] is not JSON serializable; excluding default from JSON schema [non-serializable-default]
    warnings.warn(message, PydanticJsonSchemaWarning)

-- Docs: https://docs.pytest.org/en/stable/how-to/capture-warnings.html
============================================= tests coverage =============================================
____________________________ coverage: platform darwin, python 3.13.7-final-0 ____________________________

Name                                          Stmts   Miss Branch BrPart   Cover   Missing
------------------------------------------------------------------------------------------
oracle/oci_cloud_guard_mcp_server/models.py      72     22     14      1  59.30%   16-28, 167-169, 180-183, 243-245
oracle/oci_cloud_guard_mcp_server/server.py      59     13     12      4  76.06%   29-42, 77, 78->80, 81, 141
------------------------------------------------------------------------------------------
TOTAL                                           131     35     26      5  66.88%
Coverage HTML written to dir htmlcov
Required test coverage of 64.8% reached. Total coverage: 66.88%
====================================== 7 passed, 1 warning in 1.77s ======================================
/Library/Developer/CommandLineTools/usr/bin/make combine-coverage
uv run coverage combine
Combined data file .coverage.oci-cloud-guard-mcp-server
uv run coverage html
Wrote HTML report to htmlcov/index.html
uv run coverage report --fail-under=69
Name                                                                         Stmts   Miss Branch BrPart  Cover
--------------------------------------------------------------------------------------------------------------
src/oci-cloud-guard-mcp-server/oracle/oci_cloud_guard_mcp_server/models.py      72     22     14      1    59%
src/oci-cloud-guard-mcp-server/oracle/oci_cloud_guard_mcp_server/server.py      59     13     12      4    76%
--------------------------------------------------------------------------------------------------------------
TOTAL                                                                          131     35     26      5    67%
Coverage failure: total of 67 is less than fail-under=69
make[1]: *** [combine-coverage] Error 2
make: *** [test] Error 2

[cboffa13]

yeah this is because we are combining the code coverage of all the servers. tbh i think this is a good thing and will force us to meet a minimum coverage bar

[irfan-ahmed]

Maybe if project is set, we should not combine. The failure above is a false positive. Users using this will see a failure and may start debugging it when it is not a failure, actually. That combined figure of 69 is for when we run test against all the MCP servers.