| 2017-08-01 10:12:24,798 - MainThread - __main__ - INFO - Found docker images to rebuild in following order: | |
| 2017-08-01 10:12:24,798 - MainThread - __main__ - INFO - Batch 0 (10 images): | |
| 2017-08-01 10:12:24,798 - MainThread - __main__ - INFO - - rpms/jenkins-slave-base-rhel7-docker#92fa240b80c0b2c3dd8a968113add8c6947ac8f9 (based on rhel-server-docker-7.3-97) | |
| jenkins-slave-base-rhel7-docker-1.0-25 | |
| 2017-08-01 10:12:24,799 - MainThread - __main__ - INFO - - rpms/rhmap-mongodb-docker#cbe112023eb189c78d3f57ca619aa0fe0f4eca9d (based on rhel-server-docker-7.3-97) | |
| rhmap-mongodb-docker-3.2-22 | |
| 2017-08-01 10:12:24,799 - MainThread - __main__ - INFO - - rpms/jboss-openjdk-docker#16fa05cf29356061b94b9dd2097fa089d222f8f6 (based on jboss-base-rhel7-docker-1.0-8) | |
| jboss-openjdk18-rhel7-docker-1.0-10 | |
| 2017-08-01 10:12:24,799 - MainThread - __main__ - INFO - - rpms/logging-deployment-docker#e0cb6d07b5b5bbd5cfde00610b4cc776a55aff35 (based on openshift-enterprise-docker-v3.5.5.31.6-2) | |
| logging-deployment-d |
I used to use NERD tree for quite a while, then switched to CtrlP for something a little more lightweight. My setup now includes zero file browser or tree view, and instead uses native Vim fuzzy search and auto-directory switching.
There is a super sweet feature in Vim whereby you can fuzzy find your files using **/*, e.g.:
:vs **/*<partial file name><Tab>
| # The command finds the most recent tag that is reachable from a commit. | |
| # If the tag points to the commit, then only the tag is shown. | |
| # Otherwise, it suffixes the tag name with the number of additional commits on top of the tagged object | |
| # and the abbreviated object name of the most recent commit. | |
| git describe | |
| # With --abbrev set to 0, the command can be used to find the closest tagname without any suffix: | |
| git describe --abbrev=0 | |
| # other examples |
| import collections | |
| def dict_merge(dct, merge_dct): | |
| """ Recursive dict merge. Inspired by :meth:``dict.update()``, instead of | |
| updating only top-level keys, dict_merge recurses down into dicts nested | |
| to an arbitrary depth, updating keys. The ``merge_dct`` is merged into | |
| ``dct``. | |
| :param dct: dict onto which the merge is executed | |
| :param merge_dct: dct merged into dct |
