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

The Jabber plugin prevents the end of the build

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • jabber-plugin
    • None
    • Platform: All, OS: All

    Description

      since version 0.9 of the Hudson Jabber notifier plugin
      my build do not complete, they stop on jabber notification, either on manually
      entered targets or on scm suspects.

      nothing shows up in logs, and the build can't be stopped from hudson interface.
      killing their processes does not work either since there is no process to kill.

      so i end up having to restart hudson.

      Details :
      we're using an internal jabber server, and our organization is using a proxy,
      but to connect to the jabber server, the proxy is not needed.

      example of logs :
      after build :
      Sending notification to: javabuild-status@f4-group.com

      in hudson.log :
      INFO: $PROJECT_NAME$ #441 main build action completed: SUCCESS

      if i disable the jabber plugin, everything works fine.

      Attachments

        1. stack.full
          53 kB
        2. stack.light
          42 kB

        Activity

          cactusbone cactusbone added a comment -

          it works ! thanks

          cactusbone cactusbone added a comment - it works ! thanks
          cactusbone cactusbone added a comment -

          yup, the stuck builds were indeed aborted
          i updated, i'll close tomorrow if it's ok

          thanks for the quick fix !

          cactusbone cactusbone added a comment - yup, the stuck builds were indeed aborted i updated, i'll close tomorrow if it's ok thanks for the quick fix !
          kutzi kutzi added a comment -

          I assume that the previous build in the cases where Hudson did lock up was an
          aborted (or 'not_build') build?

          In that case, it is fixed in 0.10

          kutzi kutzi added a comment - I assume that the previous build in the cases where Hudson did lock up was an aborted (or 'not_build') build? In that case, it is fixed in 0.10
          cactusbone cactusbone added a comment -

          on a sidenote, i did not receive mails for those stuck builds, so it might be the
          mail plugin that's failing. it is possible the suffix feature impacts the mail
          sending ? (or it might simply be that mails are sent after the jabber plugin
          returns)

          cactusbone cactusbone added a comment - on a sidenote, i did not receive mails for those stuck builds, so it might be the mail plugin that's failing. it is possible the suffix feature impacts the mail sending ? (or it might simply be that mails are sent after the jabber plugin returns)
          cactusbone cactusbone added a comment -

          just to confirm :
          this line : SEVERE: Some error ! Simple ping failed , hresult: 1912 doesn't appear
          anymore, but the builds still get stuck. (I restarted hudson)

          seems like this is linked to the Default Suffix feature. (because without a
          specified suffix, it works well)

          both users in the previous log have a Jabber ID specified.

          cactusbone cactusbone added a comment - just to confirm : this line : SEVERE: Some error ! Simple ping failed , hresult: 1912 doesn't appear anymore, but the builds still get stuck. (I restarted hudson) seems like this is linked to the Default Suffix feature. (because without a specified suffix, it works well) both users in the previous log have a Jabber ID specified.

          People

            kutzi kutzi
            cactusbone cactusbone
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: