git-multi | Support Multiple Git Repositories in One Directory | Command Line Interface library

I have written a script, which takes 5 inputs: 1) Clone URL 2) BranchName to which the cherry pick needs to be merged 3) The new branch name which needs to be created with all the cherry pick commits 4) The cherryPick commit ids. 5) Dynamically created temp directory in which these operations should happen.

I am trying to implement Git cherry pick for multiple commit Ids at once. But it fails, or either this is not how it should be used.

I am trying to use bash command from here : https://stackoverflow.com/a/2553705/9614476

I'd like to use multiple Git server accounts (with any of GitHub, GitLab, BitBubket etc.).

The accounts are distinguished by their email addresses, name1@email1.com and name2@email2.org and git is setup to use these addresses in the relevant repositories

The following constraints apply to the 'change-account workflow':

1. Without touching/changing SSH config files (e.g. ~/.ssh/config, etc.) when repositories or servers are added/removed/changed.
2. Without requiring SSH agent running i.e. no ssh-add ....
3. Without changing environment variables.
4. Without changing the git clone instruction.
5. Isolate the SSH keys used with git away from other SSH keys.
6. Use the same 'change-account workflow' across all private and public repositories.
7. The 'change-account workflow' is a one (1) step/command.
8. The 'change-account workflow' is one (1) time per repository (i.e. not each time you move into work on the repository).

The initial repository setup (which is also one time activity) can involve more than one step. Any conventions/assumptions are acceptable as long as they don't break the constraints.

These are responses that do not satisfy the constraints.
They generally require changes to ~/.ssh/config and/or involve the SSH agent daemon:

1. handle-multiple-git-account
2. using-multiple-git-accounts
3. multiple-git-accounts-and-ssh-key
4. multiple-github-accounts-ssh-config
5. multiple-git-users-on-same-machine
6. multiple-github-accounts-with-git-in-windows
7. git-multiple-accounts-and-repository-problems
8. ssh-config-to-access-multiple-repo-not-working
9. multiple-github-accounts-on-the-same-computer
10. can-i-specify-multiple-users-for-myself-in-gitconfig
11. setting-up-ssh-config-file-for-multiple-codebase-accounts
12. how-can-i-push-git-with-multiple-accounts-on-one-machine
13. multiple-github-accounts-what-values-for-host-in-ssh-config
14. how-to-configure-multiple-github-accounts-on-your-computer
15. ssh-config-with-multiple-keys-for-multiple-gitlab-user-accounts
16. github-multiple-accounts-permission-to-personalusername-reponame-git-denied-to

I want to create a concourse job that can audit the branches of a git repo. However the git resource and many others like it that I have tried only can pull one branch into a repo. I need to be able to have concourse download a repo with all the remote branches. How can I do that?

I have already tried the following options that do not download all the remote branches:

https://github.com/vito/git-branches-resource

https://github.com/cloudfoundry-community/git-multibranch-resource

I also cannot pull down the extra branches with git commands after the resource is downloaded:

So I've been investigating ci/cd pipelines using concourse and cloud foundry lately, and I've been confused about what the best way to do this is. So I've been thinking about how the overall flow would go from development to release. There are a lot of talks and videos that discuss this at a very high level, but often they abstract away too much of the actual implementation details for it to be useful. Like how do people actually roll this out in actual companies? I have a lot of questions, so I will try to list a few of them here in the hope that someone could enlighten me a little.

1. What does the overall process and pipeline look like conceptually from development to prod? So far I have something along the lines of :

   • During development each product team is under their own org, with each developer possibly having their own development "space" that they could manually cf push to and just develop against. There will be development spaces that devs can just directly push to as well as spaces that can only be used by the automated pipeline to deploy artifacts for functional tests.

   • Once devs finish a feature they would make a pull request, which would trigger a smaller pipeline with some tests using something like the git-multibranch-resource or the git-pullrequest-resource, which would hook into the github required status check hooks and report back if any particular PRs are able to be merged into master or not

   • Once all checks pass and the pull request is merged into master the below pipeline is kicked off, which validates the master branch before releasing the artifact to prod.

code repo [master] -> build -> snapshot artifact repo -> deploy to test space -> run functional tests -> deploy to staging space -> run smoke tests and maybe other regression tests -> deploy artifact to prod -> monitoring/rollbacks (?)

1. What other things could/should be added to this pipeline or any part of this process?

2. Once you automate deployment how do you do also automate things like canary releases or rollbacks once something happens? Should this be part of the pipeline or something completely separate?

3. I've been playing with the idea of creating spaces temporarily and then tearing them down for the functional testing phase, would there be any benefit to doing that? The idea is that the apps being deployed would have their own clean environments to use, but this could also potentially be slow, and it is difficult to know what services are required inside of each space. You would have to read the manifest, which only specifies service-names, which seems to necessitate some sort of canonical way of naming service instances within the same space? The alternative is managing a pool of spaces which also seems complicated...

4. Should the pipeline generate the manifest files? Or should that be completely up to the developers? Only the developers know which services the app needs, but also it seems like things like instance count, memory etc should be something that the performances tests/pipeline should be able to determine/automate. You could generate a manifest inside the pipeline, but then you would not know which services the app needs without reading a manifest....chicken and egg problem?

I have many more burning questions, but I will cut it off here for now. I know the subjects have kind of bounced back and forth between Concourse and Cloud Foundry, but it seems when discussing CI/CD concepts the nitty gritty implementation details are often the actual tricky bits which tangle the two rather tightly together. I am also aware that the specific implementation details are often very specific to each company, but it would be great if people could talk about how they have implemented these pipelines / automated pipelines using Concourse and Cloud Foundry at their companies (if you can spare the details of course). Thanks everyone!