Re: [papyrus-rt-dev] need help to test a gerrit in the deployed platform

[Christian Damus <give.a.damus@xxxxxxxxx>]

Hi, Asma,

When it’s just a matter of the build.properties, it’s really quite straight-forward.  I would suggest just to merge it and test from the build.

The Gerrit builds don’t publish build outputs, because they are not merged and so shouldn’t be installed by ordinary consumers.  And the Hudson job doesn’t archive any outputs because that would be replaced by the very next build for the next patch set anyways.

HTH,

Christian

On 23 September, 2016 at 07:47:59, SMAOUI Asma (asma.smaoui@xxxxxx) wrote:

Hello,

 

I want to test if a patch set (not yet merged to master) is working well in the deployed platform.

When we test the gerrit in the development environment, the bug is fixed however when testing the same bug in the deployed platform (using the tester setup file while installing)

This is due to some build properties not well configured (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=476237#c54)

 

I changed the build properties (include de profile directory for this specific bug) but I am unable to test my change in the deployed platform.

 

how can I test this gerrit ? should we merge it to master to be able to test it ? since the test work in the development platform and did not work in the deployed platform.

 

I can deploy the plugin manually (produce .jar) and delete the .jar in the \.p2\pool\plugins directory and add the manually produced jar in the same \.p2\pool\plugins but I think that this is not a very clean way to test the gerrit

 

 

Any idea ?

 

Asma

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev