karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steinar Bang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-5350) Get auto update functionality like "bundle:watch *" on snapshot artifacts from remote repositories
Date Thu, 07 Sep 2017 20:25:00 GMT

    [ https://issues.apache.org/jira/browse/KARAF-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16157581#comment-16157581
] 

Steinar Bang commented on KARAF-5350:
-------------------------------------

The issue isn't about actually updating the bundles, just "bundle:update" is sufficient for
that.

The issue is about watchdogging the remote repository for new snapshots and automatically
reloading them.

See the recent threads on the ops4j and karaf-user mailing lists:
* [karaf-user|http://karaf.922171.n3.nabble.com/Can-karaf-cave-be-used-to-watch-remote-repos-for-snapshot-updates-tp4051319p4051364.html]
* [ops4j|https://groups.google.com/d/msg/ops4j/wbiFG6cLLps/Ni_-GKyvAQAJ]

> 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)

Mime
View raw message