Switched over to to dedicated NodeJS container build environment

.devcontainer/devcontainer.json

@@ -0,0 +1,22 @@
+// For format details, see https://aka.ms/devcontainer.json. For config options, see the
+// README at: https://github.com/devcontainers/templates/tree/main/src/javascript-node
+{
+	"name": "Node.js",
+	// Or use a Dockerfile or Docker Compose file. More info: https://containers.dev/guide/dockerfile
+	"image": "mcr.microsoft.com/devcontainers/javascript-node:1-22-bookworm"
+
+	// Features to add to the dev container. More info: https://containers.dev/features.
+	// "features": {},
+
+	// Use 'forwardPorts' to make a list of ports inside the container available locally.
+	// "forwardPorts": [],
+
+	// Use 'postCreateCommand' to run commands after the container is created.
+	// "postCreateCommand": "yarn install",
+
+	// Configure tool-specific properties.
+	// "customizations": {},
+
+	// Uncomment to connect as root instead. More info: https://aka.ms/dev-containers-non-root.
+	// "remoteUser": "root"
+}

.devcontainer/noop.txt

@@ -0,0 +1,3 @@
+This file copied into the container along with environment.yml* from the parent
+folder. This file is included to prevents the Dockerfile COPY instruction from 
+failing if no environment.yml is found.

Jenkinsfile

@@ -1,40 +1,34 @@
 pipeline {
-    agent any
+    agent {
+        kubernetes {
+            cloud 'rsys-devel'
+            defaultContainer 'nodejs'
+            inheritFrom 'nodejs'
+        }
+    }
+
     stages {
         stage("install") {
             steps {
-                sh 'mamba env update --file environment.yml'
-                sh 'echo "mamba activate webdev" >> ~/.bashrc'
-                sh 'node --version && npm --version'
                 sh 'npm install'
             }
         }
         stage("test") {
             steps {
-                sh '''
+                sh 'npm run test:junit'
-                source ~/.bashrc
+                recordCoverage(tools: [[parser: 'JUNIT', pattern: 'junit/*.xml']])
-                npm run test:junit
-                '''
-                junit 'junit/*.xml'
             }
         }
         stage("build") {
             steps {
-                sh '''
+                sh 'npm run build:prod'
-                source ~/.bashrc
+                archiveArtifacts artifacts: 'dist/audioshowkit.js', fingerprint: true, followSymlinks: false, onlyIfSuccessful: true
-                npm run build:prod
-                '''
-                fingerprint "dist/**"
-                archiveArtifacts artifacts: 'dist/audioshowkit.js', followSymlinks: false
             }
         }
         stage("generate docs") {
             steps {
-                sh '''
+                sh 'npm run docs'
-                source ~/.bashrc
+                publishHTML([allowMissing: false, alwaysLinkToLastBuild: true, keepAll: true, reportDir: './docs', reportFiles: 'index.html', reportName: 'Documentation', reportTitles: ''])
-                npm run docs
-                '''
-                publishHTML([allowMissing: false, alwaysLinkToLastBuild: true, keepAll: true, reportDir: './docs', reportFiles: 'index.html', reportName: 'AudioShowKit Docs', reportTitles: ''])
             }
         }
     }

README.md

@@ -4,7 +4,7 @@ A library that makes visualizing audio data live a much simpler process.
 
 ## Getting Started
 
-As this library has not been published as a package, the best way to use it is to go to download the latest successful build artifact which can be [found here](https://dev.sys.reslate.xyz/dev-auto/job/AudioShowKit/job/master/). This build artifact is a minified and bundled version of all the components in the library.
+As this library has not been published as a package, the best way to use it is to go to download the latest successful build artifact which can be [found here](https://sys.reslate.net/rho/ci/job/projects-reslate/job/audioshowkit/job/master/). This build artifact is a minified and bundled version of all the components in the library.
 
 From here, add the downloaded javascript bundle to your html as you would any other javascript file:
 ```
@@ -13,6 +13,6 @@ From here, add the downloaded javascript bundle to your html as you would any ot
 
 Now, any script that is loaded after the `audioshowkit.js` script loads will have access to the `audioshowkit` object. Prepared are three tutorials with demonstrations. I recommend starting with the Music Playlist tutorial.
 
-## Documentation
+## Resources
 
-[The documentation can be found here](https://dev.sys.reslate.xyz/dev-auto/job/AudioShowKit/job/master/AudioShowKit_20Docs/) along with the rest of the tutorials and demonstrations.
+The documentation along with latest stable build [can be found here](https://sys.reslate.net/rho/ci/job/projects-reslate/job/audioshowkit/job/master/). The documentation is accessible to on the left bar and the build artifact can be downloaded as a zip.

environment.yml

@@ -1,16 +1,12 @@
-name: webdev
+name: audioshowkit
 channels:
   - conda-forge
 dependencies:
-  - _libgcc_mutex=0.1=conda_forge
+  - ca-certificates
-  - _openmp_mutex=4.5=2_gnu
+  - icu
-  - ca-certificates=2022.9.24=ha878542_0
+  - libuv
-  - icu=70.1=h27087fc_0
+  - libzlib
-  - libgcc-ng=12.2.0=h65d4601_19
+  - nodejs=20
-  - libgomp=12.2.0=h65d4601_19
+  - openssl
-  - libstdcxx-ng=12.2.0=h46fd767_19
+  - zlib
-  - libuv=1.44.2=h166bdaf_0
+prefix: ./env
-  - libzlib=1.2.13=h166bdaf_4
-  - nodejs=18.12.1=h8839609_0
-  - openssl=3.0.7=h166bdaf_0
-  - zlib=1.2.13=h166bdaf_4