[
https://issues.jboss.org/browse/ISPN-8479?page=com.atlassian.jira.plugin....
]
Sebastian Łaskawiec commented on ISPN-8479:
-------------------------------------------
This is how it works:
* Prod Jenkins uses unique build number for each build:
https://jdg-productization-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/JD...
* JDG 7.2 Standalone image uses branch {{dev}} which is capable of running both final
server package and development (taken from CI) server package:
https://github.com/jboss-container-images/jboss-datagrid-7-image/blob/dat...
* JDG OpenShift image uses {{dev}} tag from standalone image:
https://github.com/jboss-container-images/jboss-datagrid-7-openshift-imag...
* JDG Online image uses {{dev}} branch from JDG OpenShift image:
https://github.com/jboss-container-images/jboss-dataservices-image/blob/d...
In order to use new SNAPSHOT in the JDG Online build you need to:
* Copy a link to JDG server binary (from Jenkins) and put it in the cacher:
http://ce-cacher.usersys.redhat.com/
* Update MD5 checksum and zip name in standalone image:
https://github.com/jboss-container-images/jboss-datagrid-7-image/blob/dat...
* Get it merged
* Wait until all images are rebuilt in CE CI:
http://ce-ci.usersys.redhat.com/view/All/job/jboss-dataservices/job/datag...
(follow upstream projects links)
Automate JDG Snapshot builds so that we can use them for Online
Services
------------------------------------------------------------------------
Key: ISPN-8479
URL:
https://issues.jboss.org/browse/ISPN-8479
Project: Infinispan
Issue Type: Bug
Components: Cloud Integrations
Reporter: Sebastian Łaskawiec
Assignee: Sebastian Łaskawiec
It might be useful to have a dedicated CI pipeline to build JDG server and publish it
into candidates area. This way we could consume it in JDG Online Services whenever we want
to.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)