v9.4.0

What's Changed

• remove deprecated compliance orb examples by @golonzovsky in #110
• Add tag parameter for executor maven_vm by @cesarfm in #112

Full Changelog: v9.3.0...v9.4.0

v9.3.0

What's Changed

• authenticate to dev-banana by @robert-nemet in #108
• empty commit to publich new version by @robert-nemet in #109

Full Changelog: v9.2.0...v9.3.0

update js_jest_runner_job

The --skipProject of the base script wasn't working correctly with typescript v5 making the whole jest pipeline fail

With this new minor version we can modify the script bind to this job withe the pre_test parameter

Usage:

 - ric-orb/js_jest_runner_job:
          name: quality_gate_jest_isomorphic
          script: ci:jest:isomorphic
>>>       pre_test: yarn ts-node --transpileOnly ./testing/ci.displayTestList.ts 
          globPattern: src/app/**/*.test.{jsx,tsx,js,ts}
          # resource_class: large means 4 vCPUs and 8GB ram
          # This is why we set --maxWorkers=3 (number of CPU minus 1 for the main thread)
          resource_class: large
          jest_options: --maxWorkers=3
          parallelism: 2
          requires:
            - setup

Jobs with js executor accepts `node_version` parameter

All jobs with js executor now accepts node_version optional parameter.

breaking change

The default value for js executor is now lts

Adding a working_directory parameter to the main jobs for Java deployments

This allows to expose the working_directory option from CircleCI for some jobs. We will add it to other jobs as needed.

build_push_image: Remove default Dockerfiles by language

This removes the functionality introduced in v7.6.0 as isopod is taking that responsibility, and the current way the build_push_image is set up will not allow it to work properly.

npm publish from build folder

⚠️ Breaking changes ⚠️

Only affects node apps.

• publishing npm modules is now done from ./build folder
• publishable app need to have ci:prepublish script which copy package.json to ./build folder

build_push_image: Add default Dockerfiles by language

With this addition, we can have "templates" of Dockerfiles for different languages, that will be fetched and used by CircleCI so they don't need to be present in the apps' repositories.
This makes sense because in 99% of the cases all our apps are using a fixed Dockerfile that we just copy around. So this should ease the rollout of newer versions of the Dockerfile.
Of course, it is still possible to provide a Dockerfile in the original app repo, if one exists that one will be used.

NOTE: if you want to use a Dockerfile from a template, you also need to remove the Dockerfile from your repository and add Dockerfile to the repo's .gitignore, to prevent Isopod from throwing a "working directory not clean" error.

CodeQL step: improving parameters

This release improves the codeql job by adding a memory_usage parameter for giving more memory to the process in case of big projects.

CodeQL fixes & improvements

This fixes a bug where it was assumed a bin directory exists in the home directory of the user. This is the case for any of the provided CircleCI docker images, but not for most other ones.

We now always provide a configuration file for CodeQL. The default one is now part of this repository.