Skip to content
Jenkins
log in
Dashboard
develop
#766
Back to Project
Status
Changes
Console Output
View as plain text
View Build Information
Polling Log
Timings
Git Build Data
Test Result
Previous Build
Next Build
Started 12 mo ago
Took
2 hr 54 min
on basic-jpm81
Build #766 (Jul 1, 2021, 8:57:25 AM)
Changes
Upgrade reflections library (
details
/
githubweb
)
bump javassist to 3.26.0-GA (
details
/
githubweb
)
Use Checker Framework for type checking annotations (
details
/
githubweb
)
Remove dependencies from ActiveMQ tar.gz (
details
/
githubweb
)
Started by an SCM change
This run spent:
24 sec waiting;
2 hr 54 min build duration;
2 hr 55 min total from scheduled to completion.
Revision
: 2ab7589a7b8788ed287b947934d5fb9694ece303
Repository
:
https://github.com/eclipse/kapua.git
origin/develop
Test Result
(48 failures / +12)
Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps.And I confirm the step index is 0 and status is "PROCESS_AWAITING"
Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps.Scenario: Stop job with multiple targets and Bundle Stop and Package Uninstall steps
Scenario: Executing Job When Device Connected After The Specified Start Date And Time.When I search for events from device "rpione3" in account "kapua-sys"
Scenario: Executing Job When Device Connected After The Specified Start Date And Time.Scenario: Executing Job When Device Connected After The Specified Start Date And Time
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time.When I search for events from device "rpione3" in account "kapua-sys"
Scenario: Executing Job When Device Connected Before The Specified Start Date And Time.Scenario: Executing Job When Device Connected Before The Specified Start Date And Time
Scenario: Executing Job When Device Connected Before End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"
Scenario: Executing Job When Device Connected Before End Date And Time.Scenario: Executing Job When Device Connected Before End Date And Time
Scenario: Executing Job When Device Connected After End Date And Time.When I search for events from device "rpione3" in account "kapua-sys"
Scenario: Executing Job When Device Connected After End Date And Time.Scenario: Executing Job When Device Connected After End Date And Time
Scenario: Executing Job And Then Restarting Device.When I search for events from device "rpione3" in account "kapua-sys"
Scenario: Executing Job And Then Restarting Device.Scenario: Executing Job And Then Restarting Device
Scenario: Executing Job Without Steps.When I search for events from device "rpione3" in account "kapua-sys"
Scenario: Executing Job Without Steps.Scenario: Executing Job Without Steps
Scenario: Create scheduler with end date before start date.Then I create a new trigger from the existing creator with previously defined date properties
Scenario: Create scheduler with end date before start date.Scenario: Create scheduler with end date before start date
Scenario: Create scheduler with correct end date.Then I create a new trigger from the existing creator with previously defined date properties
Scenario: Create scheduler with correct end date.Scenario: Create scheduler with correct end date
Scenario: Update trigger definition.And I try to edit trigger definition to "Cron Job"
Scenario: Update trigger definition.Scenario: Update trigger definition
Scenario: Update scheduler end date.And I try to edit end date to 13-12-2020 at 10:00
Scenario: Update scheduler end date.Scenario: Update scheduler end date
org.eclipse.kapua.integration.misc.DefaultAuthenticatorTest.connectAdminTest
org.eclipse.kapua.integration.misc.DefaultAuthenticatorTest.disconnectAdminTest
org.eclipse.kapua.integration.misc.DefaultAuthenticatorTest.disconnectUserTest
org.eclipse.kapua.integration.misc.DefaultAuthenticatorTest.connectAdminEmptyOptionsTest
Scenario: List Endpoints From "kapua-sys" Account.Then I find 3 endpoints
Scenario: List Endpoints From "kapua-sys" Account.Scenario: List Endpoints From "kapua-sys" Account
Scenario: List Endpoints From Sub-account.And I create endpoint with schema "Schema1", domain "abc.com" and port 2222
Scenario: List Endpoints From Sub-account.Scenario: List Endpoints From Sub-account
Scenario: List Endpoints Created From Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 2222
Scenario: List Endpoints Created From Sub-Account.Scenario: List Endpoints Created From Sub-Account
Scenario: List Endpoints From Sub-Account Of Another Sub-Account.And I create endpoint with schema "Schema1", domain "abc.com" and port 2222
Scenario: List Endpoints From Sub-Account Of Another Sub-Account.Scenario: List Endpoints From Sub-Account Of Another Sub-Account
Scenario: Start datastore for all scenarios.Given Start Datastore
Scenario: Start datastore for all scenarios.Scenario: Start datastore for all scenarios
Scenario: Add datastore permissions to the role.And I search for data message with id "fake-id"
Scenario: Add datastore permissions to the role.Scenario: Add datastore permissions to the role
Scenario: Start Jetty server for all scenarios.Given Start Jetty Server on host "127.0.0.1" at port "8081"
Scenario: Start Jetty server for all scenarios.Scenario: Start Jetty server for all scenarios
Scenario: Simple Jetty with rest-api war.When REST POST call at "/v1/authentication/user" with JSON "{"password": "kapua-password", "username": "kapua-sys"}"
Scenario: Simple Jetty with rest-api war.Scenario: Simple Jetty with rest-api war
Scenario: Bug when user can retrieve user in another account if it has other account's user id.Then REST POST call at "/v1/authentication/user" with JSON "{"password": "ToManySecrets123#", "username": "kapua-a"}"
Scenario: Bug when user can retrieve user in another account if it has other account's user id.Scenario: Bug when user can retrieve user in another account if it has other account's user id
Scenario: Execute possible docker steps to show its usage.Given List images by name "kapua/kapua-broker:1.5.0-SNAPSHOT"
Scenario: Execute possible docker steps to show its usage.Scenario: Execute possible docker steps to show its usage
Scenario: Creating unique Access Group with special symbols in description.Then I find the group with name "groupName53"
Scenario: Creating unique Access Group with special symbols in description.Scenario: Creating unique Access Group with special symbols in description
Show all failed tests >>>