[#QB-3213] Builds do not start automatically since we updated fom version 6.0.27 to 8.0.5

QuickBuild

Builds do not start automatically since we updated fom version 6.0.27 to 8.0.5

Created: 27/Jun/18 09:11 AM Updated: 30/Jun/18 12:28 AM

Component/s:

None

Affects Version/s:

8.0.5

Fix Version/s:

None

Original Estimate:	Unknown	Remaining Estimate:	Unknown	Time Spent:	Unknown
Environment:	Windows

Description

« Hide

We have lots of configurations which are automatically started 'If changes found in referenced repositories' . Since we updated our QuickBuild installation from version 6.0.27 to 8.0.5 some of this configurations do not start builds automatically a commit is made to a referenced repository. We can start the builds manually without any problems.

One difference to the other configurations, which are still working as expected, is that the problem configurations are using 'Include/Exclude Path Patterns' to include or exclude some commits for the change detection while the others do not.

We didn't change the values of 'Include/Exclude Path Patterns' after the QuickBuild update but I guess something has changed in QuickBuild which causes the our problem.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Robin Shen [27/Jun/18 11:36 PM]

Are there any information printed in server log (or agent log if the master step is set to run on an agent) around the scheduled time of the problem configurations?

[ Permlink | « Hide ]

Helmut Namyslo [28/Jun/18 06:41 AM]

I committed a change at 08:26:34. A few minutes later I found this server log entry:

2018-06-28 08:30:05,028 [pool-1-thread-35659] INFO com.pmease.quickbuild.DefaultBuildEngine - Processing build request (configuration:root/Components/CommonDialogs DEV, request id:72328046-d2cc-4b04-8f4e-573772353d00)
2018-06-28 08:30:05,034 [pool-1-thread-35659] INFO com.pmease.quickbuild.DefaultBuildEngine - Checking build condition on node (address: WKA-WN-KN:8811, ip: 172.23.118.226)...
2018-06-28 08:30:06,757 [pool-1-thread-35659] INFO com.pmease.quickbuild.DefaultBuildEngine - Build condition not satisfied, new build won't be generated.
2018-06-28 08:30:06,757 [pool-1-thread-35659] INFO com.pmease.quickbuild.DefaultBuildEngine - Build request has been processed.

What I am missing is, why the Build Condition is not satisfied. We did not change this build configuration before or after updating our QuickBuild installation.

[ Permlink | « Hide ]

Robin Shen [29/Jun/18 12:24 AM]

You may turn on perforce debug logging on node "WKA-WN-KN:8811" by editing "<agent install dir>/conf/log4j.properties", and add below line:
log4j.logger.com.pmease.quickbuild.plugin.scm.perforce=DEBUG

The build agent does not need to be restarted after the change. Then please reproduce the issue again. QB will print changed files detected in agent log after line with this message "Affected files ...". Please check if affected files matches your include/exclude pattern.

[ Permlink | « Hide ]

Helmut Namyslo [29/Jun/18 08:00 AM]

Thanks for this hint.

The contents of Include/Exclude Path Patterns was wrong: +/ComponentMgr/DEV/**,+https://svn.dev.ptv.de/Vision_Dev/trunk/CommonDialogs/**

After I corrected to: +/ComponentMgr/DEV/**,+/trunk/CommonDialogs/**

the builds are starting as expected.