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

For those with VPN access, we'd also like to know if anyone uses the build-info.html pages for JBDS (we used to have something similar for JBT too): http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... If no one says "yes, that's useful" we'll likely remove it entirely for JBDS 9. Thanks, On 12/04/2014 12:25 PM, Nick Boldt wrote: > 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 >>

On 12/04/2014 07:23 PM, Denis Golovin wrote: > +1 to keep it. >> http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_8.... What's useful in this page than the regular listing of contents would not show? -- 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

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 _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

On 05 Dec 2014, at 18:10, Mickael Istria <mistria(a)redhat.com&gt; wrote: > On 12/05/2014 04:10 PM, Max Rydahl Andersen wrote: > Great we are looking at rationalizing what metadata we generate but I > think > it is the wrong question being asked. It is not wether we use the files, > it is wether we need them. We'll obviously keep the ones we need. Nick and I seemed to identify that only GIT_REVISION.txt and build.properties are currently needed for aggregation and are actually used occasionally.

> The build logs are also mostly for investigative purposes and if these > were actually available within a build that would useful (removes need > to wait for jenkins to load) Hypothetical "would" isn't enough here. For investigation, I find it pretty acceptable and consistent with the possible failures to either look at Jenkins log directly or re-run the build locally.

> What is missing is actually being able to find and read this info. Can you please elaborate on an *actual* use-case which drives you to this assumption?

> i.e. > http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-... > doesn't actually list the zip name the md5sum relate to...also it looks > like the numbers are always the same which smells like a bug. I agree on the smell of a bug there. > Also the git logs only says the sha1, but not which repository it comes > from. I plan to fix this in the publish mojo I'm working on. > Thus I think most of this info is actually very relevant info to have > but looks like it could be cleaned up, checked for errors and document > it. It may be relevant, but is it worth the maintenance effort?

-- Mickael Istria Eclipse developer at JBoss, by Red Hat My blog - My Tweets _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

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