We all should keep in mind, that "production" often means "isolated environment in the field, anywhere in the world, with small embedded systems which might not even be capable of being deployed automatically"
This means, in the real world, true feedback loops are often impossible to implement. To blame the developers that are only using CI in those cases, because that is the most they are able to do, is not the correct thing to do.
The judgement may apply for those fancy, well-connected developers from the hipster web development bubble where true CD can be established.
But there are an awful lot of embedded systems programmers out there who already struggled with manual deployment processes for years and certainly will through the next decades.
For me and my team "only CI" has been a dramatic improvement in code quality and automation of nasty build processes which take hours to complete and took a lot of time before we had a working CI environment.
So I consider "only CI" a great thing overall which should not be blamed that harsh.
Software Delivery Futurist.
Chief Storyteller at https://perfectscale.io.
CEO and founder at https://otomato.io.
Co-founder at https://stagecentral.io.
A great point! Edge and embedded deployments are definitely a largely untackled challenge. But even that is changing today. Look for example at what Zededa zededa.com/ are building.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
We all should keep in mind, that "production" often means "isolated environment in the field, anywhere in the world, with small embedded systems which might not even be capable of being deployed automatically"
This means, in the real world, true feedback loops are often impossible to implement. To blame the developers that are only using CI in those cases, because that is the most they are able to do, is not the correct thing to do.
The judgement may apply for those fancy, well-connected developers from the hipster web development bubble where true CD can be established.
But there are an awful lot of embedded systems programmers out there who already struggled with manual deployment processes for years and certainly will through the next decades.
For me and my team "only CI" has been a dramatic improvement in code quality and automation of nasty build processes which take hours to complete and took a lot of time before we had a working CI environment.
So I consider "only CI" a great thing overall which should not be blamed that harsh.
A great point! Edge and embedded deployments are definitely a largely untackled challenge. But even that is changing today. Look for example at what Zededa zededa.com/ are building.