You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Tzu-Li (Gordon) Tai (Jira)" <ji...@apache.org> on 2020/04/07 05:54:00 UTC
[jira] [Closed] (FLINK-16880) Adapt Dockerfiles from flink-statefun
to be added to flink-statefun-docker
[ https://issues.apache.org/jira/browse/FLINK-16880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tzu-Li (Gordon) Tai closed FLINK-16880.
---------------------------------------
Resolution: Fixed
Fixed via 3ee38250b7dd803e51fe1698f387f82cb3e5df0a.
> Adapt Dockerfiles from flink-statefun to be added to flink-statefun-docker
> --------------------------------------------------------------------------
>
> Key: FLINK-16880
> URL: https://issues.apache.org/jira/browse/FLINK-16880
> Project: Flink
> Issue Type: Task
> Components: Release System / Docker, Stateful Functions
> Reporter: Tzu-Li (Gordon) Tai
> Assignee: Tzu-Li (Gordon) Tai
> Priority: Major
> Labels: pull-request-available
> Fix For: statefun-2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The scripts under {{tools/docker/}} in the flink-statefun repo contains scripts that prepare the build context for building snapshot StateFun images that we use for development purposes.
> Those can be adapted so that they may be used for submission to the Docker Hub official images repo:
> - The build context should be readily in shape as is in the Dockerfile repo, instead of relying on a build script
> - {{statefun-flink-distribution}} and {{statefun-flink-core}} jars should be downloaded from Maven + signature verification needs to be performed
> - We need some tooling in place that allows us to automate the release workflow of adding a new version for the images. We should be able to adapt those from the existing Flink Dockerfiles repo.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)