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

Plugin hangs - reproduced with failed earlier build (Praqma case 12906)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • None
    • pretested integration plugin 2.2.1
      Linux Ubuntu 14.04 slave, master Linux Ubuntu 14.04.
      jenkins core 1.605

      Example of console log:

      Started by user Jenkins Admin
      [EnvInject] - Loading node environment variables.
      Building remotely on jenkins-training-linux-slave (linux) in workspace /home/praqma/.jenkins/workspace/bpe.roadshow.verify
       > git rev-parse --is-inside-work-tree # timeout=10
      Fetching changes from the remote Git repository
       > git config remote.origin.url https://github.com/buep/roadshow.git # timeout=10
      Fetching upstream changes from https://github.com/buep/roadshow.git
       > git --version # timeout=10
      using .gitcredentials to set credentials
       > git config --local credential.helper store --file=/tmp/git6460479601874649810.credentials # timeout=10
       > git -c core.askpass=true fetch --tags --progress https://github.com/buep/roadshow.git +refs/heads/*:refs/remotes/origin/*
       > git config --local --remove-section credential # timeout=10
      Seen branch in repository origin/master
      Seen branch in repository origin/ready/buep
      Seen 2 remote branches
      Checking out Revision 8b7d9910d213bf7e235beb528bfd416d0941a168 (origin/ready/buep)
       > git config core.sparsecheckout # timeout=10
       > git checkout -f 8b7d9910d213bf7e235beb528bfd416d0941a168
       > git rev-list 8b7d9910d213bf7e235beb528bfd416d0941a168 # timeout=10
      2.2.1 (63b83)
      

      jobs just hangs here...

      How to reproduce

      The situation is reproduceable every time (tried three times) after the problem reported in JENKINS-27515.

      After a successful job, that by an error is successful, I fixed the credentials to enable the job to push.
      When building manually after the configuration change the same branch is picked up again (correct, as it isn't deleted remotely), but the plugin hangs just after printing version number.

      A similar problem was reported in JENKINS-27328 but not reproduced.

      After the problem described above, the slave is killed (slave process) and master restarted. The situation can then be recreated after reboot.

            bue Bue Petersen
            bue Bue Petersen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: