tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ulrich Stärk <...@spielviel.de>
Subject Re: Jenkins build still off?
Date Mon, 22 Oct 2012 23:38:52 GMT
I'm at the airport right now and connectivity sucks. Will look at it when home tomorrow.

Uli

On 22.10.2012 02:47, Bob Harner wrote:
> I am able to trigger builds manually on Jenkins, but the plastic tests
> are failing there. I can't see the test results, because the workspace
> (https://builds.apache.org/job/tapestry-trunk-freestyle/ws/)
> disappears before I can check. I assume Jenkins is configured to
> delete the workspace after finishing (!), but since I can't see the
> Jenkins configuration, that's just a guess.
>
> Running            ./gradlew :plastic:test              works fine for
> me locally (with origin/master).
>
> Without a higher level of Jenkins access I'm not sure what else I can
> do on this.
>
> Maybe Uli can tell why the workspace is disappearing?
>
> On Sun, Oct 21, 2012 at 7:25 PM, Bob Harner <bobharner@gmail.com> wrote:
>> I'll see what I can do.
>>
>> On Sun, Oct 21, 2012 at 7:01 PM, Howard Lewis Ship <hlship@gmail.com> wrote:
>>> I would love to delegate out investigating and fixing this problem!
>>>
>>> On Sun, Oct 21, 2012 at 2:08 PM, Bob Harner <bobharner@gmail.com> wrote:
>>>> I guess the automated Jenkins builds
>>>> (https://builds.apache.org/job/tapestry-trunk-freestyle/) have been
>>>> turned off for 5 weeks now, and I think the last successful build
>>>> seems to have been 6 months ago. I hate to see this idle for so long,
>>>> with so many commits going unverified. Also, for my own purposes, I'd
>>>> like to view the Jenkins JavaDoc output to ensure my recent little
>>>> commits had the intended result.
>>>>
>>>> IIUC, the last suggestion (at
>>>> http://tapestry.1045711.n5.nabble.com/Build-failed-in-Jenkins-tapestry-trunk-freestyle-951-tt5716188.html#a5716322)
>>>> was to have Jenkins run the gradle build with some command line
>>>> argument that would then be detected within build.gradle and supply
>>>> -SNAPSHOT automatically.
>>>>
>>>> But it seems to me the problem is just that the
>>>> "continuousintegration" task in build.gradle has a
>>>> "subprojects.uploadPublished" dependency that it shouldn't. Removing
>>>> that dependency in my local build.gradle lets me run the
>>>> "continuousintegration" task without getting the "Missing upload
>>>> credentials" error.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>>
>>>
>>>
>>> --
>>> Howard M. Lewis Ship
>>>
>>> Creator of Apache Tapestry
>>>
>>> The source for Tapestry training, mentoring and support. Contact me to
>>> learn how I can get you up and productive in Tapestry fast!
>>>
>>> (971) 678-5210
>>> http://howardlewisship.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: dev-help@tapestry.apache.org
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message