On 30 October 2016 at 07:31, Andy Seaborne <[email protected]> wrote:
> This job runs daily regardless of whether git has changed or not that what
> seems to make it so verbose in commits@
>
> Other jobs (s small sample I looked at - Jenkins is quite slow ATM) are set
> to poll SCM.
>
>         Andy
>
> On 29/10/16 18:51, Apache Jenkins Server wrote:
>>
>> See
>> <https://builds.apache.org/job/incubator-taverna-commandline-nightly/291/>

Clue is in the name.. but not sure why it is failing.

The idea of this job is that it would pull together the latest
snapshots - a trigger on-build from those dependencies might bail out
on the first immediate error - while the nightly would at least the
night after pick up the very latest deployed SNAPSHOTs.

It is less important now that we have released taverna-engine,
taverna-osgi and taverna-common-activities, so this won't need to be
in SNAPSHOT.

Now it should be sufficient to build it once a week I think. I changed
the schedule in Jenkins to "H H */7 * *"


EDIT: It seems to fail because of this error

https://builds.apache.org/job/incubator-taverna-commandline/185/console

which is in https://issues.apache.org/jira/browse/TAVERNA-1001

I'll see if that change to <packaging>bundle</packaging> (which
doesn't make sense for taverna-workbench-product) is a workaround.

Reply via email to