If it says '/job/foo' in the URL when you view the job, 'foo' is its name. Even if it says something like "Project ☃" on the page you're on, in that case '☃' is its display name. (That character used for the display name is supposed to be the Unicode snowman U+2603 if your email client doesn't display it.)
To the best of my knowledge, there is no way to determine a project's name from the CLI if the project has a differing display name and the name is not already known, short of writing a plugin or patching Jenkins. On 22.08.2014, at 01:33, G Dameron <[email protected]> wrote: > What does a job's "real name" look like? > Is there a string I can build up from known parts that would convince > "get-job" that it's a legitimate argument? > > On Thursday, August 21, 2014 5:09:28 PM UTC-6, Daniel Beck wrote: > It's likely the following: > > list-jobs shows the project's _display name_, but as parameter to commands > you need to specify the project's real _name_. > > It's mind-bogglingly stupid, and there is currently no solution other than > not using display names for projects, or patching Jenkins. > > A possible solution is tracked as JENKINS-22301. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
