Viewing profile — jpdel
jpdel
HN member- Joined
- Wed, Mar 13, 2019, 11:29 AM UTC
- HN karma
- 145
- Public activity
- 34 items
- HN profile
- View on Hacker News ↗
About jpdel
No profile information was provided.
Recent public activity
- story
- story
-
comment
Comment #21681989
Also using Azure DevOps and it is indeed very well structured. As for CI/CD differences: how many commits can actually affect code and infrastructure? I think this is part of the e…
-
comment
Comment #21681762
I think this is a business trend unfortunately. Tools tackling the CI space wanted a piece of CD and then boom. Things became the same :)
-
comment
Comment #21680488
Agree. I would definitely put any infrastructure thing on the CD side though, as it is longer indeed. You can test your software faster in CI using Docker compose. Something along …
-
comment
Comment #21680295
Is this doing anything else than leveraging Docker multi layers caching?
-
comment
Comment #21680276
We have a large Java monolith application. Builds ran for 30 minutes. Then we said let's only run the unit tests and critical smoke tests. The build time went down to 7 minutes ...…
-
comment
Comment #21680265
What about splitting it in smaller parts? And apply the CI process to each module?
-
comment
Comment #21680261
Agree. CI=3-7 minutes. CD can be 30-60 if needed.
-
comment
Comment #21680244
Agree. Some faulty commits may go through. But then you strengthen your test suite to prevent similar issues to happen again, and so on.
- story
-
comment
Comment #21511964
> There's no need to as I mentioned that you're going to be hosting it somewhere during development anyway. You will probably host 1 version which is infrastructure heavy and not v…
-
comment
Comment #21511945
nock will intercept http requests in the same node process it is used in. Here the test (and the mock) are in a different container and thus process. It won't catch them. Unless it…
-
comment
Comment #21511935
I didn't know about dotmess. I'll check it out. Thanks for the tip.
-
comment
Comment #21511930
What tests are which kind depend on your use case. And is an infinite debate. I don't really care how you call them :)
- story
-
comment
Comment #19700009
I've updated the sentence with "Here are the common objections one might have and a tentative solution" and extended the conclusion to say "TBD is not the only way to work"
-
comment
Comment #19699847
Ok thanks. Won't post articles as Show HN in the future.
-
comment
Comment #19699679
Agree that feature flags count should not explode because you can never test all combinations. Feature toggles should drive the life span of a feature from start of development to …
-
comment
Comment #19699658
Fair enough. You have a valid point on "your objections are not valid" is not the right tone. I'll edit to highlight that feature branches have their benefits in some cases. Thanks…
-
comment
Comment #19699638
Not sure how the title is provocative? Even less click baity. And is there a rule I am not aware of against submitting my own posts?
- story
-
comment
Comment #19668448
Flipt is an interesting concept! I've tracked you down on Twitter. Let's talk when you have time ;)
-
comment
Comment #19668402
k8s is open source, which is a different setup: you can't just merge in anything that comes in. In commercial projects though, even with a large team, you should be able to trust a…
-
comment
Comment #19666982
And now that I look at your question again: yes. If all 23 builds were green and one person merges, then it would trigger a build on the remaining 22. The thing being that you prob…