okarmazin
okarmazin
PostsComments
RRailway
Created by okarmazin on 9/5/2024 in #✋｜help
Language provider from `nixpacks.toml` is not used
Project: f6bf90d2-8b23-4b9c-bfb2-49eabce8e261 Contents of nixpacks.toml: 
providers = ["java"]
providers = ["java"]
Contents of railway.toml: 
[build.nixpacksPlan.phases.install]
cmds = [ "mkdir -p ./shared-jvmhack/src/main && cp -R ./shared/src/commonMain/kotlin ./shared-jvmhack/src/main/kotlin" ]

[build]
builder = "NIXPACKS"
buildCommand = "./gradlew clean application:build -x check"

[deploy]
startCommand = "java -XX:+UseZGC -XX:SoftMaxHeapSize=200m -Xms30m -Xmx1500m -XX:+PrintCommandLineFlags --show-version -jar ./application/build/quarkus-app/quarkus-run.jar"
[build.nixpacksPlan.phases.install]
cmds = [ "mkdir -p ./shared-jvmhack/src/main && cp -R ./shared/src/commonMain/kotlin ./shared-jvmhack/src/main/kotlin" ]

[build]
builder = "NIXPACKS"
buildCommand = "./gradlew clean application:build -x check"

[deploy]
startCommand = "java -XX:+UseZGC -XX:SoftMaxHeapSize=200m -Xms30m -Xmx1500m -XX:+PrintCommandLineFlags --show-version -jar ./application/build/quarkus-app/quarkus-run.jar"
No provider gets used: 
 
[Region: europe-west4]
==============
Using Nixpacks
==============
context: eee02ec4c708c0708ea8ebb7e0cbc134
 
╔══════════════════════════════ Nixpacks v1.26.0 ══════════════════════════════╗
║ install    │ mkdir -p ./shared-jvmhack/src/main && cp -R                     ║
║            │ ./shared/src/commonMain/kotlin ./shared-jvmhack/src/main/kotlin ║
║──────────────────────────────────────────────────────────────────────────────║
║ build      │ ./gradlew clean application:build -x check                      ║
║──────────────────────────────────────────────────────────────────────────────║
║ start      │ java -XX:+UseZGC -XX:SoftMaxHeapSize=200m -Xms30m -Xmx1500m     ║
║            │ -XX:+PrintCommandLineFlags --show-version -jar                  ║
║            │ ./application/build/quarkus-app/quarkus-run.jar                 ║
╚══════════════════════════════════════════════════════════════════════════════╝
 
 
#0 building with "builder-51zY" instance using docker-container driver
 
#1 [internal] load build definition from Dockerfile
...
BUILD FAILED
 
[Region: europe-west4]
==============
Using Nixpacks
==============
context: eee02ec4c708c0708ea8ebb7e0cbc134
 
╔══════════════════════════════ Nixpacks v1.26.0 ══════════════════════════════╗
║ install    │ mkdir -p ./shared-jvmhack/src/main && cp -R                     ║
║            │ ./shared/src/commonMain/kotlin ./shared-jvmhack/src/main/kotlin ║
║──────────────────────────────────────────────────────────────────────────────║
║ build      │ ./gradlew clean application:build -x check                      ║
║──────────────────────────────────────────────────────────────────────────────║
║ start      │ java -XX:+UseZGC -XX:SoftMaxHeapSize=200m -Xms30m -Xmx1500m     ║
║            │ -XX:+PrintCommandLineFlags --show-version -jar                  ║
║            │ ./application/build/quarkus-app/quarkus-run.jar                 ║
╚══════════════════════════════════════════════════════════════════════════════╝
 
 
#0 building with "builder-51zY" instance using docker-container driver
 
#1 [internal] load build definition from Dockerfile
...
BUILD FAILED
------------- The result is identical if I specify the provider as providers = ["...", "java"] to allow for provider autodiscovery.
4 replies
RRailway
Created by okarmazin on 9/2/2024 in #✋｜help
Symbolic links not resolved when building with Nixpacks?
project 8093f881-dd83-4250-b725-dd87c94a218e service c4c15496-00f3-4369-a0e6-212cfedc8913 Railway builder: Nixpacks Build tool: Gradle Language: Kotlin The source directory of one of my modules ({module}/src/main/kotlin) is a symbolic link to a sibling module's source directory. The link is correct and checked in to version control - GitLab CI builds this project without any issues using the same build command. During Railway builds, however, the symbolic link isn't resolved, the module which owns the symlink reports NO-SOURCE and compilation of dependent modules fails due to unresolved references. Is there anything I can do to fix this? I suppose instead of a link I could copy the sibling module's source code during setup phase?
5 replies
RRailway
Created by okarmazin on 2/25/2024 in #✋｜help
Cannot disable autodeploy
No description
9 replies