Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 369794

Summary: [releng] Job UML's Git repository is not being pulled.
Product: [Modeling] OCL Reporter: Adolfo Sanchez-Barbudo Herrera <adolfosbh>
Component: CoreAssignee: OCL Inbox <mdt-ocl-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: Kenn.Hussey
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Adolfo Sanchez-Barbudo Herrera CLA 2012-01-26 07:20:20 EST
It looks like that some releng funnies are provoking some build failures. Concerning the build failure[1], Ed suspicions were:

"It appears that the use of UML2's GIT is not working.

'master' has not been pulled and so CMOF2UMLResource.java is stale; the 28-Nov-2011 commit has not occurred. "

The build was simply fixed by wiping out the job's workspace. This needs investigation.

[1] https://hudson.eclipse.org/hudson/job/buckminster-mdt-ocl-tools-3.2-master/130/
Comment 1 Adolfo Sanchez-Barbudo Herrera CLA 2012-01-26 12:31:34 EST
note: UML2's git repository update (probably a fetch) is done by buckminster. We need to do a full pull, so that the local master and working directory is properly updated.
Comment 2 Adolfo Sanchez-Barbudo Herrera CLA 2012-01-31 04:57:02 EST
I've only found the following property in buckminster documentation:

"git.auto.fetch 

This property applies when the local repository exists and the
git.remote.uri property is set. If git.auto.fetch is set
to true, a fetch will be made from the remote repository to
ensure that the local clone is up to date prior to resolving."

I'm not sure this suffice. Perhaps, if the checked-out is a remote tracking master branch of the local and cloned UML repository, it could work, but I don't think so.... anyway there is not other option in the documentation so I'll include it since it make sense.

On the other hand, do you have any idea how to verify the correctness of the solution ? ... I guess we will have to verify the changes of an UML file of our job's workspace, whenever a UML change occurs after pushing the change of that property.

Cheers,
Adolfo.
Comment 3 Adolfo Sanchez-Barbudo Herrera CLA 2012-01-31 05:11:11 EST
Changes pushed to master. I'll have to verify this, when a change in UML Git repo is done after todays date.

Regards,
Adolfo.
Comment 4 Adolfo Sanchez-Barbudo Herrera CLA 2012-01-31 05:44:23 EST
Some information about what is doing buckminster Bug 324441 comment 5

Waiting for some response there.
Comment 5 Kenn Hussey CLA 2012-01-31 11:29:11 EST
I've had similar problems with git repositories containing code on which a build depends. I would recommend discarding the git repository and thereby force a new clone for each build. This could be automated, for example, by adding a shell command to the beginning of the build that does rm -r <folder>.
Comment 6 Adolfo Sanchez-Barbudo Herrera CLA 2012-04-03 08:11:49 EDT
Hi Kenn,

Thanks for the suggestion. On the other hand, after solving Bug 375640 we have discarded the need of the UML Git Repository, so this bug may be solved as wontfix.
Comment 7 Ed Willink CLA 2013-05-20 11:37:05 EDT
CLOSED after a year in the RESOLVED state.