Build #756 (Jun 1, 2021, 3:57:31 AM)

	Changes Job Step Properties limits and basic validation (details / githubweb) Fixed tests (details / githubweb) Fixed test (details / githubweb) Fixed test (details / githubweb) Increased wait time for some IT test on jobs (details / githubweb) Added handling of job target not found in writeItems (details / githubweb)
	Started by an SCM change
	Revision: 7ba5cfb30de8744b4dbbf44ff7b095686c82ad81 Repository: https://github.com/eclipse/kapua.git origin/develop
	Test Result (51 failures / +6) Scenario: Restarting a job with valid Package Uninstall step two times.And I confirm the executed job is finished Scenario: Restarting a job with valid Package Uninstall step two times.Scenario: Restarting a job with valid Package Uninstall step two times Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.And I confirm the executed job is finished Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times.Scenario: Restarting job with valid Package Uninstall and Asset Write steps two times Scenario: Restarting a job with valid Package Install step and multiple devices two times.And I confirm the executed job is finished Scenario: Restarting a job with valid Package Install step and multiple devices two times.Scenario: Restarting a job with valid Package Install step and multiple devices two times Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times.And I confirm the executed job is finished Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times.Scenario: Restarting job with valid Package Uninstall and Asset Write steps and multiple devices two times Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices.And Device assets are requested Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices.Scenario: Starting a job with valid Package Uninstall and Asset Write steps and multiple devices 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: Init Security Context for all scenarios.Scenario: Init Security Context for all scenarios Scenario: Start event broker for all scenarios.Scenario: Start event broker for all scenarios Scenario: Deleting user in account that is lower in hierarchy.Scenario: Deleting user in account that is lower in hierarchy Scenario: Deleting user in account that is higher in hierarchy.Scenario: Deleting user in account that is higher in hierarchy Scenario: Create same user in different accounts.Scenario: Create same user in different accounts Scenario: Stop event broker for all scenarios.Scenario: Stop event broker for all scenarios Scenario: Reset Security Context for all scenarios.Scenario: Reset Security Context for all scenarios 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 >>>