ci: create p4-lock-checker.yml

- initial code upload, it just tries to check how p4 fstat will be displayed in github action log.

diff --git a/.github/workflows/p4-lock-checker.yml b/.github/workflows/p4-lock-checker.yml
new file mode 100644 (file)
index 0000000..82050b3
--- /dev/null
+++ b/.github/workflows/p4-lock-checker.yml
@@ -0,0 +1,39 @@
+# This is a basic workflow to help you get started with Actions
+
+name: p4-lock-checker
+
+# Controls when the workflow will run
+on:
+  pull_request:
+  push:
+    branches:
+      - main
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  p4-lock-checker:
+    runs-on: [code-default]
+    container:
+      image: actions-docker.bart.sec.samsung.net/docker-gbs-base
+      options: --user root --privileged
+    
+    # environmental variables to access VD P4. It needs to be updated when the accoung info is changed (e.g. password reset).
+    env:
+      P4PORT: ${{ secrets.P4PORT }}
+      P4USER: ${{ secrets.P4USER }}
+      P4PASSWD: ${{ secrets.P4PASSWD }}
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      - name: P4 setup
+        uses: code-actions/perforce-setup-p4@v1
+        with:
+          command: login
+          global_options: '-p ${{ secrets.P4PORT }} -u ${{ secrets.P4USER }}'
+
+      - name: check P4 ESPP DEV status
+        run: |
+          p4 fstat "//TIZEN/[MAIN]/[ONEPROD_Prj]/[FET]/[COSMOS]/PLATFORM/PPI/capi-trackrenderer-tv/AUTHORS"