RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
Table of Contents |
---|
User can login into Automatics through any one of the two authentication modes - Self-Authentication or LDAP Authentication.
...
Details of JOB status are
Job Status | Description |
QUEUED | Job is created and waiting for free Jenkins job for execution |
SCHEDULED | Found free Jenkins job and it is scheduled for execution |
IN PROGRESS | Jenkins job execution in progress |
CANCELLED | Jenkins job cancelled |
COMPLETED | Jenkins job execution completed successfully. The job has executed the tests. |
FAILURE | Jenkins job execution was not completed. The job has failed to executed tests. |
ALREADY_LOCKED | Device provided for execution is locked by some other execution. Execution cannot proceed. |
INVENTORY_DOWN | Device inventory is down. Automatics couldn’t get devices for execution. |
BOXES_UNUSABLE | Jenkins job execution could not be completed due to device issue |
BUILD_CHANGED_BEFORE_TEST | As pre-test verification, Automatics core will check if the build in device is same as user provided. If it is not same, then execution will fail with this status |
BUILD_CHANGED_AFTER_TEST | As post-test verification, Automatics core will check if the build in device is same as user provided. If it is not same, then execution will fail with this status |
SSH_FAIL | Automatics core will check the accessibility of device before starting test execution. If device is not accessible, then execution fails with this status |
Initially, the status will be QUEUED. When the job is triggered in Jenkins it changes to SCHEDULED and when job execution is going on, then status will become IN PROGRESS. Once, it is completed you can see the status as COMPLETED.
...