If you're working in a repository alone, you can take the simple approach, checkin your change and watch it run in Jenkins. For example, if you're using github and you're working on a fork of the repository, then you're "working in a repository alone".
If you're working on a repository which is shared with others, and where others expect certain branches to remain stable, then you can create a branch (a "feature branch"), create a matching Jenkins job for that feature branch, and submit your changes to the feature branch. When you are satisfied that your changes are good enough, you merge the feature branch to the stable branch so that others can benefit from your work. Mark Waite On Wed, Dec 28, 2016 at 9:00 AM Atul Sharma <[email protected]> wrote: > Thanks mark , Can you please also help me how to do > It once some steps , so that I can check besically I want to check syntax > of my Jenkins file which is wrote in groovy and we are using git where our > Jenkins file exist , so before build Jenkins job I want to check mention > code in same Jenkins futile sysmtax is correct yes or not , > > So that I want to do please help me with steps , > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/3fb01409-934e-4114-a3d8-51418f0622e4%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtH11ncbfSO__0nTq2NTvWck%2BE%3DUisj8kWkn%2BSGoA1jUng%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
