Merge pull request #150 from 18F/master

Merge 10x Milestone 6

Author: danielnaab

.github/workflows/create-release.yml

@@ -0,0 +1,31 @@
+name: Build release artifact
+on:
+  push:
+    tags:
+      - "*"
+jobs:
+  build-release:
+    runs-on: ubuntu-latest
+
+    steps:
+      # Check-out the repository under $GITHUB_WORKSPACE
+      - uses: actions/checkout@v2
+
+      - name: Read Node version from .nvmrc
+        run: echo "##[set-output name=NVMRC;]$(cat .nvmrc)"
+        id: nvm
+
+      - uses: actions/setup-node@v2.3.0
+        with:
+          node-version: ${{ steps.nvm.outputs.NVMRC }}
+
+      # Initialize workspace with git submodules and build a release
+      - name: Build release
+        run: make init build
+
+      # Create a release corresponding to the triggered tag
+      - uses: ncipollo/release-action@v1
+        with:
+          allowUpdates: true
+          artifacts: dist/validations/ssp.xsl
+          token: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -9,5 +9,4 @@ src/validations/report
 src/validations/src/ssp.xsl
 src/validations/target
 src/validations/test/*
-src/validations/ui/coverage/
 utils

.nvmrc

@@ -1 +1 @@
-v16.2.0
+v16.4.0

Makefile

@@ -0,0 +1,70 @@
+REQUIRED_NODE_VERSION = $(shell cat .nvmrc)
+INSTALLED_NODE_VERSION = $(shell node --version)
+
+.PHONY: help
+
+help:
+	@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | sort | awk 'BEGIN {FS = ":.*?## "}; {printf "\033[36m%-30s\033[0m %s\n", $$1, $$2}'
+
+all: clean test build  ## Complete clean build with tests
+
+init: init-repo init-web  ## Initialize project dependencies
+
+node:
+ifneq ($(REQUIRED_NODE_VERSION),$(INSTALLED_NODE_VERSION))
+	$(error node.js version $(REQUIRED_NODE_VERSION) required)
+endif
+
+init-repo:
+	git submodule update --init --recursive
+
+init-web: node
+	cd src/web && \
+		npm install
+
+clean: clean-dist clean-validations clean-web  ## Clean all
+
+clean-dist:  ## Clean non-RCS-tracked dist files
+	@echo "Cleaning dist..."
+	git clean -xfd dist
+
+clean-validations:  ## Clean validations artifact
+	@echo "Cleaning validations..."
+	cd src/validations \
+		rm -rf report target
+
+clean-web:  ## Clean web artifacts
+	@echo "Cleaning web..."
+	cd src/web && \
+		npm run clean
+
+test: test-validations test-web ## Test all
+
+test-validations:  ## Test validations
+	@echo "Running validations tests..."
+	cd src/validations && \
+		../../vendor/xspec/bin/xspec.sh -s -j test/test_all.xspec
+
+test-web:  ## Test web codebase
+	@echo "Running web tests..."
+	cd src/web && \
+		npm run test
+
+build: build-validations build-web dist  ## Build all artifacts and copy into dist directory
+	# Symlink for Federalist
+	ln -sf ./src/web/build _site
+
+	# Copy validations
+	mkdir -p dist/validations
+	cp src/validations/target/ssp.xsl dist/validations
+	cp -r src/validations/rules/ssp.sch dist/validations
+
+build-validations:  ## Build Schematron validations
+	@echo "Building Schematron validations..."
+	cd src/validations && \
+		./bin/validate_with_schematron.sh
+
+build-web: node ## Build web bundle
+	@echo "Building web bundle..."
+	cd src/web && \
+	  npm run build

README.md

@@ -7,7 +7,7 @@ The FedRAMP Program Management Office (PMO) has drafted FedRAMP-specific extensi
 
 To accompany these guides, the FedRAMP PMO has also drafted OSCAL files in XML and JSON formats to serve as an example and template for each major deliverable.
 
-## Support and OSCAL Deprecation Strategy 
+## Support and OSCAL Deprecation Strategy
 
 The FedRAMP PMO has [a release strategy and versioning procedures](./documents/adr/0002-git-release-version-strategy.md). FedRAMP has a minimally supported version of OSCAL, unless explicitly noted otherwise in specific documents or source code in this repository. Baselines, guides, templates, and associated tools in this repository will only support OSCAL data with a version number no lower than specified by FedRAMP version tags. A version tag that ends in `-oscal1.0.0` will only support data with `oscal-version` equal to `1.0.0` or newer, it will not support `1.0.0-milestone3`, `1.0.0-rc1`, or `1.0.0-rc2`. A future version tag ending in `-oscal1.1.0` indicates FedRAMP source code and guides will support data with `oscal-version` equal to `1.1.0` or newer, but not `1.0.0`.
 
@@ -20,7 +20,7 @@ This repository is for the development and enhancement of OSCAL artifacts only.
 The FedRAMP PMO is releasing the following files for public review and comment:
 
 - **FedRAMP Baselines:** The FedRAMP baselines for High, Moderate, Low, and Tailored for Low Impact-Software as a Service (LI-SaaS) in OSCAL (XML and JSON formats) are available [here](./dist/content/baselines).
-  
+
 - **FedRAMP OSCAL Templates:** The template files are pre-populated with FedRAMP extensions, defined-identifiers, and conformity tags where practical. They also include sample data, and are the basis for their respective guidance documents above. The drafts for public comment are available in both XML and JSON formats [here](./dist/content/templates/).
 
 - **FedRAMP OSCAL Registry** This registry is the authoritative source for all FedRAMP extensions to the OSCAL syntax, FedRAMP-defined identifiers, and accepted values. The draft for public comment is available [here](./documents/FedRAMP_Extensions.pdf).
@@ -42,12 +42,43 @@ The following NIST resources are available:
 
 - **OSCAL Workshop Training Slides:** Provided at an October workshop hosted by the NIST OSCAL Team. The early portions of the deck provide an overview, with more technical details beginning on slide 52. [https://pages.nist.gov/OSCAL/downloads/OSCAL-workshop-20191105.pdf](https://pages.nist.gov/OSCAL/learn/presentations/OSCAL-workshop-20191105.pdf)
 
-- **Content Converters:** The converters accurately convert OSCAL catalog, profile, SSP, SAP, SAR, and POA&M content from [XML to JSON](https://github.com/usnistgov/OSCAL/tree/master/json/convert) and [JSON to XML](https://github.com/usnistgov/OSCAL/tree/master/xml/convert). 
+- **Content Converters:** The converters accurately convert OSCAL catalog, profile, SSP, SAP, SAR, and POA&M content from [XML to JSON](https://github.com/usnistgov/OSCAL/tree/master/json/convert) and [JSON to XML](https://github.com/usnistgov/OSCAL/tree/master/xml/convert).
 
-- **NIST SP 800-53 & 53A Revision 4 in OSCAL:** NIST is also providing SP 800-53 and 800-53A, Revision 4 content as well as the NIST High, Moderate, and Low baselines in OSCAL (XML, JSON, and YAML formats) [here](https://github.com/usnistgov/OSCAL/tree/master/content/nist.gov/SP800-53/rev4). 
+- **NIST SP 800-53 & 53A Revision 4 in OSCAL:** NIST is also providing SP 800-53 and 800-53A, Revision 4 content as well as the NIST High, Moderate, and Low baselines in OSCAL (XML, JSON, and YAML formats) [here](https://github.com/usnistgov/OSCAL/tree/master/content/nist.gov/SP800-53/rev4).
 
-NIST offers a complete package containing the NIST OSCAL converters, syntax validation tools, 800-53 and FedRAMP baselines content is available for download in both ZIP and BZ2 format. Visit the [NIST OSCAL Github releases page for more information](https://github.com/usnistgov/OSCAL/releases/latest). 
+NIST offers a complete package containing the NIST OSCAL converters, syntax validation tools, 800-53 and FedRAMP baselines content is available for download in both ZIP and BZ2 format. Visit the [NIST OSCAL Github releases page for more information](https://github.com/usnistgov/OSCAL/releases/latest).
 
 Please ask questions or provide feedback on the above NIST dependencies either via email to [oscal@nist.gov](mailto:oscal@nist.gov), as a comment to an existing issue, or as a new issue via the [NIST OSCAL GitHub site](https://github.com/usnistgov/OSCAL/issues).
 
 FedRAMP looks forward to receiving your comments and sharing additional progress.
+
+## Developer notes
+
+### Build / test
+
+A top-level Makefile is provided to simplify builds.
+
+Build requirements are:
+
+- gcc make
+- node.js (as versioned in [./nvmrc](./.nvmrc))
+- Java 8+
+
+For usage information, use the default target:
+
+```
+make
+```
+### Creating a release
+
+[ADR 0002 (git release version strategy)](./documents/adr/0002-git-release-version-strategy.md)
+outlines the release and versioning system.
+
+Releases must be tagged from the master branch of [GSA/fedramp-automation](https://github.com/GSA/fedramp-automation). If your work resides elsewhere, first merge to master via a pull-request.
+
+To produce a release:
+
+- [Create a Github Release](https://github.com/GSA/fedramp-automation/releases/new)
+  - Ensure the tag follows the naming convention defined in [ADR 0002](./documents/adr/0002-git-release-version-strategy.md)
+- [Monitor running Github Actions](https://github.com/GSA/fedramp-automation/actions) for the `build-release` workflow's completion ([./.github/workflows/create-release.yml](./.github/workflows/create-release.yml))
+  - On completion, artifacts will be attached to the release