Introducing the worldโs most intelligent CI/CD solution, with self-tuning pipelines that wonโt ever break your dev flow.
New from JetBrains.
Replies
Best
It looks great! Regular CI/CD tools can be challenging for mid to large teams, but this product should significantly boos efficiency. I will definitely give it a try!
@bonvisions thanks Bon! Yeah we built TeamCity Pipelines specifically with small to mid size teams in mind. Looking forward to your feedback if you get to try it!
Report
Looks amazingly easy to configure, I cannot wait to try it when it supports .NET
@laurent_kempe Thanks! You can build your .NET projects through CLI commands right now and dedicated .NET runner support (for easier setup, optimizations like 1-click parallel testing and more) will come in the next couple weeks.
๐ Congratulations on the launch of TeamCity Pipelines by Jetbrains! This is an exciting development for developers. How do you foresee TeamCity Pipelines revolutionizing the development process for teams?
@yasec_kowalski We simply want teams to need to worry less about their CI/CD tool, in terms of ease of use, time spent learning about, configuring, maintaining and then also running, optimizing & debugging their pipelines - they should be able to focus on development instead.
Revolutionizing the entire development process for teams is probably a bit much to ask for a CI/CD system, but we're super stoked if we nail everything I mentioned above.
Exciting news! ๐ TeamCity Pipelines has officially launched with a well-designed, user-friendly UX/UI. As a proud member of the UX/UI team, having contributed to the user needs analysis, in-depth user research, and refinement of the entire user experience, I'm especially eager to hear your feedback to continue making improvements.
Congratulations to the entire team on this remarkable achievement!
@tanya_konvaliuk you designed an incredible good looking (and logically functioning!) product, Tanya. Kudos ๐
Report
yaml imported from the repo would be really great addition. Most annoying thing is to keep it in-sync.
I'm personally not a fan of these visual builders, but keeping pipeline along with the code is pretty useful imo.
eg:
Backend repo / build.yaml (describes how to build and deploy this particular thingy)
Frontend repo / build.yaml (how to do the same with frontend)
e2e-tests repo / build.yaml (run tests once 2 below are green and run on real env some tests)
TC UI which detects/combines 3 build.yamls from above to one single pipeline and perform some "promote.yaml" (or one huge build.yaml for monorepo use-case)
Report
@sidney3172 this is truly useful feedback, and I've already added it to our YAML improvements bucket! As we've just hit Beta, there is still room for a lot of improvements, and improving on how we process YAML is one of the key areas for sure.
i tried https://david.teamcity.com/ but got this error, and I didn't get any email, so re-registered, but david was already booked, so I had to choose an another name :(
@david_sipos Sorry, there was a technical hiccup with the registration. One of our engineers will reach out to you today or tomorrow and your instance will be made available!
Replies
JetBrains
JetBrains
JetBrains
JetBrains
JetBrains
JetBrains
JetBrains
Retexts
JetBrains
Wingman Studio
Wingman Studio
Wingman Studio
Wingman Studio
JetBrains
JetBrains