TRS Code Incorrectly Uses Jenkins "Build" instead of "Project" At Various Places

[piyush286]

Test Result Summary is using the Jenkins term "build" incorrectly instead of "project" in some places. So it's easy to get confused when the code might actually be referring to "project" and not the "build" in various places.

Sorry to be pedantic. I know it's not a big deal but it's would be good to update the wrong references so that it's easier to understand and maintain the code.

Terminology

https://jenkins.io/doc/book/glossary/

Project A user-configured description of work which Jenkins should perform, such as building a piece of software, etc. Example: PerfNext-Pipeline, Grinder, Daily-ODM

Build: Result of a single execution of a Project Example: Different Builds: 1, 2, ..., 99, 100...

Job A deprecated term, synonymous with Project.

Some references that should use "project" instead of "build":

TRSS

• BuildMonitor.js (File Name)
• EventHandler.js (Function Name: monitorBuild())
• getTopLevelBuildNames.js (File Name & var: "buildName")
• getBuildHistory.js (File Name)

TRSC

• TopLevelBuilds.jsx (/api/getBuildHistory?buildName=${buildName}&url=${url} & builds[url][buildName] in updateData())

MongoDB

• buildList (Collection Name)

[piyush286]

FYI @llxia @sophiaxu0424