Please make more real-world videos like this. I've been searching for a channel that actually dives into "real-world" project piece by piece instead of providing a simplified example.
@cloudonaut2 жыл бұрын
Thank you very much for your motivating feedback.
@ansizfark2 жыл бұрын
You guys are so knowledgeable! I love your AWS content, so helpful to me studying for my DevOps Engineer renewal exam.
@cloudonaut2 жыл бұрын
Thanks a lot for your kind words. All the best for your DevOps certification.
@ayencoscolfield33122 жыл бұрын
just discovered your channel but am loving it , thanks and good job
@cloudonaut2 жыл бұрын
Glad you enjoy it!
@kaedien Жыл бұрын
Fantastic content as always, keep it up!
@cloudonaut Жыл бұрын
Thanks!
@christianibiri2 жыл бұрын
Great video guys
@cloudonaut2 жыл бұрын
Thanks so much!
@Sam-nn3en Жыл бұрын
the wave deployments at 15:19 sounds like canary deployment
@cloudonaut Жыл бұрын
Yes, kind of.
@meras15499 ай бұрын
One remark. You don't do Linting only in pipeline unless you pay for cloud costs by yourself :) Linting should be done at very early stage so you should have scripts to lint you code locally and then next step is to lint code during push and last is lint before merge. So linting in build is as well OK but before that you have bunch of tests before you will trigger build.
@cloudonaut9 ай бұрын
Yes, lint before tests. I also agree that you should be able to run all the steps locally as well.
@yangzhihong5212 жыл бұрын
amazing
@pjpj652 Жыл бұрын
I am not able to understand why would pipeline needs to update itself as you mentioned from 19:48 onwards.
@cloudonaut Жыл бұрын
In GitHub Actions, if you change the workflow, it just works. In CodePipeline, you have to update the pipeline yourself.
@prerakhere Жыл бұрын
how to have that self updating pipeline stage?
@cloudonaut Жыл бұрын
You can find an example in CloudFormation here: github.com/widdix/aws-velocity/blob/master/deploy/pipeline.yml#L164-L181
@sbuckle1171 Жыл бұрын
Sorry, I'm not understanding why the 3rd stage is called Commit. Why not call it 'Build Image'? Commit often refers to a change in the source code which would be your trigger for your build, assuming you've configured your CI/CD system to automatically push and merge commits into your branch.
@cloudonaut Жыл бұрын
We use the terms introduced in the "Continuous Delivery" book by Jez Humble and David Farley. Check out www.informit.com/articles/article.aspx?p=1621865&seqNum=4 to learn more.
@arunramachandran87172 жыл бұрын
Thanks for the amazing content regarding codepipeline. Where can I find the sample pipeline files for matbot and other samples you showed in the slides?
@cloudonaut2 жыл бұрын
Check out cloudonaut.io/configure-your-cloudformation-managed-infrastructure-with-parameter-store-and-codepipeline/ for an example.
@luvrahooo Жыл бұрын
How to trigger code pipeline in case of pull request?
@cloudonaut Жыл бұрын
I don't think that this will easily work. CodePipeline is designed to work with a single branch.
@0xccd2 жыл бұрын
Is it possible to dynamically chnge the source before running the pipeline? I'm interested on running the same pipeline for different repositories
@cloudonaut2 жыл бұрын
I don't think, that's possible. But it is possible to define multiple sources.
@0xccd2 жыл бұрын
@@cloudonaut I found out that you can use codebuild. Basically, you can provide the project and repo info by using env vars, then trigger the build using the aws sdk and before each execution you overwrite the project and repo info as env vars. This is limited to codebuild, I'm still not sure how to integrate it with pipeline and multiple stages
@XStrikeSuper2 жыл бұрын
What tools or script did you use to run integration tests?
@cloudonaut2 жыл бұрын
It depends on the project. For example, we have been using JUnit for a Java project to write integration tests. For Node.js we are typically using mocha.
@XStrikeSuper2 жыл бұрын
@@cloudonaut if I understand correctly integration tests are hitting real services? I typically use jest for unit testinf but never tried for integration tests