I googled how travis supports publish snapshot artifacts onto sonatype
repository, and I think we could try this gist [1].. Travis CI blog also
has one good article on maven publish but it's for packagecloud [2].
-Ian.
1. https://gist.github.com/letmaik/4060735
2.
I think any CI system can do publish. the only thing is how to manage the
secret we use in third party CI system.
Travis CI has a document related to this
https://docs.travis-ci.com/user/best-practices-security/
On 2018/08/23 19:59:44, Mark Thomas wrote:
> On 23/08/18 11:26, Huxing Zhang
On 23/08/18 11:26, Huxing Zhang wrote:
> Hi,
>
> On Thu, Aug 23, 2018 at 12:54 PM Ian Luo wrote:
>>
>> I'm not quite sure if it's done, but what I suggest is, if it's not done
>> yet, we should consider to add instruction in .travis.yaml to publish all
>> artifacts to snapshot repository every
Hi,
On Thu, Aug 23, 2018 at 12:54 PM Ian Luo wrote:
>
> I'm not quite sure if it's done, but what I suggest is, if it's not done
> yet, we should consider to add instruction in .travis.yaml to publish all
> artifacts to snapshot repository every time when CI passes, to make
> everyone's life
+1.
On Thu, Aug 23, 2018 at 12:54 PM Ian Luo wrote:
> I'm not quite sure if it's done, but what I suggest is, if it's not done
> yet, we should consider to add instruction in .travis.yaml to publish all
> artifacts to snapshot repository every time when CI passes, to make
> everyone's life
I'm not quite sure if it's done, but what I suggest is, if it's not done
yet, we should consider to add instruction in .travis.yaml to publish all
artifacts to snapshot repository every time when CI passes, to make
everyone's life easier.
I filed
