> -----Original Message----- > From: Tim Williams [mailto:william...@gmail.com] > Sent: Thursday, 15 April 2010 10:03 AM > To: dev@forrest.apache.org > Subject: Re: JIRA problems (Was: ForrestBot build for forrest-docs > FAILED) > > On Wed, Apr 14, 2010 at 1:36 PM, Andreas Lehmkuehler <andr...@lehmi.de> > wrote: > > Hi, > > > > Gav... schrieb: > >> > >>> -----Original Message----- > >>> From: David Crossley [mailto:cross...@apache.org] > >>> Sent: Wednesday, 14 April 2010 7:43 PM > >>> To: dev@forrest.apache.org > >>> Subject: Re: JIRA problems (Was: ForrestBot build for forrest-docs > >>> FAILED) > >>> > >>> On Mon, Apr 12, 2010 David Crossley wrote: > >>>> > >>>> ... > >>>>> > >>>>> [java] X [0] forrest- > >>> > >>> issues.html BROKEN: /export/home/config/forrestbot- > >>> trunk/conf/work/forrest-docs/. (Is a directory) > >>>> > >>>> ... > >>>> > >>>> Now that Jira is back online, we seem to be getting this problem > >>>> on every run, rather than just sporadically. > >>>> > >>>> This is where forrest processes a report out of the JIRA > >>>> issue tracker. I gather that the weird failure message is > >>>> because Forrest suddenly has no content to process because > >>>> the JIRA query failed to return results. > >>>> > >>>> Someone will need to investigate and follow up with ASF Infra. > >> > >> the forrest-issues.html is produced from the forrest.properties > property: > >> > >> > >> project.issues-rss- > url=http://issues.apache.org/jira/secure/IssueNavigator.j > >> > >> spa?view=rss&pid=12310000&fixfor=12310041&resolutionIds=- > 1&sorter/field=prio > >> rity&sorter/order=DESC&tempMax=25&reset=true&decorator=none > > > > Did you try to use https instead of http? We have a similar issue > with some > > attachements, which will be downloaded from JIRA from the PDFBox ant > > build.xml. > > After changing the protocol everything works fine. > > Same here, I changed to https instead and all is well locally, I > reckon we'll see if it helps the zone build too in a bit. Thanks > Andreas! > > It'd be kinda cool to now know why though? :)
I think due to recent events most if not all of Jira redirects http to https anyway. Perhaps this link requires it, though my manual test of http: did redirect to https: fine on its own. Gav... > > --tim
