0.1.0 • Published 10 months ago

@htammen/deploy-abap-logger v0.1.0

Weekly downloads
-
License
MIT
Repository
-
Last release
10 months ago

Deploy ABAP logger

A tool that can be used to write logging info about deployments (also other actions are possible) of applications.
We use this tool to log our deployments of SAPUI5 applications to SAP ABAP repository.

When you call this tool it collects some information from git, package.json as well as some SAP specific deploy information and writes it to a local json file (deploy-log.json).

Installation

npm install -D @htammen/deploy-abap-logger

If you want to run the deploy-abap-logger without installing it into your local or global node_modules folder you can run it directly:

npx @htammen/deploy-abap-logger

Usage

To use this tool just add it to a script of your package.json.
Here is an example. Here we use nwabap:upload to deploy our SAPUI5 application to the ABAP system.

  "scripts": {
    ...
    "deploy": "npm-run-all build nwabap:upload write-deploy-log",
    "write-deploy-log": "deploy-abap-logger"
  }

Log information written

The log is written in json format. Here you see what gets logged

[
  {
    "project": "<name of package.json>",
    "version": "<version of package.json>",
    "branch": "<the current git branch>",
    "username": "<the git username from git config>",
    "date": "<current date with format yyyy-mm-dd>",
    "time": "<current time with format HH:MM:ss>",
    "commit": [
      {
        "hash": <hash of last commit or empty if special comit info>,
        "title": <title of commit or special info>
      }
    ],
    "abap_package": "<package name of the ABAP package the bsp is associated to",
    "abap_bsp": "<name of the ABAP BSP the application is deployed to>",
    "abap_transport": "<ABAP transport name/ID>"
  }
]

Here is an example

[
  {
    "project": "salesorder-app",
    "version": "1.1.0",
    "branch": "main",
    "username": "Helmut Tammen",
    "date": "2024-09-15",
    "time": "14:19:31",
    "commit": [
      {
        "hash": "",
        "title": "deployed with unstaged changes"
      },
      {
        "hash": "642acec9a0b44891e004d8622139c3804e2b0f3d",
        "title": "fix: application fixed"
      }
    ],
    "abap_package": "ZOURS_TP_APPS",
    "abap_bsp": "ZTP_MONI_FLP",
    "abap_transport": "AB1K600434"
  }
]

Property Documentation

project

The tool reads the property name from your package.json and prints it in this property.

version

The tools reads the property version from your package.json and prints it in this property.

branch

The branch is read with the command git branch --show-current and printed to this property.

username

The username is read with the command git config user.name and printed to this property.

date

This is the current date with format yyyy-mm-dd

time

This is the current time with format HH:MM:ss

commit

In general in the commit array there is only one entry enclosed. This is the last git commit you created.

If you haven't staged or committed your changes to git you will get more than one entry in the commit array.
The first one is a special info without a hash. The title gives more details like 'deployed with unstaged changes' or 'deployed with uncommited changes'.
The second one is the last commit found in the commit log.

abap_package

ABAP package name. This is either read from the file ui5-deploy.yaml or .nwabaprc.

abap_bsp

ABAP bsp name. This is either read from the file ui5-deploy.yaml or .nwabaprc.

abap_transport

ABAP transport name/ID. This is either read from the file ui5-deploy.yaml or .nwabaprc.

Contribution

This package currently works for our environment. There might be other ones that are slightly different.
If it does not fit into yours you can either add changes via forks and pull requests or create an issue. on github.

0.1.0

10 months ago

0.0.2

1 year ago

0.0.1

1 year ago