tika-2.x-windows - Build # 175 - Still Failing

[Apache Jenkins Server <je...@builds.apache.org>]

The Apache Jenkins build system has built tika-2.x-windows (build #175)

Status: Still Failing

Check console output at https://builds.apache.org/job/tika-2.x-windows/175/ to view the results.

tika-2.x-windows - Build # 177 - Still Failing

[Apache Jenkins Server <je...@builds.apache.org>]

The Apache Jenkins build system has built tika-2.x-windows (build #177)

Status: Still Failing

Check console output at https://builds.apache.org/job/tika-2.x-windows/177/ to view the results.

tika-2.x-windows - Build # 176 - Still Failing

[Apache Jenkins Server <je...@builds.apache.org>]

The Apache Jenkins build system has built tika-2.x-windows (build #176)

Status: Still Failing

Check console output at https://builds.apache.org/job/tika-2.x-windows/176/ to view the results.

Re: tika-2.x-windows - Build # 175 - Still Failing

[David Meikle <lo...@gmail.com>]

On 11 March 2017 at 15:35, David Meikle <lo...@gmail.com> wrote:
>
> Will send a ticket to INFRA as looks like the apache.releases.http ID may
> be out of sync.
>
>
Raised as INFRA-13647 <https://issues.apache.org/jira/browse/INFRA-13647>.

Cheers,
Dave

Fwd: tika-2.x-windows - Build # 175 - Still Failing

[David Meikle <lo...@gmail.com>]

Hello,

The Apache Jenkins build system has built tika-2.x-windows (build #175)
> Status: Still Failing
> Check console output at https://builds.apache.org/job/
> tika-2.x-windows/175/ to view the results.


I have been trying to resurrect the Window build, as I am getting some
encoding detector test failures with 2.x on Windows, and it would appear
the deployments to https://repository.apache.org is the issue.

Changing the build to use mvn install instead of deploy confirms the build
is fine, with the failure then shifting to the post-build deploy artefact
action.

Will send a ticket to INFRA as looks like the apache.releases.http ID may
be out of sync.

Cheers,
Dave