Skip to content

UniqueID schema easily generates collisions #18

@alevinetx

Description

@alevinetx

For table JENKINS_BUILD_DETAILS:

UID is [url of a build server]/[short job name]/[build number]
short job name being without the full tree path
so, something generic like "build" is going to crash

example

UID: jenkins.server.com/computer/jenkins-node//build/1

That can easily be non-unique if more than one path has a job named "build". We are using CloudBees Folders plugin, which allows for the subpaths.

Dept1/jobs/a tool/build
Dep2/jobs/another tool/build

There's a quick collision right there. First one wins, second one fails silently.

Found in:
https://github.com/jenkinsci/audit2db-plugin/blob/master/src/main/java/org/jenkins/plugins/audit2db/internal/model/BuildDetailsImpl.java
Line: 400-401

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions