Brandon Fryslie added a comment - 2021-03-25 00:42 This is breaking our jobs that use Gradle to compile the Job DSL (for testing)

Steve Hill added a comment - 2021-03-25 16:19 brandonfryslie in these situations I usually get the POM from source and publish it elsewhere until it's available in the main repo. This may be useful for resolving your breaking builds. The missing version of the parent pom is available at the handlebars-3.0.8 tag of jenkinsci/js-libs . This can be downloaded and deployed to another maven repository. If you already have an internal hosted repository, that's a good spot. If this isn't feasible, you can also define a maven repository within the source repository like this: . ├── build.gradle ├── embedded-repo │   ├── org │   │   └── jenkins-ci │   │   └── ui │   │   └── jenkins-js-libs │   │   └── 2.0.0 │   │   └── jenkins-js-libs-2.0.0.pom And then define another maven repo in your build: repositories { maven { name 'Embedded' url 'embedded-repo' metadataSources { mavenPom() } content { includeVersion 'org.jenkins-ci.ui', 'jenkins-js-libs', '2.0.0' } } } It's not required to use the content filter , but I like it as an explicit reminder that this is a workaround.