Skip to content

Set up CD pipeline

When commit is pushed to 'dev' branch and after it has gone through the CI pipeline, it should be deployed to Expo to generate a new APK.

The CD pipeline was supposed to be implemented together with the CI pipeline in issue #16 (closed). However, there was an issue with the CD process. The issue is also detailed in an open issue on Expo CLI repo on GitHub.

Basically, there was an error thrown: "Error: ENOSPC: System limit for number of file watchers reached". I tried increasing the amount of watches as suggested by including the following in the before_script section of the pipeline configuration file:
echo fs.inotify.max_user_instances=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
echo fs.inotify.max_queued_events=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

However, this resulted in the following:
$ echo fs.inotify.max_user_instances=524288 | tee -a /etc/sysctl.conf && sysctl -p
fs.inotify.max_user_instances=524288
sysctl: error setting key 'fs.inotify.max_user_instances': Read-only file system
$ echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sysctl -p
/bin/sh: eval: line 88: sudo: not found
$ echo fs.inotify.max_queued_events=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
/bin/sh: eval: line 90: sudo: not found

Thus, the issue remains unsolved for now, preventing the implementation of the CD pipeline.

Edited by Kasperi Ekqvist