Zum Hauptinhalt springen

Configuring NPM registry

Overview​

Note: Starting from Jutro 10.9, only official releases will be made available to external consumers.

Because of that, we introduced a new internal-only npm repository which will still contain all the official releases as well as the latest RC artifacts.

With that in mind, in the external Binrepo (jutro-npm-dev-local), you can expect only versions related to the ski releases, which are expected to be released every 4 months and becoming exposed through binrepos only during the GW’s official ski GA dates.

How it works?​

This flowchart illustrates what and where is being published as part of the Jutro release.

binrepo-v1.png

All internal consumers are highly encouraged to switch to the new internal-only Binrepo as part of the continuous development and testing workflow.

What are the benefits of using the internal Binrepo?​

  • It contains all RC releases which is useful in order to facilitate the adoption of new features to prepare for the ski release timeline.
  • It provides access to ski releases ahead of the official release dates. For example, the 10.7 release was generated in early May, but its GA date is August 1st.
  • It contains all the official versions as well as the latest RCs as part of the Binrepo distributions.

Which one to use LHS or RHS?​

  • Use LHS for standard development where you just want to have access to the latest versions of the JDP.
  • Use RHS for replicating the external customer environment. It is mostly for teams working as customers from the Guidewire tenant.
Warning: Remember that you need to deliver an external Binrepo npm configuration when publishing your application to external customers. Make sure the version of Jutro used by the app is actually available from the external binrepo before publishing your app to external customers.

Example workflow​

  1. Use the internal Binrepo for development, testing, and daily integration checks.
  2. Perform your daily checks, automation tests, and any similar checks on any version you want before it is released to external customers. For example, you may want to run tests on the latest RC versions to check ahead whether some unexpected changes are about to be released.
  3. Switch to External Binrepo when publishing your application to external customers so their applications point to the externally available Binrepo.