User Tools

Site Tools


Why did continuous delivery paused after too many failed attempts?

The backend monitoring service performs some validations on the settings of the continuous delivery, before starting the actual check of the remote file. If the settings of the continuous delivery are invalid, it stores the failed attempt and exits the process, until the next iteration begins. The validations it performs are the following:

  1. The URL of the remote file is given
  2. The default publisher exists
  3. The default publisher owns a personal access token
  4. The default publisher has permissions to manage the virtual appliance

If many failed attempts to start the process occur successively, the monitoring service pauses the continuous delivery for that virtual appliance and displays the latest error in the AppDB portal.

In order to resume the continuous delivery, the user must resolve these issues first.

main/faq/cd_why_cd_paused_due_to_failed_attempts.txt · Last modified: 2018/05/11 13:11 by