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

Add SOAP query to get web pages for MSBuild warnings

    • Icon: Improvement Improvement
    • Resolution: Won't Fix
    • Icon: Trivial Trivial
    • warnings-plugin
    • Platform: All, OS: All

      It would be nice if the warnings plugin could add links to MS web pages that
      contains information about a warning. The problem is that the only way is to do
      a SOAP query to a MS service. Ive logged this so I can store the SOAP
      communication somewhere.

        1. query.xml
          4 kB
        2. response.xml
          2 kB
        3. response.xml
          2 kB

          [JENKINS-1735] Add SOAP query to get web pages for MSBuild warnings

          redsolo created issue -

          redsolo added a comment -

          Created an attachment (id=262)
          SOAP query

          redsolo added a comment - Created an attachment (id=262) SOAP query

          redsolo added a comment -

          Created an attachment (id=263)
          SOAP response

          redsolo added a comment - Created an attachment (id=263) SOAP response

          redsolo added a comment -

          Created an attachment (id=264)
          SOAP response (2nd try)

          redsolo added a comment - Created an attachment (id=264) SOAP response (2nd try)

          redsolo added a comment -

          The problem is that they URL lookup can take a while (1sec) and it is not good
          to do it in the parsing. The SOAP query can be done with a simple HTTP POST, and
          it should not be hard to parse the response.

          How about the MSBuild scanner creates links to a method in the warnings plugin
          that takes the category id as parameter, then the method will query the MS
          service and return a valid URL. The browser is then relayed to the URL.

          This way it will not take longer to parse the console log, and the service
          lookup will only be done on request.

          What do you think?

          redsolo added a comment - The problem is that they URL lookup can take a while (1sec) and it is not good to do it in the parsing. The SOAP query can be done with a simple HTTP POST, and it should not be hard to parse the response. How about the MSBuild scanner creates links to a method in the warnings plugin that takes the category id as parameter, then the method will query the MS service and return a valid URL. The browser is then relayed to the URL. This way it will not take longer to parse the console log, and the service lookup will only be done on request. What do you think?

          Ulli Hafner added a comment -

          Changed priority.

          Ulli Hafner added a comment - Changed priority.
          Ulli Hafner made changes -
          Labels New: PR-appreciated
          Ulli Hafner made changes -
          Assignee Original: Ulli Hafner [ drulli ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 131808 ] New: JNJira + In-Review [ 173825 ]

          Microsoft has migrated C# and MSBuild documentation from msdn.microsoft.com to docs.microsoft.com. I don't think it would be a good idea to take a dependency on http://services.msdn.microsoft.com/search/service.asmx at this time, especially as it seems to be undocumented (unlike the MTPS Content Service).

          If the warnings plugin instead generated links to search URLs like https://docs.microsoft.com/en-us/search/?search=cs0168, I think that would be easy to implement and somewhat helpful.

          A public search API was also requested at https://msdocs.uservoice.com/forums/364242-site-feedback/suggestions/13867563-search-api but I don't know how soon Microsoft is going to implement that, and presenting the search results within Jenkins doesn't really seem to add value over just linking to Microsoft's search.

          Kalle Niemitalo added a comment - Microsoft has migrated C# and MSBuild documentation from msdn.microsoft.com to docs.microsoft.com. I don't think it would be a good idea to take a dependency on http://services.msdn.microsoft.com/search/service.asmx at this time, especially as it seems to be undocumented (unlike the MTPS Content Service ). If the warnings plugin instead generated links to search URLs like https://docs.microsoft.com/en-us/search/?search=cs0168 , I think that would be easy to implement and somewhat helpful. A public search API was also requested at https://msdocs.uservoice.com/forums/364242-site-feedback/suggestions/13867563-search-api but I don't know how soon Microsoft is going to implement that, and presenting the search results within Jenkins doesn't really seem to add value over just linking to Microsoft's search.

            Unassigned Unassigned
            redsolo redsolo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: