Last modified: 2014-05-29 00:36:00 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T64340, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62340 - Include commit hash for every synch
Include commit hash for every synch
Status: NEW
Product: Wikimedia
Classification: Unclassified
Deployment systems (Other open bugs)
wmf-deployment
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-06 19:32 UTC by Greg Grossmeier
Modified: 2014-05-29 00:36 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Greg Grossmeier 2014-03-06 19:32:16 UTC
Sometimes we just see, eg:
22:58 logmsgbot: ebernhardson synchronized php-1.23wmf15/extensions/Flow/

Where others give more information:
00:17 logmsgbot: ori synchronized php-1.23wmf16/extensions/CentralNotice 'Update CentralNotice to tip of wmf_deploy for I7d8259fc4'

The easy bit of extra info that could be included automatically is the hash associated with the latest commit for what is being sync'd.
Comment 1 Bryan Davis 2014-05-29 00:36:00 UTC
(In reply to Greg Grossmeier from comment #0)
> The easy bit of extra info that could be included automatically is the hash
> associated with the latest commit for what is being sync'd.

1) Do we want to exclude the hash entirely if the HEAD is a security patch or should it show the latest origin commit?

2) How would you like the message to be formatted? "Synchronized <path> <hash>: <message>" or maybe "Synchronized <path>: <message> (<hash>)"?

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links