Build #768 (Jul 2, 2021, 7:57:24 AM)

1. Bump Elasticsearch to 7.8.1 (details / githubweb)
2. Refactor ES Client to support ES 7 changes (details / githubweb)
3. Fix Embedded Elasticsearch Node (details / githubweb)
4. Remove leading . from registry index names (details / githubweb)
5. Change to new Datastore indices notations (details / githubweb)
6. JavaDoc fixes (details / githubweb)
7. ES Migration Tool refactoring and ES7 Migration (details / githubweb)
8. Update ES Migrator Documentation (details / githubweb)
9. Add kapua-qa-markers dependency to ES Migrator (details / githubweb)
10. Fix Datastore Indices Tests (details / githubweb)
11. Fix more Datastore Indices Tests (details / githubweb)
12. Yet another Datastrore test fixed (details / githubweb)
13. Use the same Elasticsearch version on ES Migrator (details / githubweb)
14. ES Migration Tool option to skip HTTPS certificate validation (details / githubweb)

Started by an SCM change

This run spent:

• 24 sec waiting;
• 2 hr 59 min build duration;
• 2 hr 59 min total from scheduled to completion.

• origin/develop

• Scenario: Starting a job with valid Command Execution step.When I search for events from device "rpione3" in account "kapua-sys"
• Scenario: Starting a job with valid Command Execution step.Scenario: Starting a job with valid Command Execution step
• Scenario: Stop job with multiple targets and Command Execution and Package Install steps.And I confirm the step index is 0 and status is "PROCESS_AWAITING"
• Scenario: Stop job with multiple targets and Command Execution and Package Install steps.Scenario: Stop job with multiple targets and Command Execution and Package Install steps
• Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps.And I confirm the step index is 0 and status is "PROCESS_AWAITING"
• Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps.Scenario: Stop job with multiple targets and Configuration Put and Package Uninstall steps
• Scenario: Stop job with multiple targets and Bundle Start and Package Install steps.And I confirm the step index is 0 and status is "PROCESS_AWAITING"
• Scenario: Stop job with multiple targets and Bundle Start and Package Install steps.Scenario: Stop job with multiple targets and Bundle Start and Package Install 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