Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Make http server fixture's handle() thread safe

As stated in the here implemented 'ServerWithExpectations' fixture:

"handlers, as well as failures, need to be thread-safe"

This concrete case was working most of the time since usually there are

not more than one expectations for the same request. But if the

same request is expected several times, and the requests are received

in parallel (as it is the case for metadata download), the handle()

method behaved flaky - by not doing reading and updating of the 'run'

flag as an atomic operation.

  1. … 4 more files in changeset.
Make http server fixture's handle() thread safe

As stated in the here implemented 'ServerWithExpectations' fixture:

"handlers, as well as failures, need to be thread-safe"

This concrete case was working most of the time since usually there are

not more than one expectations for the same request. But if the

same request is expected several times, and the requests are received

in parallel (as it is the case for metadata download), the handle()

method behaved flaky - by not doing reading and updating of the 'run'

flag as an atomic operation.

  1. … 4 more files in changeset.
Make http server fixture's handle() thread safe

As stated in the here implemented 'ServerWithExpectations' fixture:

"handlers, as well as failures, need to be thread-safe"

This concrete case was working most of the time since usually there are

not more than one expectations for the same request. But if the

same request is expected several times, and the requests are received

in parallel (as it is the case for metadata download), the handle()

method behaved flaky - by not doing reading and updating of the 'run'

flag as an atomic operation.

  1. … 4 more files in changeset.
Make http server fixture's handle() thread safe

As stated in the here implemented 'ServerWithExpectations' fixture:

"handlers, as well as failures, need to be thread-safe"

This concrete case was working most of the time since usually there are

not more than one expectations for the same request. But if the

same request is expected several times, and the requests are received

in parallel (as it is the case for metadata download), the handle()

method behaved flaky - by not doing reading and updating of the 'run'

flag as an atomic operation.

  1. … 4 more files in changeset.
Update sshd to 2.0.0

The library has been split into multiple artifacts which need to added

as dependencies separately.

  1. … 2 more files in changeset.
Switch to from DSA to RSA in our integration testing SFTP server

This may solve the `SignatureException: Invalid encoding for signature`

issue we see when running this on newer Java8 versions.

Switch to from DSA to RSA in our integration testing SFTP server

This may solve the `SignatureException: Invalid encoding for signature`

issue we see when running this on newer Java8 versions.

Upgrade sshd dependency to 1.2.0 (used in integration tests)

This might solve the flakiness issues we currently see with

the `SFTPServer` test fixture. sshd 1.2.0 works with Java7, while

1.2.0+ versions require Java8.

  1. … 1 more file in changeset.
Change test to simply close connections rather than restarting sftp server

  1. … 1 more file in changeset.
Check that an existing sftp connection is still connected before reuse

  1. … 4 more files in changeset.
Changing Play and SFTP integration tests to dynamically assign ports at bind time.

+review REVIEW-5579

  1. … 15 more files in changeset.
Refactoring port allocation to use fixed ranges based on test workers

+review REVIEW-5579

  1. … 22 more files in changeset.
Reverting SftpServer to AvailablePortFinder until issue can be resolved

Forcing sshd to always wait for stop in an attempt to address apparent test flakiness

+review REVIEW-5579

First stab at a multicast port allocator test fixture

+review REVIEW-5579

  1. … 28 more files in changeset.
Extracted a basic int test that verifies 'uploadArchives' for each transport, from various existing tests.

  1. … 16 more files in changeset.
Support SFTP publishing via ‘maven-publish’ (using Wagon adapter)

  1. … 5 more files in changeset.
Upgraded to new version of sshd used by test fixtures.

  1. … 1 more file in changeset.
Turn on logging from jsch to see if it helps tracking down some intermittent test failures. Use a KeyPairProvider in SFTPServer that provides a valid, on the spot generated key pair.

  1. … 1 more file in changeset.
Change: Correct some misspelling and duplicate words

  1. … 26 more files in changeset.
tweak sftpserver restart (hopefully this fixes ci issue on windows)

+review REVIEW-5034

Minor tweaks to SFTPServer

+review REVIEW-5064

add testcase for accessing sftp server with unsupported password authentication

+review REVIEW-5064

  1. … 1 more file in changeset.
Start abstracting sftp and http repository transport tests to unify coverage

  1. … 79 more files in changeset.
Switched sftp repo implementation to use jsch instead of sshd client. Let's see if it's more reliable on the CI machines.

  1. … 25 more files in changeset.
Update server interaction verification for sftp repository transport after introduction of sftp client pool

  1. … 9 more files in changeset.
Add server interaction verification for sftp repository transport

  1. … 13 more files in changeset.
Don't assign a port until the server is started.

Add coverage for error scenarios when resolving and uploading using SFTP transport

  1. … 4 more files in changeset.
Merge branch 'sftp-repository-transport' of https://github.com/erdi/gradle.

  1. … 2 more files in changeset.