GitHub user 1ambda reopened a pull request:
https://github.com/apache/zeppelin/pull/2318
[ZEPPELIN-2492] Use single Dockerfile for each tag
### What is this PR for?
Use single `Dockerfile` for each release since [apache infra uses tag
pushes](https://issues.apache.org/jira/browse/INFRA-12781) to build an image.
- https://issues.apache.org/jira/browse/INFRA-12781
After release process finishes, dockerhub will build using the pushed tag.
### What type of PR is it?
[Bug Fix | Improvement | Feature | Documentation | Hot Fix | Refactoring]
### Todos
* [ ] - Task
### What is the Jira issue?
[ZEPPELIN-2492](https://issues.apache.org/jira/browse/ZEPPELIN-2492)
### How should this be tested?
1. `./dev/change_zeppelin_version.sh 0.8.0-SNAPSHOT 0.7.1`
2. Check that version is properly set: `vi
scrtips/docker/zeppelin/bin/Dockerfile`
3. Build docker image `cd scripts/docker/zeppelin/bin; docker build -t
zeppelin:0.7.1 ./`
4. Run the image: `docker run -p 8080:8080 --rm --name zeppelin
zeppelin:0.7.1`
### Screenshots (if appropriate)
NONE
### Questions:
* Does the licenses files need update? - NO
* Is there breaking changes for older versions? - NO
* Does this needs documentation? - NO
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/1ambda/zeppelin
ZEPPELIN-2492/use-single-dockerfile-for-each-tag
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2318.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2318
----
commit 5826c8ccb71cd737df3dc9f680c421ab681529d5
Author: 1ambda <[email protected]>
Date: 2017-05-04T07:26:55Z
fix: Use single dockerfile for tag push
commit 483bec35eb2dc043d27f36aa175f1234d1ed0756
Author: 1ambda <[email protected]>
Date: 2017-05-04T07:29:13Z
docs: Update README for Dockerfile
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
