artefacts

DISCOVERY

LEGISLATION

Current ToolS





(what we have)


SCAN CONSOLE



  • Console Application
  • Scans pre-configured locations
  • Centralised configuration
  • Can configure ignore lists
  • Posts hashed results to web API
  • Only posts delta changes


WEB


  • Search for artefacts
  • Search for file instances
  • View server contents
  • Legislation per artefact
  • Central Configuration of Scan Console

Web



potential integrations

  • DISC
  • Osprey
  • Server Details
  • Integrity Checker
  • Legislation Application
  • Remedy
  • Team City etc

INTEGRITY CHECKER



  • Source of the signed file
  • Violation check

potential users


  • Developers
  • Build and Configure
  • IT Deployment
  • Product Owners
  • Regulators
  • Support Services




How is it all stored?

builds





(what we'd like to do)

store builds

(without content)

  • Diffs between builds 
  • Diffs between servers
  • Link builds to products
  • Discover which builds are on a server
  • Track builds through the process
  • Promote builds from development through to production
  • Notify product owner when a build is deployed

STORE BUILDS

(with content)

  • Push and pull build content
  • Never store the same file twice
  • View/Download a file on a server from the library
  • Build dependencies
  • Package builds for deployments and store them
  • Notify product owner when a build is deployed

Example



fsbuild --push --product Caiman --name CaimanApplication-1.0.1.44565-26 --number 26
path\to\input\dir_or_zip_or_nuget\CaimanApplication-1.0.1.44565-26.zip




fsbuild --pull --name CaimanApplication-1.0.1.44565-26 --number 26
path\to\output\dir_or_zip_or_nuget\CaimanApplication-1.0.1.44565-26.zip

certification

  • Tag files for certification
  • Relate these tagged files to servers and builds
  • Notify product owner if a build changes a certified file



demo

Title