Changed deploy strategy to use the config of the branch being deployed

[jacob-s-son]

I am not sure though where it's fetching repo. This obviously won't work if jarvis copy of the repo is not aware of the new branch.

[RadekMolenda]

👍

[benflex]

What if you do a git fetch and then git checkout for the branch ?
i.e.
cmd += "git fech; git checkout #{params[:branch]}"

[jacob-s-son]

That's an option. Will update.

[pointlessone]

git fetch && git checkout

Is probably better.

[jacob-s-son]

But git pull is still needed right, as non of those is going to merge ?

[benflex]

No sure why we would need to merge since no work is gonna be done ever on the server ? This probably needs to be tested.

[benflex]

Or we can do :
cmd += "git fetch; git checkout #{params[:branch]} && git pull origin #{params[:branch]}"

[jacob-s-son]

I have tried out locally simply fetch + checkout, works fine if you simply updating outdated repo and switch to a branch, that is not merging anything.

I think let's go with @cheba proposed git fetch && git checkout params[:branch]

WDYT?

[benflex]

👍