Thanks to this answer
I fixed this by adding the following to my lftp command
set ftp:use-allo false; set ftp:passive-mode true; set ftp:prefer-epsv false;
which made my finished command the following
lftp -e "set ftp:use-allo false; set ftp:passive-mode true; set ftp:prefer-epsv false; set ssl:verify-certificate no; open mediajackagency.com; user $...
Periodicity will only come into effect if the overall integration and deployment processes take a long time to complete, which is more likely the actual problem. Said differently, in an environment where applications are built using lightweight architectures that are quickly scanned, built, deployed and tested, periodicity would cease to be relevant.
I highly recommend using npm ci instead of npm install. The slow part of installing npm modules is figuring out everything that needs to be installed. If you commit your package-lock.json and use npm ci, it skips that part entirely and just looks at your lockfile to download what's needed. It's significantly faster.
So, I actually ended up with the following strategy.
I separated the charts from the source code. Basically, I have a repository that tracks all the helm charts only
I wanted to have a repository representing my cluster(s) so it's easy to rebuild a cluster from it
I also wanted to keep track of the current version deployed. Basically, this repository ...
Combining the answer of https://devops.stackexchange.com/a/3854/10932 and the comment of Overbryd along with a slight modification worked for me. Here, instead of using using git remote set-url command, I used git remote add.
The code will look like this:
- mvn clean ...