Majic Projects
Scripts Timeline
October 04, 2013
feature_request_tiny.png 09:39  Feature request SCR-8 - Implement logging for crlpublisher.sh
branko (branko):
Issue created
Currently the CRL publisher script is very hard to debug in case of random failures. It would be a very good idea to implement logging for the script in order to more easily debug any issues that may happen during runtime.
August 27, 2013
feature_request_tiny.png 07:29  Feature request SCR-7 - Add colour support to MySQL database backup script
branko (branko):
Issue created
It would be useful to integrate the new message colouring into the MySQL database back-up script.
enhancement_tiny.png 07:29  Enhancement SCR-6 - Simplify MySQL back-up script
branko (branko):
Issue created
It would be beneficial to simplify the MySQL back-up script by removing the mail-sending logic from it. Instead of that, the administrator should rely on the default cronjob-based mail sending (i.e. if there's any error output coming from the script, cronjob will send out a notification).
August 16, 2013
feature_request_tiny.png 18:18  Feature request SCR-5 - Implement Mercurial hook for validating format of a commit message
branko (branko):
Issue created
It would be useful to have a Mercurial hook that could be used for validating the format of a commit message. The hook should be usable both on the client and server side. In particular, the hook should be usable as:

- pretxncommit hook
- pretxnchangegroup hook

The hook should be configurable through hgrc, where a regexp can be specified for valid message. The configuration should be available in section hg_commit_message. Available parameters should be:

- format
July 19, 2013
feature_request_tiny.png 14:40  Feature request SCR-4 - Implement functions for showing coloured info, success, warning, and error messages in shell script template
branko (branko):
Issue closed
July 14, 2013
feature_request_tiny.png 12:21  Feature request SCR-4 - Implement functions for showing coloured info, success, warning, and error messages in shell script template
branko (branko):
Issue created
Currently all messages in scripts based on the shell script template are using plain '''echo''' calls. It would be useful to implement a couple of wrapper functions that would print different types of messages with different colors/templates:

* info
* success
* warning
* error

In general, the output would look something like:

* [INFO] Message
* [SUCCESS] Success
* [WARN] Warning
* [ERROR] Error

The tags would be bolded and coloured. Additionally, if the script is being piped somewhere, the colour sequences should not be printed out (so you can normally grep etc), unless a special flag is passed for this purpose.
April 10, 2013
feature_request_tiny.png 09:26  Feature request SCR-2 - Implement Mercurial commit hook for The Bug Genie
branko (branko):
Issue closed
enhancement_tiny.png 09:25  Enhancement SCR-1 - gitprotect.sh should detect changes of keyring recipients when running the "encrypt" command
branko (branko):
Issue closed
enhancement_tiny.png 09:22  Enhancement SCR-3 - gitprotect.sh should require that the imported subkeys are encryption keys
branko (branko):
Issue created
Currently gitprotect.sh will happily import any sub-key provided by the user, even if the key cannot be used for encryption. Update gitprotect.sh script to only accept the encryption sub-keys instead.
feature_request_tiny.png 09:20  Feature request SCR-2 - Implement Mercurial commit hook for The Bug Genie
branko (branko):
Issue created
The current implementation of Mercurial commit hook for The Bug Genie is implemented in a bit dirty way when it comes down to http interface:

* The calls are executed using the os.system call.
* wget is passed a no-check-certificate argument.
* Doesn't produce messages that are shown back to the user (about TBG's processing)

Implement a proper hook that won't have the above problems.
enhancement_tiny.png 09:20  Enhancement SCR-1 - gitprotect.sh should detect changes of keyring recipients when running the "encrypt" command
branko (branko):
Issue created
Currently the gitprotect.sh script will only encrypt the files again if they had been changed. The scenario when a GnuPG public keyring is changed is not covered. It would be very good to have the script check if recipients have changed in the keyring, and re-encrypt the file in such case (for example when adding new users only, without changes to protected files).