[JIRA] [git-client] (JENKINS-21137) git fetch does not have support for --progress option in 1.7.x version of git client binary
Corey OConnor commented on JENKINS-21137 git fetch does not have support for --progress option in 1.7.x version of git client binary Looks like the option was added here: https://github.com/jenkinsci/git-client-plugin/commit/a3d3d548842d6a9bafbf9f2eb45729478be7dbbc 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/groups/opt_out.
[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes
Corey OConnor commented on JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes As indicated in comment #3: command line executable version 1.8.4.4 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/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20843) build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace
Corey OConnor created JENKINS-20843 build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow Created: 02/Dec/13 9:03 PM Description: The build flow job type does not initialize the project's workspace. However, this project supports options, like SCM, that require a workspace to be initialized. This means: build-flow projects cannot use SCM build-flow projects cannot be triggered by SCM changes if that trigger requires a workspace. Due to JENKINS-20767 all Git triggered projects currently require a workspace. build-flow projects cannot use any post-build action that assumes a workspace. EG: archive artifacts Project: Jenkins Priority: Major Reporter: Corey OConnor 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/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20843) build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace
Corey OConnor updated JENKINS-20843 build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace Change By: Corey OConnor (02/Dec/13 9:04 PM) Description: Thebuildflowjobtypedoesnotinitializetheprojectsworkspace.However,thisprojectsupportsoptions,likeSCM,thatrequireaworkspacetobeinitialized.Thismeans:#build-flowprojectscannotuseSCM#*build-flowprojectscannotbetriggeredbySCMchangesifthattriggerrequiresaworkspace.DuetoJENKINS-20767allGittriggeredprojectscurrentlyrequireaworkspace.#build-flowprojectscannotuseanypost-buildactionthatassumesaworkspace.EG:archiveartifacts committhatintroducedissue:https://github.com/jenkinsci/build-flow-plugin/commit/444097d65ecb97c92005b3acd63db8e03bdeb6a3 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/groups/opt_out.
[JIRA] [core] (JENKINS-15911) needs to build from client workspace
Corey OConnor commented on JENKINS-15911 needs to build from client workspace This seems unrelated to the build flow plugin. This also does not seem like a major bug. Or a bug at all. This can be accomplished using a development branch and git plus the normal jenkins workflow. Is there any issue with this? 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/groups/opt_out.
[JIRA] [build-flow] (JENKINS-20843) build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace
Corey OConnor commented on JENKINS-20843 build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace I'd expect the requirements of a build steps should be something jenkins would filter on. As for archive artifact: That "archive artifacts" doesn't make sense for a build flow job is an example of the issue. If archiving artifacts does not make sense then the step should not be selectable in the UI. Anyways, sounds like properly resolving this issue requires changes to jenkins core. 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/groups/opt_out.
[JIRA] [core] (JENKINS-15911) support building from a users local checkout (?)
Corey OConnor updated JENKINS-15911 support building from a users local checkout (?) Adjusting title to be closer to what I think the submitter intended. Removing build flow component. Change By: Corey OConnor (02/Dec/13 8:59 PM) Summary: needstobuild supportbuilding from clientworkspace auserslocalcheckout(?) Issue Type: Bug NewFeature Priority: Major Minor Component/s: core Component/s: build-flow 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/groups/opt_out.
[JIRA] [git] (JENKINS-20861) git plugin 2.0 does not correctly migrate 1.5 configs using reference repo option
Corey OConnor created JENKINS-20861 git plugin 2.0 does not correctly migrate 1.5 configs using reference repo option Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 03/Dec/13 10:28 PM Description: The GitSCMBackwardCompatability class does not migrate the reference repo option. https://github.com/jenkinsci/git-plugin/blob/master/src/main/java/hudson/plugins/git/GitSCMBackwardCompatibility.java Note there is no part of readBackExtensionsFromLegacy that adds a CloneOption instance or set the "reference" member. Project: Jenkins Priority: Minor Reporter: Corey OConnor 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/groups/opt_out.
[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes
Corey OConnor commented on JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes The workaround of using "Force polling within workspace", a DisableRemotePoll extension instance, does not work for Build Flow projects. Those no longer initialize a workspace. I believe that is an issue with the build flow plugin. 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/groups/opt_out.
[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes
Corey OConnor commented on JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes Confirmed. On my system. What additional information is required to investigate this? 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/groups/opt_out.
[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes
Corey OConnor
commented on JENKINS-20767
Git plugin 2.0: Git polling causes builds even if no changes
Command line executable. Git version 1.8.4.4
Other observation: We use the multiple SCMs plugin. Which is known to be problematic. In this case the issue is not isolated to jobs that use that plugin. All jobs are affected.
I've adding the DisableRemotePoll option to all jobs. This resolved the issue for me. The script I used is:
import jenkins.model.*;
import hudson.model.*;
import hudson.tasks.*;
import hudson.plugins.git.*;
import hudson.plugins.git.extensions.impl. DisableRemotePoll;
def updateScm(project, scm) {
println("updating " + scm.toString() + " for project " + project);
remote_poll_opt = new DisableRemotePoll();
scm.extensions.add(remote_poll_opt);
project.save();
}
for(project in Hudson.instance.items) {
scm = project.scm;
if (scm instanceof org.jenkinsci.plugins.multiplescms.MultiSCM) {
for(actual_scm in scm.getConfiguredSCMs())
updateScm(project, (GitSCM)actual_scm);
} else if (scm instanceof hudson.plugins.git.GitSCM) {
updateScm(project, (GitSCM)scm);
} else {
println("unknown scm type " + scm.toString());
}
}
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/groups/opt_out.
[JIRA] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Corey OConnor commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Since my previous comment I have noticed two incidents of 100% cpu usage from a zip compression thread that appears "stuck". Either org.kohsuke.stapler.compression.CompressionFilter.disabled=true reduces the frequency ; a different path results in the same behavior ; or the reduction in frequency is all by chance. 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/groups/opt_out.
[JIRA] [core] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
Corey OConnor commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException We are using jenkins 1.484 and are experiencing the same issue. The "-Dorg.kohsuke.stapler.compression.CompressionFilter.disabled=true" option did result in the threads no longer taking 100% CPU. However, this broke loading the CSS. Perhaps due to what Walter Kacynski noticed. 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/groups/opt_out.
[JIRA] (JENKINS-15356) NPE caused executor thread death
Corey OConnor commented on JENKINS-15356 NPE caused executor thread death Reproduced on 1.484. This was on a new jenkins instance. No build history. Exception in thread "Executor #0 for alfred_0" java.lang.NullPointerException at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:220) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:66) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1197) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:136) at hudson.model.Executor.run(Executor.java:211) 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
