| ▲ | rr808 4 days ago |
| Surely everyone has a CI pipeline that wont allow merges with failing tests? |
|
| ▲ | jmount 4 days ago | parent | next [-] |
| This if the case where you introduce the test after the failure. |
|
| ▲ | ervine 4 days ago | parent | prev | next [-] |
| More than one assumption in that sentence, ha! |
| |
| ▲ | trenchpilgrim 4 days ago | parent [-] | | Including "code is delivered in a way that involves merges" | | |
| ▲ | ervine 4 days ago | parent [-] | | This feels like a "is a hotdog a sandwich?" situation. "Is sftp-ing to prod a merge?" | | |
| ▲ | trenchpilgrim 4 days ago | parent [-] | | My team follows good practice but I deal with a vendor who emails us a ZIP file :scream: | | |
| ▲ | ervine 4 days ago | parent [-] | | Honestly it's kind of refreshing to just push files to a server. | | |
| ▲ | trenchpilgrim 4 days ago | parent [-] | | I've been telling people for years, if the process to deploy to an environment is more complicated than one click, it's too complicated! |
|
|
|
|
|
|
| ▲ | thealistra 4 days ago | parent | prev [-] |
| But most CIs allow flaky tests :) |
