Gitlab hooks 2

We need somebody that creates hooks for Gitlab CE. Challenge: We want to have central place for all our codings (gitlab) but because we are working for many other companies to develop code it is currently hard to push all codings to the customers repositories. For our development we use our own ticketing system with our own sequence. The customer(s) need the code under their own ticket number. For example: Ticket # at us = 1248 Customer ticket # = 2587 For controlling purposes we will check in the code under our # in our gitlab. Currently the developer is making a 2nd remote and is also pushing the changes to the customer repo with his ticket number, by using command: "git push [remote] [local branch]:[upstream branch]" To centralize/stream this process we would like start using hooks method of gitlab. Our taught is as following: HOOK UPSTREAM PUSH ----------------------------------------------------- Note: when we having a downstream mirrowing then we need to have something to prevent a push to the upstream, otherwise we getting a loop mirrowing downstream --> push in origin | | new comments <-- hook push upstream Step 1) In gitlab somewhere we need to set different login creditentials, (peferred in admin part), example: Platform Login Key Password gitlab xxxx xxxx xxxx github xxxx xxxx xxxx bitbucket xxxx xxxx xxxx beanstalk xxxx xxxx xxxx cloudForge xxxx xxxx xxxx Codebase xxxx xxxx xxxx ...... etc. These need to be able to set up flexible, so no fixed fields! Perhaps as envoriment variables? Step 2) System hook On every push the some push/comments need to be pushed to the upstream. The data regarding the upstream will be in [login to view URL] in the branch. So every branch will have his own file, called "[login to view URL]", example: [login to view URL] platform: github address: [login to view URL] or xxxx@[login to view URL] client-ticket: xxxxx prefix: aaaaa suffix: bbbbb Flow: if no [login to view URL] then do nothing else push upstream. use credentials "platform" (needs to match with step 1 platform name) When address starts with @.... like in git@[login to view URL] then it needs to add login of the platform in front of the @. in combination of the key. When the address is a http or https then just use the log in credentials as given at the platform branch name prefix + client-ticket + suffix, if prefix or suffix missing then skip that part. e.g. feature_2587 or feature_2587_hello_world etc etc. I would be nice if gitlab can push a message into the origin OUR repo zo we know that push was successfull When not successfull: give the error message of unsuccesfull push When successfull: "Great, your commits were push upstream [address] to branch [branch] Optional 1) Would it be possible to do a merge in the upstream? the pushed feature branch into another branch upstream. is so we can add the following in yaml file [login to view URL] platform: github address: [login to view URL] or xxxx@[login to view URL] client-ticket: xxxxx prefix: aaaaa suffix: bbbbb merge: [upstream branch name] HOOK MIRROW DOWNSTREAM ----------------------------------------------------- Because we use gitlab CE and we need to have the update information for development, we also need to pull the latest changes from the upstream. Continuous is not something that is default in gitlab. We need to have a option/hook that will pull the latest code very xxx minutes. ------------------------------------------------------------------------------------ We are open for other suggestions, if easier to maintain/avoid issues. making developments faults less.