Quick update: Rainer's comment was not removed by him, but it was categorized as "Probably spam." I haven't noticed that, but when I did, I approved the comment so you can find it in the previous video. Lesson learned, need to pay more attention to comments that are awaiting approval in the moderation queue :-)
@rainerhaseneder2480
4 жыл бұрын
@Szymon Thank you so much for so diligently answering the questions and thus giving more insight ! I really appreciate it. No problem with using my name and referring to my questions. This is why we have this excellent media. :-)
@szymonstepniak
4 жыл бұрын
Thanks again, Rainer! My concern was caused by KZitem marking your question for the moderation queue. I get the email with a copy of your question, but no information I need to approve it (for some odd reason.) That is why I thought it was removed, but luckily I was wrong, and the question is right where it belongs, under the previous video. I hope you will find other videos equally interesting. Take care!
@rahul_bali
3 жыл бұрын
@@szymonstepniak Great. people can use any name on KZitem, which keeps the essence of true internet alive.
@boehmch1
3 жыл бұрын
I must say, I am using Jenkins for a while now, but this video and the previous one were clearer than everything else I've consumed until now on this topic. AMAZING JOB!
@szymonstepniak
3 жыл бұрын
Wow, thank you for your kind words, Chris! I hope you find other videos useful as well. Let me know if there is any topic that interests you most - I build up my videos backlog based on the community feedback, and I would love to hear it from you. Have a good day!
@jresendiz27
4 жыл бұрын
Hey! Nice video! I've been working with Scripted pipelines for at least 8 months, in our engineering team we say an important benefit over a declarative one, the customization we required due some business rules (like some validations for git, integration with Jira, Slack, Phabricator, etc). Another benefit we say was that we could Test all of our generated logic and how it integrated with the rest of the plugins using Spock. The most difficult par of it it's understanding that the Shared Libraries (and the scripted pipelines) are not really Groovy Code, some annotations, features of the language were not able to be used. Now we provide support for ~100 productive pipelines using just one shared library and it's been a lot of fun :D
@szymonstepniak
4 жыл бұрын
Nice! That is a really good example of using pipelines combined with Jenkins Shared Library. We do the same at the company I work for, but the story is different - after using a scripted pipeline for about a year, we decided to migrate to the declarative pipeline for our shared library back in 2018. It was mostly requested by the pipeline library users - they were missing e.g. restart from specific stage feature, which couldn't be implemented with the scripted pipeline. Our use cases prove, that the final decision depends on the specific context. Scripted pipelines are still widely used by the industry, but also the movement towards declarative pipeline is growing. We should pick whatever fits better our specific use case and don't be dogmatic about the technology. Thanks, Juan for a great comment! Have a good day!
@stith_pragya
2 жыл бұрын
Hello Szymon, Thanks for this great video.👍👍👍👍👍👍👍👍
@szymonstepniak
2 жыл бұрын
Thank you for your kind words, Tushar! Take care, and have a good day!
@RichardBronosky
3 жыл бұрын
@Szymon and @Rainer, you are both Legends! Such great delivery and community. And when I saw that sick Depth Of Field at 2:15 I subscribed. ☮️❤️🌈
@szymonstepniak
3 жыл бұрын
Thank you so much for such warm words, Bruno! I value the aesthetic side of videos, and I love to hear that there is someone like you who appreciates it too :) Welcome aboard, and have a good day!
@edgarlip2
4 жыл бұрын
it can be great for a coder student to have a great code course for groovy (Jenkins related from a to z ) , right now it looks like the world miss it /needs it ... nice video btw =)
@szymonstepniak
4 жыл бұрын
Thanks, Edgar! You can expect more Jenkins Pipeline related videos soon.
@kc3020
3 жыл бұрын
great video and explanation...
@szymonstepniak
2 жыл бұрын
Thank you!
@MaxMautner
3 жыл бұрын
These are good questions to be asking, thank you for answering them
@szymonstepniak
3 жыл бұрын
Thanks for your kind words, Max! I'm glad you found this video useful. Have a good day!
@Prainnam
3 жыл бұрын
fabulous explanation
@szymonstepniak
3 жыл бұрын
Thanks for your kind words, Prak! Take care, and have a good day!
@irynadiudiuk4535
4 жыл бұрын
Again a very informative video. Thank you! You have mentioned shared libraries. Is there any benefit using those with declarative pipeline instead of the scripted ones?
@szymonstepniak
4 жыл бұрын
Thanks, Iryna! 🙏 Jenkins Shared Library is a way to share the common code between multiple Jenkinsfiles without much hustle. You can use them either with the declarative or scripted pipeline. I was working on a single project with a single Jenkinsfile, or maybe a few ones without much code shared between them, I would keep using a declarative pipeline without introducing a shared library. I'm working in a company where we have 200+ pipelines maintained by different teams, with a common behavior (build, test, deploy), and this is where Jenkins Shared Library shines bright. We can distribute changes without disturbing other people, and they can focus on building their product instead of developing complex delivery pipeline. I would say that this is the best scenario to introduce shared library.
@irynadiudiuk4535
4 жыл бұрын
@@szymonstepniak, I see, thank you for your reply!
@rajindergandhi3437
4 жыл бұрын
Good Learning video
@szymonstepniak
4 жыл бұрын
Thank you, Rajinder! 🙏 I'm glad to hear you find this video useful. Happy coding!
@mohamedruzaik3483
Жыл бұрын
i had the same question
@szymonstepniak
Жыл бұрын
I hope this video helped you find the right answer :) Take care, and have a good day!
@sipirock9383
3 жыл бұрын
what editor you're using sir? that's jenkins editor?
@szymonstepniak
3 жыл бұрын
Hi there! I was using Sublime Text (www.sublimetext.com) in this video. Take care, and have a good day!
@vijaykumary5427
3 жыл бұрын
One more subscription added.. 😊
@szymonstepniak
3 жыл бұрын
Welcome aboard! Take care, and have a good day!
@sonnix31
4 жыл бұрын
Well done. I love your video's.
@szymonstepniak
4 жыл бұрын
👍☺️👍
@gopikalapaneni
3 жыл бұрын
Hi, Ca you pleas e do a video on shared libraries
@szymonstepniak
3 жыл бұрын
Yes, I plan to create a crash-course like video explaining Jenkins shared libraries. Stay tuned and have a good day, Gopi!
@sagarshah901
3 жыл бұрын
Hi how do we call stage from another stage using scripted pipline
@szymonstepniak
3 жыл бұрын
Hi Sagar! What have you tried so far? Did you make any research? Have a good day!
@rajindergandhi3437
4 жыл бұрын
Could yo please give demo on multi branch pipeline
@szymonstepniak
4 жыл бұрын
Hi Rajinder! Anything specific related to the multi-branch pipeline you would like to see? I'm open to any suggestions :-)
@rajindergandhi3437
4 жыл бұрын
@@szymonstepniak Hi, I know the concept. How build is triggerd automatically using multi branch commit by user using pipeline and also I want to know can i change the agent for different stages??
@szymonstepniak
4 жыл бұрын
@@rajindergandhi3437 Automated trigger is usually done through the webhook. All Jenkins plugins, like Git SCM plugin, Bitbucket plugin, or Github plugin support handling webhooks from the remote repository. To make it work, you need to make sure that your remote repository sends webhooks on specific actions (e.g. commit push.) The alternative is "Poll SCM" option which checks if there are changes in the SCM once in a while, however, it might be overkill for Jenkins to check every few seconds if there is anything new to build. Webhooks are much more effective. Some Jenkins plugins, like Bitbucket Server Integration plugin, register webhooks automatically when you set up a Multi-Branch Pipeline job (or even "regular" Pipeline job.) For Git SCM you need to create a webhook manually in the remote repository of your choice. Regarding changing agent in stages - yes, it works. The "agent" block can be specified at the either "pipeline" block level, or at the "stage" block level. Check the Pipeline Syntax documentation for more information - www.jenkins.io/doc/book/pipeline/syntax/#agent
Пікірлер: 42