Never mind. Got it in
import java.lang.Object
Now I am stuck with
unable to resolve class QueueTaskFuture
unable to resolve class QueueTaskFuture
On Wed, Jul 15, 2015 at 12:55 PM, Thandesha VK tha...@gmail.com wrote:
It can't find the class Future. Could you please help
unable to
It can't find the class Future. Could you please help
unable to resolve class Future
On Monday, March 10, 2014 at 4:26:28 AM UTC+5:30, dev123 wrote:
A my bad I of course had to call the correct job, it now works thanks :-)
On Sunday, March 9, 2014 11:47:20 PM UTC+1, dev123 wrote:
Yes I
In a jenkins plugin I am writing I need to run 5 jobs in parallel.
Currently I do (sequentially):
for (int i = 0; i 4; i++) {
try {
build = project.scheduleBuild2(0, new Cause.UserCause(),
myActions[i]).get();
} catch (Exception e) {
throw new
Don't immediately call .get(), instead assign the Future returned from
scheduleBuild2 to a variable. Only .get() once you're willing to wait for the
build to complete.
On 09.03.2014, at 22:27, dev123 delber...@gmail.com wrote:
In a jenkins plugin I am writing I need to run 5 jobs in parallel.
Not sure I understand I now do:
for (int i = 0; i 4; i++) {
try {
QueueTaskFuture? scheduleBuild2 = project.scheduleBuild2(0, new
Cause.UserCause(), myActions[i]);
queue.add(scheduleBuild2);
} catch (Exception e) {
throw new
If you have the executors, the builds should run in parallel. Given the
following script in the Script Console (and jobs named wait1..wait4 with
different durations):
---
def futures = []
[1, 2, 3, 4].each {
futures.add Jenkins.instance.getItemByFullName(wait${it}).scheduleBuild2(0)
}
Since you seem to be triggering multiple builds of the same project, did you
enable the project for parallel execution of multiple builds?
On 09.03.2014, at 23:21, Daniel Beck m...@beckweb.net wrote:
If you have the executors, the builds should run in parallel
--
You received this message
Yes I did a check in allow concurrent execution.
Now when I run mvn clean hpi:run it starts the jobs in parallel on the
available executors, but its spawns jobs infinitely and the text: Done
in: + object.getTime() is never printed. And I have not even pressed the
build button.
Why do I
A my bad I of course had to call the correct job, it now works thanks :-)
On Sunday, March 9, 2014 11:47:20 PM UTC+1, dev123 wrote:
Yes I did a check in allow concurrent execution.
Now when I run mvn clean hpi:run it starts the jobs in parallel on the
available executors, but its spawns
