tag | 04b61de5f33e0cd389026ba0f30dca4984e2c105 | |
---|---|---|
tagger | Ivan Kelly <ivank@apache.org> | Tue Apr 02 10:58:21 2019 +0200 |
object | 5e9828b795d7ef82c17f72a6c9efb6d0e0b4c8d7 |
Release 4.8.2 Docker Based on tag release-4.8.2
commit | 5e9828b795d7ef82c17f72a6c9efb6d0e0b4c8d7 | [log] [tgz] |
---|---|---|
author | Ivan Kelly <ivank@apache.org> | Mon Apr 01 14:19:49 2019 +0200 |
committer | Ivan Kelly <ivank@apache.org> | Mon Apr 01 14:29:23 2019 +0200 |
tree | 55b3f55aa153afe25746ccb2dabfc22a32af00c8 | |
parent | f6adb282f88ab56afa3ef33b15d7acaf4b307eef [diff] |
Docker autobuild hook This hook will allow docker autobuild to build from the offical tag and removes the need to update the dockerfile after the release has been made. It also adds a build arg, DISTRO_URL which can be used for testing release candidates. ``` docker build --build-arg BK_VERSION=4.9.1 --build-arg DISTRO_URL=<rc-tarball-url> . ``` Reviewers: Enrico Olivelli <eolivelli@gmail.com>, Sijie Guo <sijie@apache.org> This closes #2017 from ivankelly/docker-tag2 (cherry picked from commit 4573285db9e027416bf33ab9b959b952d2b0e8d5) Signed-off-by: Ivan Kelly <ivank@apache.org>
Apache BookKeeper is a scalable, fault tolerant and low latency storage service optimized for append-only workloads.
It is suitable for being used in following scenarios:
You can also read Turning Ledgers into Logs to learn how to turn ledgers into continuous log streams. If you are looking for a high level log stream API, you can checkout DistributedLog.
For filing bugs, suggesting improvements, or requesting new features, help us out by opening a Github issue or opening an Apache jira.
Subscribe or mail the user@bookkeeper.apache.org list - Ask questions, find answers, and also help other users.
Subscribe or mail the dev@bookkeeper.apache.org list - Join development discussions, propose new ideas and connect with contributors.
Join us on Slack - This is the most immediate way to connect with Apache BookKeeper committers and contributors.
We feel that a welcoming open community is important and welcome contributions.
See Developer Setup to get your local environment setup.
Take a look at our open issues: JIRA Issues Github Issues.
Review our coding style and follow our pull requests to learn about our conventions.
Make your changes according to our contribution guide.