[
https://issues.apache.org/jira/browse/KARAF-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158718#comment-16158718
]
Steinar Bang edited comment on KARAF-5350 at 9/9/17 6:53 AM:
-------------------------------------------------------------
How costly is the "feature:install" operation on a feature consisting of
snapshot bundles from a remote repository?
(I'm thinking of just the ballpark numbers. Ie. is this so time consuming it
should only be run once a day? Or is this so low-cost it could be run once a
minute?)
Note that a dedicated "remote maven listener" can be made to be cheap in
network and CPU usage terms, simply by not doing anything until it has to,
first by using conditional HTTP GETs to watch the appropriate
maven-metadata.xml files, and after downloading them only do something when
there are new timestamps.
See [my outline of a possible karaf
component|https://groups.google.com/d/msg/ops4j/wbiFG6cLLps/PPRTW_SrAQAJ] on
the OPS4J mailing list.
was (Author: [email protected]):
How costly is the "feature:install" operation on a feature consisting of
snapshot bundles from a remote repository?
(I'm thinking of just the ballpark numbers. Ie. is this so time consuming it
should only be run once a day? Or is this so low-cost it could be run once a
minute?)
> 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)
