[JIRA] (JENKINS-41461) Provide configuration option to only get sources from provided paths

4 views
Skip to first unread message

petrikvandervelde@gmail.com (JIRA)

unread,
Jan 25, 2017, 11:51:01 PM1/25/17
to jenkinsc...@googlegroups.com
Petrik van der Velde created an issue
 
Jenkins / Improvement JENKINS-41461
Provide configuration option to only get sources from provided paths
Issue Type: Improvement Improvement
Assignee: redsolo
Components: tfs-plugin
Created: 2017/Jan/26 4:50 AM
Priority: Major Major
Reporter: Petrik van der Velde

The TFS plugin currently allows excluding sources from given paths, however our source tree is very large and very active. New paths are added every day. The exclude / cloaking feature would allow us to exclude files / paths but if a new path is added then that path is pulled down in the next build even though it is not required. In our case it would be much more sensible to indicate to the TFS plugin which paths should be included and have it only get items from those paths.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

petrikvandervelde@gmail.com (JIRA)

unread,
Jan 25, 2017, 11:53:02 PM1/25/17
to jenkinsc...@googlegroups.com

petrikvandervelde@gmail.com (JIRA)

unread,
Jan 30, 2017, 5:46:01 PM1/30/17
to jenkinsc...@googlegroups.com
Petrik van der Velde commented on Improvement JENKINS-41461
 
Re: Provide configuration option to only get sources from provided paths

Olivier Dagenais if you can provide me with some pointers I could have a crack at creating a pull request for this. I'd need to know where to look in the source code to make this happen.

olivier.dagenais@gmail.com (JIRA)

unread,
Feb 20, 2017, 3:46:16 PM2/20/17
to jenkinsc...@googlegroups.com

serban.constantin+jenkins@gmail.com (JIRA)

unread,
Nov 12, 2019, 5:06:02 PM11/12/19
to jenkinsc...@googlegroups.com
Serban Constantin commented on Improvement JENKINS-41461
 
Re: Provide configuration option to only get sources from provided paths

Any updates on this, or where to start implementing it?

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

petrikvandervelde@gmail.com (JIRA)

unread,
Nov 12, 2019, 5:13:02 PM11/12/19
to jenkinsc...@googlegroups.com

I put in a PR in October 2017, that originally got merged but then pulled because of a failing test. I've put in this PR (https://github.com/jenkinsci/tfs-plugin/pull/196) last year and there has been no traction on it. We've been running the code in production but I don't have the time to keep chasing people to get it merged.

So in short, there is code, it's in my branch, it'll likely never get merged.

ian.williams1@telus.com (JIRA)

unread,
Nov 12, 2019, 5:22:02 PM11/12/19
to jenkinsc...@googlegroups.com

It seems the last release of any significance for the tfs-plugin was Mar 2018 (5.133.0). The 5.139.2 contained a one line fix and 5.157.0 contained an inaccurate documentation change to reflect the product's confusing new name. Is this Microsoft's way of telling us, go use GitHub ! ?

Reply all
Reply to author
Forward
0 new messages