Timeline for shared CD (Continuous Deployment) for multiple Git repositories
Current License: CC BY-SA 4.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 21, 2019 at 3:08 | history | edited | Robert Harvey | CC BY-SA 4.0 | added 1 character in body |
| Dec 23, 2017 at 7:18 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 23, 2017 at 6:42 | answer | added | Dan Cornilescu | timeline score: 4 | |
| Oct 12, 2017 at 11:48 | history | tweeted | twitter.com/StackSoftEng/status/918443317385400321 | ||
| Oct 11, 2017 at 14:51 | comment | added | Stav Alfi | @Eternal21 How Gitlab services provide solution for this situation? Can I implement those solutions in Git TFS ? | |
| Oct 11, 2017 at 14:50 | comment | added | Stav Alfi | @Bishoy We are running integration tests between frontend and backen. if those tests pass, we will deploy. | |
| Oct 10, 2017 at 21:51 | comment | added | Bishoy | Your problem isn't the CD configuration. its in the right level of abstraction for the tests. are your tests unit or integration tests? and which ones you dictate to pass in order to pass the PR and deploy? | |
| Oct 10, 2017 at 19:36 | comment | added | Eternal21 | Did you look into usig Gitlab CI server rather than Jenkins? | |
| Oct 7, 2017 at 21:44 | comment | added | Stav Alfi | @Justin I have considered it many times but the repositories may grow too big for doing so. Also I'm more curious to understand how to implement CD with multiple repositories.. Seems like there is no solution for this kind of popular problem. | |
| Oct 7, 2017 at 21:41 | comment | added | Justin | From what you describe the development of the front & back end for a given feature is done in parallel - have you considered having a single repository rather than two? | |
| Oct 7, 2017 at 20:10 | history | edited | Stav Alfi | CC BY-SA 3.0 | added 28 characters in body |
| Oct 6, 2017 at 22:01 | history | edited | Stav Alfi | CC BY-SA 3.0 | added 18 characters in body |
| Oct 6, 2017 at 21:39 | comment | added | gnat | consider also editing to explain what "F.E" and "B.E" stand for, frontend and backend? | |
| Oct 6, 2017 at 21:38 | history | edited | gnat | CC BY-SA 3.0 | added 13 characters in body; edited tags |
| Oct 6, 2017 at 21:22 | history | edited | Stav Alfi | CC BY-SA 3.0 | edited title |
| Oct 6, 2017 at 21:22 | comment | added | Stav Alfi | I'm sory, CD means continuous deployment. | |
| Oct 6, 2017 at 21:01 | comment | added | amon | uuh, what does CD mean in this context? Certainly not Compact Disk, the optical storage medium? | |
| Oct 6, 2017 at 20:57 | history | asked | Stav Alfi | CC BY-SA 3.0 |