<< Back to previous view |
![]() |
[QB-3457] Please let us know how to use the "If changes found in referenced repositories" option in the Build Condition.
|
|
Status: | Closed |
Project: | QuickBuild |
Component/s: | None |
Affects Version/s: | 9.0.22 |
Fix Version/s: | None |
Type: | Task | Priority: | Major |
Reporter: | Yoongeon Lee | Assigned To: | Robin Shen |
Resolution: | Won't Fix | Votes: | 0 |
Remaining Estimate: | Unknown | Time Spent: | Unknown |
Original Estimate: | Unknown |
File Attachments: |
![]() ![]() ![]() |
Description |
We are using Repository git now. We should use this option ("Build Condition : If changes found in referenced repositories") now because It's inefficient to build even if there are no changes in the repository.
I've visited the link below to use this feature, but I can't understand how to use the option with only the description there. Is there a sample node I can refer to? Please tell us how to use the function in detail. options 1) Build Condition : If changes found in referenced repositories 2) Build Condition : If changes found in referenced repositories or last build failed links 1) Repository Path - https://wiki.pmease.com/display/qb90/Repository+Path 2) File Pattern Reference - https://wiki.pmease.com/display/qb90/File+Pattern+Reference |
Comments |
Comment by Robin Shen [ 14/Oct/19 11:20 PM ] |
QB should not fire the build if no changes found in your git repository? Do you mean that the build still gets fired in this case? |
Comment by Yoongeon Lee [ 23/Oct/19 08:15 AM ] |
Yes, build should not works if there is no change in git repository. The build starts even though I set the Build Condition as "If If changes found in referenced repositories". Please see check if there is something wrong in our repository settings.( screenshot - General Settings.png , Git Repository Settings in QBuild.png ) |
Comment by Robin Shen [ 23/Oct/19 10:42 PM ] |
The setting looks fine to me. Do you have other repositories also used in your checkout step causing the build to be fired? Also please check if there is other configurations triggering this configuration via "trigger other build" step. |