(False alarm) JitPack build is failing

[vestrel00]

So, this is weird. After this commit to main, b46437d, we get the following errors in JitCI...

1353.	
1354.	BUILD SUCCESSFUL in 1s
1355.	297 actionable tasks: 41 executed, 256 up-to-date
1356.	01:45 $ ./gradlew deploy -I ../deploy.gradle
1357.	Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2
1358.	No artifacts found in contacts-android configuration.archives
1359.	Artifacts in configuration async: 2
1360.	Publishing artifacts to DEPLOY_DIR: 
1361.	 - async.aar
1362.	 - f /home/jitpack/build/contacts-android/async/build/outputs/aar/async-debug.aar
1363.	 - async.aar
1364.	 - f /home/jitpack/build/contacts-android/async/build/outputs/aar/async-release.aar
1365.	
1366.	FAILURE: Build failed with an exception.
1367.	
1368.	* Where:
1369.	Initialization script '/home/jitpack/build/deploy.gradle' line: 35
1370.	
1371.	* What went wrong:
1372.	Could not get unknown property 'java' for SoftwareComponentInternal set of type org.gradle.api.internal.component.DefaultSoftwareComponentContainer.
1373.	
1374.	* Try:
1375.	Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
1376.	
1377.	* Get more help at https://help.gradle.org
1378.	
1379.	BUILD FAILED in 1s
1380.	Command exit code: 1
Notification result: Emailed: [email protected]
Published to JitPack:
 - 
JitPack. Updated status for com.github.vestrel00/contacts-android/main-SNAPSHOT to Error. {"status":"ok"}

Link to build: https://jitci.com/gh/vestrel00/contacts-android/124

Seems like the Gradle build succeeds but the JitPack script is failing; Initialization script '/home/jitpack/build/deploy.gradle' line: 35

I'm investigating the issue now but if anyone comes across this and you know the solution, please leave a comment!

[vestrel00]

Okay, so I noticed that the PR branch or any branch that is not the main branch is not executing the "Publish" stage, which is where the failure occurs.

I'll have to investigate why the Publish stage is failing after that commit; b46437d

[vestrel00]

Unchecking the "Publish to Internal" option does NOT fix it.

[vestrel00]

Unchecking "Publish on JitPack.io" option does NOT fix it.

[vestrel00]

This option is also not something we want to uncheck 🤣

[vestrel00]

Unchecking "Publish -> Run default commands" seems to "fix" the issue; https://jitci.com/gh/vestrel00/contacts-android/128

More investigation needs to be done!

• I need to investigate further to ensure that the artifacts are actually getting published to JitPack! Unchecking this option might have just disabled publishing artifacts to internal and JitPack... It does say that the artifacts are published but I'm not sure if it means "no files are published" or not.
• Another thing to try is to rebuild a previously passing build in the main branch and see if it still passes with the default settings. It could be the that issue is coming from a change from JitPack and not this repo's code or settings.

[vestrel00]

Okay. It seems like I wasted my time. The issue was from JitPack. Builds started passing now for no reason 🤣 https://jitci.com/gh/vestrel00/contacts-android/130

Next time stuff like this happens, I'll wait a day or two 😁

P.S. I didn't really find any hot issues in the JitPack GitHub repo that might be related to this; https://github.com/jitpack/jitpack.io/issues But then again, I only looked for less than a minute

[vestrel00]

Because of this, there are ❌ marks in the main branch history 😢