Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Jenkins build fails with "Default Jenkinsfile not found"

Written By

István Gergely-Tárnoki

How To articles are not official guidelines or officially supporteddocumentation. They are community-contributed content and may not alwaysreflect the latest updates to Liferay DXP. We welcome your feedback toimprove How to articles!

While we make every effort to ensure this Knowledge Base is accurate, itmay not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with anyfeedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack"publication program, made available for informational purposes. Articlesin this program were published without a requirement for independentediting or verification and are provided "as is" withoutguarantee.

Before using any information from this article, independently verify itssuitability for your situation and project.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

  • We updated our CI service's version after deploying this change to our Infra environment, the Jenkins build fails and we also lose the Jenkins configuration:
Started by user customer
Running as customer
java.lang.IllegalArgumentException: Default Jenkinsfile not found. Check configuration.
	at org.jenkinsci.plugins.pipeline.multibranch.defaults.DefaultsBinder.create(DefaultsBinder.java:87)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:310)
	at hudson.model.ResourceController.execute(ResourceController.java:107)
	at hudson.model.Executor.run(Executor.java:449)
Finished: FAILURE

Environment

  • Liferay PaaS

Resolution

  1. Delete the CI service
  2. Rename the volume name, like
    "volumes": {
       "ciData2": "/var/jenkins_home"
    }
  3. Redeploy the changes
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?