Community
Participate
Working Groups
Hello Thommas, We have recently migrated our project's source code to GIT and I'm struggling with an unexpected error [1]. I've also run a DEBUG-ON build [2] if it were helpful to you Resuming, our features are not found by the Git provider, however, they already do exist in the expected location. Specifically, the following error should not occur: ERROR [0002] : Rejecting provider git({0},features/{1}-feature[/opt/users/hudsonbuild/.hudson/jobs/buckminster-mdt-ocl-3.1-maintenance/workspace/org.eclipse.ocl.git,features/org.eclipse.ocl.master-feature]): No component match was found You may check in the workspace, that the og.eclipse.ocl.master-feature do exist in the expected location [3] It doesn't look a trivial failure since, for instance, the first build-feature is actually found/resolved (in a different location, though): org.eclipse.ocl.build:eclipse.feature: Trying provider git({0},releng/{1}-feature[/opt/users/hudsonbuild/.hudson/jobs/buckminster-mdt-ocl-3.1-maintenance/workspace/org.eclipse.ocl.git,releng/org.eclipse.ocl.build-feature]) org.eclipse.ocl.build:eclipse.feature: trunk/head will be searched org.eclipse.ocl.build:eclipse.feature: Found match 3.1.0.qualifier Morover, I was having the same error this morning in my local eclipse: However, at some point the master, tests and subsequent features started to be resolved: Right-Clicking on my ocl.cquery -> Buckminster -> Import...: - Firstly, I was having the same error as hudson [1] - Later (I don't know what I did to make it work, and I don't know how to make it fail again, even restarting Eclipse >.<) I got the features resolved (See attachment). I know I don't repruducible steps, but I hope the provided information is good enough to make you have an idea about what is happening. Note: I'm using Buckminster 3.7 in both local and hudson. [1] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-3.1-maintenance/598/console [2] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-3.1-maintenance/599/consoleFull [3] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-3.1-maintenance/ws/org.eclipse.ocl.git/features/ Best Regards, Adolfo.
Created attachment 198460 [details] ocl.cquery suddenly works in local
What version of Buckminster are you using?
Thomas, Buckminster 3.7 v1.4.0.r11798 Eclipse Modeling Indigo + Buckminster from http://download.eclipse.org/tools/buckminster/updates-3.7 BTW, You may want to update your downloads web page (http://www.eclipse.org/buckminster/downloads.html) ;) Regards, Adolfo.
Thommas, I'm afraid that I need to increase the severity up because we can't do our integration builds... Have you had time to have a look to it ?. Regards, Adolfo.
Adolfo, I'm on vacation this week. Is there any way for you to work around the issue?
Thommas, Not really (building from the non-updated CVS is not an option)... but I quite understand that vacation can't be disturbed with this issues (unless somebody's machine were on fire ;P)... I guess that we may live without builds until next week. I'm adding my project leader, to make him know about this. Have a nice week, Adolfo.
Thommas, I've found a new possible theory which could explain of this.... and a couple of questions which could be interesting to know The build above is our maintenance stream one (I've not configured the main development stream, yet). So we are using an specific branch to do the build: "maintenance/R3_1" . The features which are not matched, should be located in the "features" folder of the repository. The maintenance/R3_1 branch, which is checked out by hudson does really contain said "features" folder. As commented in the description, we may check that if we look at the hudson's workspace [1] However, I know that the "master" branch doesn't have said folder, it has an original "feature" folder (without the s) which has changed some weeks ago, and this change is not present in the "master" branch yet. So I launch the following questions: 1. Is it possible that the Buckminster's git provider is using the "master" branch instead of using the local git repository checked out content (maintenance/R3_1) ? This would explain why the features are not found, they would be present in a "feature" folder instead of the "features" one. 2. If so, how should we deal with buckminster if we wanted to build from a branch different to "master" ? 3. If so, why the features resolution are matched in my local Eclipse installation ? Any kind of configuration in the IDE ) [1] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-3.1-maintenance/ws/org.eclipse.ocl.git P.S: I'll do an experiment, I'll temporarilly set "feature" in the ocl.rmap file to see if the build works. That could be an argument which could confirm the hypothesis thrown in the first question. Regards, Adolfo.
(In reply to comment #7) > 1. Is it possible that the Buckminster's git provider is using the "master" > branch instead of using the local git repository checked out content > (maintenance/R3_1) ? Yes, this is not only possible, it's per design. Buckminster will do a check out of it's own. > 2. If so, how should we deal with buckminster if we wanted to build from a > branch different to "master" ? You must configure it using the branch/tag path of the cquery. > 3. If so, why the features resolution are matched in my local Eclipse > installation ? Any kind of configuration in the IDE ) > Not sure what you mean here. Buckminster will perform a checkout of the designated branch. If nothing is specified, that will be the master. I think the IDE would do the same.
Thommas, Thanks for the information. I think that I now start to understand the "weird" things. 1. In the last build I've checked that the master branch is used... 2. Concerning my last question, I couldn't understand why I was not having the errors in the local Eclipse (using the IDE), as the attatched screen shot showed. The answer was that I had installed said features, in the Eclipse Installation. As soon as I unchecked the "Perform local resolution" from Preferences -> Buckminster, I started to see the expected errors in the console. 3. I don't still know why I was having said errors in the beginning, and it suddenly started to work. Perhaps, I pressed "Refresh Meta-Data" at some moment, and then it made the things work in local. Unfortunately, I'm afraid I've found different bug which prevents me to make our maintenance build work... Following your suggestion I've created an advisor node in the ocl.cquery file to make buckminster use our maintenance branch. The point is that our maintenance branch has slashes in its name, and the editor complains about it, so that fo the following advisor node: <cq:advisorNode namePattern="^org\.eclipse\.ocl.*$" branchTagPath="origin/maintenance/R3_1"/> I get the following error: org.xml.sax.SAXParseException: java.lang.IllegalArgumentException: The '/' character is only legal at first position of a branch/tag qualifier: XXXXXXXXX/releng/org.eclipse.ocl.releng.buckminster/releng/ocl.cquery at line: 5 column: 98 Any other suggestion apart from waiting for a fix to this issue ? Best Regards, Adolfo.
I'm closing this as a duplicate of bug 350210 since that seems to be the remaining problem now. *** This bug has been marked as a duplicate of bug 350210 ***
