[JIRA] [threadfix] (JENKINS-24311) Sort Team/Application list in ascending order
Steve Springett created JENKINS-24311 Sort Team/Application list in ascending order Issue Type: Improvement Assignee: Brandon Spruth Components: threadfix Created: 19/Aug/14 5:59 AM Description: In a large threadfix deployment with dozens of teams and multiple applications per team, it can be challenging to find the team/application to upload to without the list being sorted. This enhancement request is to simply sort the list prior to being displayed in the dropdown. Project: Jenkins Priority: Minor Reporter: Steve Springett This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24312) NPE if session was left open for a longer time
Björn Pedersen created JENKINS-24312 NPE if session was left open for a longer time Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 19/Aug/14 6:50 AM Description: If I have a jenkins session open for a longer time, I get a NPE (Oops page, stack trace on this page just says NPE Exception) on the first load of a jenkins page. After reloading I am still logged in and everything is fine again. Project: Jenkins Priority: Minor Reporter: Björn Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt commented on JENKINS-24244 Polling of Mercurial scm stoped working Well, instead of marking this issue at resolved, you could have just asked for more info. That is the reason I posted this issue; though the community/maintainers would request more info when needed or guide a user to get some... here's the requested info: Polling used to work just fine. We have lots of other build which still work fine. As stated, the polling runs only once after restart of Jenkins. The plugin version is 1.50. We are only using Mercurial, so I cannot say whether or not other SCMs do work. Seems like you are not using caching. Not sure what you mean, were can I check this. If you or others need any more info or guide me to get logging or something, I would be more than happy to provide 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/d/optout.
[JIRA] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt reopened JENKINS-24244 Polling of Mercurial scm stoped working Change By: Rick Oosterholt (19/Aug/14 7:03 AM) Resolution: Incomplete 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/d/optout.
[JIRA] [build-timeout] (JENKINS-24299) Maven project build fails to terminate hanging build process
Tobias Oberlies commented on JENKINS-24299 Maven project build fails to terminate hanging build process From your log, your case seems the latter one. Is that right? Yes, I think so. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [export-params] (JENKINS-24313) Export file to the master
Jonas Bang Christensen created JENKINS-24313 Export file to the master Issue Type: New Feature Assignee: rin_ne Components: export-params Created: 19/Aug/14 7:36 AM Description: Reason: --- To enable synergy with EnvInject plugin (https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin) which in the "Prepare an environment for the run" section has a "Load script and properties files from the master" check-box which will result in loading the "Properties File Path" from the master instead of the target node. This was added to EnvInject plugin in version 0.22 (https://github.com/jenkinsci/envinject-plugin/issues/2). This enables that a job pipeline with manual triggered downstream jobs can transfer parameters downstream without the entire pipeline need to be tied to the same node. New feature request: Add a check-box below "File path" field named "Export file to the master". By checking this option the parameter file will be written to the master in the file path given in "File path" field instead of to the target node. Project: Jenkins Priority: Major Reporter: Jonas Bang Christensen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [security] (JENKINS-17060) Jenkins errors when 'Remember me on this computer' is checked.
Martin Cassidy commented on JENKINS-17060 Jenkins errors when Remember me on this computer is checked. No, croud 2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20698) A lot of JellyTagExceptions in the jenkins.log
Oleg Nenashev updated JENKINS-20698 A lot of JellyTagExceptions in the jenkins.log Change By: Oleg Nenashev (19/Aug/14 8:24 AM) Labels: guijelly Component/s: core Component/s: gui This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20698) A lot of JellyTagExceptions in the jenkins.log
Oleg Nenashev
commented on JENKINS-20698
A lot of JellyTagExceptions in the jenkins.log
/lib/hudson/executors.jelly:81:85: j:when Unmatched braces in the pattern.
The related code in jenkins-1.540:
81: j:when test="${h.hasPermission(exeparent,exeparent.READ)}"
82: a href=""l:breakablevalue="${exeparent.fullDisplayName}"//a#160;a href="" class="model-link inside"l:breakable value="${exe.displayName}"//a
83: t:buildProgressBar build="${exe}" executor="${executor}"/
84: /j:when
Newest versions have the following change in the clause:
https://github.com/jenkinsci/jenkins/commit/2f7a49b7cc503606c3d9d6a472ffef37a04d6b7f
BTW, it should not change anything.
No how it can be related to the browser's locale
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-14089) JUnit report - Quarantine intermittent tests
Stephan Grimm commented on JENKINS-14089 JUnit report - Quarantine intermittent tests is someone still working on that or is there a different solution for muting specific failing tests? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-23688) Headless Linux and Valid ABIs: no ABIs.
Karthik T commented on JENKINS-23688 Headless Linux and Valid ABIs: no ABIs. Hi Should this be fixed on the plugin or atleast added to documentation? I faced this as well (how come everybody doesn't)The only way I found out this fix is through this ticket. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-23431) Google is phasing out OpenID endpoint. Need to move on to G+ sign-in
Karthik T commented on JENKINS-23431 Google is phasing out OpenID endpoint. Need to move on to G+ sign-in Would like to add support to what Ray said, even I am facing this.. Is there a way to get the OpenID provider to work instead? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
SCM/JIRA link daemon commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Code changed in jenkins User: ninian Path: src/main/java/hudson/plugins/claim/DescribableTestAction.java src/test/java/hudson/plugins/claim/ClaimReportTest.java src/test/java/hudson/plugins/claim/ClaimTest.java http://jenkins-ci.org/commit/claim-plugin/d8d105492041032941760adf256642236cffd557 Log: JENKINS-7824: Make the unit tests work and order the list of users such that the current user is selected by default This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
SCM/JIRA link daemon commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Code changed in jenkins User: Marc Carter Path: readme.md src/main/java/hudson/plugins/claim/AbstractClaimBuildAction.java src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.jelly src/main/webapp/help-assignee.html src/test/java/hudson/plugins/claim/ClaimTest.java http://jenkins-ci.org/commit/claim-plugin/c235979ff34b97b707d125d595d7cd330a029802 Log: JENKINS-7824 Allow assigning builds/tests to other users This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
SCM/JIRA link daemon commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Code changed in jenkins User: Marc Carter Path: pom.xml src/test/java/hudson/plugins/claim/ClaimTest.java http://jenkins-ci.org/commit/claim-plugin/cc86aacef6cd87c70fea5ee0ce7c19679969953f Log: JENKINS-7824 testcase to prove default assignee is yourself This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
SCM/JIRA link daemon commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Code changed in jenkins User: ninian Path: pom.xml src/main/java/hudson/plugins/claim/AbstractClaimBuildAction.java src/main/java/hudson/plugins/claim/DescribableTestAction.java src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.jelly src/main/resources/index.jelly http://jenkins-ci.org/commit/claim-plugin/8241d95ed43cbfbc842c88c9c3ce6f862df01a15 Log: JENKINS-7824: Change assign to field to be a drop down list of users from the user DB This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim] (JENKINS-7824) Claim plugin: Allow assigning builds/tests to other users
SCM/JIRA link daemon commented on JENKINS-7824 Claim plugin: Allow assigning builds/tests to other users Code changed in jenkins User: ki82 Path: readme.md src/main/java/hudson/plugins/claim/AbstractClaimBuildAction.java src/main/java/hudson/plugins/claim/DescribableTestAction.java src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.jelly src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary.properties src/main/resources/hudson/plugins/claim/AbstractClaimBuildAction/summary_zh_TW.properties src/main/resources/index.jelly src/main/webapp/help-assignee.html src/main/webapp/help-assignee_zh_TW.html src/test/java/hudson/plugins/claim/ClaimReportTest.java src/test/java/hudson/plugins/claim/ClaimTest.java http://jenkins-ci.org/commit/claim-plugin/dcefc3d941f9598663e35f4994c75bf6f7dac725 Log: Merge pull request #12 from drekbour/assign-claim JENKINS-7824 Allow assigning builds/tests to other users Compare: https://github.com/jenkinsci/claim-plugin/compare/c474b1bd27cf...dcefc3d941f9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-24315) Can't run a pipeline when first job has parameters
Nicolas De Loof created JENKINS-24315 Cant run a pipeline when first job has parameters Issue Type: Bug Assignee: Unassigned Components: build-pipeline Created: 19/Aug/14 9:28 AM Description: When first pipeline job has parameter, the Run button just has no effect. The way DownstreamProjectGridBuilder#doBuild handle this incoming POST request just hide error triggering the job. Project: Jenkins Priority: Major 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/d/optout.
[JIRA] [email-ext] (JENKINS-24314) $CHANGES is empty
Arlo Louis OKeeffe created JENKINS-24314 $CHANGES is empty Issue Type: Bug Assignee: Alex Earl Components: email-ext Created: 19/Aug/14 9:28 AM Description: After updating to 2.38.1 from 2.37.2.2 the CHANGES are no longer printed. When I use CHANGES_SINCE_LAST_SUCCESSS I at least get "Changes for Build #36" but CHANGES is completely empty. Environment: Jenkins 1.575 Email Extension Plugin 2.38.1 Project: Jenkins Priority: Minor Reporter: Arlo Louis OKeeffe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
thetaphi created JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core, ui-changes Created: 19/Aug/14 9:39 AM Description: Since the update to 1.576, the icons generated by plugins on the left navigation bar no longer display. This is throughout the whole userinterface: homepage, job page,... (everywhere). The reason is that the image src URL is generated as "//plugin/...", which makes the browser resolve "plugin" as hostname. URLs starting with "//" mean "same protocol". Project: Jenkins Priority: Major Reporter: thetaphi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
thetaphi updated JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL Change By: thetaphi (19/Aug/14 9:46 AM) Attachment: jenkins-screenshot.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer] (JENKINS-23256) Job hangs trying to resolve Perforce emails, in a non-perforce job
Alex Earl updated JENKINS-23256 Job hangs trying to resolve Perforce emails, in a non-perforce job Change By: Alex Earl (19/Aug/14 9:56 AM) Component/s: email-ext This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24314) $CHANGES is empty
Alex Earl commented on JENKINS-24314 $CHANGES is empty Are you using perforce? See JENKINS-11600 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.567 can't see output and fails
R. H. created JENKINS-24317 Nullpointer Exception on build in version 1.567 cant see output and fails Issue Type: Bug Assignee: Nicolas De Loof Attachments: fail.png Components: core, git Created: 19/Aug/14 10:08 AM Description: I have a strange Problem after upgrading to 1.576. After that i get a Nullpointer exception if i click on "deploy". You can't see the output under "Console output". The output on this page is the following you can see in the screenshot. Log FATAL: null java.lang.NullPointerException In the Background the build is working and he do it but you can't see and the output and it failes. I tried to find some issues in the Logs. But the only thing was: Log Aug 19, 2014 12:05:00 PM WARNUNG hudson.model.Run getEnvironment deprecated call to Run.getEnvironment at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:483) Aug 19, 2014 12:05:00 PM WARNUNG hudson.model.Run getEnvironment deprecated call to Run.getEnvironment at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:483) Aug 19, 2014 12:05:00 PM WARNUNG hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Aug 19, 2014 12:05:00 PM WARNUNG hudson.model.Run getEnvironment deprecated call to Run.getEnvironment at hudson.plugins.git.GitSCM.getParamExpandedRepos(GitSCM.java:355) Aug 19, 2014 12:05:00 PM WARNUNG hudson.plugins.git.GitTool$DescriptorImpl getInstallation invalid gitTool selection Default Aug 19, 2014 12:05:00 PM WARNUNG hudson.model.Run getEnvironment deprecated call to Run.getEnvironment at hudson.plugins.git.GitSCM.getParamExpandedRepos(GitSCM.java:355) Project: Jenkins Priority: Critical Reporter: R. H. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-19568) Support OpenGrok as SCM Browser for Perforce
Paul Allen commented on JENKINS-19568 Support OpenGrok as SCM Browser for Perforce I had a quick look at adding this, most of the work is done except I am not familiar with OpenGrok. Would you be willing to send me some sample urls so I can check the end-point/params correct? I would need the following: View a file Diff a file with an earlier revision View a job/issue View a change-set Thanks, Paul This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer] (JENKINS-24318) Restrict which domains mail is sent to
Per Arnold Blaasmo created JENKINS-24318 Restrict which domains mail is sent to Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: mailer Created: 19/Aug/14 10:19 AM Description: When using Jenkins internally, it is sometimes needed to restrict sending e-mail notification external. There should be possible to add allowed domains in which to send e-mails to. When using Git as VCS the e-mail address of the committers is stored with the commit, and the mailer will the try to send to all users that might have broken the build. If you have cloned an open source project and regularly pulls updates from upstream the mailer might start sending mails to those upstream committers. That is not what you want from an internal Jenkins instance. Project: Jenkins Priority: Major Reporter: Per Arnold Blaasmo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-24076) Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced)
Craig Phillips assigned JENKINS-24076 to Michal Turek Incorrect builds used to generate deltas (No deltas for builds fixed after failure where errors were introduced) There hasn't been any movement on this issue and we are desperate for a fix. Any chance you could take a look. Thanks. Change By: Craig Phillips (19/Aug/14 10:36 AM) Assignee: GregoryBoissinot MichalTurek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24299) Maven project build fails to terminate hanging build process
ikedam updated JENKINS-24299 Maven project build fails to terminate hanging build process Change By: ikedam (19/Aug/14 10:37 AM) Labels: remoting Assignee: KohsukeKawaguchi Component/s: core Component/s: build-timeout Component/s: maven This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24299) Maven project build fails to terminate hanging build process
ikedam updated JENKINS-24299 Maven project build fails to terminate hanging build process This rather looks an issue of Jenkins core, as build-timeout only aborts build steps and cannot abort hanged threads. I changed the component. Let me know followings: The version of your Jenkins. Do you run Jenkins on master / slave mode? https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds Can you reproduce the problem if needed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen commented on JENKINS-24055 Matrix Job Unable To Sync The error message "rsmsnbuild119 is a client, not a label" suggest that you have provided a client workspace name and not a label? Was this intended? I know in Perforce you can sync at a client workspace, but the use case for Jenkins is not clear to me? The good news is that the "For input string: "3605760456"" error has gone, and looked like it was due to an invalid serialized object. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24314) $CHANGES is empty
Arlo Louis OKeeffe updated JENKINS-24314 $CHANGES is empty Change By: Arlo Louis OKeeffe (19/Aug/14 11:01 AM) Environment: Jenkins1.575EmailExtensionPlugin2.38.1 GITclientplugin1.10.1GITplugin2.2.5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24314) $CHANGES is empty
Arlo Louis OKeeffe commented on JENKINS-24314 $CHANGES is empty No, I'm using git. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24314) $CHANGES is empty
Alex Earl commented on JENKINS-24314 $CHANGES is empty You were using the same Jenkins and Git plugin versions previously? Updating email-ext was the only thing you did? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
Shannon Kerr commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL I see the same, but after rebooting the host I'm now no longer able to even login to Jenkins (we use AD authentication). Going to have to roll back to 1.575. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [windows-slaves] (JENKINS-24319) Windows slave dying during build - unsatisfied link error
Andy Walker created JENKINS-24319 Windows slave dying during build - unsatisfied link error Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: windows-slaves Created: 19/Aug/14 11:08 AM Description: Windows slaved builds fail with the following error on the master: 11:56:20 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Failed to abort 11:56:20 hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Failed to abort 11:56:20 at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) 11:56:20 at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) 11:56:20 at hudson.remoting.Request.call(Request.java:174) 11:56:20 at hudson.remoting.Channel.call(Channel.java:739) 11:56:20 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) 11:56:20 at com.sun.proxy.$Proxy58.join(Unknown Source) 11:56:20 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:956) 11:56:20 at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) 11:56:20 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) 11:56:20 at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) 11:56:20 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 11:56:20 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772) 11:56:20 at hudson.model.Build$BuildExecution.build(Build.java:199) 11:56:20 at hudson.model.Build$BuildExecution.doRun(Build.java:160) 11:56:20 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535) 11:56:20 at hudson.model.Run.execute(Run.java:1740) 11:56:20 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 11:56:20 at hudson.model.ResourceController.execute(ResourceController.java:88) 11:56:20 at hudson.model.Executor.run(Executor.java:234) 11:56:20 Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Failed to abort 11:56:20 at hudson.remoting.Request.abort(Request.java:299) 11:56:20 at hudson.remoting.Channel.terminate(Channel.java:802) 11:56:20 at hudson.remoting.Channel$2.terminate(Channel.java:483) 11:56:20 at hudson.remoting.AbstractByteArrayCommandTransport$1.terminate(AbstractByteArrayCommandTransport.java:72) 11:56:20 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:195) 11:56:20 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:581) 11:56:20 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) 11:56:20 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) 11:56:20 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) 11:56:20 at java.util.concurrent.FutureTask.run(FutureTask.java:138) 11:56:20 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) 11:56:20 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) 11:56:20 at java.lang.Thread.run(Thread.java:695) 11:56:20 Caused by: java.io.IOException: Failed to abort 11:56:20 ... 9 more 11:56:20 Caused by: java.io.IOException: Connection reset by peer 11:56:20 at sun.nio.ch.FileDispatcher.read0(Native Method) 11:56:20 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:21) 11:56:20 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:198) 11:56:20 at sun.nio.ch.IOUtil.read(IOUtil.java:171) 11:56:20 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:245) 11:56:20 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:136) 11:56:20 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:306) 11:56:20 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:514) 11:56:20 ... 7 more And the following warning on the slave agent: Aug 19, 2014 11:51:09 AM hudson.util.ProcessTree get WARNING: Failed to load winp. Reverting to
[JIRA] [copyartifact] (JENKINS-24152) Add an option to copy artifacts to trigger job for all upstream jobs copied from
Johannes Wienke commented on JENKINS-24152 Add an option to copy artifacts to trigger job for all upstream jobs copied from Every job can be triggered by upstream jobs. There is an input field in the "Build Triggers" section of a job called "Build after other projects are built". What I would like to have is that this field is automatically populated (maybe somehow invisible) with all the upstream jobs I use to copy artifacts from. Does this clarify the request? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24314) $CHANGES is empty
Arlo Louis OKeeffe commented on JENKINS-24314 $CHANGES is empty Now that I looked it up, I did not update the email-ext at all. Have a look at my update history: https://gist.github.com/ArloL/7b07f9240a2cf386d652 Sadly the Jenkins logs do not contain the versions :/ According to Jenkins the previous version of Git client plugin was 1.10.1 also and GIT plugin was 2.2.4. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24314) $CHANGES is empty
Alex Earl commented on JENKINS-24314 $CHANGES is empty Can you see if there are any errors in your log files? If you haven't updated email-ext, what changed in your system? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
Shannon Kerr commented on JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL My login issue is different. It's because I checked the remember me button at login. This appears to be a new issue as well. I'll raise a ticket. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.567 can't see output and fails
Mike Penz commented on JENKINS-24317 Nullpointer Exception on build in version 1.567 cant see output and fails I get the same issue. Only solution right now is to let jenkins start 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/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.567 can't see output and fails
Mike Penz commented on JENKINS-24317 Nullpointer Exception on build in version 1.567 cant see output and fails Our log output is following: Aug 19, 2014 1:26:09 PM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: it.userName in /view/TAGM2M/job/tagm2m_test/job/TAGM2M_TNS_SendForm_Profiles_TEST/20/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.kohsuke.stapler.jelly.InternationalizedStringExpression.evaluateArguments(InternationalizedStringExpression.java:152) at org.kohsuke.stapler.jelly.InternationalizedStringExpression.access$000(InternationalizedStringExpression.java:56) at org.kohsuke.stapler.jelly.InternationalizedStringExpression$1.evaluate(InternationalizedStringExpression.java:166) at org.apache.commons.jelly.impl.ExpressionScript.run(ExpressionScript.java:66) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.567 can't see output and fails
R. H. commented on JENKINS-24317 Nullpointer Exception on build in version 1.567 cant see output and fails Thats not very good... But ok i have installed the preview version and that was working. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project] (JENKINS-24320) Can't login to jenkins-wiki
Paul Pacurar created JENKINS-24320 Cant login to jenkins-wiki Issue Type: Bug Assignee: Unassigned Components: authorize-project Created: 19/Aug/14 11:39 AM Description: Can't login to jenkis wiki page. I'created new account, changed password (or not), but still not accepted in the wiki. I want to add comments to a plugin which has issues, but can't. Project: Jenkins Priority: Major Reporter: Paul Pacurar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Shannon Kerr updated JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails Changed version mentioned in Summary to reflect the same version discussed in the Description. Change By: Shannon Kerr (19/Aug/14 11:45 AM) Summary: NullpointerExceptiononbuildinversion1. 567 576 cantseeoutputandfails This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24294) Very slow UI
Vincent Massol edited a comment on JENKINS-24294 Very slow UI I was asked to report such issues here in the past and I did and they were looked at and fixed. I consider performance an important feature of a software and when it's not working, it's a bug for me and bugs are reported in JIRA But ok, I understand that the causes can be varied and could come from my setup and not be a generic issue. I'll take it on the list, hoping for someone to look at it. In the meantime and FYI I've upgraded to the latest jenkins version (1.576 I think - can't access our ci instance to check ATM...) and the problem persists (I wonder if it's not worse actually since now our apache server in front even times out from time to time, after several minutes of waiting). 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/d/optout.
[JIRA] [core] (JENKINS-24294) Very slow UI
Vincent Massol commented on JENKINS-24294 Very slow UI I was asked to report such issues here in the past and I did and they were looked at and fixed. I consider performance an important feature of a software and when it's not working, it's a bug for me and bugs are reported in JIRA But ok, I understand that the causes can be varied and could come from my setup and not be a generic issue. I'll take it on the list, hoping for someone to look at it. In the meantime and FYI I've upgraded to the latest jenkins version () and the problem persists (I wonder if it's not worse actually since now our apache server in front even times out from time to time, after several minutes of waiting). 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/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Mike Penz edited a comment on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails Ok i did some more research. It seems the error i posted above happens if a user tries to login. It will show StackTrace: java.lang.NullPointerException If i click on the build button it shows the same Log Output as R. H. mentioned in the description. This also happens on svn builds so it should not be caused by git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24322) SCM pooling triggers builds one after another and never stops
Daniel Anechitoaie created JENKINS-24322 SCM pooling triggers builds one after another and never stops Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 19/Aug/14 12:04 PM Description: After updating https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin to Version 2.2.5 (Aug 15, 2014) all my jobs that are configured to pull the SCM @hourly started doing builds like crazy one after another even if there were no SCM changes and also having it configured to check @hourly. After i downgraded to previous version Version 2.2.4 (Aug 2, 2014), everything is working fine again. Maybe this is related to this fix http://issues.jenkins-ci.org/browse/JENKINS-22009 Stept to reproduce: 1. Have a build that's already configured and working (Multiple SCMs plugin 0.3 - configured with 2 GIT sources and @hourly pooling for changes to trigger the build) 2. Update the Git plugin to Version 2.2.5 3. Go to your working job 4. Update any setting there (I've just had the branch changed) 5. Press Apply and start a build. (now Jenkins should start doing builds like crazy one after another always because it was "triggered by a SCM change" where if you go to changes there will be none. Environment: Jenkins ver. 1.575 Git plugin Version 2.2.5 Multiple SCMs plugin 0.3 - configured with 2 GIT sources and @hourly pooling for changes to trigger the build. Project: Jenkins Priority: Blocker Reporter: Daniel Anechitoaie This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24322) SCM pooling triggers builds one after another and never stops
Daniel Anechitoaie updated JENKINS-24322 SCM pooling triggers builds one after another and never stops Change By: Daniel Anechitoaie (19/Aug/14 12:05 PM) Priority: Blocker Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-24321) Random NPE at login after upgrade to 1.576
Shannon Kerr resolved JENKINS-24321 as Duplicate Random NPE at login after upgrade to 1.576 Duplicate of Jenkins-24317? Change By: Shannon Kerr (19/Aug/14 12:06 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
R. H. commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails Nice suggestion. We use LDAP, 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/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Mike Penz commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails R. H. if you open the jenkins security configuration page (configureSecurity) does it show an error for your ldap configuration? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Shannon Kerr commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails I had opened Jenkins-24321, but I think it's the same as this. I didn't see anyone mention the NPE was login related, so I thought my NPE was unique. We use Active Directory and SVN. I'm see ing this during login, but can quickly go back to the login page and hit the "log in" button again and login without an NPE. It didn't matter if "Remember me on this computer" was checked or not. I can reproduce the NPE probably 100% of the time by logging out and attempting to login again. Seems like first attempt always fails. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Mike Penz commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails Shannon Kerr - I can also reproduce this issue to 100%. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-24323) Could not copy slave.jar into '/users/ccfw73' on slave
paul collins created JENKINS-24323 Could not copy slave.jar into /users/ccfw73 on slave Issue Type: New Feature Assignee: Oliver Gondža Components: acceptance-test-harness Created: 19/Aug/14 12:25 PM Description: When we disconnect the slave and then try to reconnect it we getting the error that it cannot get the slave jar from within the Jenkins.war file. This is repeatable across all our slaves. See output of error below: 08/19/14 10:25:29 SSH Copying latest slave.jar... hudson.util.IOException2: Could not copy slave.jar into '/users/ccfw73' on slave at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:821) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:496) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:228) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) Caused by: hudson.util.IOException2: Could not copy slave.jar to '/users/ccfw73/slave.jar' on slave at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:818) ... 7 more Caused by: java.io.FileNotFoundException: /target/jenkins/WEB-INF/slave.jar (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:137) at java.io.FileInputStream.init(FileInputStream.java:96) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection.java:87) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLConnection.java:178) at hudson.model.Slave$JnlpJar.readFully(Slave.java:335) at hudson.plugins.sshslaves.SSHLauncher.copySlaveJar(SSHLauncher.java:809) ... 7 more 08/19/14 10:25:29 SSH Connection closed. Due Date: 19/Aug/14 12:00 AM Environment: Linux Project: Jenkins Labels: jenkins Priority: Blocker Reporter: paul collins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Mark Waite updated JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails Change By: Mark Waite (19/Aug/14 12:28 PM) Component/s: git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-19568) Support OpenGrok as SCM Browser for Perforce
NetAppBlueDevil commented on JENKINS-19568 Support OpenGrok as SCM Browser for Perforce Using markers to note values View a file http://opengrok-server/source/xref/opengrok-project-name/filepath-within-depot So, if the file in P4 is //depot/production/project/main/dir1/dir2/file filepath-within-depot would be dir1/dir2/file File diff with earlier version http://opengrok-server/source/diff/opengrok-project-name/build.properties?r2=%2Fopengrok-project-name%2filepath-within-depot-url-encoded%40p4-changer1=%2Fopengrok-project-name%2Ffilepath-within-depot-url-encoded%40p4-change NOTE %2F - URL encoded / %40 - URL encoded @ View a job/issue View a change-set For these 2 it looks like we have customized our version of OpenGrok to reference these to our internal tools that track issues and related changesets. From the Opengrok source, it doesn't look like there are any paths/servlets that would make sense to be handling change number as the only query input or a bug/issue number as the same https://github.com/OpenGrok/OpenGrok/blob/50c60fa3feefb22293e30dfba92e0d571db5cd6b/web/WEB-INF/web.xml This issue would seem to support the idea that this is not available as a feature https://github.com/OpenGrok/OpenGrok/issues/392 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Andreas Katzig commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Thanks for getting back Daniel. I did what you recommended, but the log doesn't tell me anything interesting: Aug 19, 2014 2:05:19 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3688/user/xxx/__USER; Realm: svn://svnserver:3688 REALMNAME Aug 19, 2014 2:05:19 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3688/user/xxx/__USER; Realm: svn://svnserver:3688 REALMNAME Aug 19, 2014 2:05:20 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3698/Library/branches/yyy-0.1/Tools/Tool1; Realm: svn://svnserver:3698 REALMNAME Aug 19, 2014 2:05:21 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3688/xxx/code/trunk; Realm: svn://svnserver:3688 REALMNAME The build to which the log above belongs failed again. I figured out that the build always fails the first time some changes are checked in to SVN (still funny that the next checkout/build will succeed). To explain our SVN infrastructure a bit: We use initial checkout paths which contain only svn:externals, which are pointing to different source paths and also different repositories (as you can see with the port number). The error "hudson.util.IOException2: revision check failed on ..."always happens on the first external - in case of the above log it's "svn://xxx:3688/zzz/code/trunk". The external property pointing to the same repo is defined like this: "^/zzz/code/trunk localpath" External properties pointing to different repositories are defined like this: "svn://svnserver:3698/remotepath localpath" What I saw in the SCM logs was that some repositories are trying to connect to the SVN server via IP, which would not work when the realm is defined with the hostname. This doesn't affect the current build I'm talking about though, or at least not in a way I'm able to comprehend. Unfortunately the SCM log does not show which build job triggert SVN activity - I set the log level to "finer" (and will try below), maybe I'll find something that helps. I will also try to replace the circumflex "^" in the external definition with the absolute hostname. Will give feedback if that helped, but I would hate to change that for our 20+ repositories with 5 externals checkout paths each (would 100 changes) Any more clues? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Andreas Katzig edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Thanks for getting back Daniel. I did what you recommended, but the log doesn't tell me anything interesting: Aug 19, 2014 2:05:19 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3688/user/xxx/__USER; Realm: svn://svnserver:3688 REALMNAME Aug 19, 2014 2:05:19 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3688/user/xxx/__USER; Realm: svn://svnserver:3688 REALMNAME Aug 19, 2014 2:05:20 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3698/Library/branches/yyy-0.1/Tools/Tool1; Realm: svn://svnserver:3698 REALMNAME Aug 19, 2014 2:05:21 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3688/xxx/code/trunk; Realm: svn://svnserver:3688 REALMNAME The build to which the log above belongs failed again. I figured out that the build always fails the first time some changes are checked in to SVN (still funny that the next checkout/build will succeed). To explain our SVN infrastructure a bit: We use initial checkout paths which contain only svn:externals, which are pointing to different source paths and also different repositories (as you can see with the port number). The error "hudson.util.IOException2: revision check failed on ..."always happens on the first external - in case of the above log it's "svn://xxx:3688/zzz/code/trunk". The external property pointing to the same repo is defined like this: "^/zzz/code/trunk localpath" External properties pointing to different repositories are defined like this: "svn://svnserver:3698/remotepath localpath" Screenshot from the SVN settings within the build job: What I saw in the SCM logs was that some repositories are trying to connect to the SVN server via IP, which would not work when the realm is defined with the hostname. This doesn't affect the current build I'm talking about though, or at least not in a way I'm able to comprehend. Unfortunately the SCM log does not show which build job triggert SVN activity - I set the log level to "finer" (and will try below), maybe I'll find something that helps. I will also try to replace the circumflex "^" in the external definition with the absolute hostname. Will give feedback if that helped, but I would hate to change that for our 20+ repositories with 5 externals checkout paths each (would 100 changes) Any more clues? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Andreas Katzig edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials We still encounter this issue, although I read through all comments and have configured everything accordingly and correct (in my opinion). We use Jenkins ver. 1.565.1 with Subversion plugin 2.4.1. We're using externals, build servers nodes, I added additional credentials for them, took care of the correct naming with its correct realm and brackets. Every random build does fail with the following exception, and this issue is really getting very very frustrating because the next build is working fine then. The Subversion plugin should be updated to improve the user experience (and functionality). no change for svn://xxx:3688/user/yyy/aaa since the previous build hudson.util.IOException2: revision check failed on svn://xxx:3688/zzz/code/trunk at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:191) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:735) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:873) at hudson.model.AbstractProject.checkout(AbstractProject.java:1252) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:615) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:524) at hudson.model.Run.execute(Run.java:1706) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:232) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.createSaslClient(SVNSaslAuthenticator.java:306) at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.authenticate(SVNSaslAuthenticator.java:92) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.authenticate(SVNConnection.java:194) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.authenticate(SVNRepositoryImpl.java:1275) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1253) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:168) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:179) ... 11 more Finished: FAILURE 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
[JIRA] [email-ext] (JENKINS-24324) Not the full log gets attached
Michael Dänzer created JENKINS-24324 Not the full log gets attached Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 19/Aug/14 12:44 PM Description: We have console log files that can get pretty big (around 50 lines). I need to send the log together with the mails about the build results as some of our committers cannot access the Jenkins directly. But the log files is always cut after around 5180 lines. Environment: Master server on Linux, Slave on Windows Project: Jenkins Labels: email-ext Priority: Major Reporter: Michael Dänzer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Andreas Katzig edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Thanks for getting back Daniel. I did what you recommended, but the log doesn't tell me anything interesting: Aug 19, 2014 2:05:19 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3688/user/xxx/__USER; Realm: svn://svnserver:3688 REALMNAME Aug 19, 2014 2:05:19 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3688/user/xxx/__USER; Realm: svn://svnserver:3688 REALMNAME Aug 19, 2014 2:05:20 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3698/Library/branches/yyy-0.1/Tools/Tool1; Realm: svn://svnserver:3698 REALMNAME Aug 19, 2014 2:05:21 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3688/xxx/code/trunk; Realm: svn://svnserver:3688 REALMNAME The build to which the log above belongs failed again. I figured out that the build always fails the first time some changes are checked in to SVN (still funny that the next checkout/build will succeed). To explain our SVN infrastructure a bit: We use initial checkout paths which contain only svn:externals, which are pointing to different source paths and also different repositories (as you can see with the port number). The error "hudson.util.IOException2: revision check failed on ..."always happens on the first external - in case of the above log it's "svn://xxx:3688/zzz/code/trunk". The external property pointing to the same repo is defined like this: "^/zzz/code/trunk localpath" External properties pointing to different repositories are defined like this: "svn://svnserver:3698/remotepath localpath" Screenshot from the SVN settings within the build job: What I saw in the SCM logs was that some repositories are trying to connect to the SVN server via IP, which would not work when the realm is defined with the hostname. This doesn't affect the current build I'm talking about though, or at least not in a way I'm able to comprehend. Unfortunately the SCM log does not show which build job triggert SVN activity - I set the log level to "finer" (and will try below), maybe I'll find something that helps. I will also try to replace the circumflex "^" in the external definition with the absolute hostname. Will give feedback if that helped, but I would hate to change that for our 20+ repositories with 5 externals checkout paths each (would 100 changes) After checking the next build, which succeeds, I'm also sure that SVN is not trying to connect to the server via IP instead of the hostname. Any more clues? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-23986) Permissions check in ExtendedEmailPublisher.getProjectActions does not work
Alex Earl closed JENKINS-23986 as Duplicate Permissions check in ExtendedEmailPublisher.getProjectActions does not work Change By: Alex Earl (19/Aug/14 12:47 PM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Andreas Katzig edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Thanks for getting back Daniel. I did what you recommended, but the log doesn't tell me anything interesting: Aug 19, 2014 2:05:19 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3688/user/xxx/__USER; Realm: svn://svnserver:3688 REALMNAME Aug 19, 2014 2:05:19 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3688/user/xxx/__USER; Realm: svn://svnserver:3688 REALMNAME Aug 19, 2014 2:05:20 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3698/Library/branches/yyy-0.1/Tools/Tool1; Realm: svn://svnserver:3698 REALMNAME Aug 19, 2014 2:05:21 PM FINE hudson.scm.CredentialsSVNAuthenticationProviderImpl requestClientAuthentication Attempting auth for URL: svn://svnserver:3688/xxx/code/trunk; Realm: svn://svnserver:3688 REALMNAME The build to which the log above belongs failed again. I figured out that the build always fails the first time some changes are checked in to SVN (still funny that the next checkout/build will succeed). To explain our SVN infrastructure a bit: We use initial checkout paths which contain only svn:externals, which are pointing to different source paths and also different repositories (as you can see with the port number). The error "hudson.util.IOException2: revision check failed on ..."always happens on the first external - in case of the above log it's "svn://xxx:3688/zzz/code/trunk". The external property pointing to the same repo is defined like this: "^/zzz/code/trunk localpath" External properties pointing to different repositories are defined like this: "svn://svnserver:3698/remotepath localpath" Screenshot from the SVN settings within the build job: What I saw in the SCM logs was that some repositories are trying to connect to the SVN server via IP, which would not work when the realm is defined with the hostname. This doesn't affect the current build I'm talking about though, or at least not in a way I'm able to comprehend. Unfortunately the SCM log does not show which build job was triggering SVN activity - I'll try to set the log level to "finer", maybe I'll find something that helps. I will also try to replace the circumflex "^" in the external definition with the absolute hostname. Will give feedback if that helped, but I would hate to change that for our 20+ repositories with 5 externals checkout paths each (would 100 changes) After checking the next build, which succeeds, I'm also sure that SVN is not trying to connect to the server via IP instead of the hostname. Any more clues? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24324) Not the full log gets attached
Alex Earl closed JENKINS-24324 as Duplicate Not the full log gets attached Change By: Alex Earl (19/Aug/14 12:49 PM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scriptler] (JENKINS-24325) Tokem macro expansion doesn't happen in Run a script parameters
Paul Sokolovsky
created JENKINS-24325
Tokem macro expansion doesnt happen in Run a script parameters
Issue Type:
Bug
Affects Versions:
current
Assignee:
Dominik Bartholdi
Components:
scriptler
Created:
19/Aug/14 12:49 PM
Description:
When running script via "Run a script" action (/scriptler/runScript), it turns out that values supplied to script parameters are not expanded using Token Macro plugin.
This is highly confusing, as the docs page https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin#ScriptlerPlugin-TokenMacroSupport explicitly says "as a consumer, scriptler accepts tokens in the passed arguments".
Overall, with a freshly installed Jenkins, it is impossible to easily test and try token macro facility. After trying this and that, I finally thought that Scriptler would be my best friend for testing token macros, but turned out to be another wall to bang head against.
So, in the end, it turns out that tokens are expanded in values for Scriptler actions specified as job's build step. Again, they are not expanded when running script directly.
Steps to reproduce:
1. Create a token macro handler in Scriptler itself, based on the example in docs: https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin#ScriptlerPlugin-TokenMacroSupport
2. Create another Scriptler script with just "println param", then try to run it, setting "param" argument to "${SCRIPTLER, scriptId="superscript.groovy"}"
Expected result: date string to be printed
Actual result: "${SCRIPTLER, scriptId="superscript.groovy"}" is printed literally.
Project:
Jenkins
Priority:
Major
Reporter:
Paul Sokolovsky
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [scriptler] (JENKINS-24325) Token macro expansion doesn't happen in Run a script parameters
Paul Sokolovsky updated JENKINS-24325 Token macro expansion doesnt happen in Run a script parameters Change By: Paul Sokolovsky (19/Aug/14 12:49 PM) Summary: Tokem Token macroexpansiondoesnthappeninRunascriptparameters This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scriptler] (JENKINS-24325) Scriptler: Token macro expansion doesn't happen in Run a script parameters
Paul Sokolovsky updated JENKINS-24325 Scriptler: Token macro expansion doesnt happen in Run a script parameters Change By: Paul Sokolovsky (19/Aug/14 12:50 PM) Summary: Scriptler: TokenmacroexpansiondoesnthappeninRunascriptparameters This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-template] (JENKINS-23866) Templates are not saved to disk after an edit
Alex Earl commented on JENKINS-23866 Templates are not saved to disk after an edit I'll look into this one soon, for some reason JIRA is not sending out emails, so I wasn't aware of new issues coming in. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
michael soukup commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials if this is your screenshot then you have a typo in the port: 3688 - 3698 try with the same port and see if that solves your problem This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24314) $CHANGES is empty
Arlo Louis OKeeffe commented on JENKINS-24314 $CHANGES is empty The logs report several warnings. Also note that the changelog on the build are also empty. It looks like it's not a problem in email-ext. Aug 02, 2014 7:08:00 AM hudson.model.Run getEnvironment Warnung: deprecated call to Run.getEnvironment at hudson.plugins.git.GitSCM.getParamExpandedRepos(GitSCM.java:351) Aug 02, 2014 7:08:05 AM hudson.model.Run getEnvironment Warnung: deprecated call to Run.getEnvironment at hudson.plugins.git.GitSCM.getParamLocalBranch(GitSCM.java:339) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Ryan Hummer commented on JENKINS-24055 Matrix Job Unable To Sync The job is setup correctly, as the parent job did sync successfully. All of the slaves that are triggered failed with that message. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Andreas Katzig commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials It's not a typo, it's a different repository. Repo on port #3688 is the main repositories with externals pointing to the repo on port #3698. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
michael soukup commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials yes, but you have no additional credits for the 3688 port defined. So I thought that you have to add credits for that one, 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/d/optout.
[JIRA] [email-ext] (JENKINS-24314) $CHANGES is empty
Alex Earl commented on JENKINS-24314 $CHANGES is empty I agree, I will close this out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24314) $CHANGES is empty
Alex Earl closed JENKINS-24314 as Not A Defect $CHANGES is empty Change By: Alex Earl (19/Aug/14 1:21 PM) Status: Open Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
michael soukup edited a comment on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials yes - understood, but you have no additional credits for the 3688 port defined. I thought that you would have to add additional credentials for both ports / repositories. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [instant-messaging] (JENKINS-5031) instant-messaging plugin notifications with custom messages
Antoine Musso
commented on JENKINS-5031
instant-messaging plugin notifications with custom messages
For what it is worth, the messages are defined in: src/main/resources/hudson/plugins/im/build_notify/Messages.properties
SummaryOnlyBuildToChatNotifier.Summary=Project {0} build {1}: {2} in {3}: {4}
SummaryOnlyBuildToChatNotifier.BuildIsFixed=Yippee, build fixed!\n
SummaryOnlyBuildToChatNotifier.StartMessage=Starting build {0} for job {1}
I would love an option to at least disable the BuildIsFixed message. The two other messages should be changeable in the interface, probably globally and on a per job basis. The Summary message shows the job URL which already contains the job name and build number, not much point in repeating them.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Mark Waite commented on JENKINS-24304 Enable/Disable verbose Git command logging in Jenkins build log Could you try the log parser plugin as an alternative? I think the enhancement request is reasonable, but the log parser plugin may give you that already, without waiting for someone to choose to implement your request This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [thinBackup] (JENKINS-24302) backup ends before all jobs are backed-up if option Backup build results is switched on
Markus Schlegel updated JENKINS-24302 backup ends before all jobs are backed-up if option Backup build results is switched on The job's folder contains "shortcut" folders (see attached screenshot). Is this the problem? This is kind of normal for jenkins running on windows... Change By: Markus Schlegel (19/Aug/14 1:38 PM) Attachment: sf501.sf.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [all-changes] (JENKINS-23964) Opening the 'All Changes' page causes jelly.JellyTagException (Caused by MalformedURLException: no protocol
Scott Lavender commented on JENKINS-23964 Opening the All Changes page causes jelly.JellyTagException (Caused by MalformedURLException: no protocol I have a similar issue. When I browsed to my Jenkins main page today, I see the following instead of my view tabs: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/devcentral/service/ci/jenkins/master/apsd1lc9a006/war/WEB-INF/lib/jenkins-core-1.574.jar!/hudson/model/View/index.jelly:42:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/devcentral/service/ci/jenkins/master/apsd1lc9a006/war/WEB-INF/lib/jenkins-core-1.574.jar!/lib/hudson/projectView.jelly:66:22: d:invokeBody java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Andreas Katzig commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Yes, didn't add them because I thought it would be enough to have them defined above (As this is also the place were an error message is displayed if credentials are invalid or missing). So I'd have to define the main repositorie's credentials twice? What the actual #$+ Will try and give feedback. We should really put some conclusion in big letters below this thread about what one have to pay attention to until the plugin's functionality is improved. It's already too many trial+error comments which may mislead the readers in here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Jesse Glick resolved JENKINS-24244 as Incomplete Polling of Mercurial scm stoped working Resolved/Incomplete includes the state of waiting for more information. There is an open proposal to add a dedicated status for this purpose to this JIRA instance, in which case Incomplete could be reserved for abandoned issues, but that does not seem to have been implemented yet. There needs to be some mechanism for differentiating acknowledged open bugs, from conversations that may or may not be a real bug in some component or another (i.e., support requests). I would start by adding a logger recording hudson.triggers.SCMTrigger and hudson.triggers.Trigger at fine levels, checking $JENKINS_HOME/scm-polling.log, and generally checking log files for errors. If that turns up nothing special, use a debugger. Change By: Jesse Glick (19/Aug/14 1:52 PM) Status: Reopened Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24326) View Tab Replaced with JellyTagException/NullPointerException
Scott Lavender created JENKINS-24326 View Tab Replaced with JellyTagException/NullPointerException Issue Type: Bug Assignee: Unassigned Components: core Created: 19/Aug/14 1:51 PM Description: When I browsed to my Jenkins main page today, I see the following instead of my view tabs: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/devcentral/service/ci/jenkins/master/apsd1lc9a006/war/WEB-INF/lib/jenkins-core-1.574.jar!/hudson/model/View/index.jelly:42:43: st:include org.apache.commons.jelly.JellyTagException: jar:file:/devcentral/service/ci/jenkins/master/apsd1lc9a006/war/WEB-INF/lib/jenkins-core-1.574.jar!/lib/hudson/projectView.jelly:66:22: d:invokeBody java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at
[JIRA] [script-security] (JENKINS-22834) Administrator-approved classpath additions
Jesse Glick started work on JENKINS-22834 Administrator-approved classpath additions Change By: Jesse Glick (19/Aug/14 1:57 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/d/optout.
[JIRA] [core] (JENKINS-24316) Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL
Daniel Beck updated JENKINS-24316 Plugin icons do not show in left navigation: duplicate slash before plugin path in image URL Probably was never tested with empty context path... Change By: Daniel Beck (19/Aug/14 2:03 PM) Assignee: TomFENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-user-vars] (JENKINS-24326) View Tab Replaced with JellyTagException/NullPointerException
Daniel Beck updated JENKINS-24326 View Tab Replaced with JellyTagException/NullPointerException Caused by Build User Env Vars plugin. Workaround: Disable or uninstall that plugin. Fixed in https://github.com/jenkinsci/build-user-vars-plugin/commit/9a7ea4a8504c1871635c59065d8647df479a but unreleased. You could always build it yourself and install the snapshot. Assigning to Nicolas: FYI in case you want to do a release. Change By: Daniel Beck (19/Aug/14 2:09 PM) Assignee: NicolasDeLoof Component/s: build-user-vars Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Daniel Beck commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails Is this related to JENKINS-24312? Does the description there make sense to any of you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer] (JENKINS-24214) Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10
Daniel Beck resolved JENKINS-24214 as Fixed Test email fails with javax.mail.AuthenticationFailedException in mailer v1.10 Resolving based on Jesse's comments. (Bot being lazy?) Change By: Daniel Beck (19/Aug/14 2:14 PM) Status: InProgress 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/d/optout.
[JIRA] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Daniel Beck commented on JENKINS-24244 Polling of Mercurial scm stoped working By navigating to /job/foo/polling you can trigger polling for a specific job manually. Does that work and update the job's polling log? What's the output at /descriptor/hudson.triggers.SCMTrigger/ URL? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Daniel Beck commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials We should really put some conclusion in big letters below this thread about what one have to pay attention to until the plugin's functionality is improved. It's already too many trial+error comments which may mislead the readers in here. Tried that for a few issues, people kept on posting comments and those that came after didn't bother reading everything. So doesn't work. Edit the issue description again. But seriously, there's no magic going on. It's a straightforward key lookup. If it looks for a string that you don't supply exactly, it won't work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
stephenconnolly commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @Andreas, I agree it is a bit of a pain... any suggestions as to how to not permit drive-by credential scraping and at the same time make this easier to use are welcome. FYI the drive-by credential scraping is not theoretical, I know of at least one incident (of which I cannot say more) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-24244) Polling of Mercurial scm stoped working
Rick Oosterholt commented on JENKINS-24244 Polling of Mercurial scm stoped working Thanks Daniel for helping out and guiding me. Yes, when navigating to /job/foo/polling, the build is scheduled/executed and the polling log is updated. output of /descriptor/hudson.triggers.SCMTrigger: Current SCM Polling Activities No polling activity is in progress. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Mike Penz commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails Not really. The login issue also happens if i logout and instantly try a login afterwards. It's a critical issue for us because no user can trigger a build right now. Just a small workaround (let jenkins start the build (start build by time * * * * * and remove this afterwards)) works. We will have to reset the whole jenkins server to a previous state if this can't be solved in the next two days. (We got daily backups) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
Shannon Kerr commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails I agree with Mike Penz, unrelated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24317) Nullpointer Exception on build in version 1.576 can't see output and fails
R. H. commented on JENKINS-24317 Nullpointer Exception on build in version 1.576 cant see output and fails @Daniel Beck: Not thats not the Problem. @Mike Penz: You can very easy download an older .deb file and install it. Thats no problem. Go to the last Version and its working well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Paul Allen
commented on JENKINS-24055
Matrix Job Unable To Sync
Is the configuration the same as when you opened the issue?
Workspace: Static
Character set: None
Workspace Name: ${NODE_NAME}
Populate Options: Sync Only, populate have list, pin to label unchecked
Polling Filters: None
Repo Browser: Auto
or are you specifying a Label, using the 'pin to label' or as a build param?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24055) Matrix Job Unable To Sync
Ryan Hummer commented on JENKINS-24055 Matrix Job Unable To Sync Yes, the configuration is the same as when I initially opened 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/d/optout.
[JIRA] [core] (JENKINS-20858) Images missing from Jenkins UI
Jonathan Langevin commented on JENKINS-20858 Images missing from Jenkins UI In 1.576, seeing a similar issue where plugin images for the left nav menu are broken. Inspecting the images in browser shows URL of //plugin/config-rotator/images/rotate.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-user-vars] (JENKINS-24326) View Tab Replaced with JellyTagException/NullPointerException
Scott Lavender resolved JENKINS-24326 as Duplicate View Tab Replaced with JellyTagException/NullPointerException Duplicate of JENKINS-23363 Change By: Scott Lavender (19/Aug/14 2:45 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
