Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 71389 invoked from network); 15 Apr 2010 00:29:00 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 15 Apr 2010 00:29:00 -0000 Received: (qmail 47520 invoked by uid 500); 15 Apr 2010 00:28:59 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 47451 invoked by uid 500); 15 Apr 2010 00:28:59 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org List-Id: Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 47444 invoked by uid 99); 15 Apr 2010 00:28:59 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Apr 2010 00:28:59 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [202.60.90.242] (HELO enterprise.16degrees.com.au) (202.60.90.242) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Apr 2010 00:28:51 +0000 Received: from deltaflyer (CPE-121-215-243-70.static.qld.bigpond.net.au [121.215.243.70]) by enterprise.16degrees.com.au (Postfix) with ESMTPA id 6C1561902206 for ; Thu, 15 Apr 2010 10:28:27 +1000 (EST) From: "Gav..." To: References: <201004120613.o3C6DIXr015044@forrest.zones.apache.org> <20100412081953.GA7844@igg.local> <20100414094314.GC18880@igg.local> <06e001cadbbd$2dfedde0$89fc99a0$@com.au> <4BC5FD2C.5070007@lehmi.de> In-Reply-To: Subject: RE: JIRA problems (Was: ForrestBot build for forrest-docs FAILED) Date: Thu, 15 Apr 2010 10:28:24 +1000 Message-ID: <004301cadc32$908d1100$b1a73300$@com.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AcrcLwR3xjqTa/0FQQSeVVDLsSBFDgAA2afQ Content-Language: en-au X-Virus-Checked: Checked by ClamAV on apache.org > -----Original Message----- > From: Tim Williams [mailto:williamstw@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) >=20 > On Wed, Apr 14, 2010 at 1:36 PM, Andreas Lehmkuehler = > wrote: > > Hi, > > > > Gav... schrieb: > >> > >>> -----Original Message----- > >>> From: David Crossley [mailto:crossley@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: > >>>> > >>>> ... > >>>>> > >>>>> =A0 =A0 [java] X [0] =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 =A0 =A0 =A0 =A0 forrest- > >>> > >>> issues.html =A0 =A0 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=3Dhttp://issues.apache.org/jira/secure/IssueNavigator.j > >> > >> spa?view=3Drss&pid=3D12310000&fixfor=3D12310041&resolutionIds=3D- > 1&sorter/field=3Dprio > >> rity&sorter/order=3DDESC&tempMax=3D25&reset=3Dtrue&decorator=3Dnone > > > > 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. >=20 > 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! >=20 > 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... >=20 > --tim