Your browser was unable to load all of the resources. They may
have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.
I am using QuickBuild 3.1.18, with the embeded database.
I have successfully published a war file as an artifact, and have seen it display on the Overview of the task.
I have published the artifact to the default directory.
When I attempt to access this artifact in another task, bad things happen.
Configuration is set via the tree popup supplied by the interface, for the task with the publish command in it.
Setting the build to Latest Finished Version or Latest Successful version, I get the following error:
Waiting for finish of dependency build (configuration: root/ValidationRulesEditor/trunk/Maven_Deploy, build id: 303)
This does not generate an error, and the step succeeds, without waiting.
Setting the the build to Select by build number, and setting the build number of the last publish task, I get the following error:
com.pmease.quickbuild.QuickbuildException: Dependent build not found (configuration:root/ValidationRulesEditor/trunk/Maven_Deploy, build:303)
It would appear that QuickBuild cannot find the artifact that is clearly visible in the publishing task.
What am I missing? What else should I try?
BTW: I found no screen displays of the Checkout pages in the documentation, nor any help with determining what should be placed in these fields.
Gary Shurgin
Senior Systems Analyst
OCLC, Inc.
-
replies
9
-
views
3154
-
stars
0
-
Hi Gary,
Please specify build version instead of build number. They are different thing in QuickBuild.
Regards
Robin
> bin/config.sh
java version "1.6.0_13"
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
Java HotSpot(TM) 64-Bit Server VM (build 11.3-b02, mixed mode)
I hope this is the information that you requested.
Hi Gary,
Sorry I am not clear enough. What I mean is that to solve the issue, please check definition of the involved QuickBuild repository. It seems that a build number is specified for the dependency build. QB expects a version string instead.
Regards
Robin
Now it is I that does not understand fully.
If you are referring to the input data on the Repository Display for the build number:
In the case of asking for the latest build (finished or successful), there is no build number requested.
In the case of asking for a specific build, I type in a hard coded value that was presented in both the above message, and in the dashboard where the artifact was published.
I have been looking at the overview of the two tasks and the Dependents (in the case of the publisher) and the Dependencies (in the case of the checkout) are showing values that link to each other.
I have also changed the executing step to run on both the server and on the parent node (I have multiple agents running) with no change in the observed behavior.
GaryS
Can you please check if the configuration displayed in error message actually contains a build with version "303"? (not build id).
Regards
Robin
The message in the log specifies the build number (303), not a version number.
GaryS
The message "Waiting for finish of dependency build (configuration: root/ValidationRulesEditor/trunk/Maven_Deploy, build id: 303)" is not an error message. Please choose the option "latest successful build" in QuickBuild repository definition. Please check the actual war file path in the file system. For example, if it locates in directory "<QB global publish dir>/builds/<build id>/artifacts/somesubdir/myproduct.war", the files to retrieve setting of QuickBuild repository needs to be defined like below:
source path: artifacts/somesubdir
file patterns: *.war
dest path:
Then after checking out the QuickBuild repository, the "myproduct.war" should appear in the workspace directory of the node running the checkout step.
I realize that the 'Waiting' message is not an error, but it is the only information I am getting when I attempt to checkout from quickbuild.
All of the items you suggested to check are correct.
I have another idea for this problem.
We are using non-unique build.version numbers.
We are using the version number from our pom.xml files as the build version number.
Could this be the cause of my problem?
GaryS
Hi Gary,
Non-unique build versions should work as well. If you can send backup of your database to [robin AT pmease DOT com] and point me which configuration to examine, I might be able to find out the reason.
Regards
Robin
