infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-17294) Set up docker hub integration
Date Fri, 23 Nov 2018 05:48:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-17294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16696401#comment-16696401
] 

Allen Wittenauer commented on INFRA-17294:
------------------------------------------

Sorry, I got my terminology mixed up.

There is an option in the UI to link repositories.  apache/yetus should be using apache/yetus-base
as a repository link since apache/yetus depends upon apache/yetus-base to built first.

> Set up docker hub integration
> -----------------------------
>
>                 Key: INFRA-17294
>                 URL: https://issues.apache.org/jira/browse/INFRA-17294
>             Project: Infrastructure
>          Issue Type: New Feature
>          Components: Docker
>            Reporter: Allen Wittenauer
>            Assignee: Chris Lambertus
>            Priority: Major
>
> The Apache Yetus project would like to set up two Docker hub repos, preferably using
the automatic bits. The two repos should be:
> apache/yetus-base
> * generated from /precommit/src/main/shell/test-patch-docker/Dockerfile
> apache/yetus
> * generated from /Dockerfile 
> * should also use apache/yetus-base updates as a trigger
> For Docker tags, we do not want 'latest' or branch tags. Instead, we'd like for:
> master -> master (git head of master branch) 
> (tag)  -> rel/(tag)  (git release tags)
> Hopefully, this makes sense. :)  Is this possible to set up?   We are in the process
of updating our documentation to make note that these are for convenience and should not be
taken as official releases.
> Thanks!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message