Commit 9c469057 authored by Gibbs, Ian's avatar Gibbs, Ian
Browse files

Merge branch 'i0x-main-patch-30be' into 'main'

update readme

See merge request !48
parents d42dc255 6bfb25fa
Loading
Loading
Loading
Loading
+1 −0
Original line number Diff line number Diff line
@@ -3,6 +3,7 @@
workflow:
  rules:
    - { if: $CI_PIPELINE_SOURCE == "merge_request_event", when: never }
    - { changes: ['README.md'], when: never }
    - { when: always }

variables:
+9 −7
Original line number Diff line number Diff line
@@ -15,7 +15,7 @@ pre-commit install

The desktop files are validated using `desktop-file-validate` and have an error about the category being "Analysis" rather than "X-Analysis".

The spec file passes [rpmlint](https://linux.die.net/man/1/rpmlint) with one warning about the definition of the source (`invalid-url Source0`).
The spec file syntax is validated using [rpmlint](https://linux.die.net/man/1/rpmlint).

Versioning
----------
@@ -24,12 +24,14 @@ Versioning
* minor changes is when changes to the existing applications/tools happens
* patches are encompassed in minor changes and are not included

Deployment
----------
`nsd-app-wrap` is deployed via an rpm that is created using gitlab-ci and configured mostly in the `Dockerfile`.
The `Dockerfile` is based on a centos7 image with rpm-build installed.
It creates the rpm then uses `scp` to copy noarch to packages.sns.gov.
The analysis cluster is configured to automatically update `nsd-app-wrap` rpm whenever a new one is available.
Build & Deployment
------------------
The _nsd-app-wrap_ rpm build process is containerized.  The Dockerfile in the `rpm` directory is used to create a base image containing the rpm tools needed to create rpms.

Gitlab CI workflow orchestrates the build and publishing process anytime changes are made in the `src` folder.
After an rpm is built, it's published on packages.sns.gov

analysis machines are configured to automatically update `nsd-app-wrap` rpm whenever a new one is available.


Adding a new application