Should be okay for the moment. Except we forget updating links on the wiki with jenkins changing. But I wouldn't point these to the users as 'working' documentation. We should get the corrected docs on the site.
On Thu, Oct 10, 2013 at 02:26:22PM +0200, Daan Hoogland wrote: > by latest i mean the results of jenkins doc build jobs. > > and yes I mean either copy the build results to the site or the wiki > on the one hand and just set links to the artifacts in jenkins on the > other hand. > > On Thu, Oct 10, 2013 at 2:21 PM, Prasanna Santhanam <t...@apache.org> wrote: > > By latest you mean something in those pages is outdated? I haven't > > documented all the jobs yet. > > > > I think it would be nice to add links to our community repositories > > etc. Is this what you mean by artifacts? > > > > On Thu, Oct 10, 2013 at 02:17:13PM +0200, Daan Hoogland wrote: > >> Thanks Prasanna, > >> > >> should we publish some 'latest' docs or is this not desirable? We > >> could do with links to the artifacts, i imagine. > >> > >> Daan > >> > >> On Thu, Oct 10, 2013 at 2:00 PM, Prasanna Santhanam <t...@apache.org> > >> wrote: > >> > Hi, > >> > > >> > I've added some missing documentation on how our build systems > >> > (jenkins) are setup. I think I've addressed most questions that came > >> > up in threads on this mailing list. If you would like to understand > >> > how all this is setup please go through the following wiki pages: I've > >> > put in pictures and everything :) > >> > > >> > Build systems: > >> > https://cwiki.apache.org/confluence/x/Cy-VAQ > >> > > >> > Test infrastructure: > >> > https://cwiki.apache.org/confluence/x/_y7VAQ > >> > > >> > Thanks, > >> > > >> > -- > >> > Prasanna., > >> > > >> > ------------------------ > >> > Powered by BigRock.com > >> > > > > > -- > > Prasanna., > > > > ------------------------ > > Powered by BigRock.com > > -- Prasanna., ------------------------ Powered by BigRock.com
