[JIRA] [git] (JENKINS-24833) Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds

Fri, 26 Sep 2014 06:10:07 -0700

Mark Waite commented on Bug JENKINS-24833

Loren Klingman I tried to duplicate the problem you're seeing with a smaller case and couldn't. Could you attempt to narrow the failure mode further?

I tried:

  1. Create a freestyle job JENKINS-24833-git-publishes-always
  2. Configure it to use a git repository
  3. Add an XShell build step "python add_a_file.py" which runs a python script to add a file to the repo
  4. Add a git publisher step to push to the origin remote, master branch
  5. Confirm that job succeeds and the change is pushed
  6. Add a failing build step after the XShell build step (I used XShell with the command "false" and I used a call to ant)
  7. Confirm that job fails and the change is not pushed

I also tried a variation:

  1. Add a failing post build action (I used publish JUnit reports when the job has no JUnit results)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to