Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » forth segment version (quilifier) is not replaced
forth segment version (quilifier) is not replaced [message #694494] Fri, 08 July 2011 13:36 Go to next message
Eclipse User
Originally posted by:

Hello Bucky Team,

I'm wondering why some of my plugins forth segment versions (qualifier)
are not properly replaced, as you may check in the following link [1]

My replacement strategy is the following (as you may check here [2]):

qualifier.replacement.*=generator:lastModified
generator.lastModified.format='v'yyyyMMdd-HHmm

And the (robust) reference repository I used is the following [3] as you
may check here [4]

The strange thing is that some of them are replaced, but some of them
aren't.

Any idea/clue about what's happening?

Best Regards,
Adolfo.

[1]
https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.2-master/374/artifact/MDT-OCL.p2.repository/plugins/
[2]
https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.2-master/ws/buildroot/build.properties/*view*/
[3]
https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-3.1-maintenance/570/artifact/MDT-OCL.p2.repository/
[4]
https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.2-master/374/parameters/?
Re: forth segment version (quilifier) is not replaced [message #694497 is a reply to message #694494] Fri, 08 July 2011 13:53 Go to previous messageGo to next message
Adolfo Sanchez-Barbudo Herrera is currently offline Adolfo Sanchez-Barbudo Herrera
Messages: 253
Registered: July 2009
Senior Member
Sorry, I used newsgroup instead of forums and it looks like my email account is not identified ...

Using the forums now Smile

Cheers,
Adolfo,
Re: forth segment version (quilifier) is not replaced [message #694544 is a reply to message #694494] Fri, 08 July 2011 15:37 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
Hi Adolfo,

I haven't seen this before. The only reason I can think of is that the projects are somehow not recognized as git
projects. Do they have different path to the git repository root somehow? I'm thinking that maybe there's something
wrong in the algorithm that finds the git root from the checked out source folder.

- thomas

On 2011-07-08 19:36, Adolfo Sánchez-Barbudo Herrera wrote:
> Hello Bucky Team,
>
> I'm wondering why some of my plugins forth segment versions (qualifier) are not properly replaced, as you may check in
> the following link [1]
>
> My replacement strategy is the following (as you may check here [2]):
>
> qualifier.replacement.*=generator:lastModified
> generator.lastModified.format='v'yyyyMMdd-HHmm
>
> And the (robust) reference repository I used is the following [3] as you may check here [4]
>
> The strange thing is that some of them are replaced, but some of them aren't.
>
> Any idea/clue about what's happening?
>
> Best Regards,
> Adolfo.
>
> [1] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.2-master/374/artifact/MDT-OCL.p2.repository/plugins/
> [2] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.2-master/ws/buildroot/build.properties/*view*/
> [3] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-3.1-maintenance/570/artifact/MDT-OCL.p2.repository/
> [4] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-core-3.2-master/374/parameters/?
Re: forth segment version (quilifier) is not replaced [message #695311 is a reply to message #694544] Mon, 11 July 2011 09:28 Go to previous messageGo to next message
Adolfo Sanchez-Barbudo Herrera is currently offline Adolfo Sanchez-Barbudo Herrera
Messages: 253
Registered: July 2009
Senior Member
Thommas,

I'm not sure how this qualifier replacement works in buckminster, so I can't help. I thought that the reference repository played some kind of role to know if which plugins have changed in somehow, instead of relying on the SCM system. Anyway what you mentioned can't be the cause because the following plugins are located in the same workspace/org.eclipse.ocl.git/plugins folder:

org.eclipse.ocl -> org.eclipse.ocl_3.1.0.v20110711-0803.jar
org.eclipse.ocl.edit -> org.eclipse.ocl.edit_3.1.0.qualifier.jar

However the qualifier replacement was only applied in the first one.

On the other hamd, what I can say you is that I finally desisted to use git reader types in my rmaps to workaround the builds failures. I'm using local reader types which use the local git repository downloaded/updated by hudson... So I'm not sure how Buckminster-Git plays a role to do such an qualifier replacement.

P.S: The artifacts from the build 374 are not currently available. I'm not sure why this happens sometimes , I think that the cause is using a different eclipse severs to which build against. The last successful build has the same problem.
Re: forth segment version (quilifier) is not replaced [message #695394 is a reply to message #695311] Mon, 11 July 2011 12:28 Go to previous messageGo to next message
Adolfo Sanchez-Barbudo Herrera is currently offline Adolfo Sanchez-Barbudo Herrera
Messages: 253
Registered: July 2009
Senior Member
Thommas,

My two hudson jobs (indigo and juno builds) are now replacing qualifiers... I'm not sure if the fact that the servers are properly working is the cause... In any case, I'm interested in knowing how this replacemente strategy works...

BTW, do you know any way to make hudson fail the build if it has encountered any problem while replacing qualifier segment ?

Regards,
Adolfo.
Re: forth segment version (quilifier) is not replaced [message #695589 is a reply to message #695394] Tue, 12 July 2011 00:40 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3229
Registered: July 2009
Senior Member
On 2011-07-11 18:28, Adolfo S wrote:
> Thommas,
>
> My two hudson jobs (indigo and juno builds) are now replacing qualifiers... I'm not sure if the fact that the servers
> are properly working is the cause... In any case, I'm interested in knowing how this replacemente strategy works...
>
The strategy finds all commits that affect the project sub-tree. The time-stamp of the last commit is used.

> BTW, do you know any way to make hudson fail the build if it has encountered any problem while replacing qualifier
> segment ?
>
I suggest you enter a bugzilla for this. It really sounds like some exception is caught and assumed OK where it
shouldn't be.

- thomas
Re: forth segment version (quilifier) is not replaced [message #696127 is a reply to message #695589] Wed, 13 July 2011 06:07 Go to previous message
Adolfo Sanchez-Barbudo Herrera is currently offline Adolfo Sanchez-Barbudo Herrera
Messages: 253
Registered: July 2009
Senior Member
Thommas,

I raised the bugzilla[1], we may carry on the discussion there.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=351928

Best Regards,
Adolfo.
Previous Topic:create.product fails with missing package from rt.jar
Next Topic:Howto use simple pool of bundle jars
Goto Forum:
  


Current Time: Thu Aug 28 21:41:03 EDT 2014

Powered by FUDForum. Page generated in 0.02166 seconds