Started by user alexbegt
Connecting to https://api.github.com using progwml6 ci login
Obtained Jenkinsfile from 6206a336283a3056225dc6088ed48bf12dcebfa6
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in /var/lib/jenkins/workspace/ironchests_1.16
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
The recommended git tool is: NONE
using credential progwml6-ci-gh-login
 > git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/ironchests_1.16/.git # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/progwml6/ironchest.git # timeout=10
Fetching without tags
Fetching upstream changes from https://github.com/progwml6/ironchest.git
 > git --version # timeout=10
 > git --version # 'git version 1.8.3.1'
using GIT_ASKPASS to set credentials progwml6 ci login
 > git fetch --no-tags --progress https://github.com/progwml6/ironchest.git +refs/heads/1.16:refs/remotes/origin/1.16 # timeout=10
Checking out Revision 6206a336283a3056225dc6088ed48bf12dcebfa6 (1.16)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 6206a336283a3056225dc6088ed48bf12dcebfa6 # timeout=10
Commit message: "Crystal chests will now render the items inside again, and the broken upgrade recipes have been fixed. Closes #249, Closes #245"
 > git rev-list --no-walk 6206a336283a3056225dc6088ed48bf12dcebfa6 # timeout=10
[Pipeline] }
[Pipeline] // stage
[Pipeline] withEnv
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Checkout)
[Pipeline] checkout
The recommended git tool is: NONE
using credential progwml6-ci-gh-login
 > git rev-parse --resolve-git-dir /var/lib/jenkins/workspace/ironchests_1.16/.git # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/progwml6/ironchest.git # timeout=10
Fetching without tags
Fetching upstream changes from https://github.com/progwml6/ironchest.git
 > git --version # timeout=10
 > git --version # 'git version 1.8.3.1'
using GIT_ASKPASS to set credentials progwml6 ci login
 > git fetch --no-tags --progress https://github.com/progwml6/ironchest.git +refs/heads/1.16:refs/remotes/origin/1.16 # timeout=10
Checking out Revision 6206a336283a3056225dc6088ed48bf12dcebfa6 (1.16)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 6206a336283a3056225dc6088ed48bf12dcebfa6 # timeout=10
Commit message: "Crystal chests will now render the items inside again, and the broken upgrade recipes have been fixed. Closes #249, Closes #245"
[Pipeline] sh
+ rm -rf build/libs
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build)
[Pipeline] sh
+ ./gradlew build -PBUILD_NUMBER=12 --no-daemon
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.2-20210702220150+0000/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build 
> Task :compileJava UP-TO-DATE
> Task :processResources UP-TO-DATE
> Task :replaceResources UP-TO-DATE
> Task :classes UP-TO-DATE
> Task :jar
> Task :downloadMcpConfig
> Task :extractSrg UP-TO-DATE
> Task :createMcpToSrg UP-TO-DATE
> Task :reobfJar
> Task :sourcesJar
> Task :assemble
> Task :compileTestJava NO-SOURCE
> Task :processTestResources NO-SOURCE
> Task :testClasses UP-TO-DATE
> Task :test NO-SOURCE
> Task :check UP-TO-DATE
> Task :build

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.2-20210702220150+0000/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 14s
8 actionable tasks: 4 executed, 4 up-to-date
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Archive)
[Pipeline] archive
The archive step is deprecated, please use archiveArtifacts instead.
[Pipeline] junit
Recording test results
None of the test reports contained any result
[Checks API] No suitable checks publisher found.
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Deploy)
[Pipeline] sh
+ ./gradlew publishMavenJavaPublicationToMavenRepository -PBUILD_NUMBER=12 -PDEPLOY_DIR=/var/www/dvs1/files/maven --no-daemon
To honour the JVM settings for this build a single-use Daemon process will be forked. See https://docs.gradle.org/7.2-20210702220150+0000/userguide/gradle_daemon.html#sec:disabling_the_daemon.
Daemon will be stopped at the end of the build 
> Task :generatePomFileForMavenJavaPublication
> Task :compileJava UP-TO-DATE
> Task :processResources UP-TO-DATE
> Task :replaceResources UP-TO-DATE
> Task :classes UP-TO-DATE
> Task :jar
> Task :downloadMcpConfig
> Task :extractSrg UP-TO-DATE
> Task :createMcpToSrg UP-TO-DATE
> Task :reobfJar
> Task :sourcesJar UP-TO-DATE
> Task :publishMavenJavaPublicationToMavenRepository

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.2-20210702220150+0000/userguide/command_line_interface.html#sec:command_line_warnings

BUILD SUCCESSFUL in 6s
10 actionable tasks: 5 executed, 5 up-to-date
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

Could not update commit status, please check if your scan credentials belong to a member of the organization or a collaborator of the repository and repo:status scope is selected


GitHub has been notified of this commit’s build result

Finished: SUCCESS