I would like to leave CircleCI towards GitHub actions. I have migrated our publishing in

• Migrate from CircleCI to GitHub actions (publishing only) #1462

I could use some help getting our tests over. In terms of parallelism, ideally the order would be:

• assemble_testClasses first, if it fails then nothing else starts
• then every other test in parallel

I have included the details of every test below:

• assemble_testClasses

  • spotless/.circleci/config.yml

    Line 64 in 7b8ed50

    command: ./gradlew spotlessCheck assemble testClasses --build-cache

• test_justmaven_11

  • spotless/.circleci/config.yml

    Line 94 in 7b8ed50

    command: ./gradlew :plugin-maven:check --build-cache

• test_nomaven_11 and test_nomaven_17

  • spotless/.circleci/config.yml

    Line 38 in 7b8ed50

    command: export SPOTLESS_EXCLUDE_MAVEN=true && ./gradlew check -x spotlessCheck --build-cache

• test_npm_8

  • spotless/.circleci/config.yml

    Lines 100 to 103 in 7b8ed50

    	# java doesn't play nice with containers, it tries to hog the entire machine
    	# https://circleci.com/blog/how-to-handle-java-oom-errors/
    	# try the experimental JVM option
    	_JAVA_OPTIONS: "-XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap"

  • spotless/.circleci/config.yml

    Line 112 in 7b8ed50

    command: export SPOTLESS_EXCLUDE_MAVEN=true && ./gradlew testNpm --build-cache

  • spotless/.circleci/config.yml

    Line 121 in 7b8ed50

    command: export SPOTLESS_EXCLUDE_MAVEN=true && ./gradlew test --build-cache

• test_windows

  • spotless/.circleci/config.yml

    Line 136 in 7b8ed50

    command: gradlew test --build-cache -PSPOTLESS_EXCLUDE_MAVEN=true

If you're able to help, ping in this thread to say "I have started work" so that no work gets duplicated.

Don't ping to say "I could help later" - in that case just ping when you've got time to start :)