| << Back to previous view |
|
[QB-669] Proof build doesn't support checkout of main build script file
|
|
| Status: | Resolved |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 3.0.10 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | ChangSeop LEE | Assigned To: | Robin Shen |
| Resolution: | Won't Fix | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Environment: | ubuntu 9.10 server 64bit, Perforce SCM tool | ||
| Description |
|
We use a script file to build binaries and sometimes the script needs to be changed.
If we trigger a build to test the script after checkout and change, the build couldn't take the changed file from my local PC and it returns message "build script file is not exist". |
| Comments |
| Comment by Robin Shen [ 11/Oct/10 04:59 AM ] |
| Please run build in verbose logging mode, and check step log of the checkout step to see if modification of script is detected. |
| Comment by ChangSeop LEE [ 11/Oct/10 05:19 AM ] |
|
14:05:26,896 [collect_local_change@USERAGENT:8821] INFO - Checking opened files...
14:05:26,897 [collect_local_change@USERAGENT:8821] DEBUG - Executing command: p4 -p P4_PORT -u P4_ID -P ****** -c P4_WORKSPACE opened 14:05:26,897 [collect_local_change@USERAGENT:8821] DEBUG - Command working directory: D:\useragent\bin 14:05:26,990 [collect_local_change@USERAGENT:8821] DEBUG - //SOURCE_TREE/build_MODEL_PBS.sh#3 - edit default change (text) 14:05:26,993 [collect_local_change@USERAGENT:8821] DEBUG - Executing command: p4 -p P4_PORT -u P4_ID -P ****** -c P4_WORKSPACE where //SOURCE_TREE/build_MODEL_PBS.sh Above is log of check out step and below is log of build step some secure information are renamed 14:08:35,006 [master>build>build_Code@BUILDAGENT:8811] INFO - /bin/sh: ./build_MODEL_PBS.sh: not found |
| Comment by Robin Shen [ 11/Oct/10 06:18 AM ] |
| Looks like this file is picked by QuickBuild. Are you able to find this modified file in expected path by switching to workspace tab of the configuration and selecting the node running the checkout step? |
| Comment by ChangSeop LEE [ 11/Oct/10 08:52 AM ] |
|
I could see the modified file on the expected place of the running node.
For your information, our configuration steps are structured like below. I could see the file after all step is finished sync - Sequential - MAIN_SYNC - Checkout - COPY_SOURCE - Command build - Sequential - build_Code - Command |
| Comment by Robin Shen [ 11/Oct/10 09:07 AM ] |
|
I guess the "copy_source" step is used to copy synced source from the node running "main_sync" step to the node running "build_code" step? If so, how about examine workspace of the node running "build_code" step to see expected modified script exists?
If it does exist, please check definition of step "build_code" to make sure that the working directory is defined appropriately to point to the directory containing the script as you are executing "./build_MODEL_PBS.sh". |
| Comment by ChangSeop LEE [ 11/Oct/10 09:31 AM ] |
|
All build steps are running on a same node. And I could see "./build_MODEL_PBS.sh" file both of repository folder and copied folder
And if I change some other source code, it builds correctly. Only first srcipt file modification fails build Please send me a mail then I'll send you a image file to see the source tree |
| Comment by Robin Shen [ 11/Oct/10 09:37 AM ] |
| Please send to [robin AT pmease DOT com]. In the script, can you please add a code snippet to check if "/path/to/build_MODEL_PBS.sh" exists before executing it? Please also send screenshot of step definition of "build_code". |
| Comment by ChangSeop LEE [ 14/Oct/10 06:32 AM ] |
|
Line end difference was the problem.
I checked out ".sh" file from Windows system and build runs in Linux system. Windows system stores all line end with "\r\n" and Linux shell could not execute the file |