Am Donnerstag, 1. August 2013, 00:16:46 schrieb Avihay Eyal:
> 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?
Use a script-based job, eventually combined with branch based development.
Developers work on branches (one per task) to which they can commit and which
they can push at will w/o putting the default branch at risk.
You can then let the Jenkins job do the merging of the branch, perform the
build, run the tests and only commit and push the result if none of those
steps have failed.
HTH...
Dirk
http://www.recommind.com
--
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.
