You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
3This argument is correct, unless it is turned against itself. Having two strongly coupled components (lets call them front end and backend) compiled and tested together and then (re)deployed to production, even when only one of them actually changed (or should have changed), can sometimes be less error prone than testing them together and then deploy only one of them to production. Deploying only the frontend can be interpreted as "backend hasn't changed" (compared to prior version in production), or "backend might have changed" compared to corresponding version in the test environment).Doc Brown– Doc Brown2024-11-01 13:19:28 +00:00Commented Nov 1, 2024 at 13:19
-
... hence I am here with what BenCotrell wrote in a comment: the OP should keep things simple and try out what works best for them.Doc Brown– Doc Brown2024-11-01 13:20:57 +00:00Commented Nov 1, 2024 at 13:20
-
"was there a build process that can potentially pull in a new version of a third party dependency" Even if you haven't pinned your dependencies (which you really, really should be), redeploying should be taking your build artifacts from Artifactory (etc) and working with those. No building anything involved.Philip Kendall– Philip Kendall2024-11-01 14:40:36 +00:00Commented Nov 1, 2024 at 14:40
-
Taking Doc Browns argument and turning it against itself - if an artifact hasn't changed it shouldn't have been deployed to the pre-prod environment (where testing was done) either, so what was tested would be what is deployed in production.DavidT– DavidT2024-11-01 23:25:36 +00:00Commented Nov 1, 2024 at 23:25
-
I agree with Philip Kendall - in a ideal world, builds should be repeatable they should upload to artifact repositories, packaging into VM's or docker containers should be repeatable and they should also go into artifact repos and deploys should only be done from artifact repos - the world is not alway perfect, hence my argument about not deploying when not necessary.DavidT– DavidT2024-11-01 23:29:23 +00:00Commented Nov 1, 2024 at 23:29
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you