<< Back to previous view |
![]() |
[QB-198] Multiple patterns not working in Fix Permissions and Publish Artifacts Steps
|
|
Status: | Resolved |
Project: | QuickBuild |
Component/s: | None |
Affects Version/s: | None |
Fix Version/s: | None |
Type: | Bug | Priority: | Critical |
Reporter: | Johan Grape | Assigned To: | Robin Shen |
Resolution: | Won't Fix | Votes: | 0 |
Remaining Estimate: | Unknown | Time Spent: | Unknown |
Original Estimate: | Unknown | ||
Environment: | Win2K, AIX 5.2, WinXP64, HPUX 11 HPUX11i, Solaris 8, Java 1.5, Java 1.4.2 |
Description |
In both the Fix Permissions step and Publish artifacts step, multiple File name patterns do not work. It used to be that you could specify eg,: *.sh *.pl, but now you can only specify a single pattern.
|
Comments |
Comment by Johan Grape [ 30/Jan/07 09:21 AM ] |
Here is the step definition in question for QB 1.2.1: Step type Publish artifacts Step necessary condition !this.parent.anyChildStepFailed Description ------ Source directory ${workingDir}\checkouts\EnCapta\applications File name patterns *.dll *.lib Is publish recursively? yes Destination directory applications Is create symbol links? no |
Comment by Johan Grape [ 30/Jan/07 09:23 AM ] |
Here is the step in question for QB 1.0.14 Step type Change file permissions Step necessary condition !this.parent.anyChildStepFailed Source directory ------ File name patterns *.pl *.sh Change permissions recursively yes Permission string a+rwx |
Comment by Johan Grape [ 30/Jan/07 09:42 AM ] |
On AIX, this shows up in the build log file: 2007-01-30 09:21:21,464 [Thread-526] WARN - Warning: UNIXProcess.forkAndExec native error: The parameter or environment lists are too long. |
Comment by Johan Grape [ 30/Jan/07 10:17 AM ] |
Ok - looks like the problem can be split into two seperate problems: Windows (1.2.1): publish does not support multiple patterns Unix (1.0.14): fix permissions step fails for various reasons. |
Comment by Robin Shen [ 30/Jan/07 05:20 PM ] |
As the readme.txt of version 1.2.x describes, multiple patterns should now be separated by comma instead of spaces. This also holds true for "fix end of line character of text files" step for 1.0.14 (but other patterns are still separated by spaces). Regards. Robin |