| Summary: | Support composite branchTagPaths like "/drops/I20110624-0608" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Eike Stepper <stepper> | ||||
| Component: | Buckminster | Assignee: | buckminster.core-inbox <buckminster.core-inbox> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P2 | CC: | adolfosbh, ed, thomas | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Eike Stepper
In either case Buckminster should syntactically validate the specified branchTagPath values and for illegal values produce proper messages and ideally fail the build. Currently it seems as if problems with these values are not detected and lead to subsequent strange behaviour. I can not remember the details because I tried so many things before I (better: Thomas) found the cause of my problems. *** Bug 350130 has been marked as a duplicate of this bug. *** Fixed on master: http://git.eclipse.org/c/buckminster/buckminster.git/commit/?id=f4244bcba9c2aeb0d397563e573797cb24455726 Thommas, Thanks for the fix. Does this Selection Criteria wors for git ? I've tried to configure buckminster to use a Git's branch with no luck. An example of the advisorNode is the following: <cq:advisorNode namePattern="^org\.eclipse\.ocl.*$" branchTagPath="remotes/origin/master"/> The different "Selection Criteria"s I've tried are the following: master origin/master remotes/origin/master main Only main works... where "doesn't work" means that the build feature (the first one to fetch) can't be found. A screenshot with the branches list for the git repository cloned by buckminster coming right now. Created attachment 199034 [details]
Git Repository Branches
|