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 ChecksumEntryTest
Test starting: testExtendedTestCase
Description: Test the ChecksumEntry
Step: Create a ChecksumEntry
Test success: testExtendedTestCase
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@21e00efb[correlationID=38301346-01db-4876-950c-ba4db70b182b, 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@65450878[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@45ef4dcb[correlationID=38301346-01db-4876-950c-ba4db70b182b, 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@54557dd8[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@1a593fc7[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@13e59265[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@2c5b04c7[sequenceNumber=1, fileID=fileID1591705056213, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2020-06-09T14:17:36.215+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@539f0729[sequenceNumber=2, fileID=fileID1591705056213, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2020-06-09T14:17:36.216+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@ebad9a[sequenceNumber=3, fileID=fileID1591705056213, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2020-06-09T14:17:36.217+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@3fa27158[sequenceNumber=4, fileID=fileID1591705056213, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2020-06-09T14:17:36.217+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@4b2b2757[sequenceNumber=5, fileID=fileID1591705056213, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2020-06-09T14:17:36.217+02: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@4a49b26f[correlationID=b00bae47-cc47-4fab-b8de-b75de1db1114, 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@e9b227f[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@69bdb27c[correlationID=b00bae47-cc47-4fab-b8de-b75de1db1114, 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@6ee0bfee[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@393fe097[correlationID=b00bae47-cc47-4fab-b8de-b75de1db1114, 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@6ae91e0b[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@6ec36f78[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@5b7b281[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@434ad1f8[sequenceNumber=1, fileID=fileID1591705056627, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2020-06-09T14:17:36.627+02: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@617196dc[correlationID=b00bae47-cc47-4fab-b8de-b75de1db1114, 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@14bc9d25[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@2c271689[correlationID=b00bae47-cc47-4fab-b8de-b75de1db1114, 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@3977c7e4[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@54dd6160[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@24f89b6b[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@434ad1f8[sequenceNumber=1, fileID=fileID1591705056627, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2020-06-09T14:17:36.627+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@307f4223[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2020-06-09T14:17:36.627+02: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@51f26df9[correlationID=bd01b446-85c2-45b2-851f-6278f33b3f57, 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@6af78b2[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@570c6601[correlationID=bd01b446-85c2-45b2-851f-6278f33b3f57, 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@736f4c27[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@31b07a16[correlationID=bd01b446-85c2-45b2-851f-6278f33b3f57, 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@4c27fe7a[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@782fb591[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@7128d0c7[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@43fa643e[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2020-06-09T14:17:36.941+02: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@6f810a8c[correlationID=23f808b7-c15b-4e24-acd0-a760f27a3731, 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@77aa1e4[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1f0630a9[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@19ac267e[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.
14:17:38.527 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@231a475f[correlationID=647ea7be-3df7-41e1-b49e-e86aca28ac70, 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@98e2a07[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@595dda6d[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
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@8c6030b[correlationID=1a3f6f79-6943-4b3b-b0b5-d7d8f8b6babd, 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@1bdbfdcd[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@405495e7[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@15c75b4a[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@2d21dca2[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@7c5c3132[correlationID=88724cde-c39f-4f02-9d83-52f057af5346, 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@b96fb73[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@5edd911f[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1ceefb02[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@797cfaa1[correlationID=88724cde-c39f-4f02-9d83-52f057af5346, 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@e6f7638[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1ceefb02[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@38e26e29[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@52b2aa6e[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-06-09T14:17:41.074+02:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@4c85eb6b[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1591705061059, 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@32472631[correlationID=827d592b-9de5-45e3-891e-70a2e27bcc5f, 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@45055c82[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4abb5d17[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@28d78140[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@232a4cc5[correlationID=827d592b-9de5-45e3-891e-70a2e27bcc5f, 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@4c24e56e[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@28d78140[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@5ce74a18[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@482e1d45[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-06-09T14:17:41.348+02: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@36f1262c[correlationID=af50d0a3-81c7-486c-a4cd-199302030e4b, 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@5069b3c6[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@187f107[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@56062720[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@69f9ab8a[correlationID=af50d0a3-81c7-486c-a4cd-199302030e4b, 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@7493d2f0[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@56062720[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@4aa20aac[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@2dfa0bff[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-06-09T14:17:41.612+02:00]}], partialResult=false]
Step: Retrieve the ProgressResponse for the GetChecksums request
Step: Retrieve the FinalResponse for the GetChecksums request
Test success: testRestrictions
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.
14:17:41.861 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@1f489987[correlationID=009de65b-ca36-4944-9b0c-025c6a08da08, 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@62cfa78b[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1e10203[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.
14:17:43.120 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@3ef54c8d[correlationID=f41e1637-bc4a-4c72-b327-d5979204cbe9, 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@54a989ec[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4267edd9[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
14:17:43.123 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@514111ca[correlationID=f41e1637-bc4a-4c72-b327-d5979204cbe9, 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@493f14e7[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4267edd9[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@514111ca[correlationID=f41e1637-bc4a-4c72-b327-d5979204cbe9, 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@493f14e7[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4267edd9[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
14:17:44.129 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@514111ca[correlationID=f41e1637-bc4a-4c72-b327-d5979204cbe9, 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@493f14e7[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4267edd9[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@5b99ede3[correlationID=6b4b52f1-2f37-4a70-8070-20bf56d5eb9b, 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@1235aa76[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4a242227[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@76da1984[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
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@4ea505e2[correlationID=c680962d-2100-46c9-8a5e-37875cd35855, 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@33ee3a84[responseCode=DUPLICATE_FILE_FAILURE, responseText=<null>(default)], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@55fc61d8[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@4ca17241[correlationID=5678bfab-3c01-4be3-ab1d-fa7a84e23138, 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@2c1e726b[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@32c23506[correlationID=0aeb8097-6727-48a6-a1b6-094e91e0adbd, 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@3dc21e8d[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)]
14:17:48.098 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1b58b5f9[origDateTime=2020-06-09T14:17:48.095+02: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@183c271e[correlationID=96da63ef-97b5-439a-99a6-a941d6611cf6, 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@1b58b5f9[origDateTime=2020-06-09T14:17:48.095+02: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@461b078f[correlationID=590c429f-dff6-4085-99fb-f978c055eada, 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@35f0652c[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@6f18329[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@51f1ee47[correlationID=c7608de8-33d9-466a-9728-00ef748c1e32, 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@347a171e[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@265edc64[correlationID=c7608de8-33d9-466a-9728-00ef748c1e32, 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@78038d3e[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@1ca5b7c7[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@3752408b[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-06-09T14:17:49.614+02: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@7c9055e6[correlationID=078a0fed-7bba-40c8-9c84-3ae8fe7761a8, 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@45a16cac[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@256a1f2c[correlationID=e7d8f259-8f50-477c-8013-3233f32fdc02, 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@34443bb1[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@71377123[correlationID=8b5e2624-3364-47e2-8021-139d17cfb2e4, 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@5eee2617[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)]
14:17:54.212 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1bd851b4[origDateTime=2020-06-09T14:17:54.211+02: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@6c6ea911[correlationID=a23af3c2-fb03-4d78-bcc1-964b29eb6403, 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@1bd851b4[origDateTime=2020-06-09T14:17:54.211+02: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@61632f79[correlationID=f9ca14ab-8527-431b-8672-b5dec6ad57f9, 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@6e8d2ccd[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)]
14:17:54.465 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@3d29a22d[origDateTime=2020-06-09T14:17:54.465+02: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@6e7103dd[correlationID=f2656188-88e4-4f4c-a554-44aa5488d0e9, 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@3d29a22d[origDateTime=2020-06-09T14:17:54.465+02: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.
14:17:54.700 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@4a767290[correlationID=0a0f3d14-2afd-4fa7-817f-837ae691ff68, 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@1b1d094a[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)]
14:17:54.706 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@76b6b86f[origDateTime=2020-06-09T14:17:54.705+02: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@7d1d9765[correlationID=70f55f25-e7a1-4922-87d6-40525bd8d0a1, 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@76b6b86f[origDateTime=2020-06-09T14:17:54.705+02: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@798828e9[correlationID=9a962cde-8d6f-435d-9553-cb6857336074, 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@273b3afc[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@a0b8fe6[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@12f9db3f[correlationID=e01850cf-0b62-45aa-b564-e28180d00686, 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@4d408c3c[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@39648b7f[correlationID=e01850cf-0b62-45aa-b564-e28180d00686, 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@65988f4f[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@784ceacb[correlationID=2f978951-26c5-4056-b32d-25e0b70f343e, 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@17a2d74c[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@383176e1[correlationID=2f978951-26c5-4056-b32d-25e0b70f343e, 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@3928de1c[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@7569f518[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@748fb661[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2020-06-09T14:17:57.371+02:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@47ba506f[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@381dbeba[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-06-09T14:17:57.372+02:00]]
Step: Retrieve the ProgressResponse for the GetFileIDs request
Step: Retrieve the FinalResponse for the ReplaceFile request
Test success: goodCaseOperationWithChecksumsReturn
Starting testcase DeleteFileTest
Added fixture: Initialize a new Pillar.
Test starting: badCaseIdentification
Description: Tests the identification for a DeleteFile operation on the checksum 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.IdentifyPillarsForDeleteFileResponse@2b5eeae4[correlationID=900281f1-6ed4-4df6-9d8e-4be8a4b306c5, 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@39c2823b[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileID=DefaultFilebadCaseIdentification, 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: badCaseOperationMissingVerification
Description: Tests the DeleteFile functionality of the pillar for the failure scenario, where it does not have the file.
Step: Set up constants and variables.
Step: Setup for delivering pillar id and having the file
Step: Create and send the actual DeleteFile message to the pillar.
Result: Received message on TEST-TOPIC-badCaseOperationMissingVerification-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@17ba4de6[correlationID=743a3abb-0fea-43f5-97a7-34ea458cc7c1, collectionID=TwoPillarCollection, destination=TEST-TOPIC-badCaseOperationMissingVerification-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=badCaseOperationMissingVerification, version=30, minVersion=24, responseInfo=org.bitrepository.bitrepositoryelements.ResponseInfo@50ddab03[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=<null>(default)]
14:17:59.778 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@c59c954[origDateTime=2020-06-09T14:17:59.778+02:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection]
Result: Received message on TEST-ALARM-TOPIC-cibuild01 : org.bitrepository.bitrepositorymessages.AlarmMessage@49c96044[correlationID=4198a1fd-44a3-4298-89e3-907cc12036f4, collectionID=TwoPillarCollection, destination=TEST-ALARM-TOPIC-cibuild01, replyTo=TEST-TOPIC-Pillar-badCaseOperationMissingVerification-cibuild01-contributor, from=Pillar-badCaseOperationMissingVerification, to=<null>(default), version=30, minVersion=24, alarm=org.bitrepository.bitrepositoryelements.Alarm@c59c954[origDateTime=2020-06-09T14:17:59.778+02:00, alarmCode=CHECKSUM_ALARM, alarmRaiser=Pillar-badCaseOperationMissingVerification, alarmText=No mandatory checksum for destructive operation was supplied., fileID=DefaultFilebadCaseOperationMissingVerification, collectionID=TwoPillarCollection]]
Step: Retrieve the FinalResponse for the DeleteFile request
Step: Pillar should have sent an alarm
Test success: badCaseOperationMissingVerification
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationNoFile
Description: Tests the DeleteFile functionality of the pillar for the failure scenario, where it does not have the file.
Step: Set up constants and variables.
Step: Setup for delivering pillar id and not having the file
Step: Create and send the actual DeleteFile message to the pillar.
Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@61fa65c7[correlationID=d7de4d52-bd0e-45b3-8a68-ed0eaeecdf0a, 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@1b02231b[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>(default)]
Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@46103135[correlationID=d7de4d52-bd0e-45b3-8a68-ed0eaeecdf0a, 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@4c00d817[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>(default)]
Result: Received message on TEST-TOPIC-badCaseOperationNoFile-cibuild01 : org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@608e3638[correlationID=d7de4d52-bd0e-45b3-8a68-ed0eaeecdf0a, 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@27d02a85[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>(default)]
Step: Retrieve the FinalResponse for the DeleteFile request
Test success: badCaseOperationNoFile
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@46103135[correlationID=d7de4d52-bd0e-45b3-8a68-ed0eaeecdf0a, 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@4c00d817[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>(default)]
org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@608e3638[correlationID=d7de4d52-bd0e-45b3-8a68-ed0eaeecdf0a, 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@27d02a85[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>(default)]
14:18:00.962 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@46103135[correlationID=d7de4d52-bd0e-45b3-8a68-ed0eaeecdf0a, 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@4c00d817[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>(default)]
org.bitrepository.bitrepositorymessages.DeleteFileFinalResponse@608e3638[correlationID=d7de4d52-bd0e-45b3-8a68-ed0eaeecdf0a, 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@27d02a85[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileID=DefaultFilebadCaseOperationNoFile, checksumDataForExistingFile=<null>(default)]
Added fixture: Initialize a new Pillar.
Test starting: goodCaseIdentification
Description: Tests the identification for a DeleteFile 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.IdentifyPillarsForDeleteFileResponse@1f0526fc[correlationID=642d4574-f913-4eb2-9f2e-aed8429584be, 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@7a70cf38[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@78c7e153[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
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.
14:18:02.907 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 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
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.
14:18:06.213 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@55e74dde[correlationID=f4747fda-0909-4989-8cd1-e1e71f0b7123, 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@1f94500f[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=<null>(default)]
14:18:06.214 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@7eb81ff1[origDateTime=2020-06-09T14:18:06.214+02: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@11de3445[correlationID=be0cf430-6897-4820-98e4-eab7852d7e7b, 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@7eb81ff1[origDateTime=2020-06-09T14:18:06.214+02: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 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@399af2b9[correlationID=b89361e6-6eae-41e3-a7fc-6020f92b2608, 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@78dbfc95[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@7d95b464[correlationID=c24250a6-82a7-4da9-8b1b-2d113f311681, 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@1bc3ff34[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@3b81473c[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
Test starting: componentIDTest
Test success: componentIDTest
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
Test starting: getPillarCollectionsTest
Test success: getPillarCollectionsTest
Finished testcase
Finished suite
Finished project
Tests run: 72, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 49.655 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.10-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.10-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.10-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.10-SNAPSHOT-distribution.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test.tar.gz
[WARNING] Entry: bitrepository-reference-pillar-1.10-SNAPSHOT/lib/bitrepository-reference-pillar-1.10-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.10-SNAPSHOT-deploy.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-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.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-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.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-distribution.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-SNAPSHOT-deploy.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/bitrepository-reference-pillar-1.10-SNAPSHOT-acceptance-test-deploy.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-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.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 47.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37.jar (128 KB at 3641.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37.pom (8 KB at 251.1 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 23.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 83.1 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 24.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-tests.jar (244 KB at 7866.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 115.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-sources.jar (104 KB at 2876.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 109.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-distribution.tar.gz (13332 KB at 37448.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 138.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-acceptance-test.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-acceptance-test.tar.gz (12957 KB at 35017.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 148.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-deploy.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-deploy.tar.gz (4 KB at 185.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 159.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-acceptance-test-deploy.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-acceptance-test-deploy.tar.gz (4 KB at 199.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/maven-metadata.xml (3 KB at 173.2 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Monitoring Service 1.10-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 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
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.
14:18:18.420 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 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.
14:18:23.003 WARN o.b.m.a.BasicMonitoringServiceAlerter - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@25fa6889[origDateTime=2020-06-09T14:18:22.986+02: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@16ccd2bc[correlationID=e613d5a0-dbfc-4bf8-9acd-1f1702a5e484, 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@25fa6889[origDateTime=2020-06-09T14:18:22.986+02:00, alarmCode=COMPONENT_FAILURE, alarmRaiser=MonitorAlerterUnderTest, alarmText=The following components have become unresponsive: [TestMonitorService], fileID=<null>(default), collectionID=<null>(default)]]
Test success: testMonitorAlerter
Finished testcase
Finished suite
Finished project
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.335 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.10-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 [83 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-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.10-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.10-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.10-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.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-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.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-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.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 88.9 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20200609.121825-37.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20200609.121825-37.war (18082 KB at 34309.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20200609.121825-37.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20200609.121825-37.pom (4 KB at 271.5 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 44.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 94.9 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 32.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20200609.121825-37-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20200609.121825-37-tests.jar (15 KB at 834.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 118.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20200609.121825-37-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20200609.121825-37-sources.jar (19 KB at 891.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 52.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20200609.121825-37-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20200609.121825-37-distribution.tar.gz (18079 KB at 37586.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 109.5 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Webclient 1.10-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.
[JENKINS] Recording test results[INFO]
[INFO] --- jacoco-maven-plugin:0.7.5.201505241946:report (report) @ bitrepository-webclient ---
[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.10-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.10-SNAPSHOT]
[INFO] Copying webapp resources [/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/src/main/webapp]
[INFO] Webapp assembled in [351 msecs]
[INFO] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-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.10-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.10-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.10-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.10-SNAPSHOT.war to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-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.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT-distribution.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-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.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 117.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200609.121829-37.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200609.121829-37.war (12468 KB at 36455.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200609.121829-37.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200609.121829-37.pom (3 KB at 195.6 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 39.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 94.3 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 26.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200609.121829-37-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200609.121829-37-tests.jar (3 KB at 121.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 101.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200609.121829-37-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200609.121829-37-sources.jar (17 KB at 984.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 101.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200609.121829-37-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200609.121829-37-distribution.tar.gz (12463 KB at 36019.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 108.8 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integration 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-distribution.tar.gz
[INFO] Downloading: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-tests.jar
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-tests.jar (244 KB at 3810.3 KB/sec)
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37-distribution.tar.gz (13332 KB at 26243.4 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.10-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.10-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.10-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.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37.pom
[INFO] Downloaded: https://sbforge.org/nexus/content/groups/public/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200609.121813-37.pom (8 KB at 728.2 KB/sec)
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-quickstart.tar.gz
[INFO] Building tar: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-tools.tar.gz
[WARNING] Entry: bitrepository-integration-1.10-SNAPSHOT/lib/bitrepository-reference-pillar-1.10-20200609.121813-37-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.10-SNAPSHOT.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-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.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT.pom
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-tests.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-tests.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-sources.jar to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-sources.jar
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-quickstart.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-SNAPSHOT-quickstart.tar.gz
[INFO] Installing /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/bitrepository-integration-1.10-SNAPSHOT-tools.tar.gz to /home/cibuild01/.m2/repository/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-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.10-SNAPSHOT/maven-metadata.xml
[INFO] Downloaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 38.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200609.121841-37.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200609.121841-37.jar (33 KB at 1116.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200609.121841-37.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200609.121841-37.pom (4 KB at 273.5 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 31.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 108.3 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 29.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200609.121841-37-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200609.121841-37-tests.jar (3 KB at 176.0 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 101.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200609.121841-37-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200609.121841-37-sources.jar (31 KB at 2024.6 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 108.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200609.121841-37-quickstart.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200609.121841-37-quickstart.tar.gz (106461 KB at 33818.4 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 135.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200609.121841-37-tools.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200609.121841-37-tools.tar.gz (119737 KB at 40437.8 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/maven-metadata.xml (2 KB at 124.9 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 [ 3.486 s]
[INFO] Bitrepository Reference Settings ................... SUCCESS [ 6.423 s]
[INFO] Bitrepository Core ................................. SUCCESS [ 37.423 s]
[INFO] Bitrepository Client ............................... SUCCESS [01:05 min]
[INFO] Bitrepository Service .............................. SUCCESS [ 14.180 s]
[INFO] Bitrepository Integrity Service .................... SUCCESS [02:26 min]
[INFO] Bitrepository Alarm Service ........................ SUCCESS [ 13.490 s]
[INFO] Bitrepository Audit Trail Service .................. SUCCESS [ 25.301 s]
[INFO] Bitrepository Reference Pillar ..................... SUCCESS [ 57.686 s]
[INFO] Bitrepository Monitoring Service ................... SUCCESS [ 12.344 s]
[INFO] Bitrepository Webclient ............................ SUCCESS [ 3.363 s]
[INFO] Bitrepository Integration .......................... SUCCESS [ 17.592 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 06:49 min
[INFO] Finished at: 2020-06-09T14:18:51+02:00
[INFO] Final Memory: 61M/145M
[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
Console Output
Help us localize this page