My release pipeline does both stages (release, deploy) and I can download the artifacts but they don’t include the pom.xml. Where in the project’s pages can one see the “package”. This is a java project using gradle.
Well that was technically true but I did not have the maven entry set up correctly. When I do set a maven packaging construct the build fails to find a dependency (logback). Seems to be looking for that within my project, not at maven central
This does NOT work on my machine (unless I comment out the maven{} block)
repositories {
mavenLocal()
mavenCentral()
maven {
url “https://gitlab.com/camplab/api/v4/projects/2690273/packages/maven”
name “JPSGCS”
credentials(HttpHeaderCredentials) {
name = ‘Private-Token’
value = gitLabPrivateToken
}
authentication {
header(HttpHeaderAuthentication)
}
}
}
This is what I’m see in the build log
manifesting version: 3.3.2-1
Classpath:
FAILURE: Build failed with an exception.
* Where:
Build file '/builds/camplab/jpsgcs/build.gradle' line: 91
* What went wrong:
A problem occurred evaluating root project 'jpsgcs'.
> Could not resolve all files for configuration ':runtimeClasspath'.
> Could not resolve ch.qos.logback:logback-core:1.2.+.
Required by:
project :
> Failed to list versions for ch.qos.logback:logback-core.
> Unable to load Maven meta-data from https://gitlab.com/camplab/api/v4/projects/2690273/packages/maven/ch/qos/logback/logback-core/maven-metadata.xml.
> Could not GET 'https://gitlab.com/users/sign_in'. Received status code 503 from server: Service Temporarily Unavailable
> Could not resolve ch.qos.logback:logback-classic:1.2.+.
Required by:
project :
had to explicitly set the version for logback