github actions - debug logging mode

Github actions supports steps (task) and runner debugging mode. You can turn these on by 

Step Debugging level 

Set your environment variable to ACTIONS_STEP_DEBUG to true

  build:
   
    env:
      MyEnvVar: Hello
      ACTIONS_STEP_DEBUG : true

Runner debugging level

Set your environment variable to ACTIONS_RUNNER_DEBUG  to true

  build:
   
    env:
      MyEnvVar: Hello
      ACTIONS_RUNNER_DEBUG : true


After running the pipeline, if you goto your repository -> Actions -> Ensure you selected your workflow -> expand / open your job and then download your logs as shown here. 



If you expand your logs file, you will be able to see additional logs compare to a normal logs (without debugging turned on)








Comments

Post a Comment

Popular posts from this blog

The specified initialization vector (IV) does not match the block size for this algorithm

Image
If you're getting  exception when trying to assigned key to a symmetric key and getting error message below :- The specified initialization vector (IV) does not match the block size for this algorithm And your code probably look like something below :- Then you need to go into debug mode and start looking into the supported size for IV as shown in diagram below :- As you can see, IV is 16 bytes, so you need to provide 16 bytes. The same goes for Key field too, if you're adding anything to it. As long as you provide a valid key size, then we're good and you're code will be ready.
Read more