Re^2: Effectively handling prerequisites during continuous integration

In this case, this is more about pre-release testing than about continuous deployment (ie we build and test every commit on develop, then every so often push a new version to prod, rather than pushing every commit straight to prod)

Comment on Re^2: Effectively handling prerequisites during continuous integration

Replies are listed 'Best First'.
Re^3: Effectively handling prerequisites during continuous integration by BrowserUk (Patriarch) on Jun 11, 2015 at 10:22 UTC
Still sounds like your allowing your process to be driven by every random change in every one of your dependencies; rather than by the need of your own code. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". I'm with torvalds on this In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked	[reply]

Replies are listed 'Best First'.

Re^3: Effectively handling prerequisites during continuous integration
by BrowserUk (Patriarch) on Jun 11, 2015 at 10:22 UTC

Still sounds like your allowing your process to be driven by every random change in every one of your dependencies; rather than by the need of your own code.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority". I'm with torvalds on this

In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked

[reply]