Draft Applications Cannot Be Deployed
Symptoms
During application deployment, a message is displayed, indicating that CodeArts Deploy cannot deploy draft applications.
Cause Analysis
An application in draft state cannot be called by the pipeline.
Solution
- On the CodeArts Deploy homepage, click
in the same row as the target application and click Edit.
- Click Save. The application will change from the draft state to the pending state and can be called by the pipeline.
Common FAQs FAQs
- Failure in Querying Deployment Status
- Application Does Not Exist
- Can I Use a Host to Deploy Multiple Projects?
- Do I Need to Install a Running Environment (Tomcat, Python, etc.) on the Target Host Before Deploying an Application?
- CodeArts Deploy Fails to Download Files from CodeArts Artifact Due to a Spelling Error
- Application Deployment Fails, with the Message "AnsibleUndefinedVariable: 'xxxx' is undefined" Displayed
- Application Deployment Succeeds But the Application Verification URL Cannot Be Accessed
- What Can I Do If Application Deployment Fails Due to a DNS Resolution Error?
- Draft Applications Cannot Be Deployed
- JDK Has Been Installed and Environment Variables Have Been Configured, But Application Deployment Fails with the Error Message "please configure JDK environment variables" Displayed
- Insufficient Permissions
- Invalid Path
- No Host Exists in the Environment.
- Error Occurs During Application Deployment with the sudo Privileges
- File or File Path Does Not Exist
- Insufficient Permissions
- File Path Does Not Exist
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
more