jitpack.yml is no longer working or being read.

[cekvenich]

Describe the bug
jitpack.yml used to work, for example echo, jvm version, cd etc.
At some point you changed something and jitpack is now ignored!

To Reproduce
Create a project with jitpack.yml and write a simple command like:
before_install:

• echo "Running install command XXX"

That echo is never shown!

Expected behavior
jitpack.yml used to work and is documented here:
https://jitpack.io/docs/BUILDING/#custom-commands

If I write a documented command like echo, it should work.
This breaks builds, since I can't cd, call scripts or even set JDK version.

Additional context
The builds are now broken, due to you no longer respecting jitpack.yml.+

[jeffque]

I don't see it this way https://jitpack.io/com/gitlab/geosales-open-source/totalcross-resultset-extractor/1.0.1-retrolambda/build.log

Based on https://gitlab.com/geosales-open-source/totalcross-resultset-extractor/-/blob/master/jitpack.yml

[gunnarmorling]

Just came here to report the same issue, my jitpack.yml is ignored. Instead of JDK 14 as configured, JDK 10 (!) is applied. That's not a good choice in any case, as this is long out of maintenance. Thanks for your efforts!

[jeffque]

@gunnarmorling , the https://jitpack.io/com/github/gunnarmorling/jmfrx/master-5eef6f76b7-1/build.log (redirected from https://jitpack.io/com/github/gunnarmorling/jmfrx/master-SNAPSHOT/build.log) tells me that it is running with Java 14.

Indeed, this is what the log shows:

Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2
Apache Maven 3.6.1 (d66c9c0b3152b2e69ee9bac180bb8fcc8e6af555; 2019-04-04T19:00:29Z)
Maven home: /opt/apache-maven-3.6.1
Java version: 14.0.2, vendor: Oracle Corporation, runtime: /home/jitpack/jdk-14.0.2
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "4.10.0-28-generic", arch: "amd64", family: "unix"

[gunnarmorling]

Hey @jeffque, yes, it's working now, but only after I manually added an install step for OpenJDK 14, see https://github.com/gunnarmorling/jmfrx/blob/master/jitpack.yml. It would fallback to Java 10 when trying this:

jdk:
  - openjdk14

(while this works for openjdk11; so I reckon that whatever mechanism provisions the JDK based on this configuration doesn't have support for JDK 14 yet)

[DetachHead]

in my case it was falling back to jdk 8 instead of 10 when i tried setting it to openjdk14

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[HoldYourWaffle]

It looks like this is still (or again) broken.

When building HoldYourWaffle/querz-nbt@404d5d8 today Jitpack tries to use Java 8 (log). However, the build of Querz/NBT@404d5d8 from May 10th correctly used Java 17 as configured (log).

Note that this is the exact same commit containing the exact same code, just in a different repository. Building a slightly older commit of Querz/NBT today yields the same issue (log for Querz/NBT@322d4211df), signaling that this must be an issue on Jitpack's side.

[HoldYourWaffle]

After some more testing it seems that for JDK 13 and later the jdk option in jitpack.yml no longer works properly.
The before_install "workaround" mentioned in the documentation seems to do the trick, but what's the point of the jdk option then?

[github-actions]

This issue is stale because it has been open for 30 days with no activity.