If you're using Perforce, you can even shelve a changelist without ever checking it into any branch. Then you can use a Jenkins job to unshelve that changelist, run your tests against the shelved code, and then check in that shelved changelist if your tests pass.
On Thu, Aug 1, 2013 at 11:34 AM, Daniel Beck <m...@beckweb.net> wrote: > There's a commercial plugin that does this if you're using Git: > > > http://www.cloudbees.com/jenkins-enterprise-by-cloudbees-features-validated-merge-plugin.cb > > Developers push to Jenkins' repository, and if that's successful, Jenkins > pushes to your actual repo. > > On 01.08.2013, at 09:16, Avihay Eyal <avihay.e...@gmail.com> wrote: > > > I mean, If I'm a developer, I would prefer to somehow run the automated > tests before I push to the repository, cause > > if an automated test failed and there's a bug in my code, I want to know > that before pushing my change... > > > > How do you approach this problem? > > > > -- > > 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 jenkinsci-users+unsubscr...@googlegroups.com. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- > 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 jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
