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

Evergreen instance fails to start with "sh: tsc: not found" error

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Fixed
    • Component/s: evergreen
    • Labels:
      None
    • Similar Issues:

      Description

      Problem statement

      Following the official documentation, and running

      docker volume create jenkins-evergreen-data && \
      docker pull jenkins/evergreen:docker-cloud && \
      docker run --name evergreen \
          --restart=always \
          -ti \
          -p 8080:80 \
          -v /var/run/docker.sock:/var/run/docker.sock \
          -v jenkins-evergreen-data:/evergreen/data \
          -e LOG_LEVEL=debug \
          jenkins/evergreen:docker-cloud
      

      The client fails with to start with the following error :

      > evergreen-client@1.0.0 prestart /evergreen/client
      > tsc
      
      sh: tsc: not found
      npm ERR! file sh
      npm ERR! code ELIFECYCLE
      npm ERR! errno ENOENT
      npm ERR! syscall spawn
      npm ERR! evergreen-client@1.0.0 prestart: `tsc`
      npm ERR! spawn ENOENT
      npm ERR! 
      npm ERR! Failed at the evergreen-client@1.0.0 prestart script.
      npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
      

      Expected behavior

      The Evergreen instance should be able to come with a ready to use Jenkins.

      It seems like there recent js->typescript migration is responsible for this.
      But then we want to understand why our CI did let that go green :-\.

        Attachments

          Issue Links

            Activity

            batmat Baptiste Mathus created issue -
            batmat Baptiste Mathus made changes -
            Field Original Value New Value
            Description h3. Problem statement

            Following the official documentation, and running

            {noformat}
            docker volume create jenkins-evergreen-data && \
            docker pull jenkins/evergreen:docker-cloud && \
            docker run --name evergreen \
                --restart=always \
                -ti \
                -p 8080:80 \
                -v /var/run/docker.sock:/var/run/docker.sock \
                -v jenkins-evergreen-data:/evergreen/data \
                -e LOG_LEVEL=debug \
                jenkins/evergreen:docker-cloud
            {noformat}

            The client fails with to start with the following error :
            batmat Baptiste Mathus made changes -
            Description h3. Problem statement

            Following the official documentation, and running

            {noformat}
            docker volume create jenkins-evergreen-data && \
            docker pull jenkins/evergreen:docker-cloud && \
            docker run --name evergreen \
                --restart=always \
                -ti \
                -p 8080:80 \
                -v /var/run/docker.sock:/var/run/docker.sock \
                -v jenkins-evergreen-data:/evergreen/data \
                -e LOG_LEVEL=debug \
                jenkins/evergreen:docker-cloud
            {noformat}

            The client fails with to start with the following error :
            h3. Problem statement

            Following the official documentation, and running

            {noformat}
            docker volume create jenkins-evergreen-data && \
            docker pull jenkins/evergreen:docker-cloud && \
            docker run --name evergreen \
                --restart=always \
                -ti \
                -p 8080:80 \
                -v /var/run/docker.sock:/var/run/docker.sock \
                -v jenkins-evergreen-data:/evergreen/data \
                -e LOG_LEVEL=debug \
                jenkins/evergreen:docker-cloud
            {noformat}

            The client fails with to start with the following error :

            {noformat}
            > evergreen-client@1.0.0 prestart /evergreen/client
            > tsc

            sh: tsc: not found
            npm ERR! file sh
            npm ERR! code ELIFECYCLE
            npm ERR! errno ENOENT
            npm ERR! syscall spawn
            npm ERR! evergreen-client@1.0.0 prestart: `tsc`
            npm ERR! spawn ENOENT
            npm ERR!
            npm ERR! Failed at the evergreen-client@1.0.0 prestart script.
            npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
            {noformat}

            h3. Expected behavior

            The Evergreen instance should be able to come with a ready to use Jenkins.

            It seems like there recent js->typescript migration is responsible for this.
            But then we want to understand why our CI did let that go green :-\.
            rtyler R. Tyler Croy made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            rtyler R. Tyler Croy made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            rtyler R. Tyler Croy made changes -
            Remote Link This issue links to "#309 (Web Link)" [ 21905 ]
            rtyler R. Tyler Croy made changes -
            Resolution Fixed [ 1 ]
            Status In Review [ 10005 ] Resolved [ 5 ]
            Hide
            batmat Baptiste Mathus added a comment -

            Confirmed to be fixed by running from the fresh latest built public image. Thanks Tyler !

            Show
            batmat Baptiste Mathus added a comment - Confirmed to be fixed by running from the fresh latest built public image. Thanks Tyler !

              People

              Assignee:
              rtyler R. Tyler Croy
              Reporter:
              batmat Baptiste Mathus
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: