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

No automated build is started in Jenkins after Perforce trigger

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: p4-plugin
    • Labels:
    • Environment:
      Jenkins (2.263.1 to 2.277.3)
      p4 1.11.1
    • Similar Issues:

      Description

      Maybe i just describe our flow:

      • VisualStudio on developper machine to make code changes
      • Perforce client on dev. machine to submit the change
      • Goes to perforce server
      • From there to Jenkins build server
      • Starts the build after  perforce trigger

      This last step doesn't occur (probably) since last Friday (23rd of April).

      I went on PTO on Wednesday until Monday (26th of April) and from there on i realized some issues. Therefore i started our bat-file by hand which starts Jenkins. But this window cause a perforce lock and i closed it. Afterwards i updated some plugins and Jenkins itself - from 2.263.1 to 2.277.3). Checked with our IT but there was no policy change or something in the firewalls which could cause this behavior. I am sure it isn't much of an error, may just a config value that i missed or forgot? Maybe you can point me to the right direction.

       

      Best Regard,

      Thorben Seibert

        Attachments

          Activity

          Hide
          p4karl Karl Wirth added a comment -

          Hi Thorben - Can you please send an email to support@perforce.com containing your 'p4 info', trigger definition and contents of the trigger. Do you see any error messages in the P4D log file?

           

          Note - If Jenkins requires security the API token may have changed/expired. If Jenkins uses HTTPS then you may need to install a new certificate on the Perforce server or get your trigger to ignore certificate checks.

          Show
          p4karl Karl Wirth added a comment - Hi Thorben - Can you please send an email to support@perforce.com containing your 'p4 info', trigger definition and contents of the trigger. Do you see any error messages in the P4D log file?   Note - If Jenkins requires security the API token may have changed/expired. If Jenkins uses HTTPS then you may need to install a new certificate on the Perforce server or get your trigger to ignore certificate checks.

            People

            Assignee:
            p4karl Karl Wirth
            Reporter:
            thorben_seibert Thorben
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated: