[EnMasse] generated artifacts

[Ulf Lilleengen]

On 10. april 2017 19:45, Vanessa Busch wrote:
> Hi,
>
>   Last Friday we spoke about putting the generated artifacts into the
> jboss nexus repo.  This will work well for most of the artifacts, but it
> won't help the artifacts generated from artemis-image, and qdrouterd.

Is it not possible to store zip or tarballs there?
It is possible in the apache snapshot repository for instance: 
https://repository.apache.org/content/groups/snapshots/org/apache/activemq/apache-artemis/2.1.0-SNAPSHOT/

>   It would be great if travis-ci could hold unto the latest built
> artifacts, but I didn't see a feature for that.  It can however, upload
> them to a github release, or to github pages.
>   I was thinking of modifying the builds to upload the artifacts to
> github release.  Hopefully, travis-ci can tag it with 'latest' or
> something equivalent.  Then having the actual image scripts & Dockerfile
> (or dogen yaml file) in a separate rep (dockerfiles).  This would help
> with converting to dogen.

+1 for splitting into its own repo.

>   For those of you familiar with travis-ci, can it label the release
> 'latest'?  I would like to start with mqtt-lwt and mqtt-gateway.
>   What do you think?
>

Unfortunately, github cannot be used for latest or snapshot type of 
artifacts, only release tags. I experimented with this for the old 
configserv repo. However, my impression was that the product artifacts 
would be built on an internal CI and not the community CI, allowing 
downstream to apply patches that might not be included upstream.

I would anyway recommend to use the nexus, and hopefully one can use 
this for tarballs as well.

-- 
Ulf