Legacy Knowledge Base
Published Jul. 2, 2025

Compile with CI when code requires of external library in Liferay PaaS

Written By

Giulianna Munoa

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

  • When trying to compile code using CI service the process fails since it needs validation from an external library authentication
  • You need to connect to an external library in Liferay PaaS

Environment

  • Liferay PaaS

Resolution

In this case you will need the create environment variables ARTIFACTORY_READER_USER and  ARTIFACTORY_READER_API_KEY in Liferay Experience Cloud to store the credentials used to authenticate to your external library.

Then configure Jenkis service to call this environment variables. To do so you'll need to create an script to call the new variables. Here´s a script sample of jenkins-before-all file:

sh 'curl -u ${ARTIFACTORY_READER_USER}:${ARTIFACTORY_READER_API_KEY} https://external-repo.io/companyx/api/npm/auth'

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base