Skip to content

Infragistics Community Forum / Web / Ignite UI for Angular / Deploying application to Azure DevOps

Deploying application to Azure DevOps

New Discussion
Chris Sworen
Chris Sworen asked on Jun 15, 2021 7:47 AM

I am attempting to deploy my working version to an Azure DevOps hosting site and I am getting the following error:

14292 error code E404
14293 error 404 Not Found - GET https://registry.npmjs.org/@infragistics%2figniteui-angular - Not found
14294 error 404
14295 error 404 '@infragistics/igniteui-angular@12.0.3' is not in the npm registry.
14296 error 404 You should bug the author to publish it (or use the name yourself!)
14297 error 404 It was specified as a dependency of 'UI'
14298 error 404 Note that you can also install from a
14299 error 404 tarball, folder, http url, or git url.
14300 verbose exit [ 1, true ]

##[error]Error: Npm failed with return code: 1

Is there something I need to add to the YML/TF scripts for the build pipeline in order to access the paid subscription so my build goes through properly? I remember having to set a build variable in NPM for my local but I can’t find the page and I don’t remember it saying anything about applying the same changes to an automated build location.

Sign In to post a reply

Replies

  • 0
    Anastas Staev
    Anastas Staev answered on Jun 11, 2021 6:11 AM

    Looking at the error that you are getting, it seems that you are missing the configuration for our private repository. We have an article which you can refer to for more details how to setup your Azure DevOps build – https://www.infragistics.com/products/ignite-ui-angular/angular/components/general/ignite-ui-licensing#azure-pipelines-configuration.

    Please let me know whether I can assists you with anything else on the matter.

    • 0
      Chris Sworen
      Chris Sworen answered on Jun 11, 2021 5:18 PM

      I have integrated the steps and variables as specified and am still getting errors:

      14884 verbose stack Error: 404 Not Found - GET https://registry.npmjs.org/@infragistics%2figniteui-angular - Not found
      14884 verbose stack     at /opt/hostedtoolcache/node/12.22.1/x64/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:117:15
      14884 verbose stack     at runMicrotasks ()
      14884 verbose stack     at processTicksAndRejections (internal/process/task_queues.js:97:5)
      14885 verbose statusCode 404
      14886 verbose pkgid @infragistics/igniteui-angular@12.0.3
      14887 verbose cwd /home/vsts/work/1/s/UI
      14888 verbose Linux 5.8.0-1033-azure
      14889 verbose argv "/opt/hostedtoolcache/node/12.22.1/x64/bin/node" "/opt/hostedtoolcache/node/12.22.1/x64/bin/npm" "install"
      14890 verbose node v12.22.1
      14891 verbose npm  v6.14.12
      14892 error code E404
      14893 error 404 Not Found - GET https://registry.npmjs.org/@infragistics%2figniteui-angular - Not found
      14894 error 404
      14895 error 404 '@infragistics/igniteui-angular@12.0.3' is not in the npm registry.
      14896 error 404 You should bug the author to publish it (or use the name yourself!)
      14897 error 404 It was specified as a dependency of 'UI'
      14898 error 404 Note that you can also install from a
      14899 error 404 tarball, folder, http url, or git url.
      14900 verbose exit [ 1, true ]
      
      ##[error]Error: Npm failed with return code: 1
      Finishing: npm install
      

      I am directly injecting the variables (blocking IG token below) in my ui-pipelines.yml:

      # Starter pipeline
      # Start with a minimal pipeline that you can customize to build and deploy your code.
      # Add steps that build, run tests, deploy, and more:
      # https://aka.ms/yaml
      
      trigger:
       branches:
         include:
           - master
       paths:
         include:
           - UI/*
      
      pool:
        vmImage: 'ubuntu-latest'
      
      steps:
      - script: npm config set @infragistics:registry https://packages.infragistics.com/npm/js-licensed/
        displayName: 'Npm add registry'
      
      - script: npm config set //packages.infragistics.com/npm/js-licensed/:always-auth=true
        displayName: 'Npm config'
      
      - script: npm config set //packages.infragistics.com/npm/js-licensed/:_auth=***************************************
        displayName: 'Npm config auth'
        
      - task: NodeTool@0
        displayName: 'Use Node 12.x'
        inputs:
          versionSpec: '12.x'
      
      - task: Npm@1
        displayName: 'Angular CLI'
        inputs:
         command: custom
         workingDir: UI
         verbose: false
         customCommand: 'install -g @angular/cli@latest'
      
      - task: Npm@1
        displayName: 'npm install'
        inputs:
         command: install
         workingDir: UI
      
      - task: Npm@1
        displayName: 'Build'
        inputs:
         command: custom
         workingDir: UI
         verbose: false
         customCommand: 'run build'
      
      - task: ArchiveFiles@2
        inputs:
          rootFolderOrFile: '$(Build.SourcesDirectory)/UI/dist/commits'
          includeRootFolder: false
          archiveType: 'zip'
          archiveFile: '$(Build.ArtifactStagingDirectory)/$(Build.BuildId).zip'
          replaceExistingArchive: true
      
      - task: PublishBuildArtifacts@1
        inputs:
          PathtoPublish: '$(Build.ArtifactStagingDirectory)'
          ArtifactName: 'drop'
          publishLocation: 'Container'

      Can you please tell me why it's still failing?

      • 0
        Anastas Staev
        Anastas Staev answered on Jun 14, 2021 3:41 PM

        The error indicates that the npm is still not configured and when installing our package, npm still searches it under the npmjs.org repo(GET https://registry.npmjs.org/@infragistics….). You can check the .npmrc file after the configuration steps by outputting it with npm list command. You can try to update the .npmrc file by redirecting the output with "TEXT" >> ~/.npmrc.
        Another thing is to check whether you have a local .npmrc file per your project, which "shadows" the global one which has been updated with above steps. 

      • 0
        Anastas Staev
        Anastas Staev answered on Jun 15, 2021 7:47 AM

        I'm glad that you were able to configure your Azure pipeline to install our @infragistics/igniteui-angular package.

  • You must be logged in to reply to this topic.
Discussion created by
Favorites
Replies
Created On
Last Post
Discussion created by
Chris Sworen
Favorites
0
Replies
4
Created On
Jun 15, 2021
Last Post
4 years, 11 months ago

Suggested Discussions

Created by

Created on

Jun 15, 2021 7:47 AM

Last activity on

Feb 18, 2026 2:12 PM