Good point. Thanks Gian. I think we can use https://dist.apache.org/repos/dist/dev/druid/nightly/. It looks that Nexus repository manager is not available for https://builds.apache.org/. So, the Jenkins job would create a nightly build and overwrite the artifact on https://dist.apache.org/repos/dist/dev/druid/nightly/. Does it make sense?
Jihoon On Thu, Aug 9, 2018 at 6:39 PM Gian Merlino <g...@apache.org> wrote: > I found http://www.apache.org/legal/release-policy.html#host-rc which > looks > like the policy we should follow if we start doing nightly builds. I guess > we shouldn't archive nightly builds, since there would be too many. > > On Thu, Aug 9, 2018 at 6:02 PM Jihoon Son <jihoon...@apache.org> wrote: > > > Hi all, > > > > Nightly build would be useful for folks who want to stay on the bleeding > > edge of Druid. I'm thinking to add a Jenkins job to > > https://builds.apache.org/ which checks every hour that there are > changes > > in the master branch and builds a new build. Once the build succeeds, the > > binary is archived, so that we can add a link to the binary to our web > > page. If the build fails, the notification would be sent to > > comm...@druid.apache.org. > > > > Welcome any thoughts. > > > > Best, > > Jihoon > > >
