[GitHub] beam pull request #2785: Do not prune branches in Jenkins

2017-04-30 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/beam/pull/2785


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] beam pull request #2785: Do not prune branches in Jenkins

2017-04-29 Thread kennknowles
GitHub user kennknowles opened a pull request:

https://github.com/apache/beam/pull/2785

Do not prune branches in Jenkins

It seems that pruning in Jenkins has bugs which result in
branches being pruned when they should not, resulting in
log spam and build delays.

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

 - [ ] Make sure the PR title is formatted like:
   `[BEAM-] Description of pull request`
 - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
   Travis-CI on your fork and ensure the whole test matrix passes).
 - [ ] Replace `` in the title with the actual Jira issue
   number, if there is one.
 - [ ] If this contribution is large, please file an Apache
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.pdf).

---

R: @jasonkuster 

Reverting my prior change. The prior change supports changing the refspec, 
but I suspect bugs in this feature are behind unreasonable behavior such as the 
git fetch here: 
https://builds.apache.org/job/beam_PreCommit_Java_MavenInstall/10329/consoleFull

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/kennknowles/beam no-prune-jenkins

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/beam/pull/2785.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #2785


commit cc66e2defff592efbbc3755b16fe74ff2ae0d011
Author: Kenneth Knowles 
Date:   2017-04-30T04:25:03Z

Do not prune branches in Jenkins

It seems that pruning in Jenkins has bugs which result in
branches being pruned when they should not, resulting in
log spam and build delays.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---