[JIRA] (JENKINS-37118) No Build Without Changes, Anymore
Title: Message Title Ingo Mohr commented on JENKINS-37118 Re: No Build Without Changes, Anymore Mark, Thanks for the quick answer. We'll (have to) check the other alternatives. Thx for advice. If more users should request the "build anyway" behavior, maybe there's a way to add a config option for this... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.
[JIRA] (JENKINS-37118) No Build Without Changes, Anymore
Title: Message Title Ingo Mohr created an issue Jenkins / JENKINS-37118 No Build Without Changes, Anymore Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2016/Aug/02 11:46 AM Labels: build stash bitbucket Priority: Major Reporter: Ingo Mohr In V2.3.5 of the git plug-in polling without detecting changes caused a build to run. With V2.3.6 and later this is no longer true. We think the issue that changed this was: https://issues.jenkins-ci.org/browse/JENKINS-29066 This, however, is a problem now. We host our Git repos on Bitbucket (former Stash). Sometimes, we have to invoke "Trigger Build" even when there were no changes pushed to the Git repos. Since that trigger causes a polling for changes, this has no effect anymore with a version newer than V2.3.5. Why Do We Need This, Anyway? Build results can depend on external systems. If external systems are not available or not correctly configured, the build results are Failed. Now, if we fix those external systems problems, we want to just re-trigger the job to rebuild again.
[JIRA] [git-plugin] (JENKINS-21536) GIT_BRANCH should not change after merge
Ingo Mohr commented on JENKINS-21536 GIT_BRANCH should not change after merge Same problem here. We locally merge a feature branch (or bugfix branch) to master in order to check whether the branch can be merged later with a pull request. And for this, we need the "actual" feature branch name. But on Jenkins, the name of the $GIT_BRANCH is always "master" once we've locally merged. Maybe, an all-new variable should be added since the GIT_BRANCH name actually is "master. It's just: we need the name of the branch merged before building. 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.
