CircleCI Common Build Errors
CircleCI Common Build Errors
If you come across or experience some build errors while working on CircleCI Orb integration, please refer to the common CircleCI build errors given below for troubleshooting.
1) No config.yml file is found in the project.
Solution: Make sure your ProjectName is correctly referenced in the CircleCI config.yml file and you are correctly using the variables/parameters in the build.xml file for the {testproject.home}.
2) No Provar libraries are found.
Solution: Check your {provar.home} value in the build file and make sure it is not referencing any environment variables in CircleCI that are using relative paths. The path must be an absolute path in this case. Also, make sure that the config.yml file is correctly passing the {provar.home} parameter to the ANT build as in the command: ant -Dprovar.home=”/home/circleci/project/Provar_Home”.
3) The Test Plan does not exist.
Solution: Your config.yml is referencing a test plan that does not exist in your project. Make sure whatever you set the parameter test_plan to, it refers to an actual test plan inside the plans/ folder in your project.
4) The Test results are not showing in CircleCI.
Solution: Your store_test_results and store_artifacts test steps are not referencing the correct directory as it exists in CircleCI and your repository home. The project_name parameter should match the initial folder name here. For example, if project_name is SalesforceProject, then your steps should look as shown below.
You cannot reference parameters and/or environment variables in these paths since CircleCI does not expand parameters in these paths.
5) An invalid secrets password is provided.
Solution: The Provar project was encrypted and checked into the Version Control System (VCS), but CircleCI does not have the proper secrets password to access the project. Ensure you have an environment variable created in CircleCI that is named properly. The build file should refer to your secrets password as shown below.
The “ProvarSecretsPassword” value must match the name of the environment variable that you created in CircleCI. Additionally, your build file should refer to the secrets password as shown below.
- General Information
- About Provar
- Browser and driver recommendations
- Granting org permissions to Provar
- Installing Provar Automation
- Provar Success Portal
- Recent support article improvements
- Reintroduction of CLI license Check
- System requirements
- Updating Provar Automation
- Using hash functions to verify the security of Provar files
- Licensing Provar
- Provar trial guide and extensions
- Using Provar
- API testing
- Behavior-driven development
- Creating and importing projects
- Creating test cases
- Custom table mapping
- Functions
- Debugging tests
- Defining a namespace prefix on a connection
- Defining proxy settings
- Environment management
- Exporting test cases into a PDF
- Exporting test projects
- Override auto-retry for Test Step
- Managing test steps
- Namespace org testing
- NitroX
- Provar desktop
- Provar Test Builder
- Refresh and Recompile
- Reload Org Cache
- Reporting
- Running tests
- Searching Provar with find usages
- Secrets management and encryption
- Setup and teardown test cases
- Tags and Service Level Agreements (SLAs)
- Test cycles
- Test plans
- Testing browser options
- Tooltip testing
- Using the Test Palette
- Using custom APIs
- Callable tests
- Data-driven testing
- Page objects
- Block locator strategies
- Introduction to XPaths
- Creating an XPath
- JavaScript locator support
- Label locator strategies
- Maintaining page objects
- Mapping non-Salesforce fields
- Page object operations
- ProvarX™
- Refresh and reselect field locators in Test Builder
- Using Java method annotations for custom objects
- Applications testing
- DevOps
- Introduction to test scheduling
- Apache Ant
- Configuration for Sending Emails via the Provar Command Line Interface
- Continuous integration
- AutoRABIT Salesforce DevOps in Provar Test
- Azure DevOps
- Running a Provar CI Task in Azure DevOps Pipelines
- Configuring the Provar secrets password in Microsoft Azure Pipelines
- Parallel Execution in Microsoft Azure Pipelines Using Multiple build.xml Files
- Parallel Execution in Microsoft Azure Pipelines using Targets
- Parallel execution in Microsoft Azure Pipelines using Test Plans
- Bitbucket Pipelines
- CircleCI
- Copado
- Docker
- Flosum
- Gearset DevOps CI/CD
- GitHub Actions
- Integrating GitHub Actions CI to Run Provar CI Task
- Remote Trigger in GitHub Actions
- Parameterization using Environment Variables in GitHub Actions
- Parallel Execution in GitHub Actions using Multiple build.xml Files
- Parallel Execution in GitHub Actions using Targets
- Parallel Execution in GitHub Actions using Test Plan
- Parallel Execution in GitHub Actions using Job Matrix
- GitLab Continuous Integration
- Travis CI
- Jenkins
- Execution Environment Security Configuration
- Provar Jenkins Plugin
- Parallel Execution
- Running Provar on Linux
- Reporting
- Salesforce DX
- Git
- Team foundation server
- Version control
- Salesforce testing
- Adding a Salesforce connection
- Assert Page Error Messages on Add/Edit Product
- Dynamic Forms
- Internationalization support
- List and table testing
- Salesforce Release Updates
- Salesforce Lightning Testing
- Salesforce Lightning Web Component (LWC) locator support
- Salesforce console testing
- Visualforce Testing
- Connection Best Practices
- Performance Best Practices
- Testing Best Practices
- Troubleshooting
- Browsers
- Configurations and permissions
- Connections
- DevOps
- Error messages
- Administrator has blocked access to client
- JavascriptException: Javascript error
- macOS Big Sur Upgrade
- Resolving failed to create ChromeDriver error
- Resolving Jenkins license missing error
- Resolving metadata timeout errors
- Test execution fails – Firefox not installed
- Update to Opportunity field validation behaviour
- Licensing, installation and firewalls
- Memory
- Test Builder and test cases
- Provar AArch64 Mac Installer
- Release notes