parallel builds in jenkins - jenkins-plugins

I just installed the "Build Flow" plugin ver 0.7 and i seem to have issues getting it to work. I configured 2 simple jobs (JOB1 and JOB2). Then another jenkins job which i named "parallel_build} that basically calls this job to build them in parallel.
In the "Define build flow using flow DS" section i have the following
parallel ( {buildIJOB1)}, {build(JOB2)} )
when i execute "parallel_build" job, the console output print the following msg and return a build faillure
parallel {
}
Notifying upstream projects of job completion
Finished: FAILURE
It does not seem to be executing the jobs i intend to run in parallel. The two jobs (JOB1 and JOB2 are pretty simple. All they do is print hello msg.
I appreciate any help in advance.
Jenny

Never mind folks. Upgrading to the latest jenkins version (1.501) from 1.447 fixed the issue. It's all good now.

try this syntax
parallel(
{build("JOB1")},
{build("JOB2")}
)

Related

Problem when running the first Flink python code

I want to run my first flink code, so I created a virtual environement and I run it with: python tab.py
I find :
What's wrong with my Pyflink setup that Python UDFs throw py4j exceptions?
but it doesn't work.

Gradle Jar Creating Task getting stucked

I am new to gradle. When running the gradle build task in intelliJ, my task keep running infinitely and never completed. The task is written as follows:
task webjar(type: Jar) {
from(fileTree("build")) {
into "META-INF/resources"
}
}
jar.finalizedBy('webjar')
Can anybody help me in pointing out if I am doing anything wrong here?
update: When i am writing the task as follows it finishes successfully:
task webjar(type: Jar) {
destinationDir file("${projectDir}/build")
from(fileTree("build")) {
into "META-INF/resources"
}
}
Thanks,
The issue is that you are attempting to pack the whole build folder into that jar, which includes all the project output.
So that is most likely the issue there. build should not be what you package in META-INF/resources.
Instead you will need to identify which task produces the content to be included in META-INF/resources and use its output as the from argument.

How to trigger a batch file in Jenkins without waiting for batch execution results and status

I have a Jenkins job which is building /packaging/ deploying .NET project. I use "Clean Before checkout" git property for each build.
Finally, I'm executing a batch file. This batch file scanning sonar Qube MSBuild, c# analysis and update the code quality results. But It is taking a long time and I don't want to increment Jenkins job's total execution time from 1 minute to 5 minutes. Developers are thinking so the deployment is taking a long time and not finished yet.
I want to run this batch file independent from the Jenkins job and don't want to see the console output in Jenkins. How could I do this without creating a new Jenkins job for each Jenkins project (upstream/downstream projects)
you need to use the start cmd command,for example:
start YourBatch.bat
This will open a new CMD window and Jenkins won't wait for result.
Bare in mind that if you get an exit code different than 0, it won't fail the build.

Android build fails in codenameone build sever

My android build fails after build and this is the error log i get
Total time: 1 mins 16.631 secs
Stopped 0 compiler daemon(s).
Received result Failure[value=org.gradle.initialization.ReportedException: org.gradle.internal.exceptions.LocationAwareException: Execution failed for task ':dexRelease'.] from daemon DaemonInfo{pid=5907, address=[10331ba5-2501-41cc-aa13-52a0ba46bd51 port:41817, addresses:[/0:0:0:0:0:0:0:1%1, /127.0.0.1]], idle=false, context=DefaultDaemonContext[uid=2862cb6d-50e8-4321-a1fa-590435e89f0f,javaHome=/usr/java/jdk1.7.0_67,daemonRegistryDir=/home/ec2-user/.gradle/daemon,pid=5907,idleTimeout=120000,daemonOpts=-XX:MaxPermSize=512m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1500m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]} (build should be done).
This is probably related to this: https://www.codenameone.com/blog/video-new-defaults-barcode-qrcode-changes.html
You can workaround this by using android.gradle=false in the build hints. However, I'm guessing its related to some cn1lib or build hint you added. But it seems the build error log you provided is partial so I don't see any issue there.

Is JRebel necessary to run Maven?

Greetings,
I am trying to start a scala/liftweb project for deployment on Google App Engine. To do this, i need to package it up as a .war using maven.
However, whenever I run the 'mvn' command, I am met with:
Error opening zip file or JAR manifest missing : /Applications/JRebel/jrebel.jar
Error occurred during initialization of VM
agent library failed to init: instrument
Is there something wrong with my maven or do I need Jrebel? I see jrebel is not free which is why I am so surprised.
thanks!
No, JRebel is definitely not required to run Maven.
As Matt mentioned, JRebel is not required to run Maven. However, ZeroTurnaround does offer a free version that works with Scala. You can get it here:
http://sales.zeroturnaround.com/
As for your error - it indicates you are trying to start the JVM as though you are using JRebel. What is the full Maven command you are running? What is in your MAVEN_OPTS environment variable? If either of them contain something like -noverify -javaagent:/Applications/JRebel/jrebel.jar, then that's your problem.
One of the reason of the problem is a blank in the path of jrebel.jar
Make sure that there is no blank in the path like in "Program Files"

Resources