pipeline doesnt recognize origin/master

[Evan Wu]

I'm running pipeline on a angular workspace project power by nrwl.

and I have a npm script that reference the branch (`origin/master`)

node --max_old_space_size=8192 ./node_modules/.bin/nx affected:lint --parallel --maxParallel 8 --base=origin/master --head=1ffcde318bba511382be7bd44cfdccb186e063a1

 (Note the --base option)

this will work when the pipeline is running on master branch but I kept getting 

fatal: Not a valid object name origin/master

when running pipeline on other branch. 

I thought it's because master is not fetched, so I add 

git fetch origin master

before I run the other command, and from the log I can tell that master is being fetched but I still get the error. 

Does anyone know how to resolve this?

[Steven Vaccarella]

Hi Evan,

I suspect your "git fetch" command is not working as expected because Pipelines doesn't do a full clone and this results in a git configuration that won't automatically create remote tracking branches for other branches (besides the one being built). To fetch a different branch, try something like this:

git fetch origin master:refs/remotes/origin/master

This should create the remote tracking branch "origin/master" regardless of the current configuration. 

[dan.foley]

Same, using nx and encountering the same issue.  This solved the problem.

[Garrett Hughes]

deleted