[ https://issues.apache.org/jira/browse/KARAF-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158149#comment-16158149 ]
Guillaume Nodet edited comment on KARAF-5350 at 9/8/17 10:43 AM: ----------------------------------------------------------------- A way to automate that is to trigger a feature installation on a regular basis: {code} > feature:install scheduler > scheduler:schedule --period 60 { feature:install shell } {code} Note that the code should update all snapshot bundles from remote repositories installed through features (not only the one from the {{shell}} feature). The reason is that the FeatureService always work on a global way, so any call to it will update all the necessary bundles. was (Author: gnt): A way to automate that is to trigger a feature installation on a regular basis: {code} > feature:install scheduler > scheduler:schedule --period 60 { feature:install shell } {code} > Get auto update functionality like "bundle:watch *" on snapshot artifacts > from remote repositories > -------------------------------------------------------------------------------------------------- > > Key: KARAF-5350 > URL: https://issues.apache.org/jira/browse/KARAF-5350 > Project: Karaf > Issue Type: Improvement > Reporter: Steinar Bang > > I now have a continous deployment pipeline for [my > project|https://github.com/steinarb/ukelonn] almost automated: > # All changes I would like deployed, I merge to master and then push master > to github > # New pushes on master triggers a build on travis-ci > # A successful build on travis-ci results in a new snapshot being deployed to > a maven repository accessible via HTTP > ## The bundles that make up my application have been installed from snapshots > in the maven repository, like so (karaf consolle commands): > {noformat} > config:edit org.ops4j.pax.url.mvn > config:property-append org.ops4j.pax.url.mvn.repositories ", > https://maven.bang.priv.no/repository/@snapshots, > http://maven.vaadin.com/vaadin-addons" > config:property-set org.ops4j.pax.url.mvn.globalUpdatePolicy always > config:update > feature:repo-add mvn:no.priv.bang.ukelonn/ukelonn.karaf/LATEST/xml/features > feature:install ukelonn-db-postgresql > feature:install ukelonn > {noformat} > # The final step I have to do during a deployment, is to log in with ssh to > the karaf console and give "bundle:update" on each bundle > {noformat} > bundle:update no.priv.bang.ukelonn.api > bundle:update no.priv.bang.ukelonn.db.liquibase > bundle:update no.priv.bang.ukelonn.db.postgresql > bundle:update no.priv.bang.ukelonn > {noformat} > It is the final step I would like to have automated, so that new snapshots > deployed to the remote repository is automatically picked up by karaf. -- This message was sent by Atlassian JIRA (v6.4.14#64029)