Start multi-branch indexing from SCM notification

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Start multi-branch indexing from SCM notification

Daniel Becroft
Hi,

I have a multi-branch pipeline setup to initiate a branch indexing every X minutes, which works fine. However, I am trying to start that process from the command line via a post-commit hook.

For a normal job, I can use the /subversion/<uuid>/notifyCommit to tell Jenkins of a new commit, and it will start any jobs that require it. This doesn't seem to apply to the multi-branch jobs, though. I can only start a job by using /jobs/<job-nam>/build.

I could have multiple jobs that share a repository, and I would like to avoid having to manually list each job in the post-commit hook.

The polling also had the advantage of triggering downstream jobs when an external changed - is this possible with the branch indexing? (ie run branch indexing, if external changes then run the branch build)?
---
Daniel Becroft

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAJM0iSRaAFLfMDM6EoCFezBWHq26cMRFEfd5pq3hOPQfHm_yeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Start multi-branch indexing from SCM notification

stephenconnolly
Brack indexing is basically a smart polling, and *should* be triggered off scm notifications 

However Subversion has not been updated in multibranch support for a good while now. 

On Fri 7 Sep 2018 at 02:42, Daniel Becroft <[hidden email]> wrote:
Hi,

I have a multi-branch pipeline setup to initiate a branch indexing every X minutes, which works fine. However, I am trying to start that process from the command line via a post-commit hook.

For a normal job, I can use the /subversion/<uuid>/notifyCommit to tell Jenkins of a new commit, and it will start any jobs that require it. This doesn't seem to apply to the multi-branch jobs, though. I can only start a job by using /jobs/<job-nam>/build.

I could have multiple jobs that share a repository, and I would like to avoid having to manually list each job in the post-commit hook.

The polling also had the advantage of triggering downstream jobs when an external changed - is this possible with the branch indexing? (ie run branch indexing, if external changes then run the branch build)?
---
Daniel Becroft

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAJM0iSRaAFLfMDM6EoCFezBWHq26cMRFEfd5pq3hOPQfHm_yeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
--
Sent from my phone

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMxM2ggnjZ-hYLg08CMjOb_ZG9Y%2BgRpcAJAiQdHZ87D6Hg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Start multi-branch indexing from SCM notification

Jan Monterrubio
In reply to this post by Daniel Becroft
There’s a scan button on the UI, so maybe we can track down what endpoint that’s hitting and call that instead of notifyCommit? Would that do the trick? 

On Thu, Sep 6, 2018 at 20:42 Daniel Becroft <[hidden email]> wrote:
Hi,

I have a multi-branch pipeline setup to initiate a branch indexing every X minutes, which works fine. However, I am trying to start that process from the command line via a post-commit hook.

For a normal job, I can use the /subversion/<uuid>/notifyCommit to tell Jenkins of a new commit, and it will start any jobs that require it. This doesn't seem to apply to the multi-branch jobs, though. I can only start a job by using /jobs/<job-nam>/build.

I could have multiple jobs that share a repository, and I would like to avoid having to manually list each job in the post-commit hook.

The polling also had the advantage of triggering downstream jobs when an external changed - is this possible with the branch indexing? (ie run branch indexing, if external changes then run the branch build)?
---
Daniel Becroft

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAJM0iSRaAFLfMDM6EoCFezBWHq26cMRFEfd5pq3hOPQfHm_yeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CADgiF9KOvaqdaRVi8wHpGpiOdr%3DrfWCQv2Ha9KNUtOkd7x67eA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.