Skip to content

Deployment of SuiteCRM


This section aims to set up a basic pipeline in Jenkins to provide a solution to the 1st, 2nd, 5th and 6th points of the problem statement under Task 1.

Jenkins pipeline project created

I clicked on New Item from the main dashboard which leads me to a different page. I gave suitecrm-pipeline as the project's name and chose Pipeline as the project type amongst all the options present.

Next came the project configurations page. Here:

  • Under General section:

    • I gave a brief description of the application being deployed and the purpose of this pipeline.
    • I also checked the GitHub Project option and provided the GitHub URL for the project's repository. This option allowed Jenkins to know where to fetch the project from.
  • Under Build Triggers section:

    • I checked the GitHub hook trigger for GITScm Polling option to allow automated builds based on webhook triggers on GitHub for selected events.
  • Under Pipeline section:

    • For Definition, I chose Pipeline Script option and wrote the pipeline code in the script section.

Then, I clicked on save to save the configurations made.


I have explained about Jenkinsfile in Setting Up Pipeline section.

The following are the contents of the Jenkinsfile which executes the pipeline:

pipeline {
    agent any

    stages {
        stage('git') {
            steps {
                git url: ''

        stage ('Build') {
            steps {
                sh 'composer install'

        stage ('Deploying App to production server'){
            steps {
                sh 'echo "Deploying App to production Server"'
                sh 'ssh -o StrictHostKeyChecking=no production@ "rm -rf suitecrm && mkdir suitecrm"'
                sh 'scp -r * production@'
                sh 'ssh -o StrictHostKeyChecking=no production@ "cd suitecrm && sudo cp -r * /home/production/html/suitecrm"'
                sh 'ssh -o StrictHostKeyChecking=no production@ "sudo cp -r /home/production/config.php /home/production/html/suitecrm"'     
                sh 'ssh -o StrictHostKeyChecking=no production@ "cd /home/production/html/suitecrm && sudo chmod -R 755 * && sudo chown -R www-data:www-data *"'

  • StrictHostKeyChecking=no In host key checking, SSH automatically maintains and checks a database containing identification for all hosts it has ever been used with. If this property is set to yes, SSH will never automatically add host keys to the $HOME/.ssh/known_hosts file, and refuses to connect to hosts whose host key has changed. This property forces the user to manually add all new hosts. If this property is set to no, ssh will automatically add new host keys to the user known hosts files.

The stages of pipeline

  • git : In this stage git repository of SuiteCRM is cloned.

  • Build: In the build stage, application is built and dependencies are installed using composer in the build stage on the Jenkins VM. This loads all the dependencies that the app (SuiteCRM) requires.

  • Deploying App to production server: In this stage, the files are deployed from Jenkins to production VM and also removes the files of SuiteCRM from production server as it might cause conflict in between the files.

Build Stage - Permission denied

In the build stage, I was getting an error for permission denied for the folder was not getting deleted and permission denied for regular files not being created. So to solve this I followed this documentation

  • I changed root directory to home directory as the DocumentRoot was set to /var/www/html. It was configured in the following file: /etc/apache2/sites-enabled/000-default.conf.
  • I ran this command in terminal to make the changes:
sudo nano /etc/apache2/sites-enabled/000-default.conf
  • I changed it to /home/production/html/suitecrm from /var/www/html
  • Then created a file suitecrm under /home/production/html
  • Made changes in the last path in Jenkinsfile to /home/production/html/suitecrm
  • Click On Save and then build the pipeline, it is successfully built this time.

SuiteCRM Web Page

When I opened the webpage there it showed to set the session.save_path. So I changed it from this session.save_path = "var/www/html/suitecrm/" to session.save_path = "tmp/" by going in the file:

sudo nano /etc/php/7.2/apache2/php.ini

This was displayed when I opened the webpage again:

Component Status
Writeable Custom Directory The Custom Directory exists but is not writeable. You may have to change permissions on it (chmod 766) or right-click on it and uncheck the read-only option, depending on your Operating System. Please take the needed steps to make the file writeable.
Writable Cache Sub-Directories The files or directories listed below are not writeable or are missing and cannot be created. Depending on your Operating System, correcting this may require you to change permissions on the files or parent directory (chmod 755), or to right-click on the parent directory and uncheck the ‘read only’ option and apply it to all subfolders.
Please fix the following files or directories before proceeding:

I ran these commands to set the following recommended permissions on SuiteCRM instance:

sudo chown -R www-data:www-data .

sudo chmod -R 755 .

sudo chmod -R 775 cache custom modules themes data upload config_override.php

After this, the web page opened for making the configurations of database and Site.


  • I was getting an error of database not connected because every time I build the pipeline, it deletes the older files and creates a new one. Hence, config.php file is missing that has the database credentials. So copy the config.php file when SuiteCRM installed manually to another place and also in SuiteCRM instance. and in the pipeline pass the step to copy the config.php file. After it is successfully done the application will be directly deployed by the pipeline.

  • To open the config page multiple times on the browser, I made the changes in config.php file installer_locked = True to false.