Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Webhooks not being created with GitLab due to GitLab connection to Jenkins

Written By

Justin Mann

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

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

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability 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

  • Webhooks are not being created when trying to connect a GitLab Repository with Jenkins
  •  Based on the error seen in the logs, the connection between GitLab and Jenkins is not working
[DXP Cloud] LCP_CI_SCM_REPOSITORY_NAME env variable should have been set by DXP Cloud infrastructure, but was not found.

Environment

  • Liferay SaaS
  • Liferay DXP 7.4
  • GitLab Repository

Resolution

  • The Repository Owner and Repository Name environmental variables must match the project exactly
  • There can be some confusion as to what the Repository Owner should be. Rather than the name of the user who owns the project, the Repository Owner is the root Group Name of the project. This can often be the same as the user who owns the project, but is not always that way.
  • Subsequently, the Repository Name is the full Subgroup path following the Repository Owner. If the project repo that is being connected to Jenkins is nested some levels down, the full Subgroup path is required for the Repository Name.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?