It's fine. I actually do not spend any time on it. Instead, I just separated it into these jobs: https://ci.bigtop.apache.org/view/Packages/job/Bigtop-trunk-packages/ https://ci.bigtop.apache.org/view/Packages/job/Bigtop-trunk-packages-aarch64/
Let's hook the aarch 64 back once the slave is stable. Evans 2017-04-18 4:45 GMT+08:00 Roman Shaposhnik <[email protected]>: > On Sun, Apr 16, 2017 at 7:56 AM, Evans Ye <[email protected]> wrote: > > I found that the link on our home page for ci is broken ( > > http://bigtop.apache.org/download.html#releases) > > Hence I changed the job name back. > > Thanks! > > > In additional, it seems that the packages job is stable enough for all > the > > platform except aarch64. It looks like there're some infra issues > > preventing the build to success. Therefore, I'd like to separate out > > aarch64 from Bigtop-trunk-packages and create a new job for it. That way > we > > get a clear view on whats going on, for both developer and user. > > The slave is pretty sick. I actually got a new slave from Linaro folks and > will try to hook it to Jenkins later this week. > > I guess what I'm trying to say is: you may be better off waiting for that > before spending any more time on aarch64 > > Thanks, > Roman. >
