5 ms·

At some point there has to be centralization. We are deploying one product, not N products for N commits. If I can't push, I can't have CI build my branch, and

At some point there has to be centralization. We are deploying one product, not N products for N commits. If I can't push, I can't have CI build my branch, and I can't submit a PR for review.

inflatableDodo 7y ago
It should be easy to move the center. Having a single 3rd party be the only central point you have available is asking for trouble.
mbrumlow 7y ago
But you could continue working and only have to apply minor patches forward if you later find your starting point needed to be fixed. You don't have to wait for CI, just create a new branch and continue your work as though CI passed, and your PR was accepted. If that comes true you don't need to worry much, just rebase and continue. On the other hand if you find out you needed to make changes - do those on the branch you made those changes, and finish your PR/CI cycle. Then go to the new branch you continued work on and rebase, and continue. Is there something I am missing?
- zymhan 7y ago
  Heaven forbid we find a reason to take a break
  - deleted 7y ago
    [deleted]
  - jnbiche 7y ago
    In the old days at least we had compiling. Not so much anymore.
    - tjoff 7y ago
      No, today we have something else to wait for, it is called the runtime.
      - OJFord 7y ago
        But users wait for that, I can get on with finding a new framework instead.
    - ascorbic 7y ago
      npm install
      - radicalriddler 7y ago
        And when you need to delete your node_modules folder for the upteenth time, it's a nice 5 minute break.
      - Smithalicious 7y ago
        He said a break, not a vacation
giancarlostoro 7y ago
But you can technically spin up another git server, you can spin up as many git servers as you need and the same code will be there. I do understand what you mean though, been there. Organizations may not be happy with hearing that they need multiple places to store code.
LoSboccacc 7y ago
you can totally push to each other dev machine as needed, so that covers reviews. and just get the guy responsible for maintaining ci to fetch from everyone machine and push to the build server, or you can configure that to pull from this guy pc if needed depending on your ci

At some point there has to be centralization. We are deploying one product, not N products for N commits. If I can't push, I can't have CI build my branch, and I can't submit a PR for review.

inflatableDodo 7y ago

It should be easy to move the center. Having a single 3rd party be the only central point you have available is asking for trouble.

mbrumlow 7y ago

But you could continue working and only have to apply minor patches forward if you later find your starting point needed to be fixed. You don't have to wait for CI, just create a new branch and continue your work as though CI passed, and your PR was accepted. If that comes true you don't need to worry much, just rebase and continue. On the other hand if you find out you needed to make changes - do those on the branch you made those changes, and finish your PR/CI cycle. Then go to the new branch you continued work on and rebase, and continue. Is there something I am missing?

zymhan 7y ago
Heaven forbid we find a reason to take a break
- deleted 7y ago
  [deleted]
- jnbiche 7y ago
  In the old days at least we had compiling. Not so much anymore.
  - tjoff 7y ago
    No, today we have something else to wait for, it is called the runtime.
    - OJFord 7y ago
      But users wait for that, I can get on with finding a new framework instead.
  - ascorbic 7y ago
    npm install
    - radicalriddler 7y ago
      And when you need to delete your node_modules folder for the upteenth time, it's a nice 5 minute break.
    - Smithalicious 7y ago
      He said a break, not a vacation

giancarlostoro 7y ago

But you can technically spin up another git server, you can spin up as many git servers as you need and the same code will be there. I do understand what you mean though, been there. Organizations may not be happy with hearing that they need multiple places to store code.

LoSboccacc 7y ago

you can totally push to each other dev machine as needed, so that covers reviews. and just get the guy responsible for maintaining ci to fetch from everyone machine and push to the build server, or you can configure that to pull from this guy pc if needed depending on your ci