Improve the user experience in order to show the command before being executed

[diegolovison]

Create the following script

scripts:
  ensure-quarkus-cli:
  - sh: quarkus version #to see if the command exists
  getting-started:
  - sh: cd /tmp/
  - sh: "[[ ! -d quarkus-quickstarts ]] && git clone https://github.com/quarkusio/quarkus-quickstarts.git" # prevent cloning again
  - sh: cd quarkus-quickstarts
  - sh: cd getting-started
  - script: ensure-quarkus-cli
  - sh: quarkus dev
hosts:
  test: dlovison@localhost
roles:
  setup-env:
    hosts:
    - test
    run-scripts:
    - getting-started

Run it with -ix in order to ignore the quarkus-quickstarts folder presented on the disk.

The output will be:

Screencast.from.2025-01-08.16-12-24.mp4

This will give the impression that the qDup is hanging.
In practice, it is running quarkus dev without printing anything in the terminal.

I would like:

• print the command before being executed
• being able to capture quarkus dev output and display it in the terminal

What does the community think about that?
I spent some hours until I figured it out.

[diegolovison]

Here is other example

scripts:
  hello-qdup:
    - sh: "ping -c 30 redhat.com"
hosts:
  local : ${{target-host}}
roles:
  run-hello-qdup:
    hosts:
      - local
    run-scripts:
      - hello-qdup

Output:

14:00:22.763 starting 1 scripts
14:00:22.765 hello-qdup:16@localhost: script-cmd: hello-qdup
14:00:22.766 hello-qdup:16@localhost: hello-qdup
14:01:02.902 hello-qdup:16@localhost: ping -c 30 redhat.com
PING redhat.com (34.235.198.240) 56(84) bytes of data.

--- redhat.com ping statistics ---
30 packets transmitted, 0 received, 100% packet loss, time 29721ms

It will be in the console only when the ping has finished.

[diegolovison]

Another thing
Jenkins log

What was really happening

[johnaohara]

There is a troubleshooting guide to help diagnose issues: https://github.com/Hyperfoil/qDup/blob/master/docs/tutorial/troubleshoot.adoc

[diegolovison]

I didn't read that guide yet but for me, this kind of troubleshooting and knowledge is more for developers instead of user
developers: the persona that maintains qDup
user: the persona that uses qDup

For me, as a user ( I am still learning qDup ) I prefer to have everything in the the terminal. It is easy to see. This is also true while doing things on Jenkins. Reading the Jenkins Console and being able to understand what is going on is a big win.