3rd party packages version control

Amit Bhardwaj

unread,

Aug 31, 2015, 8:39:44 AM8/31/15

to Jenkins Users

Hello Group !!

I am in process of evaluation and implementing Jenkins and so far successful in almost everything I intended. Here is an important task on which I need your expert opinions.

Is there any way I can take care of 3rd party packages and list them with each build? Something like a list or file that has the 3rd party packages list with its version respectively so that in future if I want to get code base for some build #, I also know what version of 3rd party packages I used at that time.

I agree requirement seems to be a bit unclear as I am unsure if Jenkins is the right tool that can help me in this. Please let me know if you need any further inputs from my side.

Simply put, I want list of 3rd party tools we have at the time of build with version of all 3rd party packages.

--

Thanks and

R

egards,

AB

Richard Bywater

unread,

Aug 31, 2015, 5:00:36 PM8/31/15

to Jenkins Users

You might want to provide more details like what language and build system you are using otherwise it's quite hard to help.

Richard

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAKs7jXLWv0L6quui9jto7Uz%3DsgD52OT8a0fHb4xqMUHjTRdO3w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Victor Martinez

unread,

Sep 6, 2015, 11:32:18 AM9/6/15

to Jenkins Users

You might need some other tool, such as BlackDuck, Protecode, etc

Some of them are already integrated with jenkins:
- https://wiki.jenkins-ci.org/display/JENKINS/Black+Duck+Open+Source+Vulnerability+Plugin

Cheers

AB

unread,

Sep 21, 2015, 3:20:48 AM9/21/15

to Jenkins Users

Oh I am so sorry I missed the update on my query.

We have codebase in both C and Python. There are few 3rd party libraries that we have in make process. The requirement actually is to map the 3rd party packages that we would need to ship with each make/build to customer end. A list with direct link to vendor or a local repo along with its version/MD5 would be easy to track things if we revisit a build say 1-2 years from now.

Suppose for a Build A, one needs v1.0 of 3rd party package, B(scope is outside make process). Tomorrow A grows and B changes its version but we need to revisit previous version of A and also would want a list of Bs that I used for complete suite. I hope I made the requirement clear though I understand it can still be explained in a better way. Let me know if I need to add anything additional in this regard.