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.

QuickBuild

How let the build fail if any of the substeps failed? #2735

#1
Maxxi ·
I have a setup with a parallel step which contains a sequential step with a list of many substeps.
The build seems to run forever, even though one of the steps in the sequential step list has already failed.
I already have the parent parallel step success condition set to "if all child steps are successeful", but apparently it only looks for immediate children, not all children.
  • replies 5
  • views 1520
  • stars 0
#2
robinshen ADMIN ·
Does the build continues to run subsequent child steps in that case, or just block there without running any other steps? If continues to run other steps, you may need to check step execute condition of subsequent steps to see if they have set to "execute only if previous steps are successful".
#3
Maxxi ·
No it blocks there and all steps are yellow.
#4
robinshen ADMIN ·
If all child steps are running, what make you believe that one of the step is failed? Are you observing from logs? If yes, can you please post some snippet of log here?
#5
Maxxi ·
Failed to run command: mvn.bat clean validate package
Command return code: 1
Command error output: Mrz 18, 2014 11:20:43 AM com.izforge.izpack.core.container.PlatformProvider provide
INFO: Detected platform: windows,version=6.1,arch=x86,symbolicName=WINDOWS_7,javaVersion=1.7.0_25
Mrz 18, 2014 11:20:44 AM com.izforge.izpack.compiler.CompilerConfig addInfo
INFO: Adding uninstaller
Exception in thread "main" java.lang.AssertionError: com.izforge.izpack.api.exception.CompilerException: D:\Quickbuild_Agent\workspace\root[...]\installer\target/staging/install.xml:28: Resource not found: D:\Quickbuild_Agent\workspace\root[...]\installer\target\staging\Licence.txt
D:\Quickbuild_Agent\workspace\root[...]\installer\target\staging\Licence.txt
at org.izpack.mojo.IzPackNewMojo.execute(IzPackNewMojo.java:184)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:106)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:20...


This is where the step was yellow forever. The installer maven usually finishes within seconds if there are no errors present. (=after I added the licence.txt)
The problem is why it would halt forever instead of aborting with the error as it should, because clearly "if all child steps are successeful" should be false by then.

So the topology of the steps is like this:

  parallel -
           - webserver
           - sequential
                       - buildsomething
                       - installer (! fails but does not cause 'parallel' to fail, which I would expect)
                       - buildsomethingelse
#6
robinshen ADMIN ·
When executing external command (including all Maven and Ant builds), QB has to wait for external process to terminate gracefully. Normally the maven process should quit after encounting an error, but in your case, it does not. This may happen for instance if your maven build expects an input from terminal, or displays some UI for user interation. Can you please run exactly the same command from command line to see if it can exit upon such error?
Log in to reply