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

Review: support swarm's update url

XMLWordPrintable

      Latest Swarm suggests use of the update parameter in the review/build to show running and some (hopefully) meaningful message(s).

      The "update" (instead of pass and fail) also as formatted in JSON in the body of the POST request. Test status: valid test status values are running, pass, and fail. Messages: you can pass a maximum 10 messages, if you provide more than 10 messages only the first 10 are saved. 

      See https://www.perforce.com/manuals/swarm/Content/Swarm/admin.integrate_test_suite.html?Highlight=update

       

       

          [JENKINS-62115] Review: support swarm's update url

          Joel Brown created issue -
          Joel Brown made changes -
          Labels New: P4_VERIFY.

          Pinned by Dhaval

          Karl Wirth added a comment -

          Have had a request for this so pinging it.

          Karl Wirth added a comment - Have had a request for this so pinging it.
          Karl Wirth made changes -
          Link New: This issue is duplicated by JENKINS-49843 [ JENKINS-49843 ]

          Michael Rose added a comment -

          We are in the process of upgrading our Perforce and Swarm servers and came across this issue. For our needs, I think it would be sufficient for the update field to mean that the Jenkins job will handle all callbacks instead of the plugin doing it. That was my interpretation of what the Swarm documentation said. I went through and updated the Jenkins job to do additional http POST requests when the "update" parameter is set only to find that the field is never passed on to the job.

          Michael Rose added a comment - We are in the process of upgrading our Perforce and Swarm servers and came across this issue. For our needs, I think it would be sufficient for the update field to mean that the Jenkins job will handle all callbacks instead of the plugin doing it. That was my interpretation of what the Swarm documentation said. I went through and updated the Jenkins job to do additional http POST requests when the "update" parameter is set only to find that the field is never passed on to the job.

          Michael Rose added a comment -

          However, if you wanted to implement a function that we can send arbitrary message to that would hand the POST request, even better.

          Michael Rose added a comment - However, if you wanted to implement a function that we can send arbitrary message to that would hand the POST request, even better.
          Joel Brown made changes -
          Assignee New: Joel Brown [ joel_brown ]
          Karl Wirth made changes -
          Labels Original: P4_VERIFY. New: P4_A P4_VERIFY.
          Karl Wirth made changes -
          Link New: This issue is duplicated by JENKINS-73473 [ JENKINS-73473 ]

          Karl Wirth added a comment -

          Devs - Please see JENKINS-73473

          Karl Wirth added a comment - Devs - Please see JENKINS-73473

            joel_brown Joel Brown
            joel_brown Joel Brown
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: