What is your favorite solution for pipelines/workflows? Should I explore another one from that category?
@n4870s
3 жыл бұрын
What if we are developing in a microservice env. Does this mean that we should bring up the whole set of services in a temp env to exec some integration tests or should we have the service under test in a temp env working against other integration env? Does argo substitute gh actions?
@DevOpsToolkit
3 жыл бұрын
@@n4870s You definitely should not "bring up the whole set of services in a temp env", unless you have to. Normally, you would use stubs or mock so that during early stages (especially while developing), you can run and test the service without the dependencies. Nevertheless, sooner or later you do need to hook it into the rest of the system. Ideally, you should be working against the production env, so there is no need for the integration env. Ideally, the microservice you are working on is based on the dependencies running in production and not something someone might be releasing some time in the future. However, if that's not the case and if microservices are treated as distributed monoliths then have an integration env to hook into might be a valid alternative.
@n4870s
3 жыл бұрын
@@DevOpsToolkit alright, got it. I get your point about working against prod, but what if my service is modifying state of other services. That would screw production.
@DevOpsToolkit
3 жыл бұрын
@@n4870s Normally, that does not have to be a problem. If, for example, it's an e-commerce site, one of the users in prod might be technical and used by other apps for testing. Still, you're right. That's not an option for all and, in those cases, you can just make a replica of the prod. Copy your prod manifests to a Git repo, change the domains and scale HPA to some lower values (so that it's not too expensive), and you can easily have a replica of the prod. I don't like calling it integration since integration typically means that it is the place where all the future prod releases are deployed and not the (almost) exact replica of prod.
@barefeg
3 жыл бұрын
Small correction. Not only “GitHub events” trigger actions. Workflow dispatch and repository dispatch is exactly for this use case. I wrote a CLI for triggering workflows from a developer terminal, without needing to make a Git operation (which then translated into a standard GitHub event). The develop can send payloads which converts into the workflow inputs
@DevOpsToolkit
3 жыл бұрын
You're right. That was an omission on my part.
@boriphuthsaensukphattraka3397
3 жыл бұрын
Great to see GitHub actions here
@boopathyn6079
3 жыл бұрын
Very Nice explanantion
@spy.catcher
3 жыл бұрын
can you also do a video on the split DNS feature of tailscale and how best to set up your clusters inside your vm's in conjunction with tailscale/taildrop and how it compares to zerotier, etc
@StanleyCruvinel
3 жыл бұрын
Great, I like watch videos about GitHub Actions, many possibilities maybe with Severless in some Cloud, you could show video about Azure Repos is like Git Actions. Is so great do take control of your projects. With Azure Repos you can do parallels jobs.
@DevOpsToolkit
3 жыл бұрын
Great suggestion! Adding it to my TODO list...
@bisdak5761
3 жыл бұрын
i subscribed when you threatened to move my pipelines to travis ci :)
@DevOpsToolkit
3 жыл бұрын
It's good to know that threats work :)
@jakeplissken7494
2 жыл бұрын
Yo please tell me the name of the absolute banger you play at 11:41
@DevOpsToolkit
2 жыл бұрын
Unfortunately, I do not remember anymore where I got it. It's one of the tunes you can purchase (or at least I think I purchased it) for use in videos.
@BrettJamesSuperRoach
2 жыл бұрын
I feel for anything that needs macos (react native, apps) github actions is a bit of a poor choice. The minutes are run at 10x, or in other words $4.80usd an hour. When an xcode build take 30 minutes, that means you can do 7-10 builds in a month if you are lucky.
@DevOpsToolkit
2 жыл бұрын
You're right. Performance, followed by the price, are the main downsides of GHA.
Пікірлер: 18