| << Back to previous view |
|
[QB-3880] 12.0.12 file permission changed on linux system
|
|
| Status: | Closed |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 12.0.12 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Bin Wu | Assigned To: | Robin Shen |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Description |
|
Sorry for this report, it maybe some configure changed, but I missed
I upgrade to 12.0.12 for the token feature to do the automation authorized, so not check the other part But I find some linux build process failed after upgrade from 11.0.26 I add some step to list file permission on the poll & build step for the source code poll: Repository -> git to download source code "dump file permission" which is correct Artifacts type to publish the source for the build: mapping target repository to check the source "dump file permission" lost the execute permission run the build command I'm don't know why the file transform on the QB will cause this problem it almost like QB use some file transform(zip?) lost it |
| Comments |
| Comment by U. Artie Eoff [ 24/Aug/22 09:27 PM ] |
|
Let me try to make it clear so we understand each other...
There are two configurations, "poll" and "build". The "build" configuration depends on the artifacts from the "poll" configuration. The "poll" configuration defines a Git Repository. It has a Checkout step and a Publish Artifacts step (to publish the files from checkout). The "build" configuration defines a QuickBuild repository that retrieves the artifacts from the "poll" configuration during a Checkout step. After checkout in the "poll" configuration, the execute permissions are correct. After checkout in the "build" configuration, the execute permissions are wrong. So either: A. the execute permissions are lost when the files are published in the "poll" configuration or... B. the execute permissions are lost when the files are retrieved in the "build" configuration. You mentioned "file transform(zip)". Does this mean it only happens when "Compress During Transfer" is "yes" in the QuickBuild repository setting? |
| Comment by Robin Shen [ 24/Aug/22 11:17 PM ] |
|
The file permission will be preserved even if "compressed during transfer" option is enabled. I just set up a simple test as below on a brand new QB installation and it works:
1. Create configuration "root/component" to checkout from a git repository containing executable files, this configuration also has a publish step to publish the whole repository content as artifacts with "compress during transfer" ticked 2. Create configuration "root/product", and define a QuickBuild repository pointing to configuration "root/component" to retrieve all artifacts from "latest build (generate new if necessary)", with option "compress during transfer" enabled. The configuration has a checkout step to checkout from defined QuickBuild repository, and a command build to run an executable from retrieved artifacts 3. Run configuration "root/product" and the executable can run without any issues. This works no matter master step of both configurations runs on server or agent. You may test if this simple test works at your side. If yes, it might indicate an issue of your own build script instead of QB itself. |
| Comment by Bin Wu [ 26/Aug/22 03:28 AM ] |
|
this issue is gone
here is the problem find in the check process: QB will lost file permission about execute is exist: when pull the source code from repo, the execute permission is U(user), G(Group), A(all) have execute permission check the file on the artifacts folder (from build path), it's permission is U have execute permission, the G and A is missing the store file system is ext4 but with check about all log, in the that time, it lost all execute permission, it should be our self build script problem in the CI system |
| Comment by Robin Shen [ 26/Aug/22 07:00 AM ] |
| So I can close this issue now? |
| Comment by Bin Wu [ 26/Aug/22 07:11 AM ] |
|
please hold on this issue for 2 days
I'm not sure the root cause on it after 2 days you can close it |
| Comment by Bin Wu [ 30/Aug/22 04:51 AM ] |
|
couldn't reproduce it
you can close it, it look's like is not cause by QB upgrade |
| Comment by Robin Shen [ 30/Aug/22 04:54 AM ] |
| Thanks for the update. |