Having the projectId obligatory when using this plugin while having synchronous: true, is an issue for automatically created pipelines. Most of the developers that are going to use this tool, know nothing of the projectId, but obviously knows their projectName and projectVersion. Since the plugin can communicate fine with a Dependency-Track server only using projectName and projectVersion for non-synchronous configuration, it should also be doable with a synchronous configuration.

Executing the following pipeline step:

dependencyTrackPublisher projectId: "[projectId]", projectName: "${pom.artifactId}", projectVersion: "${pom.version}", artifact: "target/bom.xml", artifactType: 'bom', synchronous: true

works.

Executing the following pipeline step:

dependencyTrackPublisher projectName: "${pom.artifactId}", projectVersion: "${pom.version}", artifact: "target/bom.xml", artifactType: 'bom', synchronous: true

does not work.

Executing the following pipeline step:

dependencyTrackPublisher projectName: "${pom.artifactId}", projectVersion: "${pom.version}", artifact: "target/bom.xml", artifactType: 'bom', synchronous: false

works.