• Type: Bug
• Resolution: Unresolved
• Priority: Critical
• Component/s: tfs-plugin
• Labels:

  None
• Environment:

  Jenkins 2.92
  TFS Plugin 5.126.0

[JENKINS-48298] Pipeline builds don't trigger on VSTS commit notification until there is one successful build manually triggered first

Debasish Das created issue - 2017-11-29 18:12

Debasish Das made changes - 2017-11-29 18:14

Description

Original: We have TFS commit notifications setup to push to a Jenkins service hook and rely on TFS plugin's push trigger option to trigger the jenkins job. The notification is able to trigger freestyle projects fine. However for pipeline projects auto-triggering only works after i have manually build the pipeline project successfully first. Additionally the pipeline project has to be successfully built for a repo url and credential combination. We found this recently when we had to change from ssh:// url to https:// repo url.

New: We have TFS commit notifications setup to push to a Jenkins service hook and rely on TFS plugin's push trigger option to trigger the jenkins job. UPDATE: we specify the Jenkinsfile from GIT SCM. The notification is able to trigger freestyle projects fine. However for pipeline projects auto-triggering only works after i have manually build the pipeline project successfully first. Additionally the pipeline project has to be successfully built for a repo url and credential combination. We found this recently when we had to change from ssh:// url to https:// repo url.

Ian Williams made changes - 2021-09-12 09:00

Assignee

Original: redsolo [ redsolo ]