One thing that i've learned through a couple of projects is that the more we can move into the projects repo for build/test/release scripts along with release verification helps immensely and reduces any behind the scenes magic and also enables others in the community to be involved with these scripts or run them in their own environments. Apache Aurora is a good example of this setup that comes to mind
-Jake On Thu, Apr 5, 2018 at 2:56 PM, Ali Ahmed <a.ah...@streaml.io> wrote: > Understood we need to start granting access to these rosaries , so the > current build scripts can be ported. > > -Ali > > > On Apr 5, 2018, at 11:44 AM, Ning Wang <wangnin...@gmail.com> wrote: > > > > Cool. Thanks! > > > > On Thu, Apr 5, 2018 at 11:39 AM, Jake Farrell <jfarr...@apache.org> > wrote: > > > >> Hey Ali > >> The ASF Jenkins build system is at https://builds.apache.org/ and setup > >> details are available at > >> https://cwiki.apache.org/confluence/display/INFRA/Jenkins . We can not > >> create release artifacts on those servers as they must go through a > voting > >> process. We can as part of a release candidate stage artifacts like jars > >> using the Apache Nexus repository and after a successful vote publish > those > >> jars which automatically get picked up and mirrored to Maven central > from > >> https://repository.apache.org/. > >> > >> If you have any other questions please let us know > >> -Jake > >> > >> On 2018/04/02 21:36:19, Ali Ahmed <a.ah...@streaml.io> wrote: > >>> I have currently mananging the heron releases for the last few months > >> via a local jenkins instance, as part of apache incubation I need > guidance > >> on transition to an official build and release pipeline possibly on > infra > >> managed by apache org. > >>> > >>> Can someone forward me to point of contact or documentation for this > >> process. > >>> > >>> Thanks > >>> -Ali > >> > >
