To get you thinking about what artifacts we mean, and which you might
use, here's a couple examples:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_...
[contains the SHA used to create that CI build]
http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_...
[contains details re: slave used for the build]
--
Note that aggregate builds contain MORE metadata files. For example, we
currently create summaries of the contents of the aggregate based on
which projects fed that specific build:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-...
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-...
Does anyone use these?
Nick
On 12/04/2014 12:14 PM, Mickael Istria wrote:
Hi all,
We're strongly brainstorming about our publication process: how to make
it simpler? how to make it more independent from Jenkins? how to
organize our various site in a more straightforward way?...
As part of this investigation, we'd like to get rid of some legacy
things that don't seem to provide value any more. So, before we make big
changes, I have a simple question to ask you all:
/In the p2 repository that is the output of build/CI, such as
http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_...
, what exact files have you consulted recently?/
The files that won't be mentioned in your answers will be dropped (only
those that are there for aggregation will be kept).
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com