AW: Pipeline SCM trigger breaks

[Stefan.R...@tk.de]

Hi everyone,

 

does anyone know, how I can get more information about the internal state of the Jenkins Git Plugin, especially the mapping from repositories/branches to pipelines, that need to be triggered on SCM changes?

Are there classes, that I can add to a log recorder, files in Jenkins Home, anything?

 

Thanks!

Stefan

 

Von: jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] Im Auftrag von Stefan.R...@tk.de
Gesendet: Donnerstag, 14. Mai 2020 16:47
An: jenkins...@googlegroups.com
Betreff: [SPAM-Verdacht] Pipeline SCM trigger breaks

 

Hi,

 

I have configured a multibranch pipeline (declarative), which checks out several git repositories and has pollSCM('') configured:

 

I deleted and recreated the build for branch 'int'. The first two builds were triggered by branch indexing and manually by me.

The 'Git Polling Log' from yesterday shows "Changes found" at the end of the polling log.

Build #3 was successfully triggered yesterday, right after polling had run.

 

Nothing changed in the meantime, but since then all calls to

https://jenkins.dst.tk-inline.net:8181/git/notifyCommit?url=https://github.tk-online.net/TKeasy/arbeitgeberbeitrag&branches=int

('TKeasy/arbeitgeberbeitrag' is one of the repositories, that were checked out by the pipeline and polled for changes)

don't trigger a new polling.

Instead I get

No git jobs using repository: https://github.tk-online.net/TKeasy/arbeitgeberbeitrag and branches: int

No Git consumers using SCM API plugin for: https://github.tk-online.net/TKeasy/arbeitgeberbeitrag

 

"View Configuration" shows, that "poll SCM" is still checked.

 

Logging output shows no "Triggering the polling of…", after

Received notification from 10.252.62.17 ⇒ https://jenkins.dst.tk-inline.net:8181/git/notifyCommit for uri = https://github.tk-online.net/TKeasy/arbeitgeberbeitrag ; sha1 = null ; branches = [int]

 

For other branches, the polling is triggered successfully.

 

Does anyone have a hint, how to trace down the cause of this issue further?

 

Thanks and best regards

Stefan

 

 

--
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/27e93ee328da4e66962363082d3afd7f%40tk.de.

[Jan Monterrubio]

https://github.com/jenkinsci/git-plugin

The plugin lives there, so probably adding loggers to its root packages might give you some info. 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/82617e38e6054d278da143aa4ba6525a%40tk.de.