Comment on Heroku is not deadparentComments−stickfigure6moThat lacks imagination. There's no corporate workflow that can't ultimately translate to moving git tags.−ragall6moPerhaps, but why should one do it when it's a bad model ? Jury because it's possible ?−jeswin6moHow did you objectively decide it's a bad model?−Daviey6moBecause it's more enterprise to open a Service Now ticket and have Joe from IT upload the new content using FTP.−ragall6moI subjectively did based on my experience.−Bombthecat6moExcept you want to track what went to production and what didn't and for how long−jononor6moReleases of a Heroku app is tracked by the platform, and both shown the the UI, in the CLI and available in the API.−stickfigure6moGit is remarkably good at tracking history. CI systems are also great at showing history.
Comments
That lacks imagination. There's no corporate workflow that can't ultimately translate to moving git tags.
Perhaps, but why should one do it when it's a bad model ? Jury because it's possible ?
How did you objectively decide it's a bad model?
Because it's more enterprise to open a Service Now ticket and have Joe from IT upload the new content using FTP.
I subjectively did based on my experience.
Except you want to track what went to production and what didn't and for how long
Releases of a Heroku app is tracked by the platform, and both shown the the UI, in the CLI and available in the API.
Git is remarkably good at tracking history. CI systems are also great at showing history.