問題タブ [cicd]

質問する

For questions regarding programming in ECMAScript (JavaScript/JS) and its various dialects/implementations (excluding ActionScript). Note JavaScript is NOT the same as Java! Please include all relevant tags on your question; e.g., [node.js], [jquery], [json], [reactjs], [angular], [ember.js], [vue.js], [typescript], [svelte], etc.

621 問題
Newest
Active
Bountied
318
Unanswered
0 投票する
1 に答える
100 参照

amazon-ec2 - .net コア コードを公開し、gitlab yml ファイルを使用して AWS Windows インスタンスにデプロイする方法

コード .net コアが GitLab に追加され、Web アプリケーションが AWS Windows インスタンス IIS にデプロイされます。IIS でコードを自動的に公開および展開する yml ファイルを作成する方法。

0 投票する
2 に答える
248 参照

git - Deploy Single Code Base To Multiple Clients

In my company there's an application repository that we would want to deploy to multiple clients. Each client have different application configuration values (appsettings.json) and this settings may change overtime depending on the clients. That is why, we create different git branches for each client in order to do CICD. There are multiple TeamCity Servers located in each client server (on premise) which are listening to their git branch for changes. Our concern is these number of clients will grow. The number of git branches will also increase and we do not want that to happen.

Note: Each client have their own staging and production environment. So we created the branch name as "clientA-staging", "clientA-production", "clientB-staging", "clientB-production". Another reason why we did this is because, if there is a changes in a client configuration. We just want to deploy this changes to that client only.

Are there any ways that we can improve this? What we want to achieve are:-

  1. Reduce and maintain the number of staging and production git branches to two branches only.
  2. Deploy to specific client only if there is configuration changes on their side.

12345678910