[JIRA] [core] (JENKINS-18313) H cron syntax - cannot specify between 10 pm and 6 am
Dave Ohlsson commented on JENKINS-18313 H cron syntax - cannot specify between 10 pm and 6 am Have you tried "0-6" "0-6" would work, of course, but that's not what I want. maybe it fails because your example crosses into the next day? Yes, my example fails precisely because it crosses into the next day. So, how should one specify "any time between 10 pm and 6 am"? 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] [xvfb] (JENKINS-18094) Xvfb plugin doesn't write any error message in build log
Aleksey Alekseev commented on JENKINS-18094 Xvfb plugin doesnt write any error message in build log I test it on ~100 builds. Everything is fine ) 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-17347) xpath functions are broken in API (Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. is back)
benza commented on JENKINS-17347 xpath functions are broken in API (Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error. is back) I am stuck with version 1.500 because of this bug. will it be fixed any time soon ? 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] [warnings] (JENKINS-18290) cpplint.py outputs not handled by Warnings plugin
Gerard Kempff
commented on JENKINS-18290
cpplint.py outputs not handled by Warnings plugin
I used the latest "cpplint.py" downloaded from "http://google-styleguide.googlecode.com/svn/trunk/cpplint/cpplint.py".
It seems that there is an extra ":" in the latest message format and without the "()" around the line numbers, see below:
/opt/ros/fuerte/stacks/Mule/Mapping/Local_map/src/LocalCostMap.cpp:399: Missing space before { whitespace/braces 5
/opt/ros/fuerte/stacks/Mule/Mapping/Local_map/src/LocalCostMap.cpp:400: Tab found; better to use spaces whitespace/tab 1
Thanks!
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] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor commented on JENKINS-15128 Renaming job doesnt work with Git As I said in the PR 14, this is not this simple The last time I looked at it, I was stuck on some svn/git differences in behaviour (having to rely on a generic layer for SCM manipulations is not always obvious). This makes me wondering if current issue is "fixable" given the current state of the project. It might be handled if I was dropping the use of scm API (that is to say, reimplement only my needed commands) and use jenkins' own credential api (see JENKINS-18129) 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] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git
Sebastian Schuberth commented on JENKINS-15128 Renaming job doesnt work with Git Would extending the upstream Jenkins SCM API to your needs then be an option? That at least sounds to be less work than using the credentials API yourself, and other plugin developers would benefit from your work, too. 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] [other] (JENKINS-18104) Daily HTTP traffic problem on network
Ken Van Hoeylandt updated JENKINS-18104 Daily HTTP traffic problem on network Change By: Ken Van Hoeylandt (18/Jun/13 8:45 AM) Description: WheneverweturnonJenkinsonourbuildserveratwork,everydayinthemorning(whenpeoplearrive)HTTPtrafficonourinternetconnectionseemstobebroken. WhenweturnoffTomcat(which It only runstheadminwar happenswhenJenkinsisactive and our Jenkins ),wedon jobsarerunning.Theamountofjobsdoesn t have seemtoinfluence the occuranceoftheissue.WhenIletJenkinsrunningbutdisablealljobs,the problem goesaway . IthappensalsowithanewerJenkinsversion(1.509.1). WhenourHTTPtrafficisbroken,datain-orout-boundonport80and443failsmostofthetime(butnotalways).Otherdatacomesthroughjustfine(e.g.email,SSH).Weranasoftwarepackageontheservertoseetheactiveconnectionsonthatmachine,butwecouldntseeanythingoutoftheordinary.Wheneverourinternetisbroken,theonlywaytofixitistorestartourmodem.WetriedinstallinganewerFritz!Box,butitdidntsolvetheproblem.IhaveGoogledthisissue,butIdidntgetanyclosertofindingapossiblecause(letaloneasolution)tothisproblem.Situation:WehaveaLANwhereourbuildmachineisplacedin.ThisbuildmachineisonlyaccessiblefromtheLANitself.TheLANisconnectedtotheinternetthroughaswitchandthentoaFritz!Boxmodem/router.OtherdevicesconnecttotheLAN(andthebuildmachine)throughcableorWiFi.[edit]CoulditbethatJenkinsoroneofthepluginsopenstonsofconnectionsandthattheseconnectionsareneverclosed?E.g.coulditbethegitpluginthatpollseveryminutefornewsourcecodeandthatitdoesntclosetheconnectionproperlyaftereachpoll?[edit2]Ourmodemlogsalsodidntshowanythingsuspicious 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] [ant] (JENKINS-18380) Processing failed due to a bug in the code - NPE in Ant task
Pawel Gronkiewicz created JENKINS-18380 Processing failed due to a bug in the code - NPE in Ant task Issue Type: Bug Assignee: Unassigned Components: ant Created: 18/Jun/13 9:26 AM Description: During one of the ant targets invoked in Ant step I got the following error: 09:59:52 ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com 09:59:57 java.lang.NullPointerException 10:00:02 at hudson.tasks.Ant.buildFilePath(Ant.java:240) 10:00:07 at hudson.tasks.Ant.perform(Ant.java:165) 10:00:12 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 10:00:17 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) 10:00:22 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:829) 10:00:27 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:780) 10:00:27 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) 10:00:27 at hudson.model.Run.execute(Run.java:1576) 10:00:27 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:486) 10:00:27 at hudson.model.ResourceController.execute(ResourceController.java:88) 10:00:33 at hudson.model.Executor.run(Executor.java:241) 10:00:33 project=hudson.maven.MavenModuleSet@6ca4040a-- Environment: Jenkins 1.517, Ubuntu 10.04 slave Project: Jenkins Priority: Major Reporter: Pawel Gronkiewicz 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-14079) LDAP authentication crashes
evernat commented on JENKINS-14079 LDAP authentication crashes If it works with Jenkins 1.470 or later, this issue can be closed? 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-14134) Configure breadcrumb on slaves in the sidebar goes to /configure
evernat commented on JENKINS-14134 Configure breadcrumb on slaves in the sidebar goes to /configure I do not reproduce the issue with Jenkins 1.517. Do you reproduce it? 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-18381) Some node properties do not make sense as global node properties
stephenconnolly created JENKINS-18381 Some node properties do not make sense as global node properties Issue Type: New Feature Assignee: Unassigned Components: core Created: 18/Jun/13 9:50 AM Description: Since 1.472+ it has been possible to configure the master node's own properties. There are some node properties that do not make sense as a global node property. Up until Jenkins 1.472 the way to mark properties as such was to return false from NodePropertyDescriptor.isApplicable(clazz) if clazz instanceof Jenkins That technique no longer works as that also means that the property cannot be configured as a node property of the master directly. There needs to be an alternative mechanism for differentiating properties that can be applied to all nodes from properties that can be applied to the master node. Project: Jenkins Priority: Minor Reporter: stephenconnolly 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-18381) Some node properties do not make sense as global node properties
stephenconnolly resolved JENKINS-18381 as Fixed Some node properties do not make sense as global node properties Change By: stephenconnolly (18/Jun/13 9:55 AM) Status: Open Resolved Assignee: stephenconnolly Resolution: Fixed 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-18381) Some node properties do not make sense as global node properties
stephenconnolly commented on JENKINS-18381 Some node properties do not make sense as global node properties Implemented in https://github.com/jenkinsci/jenkins/commit/48e801023123f84ee4eebf60737089f41b44958e 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-18381) Some node properties do not make sense as global node properties
SCM/JIRA link daemon commented on JENKINS-18381 Some node properties do not make sense as global node properties Code changed in jenkins User: Stephen Connolly Path: changelog.html core/src/main/java/hudson/Functions.java core/src/main/java/hudson/slaves/NodePropertyDescriptor.java core/src/main/resources/jenkins/model/GlobalNodePropertiesConfiguration/config.groovy http://jenkins-ci.org/commit/jenkins/48e801023123f84ee4eebf60737089f41b44958e Log: JENKINS-18381 Provide a mechanism to differentiate between node properties that are applicable to the master node only and node properties that can be applied to all nodes 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] [redmine] (JENKINS-18382) Basic test : RedmineInternalError: NotFoundException thrown
Olivier Chorier created JENKINS-18382 Basic test : RedmineInternalError: NotFoundException thrown Issue Type: Bug Affects Versions: current Assignee: gaooh Components: redmine Created: 18/Jun/13 9:58 AM Description: Here is my use cas : Redmine side : admin / configuration / authentication / x activate api rest my account / show api key / copy api key Jenkins side : 1- Create a minimal project (free-style) 2- Set up Redmine such as : redmine webiste : http://192.168.2.1 redmine project name : myprojname redmine versin 1.0.1 Project is located at http://192.168.2.1/redmine/projects/myprojname 3- Add post build action : Paste API Key Save 4- Launch build And then I get the following trace : Démarré par l'utilisateur olivier Building in workspace /home/user/.jenkins/jobs/Agreger Redmine/workspace FATAL: NotFoundException received, which should never happen in this request com.taskadapter.redmineapi.RedmineInternalError: NotFoundException received, which should never happen in this request at com.taskadapter.redmineapi.RedmineManager.getProjects(RedmineManager.java:156) at hudson.plugins.redmine.RedmineMetricsCalculator.getProject(RedmineMetricsCalculator.java:99) at hudson.plugins.redmine.RedmineMetricsCalculator.calc(RedmineMetricsCalculator.java:46) at hudson.plugins.redmine.RedmineMetricsPublisher.perform(RedmineMetricsPublisher.java:54) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1601) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) I Googled and couldn't find any help about this trace. I tried to add this post build action to a real built project, but the error is the same. Environment: OS : Ubuntu 8.04.4 LTS JDK : build 1.6.0_33-b03 Jenkins : 1.514 Project: Jenkins Priority: Major Reporter: Olivier Chorier 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] [ws-cleanup] (JENKINS-18345) Current implementation forces the wait of previous build to complete
vjuranek resolved JENKINS-18345 as Fixed Current implementation forces the wait of previous build to complete Fixed in https://github.com/jenkinsci/ws-cleanup-plugin/pull/9/ Change By: vjuranek (18/Jun/13 10:11 AM) Status: Open Resolved Resolution: Fixed 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-18368) Decorated Launcher Does Not Maintain isUnix for RemoteLauncher
Timothy Lantz
commented on JENKINS-18368
Decorated Launcher Does Not Maintain isUnix for RemoteLauncher
Some tests to reproduce the issue, will put together a pull request referencing the bug.
@Bug(18368)
public void testDecoratedByEnvMaintainsIsUnix() throws Exception {
ByteArrayOutputStream output = new ByteArrayOutputStream();
TaskListener listener = new StreamBuildListener(output);
Launcher remoteLauncher = new Launcher.RemoteLauncher(listener, Jenkins.MasterComputer.localChannel, false);
Launcher decorated = remoteLauncher.decorateByEnv(new EnvVars());
assertEquals(false, decorated.isUnix());
remoteLauncher = new Launcher.RemoteLauncher(listener, Jenkins.MasterComputer.localChannel, true);
decorated = remoteLauncher.decorateByEnv(new EnvVars());
assertEquals(true, decorated.isUnix());
}
@Bug(18368)
public void testDecoratedByPrefixMaintainsIsUnix() throws Exception {
ByteArrayOutputStream output = new ByteArrayOutputStream();
TaskListener listener = new StreamBuildListener(output);
Launcher remoteLauncher = new Launcher.RemoteLauncher(listener, Jenkins.MasterComputer.localChannel, false);
Launcher decorated = remoteLauncher.decorateByPrefix("test");
assertEquals(false, decorated.isUnix());
remoteLauncher = new Launcher.RemoteLauncher(listener, Jenkins.MasterComputer.localChannel, true);
decorated = remoteLauncher.decorateByPrefix("test");
assertEquals(true, decorated.isUnix());
}
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] [matrix-reloaded] (JENKINS-16591) Matrix Reloaded plugin - our case 8520
Lars Kruse commented on JENKINS-16591 Matrix Reloaded plugin - our case 8520 This issue is caused by the design of the plugin: The Matrix Reloaded feature is an action that is attached to the executed Matrix build - at the time of the execution. Consequently the reload feature is not available on builds that was executed before the plugin was installed. This was not clear in the documentation, but it has been updated now as a note: Reload option sometimes not available The Matrix Reloaded link is only available on the builds that were executed while the Matrix Reloaded Plugin was actually installed. Sometimes you may see a Matrix Build, that doesn't offer the Reload option, even though you did install the plugin. When that happens you can simply do a regular re-run (of the entire matrix) and the Matrix Reloaded option will be available on the new result. IF this is not satisfactory to you guys, then we will have to change the behavior of the plugin, so that it upon installation scans the whole master for currently existing Matrix builds and apply the action to all of them. It does however seem to be a little overkill, so we need to see an explicit demand for this before we estimate/implement. I'm closing this issue again - It's by design 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] [matrix-reloaded] (JENKINS-16591) Matrix Reloaded plugin - our case 8520
Lars Kruse resolved JENKINS-16591 as Wont Fix Matrix Reloaded plugin - our case 8520 It's by design - The documentation is now updated! Change By: Lars Kruse (18/Jun/13 10:39 AM) Status: Reopened Resolved Resolution: WontFix 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-18368) Decorated Launcher Does Not Maintain isUnix for RemoteLauncher
Timothy Lantz
edited a comment on JENKINS-18368
Decorated Launcher Does Not Maintain isUnix for RemoteLauncher
Some tests to reproduce the issue, will put together a pull request referencing the bug.
@Bug(18368)
public void testDecoratedByEnvMaintainsIsUnix() throws Exception {
ByteArrayOutputStream output = new ByteArrayOutputStream();
TaskListener listener = new StreamBuildListener(output);
Launcher remoteLauncher = new Launcher.RemoteLauncher(listener, Jenkins.MasterComputer.localChannel, false);
Launcher decorated = remoteLauncher.decorateByEnv(new EnvVars());
assertEquals(false, decorated.isUnix());
remoteLauncher = new Launcher.RemoteLauncher(listener, Jenkins.MasterComputer.localChannel, true);
decorated = remoteLauncher.decorateByEnv(new EnvVars());
assertEquals(true, decorated.isUnix());
}
@Bug(18368)
public void testDecoratedByPrefixMaintainsIsUnix() throws Exception {
ByteArrayOutputStream output = new ByteArrayOutputStream();
TaskListener listener = new StreamBuildListener(output);
Launcher remoteLauncher = new Launcher.RemoteLauncher(listener, Jenkins.MasterComputer.localChannel, false);
Launcher decorated = remoteLauncher.decorateByPrefix("test");
assertEquals(false, decorated.isUnix());
remoteLauncher = new Launcher.RemoteLauncher(listener, Jenkins.MasterComputer.localChannel, true);
decorated = remoteLauncher.decorateByPrefix("test");
assertEquals(true, decorated.isUnix());
}
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-14079) LDAP authentication crashes
Tatsuhito Kato commented on JENKINS-14079 LDAP authentication crashes No problem, for me. 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-14134) Configure breadcrumb on slaves in the sidebar goes to /configure
sogabe commented on JENKINS-14134 Configure breadcrumb on slaves in the sidebar goes to /configure I do not reproduce this issue with 1.520-SNAPSHOT too. 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-18381) Some node properties do not make sense as global node properties
dogfood commented on JENKINS-18381 Some node properties do not make sense as global node properties Integrated in jenkins_main_trunk #2626 JENKINS-18381 Provide a mechanism to differentiate between node (Revision 48e801023123f84ee4eebf60737089f41b44958e) Result = UNSTABLE Stephen Connolly : 48e801023123f84ee4eebf60737089f41b44958e Files : core/src/main/java/hudson/slaves/NodePropertyDescriptor.java core/src/main/java/hudson/Functions.java changelog.html core/src/main/resources/jenkins/model/GlobalNodePropertiesConfiguration/config.groovy 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] [copyartifact] (JENKINS-16476) Add Last Completed Build to permalink list
Bill Chen assigned JENKINS-16476 to Bill Chen Add Last Completed Build to permalink list Change By: Bill Chen (18/Jun/13 11:27 AM) Assignee: BillChen 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] [perforce] (JENKINS-15315) Slave polling hungup
Oleg Nenashev started work on JENKINS-15315 Slave polling hungup Change By: Oleg Nenashev (18/Jun/13 11:28 AM) Status: Open InProgress 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] [perforce] (JENKINS-15315) Slave polling hungup
Oleg Nenashev assigned JENKINS-15315 to Oleg Nenashev Slave polling hungup Change By: Oleg Nenashev (18/Jun/13 11:28 AM) Assignee: OlegNenashev 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] [perforce] (JENKINS-15315) Slave polling hungup
Oleg Nenashev commented on JENKINS-15315 Slave polling hungup Hello Robert, This issue is quite painful for our users, so I would like to fix it. This issue has been reproduced at the latest plugin version (Jenkins version – 1.480.3, java version "1.7.0_19", OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode) and several previous versions as well. According to the stacktraces, P4 hangs at BufferedReader::readLine(), which is infinitely waits for new line or EOF. I suppose that P4 command-line client finishes before call of readLine() or somehow enters interactive mode and waits till user’s input. However, I can’t reproduce issue at my testing stand with slaves with debugger. Restart of the slave fixes the problem. There are 84 BufferedReader::readLine() calls in p4 plugin, so we can’t just fix getPerforceResponse() function. Possible solutions: • We can add something like timeouts to the checkout() and other top-level overrides. BTW, it’s just a workaround for operative notification, because only restart can fix issue’s origin. • Add timeout to the getPerforceResponse() only and wait for other errors (yeah, just fix the known issue) • Replace BufferedReaders by wrapper, which knows how to handle issue. I’m going to implement second approach. It will be possible to configure timeout via perforce global configuration. Best regards, Oleg Nenashev RD Engineer, Synopsys Inc. www.synopsys.com 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-18291) http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb 404 not found
David Thornley reopened JENKINS-18291 http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb 404 not found I am getting this issue at the moment. wget http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb returns: wget http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb -2013-06-18 13:53:31- http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb Resolving pkg.jenkins-ci.org (pkg.jenkins-ci.org)... 63.246.20.93 Connecting to pkg.jenkins-ci.org (pkg.jenkins-ci.org)|63.246.20.93|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://mirrors.jenkins-ci.org/debian/jenkins_1.518_all.deb following -2013-06-18 13:53:31- http://mirrors.jenkins-ci.org/debian/jenkins_1.518_all.deb Resolving mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)... 63.246.20.93 Connecting to mirrors.jenkins-ci.org (mirrors.jenkins-ci.org)|63.246.20.93|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://fallback.jenkins-ci.org/debian/jenkins_1.518_all.deb following -2013-06-18 13:53:31- http://fallback.jenkins-ci.org/debian/jenkins_1.518_all.deb Resolving fallback.jenkins-ci.org (fallback.jenkins-ci.org)... 173.203.60.151 Connecting to fallback.jenkins-ci.org (fallback.jenkins-ci.org)|173.203.60.151|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2013-06-18 13:53:31 ERROR 404: Not Found. Change By: David Thornley (18/Jun/13 11:55 AM) Resolution: Fixed Status: Resolved Reopened 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-18291) http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb 404 not found
Steve Sutton commented on JENKINS-18291 http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb 404 not found I don't like to +1, but to confirm; I'm seeing the same, so this issue is not local to above poster. 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] [copyartifact] (JENKINS-16476) Add Last Completed Build to permalink list
Jesse Glick commented on JENKINS-16476 Add Last Completed Build to permalink list No, @lastSuccessfulBuild@ (available as a permalink) includes unstable builds. @Job.getLastCompletedBuild@ would include failed builds but not running builds. 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] [copyartifact] (JENKINS-16476) Add Last Completed Build to permalink list
Jesse Glick edited a comment on JENKINS-16476 Add Last Completed Build to permalink list No, lastSuccessfulBuild (available as a permalink) includes unstable builds. Job.getLastCompletedBuild would include failed builds but not running builds. 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] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git
Frédéric Camblor commented on JENKINS-15128 Renaming job doesnt work with Git In the scm-sync-config plugin, there are 2 SCM API used (and bridged) nowadays : Jenkins SCM API : used mainly for authentication Maven SCM API : used mainly to provide an abstraction over "standard" scm commands Problem with SCM API are : I don't know them very well (don't think it is well documented either) I don't think it is as rich (in terms of abstractions) as the Maven SCM API (I don't think, for instance, that there is a generic method allowing to "commit" things on the repository ... since jenkins doesn't need to commit anything generally .. it only uses scm to checkout source files). On the SCM API side, problem is not with lack of generic layered methods, but differences in behaviour in these ones. For instance, update() with svn will do an `svn update` (thus, working copy will be up to date, and ready for subsequent modifications). A svn delete will then be taken into account directly. Whereas update() with a git impl will only do a `git fetch` (working copy not up-to-date (only origin references are updated)), thus we will need either a 'rebase' or 'merge' to include changes to push them on the upstream remote. These methods don't exist because they are too DVCS-oriented (and couldn't be implemented in non-DVCS scms). Moreover, changing things in SCM API takes time because adding a generic method needs every scm implementation to provide their impl for this new generic method This is the reason why I think the better solution will be to implement our own generic impl for plugin needs only 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] [grails] (JENKINS-18235) need to add GRAILS_HOME/bin to PATH
SCM/JIRA link daemon resolved JENKINS-18235 as Fixed need to add GRAILS_HOME/bin to PATH Change By: SCM/JIRA link daemon (18/Jun/13 12:50 PM) Status: Open Resolved Resolution: Fixed 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-15331) Workaround Windows unpredictable file locking in Util.deleteContentsRecursive
Per Westling commented on JENKINS-15331 Workaround Windows unpredictable file locking in Util.deleteContentsRecursive This is a very interesting patch, as we encounter a similar bug several times a week. Will this be added to the Jenkins releases in the near future? 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] [grails] (JENKINS-18235) need to add GRAILS_HOME/bin to PATH
SCM/JIRA link daemon commented on JENKINS-18235 need to add GRAILS_HOME/bin to PATH Code changed in jenkins User: Nicolas De loof Path: src/main/java/com/g2one/hudson/grails/GrailsBuilder.java http://jenkins-ci.org/commit/grails-plugin/2de4edb57d19ea700392464e5cc65876e0fbfea7 Log: Merge pull request #7 from ndeloof/master JENKINS-18235 set PATH with GRAILS_HOME/bin Compare: https://github.com/jenkinsci/grails-plugin/compare/b64d73288769...2de4edb57d19 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] [grails] (JENKINS-18235) need to add GRAILS_HOME/bin to PATH
SCM/JIRA link daemon commented on JENKINS-18235 need to add GRAILS_HOME/bin to PATH Code changed in jenkins User: Nicolas De Loof Path: src/main/java/com/g2one/hudson/grails/GrailsBuilder.java http://jenkins-ci.org/commit/grails-plugin/250c5343d2ab489e7d799a83d644d295b38803d6 Log: FIXED JENKINS-18235 set PATH with GRAILS_HOME/bin 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] [confluence-publisher] (JENKINS-18383) Out of memory errors when uploading
Alexis Seigneurin
created JENKINS-18383
Out of memory errors when uploading
Issue Type:
Bug
Assignee:
Joe Hansche
Components:
confluence-publisher
Created:
18/Jun/13 1:18 PM
Description:
I get Out of memory errors when uploading files to Confluence (v5.1.2). This happens with files 25 MB.
confluence - Uploading file: Ipsos.MediaCell_v2.8_PanelistWebsite.zip (application/zip)
ERROR: Unable to upload file...
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
faultSubcode:
faultString: java.lang.OutOfMemoryError: Java heap space; nested exception is:
java.lang.OutOfMemoryError: Java heap space
faultActor:
faultNode:
faultDetail:
{}faultData:null
{http://xml.apache.org/axis/}hostname:barral
java.lang.OutOfMemoryError: Java heap space; nested exception is:
java.lang.OutOfMemoryError: Java heap space
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:606)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1741)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2898)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1210)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:568)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:302)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at jenkins.plugins.confluence.soap.v1.ConfluenceserviceV1SoapBindingStub.addAttachment(ConfluenceserviceV1SoapBindingStub.java:4896)
at com.myyearbook.hudson.plugins.confluence.ConfluenceSession.addAttachment(ConfluenceSession.java:181)
at com.myyearbook.hudson.plugins.confluence.ConfluenceSession.addAttachment(ConfluenceSession.java:201)
at com.myyearbook.hudson.plugins.confluence.ConfluencePublisher.performAttachments(ConfluencePublisher.java:241)
at com.myyearbook.hudson.plugins.confluence.ConfluencePublisher.perform(ConfluencePublisher.java:314)
at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726)
at hudson.model.Run.execute(Run.java:1601)
[JIRA] [core] (JENKINS-18384) Scheduled restart from plugin manager does not restart
Jesse Glick created JENKINS-18384 Scheduled restart from plugin manager does not restart Issue Type: Bug Assignee: Nicolas De Loof Components: core Created: 18/Jun/13 1:21 PM Description: In a trunk build I updated a plugin and checked the box asking to restart as soon as no jobs were running. The log file said that Jenkins was scheduled to restart, but I waited the usual ten seconds and nothing happened. I had to go /restart and force it. I think https://github.com/jenkinsci/jenkins/pull/795 may have introduced a regression here. Project: Jenkins Labels: regression Priority: Major Reporter: Jesse Glick 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] [promoted-builds] (JENKINS-18385) accept groups for users that can run a manual promotion
Nicolas De Loof created JENKINS-18385 accept groups for users that can run a manual promotion Issue Type: Bug Assignee: Unassigned Components: promoted-builds Created: 18/Jun/13 1:32 PM Description: current promotion restriction require to set user names, and don't integrate with security settings. Should accept a group name. Project: Jenkins Priority: Minor Reporter: Nicolas De Loof 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] [view-job-filters] (JENKINS-18386) more flexible job filter by parameter
Maris Zulis
created JENKINS-18386
more flexible job filter by parameter
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Jacob Robertson
Components:
view-job-filters
Created:
18/Jun/13 1:32 PM
Description:
parameter filter can only filter by StringParameterValue, BooleanParameterValue and FileParameterValue. So we can't filter by custom parameters.
I can't understand why can't we change ParameterFilter class getStringValue function to something like this:
protected String getStringValue(ParameterValue value) {
if (value instanceof StringParameterValue) {
return ((StringParameterValue) value).value;
} else if (value instanceof BooleanParameterValue) {
boolean bval = ((BooleanParameterValue) value).value;
return String.valueOf(bval);
} else if (value instanceof FileParameterValue) {
// not the full path - just the name
// this is the only public value available to us
String file = ((FileParameterValue) value).getOriginalFileName();
return file;
} else {
return value.toString();
}
}
mine difference is return value.toString(); not return null;
Project:
Jenkins
Priority:
Critical
Reporter:
Maris Zulis
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] [view-job-filters] (JENKINS-18386) more flexible job filter by parameter
Maris Zulis
updated JENKINS-18386
more flexible job filter by parameter
Change By:
Maris Zulis
(18/Jun/13 1:36 PM)
Description:
parameterfiltercanonlyfilterbyStringParameterValue,BooleanParameterValueandFileParameterValue.Sowecantfilterbycustomparameters.IcantunderstandwhycantwechangeParameterFilterclassgetStringValuefunctiontosomethinglikethis:
{code:none}
protectedStringgetStringValue(ParameterValuevalue){ if(valueinstanceofStringParameterValue){ return((StringParameterValue)value).value; }elseif(valueinstanceofBooleanParameterValue){ booleanbval=((BooleanParameterValue)value).value; returnString.valueOf(bval); }elseif(valueinstanceofFileParameterValue){ //notthefullpath-justthename //thisistheonlypublicvalueavailabletous Stringfile=((FileParameterValue)value).getOriginalFileName(); returnfile; }else{ returnvalue.toString(); } }
{code}
minedifferenceisreturnvalue.toString();notreturnnull;
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] [junit] (JENKINS-15380) No history for test cases where name of suite is part of test case name
Jesse Glick commented on JENKINS-15380 No history for test cases where name of suite is part of test case name Should this be an lts-candidate? 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] [promoted-builds] (JENKINS-18385) accept groups for users that can run a manual promotion
Jesse Glick commented on JENKINS-18385 accept groups for users that can run a manual promotion Setting a group name seems as hacky as setting a user name, just a bit more general. Would it not be better to define a new permission (checked I guess on the parent job) for promoting a build, so that an authorization strategy can decide using normal idioms what users should be permitted? 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] [confluence-publisher] (JENKINS-18383) Out of memory errors when uploading
Joe Hansche
updated JENKINS-18383
Out of memory errors when uploading
Change By:
Joe Hansche
(18/Jun/13 2:05 PM)
Description:
IgetOutofmemoryerrorswhenuploadingfilestoConfluence(v5.1.2).Thishappenswithfiles25MB.{
quote
noformat
}[confluence]-Uploadingfile:Ipsos.MediaCell_v2.8_PanelistWebsite.zip(application/zip)ERROR:Unabletouploadfile...AxisFaultfaultCode:\{http://schemas.xmlsoap.org/soap/envelope/}Server.generalExceptionfaultSubcode:faultString:java.lang.OutOfMemoryError:Javaheapspace;nestedexceptionis: java.lang.OutOfMemoryError:JavaheapspacefaultActor:faultNode:faultDetail: {}faultData:null \{http://xml.apache.org/axis/}hostname:barraljava.lang.OutOfMemoryError:Javaheapspace;nestedexceptionis: java.lang.OutOfMemoryError:Javaheapspace atorg.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder.java:222) atorg.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.java:129) atorg.apache.axis.encoding.DeserializationContext.endElement(DeserializationContext.java:1087) atcom.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:606) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragmentScannerImpl.java:1741) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2898) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:607) atcom.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:116) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:488) atcom.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:835) atcom.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764) atcom.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:123) atcom.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1210) atcom.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:568) atcom.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:302) atorg.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227) atorg.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696) atorg.apache.axis.Message.getSOAPEnvelope(Message.java:435) atorg.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62) atorg.apache.axis.client.AxisClient.invoke(AxisClient.java:206) atorg.apache.axis.client.Call.invokeEngine(Call.java:2784) atorg.apache.axis.client.Call.invoke(Call.java:2767) atorg.apache.axis.client.Call.invoke(Call.java:2443) atorg.apache.axis.client.Call.invoke(Call.java:2366) atorg.apache.axis.client.Call.invoke(Call.java:1812) atjenkins.plugins.confluence.soap.v1.ConfluenceserviceV1SoapBindingStub.addAttachment(ConfluenceserviceV1SoapBindingStub.java:4896) atcom.myyearbook.hudson.plugins.confluence.ConfluenceSession.addAttachment(ConfluenceSession.java:181) atcom.myyearbook.hudson.plugins.confluence.ConfluenceSession.addAttachment(ConfluenceSession.java:201) atcom.myyearbook.hudson.plugins.confluence.ConfluencePublisher.performAttachments(ConfluencePublisher.java:241) atcom.myyearbook.hudson.plugins.confluence.ConfluencePublisher.perform(ConfluencePublisher.java:314) athudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) athudson.model.Build$BuildExecution.post2(Build.java:183) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) athudson.model.Run.execute(Run.java:1601) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:241){
quote
noformat
}
[JIRA] [confluence-publisher] (JENKINS-18383) Out of memory errors when uploading
Joe Hansche commented on JENKINS-18383 Out of memory errors when uploading Unfortunately, there's not much I can do to fix that. I haven't tried uploading a 25MB file via the plugin. You might need to increase your java heap space given to the Jenkins server. Can you tell what the upward limit is for the attachment in your JVM? There's only one way to add an attachment in this API, and if the axis client is unable to attach it within the JVM heap provided, the plugin will not be able to do anything to fix that. From the Confluence documentation, it states: Attachment addAttachment(String token, long contentId, Attachment attachment, byte[] attachmentData) - add a new attachment to a content entity object. Note that this uses a lot of memory - about 4 times the size of the attachment. The 'long contentId' is actually a String pageId for XML-RPC. 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] [repository] (JENKINS-18288) Link to latest send to version 1.518 on the mirror page
Matt Kraai commented on JENKINS-18288 Link to latest send to version 1.518 on the mirror page It now redirects to http://fallback.jenkins-ci.org/war/1.518/jenkins.war, which does not work. I suspect this occurs because 1.519 has been released. I've tried this from multiple systems, at least one of which I'm sure is not cached. 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] [confluence-publisher] (JENKINS-18383) Out of memory errors when uploading
Alexis Seigneurin commented on JENKINS-18383 Out of memory errors when uploading It did succeed uploading files that were ~15 MB. However, files of 30 MB and more failed uploading. That's why I would say the limit is around 25 MB. I've tried increasing the memory allocated to Jenkins to 1280 MB but it didn't change the result. If that's something that cannot be fixed, I would suggest adding a warning on the plugin description page so that other users know this should not be used with large files. Thanks! 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] [confluence-publisher] (JENKINS-18383) Out of memory errors when uploading
Joe Hansche commented on JENKINS-18383 Out of memory errors when uploading "should not be used with large files" is incorrect, though. If the JVM allows the attachment to be added, it will work. So having the stacktrace showing an error because of OOM shows the Jenkins site administrator that the attachment puts it over its heap limit. I could catch the OOME and and show a more friendly error message in the console, but if it's a failure, the stacktrace is probably helpful to have. 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] [warnings] (JENKINS-17791) Replace Pep8 parser with native parser
SCM/JIRA link daemon resolved JENKINS-17791 as Fixed Replace Pep8 parser with native parser Change By: SCM/JIRA link daemon (18/Jun/13 2:38 PM) Status: Open Resolved Resolution: Fixed 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] [warnings] (JENKINS-17791) Replace Pep8 parser with native parser
SCM/JIRA link daemon commented on JENKINS-17791 Replace Pep8 parser with native parser Code changed in jenkins User: Ulli Hafner Path: .classpath .settings/org.eclipse.core.resources.prefs src/main/java/hudson/plugins/warnings/parser/Pep8Parser.java src/main/java/hudson/plugins/warnings/parser/ViolationsRegistry.java src/test/java/hudson/plugins/warnings/parser/Pep8ParserTest.java src/test/resources/hudson/plugins/warnings/parser/pep8Test.txt http://jenkins-ci.org/commit/warnings-plugin/233085dae99708d2e4ddd17d8df3e52286d3b2a6 Log: Merge pull request #25 from habast/jenkins-Pep8Parser FIXED JENKINS-17791 Added native Pep8 parser. Compare: https://github.com/jenkinsci/warnings-plugin/compare/d958f11ad36d...233085dae997 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] [warnings] (JENKINS-18081) Gcc compiler parser does not detect fatal error
SCM/JIRA link daemon resolved JENKINS-18081 as Fixed Gcc compiler parser does not detect fatal error Change By: SCM/JIRA link daemon (18/Jun/13 2:46 PM) Status: Open Resolved Resolution: Fixed 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] [warnings] (JENKINS-18084) Clang compiler parser does not detect fatal error
SCM/JIRA link daemon commented on JENKINS-18084 Clang compiler parser does not detect fatal error Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/AppleLLVMClangParser.java src/main/java/hudson/plugins/warnings/parser/ClangParser.java src/test/java/hudson/plugins/warnings/parser/AppleLLVMClangParserTest.java src/test/java/hudson/plugins/warnings/parser/ClangParserTest.java src/test/resources/hudson/plugins/warnings/parser/issue18084.txt http://jenkins-ci.org/commit/warnings-plugin/504c69927febe0b21ca27a54bba93d487621f73b Log: FIXED JENKINS-18084 Added support for errors in CLang parser. 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] [warnings] (JENKINS-17788) Replace CSSLinit parser with native parser
SCM/JIRA link daemon commented on JENKINS-17788 Replace CSSLinit parser with native parser Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/AbstractWarningsParser.java src/main/java/hudson/plugins/warnings/parser/CssLintParser.java src/main/java/hudson/plugins/warnings/parser/JSLintParser.java src/main/java/hudson/plugins/warnings/parser/JSLintXMLSaxParser.java src/main/java/hudson/plugins/warnings/parser/LintParser.java src/main/java/hudson/plugins/warnings/parser/ViolationsRegistry.java src/test/java/hudson/plugins/warnings/parser/CssLintParserTest.java src/test/java/hudson/plugins/warnings/parser/JSLintParserTest.java src/test/resources/hudson/plugins/warnings/parser/jslint/csslint.xml http://jenkins-ci.org/commit/warnings-plugin/368852ec17f95a6bf6f61f111b9792b5c8baaa3e Log: FIXED JENKINS-17788 Use JS-Lint parser when parsing CSS-Lint files. 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] [warnings] (JENKINS-18081) Gcc compiler parser does not detect fatal error
SCM/JIRA link daemon commented on JENKINS-18081 Gcc compiler parser does not detect fatal error Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/parser/Gcc4CompilerParser.java src/test/java/hudson/plugins/warnings/parser/Gcc4CompilerParserTest.java src/test/resources/hudson/plugins/warnings/parser/issue18081.txt http://jenkins-ci.org/commit/warnings-plugin/c7efe21a94c8f4228530ad6e19818ca172d54fea Log: FIXED JENKINS-18081 Added support for errors in GCC parser. 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] [warnings] (JENKINS-18084) Clang compiler parser does not detect fatal error
SCM/JIRA link daemon resolved JENKINS-18084 as Fixed Clang compiler parser does not detect fatal error Change By: SCM/JIRA link daemon (18/Jun/13 2:46 PM) Status: Open Resolved Resolution: Fixed 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] [warnings] (JENKINS-17788) Replace CSSLinit parser with native parser
SCM/JIRA link daemon resolved JENKINS-17788 as Fixed Replace CSSLinit parser with native parser Change By: SCM/JIRA link daemon (18/Jun/13 2:46 PM) Status: Open Resolved Resolution: Fixed 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] [publish-over-cifs] (JENKINS-16739) Can't strip **/
unkown unkown commented on JENKINS-16739 Cant strip **/ +1 I have the same problem. My path contains the git tag and that may change from time to time. For this reason i use wildcards but i can't remove the prefix. An option to disable the prefix would be very useful. 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] [downstream-buildview] (JENKINS-18388) support parameterized build trigger
Nicolas De Loof created JENKINS-18388 support parameterized build trigger Issue Type: New Feature Assignee: shinodkm Components: downstream-buildview Created: 18/Jun/13 3:55 PM Description: jobs triggered within build steps aren't (ye() supported by DownStream BuildView Project: Jenkins Priority: Minor Reporter: Nicolas De Loof 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-18387) Jenkins sometimes fails to restart successfully
Matt Kraai created JENKINS-18387 Jenkins sometimes fails to restart successfully Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: log Components: core Created: 18/Jun/13 3:54 PM Description: When I try to restart Jenkins by visiting its /restart URL, it sometimes fails to restart successfully. When this problem occurs, Process Explorer first shows the existing jenkins.exe and java.exe processes terminate. It then shows a new jenkins.exe as the parent of a new java.exe process and a DW20.exe process (a Microsoft Office error reporting tool). After some time, it shows the jenkins.exe process terminate and the java.exe and DW20.exe processes with no parent. It then shows another jenkins.exe and java.exe start, run briefly, then terminate. This repeats indefinitely. Eventually, DW20.exe terminates. The first java.exe process started runs until manually killed, at which point jenkins.exe and java.exe start and run successfully. I'll attach the contents of jenkins.err.log from one such occurrence. Environment: Microsoft Windows Server 2003 R2, Standard Edition, Service Pack 2 Project: Jenkins Priority: Major Reporter: Matt Kraai 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] [mercurial] (JENKINS-18252) Push notifications on Windows and a local repository
Zamir Khan commented on JENKINS-18252 Push notifications on Windows and a local repository I have a similar problem, but cannot use a file URL because the repo is on a remote machine (on the LAN, not accessible through http). Mercurial will not accept file URLs for non-local repositories. Using the \\MACHINE_NAME\path\to\repo form does not seem to trigger a build. 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] [mercurial] (JENKINS-18252) Push notifications on Windows and a local repository
Jesse Glick commented on JENKINS-18252 Push notifications on Windows and a local repository @zkhan did you try file://MACHINE_NAME/path/to/repo/? 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] [mercurial] (JENKINS-18252) Push notifications on Windows and a local repository
Zamir Khan commented on JENKINS-18252 Push notifications on Windows and a local repository @jglick I should have clarified, but what I meant by Mercurial not accepting file URLs for non-local, is you'll get a message like this from hg: "abort: file:// URLs can only refer to localhost" 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] [buildresulttrigger] (JENKINS-18389) BuildResult constantly triggers job
teilo
created JENKINS-18389
BuildResult constantly triggers job
Issue Type:
Bug
Assignee:
Gregory Boissinot
Components:
buildresulttrigger
Created:
18/Jun/13 4:22 PM
Description:
The build result trigger constantly triggers jobs when the build number is not low.
Issue caused by comparing two Integer objects with == rather than equals()
patch inline
diff --git a/src/main/java/org/jenkinsci/plugins/buildresulttrigger/BuildResultTrigger.java b/src/mai
index c6946e3..192947f 100644
--- a/src/main/java/org/jenkinsci/plugins/buildresulttrigger/BuildResultTrigger.java
+++ b/src/main/java/org/jenkinsci/plugins/buildresulttrigger/BuildResultTrigger.java
@@ -168,7 +168,7 @@ public class BuildResultTrigger extends AbstractTriggerByFullContextBuildResult
}
//Process if there is a new build between now and previous polling
-if (newLastBuildNumber == 0 || newLastBuildNumber != oldLastBuildNumber) {
+if (newLastBuildNumber == 0 || ! newLastBuildNumber.equals(oldLastBuildNumber)) {
return isMatchingExpectedResults(configuredTriggerJobInfo, log);
}
Project:
Jenkins
Priority:
Blocker
Reporter:
teilo
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] [perforce] (JENKINS-15315) Slave polling hungup
Rob Petti commented on JENKINS-15315 Slave polling hungup The timeout needs to be reset every time a line comes through. As I've mentioned, some users have a very large amount of data that can take hours to sync, so it shouldn't time out an operation if it's clearly still doing something. 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] [mercurial] (JENKINS-18252) Push notifications on Windows and a local repository
Jesse Glick commented on JENKINS-18252 Push notifications on Windows and a local repository I see. A bug in Mercurial. Pity. 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-17276) Downward configuration of executor count on master delayed in effect
dogfood commented on JENKINS-17276 Downward configuration of executor count on master delayed in effect Integrated in jenkins_main_trunk #2628 FIXED JENKINS-17276 (Revision 0cc517f3dcc0839c55a957da0db53deb84e808be) Result = UNSTABLE kohsuke : 0cc517f3dcc0839c55a957da0db53deb84e808be Files : changelog.html 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] [cvs] (JENKINS-18390) -P does not work
Jesse Glick created JENKINS-18390 -P does not work Issue Type: Bug Assignee: Unassigned Components: cvs Created: 18/Jun/13 4:46 PM Description: Create a tree in CVS including an empty directory. Configure a Jenkins job to check it out, leaving the prune option checked. The build runs but the empty directories are not checked out. Seems to be a bug in the client. UpdateCommand.pruneEmptyDirectories is called but emptyDirectories is empty; messageSent was called once, but MessageEvent.getMessage was blank. If you select Show all CVS output then it works, presumably because cvs update: Updating workspace/empty was printed. Environment: 2.10-SNAPSHOT in hpi:run on Linux Project: Jenkins Priority: Major Reporter: Jesse Glick 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] [cvs] (JENKINS-18390) -P does not work
Jesse Glick updated JENKINS-18390 -P does not work Change By: Jesse Glick (18/Jun/13 4:55 PM) Labels: regression 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] [gerrit-trigger] (JENKINS-18391) Gerrit Version is null after upgrade to 2.10.1
teilo created JENKINS-18391 Gerrit Version is null after upgrade to 2.10.1 Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 18/Jun/13 5:14 PM Description: After upgradeing from 2.10.0 to 2.10.1 at startup jenkins emits the following warning Jun 18, 2013 5:07:32 PM com.sonyericsson.hudson.plugins.gerrit.trigger.version.GerritVersionChecker createVersionNumber SEVERE: Gerrit version number is null or the empty string. Jun 18, 2013 5:07:32 PM com.sonyericsson.hudson.plugins.gerrit.gerritevents.GerritHandler run INFO: Ready to receive data from Gerrit This is obviously not good (our Gerrit version is 2.5) and has been detected correctly before. So the plugin may now expect functionality from Gerrit that our server does not support. Project: Jenkins Priority: Major Reporter: teilo 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] [warnings] (JENKINS-17792) Replace PerlCritic parser with native parser
Ulli Hafner resolved JENKINS-17792 as Fixed Replace PerlCritic parser with native parser Change By: Ulli Hafner (18/Jun/13 5:25 PM) Status: Open Resolved Resolution: Fixed 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] [warnings] (JENKINS-17767) Unable to get warnings from all parsers via API
Ulli Hafner assigned JENKINS-17767 to Sebastian Hansbauer Unable to get warnings from all parsers via API Change By: Ulli Hafner (18/Jun/13 5:27 PM) Assignee: UlliHafner SebastianHansbauer 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] [analysis-core] (JENKINS-17663) Fail by publishing report will fail whole build
Ulli Hafner assigned JENKINS-17663 to Mihail Menev Fail by publishing report will fail whole build Change By: Ulli Hafner (18/Jun/13 5:26 PM) Assignee: UlliHafner MihailMenev 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] [analysis-core] (JENKINS-17047) Make dependency to bundled ant plugin optional
Ulli Hafner assigned JENKINS-17047 to Ulli Hafner Make dependency to bundled ant plugin optional Change By: Ulli Hafner (18/Jun/13 5:26 PM) Assignee: SebastianHansbauer UlliHafner 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] [warnings] (JENKINS-17793) Replace PyLint parser with native parser
Ulli Hafner resolved JENKINS-17793 as Fixed Replace PyLint parser with native parser Change By: Ulli Hafner (18/Jun/13 5:24 PM) Status: Open Resolved Resolution: Fixed 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] [perforce] (JENKINS-15315) Slave polling hungup
Oleg Nenashev commented on JENKINS-15315 Slave polling hungup Yes, I agree with you. Hope to finish testing and create pull request today. 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-18224) TransientActionFactory
Kohsuke Kawaguchi commented on JENKINS-18224 TransientActionFactory Making Actionable understand transient actions is actually a good idea, because transient actions in general are typically done as a hack. Although it probably implies calling transient action factory on every page rendering. 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] [perforce] (JENKINS-15315) Slave polling hungup
Oleg Nenashev edited a comment on JENKINS-15315 Slave polling hungup Pull request with the discussed workaround: https://github.com/jenkinsci/perforce-plugin/pull/32 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] [perforce] (JENKINS-15315) Slave polling hungup
Oleg Nenashev commented on JENKINS-15315 Slave polling hungup Pull request with workaround: https://github.com/jenkinsci/perforce-plugin/pull/32 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] [artifactory] (JENKINS-18392) Support Matrix Projects in Jenkins Artifactory Plugin
rravi created JENKINS-18392 Support Matrix Projects in Jenkins Artifactory Plugin Issue Type: Improvement Assignee: yossis Components: artifactory Created: 18/Jun/13 8:16 PM Description: The Jenkins Artifactory plugin currently doesn't support Matrix jobs. Please add support for this. Project: Jenkins Priority: Critical Reporter: rravi 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] [integrity-plugin] (JENKINS-18335) PTC Integrity Plugin throws SQL Exception: Der Datenstrom- oder LOB-Wert kann nicht mehrmals abgerufen werden
Cletus DSouza resolved JENKINS-18335 as Wont Fix PTC Integrity Plugin throws SQL Exception: Der Datenstrom- oder LOB-Wert kann nicht mehrmals abgerufen werden Issue is resolved by using a compatible version of Derby Change By: Cletus DSouza (18/Jun/13 8:58 PM) Status: InProgress Resolved Fix Version/s: current Resolution: WontFix 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] [cli] (JENKINS-18393) list-jobs CLI command should list TopLevelItems exclusively
Oliver Gondža created JENKINS-18393 list-jobs CLI command should list TopLevelItems exclusively Issue Type: Bug Assignee: Oliver Gondža Components: cli Created: 18/Jun/13 9:10 PM Project: Jenkins Priority: Minor Reporter: Oliver Gondža 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] [cli] (JENKINS-18393) list-jobs CLI command should not list ItemgGroups of any items but TopLevelItems
Oliver Gondža
updated JENKINS-18393
list-jobs CLI command should not list ItemgGroups of any items but TopLevelItems
Change By:
Oliver Gondža
(18/Jun/13 9:19 PM)
Summary:
list-jobsCLIcommandshould
not
list
ItemgGroupsofanyitemsbut
TopLevelItems
exclusively
Description:
Currently,{{list-jobs}}commandtriestolistany{{ItemGroups}}(including{{MavenModuleSet}}or{{MatrixProject}}whichdoesnotmakesense).Itshouldlistinstancesof{{View}}and{{ItemGroup?extendsTopLevelItem}}exclusively.{{jenkins-cli.jarlist-jobsMyMatrixJob}}failswith:{noformat}java.lang.ClassCastException:hudson.matrix.MatrixConfigurationcannotbecasttohudson.model.TopLevelItem athudson.cli.ListJobsCommand.run(ListJobsCommand.java:88) athudson.cli.CLICommand.main(CLICommand.java:229) athudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) atjava.lang.reflect.Method.invoke(Method.java:597) athudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:282) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:263) athudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:222) athudson.remoting.UserRequest.perform(UserRequest.java:118) athudson.remoting.UserRequest.perform(UserRequest.java:48) athudson.remoting.Request$2.run(Request.java:326) athudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) athudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63) athudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95) atjava.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) atjava.util.concurrent.FutureTask.run(FutureTask.java:138) atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) atjava.lang.Thread.run(Thread.java:662){noformat}
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] [findbugs] (JENKINS-18394) IncompatibleClassChangeError after upgrade to 1.519
Chris Lee created JENKINS-18394 IncompatibleClassChangeError after upgrade to 1.519 Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: findbugs Created: 18/Jun/13 10:31 PM Description: Below exception occurs on every build following upgrade to 1.519: [FINDBUGS] Collecting findbugs analysis files... ERROR: Publisher hudson.plugins.findbugs.FindBugsPublisher aborted due to exception hudson.util.IOException2: remote file operation failed: /data/jenkins/workspace/EMR_450 at hudson.remoting.Channel@15f6059:devbuild01 at hudson.FilePath.act(FilePath.java:901) at hudson.FilePath.act(FilePath.java:878) at hudson.plugins.findbugs.FindBugsPublisher.perform(FindBugsPublisher.java:161) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:146) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:331) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1618) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:242) Caused by: java.io.IOException: Remote call on devbuild01 failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.FilePath.act(FilePath.java:894) ... 13 more Caused by: java.lang.IncompatibleClassChangeError: Implementing class at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:791) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:791) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:791) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142) at java.net.URLClassLoader.defineClass(URLClassLoader.java:449) at java.net.URLClassLoader.access$100(URLClassLoader.java:71) at java.net.URLClassLoader$1.run(URLClassLoader.java:361) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:705) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:759) at sun.reflect.GeneratedMethodAccessor52.invoke(Unknown Source) at
[JIRA] [matrix] (JENKINS-7683) Restrict where this project can be run-Option not available for Matrix builds
Jonathan Rice commented on JENKINS-7683 Restrict where this project can be run-Option not available for Matrix builds I think I'm hitting the same issue as the original poster. Perhaps I can clarify the failure scenario. Say you have a matrix build called "Matrix", with a single axis of user-defined values "p1", "p2", ... "p5". And say you want all of that build to run on the Master node, and not on another slave node "node1". AFAICS, six tasks are kicked off for such a build - the parent (flyweight) task "Matrix", plus a task for each configuration in the matrix: "Matrix p1", "Matrix p2", ... "Matrix p5". Now, with the "Matrix Tie Parent" plugin, you can succeed in pinning the parent task "Matrix" to the Master node, but this has no effect on the per-configuration tasks "Matrix p1", etc. So some of those will tend to run on the slave node "node1". I have not found any way to restrict where these tasks are run, as can be easily done with non-matrix jobs. 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] [cvs] (JENKINS-18390) -P does not work
Jesse Glick updated JENKINS-18390 -P does not work Change By: Jesse Glick (18/Jun/13 11:02 PM) URL: https://github.com/jenkinsci/cvs-plugin/pull/21 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] [cvs] (JENKINS-18390) -P does not work
Jesse Glick started work on JENKINS-18390 -P does not work Change By: Jesse Glick (18/Jun/13 11:02 PM) Status: Open InProgress 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] [http_request] (JENKINS-18395) Add post-build step
Jonathan Zimmerman created JENKINS-18395 Add post-build step Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: http_request Created: 18/Jun/13 11:14 PM Description: We'd like to be able to use this plug-in as a post-build step. Unfortunately this plug-in only exposes a build step. Project: Jenkins Priority: Major Reporter: Jonathan Zimmerman 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] [mercurial] (JENKINS-18252) Push notifications on Windows and a local repository
Dan Jasek commented on JENKINS-18252 Push notifications on Windows and a local repository @zkhan As a workaround, mapping the remote directory to a local drive letter may fix your issue. 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] [matrix] (JENKINS-7683) Restrict where this project can be run-Option not available for Matrix builds
Jonathan Rice commented on JENKINS-7683 Restrict where this project can be run-Option not available for Matrix builds Ah, I figured out two work-arounds. The first solution, which had been staring me in the face, and I think may have been implied in one or two previous comments, is to add a "Slaves" matrix axis with just one value, "master". This makes all of the per-configuration jobs run on the master. Combined with the "Matrix Tie Parent" plugin, to also tie the parent task to "master", we then have all jobs running on the master, and not on any slave nodes. The second solution is to use the "NodeLabel Parameter" plugin, to add a node parameter "master" to the matrix build. This also makes all of the per-configuration jobs run on the master, and with the "Matrix Tie Parent" plugin once again taking care of tying the parent job to the master, we have a full solution. 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-14079) LDAP authentication crashes
Kiyotaka Kikuchi resolved JENKINS-14079 as Fixed LDAP authentication crashes no problem. thanks Change By: Kiyotaka Kikuchi (19/Jun/13 12:34 AM) Status: Open Resolved Resolution: Fixed 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] [findbugs] (JENKINS-18394) IncompatibleClassChangeError after upgrade to 1.519
Chris Lee commented on JENKINS-18394 IncompatibleClassChangeError after upgrade to 1.519 ...downgrading to 1.518 resolves the issue. 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
dogfood commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Integrated in jenkins_main_trunk #2629 FIXED JENKINS-17713 JENKINS-14362 (Revision bda95c67a6780ff0e6350f80d6f69cf0f61e737c) Result = SUCCESS kohsuke : bda95c67a6780ff0e6350f80d6f69cf0f61e737c Files : core/pom.xml changelog.html 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-18368) Decorated Launcher Does Not Maintain isUnix for RemoteLauncher
Timothy Lantz assigned JENKINS-18368 to Timothy Lantz Decorated Launcher Does Not Maintain isUnix for RemoteLauncher Change By: Timothy Lantz (19/Jun/13 2:06 AM) Assignee: TimothyLantz 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-4409) Hudson test case leaks temp folders
dogfood commented on JENKINS-4409 Hudson test case leaks temp folders Integrated in jenkins_main_trunk #2630 FIX JENKINS-4409 Release plugins and class loaders when JVM shuts down. (Revision 2b9a083fbf2b9f4946ffa01e35dffea2b20a98d1) Result = SUCCESS kohsuke : 2b9a083fbf2b9f4946ffa01e35dffea2b20a98d1 Files : test/src/main/java/org/jvnet/hudson/test/TestPluginManager.java 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] [job-dsl-plugin] (JENKINS-18396) Add ability to inject imports for helper classes used in job dsl.
Chris Dore created JENKINS-18396 Add ability to inject imports for helper classes used in job dsl. Issue Type: Improvement Assignee: Justin Ryan Components: job-dsl-plugin Created: 19/Jun/13 4:39 AM Description: Currently, in order for a user to use helper classes such as javaposse.jobdsl.dsl.helpers.Permissions they need to import them in their DSL code. It would be great if these type of helper classes could be automatically injected into the GroovyClassLoader. Project: Jenkins Priority: Major Reporter: Chris Dore 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
SCM/JIRA link daemon commented on JENKINS-14362 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/pom.xml http://jenkins-ci.org/commit/jenkins/bda95c67a6780ff0e6350f80d6f69cf0f61e737c Log: FIXED JENKINS-17713 JENKINS-14362 Integrated the new version of Stapler that fixes them. Compare: https://github.com/jenkinsci/jenkins/compare/59d4c6a4c25a...bda95c67a678 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] [maven] (JENKINS-17713) Maven Module links are now broken - missing Job Name
SCM/JIRA link daemon commented on JENKINS-17713 Maven Module links are now broken - missing Job Name Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/pom.xml http://jenkins-ci.org/commit/jenkins/bda95c67a6780ff0e6350f80d6f69cf0f61e737c Log: FIXED JENKINS-17713 JENKINS-14362 Integrated the new version of Stapler that fixes them. Compare: https://github.com/jenkinsci/jenkins/compare/59d4c6a4c25a...bda95c67a678 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-4409) Hudson test case leaks temp folders
SCM/JIRA link daemon commented on JENKINS-4409 Hudson test case leaks temp folders Code changed in jenkins User: ikedam Path: test/src/main/java/org/jvnet/hudson/test/TestPluginManager.java http://jenkins-ci.org/commit/jenkins/2b9a083fbf2b9f4946ffa01e35dffea2b20a98d1 Log: FIX JENKINS-4409 Release plugins and class loaders when JVM shuts down. 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] [job-dsl-plugin] (JENKINS-18396) Add ability to inject imports for helper classes used in job dsl.
Justin Ryan assigned JENKINS-18396 to Chris Dore Add ability to inject imports for helper classes used in job dsl. Change By: Justin Ryan (19/Jun/13 5:06 AM) Assignee: JustinRyan ChrisDore 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] [job-dsl-plugin] (JENKINS-18396) Add ability to inject imports for helper classes used in job dsl.
Chris Dore assigned JENKINS-18396 to Justin Ryan Add ability to inject imports for helper classes used in job dsl. Change By: Chris Dore (19/Jun/13 5:26 AM) Assignee: ChrisDore JustinRyan 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.
