Yes, that's the best push notification unless your git server provides Web
hooks which can provide the same capability.

Git providers with supported web hooks:

   - GitHub
   - Bitbucket
   - Gitea
   - GitLab

Others probably support them as well, but those I've seen mentioned in
various places.

On Mon, Mar 30, 2020 at 11:48 PM Andreas Tscharner <sternenfe...@gmail.com>
wrote:

> Hello World,
>
> We are in the process of updating Jenkins from version 2.150.3 to
> version 2.222.x.
> Our version control system is a git server which is in-house. Currently
> our "push notification" is an empty schedule for a "PollSCM" Build
> Trigger combined with a
> curl -s
> http://buildserver:8080/git/notifyCommit?url=git://
> <git-server>/<repo>'&'branches=$BRANCH
>
> Is this still the best practice of a "push notification" in version
> 2.222.x?
>
> TIA and best regards
>         Andreas
> --
> Andreas Tscharner                                 sternenfe...@gmail.com
> ------------------------------------------------------------------------
> Der entscheidende Vorteil eines Chats gegenueber einem normalen Telefon-
> anruf ist der, dass ersterer langsamer geht und mehr kostet (fuer den
> lebenswichtigen Austausch von Informationen wie "hya folks", "C U
> l8er" und ":-)") ...                       Aus Murphy's Computergesetzen
>
> --
> 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-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/48275ae9-a21d-596d-ac4e-7b82c8d05ea5%40gmail.com
> .
>

-- 
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFutBzUcqz05JVeUvLVyFaNON94-E%3D%3DaukZ06rqh5SceA%40mail.gmail.com.

Reply via email to