Also, the deprecation notes from the last working version may help. You may get the good picture of what's wrong simply by expanding the outputs in the GitHub Actions console. Now there's a time to fix the problem for the first failing version. Then commit the changes in case of that you will need to revert some changes. We start with a workflow file located in. upgrade of static analysis tools) which may also happen in minor versions. You may argue that it would be enough to just use the major versions but there might be some consequences (e.g. The idea is to run your project against every possible minor version of Gradle between the one currently present in the project ( 4.7) and the latest one ( 6.0.1 as a time of writing) to find you the which version still working with the current setup.
Stepwise Gradle Upgrade with Gradle Actionsįollowing steps could be achieved with any continuous integration tool but GitHub Actions allow to run much more parallel jobs at once than other available CI servers I know (at least for free). It's always better to move stepwise so I took GitHub Actions for a rescue. Jumping form a very old version to the newest one is obviously not a good way to go. I usually face a storm of issues from the build when I try to get the latest possible Gradle version working.
0 kommentar(er)
