[
https://issues.apache.org/jira/browse/DMAP-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679744#comment-14679744
]
Werner Keil commented on DMAP-31:
---------------------------------
I can't see this even if I log into Jenkins, so I guess
https://builds.apache.org/view/All/job/devicemap-data-1.0/ and
https://builds.apache.org/view/A-D/view/DeviceMap/job/devicemap-java-client-1.0/
are not connected. Would it be possible to define a downstream trigger, so if
data changes, client is being tested against that new data?
If Java 1.0 client builds against the latest 1.0.3 data only, then IMHO it
would be great to have a "stable/milestone" and a "nightly" build against the
latest data.
Whatever happens with 2.0 data, the 1.0 stream will also be maintained at least
when new devices, browsers, etc. are demanded (just see the ~40 tickets here
;-) )
> Jenkins setup for devicemap continuous builds
> ---------------------------------------------
>
> Key: DMAP-31
> URL: https://issues.apache.org/jira/browse/DMAP-31
> Project: DeviceMap
> Issue Type: Task
> Components: Infrastructure
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
>
> We'll use this issue to record changes to our https://builds.apache.org build
> jobs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
