>
>
> *The only solution I came up with is to create 3 lockable resources of the
> same label and lock them in each*
> *of the closures. *
>
Now that I think of it - it wouldn't work anyway - another build of this
job would not be able to reach the test-throttler resources, so it would
wait
Hi!
I'm using something like this to run tests in parallel:
stage('Test') {
steps {
script {
testing_closures = [one: { print("staring one"); sleep 10;
print("finishing
one") },
two: { print("staring two"); sleep 10;
print("finishing
two") },
times with the same parameter "4"//and jenkins will unite
them into a single run of the job
W dniu środa, 9 sierpnia 2017 17:17:53 UTC+2 użytkownik Mirek S napisał:
>
> Hi!
>
> I'm using the following Pipeline script:
>
> testruns = [:]
> for (name in ["one&qu
Hi!
I'm using the following Pipeline script:
testruns = [:]
for (name in ["one", "two", "three"]) {
print("Adding ${name} to testruns")
testruns[name] = { print("Staring phase ${name}"); sleep 10;
print("Finished phase ${name}")}
}
pipeline {
agent { label 'master' }
stages {
Hello!
When trying to create account at issues.jenkins-ci.org (i.e.
accounts.jenkins.io) one needs to send an email to jenkinsci-accounts
google group. I sent my "additional verification" twice and received no
reply. I tried asking on #jenkins, no reply whatsoever. Anyone knows how to
create
Victor - since you mentioned it - did you succeed to split your tests
per-testcase?
It's only grouping suites for me - I'd like to see half of suite in one
parallel closure and the other half in another.
W dniu piątek, 3 listopada 2017 13:54:43 UTC+1 użytkownik Victor Martinez
napisał:
>
>
Hello,
I'm looking for some kind of real-time, scriptable monitor for every build
that's running.
The example scenario: Basically when I'm running tests I always ssh to the
jenkins service and run "watch -n 0.1 'tail -n 0.1
workspace/jobname/test_result_file*'" to see if given test execution
W dniu piątek, 3 listopada 2017 13:54:43 UTC+1 użytkownik Victor Martinez
napisał:
> - Can you just use Pipeline and split your tests in stages and parallel
> executions? It won't fulfil your initial requirement but might help you to
> orchestrate your builds with parallel test executions
