-
-
Notifications
You must be signed in to change notification settings - Fork 327
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix CI/CD pipeline #971
Fix CI/CD pipeline #971
Conversation
I guess not, Bitrise is still failing nearly instantly. I think the issue is in the Bitrise workflow configuration. I had to change mine to get it to get past the new Java 17 requirement, like so:
The changes in this branch are also required, but the errors that are being fixed won't appear until the pipeline can get past the current error ("error: invalid source release: 17"). |
4932bc1
to
52431f5
Compare
THanks, we'll work on getting bitrise fixed up again. |
I will also try to help this get resolved faster. Can you rebase on master so everything is up-to-date @hax0rbana-adam ? I want to take a look on what the actual problem is that the applied changes cannot fix. |
52431f5
to
aa32c3c
Compare
I have rebased on the default branch, and I think I even did so correctly this time. |
Thanks! It looks like there is a mismatch in the Java version we use.
Plus, things are broken starting from #903, as Bitrise checks passed before. Could you try to revert said PR and see if my hypothesis is true or not? |
No need to revert, just change here to 17. orbot/.github/workflows/android.yml Line 22 in 5457cf1
|
I updated the java version in .github/workflows/android.yml, but I still think the change need to be made in the bitrise UI. |
Will review this week |
fixed now... had to add the bitrise step to set java sdk to 17 |
It looks like there are linter errors that are stopping the CI/CD from running on all branches, so I thought I'd take a shot at trying to fix them.
This builds on !965 since that's the MR where I was trying to make the CI/CD green. I didn't commit it over there because I didn't want to force these changes to be accepted with the logo change.