prepare-ChangeLog -b does not know how to use bugzilla credentials

• Component: Tools / Tests
• Status: NEW ---

[Eric Seidel (no email)]

prepare-ChangeLog -b does not know how to use bugzilla credentials

This means it falls on its face if using -b with a non-public (security) bug:
prepare-ChangeLog -o -b 28755

Use of uninitialized value in substitution (s///) at /Users/eseidel/Projects/WebKit/WebKitTools/Scripts/prepare-ChangeLog line 1610.
Use of uninitialized value in substitution (s///) at /Users/eseidel/Projects/WebKit/WebKitTools/Scripts/prepare-ChangeLog line 1611.
Use of uninitialized value in substitution (s///) at /Users/eseidel/Projects/WebKit/WebKitTools/Scripts/prepare-ChangeLog line 1612.
Use of uninitialized value in substitution (s///) at /Users/eseidel/Projects/WebKit/WebKitTools/Scripts/prepare-ChangeLog line 1613.
Use of uninitialized value in substitution (s///) at /Users/eseidel/Projects/WebKit/WebKitTools/Scripts/prepare-ChangeLog line 1614.
Use of uninitialized value in concatenation (.) or string at /Users/eseidel/Projects/WebKit/WebKitTools/Scripts/prepare-ChangeLog line 262.
  Description from bug 28755:
    "".

If we ever end up moving it to python, the bugzilla.py module already handles authentication like this.

[BJ Burg]

*** Bug 35901 has been marked as a duplicate of this bug. ***

[BJ Burg]

Dan/Dave/someone, do you think we could hook this up by calling into python from prepare-Changelog as a fallback? I am not sure whether this will work on all configurations, but it's probably the only realistic solution in the short-term.

The following prints the expected (security) bug title to stdout, and dumps the useless webkitpy warning about logging not being set up:

python -c "from webkitpy.common.net.bugzilla import Bugzilla; bz = Bugzilla(); b = bz.fetch_bug(136715); print(b.title())" 2> /dev/null