building `master` of `arrow-meta` takes about 6 m...
# arrow-meta
j
building
master
of
arrow-meta
takes about 6 minutes here. I've found that it only takes about a minute when using gradle's offline mode (flag
--offline
in a terminal and https://www.jetbrains.com/help/idea/jetgradle-tool-window.html#offline for the setting in IntelliJ)
gradle --info build
is showing lots of (failing) HTTP requests, I'm not sure why. @Imran/Malic
i
This also works for me perfectly, If I do a clean build and run everything after that in offline. Builds are now as fast as before. I think @Rachel may help you there. I tried to check if it’s an issue in Bintray or the Release in GIthub, but I could find the right data to confirm either. You cant take the
SNAPSHOT
from BIntray because the element you need is within an internal DataType… wc: Just copy whatever you need or use mock data as we discussed
r
i
Now we can run online again. Thank you @Ryan Benasutti for your pudding. I am loving it.
Push and Pull PR in Github Action is down to
4
minutes😍🤯arrow
r
Happy to help
i
I am wondering what the issue was, may you explain how you made that pudding?
r
I looked at the build scan and noticed that dependency resolution took 11.5 minutes. Lots of jfrog failures, so I moved that into the last position. Also a lot of time was spent on the arrow artifacts, so knowing that those would be pulled from arrow's bintray, I added that filter to narrow Gradle's search.
👆🏽 4
r
Thank you @Ryan Benasutti!
r
Amazing @Ryan Benasutti, and we were setting JAVA_OPTS parameters before calling Gradle and now we know that they were being redefined again inside Gradle scripts... thanks!!
I think we'll be able to do the same in Arrow
👏 👏 👏
t
You should be aware that there are problems with OpenJDK 13+ on the latest Gradle versions, in case you want to test with those.
👍 1