Re: Build machine provisioning and release access

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

Re: Build machine provisioning and release access

Cool. Thanks! On Thu, Apr 5, 2018 at 11:39 AM, Jake Farrell 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

Re: Build machine provisioning and release access

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

Build machine provisioning and release access

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