Bryan Pendleton <[email protected]> writes: > On 5/19/2015 7:50 PM, Myrna van Lunteren wrote: >> I could see the output by going to the derby builds overview >> (https://builds.apache.org/view/A-D/view/Derby/) > > Thanks Myrna, that works for me, too. > > Perhaps the simplest thing to do is to change the links on > > http://db.apache.org/derby/manuals/index.html#javadoc > > to point to, e.g., > > > https://builds.apache.org/view/A-D/view/Derby/job/Derby-trunk/lastSuccessfulBuild/artifact/trunk/javadoc/ > > If that seems like a reasonable approach, I can do that.
The old, shorter links seem to work again now. Probably it was Myrna's rebuild that brought back the artifacts. The docs builds had the same problem. The last build didn't have any artifacts. Probably the infrastructure team automatically deletes old build artifacts after a while, and the Derby-docs build hadn't run since January, so the artifacts were quite old. I've reconfigured the Derby-docs and Derby-trunk build jobs to run once every month, even if there hasn't been a commit lately. That should hopefully be frequently enough to avoid the automatic cleanup. The build jobs will still check the Subversion repository daily and run more frequently if the code base is updated. -- Knut Anders
