Superb explaination bro, I was looking this process since long but didn't get a chance to deep dive into it. was just imagine how these code push connected with the Orchestrator :D. Thanks
Excellent tutorial . Could you please make a detail video on Automation Ops - source control in this month? I need to present this topic in front of the team?
21.11 when we are making changes to the UIpath studio code shouldn’t it be auto deploy to Git hub ? Why are we pushing the new version of code through GitHub commands? Can you explain this?
No it shouldn't, that would be a perfect recipe for disaster and confusion. If everytime changes are done on the code are automatically pushed to Git, soon you would have problems, specially if you have CI/CD pipeline in place, that gets triggered per each new commit and does package deploy... either because the code commited wasnt't ready, or because wasn't functional or tested yet, etc... being pushed when it shouldn't. That's why you have to do it intentionally, saying clearly the change reason on the commit message, and then, push the change to the repo. Of course you can have multiple branch strategy, which I recommend, at least one for dev and another for prod releases, and just commit to dev branch, and just using the main/master branch with code merged and ready to deploy from dev, but stills you have to commit to some branch, and the code should be commited with intention and reason, and have control over what goes into the repo and when.
Usually in repo when we push code we just put jenkins file and no need to create seprate pipeline per project how do we manage here as for each project or repo we are creating new pipeline
As far as I know, you will need to create a pipeline per each project/repo. However, Automation Ops Pipelines stills too new (and in preview), so this might change in the future.
Already had fair share of issues with using Git from Studio. I prefer to suggest and show on what I believe to be the best, which on this case was the Git Bash. If you want to learn about using Git from Studio, there are plenty of tutorials on TH-cam😉
![Warhammer 40k: Space Marine 2 | เพื่อจักรพรรดิ ! [ตอนเดียวจบ]](http://i.ytimg.com/vi/4M0ckYMA4-U/mqdefault.jpg)
Superb explaination bro, I was looking this process since long but didn't get a chance to deep dive into it. was just imagine how these code push connected with the Orchestrator :D. Thanks
Thanks a lot for the feedback :D You're welcome 😊
Great stuff as always, Marcelo. Thanks for posting 🙂👍
Thank you so much for the support Jeppe! 💪🏻😄
Excellent tutorial . Could you please make a detail video on Automation Ops - source control in this month? I need to present this topic in front of the team?
Excelente tutorial 👏🏻 tudo muito explícito
Muito obrigado pelo feedback 😃
Very good video 👍👍👍
Thank you for the feedback!💪🏻
Good video
Thank you!
Hi, I exactly follow same steps, but it stucks in "Building" stage. What can be wrong?
21.11 when we are making changes to the UIpath studio code shouldn’t it be auto deploy to Git hub ? Why are we pushing the new version of code through GitHub commands? Can you explain this?
No it shouldn't, that would be a perfect recipe for disaster and confusion. If everytime changes are done on the code are automatically pushed to Git, soon you would have problems, specially if you have CI/CD pipeline in place, that gets triggered per each new commit and does package deploy... either because the code commited wasnt't ready, or because wasn't functional or tested yet, etc... being pushed when it shouldn't. That's why you have to do it intentionally, saying clearly the change reason on the commit message, and then, push the change to the repo.
Of course you can have multiple branch strategy, which I recommend, at least one for dev and another for prod releases, and just commit to dev branch, and just using the main/master branch with code merged and ready to deploy from dev, but stills you have to commit to some branch, and the code should be commited with intention and reason, and have control over what goes into the repo and when.
Usually in repo when we push code we just put jenkins file and no need to create seprate pipeline per project how do we manage here as for each project or repo we are creating new pipeline
As far as I know, you will need to create a pipeline per each project/repo. However, Automation Ops Pipelines stills too new (and in preview), so this might change in the future.
6:25 should have at least shown how to do it from Studio…
Already had fair share of issues with using Git from Studio. I prefer to suggest and show on what I believe to be the best, which on this case was the Git Bash. If you want to learn about using Git from Studio, there are plenty of tutorials on TH-cam😉