Update Plugin to Support Separate URL's for API and Frontend - Links to Projects do not work without this about dependency-track-plugin HOT 9 CLOSED

@jonbrohauge, thanks for the PR, I will look at it within the next days.

from dependency-track-plugin.

Is anyone looking at this?
I'm trying to hack my way through this, but I'm no Jenkins-plugin expert.

from dependency-track-plugin.

@sephiroth-j Could you take a look to see if it's something remotely useful?
PR: #23

from dependency-track-plugin.

Separating Frontend and Backend was already possible in version 3.8. The bundled distribution is still available with v4.0 but deprecated. The new setting will therefore be optional.

from dependency-track-plugin.

@jonbrohauge , @JBlandHV : Please give this build a try. It contains the proposed fix this issue.
https://github.com/jenkinsci/dependency-track-plugin/suites/1886262418/artifacts/36865613

from dependency-track-plugin.

@sephiroth-j Works on my machine 😉

from dependency-track-plugin.

@sephiroth-j This also works for me. I noticed on jobs that have already run it doesn't as I guess those URL's are already generated but new ones work like a champ. I'm not worried about the older jobs and ultimately imagine nothing much to be done about it, they'll drop out of the system over time anyway.

Appreciate the fast fix on this.

from dependency-track-plugin.

Thanks for testing. 😃

@sephiroth-j This also works for me. I noticed on jobs that have already run it doesn't as I guess those URL's are already generated but new ones work like a champ.

Yes, that is correct, the new URL is only used for new build jobs. This is because the URL can be specific to a job run and is therefore persisted along with the job result.

from dependency-track-plugin.

No problems. That makes sense :)

from dependency-track-plugin.