Hi,
Actually I've found that you can browse per parallel branch output by going
to "Running Steps" in the left job menu.
Can this be made more explicit for the end-user?
Should I create a ticket for that?
Thanks,
Timur
вторник, 13 января 2015 г., 19:14:49 UTC+3 пользователь Timur Batyrshin
написал:
>
> Hi,
>
> I've just started to use the new workflow plugin and it looks great.
> But I can't get readable output for parallel jobs -- it is heavily
> intermixed and hardly readable (see below).
>
> My test flow:
>
> parallel cApps: {
> node {
> // C applications built by make
> dir('c-apps') {
> checkout changelog: true, poll: true, scm: [$class: 'GitSCM',
> branches: [[name: 'remotes/origin/master']], userRemoteConfigs:
> [[credentialsId: 'XXXXX', url: 'https://github.com/XXXX/XXXX.git']]]
> sh "make clean deb"
>
> }
> }
> }, mavenProj: {
> node {
> // Maven project
> dir('maven-proj) {
> checkout changelog: true, poll: true, scm: [$class: 'GitSCM',
> branches: [[name: 'remotes/origin/master']], userRemoteConfigs:
> [[credentialsId: 'XXXXX', url: 'https://github.com/XXXX/XXXX.git']]]
> sh "mvn clean install"
> }
> }
> }
>
> (I've tried folding the parallel block to inside the single node with the
> same results).
>
> What I get is the output like the following in the build job:
>
> [INFO]
> [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @
> core-net ---
> [INFO] No sources to compile
> [INFO]
> [INFO] --- maven-surefire-plugin:2.10:test (default-test) @ core-net ---
> [INFO] No tests to run.
> [INFO] Surefire report directory:
> /mnt1/jenkins/jobs/test-workflow/workspace/maven-proj/core/net/target/surefire-reports
>
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
>
> make[1]: Leaving directory
> `/mnt1/jenkins/jobs/test-workflow/workspace/c-apps/dece'
> make -C ./ack deb
> make[1]: Entering directory
> `/mnt1/jenkins/jobs/test-workflow/workspace/c-apps/ack'
> make -C src
> make[2]: Entering directory
> `/mnt1/jenkins/jobs/test-workflow/workspace/c-apps/ack/src'
> Compiled ack_app.c successfully!
> Compiled ack_cli.c successfully!
> Compiled ack_crypt.c successfully!
> Compiled ack_ini.c successfully!
> Compiled ack_stat.c successfully!
> Compiled ack_wrk.c successfully!
> Compiled main.c successfully!
>
>
>
> Results :
>
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
>
> [INFO]
> [INFO] --- jacoco-maven-plugin:0.7.2.201409121644:report (default-report) @
> core-net ---
>
>
>
> This means that it is quite hard to determine to which branch the log
> lines belong.
> When I have more than the 2 branches building in parallel there will be
> even more difficulty in that.
> Is there a way to separate logs for the branches to make them easily
> readable?
>
> Alternatively I could spawn subjobs as parallel builds but I've read here
> that it is not recommended
> and I don't like very much the fact that I'll have 2X executors used for
> that (the one for the subjob and the one for the "building part of" -- per
> job).
>
> Any ideas on how should I deal with that?
>
>
> Thanks,
> Timur
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/0a93723a-1ae5-4157-8f6e-bb6ac283b74b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
