Issue #18748: Split openrewrite-recipes CI job into two parallel jobs#18762
Conversation
ff852a7 to
1d119d3
Compare
|
No changes are expected. |
0f124ae to
2f137c6
Compare
|
@romani the jobs are now split and running in parallel, openrewrite-recipes-1 is executing in 5 minutes but it is failing because it found valid java 21 upgrades (changing SortedSet.first() to getFirst()). |
|
Please create issue on this we will do activation of it separately. |
2f137c6 to
5a9beb7
Compare
5a9beb7 to
7c8d08c
Compare
|
@Pankraz76 should not have problems to run all at ones and CI will run it separately. |
| - org.openrewrite.java.migrate.util.MigrateInflaterDeflaterToClose | ||
| - org.openrewrite.java.migrate.util.ReplaceStreamCollectWithToList | ||
| - org.openrewrite.java.migrate.util.SequencedCollection | ||
| # - org.openrewrite.java.migrate.util.SequencedCollection |
There was a problem hiding this comment.
why this one without any comment? now every dev has to ask this question....
yes had this myself... its an rewrite issue it feels like caching because this stuff only comes with other changes as well. We should just have applied the stuff and thats it. I dont understand the big deal |
without release users can not run the recipes anyways so this statement is for sure wrong. |
this is good reason to move it to separate job and run only by CI , not local. |
|
yes only if you have no changes and this is not supposed 2 be, so no then users having go back and forth going crazy like hell. CI (rewrite) has to work seamlessly everywhere not only somewhere. |
Fixes #18748.
this PR splits the recipes into two parallel CircleCI jobs to cut the execution time effectively in half