[jbosstools-dev] What are you using in p2 repositories produced by build/CI ?

[Max Rydahl Andersen]

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.

i.e. git revisions we don't use actively, but we do need them since that 
is the only way we actually know which repository SHA's have been used.

I think we catch most of this in eclipse source references today - but 
that is only for bundles, not for other artifacts like the udpdate 
sites, features etc. thus this information is relevant.


Build properties are useful to actually reproduce or at least trace what 
actually was done in the build ?

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)

What is missing is actually being able to find and read this info.

Also, some of the files seem to be in a very hard to parse format even 
though it would be really great to do so.

i.e. 
http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/md5sums.txt 
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.

Also the git logs only says the sha1, but not which repository it comes 
from.

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.

for example what is zip.list.txt?

/max

> 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_master/logs/GIT_REVISION.txt
> [contains the SHA used to create that CI build]
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_master/logs/build.properties
> [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-build-core/2014-11-23_23-27-39-B304/logs/ALL_REVISIONS.txt
> http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.2.1.CR1-build-core/2014-11-23_23-27-39-B304/logs/build.properties.all.xml
>
> 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_master/
>> , 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 at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


/max
http://about.me/maxandersen