The standard procedure is to allow SLAVE to deploy on public repositories and SLAVEPRIV to deploy on private repositories, but for the Lambda addon we need to build on SLAVEPRIV accessing private sources but deploy publicly.
In order to do so, the settings.xml file of SLAVEPRIV should be updated with the missing credentials to deploy on public daily-snapshots.
Until fixed, QA job will fail and release of this addon cannot happen.