Jan 12, 2010, 11:55:27 PM (14 years ago)
Merged in changes from trunk

--- Merging r1262 through r1413 into 'deploy/bin':
U    deploy/bin/django
   C deploy/bin/rails
   > Resolved by accepting working copy
--- Merging r1221 through r1413 into '.':
U    sql/bin/get-password
U    sql/bin/save-password
U    doc/tickets/rt.txt
U    doc/tickets/cnames.txt
U    bin/fix-php-ini
   C bin/scripts-rails
   > Resolved by accepting working copy
Skipped 'bin/for-each-server'
 U   bin
U    sbin/parallel-find.pl
U    sbin/commit-email.pl
U    sbin/commit-zephyr
Summary of conflicts:
  Tree conflicts: 2
  Skipped paths: 1

2 edited


  • branches/locker-dev/locker

  • branches/locker-dev/locker/doc/tickets/rt.txt

    r1026 r1414  
    1010yourself of own updates" is on. You can also set the "Default Working Queue"
    1111to Scripts, and give yourself a signature referring to scripts@mit.edu.
    12 Another useful option here is to set a password, so you don't need certs to
    13 log in (and so you can use the zephyrbot).
    15 The zephyrbot (currently down) will take commands to -c scripts -i [ticket
    16 number] of the form /set status=resolved or /set owner=geofft.
     13Another useful option here is to set an RT passwordfor your account, so you
     14don't need certs to log in (though it sometimes will keep asking you for
     15your password on each page load if you don't have certs) and so you can use
     16the zephyrbot).  The zephyrbot will take commands to
     17-c scripts -i [ticket number] of the form /set status=resolved or
     18/set owner=geofft.  You need to drop a file in
     19/mit/geofft/web_scripts/rt/rt-passwords by your username with the format:
     21"username" "yourawesomepassword"
     23And then ask geofft (zwrite geofft) to restart the RT bot.
     25Note that in the event that Geoff's account is compromised, it is possible
     26for an attacker to use this password do manipulate tickets in *any*
     27queue you have bits on, not just the Scripts one.
     29The RT bot will post ticket notifications as -c scripts -i nnn.  If you are
     30responding to a ticket, it is conventional to post "lock" to the appropriate
     31instance, so others know not to pre-empt you.  You should post "unlock" once
     32you are done handling the ticket.
    1834You can also place these commands on a line by themselves inside e-mail; they
    1935will be acted upon and removed before the e-mail gets sent back out.
    21 Don't use the To field, it doesn't work. If you want to send the ticket somewhere else, use CC.
     37If you're adding a *comment* (such as when you're forwarding a cname request
     38on to IS&T), don't use the 'To:' field, because it'll be clobbered by our
     39RT scrips and the mail won't actually go to the destination you added.
     40Instead, you should use the 'Cc:' field.  Similarly, if you're adding
     41*correspondence*, the 'Cc:' field will be clobbered and you need to use
     42the 'To:' field.
    2344Don't CC other RT queues, it doesn't work. If you really need to, use your
Note: See TracChangeset for help on using the changeset viewer.