devicemap-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Werner Keil (JIRA)" <>
Subject [jira] [Commented] (DMAP-31) Jenkins setup for devicemap continuous builds
Date Mon, 10 Aug 2015 07:57:45 GMT


Werner Keil commented on DMAP-31:

I can't see this even if I log into Jenkins, so I guess
and 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:
>             Project: DeviceMap
>          Issue Type: Task
>          Components: Infrastructure
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
> We'll use this issue to record changes to our build jobs.

This message was sent by Atlassian JIRA

View raw message