CircleCI start running steps in parallel after number of steps












0















I have a config.yaml for my CirleCI workflow.



I use PHPUnit to run my tests but I would like to start running these in parallel using Circle to speed up the deploy process.



So BuildJob looks like this:



jobs:

  #  build-job

  build-job:

    <<: *defaults  

    resource_class: large

    steps:

      - checkout

      - run: sudo apt install -y libsqlite3-dev zlib1g-dev libpng-dev libxml2-dev

      - run: sudo docker-php-ext-install zip

      - run: sudo docker-php-ext-install gd

      - run: sudo docker-php-ext-install soap

      - run: sudo docker-php-ext-install bcmath

      - run: sudo composer self-update

      - restore_cache:

          keys:

            - composer-v1-{{ checksum "composer.lock" }}

            - composer-v1-

      - run: composer install -n --prefer-dist

      - save_cache:

          key: composer-v1-{{ checksum "composer.lock" }}

          paths:

            - vendor

      - restore_cache:

          keys:

            - node-v1-{{ checksum "package.json" }}

            - node-v1-

      - run: 

          name: Create sqlite db

          command: touch database/database.sqlite

      - run: 

          name: Run tests

          command: ./vendor/bin/phpunit -d memory_limit=512M

      - persist_to_workspace:

          root: ~/laravel

          paths: .


So I know I need to add parallelism: 4 into there before the steps to run them in parallel, as documented here but I need the steps up to Run tests in order. Then I will have multiple run tests steps to hit each folder of tests.



Is there anyway to achieve this?






phpunit circleci circleci-2.0







share|improve this question


















  • 1





    First off, parallelism is not necessary. You just need to define multiple jobs (you only have the one build-job) and split up the testing scope of phpunit.

    – matfax
    Nov 15 '18 at 23:21
















0















I have a config.yaml for my CirleCI workflow.



I use PHPUnit to run my tests but I would like to start running these in parallel using Circle to speed up the deploy process.



So BuildJob looks like this:



jobs:

  #  build-job

  build-job:

    <<: *defaults  

    resource_class: large

    steps:

      - checkout

      - run: sudo apt install -y libsqlite3-dev zlib1g-dev libpng-dev libxml2-dev

      - run: sudo docker-php-ext-install zip

      - run: sudo docker-php-ext-install gd

      - run: sudo docker-php-ext-install soap

      - run: sudo docker-php-ext-install bcmath

      - run: sudo composer self-update

      - restore_cache:

          keys:

            - composer-v1-{{ checksum "composer.lock" }}

            - composer-v1-

      - run: composer install -n --prefer-dist

      - save_cache:

          key: composer-v1-{{ checksum "composer.lock" }}

          paths:

            - vendor

      - restore_cache:

          keys:

            - node-v1-{{ checksum "package.json" }}

            - node-v1-

      - run: 

          name: Create sqlite db

          command: touch database/database.sqlite

      - run: 

          name: Run tests

          command: ./vendor/bin/phpunit -d memory_limit=512M

      - persist_to_workspace:

          root: ~/laravel

          paths: .


So I know I need to add parallelism: 4 into there before the steps to run them in parallel, as documented here but I need the steps up to Run tests in order. Then I will have multiple run tests steps to hit each folder of tests.



Is there anyway to achieve this?






phpunit circleci circleci-2.0







share|improve this question


















  • 1





    First off, parallelism is not necessary. You just need to define multiple jobs (you only have the one build-job) and split up the testing scope of phpunit.

    – matfax
    Nov 15 '18 at 23:21














0












0








0








I have a config.yaml for my CirleCI workflow.



I use PHPUnit to run my tests but I would like to start running these in parallel using Circle to speed up the deploy process.



So BuildJob looks like this:



jobs:

  #  build-job

  build-job:

    <<: *defaults  

    resource_class: large

    steps:

      - checkout

      - run: sudo apt install -y libsqlite3-dev zlib1g-dev libpng-dev libxml2-dev

      - run: sudo docker-php-ext-install zip

      - run: sudo docker-php-ext-install gd

      - run: sudo docker-php-ext-install soap

      - run: sudo docker-php-ext-install bcmath

      - run: sudo composer self-update

      - restore_cache:

          keys:

            - composer-v1-{{ checksum "composer.lock" }}

            - composer-v1-

      - run: composer install -n --prefer-dist

      - save_cache:

          key: composer-v1-{{ checksum "composer.lock" }}

          paths:

            - vendor

      - restore_cache:

          keys:

            - node-v1-{{ checksum "package.json" }}

            - node-v1-

      - run: 

          name: Create sqlite db

          command: touch database/database.sqlite

      - run: 

          name: Run tests

          command: ./vendor/bin/phpunit -d memory_limit=512M

      - persist_to_workspace:

          root: ~/laravel

          paths: .


So I know I need to add parallelism: 4 into there before the steps to run them in parallel, as documented here but I need the steps up to Run tests in order. Then I will have multiple run tests steps to hit each folder of tests.



Is there anyway to achieve this?






phpunit circleci circleci-2.0







share|improve this question














I have a config.yaml for my CirleCI workflow.



I use PHPUnit to run my tests but I would like to start running these in parallel using Circle to speed up the deploy process.



So BuildJob looks like this:



jobs:

  #  build-job

  build-job:

    <<: *defaults  

    resource_class: large

    steps:

      - checkout

      - run: sudo apt install -y libsqlite3-dev zlib1g-dev libpng-dev libxml2-dev

      - run: sudo docker-php-ext-install zip

      - run: sudo docker-php-ext-install gd

      - run: sudo docker-php-ext-install soap

      - run: sudo docker-php-ext-install bcmath

      - run: sudo composer self-update

      - restore_cache:

          keys:

            - composer-v1-{{ checksum "composer.lock" }}

            - composer-v1-

      - run: composer install -n --prefer-dist

      - save_cache:

          key: composer-v1-{{ checksum "composer.lock" }}

          paths:

            - vendor

      - restore_cache:

          keys:

            - node-v1-{{ checksum "package.json" }}

            - node-v1-

      - run: 

          name: Create sqlite db

          command: touch database/database.sqlite

      - run: 

          name: Run tests

          command: ./vendor/bin/phpunit -d memory_limit=512M

      - persist_to_workspace:

          root: ~/laravel

          paths: .


So I know I need to add parallelism: 4 into there before the steps to run them in parallel, as documented here but I need the steps up to Run tests in order. Then I will have multiple run tests steps to hit each folder of tests.



Is there anyway to achieve this?






phpunit circleci circleci-2.0




phpunit circleci circleci-2.0






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 13 '18 at 11:22









Lewis SmithLewis Smith

15511




15511








  • 1





    First off, parallelism is not necessary. You just need to define multiple jobs (you only have the one build-job) and split up the testing scope of phpunit.

    – matfax
    Nov 15 '18 at 23:21














  • 1





    First off, parallelism is not necessary. You just need to define multiple jobs (you only have the one build-job) and split up the testing scope of phpunit.

    – matfax
    Nov 15 '18 at 23:21








1




1





First off, parallelism is not necessary. You just need to define multiple jobs (you only have the one build-job) and split up the testing scope of phpunit.

– matfax
Nov 15 '18 at 23:21





First off, parallelism is not necessary. You just need to define multiple jobs (you only have the one build-job) and split up the testing scope of phpunit.

– matfax
Nov 15 '18 at 23:21












1 Answer
1






active

oldest

votes


















1














The usual approach of using the CircleCI CLI command circleci tests split to split the tests up for parallel containers does not work with phpunit, according to this discussion (https://discuss.circleci.com/t/how-to-execute-phpunit-tests-in-parallel/25622). However, as @matfax is saying, can you run the tests in several logical groups? Something like



./vendor/bin/phpunit tests/ThisGroup

./vendor/bin/phpunit tests/ThatGroup


If so, you could then run each of those commands in a parallel job within a CircleCI workflow.






share|improve this answer
























  • Trouble is running those first parts, I think I need a couple jobs, one to set up and one to run the tests in parallel

    – Lewis Smith
    Dec 3 '18 at 11:07











  • One to set up (and save workspace), then multiple to run tests in parallel (with attached workspace) I think.

    – macbeccam
    Dec 3 '18 at 16:10











  • Yep sounds about right.

    – Lewis Smith
    Dec 3 '18 at 16:23











  • You should not attempt to use workspace for tools installed with apt-get, etc. Instead consider a single job that adds these to a custom docker image that downstream jobs can use. To make builds even faster, consider a separate project/repo to build your PHP image as needed, and reference that in you jobs.

    – Eddie
    Dec 6 '18 at 15:54











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53279951%2fcircleci-start-running-steps-in-parallel-after-number-of-steps%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














The usual approach of using the CircleCI CLI command circleci tests split to split the tests up for parallel containers does not work with phpunit, according to this discussion (https://discuss.circleci.com/t/how-to-execute-phpunit-tests-in-parallel/25622). However, as @matfax is saying, can you run the tests in several logical groups? Something like



./vendor/bin/phpunit tests/ThisGroup

./vendor/bin/phpunit tests/ThatGroup


If so, you could then run each of those commands in a parallel job within a CircleCI workflow.






share|improve this answer
























  • Trouble is running those first parts, I think I need a couple jobs, one to set up and one to run the tests in parallel

    – Lewis Smith
    Dec 3 '18 at 11:07











  • One to set up (and save workspace), then multiple to run tests in parallel (with attached workspace) I think.

    – macbeccam
    Dec 3 '18 at 16:10











  • Yep sounds about right.

    – Lewis Smith
    Dec 3 '18 at 16:23











  • You should not attempt to use workspace for tools installed with apt-get, etc. Instead consider a single job that adds these to a custom docker image that downstream jobs can use. To make builds even faster, consider a separate project/repo to build your PHP image as needed, and reference that in you jobs.

    – Eddie
    Dec 6 '18 at 15:54
















1














The usual approach of using the CircleCI CLI command circleci tests split to split the tests up for parallel containers does not work with phpunit, according to this discussion (https://discuss.circleci.com/t/how-to-execute-phpunit-tests-in-parallel/25622). However, as @matfax is saying, can you run the tests in several logical groups? Something like



./vendor/bin/phpunit tests/ThisGroup

./vendor/bin/phpunit tests/ThatGroup


If so, you could then run each of those commands in a parallel job within a CircleCI workflow.






share|improve this answer
























  • Trouble is running those first parts, I think I need a couple jobs, one to set up and one to run the tests in parallel

    – Lewis Smith
    Dec 3 '18 at 11:07











  • One to set up (and save workspace), then multiple to run tests in parallel (with attached workspace) I think.

    – macbeccam
    Dec 3 '18 at 16:10











  • Yep sounds about right.

    – Lewis Smith
    Dec 3 '18 at 16:23











  • You should not attempt to use workspace for tools installed with apt-get, etc. Instead consider a single job that adds these to a custom docker image that downstream jobs can use. To make builds even faster, consider a separate project/repo to build your PHP image as needed, and reference that in you jobs.

    – Eddie
    Dec 6 '18 at 15:54














1












1








1







The usual approach of using the CircleCI CLI command circleci tests split to split the tests up for parallel containers does not work with phpunit, according to this discussion (https://discuss.circleci.com/t/how-to-execute-phpunit-tests-in-parallel/25622). However, as @matfax is saying, can you run the tests in several logical groups? Something like



./vendor/bin/phpunit tests/ThisGroup

./vendor/bin/phpunit tests/ThatGroup


If so, you could then run each of those commands in a parallel job within a CircleCI workflow.






share|improve this answer













The usual approach of using the CircleCI CLI command circleci tests split to split the tests up for parallel containers does not work with phpunit, according to this discussion (https://discuss.circleci.com/t/how-to-execute-phpunit-tests-in-parallel/25622). However, as @matfax is saying, can you run the tests in several logical groups? Something like



./vendor/bin/phpunit tests/ThisGroup

./vendor/bin/phpunit tests/ThatGroup


If so, you could then run each of those commands in a parallel job within a CircleCI workflow.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 30 '18 at 23:20









macbeccammacbeccam

343




343













  • Trouble is running those first parts, I think I need a couple jobs, one to set up and one to run the tests in parallel

    – Lewis Smith
    Dec 3 '18 at 11:07











  • One to set up (and save workspace), then multiple to run tests in parallel (with attached workspace) I think.

    – macbeccam
    Dec 3 '18 at 16:10











  • Yep sounds about right.

    – Lewis Smith
    Dec 3 '18 at 16:23











  • You should not attempt to use workspace for tools installed with apt-get, etc. Instead consider a single job that adds these to a custom docker image that downstream jobs can use. To make builds even faster, consider a separate project/repo to build your PHP image as needed, and reference that in you jobs.

    – Eddie
    Dec 6 '18 at 15:54



















  • Trouble is running those first parts, I think I need a couple jobs, one to set up and one to run the tests in parallel

    – Lewis Smith
    Dec 3 '18 at 11:07











  • One to set up (and save workspace), then multiple to run tests in parallel (with attached workspace) I think.

    – macbeccam
    Dec 3 '18 at 16:10











  • Yep sounds about right.

    – Lewis Smith
    Dec 3 '18 at 16:23











  • You should not attempt to use workspace for tools installed with apt-get, etc. Instead consider a single job that adds these to a custom docker image that downstream jobs can use. To make builds even faster, consider a separate project/repo to build your PHP image as needed, and reference that in you jobs.

    – Eddie
    Dec 6 '18 at 15:54

















Trouble is running those first parts, I think I need a couple jobs, one to set up and one to run the tests in parallel

– Lewis Smith
Dec 3 '18 at 11:07





Trouble is running those first parts, I think I need a couple jobs, one to set up and one to run the tests in parallel

– Lewis Smith
Dec 3 '18 at 11:07













One to set up (and save workspace), then multiple to run tests in parallel (with attached workspace) I think.

– macbeccam
Dec 3 '18 at 16:10





One to set up (and save workspace), then multiple to run tests in parallel (with attached workspace) I think.

– macbeccam
Dec 3 '18 at 16:10













Yep sounds about right.

– Lewis Smith
Dec 3 '18 at 16:23





Yep sounds about right.

– Lewis Smith
Dec 3 '18 at 16:23













You should not attempt to use workspace for tools installed with apt-get, etc. Instead consider a single job that adds these to a custom docker image that downstream jobs can use. To make builds even faster, consider a separate project/repo to build your PHP image as needed, and reference that in you jobs.

– Eddie
Dec 6 '18 at 15:54





You should not attempt to use workspace for tools installed with apt-get, etc. Instead consider a single job that adds these to a custom docker image that downstream jobs can use. To make builds even faster, consider a separate project/repo to build your PHP image as needed, and reference that in you jobs.

– Eddie
Dec 6 '18 at 15:54


















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid …



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53279951%2fcircleci-start-running-steps-in-parallel-after-number-of-steps%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







-

Popular posts from this blog

Florida Star v. B. J. F.

Image
Florida Star v. B. J. F. From Wikipedia, the free encyclopedia Jump to navigation Jump to search United States Supreme Court case Florida Star v. B. J. F. Supreme Court of the United States Argued March 21, 1989 Decided June 21, 1989 Full case name The Florida Star v. B. J. F. Citations 491 U.S. 524 ( more ) 109 S. Ct. 2603; 105 L. Ed. 2d 443; 1989 U.S. LEXIS 3120; 57 U.S.L.W. 4816; 16 Media L. Rep. 1801 Prior history The Florida Star v. B.J.F., 530 So.2d 286 (1988) Supreme Court of Florida; Florida Star v. B.J.F., 499 So.2d 883 (1986) Fla. Dist. Court of Appeals Holding Florida Stat. § 794.03 is unconstitutional to the extent it makes the truthful reporting of information that was a matter of public record unlawful, as it violates the First Amendment. Court membership Chief Justice William Rehnquist Associate Justices William J. Brennan Jr.  · Byron White Thurgood Marshall  · Harry Blac
Read more

Danny Elfman

Image
Danny Elfman From Wikipedia, the free encyclopedia Jump to navigation Jump to search Danny Elfman Elfman at the 2010 San Diego Comic-Con Born Daniel Robert Elfman ( 1953-05-29 ) May 29, 1953 (age 65) Los Angeles, California, U.S. Spouse(s) Bridget Fonda ( m.  2003) Children 1 Musical career Genres Rock [1] ska [2] new wave film music video game music Occupation(s) Composer, singer, songwriter, record producer Instruments Trombone guitar percussion vocals keyboards [3] Years active 1972–present Associated acts Oingo Boingo James Newton Howard Daniel Robert Elfman (born May 29, 1953) is an American composer, singer, songwriter, and record producer. Elfman first became known for being the lead singer and songwriter for the band Oingo Boingo from 1974 to 1995. He is well known for scoring films and television shows, particularly his frequent collabora
Read more

Retrieve a Users Dashboard in Tumblr with R and TumblR. Oauth Issues

Image
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box; } 0 I am trying to use the TumblR package in R to set up the Oauth Authentication to Retrieve a user's dashboard using the second example in tumblR documentation However I get the following error, it seems that using twitter others have been able to use a different function to get around this, but I am not finding the same function available for Tumblr. See twitter package for R authentication: error 401 My code consumer_key <- OKey consumer_secret <- SKey appname <- App_name tokenURL <- 'http://www.tumblr.com/oauth/request_token' accessTokenURL <- 'http://www.tumblr.com/oauth/acces_token'
Read more