norc | manage logging , error reporting | Cron Utils library

i'm trying to built a bash using c.

but I faced this problem when I try this: env -i bash

this should pass a void env into bash so all the environment variables should be null

example :

I'm trying to dive in the GitHub action, and so on the .ylm files, and to understand the process I would like to echo some environment variables, such as ${{ github.repository }} or ${{ github.repository_owner }} or event secrets like ${{ secrets.GITHUB_TOKEN }} or any other, and in the output I'm getting ***.

Is there any way to force the output to show the actual values instead of the asterisks?

dev.ylm

I've setup and Azure Database for MySQL. I am able to connect fine through the Azure Cloud Shell using

mysql -h ...mysql.database.azure.com --ssl -u web -p

Now what I want to do is to be able to connect to this database from an Azure pipeline. The purpose is to use the database to track the version numbers for our artifacts.

My initial test pipeline yaml looks like

We have an Azure Repository which triggers a Release-Pipeline every time something is pushed to the main branch. When a Release is triggered it shows its status (succeeded) on the right side in the commits in Azure Repos like on the following Picture:

It even shows which stage is already promoted etc. which is awesome. This all works fine when configuring the Release Pipeline Manually with the following CD-Trigger Configuration:

Even when exporting the Pipeline JSON file and reimporting it everything works as expected.

However, when creating the Release with the exact same Settings via API i don't see the Status of the Release. The trigger itself works as expected but the status in the commits is simply not there:

Does someone know which exact Setting in the Release-Pipeline.json is responsible for this status?

Here are some parts of the json body I send via API which might be missing something?

Edit: A few more information needed i guess. I use a cli-tool to create the body and send the api request. The values are templated. The template gets its values either from previous api calls or from user inputs. Here is the complete template. I created it based on the manually configured relase-pipeline JSON (Which works fine and shows the status i want).

I have a condition for a stage to run. The condition is true, but the stage keeps being skipped and I'm not sure why.

This is the stage:

Im using the below task to install AWS.Lambda.Tools in my pipeline, however I can't get it to use nuget.org as the source and it continues to try and use my internal feed.

I have a git repository containing a node.js "app" (only 1 file) with its package.json.

I need to use that "app" from azure devops pipeline of other organizations, so I made a pipeline in that nodejs project that makes a versioning+publish of that script on a NPM based azure artifact feed.

On another organization, in the pipeline where I wanted to use that app, I used an "npm" task configured like that :

I'm trying to publish the resulting jar from a Gradle build. The problem I've come across is that the PublishBuildArtifacts fails with:

I would like to ask how can I implement the ESLint on our Azure Pipeline? I do not have enough knowledge on Azure Pipelines and SonarQube, and I also am not so sure about ESLint. So far, here's the script I have. Although this is pretty much from the available tasks. I'd like to implement the ESLint on SonarQube like on this link: https://docs.sonarqube.org/pages/viewpage.action?pageId=11639183