SuccessConsole Output

Skipping 553 KB.. Full Log
, fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@c76762[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
    Starting testcase GetFileIDsTest
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseIdentification
        Description: Tests the identification for a GetFileIDs operation on the pillar for the failure scenario, when the file is missing.
        Step: Set up constants and variables.
        Step: Setup for delivering pillar id and not having the file 
        Step: Create and send the identify request message.
10:50:20.574 WARN  o.b.p.m.IdentifyPillarsForGetFileIDsRequestHandler - The following file is missing 'DefaultFilebadCaseIdentification' at collection 'TwoPillarCollection'.
          Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsResponse@52a8f789[correlationID=3ae71eb3-94ac-4c17-9854-257a536f112a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5345552f[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@237824b0[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>(default)], timeToDeliver=<null>(default)]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: badCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationNoFile
        Description: Tests the GetFileIDs functionality of the pillar for the failure scenario, where it does not have the file.
        Step: Set up constants and variables.
        Step: Setup for not having the file
        Step: Create and send the actual GetFileIDs message to the pillar.
10:50:21.919 WARN  o.b.p.m.GetFileIDsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'.
          Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@4e23ddf0[correlationID=f3c35b60-5fea-47ea-bbbf-c1d7d70c4ed2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4e00723b[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@69d9d322[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
10:50:21.927 WARN  o.b.p.m.GetFileIDsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'.
          Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@94b5fe3[correlationID=f3c35b60-5fea-47ea-bbbf-c1d7d70c4ed2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4417755b[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@69d9d322[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
        Step: Retrieve the FinalResponse for the GetFileIDs request
      Test success: badCaseOperationNoFile
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@94b5fe3[correlationID=f3c35b60-5fea-47ea-bbbf-c1d7d70c4ed2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4417755b[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@69d9d322[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
10:50:22.935 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@94b5fe3[correlationID=f3c35b60-5fea-47ea-bbbf-c1d7d70c4ed2, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4417755b[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@69d9d322[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseIdentification
        Description: Tests the identification for a GetFileIDs operation on the pillar for the successful scenario.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileIDsResponse@282079b9[correlationID=57b8d15e-1825-45ff-a521-9963b7197775, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3d6c7152[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4e6add8d[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@23974cac[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
      Test starting: componentIDTest
      Test success: componentIDTest
    Starting testcase PutFileTest
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseIdentification
        Description: Tests the identification for a PutFile operation on the pillar for the failure scenario, when the file already exists.
        Step: Set up constants and variables.
        Step: Setup for already having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@72bef795[correlationID=fadcbcb9-1488-401d-bacc-5a31ffbbb45f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1f4d9c7f[responseCode=DUPLICATE_FILE_FAILURE, responseText=<null>(default)], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@6dcb4f30[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: badCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationFileAlreadyExists
        Description: Tests the PutFile operation on the pillar for the failure scenario, when the file already exists.
        Step: Set up constants and variables.
        Step: Setup for already having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseOperationFileAlreadyExists-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@3fc105dd[correlationID=538d1138-fb68-48c4-92a4-d3e8e7bdc019, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationFileAlreadyExists-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationFileAlreadyExists-cibuild01-contributor, from=Pillar-badCaseOperationFileAlreadyExists, to=badCaseOperationFileAlreadyExists, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@35129b9e[responseCode=DUPLICATE_FILE_FAILURE, responseText=We already have the file], pillarID=Pillar-badCaseOperationFileAlreadyExists, pillarChecksumSpec=<null>(default), fileID=DefaultFilebadCaseOperationFileAlreadyExists, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=<null>(default), checksumDataForExistingFile=<null>(default)]
        Step: Retrieve the FinalResponse for the PutFile request
      Test success: badCaseOperationFileAlreadyExists
        Added fixture: Initialize a new Pillar.
      Test starting: badCasePutOperationNoValidationChecksum
        Description: Tests the PutFile operation on the pillar for the failure scenario, when no validation checksum is given but required.
        Step: Set up constants and variables.
        Step: Setup for not already having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@6dae5562[correlationID=90818d7b-7096-465f-90e4-ce3911c5c66c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCasePutOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=badCasePutOperationNoValidationChecksum, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1cc5d8a9[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=A checksum is required for the PutFile operation to be performed.], pillarID=Pillar-badCasePutOperationNoValidationChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFilebadCasePutOperationNoValidationChecksum, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=<null>(default), checksumDataForExistingFile=<null>(default)]
10:50:27.759 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@4ec28534[origDateTime=2017-03-10T10:50:27.757+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@921dbcf[correlationID=1b1ffc56-7375-400f-9d29-b964ddc9101c, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCasePutOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCasePutOperationNoValidationChecksum, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@4ec28534[origDateTime=2017-03-10T10:50:27.757+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCasePutOperationNoValidationChecksum, alarmText=A checksum is required for the PutFile operation to be performed., fileID=DefaultFilebadCasePutOperationNoValidationChecksum, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the PutFile request
        Step: Pillar should have sent an alarm
      Test success: badCasePutOperationNoValidationChecksum
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseIdentification
        Description: Tests the identification for a PutFile operation on the pillar for the successful scenario.
        Step: Set up constants and variables.
        Step: Setup for not already having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForPutFileResponse@72f5fb36[correlationID=c8384452-ce20-4374-a3dd-9669410af309, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@300b839c[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@352288bc[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseOperationWithChecksumReturn
        Description: Tests the PutFile operation on the pillar for the success scenario, when requesting the cheksum of the file returned.
        Step: Set up constants and variables.
        Step: Setup for not already having the file and delivering pillar id, and delivering an answer for the checksum request
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileProgressResponse@30fba306[correlationID=bd3aabe9-648d-4ce7-811f-3b1ee999865f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1ca55d5[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Started to receive data.], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
          Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01 : org.bitrepository.bitrepositorymessages.PutFileFinalResponse@12939937[correlationID=bd3aabe9-648d-4ce7-811f-3b1ee999865f, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumReturn, to=goodCaseOperationWithChecksumReturn, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@14501070[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationWithChecksumReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFilegoodCaseOperationWithChecksumReturn, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@4f7a2262[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4a577b99[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-03-10T10:50:29.411+01:00], checksumDataForExistingFile=<null>(default)]
        Step: Retrieve the ProgressResponse for the GetFileIDs request
        Step: Retrieve the FinalResponse for the PutFile request
      Test success: goodCaseOperationWithChecksumReturn
    Starting testcase RecalculateChecksumWorkflowTest
        Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection
      Test starting: testWorkflowDoesNotRecalculateWhenNotNeeded
        Description: Test that the workflow does not recalculates the workflows, when the maximum age has not yet been met.
        Step: Create and run workflow
      Test success: testWorkflowDoesNotRecalculateWhenNotNeeded
        Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection
      Test starting: testWorkflowRecalculatesChecksum
        Description: Test that the workflow recalculates the workflows, when the maximum age has been met.
        Step: Create and run workflow
      Test success: testWorkflowRecalculatesChecksum
    Starting testcase ReferenceArchiveTest
        Added fixture: Initialize the Reference pillar cache with an empty file in default collection TwoPillarCollection
      Test starting: testReferenceArchive
        Description: Test the ReferenceArchive.
        Step: Setup
        Step: test 'hasFile'
        Step: Test 'getFile'
        Step: Test getAllFileIDs
        Step: Test 'getFileAsInputstream'
        Step: Delete, recreate and delete again
        Step: Try to delete missing file.
        Step: Replace a file, which does not exist in the filedir.
        Step: Copy a file into the tmpDir and then use replace.
        Step: Try performing the replace, when the file in the tempdir has been removed.
      Test success: testReferenceArchive
    Starting testcase ReplaceFileTest
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseIdentification
        Description: Tests the identification for a ReplaceFile operation on the pillar for the failure scenario, when the file does not exist.
        Step: Set up constants and variables.
        Step: Setup for not having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileResponse@749054a3[correlationID=ac3c8a3f-756c-457c-b95e-a64045da180d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@bf70ce5[responseCode=FILE_NOT_FOUND_FAILURE, responseText=Could not find the requested file to delete.], fileID=DefaultFile, pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=<null>(default)]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: badCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationMissingFile
        Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when the file is missing.
        Step: Set up constants and variables.
        Step: Setup for not having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseOperationMissingFile-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@63916a3[correlationID=25805135-69a6-4813-b741-f20d700cc93c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingFile-cibuild01-contributor, from=Pillar-badCaseOperationMissingFile, to=badCaseOperationMissingFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@25dc8147[responseCode=FILE_NOT_FOUND_FAILURE, responseText=The file 'DefaultFile' has been requested, but we do not have that file!], pillarID=Pillar-badCaseOperationMissingFile, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
        Step: Retrieve the FinalResponse for the ReplaceFile request
      Test success: badCaseOperationMissingFile
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationNoDestructiveChecksum
        Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when no validation checksum is given for the destructive action, but though is required.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@bb78f01[correlationID=fb62e00e-452f-46ff-b30f-35f7e4da14a3, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=badCaseOperationNoDestructiveChecksum, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1caf77f6[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=According to the contract a checksum for file to be deleted during the replacing operation is required.], pillarID=Pillar-badCaseOperationNoDestructiveChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
10:50:34.398 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@246f9fa8[origDateTime=2017-03-10T10:50:34.398+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@4d001a14[correlationID=cc8852e4-0beb-494a-8d1c-904ed036255b, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoDestructiveChecksum, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@246f9fa8[origDateTime=2017-03-10T10:50:34.398+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoDestructiveChecksum, alarmText=According to the contract a checksum for file to be deleted during the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the ReplaceFile request
        Step: Pillar should have sent an alarm
      Test success: badCaseOperationNoDestructiveChecksum
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationNoValidationChecksum
        Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when no validation checksum is given for the new file, but though is required.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@10fef6da[correlationID=8dd39baa-c338-4cb2-870f-8621cf9d84a9, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoValidationChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=badCaseOperationNoValidationChecksum, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1da77a43[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=According to the contract a checksum for new file in the replacing operation is required.], pillarID=Pillar-badCaseOperationNoValidationChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
10:50:34.702 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@63604641[origDateTime=2017-03-10T10:50:34.701+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@1313dea8[correlationID=d95fdb8f-432f-421b-b1b8-fda7ddd2eb53, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoValidationChecksum-cibuild01-contributor, from=Pillar-badCaseOperationNoValidationChecksum, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@63604641[origDateTime=2017-03-10T10:50:34.701+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationNoValidationChecksum, alarmText=According to the contract a checksum for new file in the replacing operation is required., fileID=DefaultFile, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the ReplaceFile request
        Step: Pillar should have sent an alarm
      Test success: badCaseOperationNoValidationChecksum
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationWrongDestructiveChecksum
        Description: Tests the ReplaceFile operation on the pillar for the failure scenario, when the checksum for the destructive action is different from the one in the cache.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
10:50:34.994 WARN  o.b.p.m.ReplaceFileRequestHandler - Failed to handle replace operation on file 'DefaultFile' since the request had the checksum '1234cccccccc4321' where our local file has the value '1234cccccccc4322'. Sending alarm and respond failure.
          Result: Received message on TEST-TOPIC-badCaseOperationWrongDestructiveChecksum-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@7acb8e6b[correlationID=74a39583-1846-4d2d-87cc-6d8d1131691e, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationWrongDestructiveChecksum-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=badCaseOperationWrongDestructiveChecksum, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6c758c74[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum.], pillarID=Pillar-badCaseOperationWrongDestructiveChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
10:50:35.003 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@5a32ab89[origDateTime=2017-03-10T10:50:35.003+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@8dcc25[correlationID=deee7c3c-bc52-4315-ade4-3dc695f5d014, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationWrongDestructiveChecksum-cibuild01-contributor, from=Pillar-badCaseOperationWrongDestructiveChecksum, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@5a32ab89[origDateTime=2017-03-10T10:50:35.003+01:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationWrongDestructiveChecksum, alarmText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum., fileID=DefaultFile, collectionID=TwoPillarCollection]]
        Step: Retrieve the FinalResponse for the ReplaceFile request
        Step: Pillar should have sent an alarm
      Test success: badCaseOperationWrongDestructiveChecksum
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseIdentification
        Description: Tests the identification for a ReplaceFile operation on the pillar for the successful scenario.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForReplaceFileResponse@2b8502e7[correlationID=99d270fc-5c77-45f0-a281-7945995b18b6, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@37669c4[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@1e3469df[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseOperation
        Description: Tests the ReplaceFile operation on the pillar for the success scenario.
        Step: Set up constants and variables.
        Step: Setup for already having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseOperation-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileProgressResponse@15c46930[correlationID=a252cade-ff48-4f5c-802d-c0f334d07c8c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@2c635953[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
          Result: Received message on TEST-TOPIC-goodCaseOperation-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@39dfadd7[correlationID=a252cade-ff48-4f5c-802d-c0f334d07c8c, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperation-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperation-cibuild01-contributor, from=Pillar-goodCaseOperation, to=goodCaseOperation, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@f64ce35[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperation, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
        Step: Retrieve the ProgressResponse for the GetFileIDs request
        Step: Retrieve the FinalResponse for the ReplaceFile request
      Test success: goodCaseOperation
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseOperationWithChecksumsReturn
        Description: Tests the ReplaceFile operation on the pillar for the success scenario, when requesting both the cheksums of the file returned.
        Step: Set up constants and variables.
        Step: Setup for already having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileProgressResponse@50cf26b7[correlationID=38584a0a-7c54-45c9-a071-80dfcda36b53, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@611c9d31[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Performing the ReplaceFileRequest for file 'DefaultFile' at 'TwoPillarCollection'.], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt]
          Result: Received message on TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01 : org.bitrepository.bitrepositorymessages.ReplaceFileFinalResponse@1aacde34[correlationID=38584a0a-7c54-45c9-a071-80dfcda36b53, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationWithChecksumsReturn-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationWithChecksumsReturn-cibuild01-contributor, from=Pillar-goodCaseOperationWithChecksumsReturn, to=goodCaseOperationWithChecksumsReturn, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1fdc2d45[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationWithChecksumsReturn, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@65fc2639[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2bae0ac8[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2017-03-10T10:50:37.815+01:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@570f2cf7[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@29478556[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-03-10T10:50:37.816+01:00]]
        Step: Retrieve the ProgressResponse for the GetFileIDs request
        Step: Retrieve the FinalResponse for the ReplaceFile request
      Test success: goodCaseOperationWithChecksumsReturn
      Test starting: getPillarCollectionsTest
      Test success: getPillarCollectionsTest
    Starting testcase ArchiveDirectoryTest
      Test starting: testArchiveDirectoryExistingFile
        Description: Test the ArchiveDirectory when the file exists
        Step: Setup
        Step: Validate the existence of the file
        Step: Delete the file.
      Test success: testArchiveDirectoryExistingFile
      Test starting: testArchiveDirectoryExistingFolderFile
        Description: Test the ArchiveDirectory when the file exists
        Step: Setup
        Step: Validate the existence of the file
        Step: Delete the file.
      Test success: testArchiveDirectoryExistingFolderFile
      Test starting: testArchiveDirectoryMissingFile
        Description: Test the ArchiveDirectory when the file is missing.
        Step: Setup
        Step: Validate the existence of the file
        Step: Delete the file.
      Test success: testArchiveDirectoryMissingFile
      Test starting: testArchiveDirectoryMissingFolderFile
        Description: Test the ArchiveDirectory when the file is missing.
        Step: Setup
        Step: Validate the existence of the file
        Step: Delete the file.
      Test success: testArchiveDirectoryMissingFolderFile
      Test starting: testArchiveDirectoryMoveFileToArchive
        Description: Testing the error scenarios when moving a file from tmp to archive for the ArchiveDirectory.
        Step: Setup
        Step: Moving file from tmp to archive
        Step: Create file in both tmp and archive.
        Step: Moving file from tmp to archive
        Step: Remove the file from archive and try again
      Test success: testArchiveDirectoryMoveFileToArchive
      Test starting: testArchiveDirectoryMoveFolderFileToArchive
        Description: Testing the error scenarios when moving a file from tmp to archive for the ArchiveDirectory.
        Step: Setup
        Step: Moving file from tmp to archive
        Step: Create file in both tmp and archive.
        Step: Moving file from tmp to archive
        Step: Remove the file from archive and try again
      Test success: testArchiveDirectoryMoveFolderFileToArchive
      Test starting: testArchiveDirectoryNewFile
        Description: Testing the ArchiveDirectory handling of a new file.
        Step: Setup
        Step: Retrieve tmp file
        Step: Request a new file for the tmp dir
        Step: Retrieve tmp file
        Step: Request another new file with the same name
        Step: Move the file from tmp to archive
      Test success: testArchiveDirectoryNewFile
      Test starting: testArchiveDirectoryNewFolderFile
        Description: Testing the ArchiveDirectory handling of a new file.
        Step: Setup
        Step: Retrieve tmp file
        Step: Request a new file for the tmp dir
        Step: Retrieve tmp file
        Step: Request another new file with the same name
        Step: Move the file from tmp to archive
      Test success: testArchiveDirectoryNewFolderFile
      Test starting: testArchiveDirectoryRemoveFile
        Description: Testing the error scenarios when removing files from the archive.
        Step: Setup
        Step: Remove nonexisting file from archive
        Step: Remove nonexisting file from tmp
        Step: Create file in both tmp, archive and retain directories.
        Step: Remove the file from archive and tmp
      Test success: testArchiveDirectoryRemoveFile
      Test starting: testArchiveDirectoryRemoveFolderFile
        Description: Testing the error scenarios when removing files from the archive.
        Step: Setup
        Step: Remove nonexisting file from archive
        Step: Remove nonexisting file from tmp
        Step: Create file in both tmp, archive and retain directories.
        Step: Remove the file from archive and tmp
      Test success: testArchiveDirectoryRemoveFolderFile
    Starting testcase FullPillarModelTest
      Test starting: testPillarModelBasicFunctionality
        Description: Test the basic functions of the full reference pillar model.
        Step: Check the pillar id in the pillar model
        Step: Ask whether it can handle a file of size 0
        Step: Ask whether it can handle a file of maximum size
        Step: Check the ChecksumPillarSpec
      Test success: testPillarModelBasicFunctionality
      Test starting: testPillarModelHasFile
        Description: Test that the file exists, when placed in the archive and cache
        Step: Setup
        Step: Check whether file exists and retrieve it.
        Step: Verify that no exceptions are thrown when verifying file existance.
        Step: Check retrieval of non-default checksum
      Test success: testPillarModelHasFile
      Test starting: testPillarModelNoFile
        Description: Test that the file exists, when placed in the archive and cache
        Step: Setup
        Step: Check whether file exists and try to retrieve it.
        Step: Verify that anexceptions are thrown when verifying file existance.
10:50:40.219 WARN  o.b.pillar.store.FileStorageModel - The file 'DefaultFile' has been requested, but we do not have that file in collection 'TwoPillarCollection'!
      Test success: testPillarModelNoFile
    Starting testcase GetAuditTrailsTest
        Added fixture: Initialize a new Pillar.
      Test starting: checksumPillarGetAuditTrailsMaximumNumberOfResults
        Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a limited number of audit trails are requested.
        Step: Set up constants and variables.
        Step: Send the request for the limited amount of audit trails to the pillar.
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@6f54a7be[correlationID=a1943178-cee4-40a4-a707-89dbc5ea2cce, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4c48ccc4[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@597f9d9d[correlationID=a1943178-cee4-40a4-a707-89dbc5ea2cce, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, to=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@72e6e93[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@2fbe0960[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@32c29f7b[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@17746fcb[sequenceNumber=1, fileID=fileID1489139440491, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2017-03-10T10:50:40.491+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@635ad140[sequenceNumber=2, fileID=fileID1489139440491, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2017-03-10T10:50:40.495+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@3c703142[sequenceNumber=3, fileID=fileID1489139440491, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2017-03-10T10:50:40.495+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@1aef48f0[sequenceNumber=4, fileID=fileID1489139440491, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2017-03-10T10:50:40.495+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@2ed16651[sequenceNumber=5, fileID=fileID1489139440491, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2017-03-10T10:50:40.495+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=true]
        Step: Validate the final response
      Test success: checksumPillarGetAuditTrailsMaximumNumberOfResults
        Added fixture: Initialize a new Pillar.
      Test starting: checksumPillarGetAuditTrailsSpecificRequests
        Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where a specific audit trail are requested.
        Step: Set up constants and variables.
        Step: Send the identification request
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@71268b8c[correlationID=a2973f02-9665-4ee9-a19d-7cbbfefc7f7a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6697389c[responseCode=IDENTIFICATION_POSITIVE, responseText=<null>(default)]]
        Step: Retrieve and validate the response.
        Step: Make and send the request for the actual GetAuditTrails operation
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@58e5a81c[correlationID=a2973f02-9665-4ee9-a19d-7cbbfefc7f7a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1d5a2267[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@42d6aa88[correlationID=a2973f02-9665-4ee9-a19d-7cbbfefc7f7a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@751661b[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@72018ba5[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@3e84c698[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@4971a92a[sequenceNumber=1, fileID=fileID1489139440766, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2017-03-10T10:50:40.766+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails]}]], partialResult=false]
        Step: Receive and validate the progress response.
        Step: Receive and validate the final response
        Step: Make another request, where both ingested audit trails is requested
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@459c7fa1[correlationID=a2973f02-9665-4ee9-a19d-7cbbfefc7f7a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3b3e9814[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@239629ed[correlationID=a2973f02-9665-4ee9-a19d-7cbbfefc7f7a, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSpecificRequests-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSpecificRequests-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSpecificRequests, to=Pillar-checksumPillarGetAuditTrailsSpecificRequests, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@676aec4c[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@412de677[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@e1c387e[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@4971a92a[sequenceNumber=1, fileID=fileID1489139440766, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2017-03-10T10:50:40.766+01:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@1c57a111[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2017-03-10T10:50:40.766+01:00, info=badInfo, operationID=operationID, certificateID=certificateid, auditTrailInformation=WrongAuditTrail]}]], partialResult=false]
        Step: Receive and validate the progress response.
        Step: Receive and validate the final response
      Test success: checksumPillarGetAuditTrailsSpecificRequests
        Added fixture: Initialize a new Pillar.
      Test starting: checksumPillarGetAuditTrailsSuccessful
        Description: Tests the GetAuditTrails functionality of the pillar for the successful scenario, where all audit trails are requested.
        Step: Set up constants and variables.
        Step: Send the identification request
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetAuditTrailsResponse@6799cded[correlationID=79afb2d9-5828-4e96-a10a-19fe888b1b04, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@38f20b58[responseCode=IDENTIFICATION_POSITIVE, responseText=<null>(default)]]
        Step: Make and send the request for the actual GetAuditTrails operation
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsProgressResponse@1f404aa1[correlationID=79afb2d9-5828-4e96-a10a-19fe888b1b04, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6d5fc2ca[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to extract the requested audit trails.], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01 : org.bitrepository.bitrepositorymessages.GetAuditTrailsFinalResponse@44808c29[correlationID=79afb2d9-5828-4e96-a10a-19fe888b1b04, collectionID=TwoPillarCollection, destination=TEST-TOPIC-checksumPillarGetAuditTrailsSuccessful-cibuild01, replyTo=TEST-TOPIC-Pillar-checksumPillarGetAuditTrailsSuccessful-cibuild01-contributor, from=Pillar-checksumPillarGetAuditTrailsSuccessful, to=Pillar-checksumPillarGetAuditTrailsSuccessful, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@6c00f72a[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@7188bd49[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@62d26820[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@22f34197[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2017-03-10T10:50:41.034+01:00, info=info, operationID=operationID, certificateID=certificateID, auditTrailInformation=auditTrail]}]], partialResult=false]
        Step: Receive and validate the progress response.
        Step: Receive and validate the final response
      Test success: checksumPillarGetAuditTrailsSuccessful
    Starting testcase GetChecksumsTest
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseIdentification
        Description: Tests the identification for a GetChecksums operation on the pillar for the failure scenario, when the file is missing.
        Step: Set up constants and variables.
        Step: Setup for delivering pillar id and not having the file 
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsResponse@cfec1ec[correlationID=bee23620-f7fb-47cf-863b-52e1d786c79d, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1af2c5c8[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@55de1b68[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2040722f[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=<null>(default)]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: badCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseOperationNoFile
        Description: Tests the GetChecksums functionality of the pillar for the failure scenario, where it does not have the file.
        Step: Set up constants and variables.
        Step: Setup for not having the file
        Step: Create and send the actual GetChecksums message to the pillar.
10:50:42.624 WARN  o.b.p.m.GetChecksumsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'.
          Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@7b779c7b[correlationID=77dd6e84-da10-404d-8c79-e2d7b05af5d8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@16fc5679[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22f3a5bc[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
10:50:42.634 WARN  o.b.p.m.GetChecksumsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'.
          Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@27cfc534[correlationID=77dd6e84-da10-404d-8c79-e2d7b05af5d8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3e046920[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22f3a5bc[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
10:50:42.638 WARN  o.b.p.m.GetChecksumsRequestHandler - The following file is missing 'DefaultFilebadCaseOperationNoFile' at collection 'TwoPillarCollection'.
          Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@671ba0dc[correlationID=77dd6e84-da10-404d-8c79-e2d7b05af5d8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3e242f6e[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22f3a5bc[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
        Step: Retrieve the FinalResponse for the GetChecksums request
      Test success: badCaseOperationNoFile
          Result: The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@27cfc534[correlationID=77dd6e84-da10-404d-8c79-e2d7b05af5d8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3e046920[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22f3a5bc[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@671ba0dc[correlationID=77dd6e84-da10-404d-8c79-e2d7b05af5d8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3e242f6e[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22f3a5bc[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
10:50:43.646 WARN  o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase: 
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@27cfc534[correlationID=77dd6e84-da10-404d-8c79-e2d7b05af5d8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3e046920[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22f3a5bc[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@671ba0dc[correlationID=77dd6e84-da10-404d-8c79-e2d7b05af5d8, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationNoFile-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationNoFile-cibuild01-contributor, from=Pillar-badCaseOperationNoFile, to=badCaseOperationNoFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@3e242f6e[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@22f3a5bc[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseIdentification
        Description: Tests the identification for a GetChecksums operation on the pillar for the successful scenario.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsResponse@fef4fda[correlationID=1ff2725e-65c2-4312-a981-af50a7e7fb29, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1d2d3bc2[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@79c01d37[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@18e6b4e2[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@6d82a9bb[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseOperationAllFiles
        Description: Tests the GetChecksums operation on the pillar for the successful scenario, when requesting all files.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering result-set
        Step: Create and send the actual GetChecksums message to the pillar.
          Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@6cf782b6[correlationID=10781b9f-c7df-449e-9be1-ee70790d2586, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@5f0369af[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@427bbaac[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@72c3bc5e[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@7892045f[correlationID=10781b9f-c7df-449e-9be1-ee70790d2586, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationAllFiles-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationAllFiles-cibuild01-contributor, from=Pillar-goodCaseOperationAllFiles, to=goodCaseOperationAllFiles, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@30081ff4[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@72c3bc5e[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@34dcad0d[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@5ab1b065[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-03-10T10:50:45.321+01:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@3269e790[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1489139445304, checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=1970-01-01T01:00:00.000+01:00]}], partialResult=false]
        Step: Retrieve the ProgressResponse for the GetChecksums request
        Step: Retrieve the FinalResponse for the GetChecksums request
      Test success: goodCaseOperationAllFiles
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseOperationSingleFile
        Description: Tests the GetChecksums operation on the pillar for the successful scenario when requesting one specific file.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering result-set
        Step: Create and send the actual GetChecksums message to the pillar.
          Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@5c8ba2ed[correlationID=76a4aa40-5bf7-4eb3-b4bb-6d790f998dbd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@72a90036[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@703e8fe8[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2d29b8d3[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@2c34fb51[correlationID=76a4aa40-5bf7-4eb3-b4bb-6d790f998dbd, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseOperationSingleFile-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseOperationSingleFile-cibuild01-contributor, from=Pillar-goodCaseOperationSingleFile, to=goodCaseOperationSingleFile, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@1626e651[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@2d29b8d3[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@12e37ab2[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@72ecb71d[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-03-10T10:50:45.625+01:00]}], partialResult=false]
        Step: Retrieve the ProgressResponse for the GetChecksums request
        Step: Retrieve the FinalResponse for the GetChecksums request
      Test success: goodCaseOperationSingleFile
        Added fixture: Initialize a new Pillar.
      Test starting: testRestrictions
        Description: Tests that the restrictions are correctly passed on to the cache.
        Step: Set up constants and variables.
        Step: Setup for only delivering result-set when the correct restrictions are given.
        Step: Create and send the actual GetChecksums message to the pillar.
          Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsProgressResponse@6f32cfff[correlationID=3e9c2b6b-21d3-48ca-a42e-2ddcef9e5643, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@4eac6cb4[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@7f277cf6[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3d5a99e6[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
          Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@44eee485[correlationID=3e9c2b6b-21d3-48ca-a42e-2ddcef9e5643, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testRestrictions-cibuild01, replyTo=TEST-TOPIC-Pillar-testRestrictions-cibuild01-contributor, from=Pillar-testRestrictions, to=testRestrictions, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@698af960[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3d5a99e6[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@2d8ef86b[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@44f2d195[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2017-03-10T10:50:45.919+01:00]}], partialResult=false]
        Step: Retrieve the ProgressResponse for the GetChecksums request
        Step: Retrieve the FinalResponse for the GetChecksums request
      Test success: testRestrictions
    Starting testcase ChecksumDatabaseMigrationTest
      Test starting: testMigratingChecksumDatabaseFromV3ToV4
        Description: Tests that the checksums table can be migrated from version 3 to 4, e.g. changing the column calculatedchecksumdate from timestamp to bigint.
        Step: Ensure cleanup
10:50:46.052 WARN  o.b.common.utils.FileUtils - Could not delete '/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/test/referencepillar/checksumdb-for-migration'
        Step: Unzipping and connecting to checksum database version 3
        Step: Validate setup
        Step: Ingest a entry to the database with a date for the calculationdate
        Step: Perform migration
10:50:51.003 WARN  o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 3 to 4.
        Step: Validate the migration
      Test success: testMigratingChecksumDatabaseFromV3ToV4
    Starting testcase ChecksumDatabaseTest
      Test starting: testChecksumDatabaseExtraction
        Description: Test the extraction of data from the checksum database.
        Step: Check whether the default entry exists.
        Step: Extract calculation date
        Step: Extract the checksum
        Step: Extract the whole entry
        Step: Extract all entries
      Test success: testChecksumDatabaseExtraction
      Test starting: testDeletion
        Description: Test that data can be deleted from the database.
        Step: Check whether the default entry exists.
        Step: Remove the default entry
      Test success: testDeletion
      Test starting: testExtractionOfMissingData
        Description: Test the handling of bad arguments.
        Step: Try to get the date of a wrong file id.
        Step: Try to get the date of a wrong file id.
        Step: Try to remove a bad file id
      Test success: testExtractionOfMissingData
      Test starting: testGetChecksumResult
        Description: Tests the restrictions on the GetChecksumResult call to the database.
        Step: Instantiate database with appropriate data.
        Step: Test with no time restrictions
        Step: Test with time restrictions from epoc to now
        Step: Test with very strict time restrictions around the default date
        Step: Test with too new a lower limit
        Step: Test with exact date as both upper and lower limit
        Step: Test with date limit from 1 millis before as lower and exact date a upper limit
        Step: Test with date limit from exact date as lower and 1 millis after date a upper limit
        Step: Test with too old an upper limit
      Test success: testGetChecksumResult
      Test starting: testGetFileIDsRestrictions
        Description: Tests the restrictions on the GetFileIDs call to the database.
        Step: Instantiate database with appropriate data.
        Step: Test with no time restrictions and 10000 max_results
        Step: Test with minimum-date earlier than first file
        Step: Test with maximum-date earlier than first file
        Step: Test with minimum-date set to later than second file.
        Step: Test with maximum-date set to later than second file.
        Step: Test with minimum-date set to middle date.
        Step: Test with maximum-date set to middle date.
        Step: Test with both minimum-date and maximum-date set to middle date.
        Step: Test the first file-id, with no other restrictions
        Step: Test the second file-id, with no other restrictions
        Step: Test the date for the first file-id, while requesting the second file-id
      Test success: testGetFileIDsRestrictions
      Test starting: testGetFileIDsWithOldChecksums
        Description: Tests the restrictions on the GetFileIDsWithOldChecksums call to the database.
        Step: Instantiate database with appropriate data.
        Step: Extract all entries with checksum date older than now
        Step: Extract all entries with checksum date older than epoch
        Step: Extract all entries with checksum date older than middle date
      Test success: testGetFileIDsWithOldChecksums
      Test starting: testReplacingExistingEntry
        Description: Test that an entry can be replaced by another in the database.
        Step: Check whether the default entry exists.
        Step: Replace the checksum and date
      Test success: testReplacingExistingEntry
      Test starting: testSpecifiedEntryExtraction
        Description: Test that specific entries can be extracted. Has two entries in the database: one for the current timestamp and one for the epoch.
        Step: Instantiate database with appropriate data.
        Step: Extract with out restrictions
        Step: Extract with a maximum of 1 entry
        Step: Extract all dates older than this tests instantiation
        Step: Extract all dates newer than this tests instantiation
        Step: Extract all dates older than the newest instance
        Step: Extract all dates newer than the oldest instantiation
      Test success: testSpecifiedEntryExtraction
    Starting testcase GetFileTest
        Added fixture: Initialize a new Pillar.
      Test starting: badCaseIdentification
        Description: Tests the identification for a GetFile operation on the checksum pillar for the failure scenario, when the file is missing.
        Step: Set up constants and variables.
        Step: Setup for throwing an exception when asked to verify file existence
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-badCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileResponse@433e1d21[correlationID=2211f81a-7950-4906-b2ec-0dc1a94a0182, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseIdentification-cibuild01-contributor, from=Pillar-badCaseIdentification, to=badCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@283d49e5[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, pillarID=Pillar-badCaseIdentification, timeToDeliver=<null>(default)]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: badCaseIdentification
        Added fixture: Initialize a new Pillar.
      Test starting: goodCaseIdentification
        Description: Tests the identification for a GetFile operation on the pillar for the successful scenario.
        Step: Set up constants and variables.
        Step: Setup for having the file and delivering pillar id
        Step: Create and send the identify request message.
          Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetFileResponse@8f44eb4[correlationID=2a03aee8-b644-4af7-9ae2-1eb7f7d914ce, collectionID=TwoPillarCollection, destination=TEST-TOPIC-goodCaseIdentification-cibuild01, replyTo=TEST-TOPIC-Pillar-goodCaseIdentification-cibuild01-contributor, from=Pillar-goodCaseIdentification, to=goodCaseIdentification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@48bbf53e[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@b5375e0[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
        Step: Retrieve and validate the response getPillarID() the pillar.
      Test success: goodCaseIdentification
    Starting testcase ChecksumEntryTest
      Test starting: testExtendedTestCase
        Description: Test the ChecksumEntry
        Step: Create a ChecksumEntry
      Test success: testExtendedTestCase
    Starting testcase MediatorTest
      Test starting: testMediatorRuntimeExceptionHandling
        Description: Tests the handling of a runtime exception
        Step: Setup create and start the mediator.
        Step: Send a request to the mediator.
10:51:15.394 WARN  o.b.pillar.MediatorTest$TestMediator - Unexpected exception caught.
java.lang.RuntimeException: I am supposed to throw a RuntimeException
	at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:122)
	at org.bitrepository.pillar.MediatorTest$ErroneousRequestHandler.processRequest(MediatorTest.java:113)
	at org.bitrepository.pillar.messagehandler.PillarMediator.handleRequest(PillarMediator.java:80)
	at org.bitrepository.service.contributor.AbstractContributorMediator$GeneralRequestHandler.onMessage(AbstractContributorMediator.java:101)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.lambda$sendMessage$0(SimpleMessageBus.java:73)
	at java.lang.Iterable.forEach(Iterable.java:75)
	at org.bitrepository.protocol.messagebus.SimpleMessageBus.sendMessage(SimpleMessageBus.java:73)
	at org.bitrepository.pillar.MediatorTest.testMediatorRuntimeExceptionHandling(MediatorTest.java:84)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:86)
	at org.testng.internal.Invoker.invokeMethod(Invoker.java:643)
	at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:820)
	at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1128)
	at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:129)
	at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:112)
	at org.testng.TestRunner.privateRun(TestRunner.java:782)
	at org.testng.TestRunner.run(TestRunner.java:632)
	at org.testng.SuiteRunner.runTest(SuiteRunner.java:366)
	at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:361)
	at org.testng.SuiteRunner.privateRun(SuiteRunner.java:319)
	at org.testng.SuiteRunner.run(SuiteRunner.java:268)
	at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
	at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
	at org.testng.TestNG.runSuitesSequentially(TestNG.java:1244)
	at org.testng.TestNG.runSuitesLocally(TestNG.java:1169)
	at org.testng.TestNG.run(TestNG.java:1064)
	at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:115)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:204)
	at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:107)
	at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:112)
	at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
	at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
	at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
          Result: Received message on TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusResponse@2ccec9b8[correlationID=4e2798f4-0b32-4813-8e1c-8ae97b51a018, collectionID=TwoPillarCollection, destination=TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=MediatorUnderTest, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@78964a74[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=<null>(default)]
10:51:15.397 WARN  o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@656ea219[origDateTime=2017-03-10T10:51:15.397+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>(default), collectionID=<null>(default)]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@3f372405[correlationID=bb30073e-939b-4a3c-a6f5-5a186a0422cb, collectionID=<null>(default), destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MediatorUnderTest-cibuild01-contributor, from=MediatorUnderTest, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@656ea219[origDateTime=2017-03-10T10:51:15.397+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MediatorUnderTest, alarmText=java.lang.RuntimeException: I am supposed to throw a RuntimeException, fileID=<null>(default), collectionID=<null>(default)]]
      Test success: testMediatorRuntimeExceptionHandling
    Starting testcase ChecksumPillarModelTest
      Test starting: testPillarModelBasicFunctionality
        Description: Test the basic functions of the full reference pillar model.
        Step: Check the pillar id in the pillar model
        Step: Ask whether it can handle a file of size 0
        Step: Ask whether it can handle a file of maximum size
        Step: Check the ChecksumPillarSpec
        Step: Checkum whether the checksum pillar should download
      Test success: testPillarModelBasicFunctionality
      Test starting: testPillarModelHasFile
        Description: Test that the file exists, when placed in the archive and cache
        Step: Setup
        Step: Check whether file exists and retrieve it.
        Step: Check whether file exists.
        Step: Ask for the checksum data for the file with different checksum specs
        Step: Ask for the checksum entry for the file with different checksum specs
        Step: Ask for the checksum for the file with different checksum specs
        Step: Check extraction of checksum result set
        Step: Check retrieval of non-default checksum
        Step: Check retrieval of non-default checksum result set
        Step: Test retrieval of single checksum result set
      Test success: testPillarModelHasFile
      Test starting: testPillarModelNoFile
        Description: Test that the file exists, when placed in the archive and cache
        Step: Setup
        Step: Check whether file exists and try to retrieve it.
        Step: Verify that anexceptions are thrown when verifying file existance.
      Test success: testPillarModelNoFile
    Starting testcase GeneralMessageHandlingTest
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandler
        Description: Test the handling of the PillarMessageHandler super-class.
        Step: Setup
        Step: Test the pillar ID
      Test success: testPillarMessageHandler
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatDefaultFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on the default file id
      Test success: testPillarMessageHandlerValidateFileIDFormatDefaultFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatEnvHomePathFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path relative paths from the environment variable home folder
      Test success: testPillarMessageHandlerValidateFileIDFormatEnvHomePathFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatFolderFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id with directory path
      Test success: testPillarMessageHandlerValidateFileIDFormatFolderFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatParentFolderFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path to a parent directory
      Test success: testPillarMessageHandlerValidateFileIDFormatParentFolderFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatRootPathFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path from the root folder
      Test success: testPillarMessageHandlerValidateFileIDFormatRootPathFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatSubFolderToParentFolderFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path to a parent directory, but starting with a sub-folder
      Test success: testPillarMessageHandlerValidateFileIDFormatSubFolderToParentFolderFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatTildeHomePathFileId
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path relative paths from the tilde home folder
      Test success: testPillarMessageHandlerValidateFileIDFormatTildeHomePathFileId
        Added fixture: Initialize a new Pillar.
      Test starting: testPillarMessageHandlerValidateFileIDFormatTooLong
        Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id which has more characters than required
      Test success: testPillarMessageHandlerValidateFileIDFormatTooLong
      Finished testcase
  Finished suite
Finished project
Tests run: 72, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 67.543 sec - in TestSuite

Results :

Tests run: 72, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-reference-pillar ---
[INFO] Analyzed bundle 'Bitrepository Reference Pillar' with 43 classes
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-reference-pillar ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-reference-pillar ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/main/assembly/deploy-assembly.xml
[INFO] Reading assembly descriptor: src/test/assembly/test-deploy-assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-distribution.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-acceptance-test.tar.gz
[WARNING] Entry: bitrepository-reference-pillar-1.9-SNAPSHOT/lib/bitrepository-reference-pillar-1.9-SNAPSHOT-tests.jar longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-deploy.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-acceptance-test-deploy.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-reference-pillar ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT-distribution.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-acceptance-test.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT-acceptance-test.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT-deploy.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.9-SNAPSHOT-acceptance-test-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-SNAPSHOT-acceptance-test-deploy.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-reference-pillar ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 35.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18.jar (128 KB at 1960.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18.pom (8 KB at 112.0 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml (494 B at 13.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 47.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/maven-metadata.xml (494 B at 10.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-tests.jar (238 KB at 3605.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 55.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-sources.jar (104 KB at 1670.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 25.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-distribution.tar.gz (13314 KB at 21718.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 79.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-acceptance-test.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-acceptance-test.tar.gz (12949 KB at 18160.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 86.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-deploy.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-deploy.tar.gz (4 KB at 110.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 50.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-acceptance-test-deploy.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-acceptance-test-deploy.tar.gz (4 KB at 62.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/maven-metadata.xml (3 KB at 47.0 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Monitoring Service 1.9-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-monitoring-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-monitoring-service ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/jacoco.exec
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-monitoring-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/src/main/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-monitoring-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 14 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/classes
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-monitoring-service ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-monitoring-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 7 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/test-classes
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-monitoring-service ---
[INFO] Surefire report directory: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/surefire-reports

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running TestSuite
Configuring TestNG with: TestNG652Configurator
Starting test project Core module test
  Suite: Surefire suite
    Starting testcase StatusCollectorTest
      Test starting: testStatusCollector
        Description: Tests the status collector.
        Step: Setup
        Step: Create the collector
        Step: Start the collector
        Step: wait 2 * the interval
        Step: wait the interval + delay again
      Test success: testStatusCollector
    Starting testcase MonitorAlerterTest
      Test starting: testMonitorAlerter
        Description: Tests the org.bitrepository.monitoringservice.alarm.BasicMonitoringServiceAlerter
        Step: Setup
        Step: Create the alerter, but ignore the part of actually sending the alarms. Just log it.
        Step: Check statuses with an empty map.
        Step: Check the status when a positive entry exists.
        Step: Check the status when a negative entry exists.
10:51:37.547 WARN  o.b.m.a.BasicMonitoringServiceAlerter - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@15186ce0[origDateTime=2017-03-10T10:51:37.525+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>(default), collectionID=<null>(default)]
          Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@573a078[correlationID=1327cd85-c6ab-4823-8427-c996e45343c1, collectionID=<null>(default), destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-MonitorAlerterUnderTest-cibuild01-contributor, from=MonitorAlerterUnderTest, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@15186ce0[origDateTime=2017-03-10T10:51:37.525+01:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>(default), collectionID=<null>(default)]]
      Test success: testMonitorAlerter
    Starting testcase ComponentStatusStoreTest
      Test starting: testComponentStatus
        Description: Tests the compontent status
        Step: Setup
        Step: Validate the initial content
        Step: Update the replay counts and validate 
        Step: Test what happens when an invalid component id attempted to be updated.
10:51:38.031 WARN  o.b.m.status.ComponentStatusStore - Got status from an unexpected component: BAD-COMPONENT-ID
        Step: Try giving it a positive status
      Test success: testComponentStatus
    Starting testcase StatusEventHandlerTest
      Test starting: testStatusEventHandler
        Description: Test the GetStatusEventHandler handling of events
        Step: Setup
        Step: Validate initial calls to the mocks
        Step: Test an unhandled event.
        Step: Test the Complete event
        Step: Test the Failed event
        Step: Test the component complete status
      Test success: testStatusEventHandler
      Finished testcase
  Finished suite
Finished project
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 9.394 sec - in TestSuite

Results :

Tests run: 4, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-monitoring-service ---
[INFO] Analyzed bundle 'Bitrepository Monitoring Service' with 14 classes
[INFO] 
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-monitoring-service ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-monitoring-service] in [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/src/main/webapp]
[INFO] Webapp assembled in [142 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT.war
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-monitoring-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-monitoring-service ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-monitoring-service ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-monitoring-service ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.9-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-monitoring-service ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 30.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170310.095141-18.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170310.095141-18.war (18063 KB at 21947.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170310.095141-18.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170310.095141-18.pom (4 KB at 69.2 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml (496 B at 17.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 28.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/maven-metadata.xml (496 B at 11.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170310.095141-18-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170310.095141-18-tests.jar (15 KB at 337.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 52.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170310.095141-18-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170310.095141-18-sources.jar (19 KB at 389.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 37.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170310.095141-18-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/bitrepository-monitoring-service-1.9-20170310.095141-18-distribution.tar.gz (18061 KB at 21998.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 39.4 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Webclient 1.9-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-webclient ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-webclient ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/jacoco.exec
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-webclient ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-webclient ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 12 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/classes
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-webclient ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-webclient ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-webclient ---
[INFO] No tests to run.
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-webclient ---
[JENKINS] Recording test results
[INFO] Skipping JaCoCo execution due to missing execution data file:/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/jacoco.exec
[INFO] 
[INFO] --- maven-war-plugin:2.4:war (default-war) @ bitrepository-webclient ---
[INFO] Packaging webapp
[INFO] Assembling webapp [bitrepository-webclient] in [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp webResources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/src/main/webapp] to [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT]
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/src/main/webapp]
[INFO] Webapp assembled in [465 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT.war
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-webclient ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-webclient ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.4:single (distribution) @ bitrepository-webclient ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-webclient ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-SNAPSHOT.war
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.9-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-SNAPSHOT-distribution.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-webclient ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 36.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170310.095147-18.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170310.095147-18.war (12468 KB at 22144.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170310.095147-18.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170310.095147-18.pom (3 KB at 97.8 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml (487 B at 15.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 28.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/maven-metadata.xml (487 B at 13.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170310.095147-18-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170310.095147-18-tests.jar (3 KB at 52.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 61.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170310.095147-18-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170310.095147-18-sources.jar (17 KB at 577.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 44.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170310.095147-18-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/bitrepository-webclient-1.9-20170310.095147-18-distribution.tar.gz (12463 KB at 21194.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 31.3 KB/sec)
[JENKINS] Archiving disabled
[INFO]                                                                         
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integration 1.9-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-distribution.tar.gz
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-tests.jar
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-tests.jar (238 KB at 2124.7 KB/sec)
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18-distribution.tar.gz (13314 KB at 14550.0 KB/sec)
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ bitrepository-integration ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target
[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:prepare-agent (default) @ bitrepository-integration ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.7.5.201505241946/org.jacoco.agent-0.7.5.201505241946-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/jacoco.exec
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ bitrepository-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 33 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ bitrepository-integration ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ bitrepository-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO] 
[INFO] --- maven-compiler-plugin:3.1:testCompile (default-testCompile) @ bitrepository-integration ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ bitrepository-integration ---
[JENKINS] Recording test results[INFO] 
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-integration ---
[INFO] Skipping JaCoCo execution due to missing execution data file:/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/jacoco.exec

[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT.jar
[INFO] 
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-tests.jar
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (attach-sources-no-fork) @ bitrepository-integration ---
[INFO] Building jar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-sources.jar
[INFO] 
[INFO] --- maven-assembly-plugin:2.4:single (make-assembly) @ bitrepository-integration ---
[INFO] Reading assembly descriptor: src/main/assembly/assembly.xml
[INFO] Reading assembly descriptor: src/main/assembly/tools-assembly.xml
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18.pom
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-reference-pillar/1.9-SNAPSHOT/bitrepository-reference-pillar-1.9-20170310.095124-18.pom (8 KB at 242.7 KB/sec)
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-quickstart.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-tools.tar.gz
[WARNING] Entry: bitrepository-integration-1.9-SNAPSHOT/lib/bitrepository-reference-pillar-1.9-20170310.095124-18-distribution.tar.gz longer than 100 characters.
[WARNING] Resulting tar file can only be processed successfully by GNU compatible tar commands
[INFO] 
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @ bitrepository-integration ---
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-SNAPSHOT.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/pom.xml to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-quickstart.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-SNAPSHOT-quickstart.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.9-SNAPSHOT-tools.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-SNAPSHOT-tools.tar.gz
[INFO] 
[INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ bitrepository-integration ---
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 26.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170310.095206-18.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170310.095206-18.jar (33 KB at 899.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170310.095206-18.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170310.095206-18.pom (4 KB at 119.6 KB/sec)
[INFO] Downloading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml (489 B at 19.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 38.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/maven-metadata.xml (489 B at 15.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170310.095206-18-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170310.095206-18-tests.jar (3 KB at 61.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 64.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170310.095206-18-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170310.095206-18-sources.jar (31 KB at 1168.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 64.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170310.095206-18-quickstart.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170310.095206-18-quickstart.tar.gz (106367 KB at 28006.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 62.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170310.095206-18-tools.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/bitrepository-integration-1.9-20170310.095206-18-tools.tar.gz (119625 KB at 27627.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.9-SNAPSHOT/maven-metadata.xml (2 KB at 70.3 KB/sec)
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[JENKINS] Archiving disabled
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] Bitrepository ...................................... SUCCESS [  7.292 s]
[INFO] Bitrepository Reference Settings ................... SUCCESS [ 10.974 s]
[INFO] Bitrepository Core ................................. SUCCESS [ 48.250 s]
[INFO] Bitrepository Client ............................... SUCCESS [01:18 min]
[INFO] Bitrepository Service .............................. SUCCESS [ 28.558 s]
[INFO] Bitrepository Integrity Service .................... SUCCESS [01:59 min]
[INFO] Bitrepository Alarm Service ........................ SUCCESS [ 23.528 s]
[INFO] Bitrepository Audit Trail Service .................. SUCCESS [ 45.402 s]
[INFO] Bitrepository Reference Pillar ..................... SUCCESS [01:22 min]
[INFO] Bitrepository Monitoring Service ................... SUCCESS [ 17.163 s]
[INFO] Bitrepository Webclient ............................ SUCCESS [  5.059 s]
[INFO] Bitrepository Integration .......................... SUCCESS [ 25.856 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 08:19 min
[INFO] Finished at: 2017-03-10T10:52:19+01:00
[INFO] Final Memory: 56M/143M
[INFO] ------------------------------------------------------------------------
channel stopped
Started indexing related Jira issue keys
Successfully indexed related Jira issue keys
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Triggering a new build of Bitrepository-deploy-ci-test
Finished: SUCCESS