-
Improvement
-
Resolution: Not A Defect
-
Minor
-
plugin version: 2.2.0
jenkins: CloudBees Jenkins Enterprise 2.176.4.3-rolling
Currently the plugin/pipeline configuration requires an existing project by defining projectId.
I think it would be smoother to auto-create project, and read name/version from pom-files like:
name: ${groupId}-${artifactId}
version: ${version}
then the entry-barrier would be lowered and it would be easier to adopt DT at larger scale.
[JENKINS-60643] Auto-create project for maven-based jobs
Hm - I get:
Missing required parameter: "projectId" @ line 114, column 9.
dependencyTrackPublisher artifact: 'target/bom.xml', artifactType: 'bom'
when running with:
dependencyTrackPublisher artifact: 'target/bom.xml', artifactType: 'bom'
Pipeline parameters are documented here:
https://jenkins.io/doc/pipeline/steps/dependency-track/
If you don't specify a projectId, then you have to specify the projectName and projectVersion. If the project name and version does not exist, it will be created.
I get:
WorkflowScript: 102: Invalid parameter "projectVersion", did you mean "projectId"? @ line 102, column 121.
.edb.fs.tac.jfr.srv:jfr-srv", projectVer
^
when running:
dependencyTrackPublisher artifact: 'bom.xml', artifactType: 'bom', projectId: "com.edb.fs.tac.jfr.srv:jfr-srv", projectVersion: "10.1.0-SNAPSHOT"
When I visit the ..../pipeline-syntax page, only these parameters are documented:
dependencyTrackPublisher: Publish results to Dependency-Track
projectId
Type:String
artifact
Type:String
artifactType
Type:String
installed plugin version: 2.2.0
| Environment |
New:
plugin version: 2.2.0 jenkins: CloudBees Jenkins Enterprise 2.176.4.3-rolling |
I'm still unable to replicate. The automated generated docs posted here https://jenkins.io/doc/pipeline/steps/dependency-track/ contain all the configurable params including the projectName and projectVersion params I mentioned earlier. The pipeline syntax feature in Jenkins itself has a lot of limitations and will not properly generate all docs for some plugins. Use jenkins.io for plugin docs.
dependencyTrackPublisher artifact: 'bom.xml', artifactType: 'bom', projectName: 'Acme Example', projectVersion: '1.0.0', synchronous: true
| Attachment | New: Screenshot 2020-01-22 at 14.17.14.png [ 50023 ] |
Our config section looks a "little strange" - double up with settings. What could cause this?
Auto-creating projects is already supported, but is limited to pipeline jobs. Non-pipeline jobs do not have the option.