You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a set up where we have 1 git repo with many subdirs and many jenkins projects.
For example:
gitrepo/
proj1/
proj2/
proj3/
proj1, proj2 and proj3 are independent applications and built independently.
The current jenkins setup we have for them is using jenkins scm includedRegions and git plugin's sparsepath we can effectively treat proj1, proj2 and proj3 as separate repos. This means that with the usual jenkins notifyCommit jenkins will only build proj1 if proj1 has changed.
We'd really like to use build_now with this scm/git feature but right now it will indiscriminately fire a change (commits on proj2 will cause an unnecessary build of proj1).
As you suppose, the information sent is enough. I'm not sure about your detailed project setup, but I'm afraid that the point is that the plugin does not currently behaves as a Jenkins trigger, and that basically means that none of the advanced items from git plugin (such as skipping commits from some authors or paths). I have some work in a experimental branch that could extend the plugin in that sense, so if you are interested I can try to wrap it up so that you can test if it is enough for your needs or at least use as starting point for developing that functionality.
We have a set up where we have 1 git repo with many subdirs and many jenkins projects.
For example:
proj1, proj2 and proj3 are independent applications and built independently.
The current jenkins setup we have for them is using jenkins scm includedRegions and git plugin's sparsepath we can effectively treat proj1, proj2 and proj3 as separate repos. This means that with the usual jenkins notifyCommit jenkins will only build proj1 if proj1 has changed.
We'd really like to use build_now with this scm/git feature but right now it will indiscriminately fire a change (commits on proj2 will cause an unnecessary build of proj1).
My initial readings of the gitlab docs (https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/web_hooks/web_hooks.md) suggest we do get posted enough information to do this. Is this something you'd consider developing or consider a pull request for?
Thanks
The text was updated successfully, but these errors were encountered: