如何使用MKS CLI列出指定版本开发路径的所有成员及对应版本号

You’re totally on the right track with si rlog—it’s exactly the command you need to pull the member list and their corresponding versions for a specific development path revision. Let’s break down the exact syntax and parameters to get you the output you want:

si rlog --project="<your-dev-path-name>" --revision="<target-version>" --recurse --fields=name,rev --noHeader

Let’s unpack each part so you understand what’s doing what:

• --project="<your-dev-path-name>": Replace this with the full path/name of your target development path (wrap it in quotes if the path includes spaces).
• --revision="<target-version>": Specify the exact version of the development path you’re inspecting—this can be a semantic version like 1.4, a label like RELEASE_Q3, or a changelist number.
• --recurse: This ensures the command traverses all subdirectories under the development path, not just top-level files.
• --fields=name,rev: Filters the output to only show two key pieces of info: each member’s full path/name and its specific revision tied to the development path version you specified.
• --noHeader: Optional but useful—it strips out the default column headers, giving you cleaner, more parsable output.

Example Output #

If you run this for a development path /MyProject/LoginFeature at version 1.2, your output will look something like:

/MyProject/LoginFeature/src/login.c,1.5
/MyProject/LoginFeature/src/auth.h,1.3
/MyProject/LoginFeature/tests/login_test.sh,1.2

Want More Details? #

If you need additional metadata (like a member’s status or last modified date), just add more fields to the --fields parameter. For example:

si rlog --project="/MyProject/LoginFeature" --revision="1.2" --recurse --fields=name,rev,status,modifiedDate

A quick check: Make sure your development path name and version match the casing used in your MKS repository—most setups are case-sensitive, so mismatched casing can lead to empty results.

内容的提问来源于stack exchange，提问作者E.S.