Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-48298

Pipeline builds don't trigger on VSTS commit notification until there is one successful build manually triggered first

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • tfs-plugin
    • None
    • Jenkins 2.92
      TFS Plugin 5.126.0

      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.

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

            Unassigned Unassigned
            dskdas Debasish Das
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: