ract 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 ChecksumPillarModelTest
Test starting: testPillarModelBasicFunctionality
Description: Test the basic functions of the full reference pillar model.
Step: Check the pillar id in the pillar model
Step: Ask whether it can handle a file of size 0
Step: Ask whether it can handle a file of maximum size
Step: Check the ChecksumPillarSpec
Step: Checkum whether the checksum pillar should download
Test success: testPillarModelBasicFunctionality
Test starting: testPillarModelHasFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and retrieve it.
Step: Check whether file exists.
Step: Ask for the checksum data for the file with different checksum specs
Step: Ask for the checksum entry for the file with different checksum specs
Step: Ask for the checksum for the file with different checksum specs
Step: Check extraction of checksum result set
Step: Check retrieval of non-default checksum
Step: Check retrieval of non-default checksum result set
Step: Test retrieval of single checksum result set
Test success: testPillarModelHasFile
Test starting: testPillarModelNoFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and try to retrieve it.
Step: Verify that anexceptions are thrown when verifying file existance.
Test success: testPillarModelNoFile
Starting testcase 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@13d2a198[correlationID=9dae22d2-60f8-4a42-b17e-54ec0a2c74b3, 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@563f9766[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@674fee6d[correlationID=fecbe81b-aa80-40a9-804a-40d976f4f402, 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@3c556542[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=No mandatory checksum for destructive operation was supplied.], pillarID=Pillar-badCaseOperationMissingVerification, fileID=DefaultFilebadCaseOperationMissingVerification, checksumDataForExistingFile=<null>(default)]
10:34:41.000 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@7fed08c6[origDateTime=2020-07-03T10:34:41.000+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@6749add0[correlationID=98aeb822-8c42-4ae0-8239-556497ca2ab0, 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@7fed08c6[origDateTime=2020-07-03T10:34:41.000+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@2a6d0fb3[correlationID=394054d2-1b71-4bcc-800d-80287305dbdf, 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@5fa5dc92[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
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@4807382f[correlationID=22948ae5-c627-43fb-ae40-1a1f2ce0cd66, 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@36c86704[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@4ed4f01f[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
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@3c83d370[correlationID=d0dbaa54-c33e-4635-98b1-74c6507d3d20, 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@5a9ae0ad[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@5bc11e3c[correlationID=d0dbaa54-c33e-4635-98b1-74c6507d3d20, 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@3436da82[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsMaximumNumberOfResults, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@6e13743c[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@1001ede3[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@43623121[sequenceNumber=1, fileID=fileID1593765283899, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=CHECKSUM_CALCULATED, actionDateTime=2020-07-03T10:34:43.901+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@41820105[sequenceNumber=2, fileID=fileID1593765283899, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=DELETE_FILE, actionDateTime=2020-07-03T10:34:43.901+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@34453f9d[sequenceNumber=3, fileID=fileID1593765283899, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FAILURE, actionDateTime=2020-07-03T10:34:43.905+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@2bb4b203[sequenceNumber=4, fileID=fileID1593765283899, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=FILE_MOVED, actionDateTime=2020-07-03T10:34:43.906+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@798d656d[sequenceNumber=5, fileID=fileID1593765283899, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=GET_CHECKSUMS, actionDateTime=2020-07-03T10:34:43.906+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@553c2c70[correlationID=8a44f810-8b5b-467b-975c-8b33c6711df8, 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@5e02ed6a[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@45d32ca3[correlationID=8a44f810-8b5b-467b-975c-8b33c6711df8, 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@71b8c7c5[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@38980d25[correlationID=8a44f810-8b5b-467b-975c-8b33c6711df8, 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@257e54b2[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@7994c28a[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@4e25b492[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@36ac7956[sequenceNumber=1, fileID=fileID1593765284211, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2020-07-03T10:34:44.211+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@612070f5[correlationID=8a44f810-8b5b-467b-975c-8b33c6711df8, 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@3eff7ec9[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@5d9dcca0[correlationID=8a44f810-8b5b-467b-975c-8b33c6711df8, 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@82e688c[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSpecificRequests, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@6a6b06a4[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@2f273416[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@36ac7956[sequenceNumber=1, fileID=fileID1593765284211, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=ACTOR, actionOnFile=OTHER, actionDateTime=2020-07-03T10:34:44.211+02:00, info=InFo, operationID=operationID, certificateID=certificateid, auditTrailInformation=auditTrails],org.bitrepository.bitrepositoryelements.AuditTrailEvent@1c6c059e[sequenceNumber=2, fileID=notThisFile, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=UnknownActor, actionOnFile=FAILURE, actionDateTime=2020-07-03T10:34:44.211+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@2ceb0ef3[correlationID=2b6244c2-c5e3-489d-a983-fc0932fce561, 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@382234cc[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@63dd4d70[correlationID=2b6244c2-c5e3-489d-a983-fc0932fce561, 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@c16feeb[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@78fee50c[correlationID=2b6244c2-c5e3-489d-a983-fc0932fce561, 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@51d32a8b[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], contributor=Pillar-checksumPillarGetAuditTrailsSuccessful, resultingAuditTrails=org.bitrepository.bitrepositoryelements.ResultingAuditTrails@58ec5b0c[resultAddress=<null>(default), auditTrailEvents=org.bitrepository.bitrepositoryelements.AuditTrailEvents@6336075c[auditTrailEvent={org.bitrepository.bitrepositoryelements.AuditTrailEvent@6cef48b3[sequenceNumber=1, fileID=fileid, reportingComponent=MOCK-AUDIT-MANAGER, actorOnFile=actor, actionOnFile=OTHER, actionDateTime=2020-07-03T10:34:44.499+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 GetFileIDsTest
Added fixture: Initialize a new Pillar.
Test starting: badCaseIdentification
Description: Tests the identification for a GetFileIDs operation on the pillar for the failure scenario, when the file is missing.
Step: Set up constants and variables.
Step: Setup for delivering pillar id and not having the file
Step: Create and send the identify request message.
10:34:44.778 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@5a84e8ec[correlationID=47cef6f3-b4fc-4a6b-b9d1-5942bac9487e, 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@65b1321f[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@46a2760a[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>(default)], timeToDeliver=<null>(default)]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: badCaseIdentification
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationNoFile
Description: Tests the GetFileIDs functionality of the pillar for the failure scenario, where it does not have the file.
Step: Set up constants and variables.
Step: Setup for not having the file
Step: Create and send the actual GetFileIDs message to the pillar.
10:34:46.051 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@76eb41bc[correlationID=c0cf8640-661d-46a2-bfc0-998d85cd92fd, 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@dae3613[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@58c9fcbf[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
10:34:46.058 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@71d2fac0[correlationID=c0cf8640-661d-46a2-bfc0-998d85cd92fd, 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@d304447[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@58c9fcbf[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@71d2fac0[correlationID=c0cf8640-661d-46a2-bfc0-998d85cd92fd, 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@d304447[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@58c9fcbf[fileID=DefaultFilebadCaseOperationNoFile, allFileIDs=<null>(default)], resultingFileIDs=<null>(default), partialResult=<null>(default)]
10:34:47.063 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetFileIDsFinalResponse@71d2fac0[correlationID=c0cf8640-661d-46a2-bfc0-998d85cd92fd, 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@d304447[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@58c9fcbf[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@513d4389[correlationID=dd4b2b60-30fb-4489-9b91-8e6d7e25a860, 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@67ee5b15[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@4dcaab6b[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@7b13fc9f[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@1a1d9a9d[correlationID=52d816b6-6aa1-4f03-ae5a-c5b902eaf632, 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@618e8791[responseCode=DUPLICATE_FILE_FAILURE, responseText=<null>(default)], pillarID=Pillar-badCaseIdentification, fileID=DefaultFilebadCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@b7c3b07[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@afe092e[correlationID=c84fa432-80d3-4cea-99bf-1845c642f490, 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@7b62b17c[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@21aa13cf[correlationID=b8a4a9b7-96f5-411a-a68a-813a14d80f45, 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@5205391d[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=A checksum is required for the PutFile operation to be performed.], pillarID=Pillar-badCasePutOperationNoValidationChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFilebadCasePutOperationNoValidationChecksum, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForNewFile=<null>(default), checksumDataForExistingFile=<null>(default)]
10:34:51.199 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@11733fbb[origDateTime=2020-07-03T10:34:51.198+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@561e62ed[correlationID=a168990c-2651-4ade-894e-296b335ff2a7, 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@11733fbb[origDateTime=2020-07-03T10:34:51.198+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@56d1c219[correlationID=c9440607-4e74-4914-8649-498ba547e8a4, 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@3f853a53[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], pillarID=Pillar-goodCaseIdentification, fileID=DefaultFilegoodCaseIdentification, pillarChecksumSpec=<null>(default), checksumDataForExistingFile=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@5d3d8794[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@26e40792[correlationID=0b53adc8-cf89-4af0-a56f-25a75b139ade, 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@66a9c677[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@5c8b33bd[correlationID=0b53adc8-cf89-4af0-a56f-25a75b139ade, 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@647e955d[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@2a946570[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@10de4140[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-07-03T10:34:52.826+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
Test starting: getPillarCollectionsTest
Test success: getPillarCollectionsTest
Starting testcase ArchiveDirectoryTest
Test starting: testArchiveDirectoryExistingFile
Description: Test the ArchiveDirectory when the file exists
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryExistingFile
Test starting: testArchiveDirectoryExistingFolderFile
Description: Test the ArchiveDirectory when the file exists
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryExistingFolderFile
Test starting: testArchiveDirectoryMissingFile
Description: Test the ArchiveDirectory when the file is missing.
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryMissingFile
Test starting: testArchiveDirectoryMissingFolderFile
Description: Test the ArchiveDirectory when the file is missing.
Step: Setup
Step: Validate the existence of the file
Step: Delete the file.
Test success: testArchiveDirectoryMissingFolderFile
Test starting: testArchiveDirectoryMoveFileToArchive
Description: Testing the error scenarios when moving a file from tmp to archive for the ArchiveDirectory.
Step: Setup
Step: Moving file from tmp to archive
Step: Create file in both tmp and archive.
Step: Moving file from tmp to archive
Step: Remove the file from archive and try again
Test success: testArchiveDirectoryMoveFileToArchive
Test starting: testArchiveDirectoryMoveFolderFileToArchive
Description: Testing the error scenarios when moving a file from tmp to archive for the ArchiveDirectory.
Step: Setup
Step: Moving file from tmp to archive
Step: Create file in both tmp and archive.
Step: Moving file from tmp to archive
Step: Remove the file from archive and try again
Test success: testArchiveDirectoryMoveFolderFileToArchive
Test starting: testArchiveDirectoryNewFile
Description: Testing the ArchiveDirectory handling of a new file.
Step: Setup
Step: Retrieve tmp file
Step: Request a new file for the tmp dir
Step: Retrieve tmp file
Step: Request another new file with the same name
Step: Move the file from tmp to archive
Test success: testArchiveDirectoryNewFile
Test starting: testArchiveDirectoryNewFolderFile
Description: Testing the ArchiveDirectory handling of a new file.
Step: Setup
Step: Retrieve tmp file
Step: Request a new file for the tmp dir
Step: Retrieve tmp file
Step: Request another new file with the same name
Step: Move the file from tmp to archive
Test success: testArchiveDirectoryNewFolderFile
Test starting: testArchiveDirectoryRemoveFile
Description: Testing the error scenarios when removing files from the archive.
Step: Setup
Step: Remove nonexisting file from archive
Step: Remove nonexisting file from tmp
Step: Create file in both tmp, archive and retain directories.
Step: Remove the file from archive and tmp
Test success: testArchiveDirectoryRemoveFile
Test starting: testArchiveDirectoryRemoveFolderFile
Description: Testing the error scenarios when removing files from the archive.
Step: Setup
Step: Remove nonexisting file from archive
Step: Remove nonexisting file from tmp
Step: Create file in both tmp, archive and retain directories.
Step: Remove the file from archive and tmp
Test success: testArchiveDirectoryRemoveFolderFile
Starting testcase ChecksumDatabaseMigrationTest
Test starting: testMigratingChecksumDatabaseFromV3ToV4
Description: Tests that the checksums table can be migrated from version 3 to 4, e.g. changing the column calculatedchecksumdate from timestamp to bigint.
Step: Ensure cleanup
10:34:54.763 WARN o.b.common.utils.FileUtils - Could not delete '/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/test/referencepillar/checksumdb-for-migration'
Step: Unzipping and connecting to checksum database version 3
Step: Validate setup
Step: Ingest a entry to the database with a date for the calculationdate
Step: Perform migration
10:34:55.317 WARN o.b.service.database.DatabaseUtils - Migrating ChecksumDB from version 3 to 4.
Step: Validate the migration
Test success: testMigratingChecksumDatabaseFromV3ToV4
Starting testcase FullPillarModelTest
Test starting: testPillarModelBasicFunctionality
Description: Test the basic functions of the full reference pillar model.
Step: Check the pillar id in the pillar model
Step: Ask whether it can handle a file of size 0
Step: Ask whether it can handle a file of maximum size
Step: Check the ChecksumPillarSpec
Test success: testPillarModelBasicFunctionality
Test starting: testPillarModelHasFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and retrieve it.
Step: Verify that no exceptions are thrown when verifying file existance.
Step: Check retrieval of non-default checksum
Test success: testPillarModelHasFile
Test starting: testPillarModelNoFile
Description: Test that the file exists, when placed in the archive and cache
Step: Setup
Step: Check whether file exists and try to retrieve it.
Step: Verify that anexceptions are thrown when verifying file existance.
10:34:56.561 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 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@5dea04f[correlationID=bd82ceda-f6d8-4eb3-b1dc-839e99003f30, 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@41fe6103[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@5f536620[correlationID=00db22a5-222f-41c3-bc78-bf91e0a4744f, 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@78707c5b[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFilegoodCaseIdentification, pillarID=Pillar-goodCaseIdentification, timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@7ee1077f[timeMeasureUnit=MILLISECONDS, timeMeasureValue=1000]]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: goodCaseIdentification
Test starting: componentIDTest
Test success: componentIDTest
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@ced5671[correlationID=e9c0beaf-f343-4b64-afdf-ac96d1fa89bf, 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@1f0d5dec[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@13bdf19[correlationID=c45e414a-bcd6-4650-97d0-9712ab609b4b, 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@7cad7d48[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@7c6c3b42[correlationID=e0951ee9-1a50-468f-a2cc-bfb635afe070, 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@539ba851[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=According to the contract a checksum for file to be deleted during the replacing operation is required.], pillarID=Pillar-badCaseOperationNoDestructiveChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
10:35:02.277 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@55bc58df[origDateTime=2020-07-03T10:35:02.277+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@43e3da00[correlationID=3e725be5-eb16-48c6-9bcd-7d52c1483029, 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@55bc58df[origDateTime=2020-07-03T10:35:02.277+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@40045f23[correlationID=c945840a-b9d5-4d43-a4d8-953e3559a455, 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@4ed59c18[responseCode=NEW_FILE_CHECKSUM_FAILURE, responseText=According to the contract a checksum for new file in the replacing operation is required.], pillarID=Pillar-badCaseOperationNoValidationChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
10:35:02.479 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@6002379e[origDateTime=2020-07-03T10:35:02.476+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@71d181c8[correlationID=4a53e681-01f3-4da3-a573-0477a48768f3, 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@6002379e[origDateTime=2020-07-03T10:35:02.476+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.
10:35:02.721 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@6a306f63[correlationID=bcb77401-cf12-47d0-a375-74229dc4d298, 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@1057d9a4[responseCode=EXISTING_FILE_CHECKSUM_FAILURE, responseText=Requested to replace the file 'DefaultFile' with checksum '1234cccccccc4321', but our file had a different checksum.], pillarID=Pillar-badCaseOperationWrongDestructiveChecksum, pillarChecksumSpec=<null>(default), fileID=DefaultFile, fileAddress=file:../bitrepository-core/src/test/resources/test-files//default-test-file.txt, checksumDataForExistingFile=<null>(default), checksumDataForNewFile=<null>(default)]
10:35:02.729 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@5049517a[origDateTime=2020-07-03T10:35:02.728+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@67574a80[correlationID=a77dd875-5ed7-42f9-ad6b-39735b2e8566, 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@5049517a[origDateTime=2020-07-03T10:35:02.728+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@4d8c69ee[correlationID=51124bee-4bf1-47f5-ab67-d06b848da76d, 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@6b890860[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileID=DefaultFile, pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@5796196b[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@6a13143[correlationID=dbc156d8-1d3c-4a2f-934f-e69350ed6288, 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@4fe85096[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@62a795a8[correlationID=dbc156d8-1d3c-4a2f-934f-e69350ed6288, 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@6d039b96[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@5c93b372[correlationID=3818ca25-fa7f-4943-9dad-f8c80484f504, 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@4b8ae62e[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@4b43f28[correlationID=3818ca25-fa7f-4943-9dad-f8c80484f504, 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@1ac45b4[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@40e57ed0[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5cc24b74[checksumType=HMAC_SHA512, checksumSalt={97,98}, otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,34}, calculationTimestamp=2020-07-03T10:35:05.535+02:00], checksumDataForNewFile=org.bitrepository.bitrepositoryelements.ChecksumDataForFileTYPE@79aa72bb[checksumSpec=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@1ac819df[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-07-03T10:35:05.537+02:00]]
Step: Retrieve the ProgressResponse for the GetFileIDs request
Step: Retrieve the FinalResponse for the ReplaceFile request
Test success: goodCaseOperationWithChecksumsReturn
Starting testcase MediatorTest
Test starting: testMediatorRuntimeExceptionHandling
Description: Tests the handling of a runtime exception
Step: Setup create and start the mediator.
Step: Send a request to the mediator.
10:35:07.792 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:134)
at org.testng.internal.TestInvoker.invokeMethod(TestInvoker.java:597)
at org.testng.internal.TestInvoker.invokeTestMethod(TestInvoker.java:173)
at org.testng.internal.MethodRunner.runInSequence(MethodRunner.java:46)
at org.testng.internal.TestInvoker$MethodInvocationAgent.invoke(TestInvoker.java:816)
at org.testng.internal.TestInvoker.invokeTestMethods(TestInvoker.java:146)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:146)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:128)
at java.util.ArrayList.forEach(ArrayList.java:1249)
at org.testng.TestRunner.privateRun(TestRunner.java:766)
at org.testng.TestRunner.run(TestRunner.java:587)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:384)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:378)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:337)
at org.testng.SuiteRunner.run(SuiteRunner.java:286)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:53)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:96)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1187)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1109)
at org.testng.TestNG.runSuites(TestNG.java:1039)
at org.testng.TestNG.run(TestNG.java:1007)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeMulti(TestNGDirectoryTestSuite.java:193)
at org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:94)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:146)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:377)
at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:138)
at org.apache.maven.surefire.booter.ForkedBooter.run(ForkedBooter.java:465)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:451)
Result: Received message on TEST-TOPIC-testMediatorRuntimeExceptionHandling-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyContributorsForGetStatusResponse@1e47ddc3[correlationID=6b17fe04-6e54-4d63-b177-016f552d1a14, 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@70aea571[responseCode=FAILURE, responseText=java.lang.RuntimeException: I am supposed to throw a RuntimeException], contributor=TEST-TOPIC-cibuild01, timeToDeliver=<null>(default)]
10:35:07.795 WARN o.b.p.common.PillarAlarmDispatcher - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@71ec704d[origDateTime=2020-07-03T10:35:07.794+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@51e51276[correlationID=4e9dc8c1-108e-4655-a805-ee4a6c4f6958, 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@71ec704d[origDateTime=2020-07-03T10:35:07.794+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 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@7ffe3144[correlationID=149f1b0e-fd38-490b-ac77-ca071de4d1bf, 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@66529948[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2de69a61[fileID=DefaultFilebadCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6b2a290d[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], pillarID=Pillar-badCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=<null>(default)]
Step: Retrieve and validate the response getPillarID() the pillar.
Test success: badCaseIdentification
Added fixture: Initialize a new Pillar.
Test starting: badCaseOperationNoFile
Description: Tests the GetChecksums functionality of the pillar for the failure scenario, where it does not have the file.
Step: Set up constants and variables.
Step: Setup for not having the file
Step: Create and send the actual GetChecksums message to the pillar.
10:35:09.192 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@3b6c5f14[correlationID=414353da-f223-4d7b-9496-0dfa687a0675, 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@3f5ef532[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c321ea1[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
10:35:09.199 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@797618c3[correlationID=414353da-f223-4d7b-9496-0dfa687a0675, 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@31c995ba[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c321ea1[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
10:35:09.204 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@13019659[correlationID=414353da-f223-4d7b-9496-0dfa687a0675, 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@5af834fa[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c321ea1[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
Step: Retrieve the FinalResponse for the GetChecksums request
Test success: badCaseOperationNoFile
Result: The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@797618c3[correlationID=414353da-f223-4d7b-9496-0dfa687a0675, 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@31c995ba[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c321ea1[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@13019659[correlationID=414353da-f223-4d7b-9496-0dfa687a0675, 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@5af834fa[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c321ea1[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
10:35:10.213 WARN o.b.protocol.bus.MessageReceiver - The following messages haven't been handled by the testcase:
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@797618c3[correlationID=414353da-f223-4d7b-9496-0dfa687a0675, 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@31c995ba[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c321ea1[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@13019659[correlationID=414353da-f223-4d7b-9496-0dfa687a0675, 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@5af834fa[responseCode=FILE_NOT_FOUND_FAILURE, responseText=File not found.], pillarID=Pillar-badCaseOperationNoFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@6c321ea1[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=<null>(default), partialResult=<null>(default)]
Added fixture: Initialize a new Pillar.
Test starting: goodCaseIdentification
Description: Tests the identification for a GetChecksums operation on the pillar for the successful scenario.
Step: Set up constants and variables.
Step: Setup for having the file and delivering pillar id
Step: Create and send the identify request message.
Result: Received message on TEST-TOPIC-goodCaseIdentification-cibuild01 : org.bitrepository.bitrepositorymessages.IdentifyPillarsForGetChecksumsResponse@6eec86d5[correlationID=586de3ca-6f37-4635-a336-801c8f8fb9bd, 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@7e4b5b3a[responseCode=IDENTIFICATION_POSITIVE, responseText=Operation acknowledged and accepted.], fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@1b83b7b8[fileID=DefaultFilegoodCaseIdentification, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@4ffc5d53[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], pillarID=Pillar-goodCaseIdentification, pillarChecksumSpec=<null>(default), timeToDeliver=org.bitrepository.bitrepositoryelements.TimeMeasureTYPE@45aca057[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@786a90d2[correlationID=df663397-3d31-45d0-87a3-9df730d09f82, 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@4a617a25[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationAllFiles, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@6ae3aeb[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5d6c3486[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
Result: Received message on TEST-TOPIC-goodCaseOperationAllFiles-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@7a3ff9a2[correlationID=df663397-3d31-45d0-87a3-9df730d09f82, 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@47e74493[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationAllFiles, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@5d6c3486[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@48245fbc[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@63087200[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-07-03T10:35:11.617+02:00],org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@667f652a[fileID=goodCaseOperationAllFiles-cibuild01--Test-File-1593765311600, 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@69cf08a5[correlationID=f07ea13c-5837-4cec-b32a-d36b5ea16cee, 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@7f8e4389[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-goodCaseOperationSingleFile, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@2097a9e3[fileID=DefaultFilegoodCaseOperationSingleFile, allFileIDs=<null>(default)], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@b39920[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
Result: Received message on TEST-TOPIC-goodCaseOperationSingleFile-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@11a823b3[correlationID=f07ea13c-5837-4cec-b32a-d36b5ea16cee, 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@1c37b804[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-goodCaseOperationSingleFile, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@b39920[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@1f2d2d0[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@1d943157[fileID=DefaultFilegoodCaseOperationSingleFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-07-03T10:35:11.868+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@69abe626[correlationID=5634fcb5-d5d1-4166-ae97-3cf4e6ce76d1, 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@50043914[responseCode=OPERATION_ACCEPTED_PROGRESS, responseText=Starting to calculate checksums.], pillarID=Pillar-testRestrictions, fileIDs=org.bitrepository.bitrepositoryelements.FileIDs@406f7217[fileID=<null>(default), allFileIDs=true], checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@168d823[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultAddress=<null>(default)]
Result: Received message on TEST-TOPIC-testRestrictions-cibuild01 : org.bitrepository.bitrepositorymessages.GetChecksumsFinalResponse@37c494fe[correlationID=5634fcb5-d5d1-4166-ae97-3cf4e6ce76d1, 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@46f9c78b[responseCode=OPERATION_COMPLETED, responseText=<null>(default)], pillarID=Pillar-testRestrictions, checksumRequestForExistingFile=org.bitrepository.bitrepositoryelements.ChecksumSpecTYPE@168d823[checksumType=MD5, checksumSalt=<null>(default), otherChecksumType=<null>(default)], resultingChecksums=org.bitrepository.bitrepositoryelements.ResultingChecksums@7dbdea89[resultAddress=<null>(default), checksumDataItems={org.bitrepository.bitrepositoryelements.ChecksumDataForChecksumSpecTYPE@3a538cdd[fileID=DefaultFile, checksumValue={18,52,-52,-52,-52,-52,67,33}, calculationTimestamp=2020-07-03T10:35:12.063+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 GeneralMessageHandlingTest
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandler
Description: Test the handling of the PillarMessageHandler super-class.
Step: Setup
Step: Test the pillar ID
Test success: testPillarMessageHandler
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatDefaultFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on the default file id
Test success: testPillarMessageHandlerValidateFileIDFormatDefaultFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatEnvHomePathFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path relative paths from the environment variable home folder
Test success: testPillarMessageHandlerValidateFileIDFormatEnvHomePathFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatFolderFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id with directory path
Test success: testPillarMessageHandlerValidateFileIDFormatFolderFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatParentFolderFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path to a parent directory
Test success: testPillarMessageHandlerValidateFileIDFormatParentFolderFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatRootPathFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path from the root folder
Test success: testPillarMessageHandlerValidateFileIDFormatRootPathFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatSubFolderToParentFolderFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path to a parent directory, but starting with a sub-folder
Test success: testPillarMessageHandlerValidateFileIDFormatSubFolderToParentFolderFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatTildeHomePathFileId
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id containing path relative paths from the tilde home folder
Test success: testPillarMessageHandlerValidateFileIDFormatTildeHomePathFileId
Added fixture: Initialize a new Pillar.
Test starting: testPillarMessageHandlerValidateFileIDFormatTooLong
Description: Test the validation of file id formats of the PillarMessageHandler super-class on a file id which has more characters than required
Test success: testPillarMessageHandlerValidateFileIDFormatTooLong
Finished testcase
Finished suite
Finished project
[INFO] Tests run: 72, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 54.292 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 72, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[JENKINS] Recording test results
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-reference-pillar ---
[INFO] Loading execution data file /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-reference-pillar/target/jacoco.exec
[INFO] Analyzed bundle 'Bitrepository Reference Pillar' with 41 classes
[INFO]
[INFO] --- maven-jar-plugin:3.2.0: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:3.2.0: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:3.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:3.3.0: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
[WARNING] Entry: bitrepository-reference-pillar-1.10-SNAPSHOT/lib/listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar longer than 100 characters.
[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:3.0.0-M1: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:3.0.0-M1: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 54.7 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-20200703.083522-50.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200703.083522-50.jar (128 KB at 1146.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-20200703.083522-50.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-reference-pillar/1.10-SNAPSHOT/bitrepository-reference-pillar-1.10-20200703.083522-50.pom (6 KB at 166.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-20200703.083522-50-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-20200703.083522-50-tests.jar (249 KB at 7541.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-20200703.083522-50-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-20200703.083522-50-sources.jar (106 KB at 3112.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-20200703.083522-50-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-20200703.083522-50-distribution.tar.gz (14768 KB at 34746.8 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-20200703.083522-50-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-20200703.083522-50-acceptance-test.tar.gz (21344 KB at 37378.7 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-20200703.083522-50-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-20200703.083522-50-deploy.tar.gz (4 KB at 219.8 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-20200703.083522-50-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-20200703.083522-50-acceptance-test-deploy.tar.gz (4 KB at 186.6 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 25.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 94.5 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 25.4 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Monitoring Service 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-monitoring-service ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-monitoring-service ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-monitoring-service ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/jacoco.exec
[INFO]
[INFO] --- maven-resources-plugin:3.1.0: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.8.1:compile (default-compile) @ bitrepository-monitoring-service ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 15 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/classes
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-monitoring-service ---
[INFO] Scanning for classes to check...
[INFO] Reading bundled API signatures: jdk-unsafe-1.8
[INFO] Reading bundled API signatures: jdk-deprecated-1.8
[INFO] Reading bundled API signatures: jdk-non-portable
[INFO] Reading bundled API signatures: jdk-reflection
[INFO] Loading classes to check...
[INFO] Scanning classes for violations...
[INFO] Scanned 18 class file(s) for forbidden API invocations (in 0.07s), 0 error(s).
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-monitoring-service ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0: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.8.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:3.0.0-M4:test (default-test) @ bitrepository-monitoring-service ---
[INFO]
[INFO] -------------------------------------------------------
[INFO] T E S T S
[INFO] -------------------------------------------------------
[INFO] Running TestSuite
Starting test project Core module test
Suite: Surefire suite
Starting testcase StatusCollectorTest
Test starting: testStatusCollector
Description: Tests the status collector.
Step: Setup
Step: Create the collector
Step: Start the collector
Step: wait 2 * the interval
Step: wait the interval + delay again
Test success: testStatusCollector
Starting testcase 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.
10:35:31.668 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 MonitorAlerterTest
Test starting: testMonitorAlerter
Description: Tests the org.bitrepository.monitoringservice.alarm.BasicMonitoringServiceAlerter
Step: Setup
Step: Create the alerter, but ignore the part of actually sending the alarms. Just log it.
Step: Check statuses with an empty map.
Step: Check the status when a positive entry exists.
Step: Check the status when a negative entry exists.
10:35:34.045 WARN o.b.m.a.BasicMonitoringServiceAlerter - Sending alarm: org.bitrepository.bitrepositoryelements.Alarm@1fcfcf37[origDateTime=2020-07-03T10:35:34.029+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@54087bdb[correlationID=a35a89d5-32a3-4918-b65a-830b47f63768, 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@1fcfcf37[origDateTime=2020-07-03T10:35:34.029+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
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.878 s - in TestSuite
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[JENKINS] Recording test results
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-monitoring-service ---
[INFO] Loading execution data file /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/jacoco.exec
[INFO] Analyzed bundle 'Bitrepository Monitoring Service' with 14 classes
[INFO]
[INFO] --- maven-war-plugin:3.3.0: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] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-monitoring-service/target/bitrepository-monitoring-service-1.10-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:3.2.0: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:3.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:3.3.0: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:3.0.0-M1: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:3.0.0-M1: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 74.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-20200703.083537-50.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20200703.083537-50.war (21393 KB at 38407.0 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-20200703.083537-50.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-monitoring-service/1.10-SNAPSHOT/bitrepository-monitoring-service-1.10-20200703.083537-50.pom (4 KB at 207.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-20200703.083537-50-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-20200703.083537-50-tests.jar (15 KB at 671.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-20200703.083537-50-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-20200703.083537-50-sources.jar (22 KB at 1107.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-20200703.083537-50-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-20200703.083537-50-distribution.tar.gz (21392 KB at 35125.1 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 28.5 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 101.6 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)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Webclient 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-webclient ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-webclient ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-webclient ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/jacoco.exec
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-webclient ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-webclient ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 13 source files to /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/classes
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-webclient ---
[INFO] Scanning for classes to check...
[INFO] Reading bundled API signatures: jdk-unsafe-1.8
[INFO] Reading bundled API signatures: jdk-deprecated-1.8
[INFO] Reading bundled API signatures: jdk-non-portable
[INFO] Reading bundled API signatures: jdk-reflection
[INFO] Loading classes to check...
[INFO] Scanning classes for violations...
[INFO] Scanned 13 class file(s) for forbidden API invocations (in 0.11s), 0 error(s).
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-webclient ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0: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.8.1:testCompile (default-testCompile) @ bitrepository-webclient ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-webclient ---
[INFO] No tests to run.
[INFO]
[JENKINS] Recording test results[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-webclient ---
[INFO] Skipping JaCoCo execution due to missing execution data file.
[INFO]
[INFO] --- maven-war-plugin:3.3.0: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] Building war: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-webclient/target/bitrepository-webclient-1.10-SNAPSHOT.war
[INFO]
[INFO] --- maven-jar-plugin:3.2.0: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:3.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:3.3.0: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:3.0.0-M1: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:3.0.0-M1: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 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-20200703.083543-50.war
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200703.083543-50.war (15550 KB at 35745.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200703.083543-50.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200703.083543-50.pom (3 KB at 124.2 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200703.083543-50-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200703.083543-50-tests.jar (3 KB at 158.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200703.083543-50-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200703.083543-50-sources.jar (20 KB at 1118.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200703.083543-50-distribution.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-webclient/1.10-SNAPSHOT/bitrepository-webclient-1.10-20200703.083543-50-distribution.tar.gz (15545 KB at 36661.9 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 36.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 70.7 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 29.7 KB/sec)
[JENKINS] Archiving disabled
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Bitrepository Integration 1.10-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-clean-plugin:3.1.0:clean (default-clean) @ bitrepository-integration ---
[INFO] Deleting /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target
[INFO]
[INFO] --- maven-enforcer-plugin:3.0.0-M3:enforce (enforce-maven) @ bitrepository-integration ---
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:prepare-agent (default) @ bitrepository-integration ---
[INFO] argLine set to -javaagent:/home/cibuild01/.m2/repository/org/jacoco/org.jacoco.agent/0.8.5/org.jacoco.agent-0.8.5-runtime.jar=destfile=/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/jacoco.exec
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ bitrepository-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 33 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ bitrepository-integration ---
[INFO] No sources to compile
[INFO]
[INFO] --- forbiddenapis:2.7:check (default) @ bitrepository-integration ---
[INFO] Scanning for classes to check...
[WARNING] No classes found in '/home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/classes' (includes=[**/*.class], excludes=null), forbiddenapis check skipped.
[INFO]
[INFO] --- forbiddenapis:2.7:testCheck (default) @ bitrepository-integration ---
[INFO] Scanning for classes to check...
[WARNING] Classes directory does not exist, forbiddenapis check skipped: /home/cibuild01/workspace/Bitrepository-reference-test/bitrepository-integration/target/test-classes
[INFO]
[INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) @ bitrepository-integration ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 1 resource
[INFO]
[INFO] --- maven-compiler-plugin:3.8.1:testCompile (default-testCompile) @ bitrepository-integration ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:3.0.0-M4:test (default-test) @ bitrepository-integration ---
[JENKINS] Recording test results
[INFO]
[INFO] --- jacoco-maven-plugin:0.8.5:report (report) @ bitrepository-integration ---
[INFO] Skipping JaCoCo execution due to missing execution data file.
[INFO]
[INFO] --- maven-jar-plugin:3.2.0: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:3.2.0: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:3.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:3.3.0: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] 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-SNAPSHOT-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:3.0.0-M1: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:3.0.0-M1: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 62.5 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200703.083601-50.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200703.083601-50.jar (33 KB at 1113.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200703.083601-50.pom
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200703.083601-50.pom (4 KB at 182.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200703.083601-50-tests.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200703.083601-50-tests.jar (3 KB at 138.3 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200703.083601-50-sources.jar
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200703.083601-50-sources.jar (33 KB at 1606.1 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200703.083601-50-quickstart.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200703.083601-50-quickstart.tar.gz (125106 KB at 37400.7 KB/sec)
[INFO] Uploading: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200703.083601-50-tools.tar.gz
[INFO] Uploaded: https://sbforge.org/nexus/content/repositories/snapshots/org/bitrepository/reference/bitrepository-integration/1.10-SNAPSHOT/bitrepository-integration-1.10-20200703.083601-50-tools.tar.gz (139820 KB at 36487.3 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 28.1 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 21.9 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 26.5 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 [ 5.391 s]
[INFO] Bitrepository Reference Settings ................... SUCCESS [ 8.271 s]
[INFO] Bitrepository Core ................................. SUCCESS [ 43.573 s]
[INFO] Bitrepository Client ............................... SUCCESS [01:14 min]
[INFO] Bitrepository Service .............................. SUCCESS [ 17.596 s]
[INFO] Bitrepository Integrity Service .................... SUCCESS [01:18 min]
[INFO] Bitrepository Alarm Service ........................ SUCCESS [ 16.144 s]
[INFO] Bitrepository Audit Trail Service .................. SUCCESS [ 29.615 s]
[INFO] Bitrepository Reference Pillar ..................... SUCCESS [01:08 min]
[INFO] Bitrepository Monitoring Service ................... SUCCESS [ 15.139 s]
[INFO] Bitrepository Webclient ............................ SUCCESS [ 5.106 s]
[INFO] Bitrepository Integration .......................... SUCCESS [ 23.953 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 06:33 min
[INFO] Finished at: 2020-07-03T10:36:13+02:00
[INFO] Final Memory: 74M/256M
[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