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

unable to install ATH on macos

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When installing the ATH on osx, some users see this type of error: 

      https://gist.github.com/sophistifunk/c73e0d635dac84d7d796559ae12c0dd7

       

      Installing the required dependencies on OSX is not documented (and past techniques don't seem to work on fresh installs). This seems required by nodegit only. 

       

      Nodegit has also been a problem (see Vivek Pandey) with failures with signatures (still trying to get the specific error message for that). Nodegit is presumably used to test multibranch (the equivalent in unit test code doesn't have this problem, it also uses a git client but doesn't seem as problematic as nodegit). Perhaps nodegit should be replaced with direct calls to the git client via shell scripting (given that seems to be mostly what it does anyway). 

       

       

        Attachments

          Activity

          Hide
          tfennelly Tom FENNELLY added a comment - - edited

          Has anyone (that has had this problem) tried the obvious things of:

          1. Updating the dependency version of nodegit.
          2. Updating the version of git installed on the host machine.
          3. Manually adding logs in the failing preinstall script in an effort to get a better idea of why it's failing.
          Show
          tfennelly Tom FENNELLY added a comment - - edited Has anyone (that has had this problem) tried the obvious things of: Updating the dependency version of nodegit. Updating the version of git installed on the host machine. Manually adding logs in the failing preinstall script in an effort to get a better idea of why it's failing.
          Hide
          tfennelly Tom FENNELLY added a comment - - edited

          In Vivek's case, it was because nodegit was not able to parse his ~/.gitconfig to get the user details. It didn't like the format being used by the email config - in his case, it was wrapped in angle brackets e.g. "<vivek@cloudbees.com>" or whatever.

          Show
          tfennelly Tom FENNELLY added a comment - - edited In Vivek's case, it was because nodegit was not able to parse his ~/.gitconfig to get the user details. It didn't like the format being used by the email config - in his case, it was wrapped in angle brackets e.g. "<vivek@cloudbees.com>" or whatever.
          Hide
          michaelneale Michael Neale added a comment -

          Tom fixed it!

          Show
          michaelneale Michael Neale added a comment - Tom fixed it!

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            michaelneale Michael Neale
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: