Troubleshooting Common Issues

1 minute read
  • Workflow Syntax Errors: The solution enforces its own YAML structure and validation logic. Refer to documentation and use built-in validation tools to identify and resolve issues.

  • Missing Integrations: Verify configuration of all required services, including source control, cloud providers, and notification systems.

  • Permissions Issues: Ensure proper access to repositories, secrets, and deployment targets through assigned roles and platform-level permissions.

  • Secrets Failures: Validate that credentials exist in the product and are correctly referenced in workflow definitions.

  • Environment Differences: Align Docker images and execution environments with project requirements to maintain compatibility and consistency.

  • Connectivity Issues: Confirm network access from CloudBees execution agents to external services such as SCM providers, cloud endpoints, and APIs.

  • Resource Constraint for a Job: Every job initially receives a default resource request and limits:

    • Requests include:

      • CPU: 4 vCPUs (not pinned CPU cores really but compute time that corresponds to 4 virtual cores)

      • Memory: 4G

      • Ephemeral storage: 4G

    • If your job requires more resources than allocated, this can cause issues with:

      • CPU: when a job’s step/service attempts to consume more compute time, it is throttled, not failing the job but slowing it down.

      • Memory/Ephemeral storage: when a job/step/service attempts to exceed the limit of these types of CPU resources, it is killed.

    • Please reach out to CloudBees Support to guide you through the available options.