Daniel -- your SSH key suggestion did the trick. Thanks. On Friday, August 22, 2014 10:31:31 AM UTC-6, Daniel Beck wrote: > > There's a known issue with CLI authentication via --username not working > for some commands in Jenkins 1.538-1.576. > > Try using SSH key based authentication. > > On 22.08.2014, at 17:58, G Dameron <[email protected] <javascript:>> > wrote: > > > I think I may be on to something, and I think it's related to the issue > https://issues.jenkins-ci.org/browse/JENKINS-21086 I mentioned in my OP. > The system log responds this way when I try to to a get-job on project_B: > > > > Aug 22, 2014 9:23:07 AM WARNING > hudson.cli.handlers.GenericItemOptionHandler$1 run > > running as anonymous could not find > hudson.model.FreeStyleProject@2130a9c[project_B] of class > hudson.model.AbstractItem > > > > I still have the "login" just before it, as recommended in the issue. I > even tried (a) appending the --username and --password args to the get-job, > and even (b) opening up Overall/Read to the anonymous user, then using the > "restart" URL to restart the server. Still no joy. > > > > (Thanks, Daniel, for hanging in there through my struggle.) > > > > > > On Thursday, August 21, 2014 6:56:21 PM UTC-6, Daniel Beck wrote: > > What kind of project is it (e.g. freestyle, maven, multijob, build flow, > ...)? What plugin provides it? > > > > On 22.08.2014, at 02:31, G Dameron <[email protected]> wrote: > > > > > Just alphanumerics and underscores in the name. We're not using any > CloudBees plugins. > > > > > > On Thursday, August 21, 2014 6:14:16 PM UTC-6, Daniel Beck wrote: > > > Are there leading/trailing spaces in the project name? Characters that > are not basic printable ASCII, preferably alphanumeric, e.g. characters > with special meaning on the command line, like the dollar sign? > > > > > > Are you using the Cloudbees Folders plugin, and the job is actually in > a folder? Other than changing project names, are the java calls in your > first question unmodified (e.g. no parameters removed)? > > > > > > On 22.08.2014, at 02:01, G Dameron <[email protected]> wrote: > > > > > > > The job name I'm using meets the URL criterion. (It also meets the > "snowman" criterion, which implies the job's "real name" and "display name" > are identical, if I'm understanding you correctly). Is there any other > string I could/should use for the get-job argument? > > > > > > > > On Thursday, August 21, 2014 5:43:33 PM UTC-6, Daniel Beck wrote: > > > > 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. > > > > > > -- > > 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] <javascript:>. > > 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.
