[JIRA] [core] (JENKINS-26887) git polling/web hooks need to occur in a separate polling workspace
Jan Klass commented on JENKINS-26887 git polling/web hooks need to occur in a separate polling workspace I still don’t see why a polling workspace would be necessary. Most of the use-case described here seems like a bug report rather than an improvement. What are the actions to be taken that would make a workspace or repository clone necessary? 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.
[JIRA] [core] (JENKINS-26887) git polling/web hooks need to occur in a separate polling workspace
Jeremiah Norris commented on JENKINS-26887 git polling/web hooks need to occur in a separate polling workspace Also it looks like polling won't even be attempted if a build is already running. It doesn't take concurrent builds in to consideration at all. 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.
[JIRA] [core] (JENKINS-26887) git polling/web hooks need to occur in a separate polling workspace
Jeremiah Norris commented on JENKINS-26887 git polling/web hooks need to occur in a separate polling workspace It will execute concurrent builds only if they are kicked off manually. If a build is already running and an new commit comes in to the repository and Jenkins gets notified via web hook Jenkins will just ignore it and continue running the current build instead of starting a concurrent build to build the new commit. 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.
[JIRA] [core] (JENKINS-26887) git polling/web hooks need to occur in a separate polling workspace
Jeremiah Norris created JENKINS-26887 git polling/web hooks need to occur in a separate polling workspace Issue Type: Improvement Assignee: Niklaus Giger Components: core, git-parameter-plugin, git-plugin Created: 10/Feb/15 8:40 PM Description: The main issue I'm trying to solve is I need a web hook to be able to kick off concurrent builds. Whereas right now if a commit comes in to a job that is already building that commit will just be ignored and will never be built. Essentially the why the current git activities work are a little unintuitive since they depend on a local git repository to be sitting in the workspace from a previous build. Instead when a new job is created that has a git repository listed in SCM a local repository should be immediately pulled to be used from polling and webhooks that is completely independant of the job workspace. There are probably more elegant or lightweight solutions to this issue to be explored. I want to see how much interest there is in this subject and if there is anyone more experienced who wants to contribute that would be great, but my team is in dire need of this so I will look into coding if no one else has value for a solution. Project: Jenkins Labels: git Priority: Major Reporter: Jeremiah Norris 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.
[JIRA] [core] (JENKINS-26887) git polling/web hooks need to occur in a separate polling workspace
Jeremiah Norris edited a comment on JENKINS-26887 git polling/web hooks need to occur in a separate polling workspace linking an example of an issue this improvement aims to fix 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.
[JIRA] [core] (JENKINS-26887) git polling/web hooks need to occur in a separate polling workspace
Jeremiah Norris updated JENKINS-26887 git polling/web hooks need to occur in a separate polling workspace Change By: Jeremiah Norris (10/Feb/15 8:42 PM) Description: ThemainissueImtryingtosolveisIneedawebhooktobeabletokickoffconcurrentbuilds.Whereasrightnowifacommitcomesintoajobthatisalreadybuildingthatcommitwilljustbeignoredandwillneverbebuilt.Essentiallythe why way thecurrentgitactivitiesworkarealittleunintuitivesincetheydependonalocalgitrepositorytobesittingintheworkspacefromapreviousbuild.InsteadwhenanewjobiscreatedthathasagitrepositorylistedinSCMalocalrepositoryshouldbeimmediatelypulledtobeused from for pollingand webhooks webhooks thatiscompletelyindependantofthejobworkspace.Thereareprobablymoreelegantorlightweightsolutionstothisissuetobeexplored.Iwanttoseehowmuchinterestthereisinthissubjectandifthereisanyonemoreexperiencedwhowantstocontributethatwouldbegreat,butmyteamisindireneedofthissoIwilllookintocoding it ifnooneelsehasvalueforasolution. 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.
[JIRA] [core] (JENKINS-26887) git polling/web hooks need to occur in a separate polling workspace
Mark Waite commented on JENKINS-26887 git polling/web hooks need to occur in a separate polling workspace The other work around offered in JENKINS-7423 says that a web hook will run concurrent builds if you select "Execute concurrent builds if necessary". I don't understand your statement that git activities depend on a local git repository in the workspace. The default (since git plugin 2.0) is to not require a local workspace for polling. 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.
