Automatically updating composer.lock in build process

Question

I have a Neos project, consisting of a Site providing the main composer container. composer.json requires a huge number of packages (whole neos/flow environment), including some packages we develop.

Our deployment setup consists of Jenkins, building the css/javascript for both the site and plugin packages (only within their specific gits) and finally triggering TYPO3 Surf, which actually calls composer install and then rsync's to the server.

Right now, each time we want some changes in our dev branch to be deployed to the testing environment, we have to manually cd to the main composer directory, do a

composer update vendor/package && git add composer.lock && git commit -m "update composer.lock"`.

Is there anyway to always use the newest version of our plugin package with composer? Perhaps excluding the requirement from composer.lock, or just changing it without installing the actual packages.

Answer 1

For a continuous deployment to a testing server you could just make jenkins do a composer update and with your packages set to dev/master in the composer.json.