>>>>> Steinar Bang <[email protected]>: >>>>> Jean-Baptiste Onofré <[email protected]>:
>> By the way, I'm adding "deployment tooling" in Cave right now >> (allowing to explode a kar, create meta feature assembling existing >> features, ...). > Interesting! Will study! > https://karaf.apache.org/manual/cave/latest-4/ So now I see three ways to do continous delivery: 1. Snapshot builds from travis, triggered by github changes, deploying to a package cloud account[1] (a free package cloud account will probably serve my humble needs...) 2. Installing jenkins on the same server karaf is running, and using cave to refer to the /home/jenkins/.m2/repository 3. Running jenkins on a different computer and rsync the /home/jenkins/.m2/repository to the server karaf is running and use cave to make karaf listen to /home/jenkins/.m2/repository (I tried rsyncing my manual builds from my own account on a different computer to the karaf account on the karaf server, ie. /home/karaf/.m2/repository, but that got a lot of issues wrt. file ownership and access. Doing it to the same account and on a different account from the karaf account should resolve this) References: [1] <https://packagecloud.io/pricing>
