-
Bug
-
Resolution: Not A Defect
-
Minor
-
None
First, do not take these request as fixed, we should find a clear naming and stick to it in all places in order to improve the user experiece and facilitate hudson adoption.
Here are some of the inconsistencies I found:
- job versus project
- build (action), may not be the best because not every thing you run or execute on hudson is a build.
- node versus slave
We already have a page at http://wiki.jenkins-ci.org/display/JENKINS/Terminology but this is incomplete and reading it doesn't help too much.
A good terminology should also include a list of `old terms`, terms that are outdated and to be replaced by newer variants.
- is duplicated by
-
JENKINS-1968 "Project" or "Job"?
-
- Resolved
-
- is related to
-
JENKINS-31095 2.0: Jenkins terminology sweep
-
- Open
-
Projects are a kind of Job (or Item now). Before you create "something", its kind is unknown, so the label is "New Item". After you've created a project, its kind is known, so it says "Delete Project".
Build: Jenkins is primarily for building software projects. There's no inconsistency just because you misuse it as a cron replacement. That being said, many places call it 'Run' (Run is to Job like Build is to Project). Due to technical limitations and backwards compatibility concerns, this isn't universal.
Node and Slave are mostly consistent: Jenkins itself is the master node, all others are slave nodes.
------
Issue needs to be updated for current Jenkins versions and specific issues with terminology.