git-cl | Git command line tool for managing your CHANGELOG | Command Line Interface library

Ok, I found a solution for me that involves using the Azure DevOps Git SSH URL and not the HTTPS.

First of all, I created a SSH Key according to this Use SSH key authentication or choose your Git providers tutorial.

Once you have your SSH private and public key, you need to install the SSH Key into your YAML pipeline. See Install SSH Key task.

To summarize the discussion in the comments thread.

Most likely it's happening since DVC can't get access to a private repo on GitLab. (The error message is obscure and should be fixed.)

The same way you would not be able to run:

Unfortunately, there is no configuration variable or command line option to turn off this warning (see the code in clone.c).

The options I see are :

• disable all of stderr,
• spot the translation of that message and grep it out,
• write an alias for git init && git remote add origin

In v0.14 Tekton introduced the so called finally Tasks, which run at the end of every Pipeline - regardless which Task failed or succeeded. As the docs state:

finally tasks are guaranteed to be executed in parallel after all PipelineTasks under tasks have completed regardless of success or error.

In general finally tasks look like this:

TLDR;

I created a fully comprehensible example project showing all necessary steps and running pipelines here: https://gitlab.com/jonashackt/microservice-api-spring-boot/ with the full .gitlab-ci.yml to directly trigger a Tekton Pipeline:

As you are using node version 17, I can see that this problem happens,

Downgrading to node version 16 will solve the problem(using nvm):

No, they're not. When it says, "don't use the standard ignore rules", it means, "don't ignore (i.e., don't prevent the removal of) files that match the standard ignore rules; treat them as any other untracked files."

Normally files that are ignored are preserved with git clean -df, but with -x, these files are not ignored because the standard ignore patterns are not considered, so the files are considered untracked and hence removed.

You are correct about what the standard ignore rules comprise.

Supposing you're talking about Bitrise's step to deploy ipa and pkg files to AppStore Connect. This step is using Fastlane's deliver action under the hood, which reads the metadata from local .txt files found inside the repo itself (see this section on configuring metadata files)

I see no way to configure the metadata_path on Bitrise's step, which means most likely they're keeping the default value of ./fastlane/metadata.

So theoretically all you have to do is setting your metadata txt files in your repo (or use fastlane's deliver action to help you setup those folders the first time), and then Bitrise's step should be able to pick those up automatically, given you're already setting - skip_metadata: 'no' on that step.

I uninstalled node completely, deleted all npm folders in appdata. Reinstalled node. Then it worked enough to give me a different error.