[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
Balthasar Nebel commented on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled I am having the same problem with Jenkins 1.502 on Linux (Oracle JDK 1.6.0_39). For some unknown reason not all my jobs are having this 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/groups/opt_out.
[JIRA] (JENKINS-16684) Add GIT_URL to build environment
Nicolas De Loof resolved JENKINS-16684 as Fixed Add GIT_URL to build environment Change By: Nicolas De Loof (20/Feb/13 8:50 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16684) Add GIT_URL to build environment
SCM/JIRA link daemon commented on JENKINS-16684 Add GIT_URL to build environment Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/68d9eb934d638efd6a3146140cd9868b5e1c137f Log: Merge pull request #136 from deepsmgt/master Support for GIT_URL in environment JENKINS-16684 Compare: https://github.com/jenkinsci/git-plugin/compare/4a4b5db943e0...68d9eb934d63 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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/groups/opt_out.
[JIRA] (JENKINS-16849) StackOverflowError involving findMailAddressFor
Eloy Lafuente commented on JENKINS-16849 StackOverflowError involving findMailAddressFor Note: We were having this same problem (running 1.1.29 and "Jenkins GIT client plugin" 1.0.1). Then, some minutes ago, I updated to "Jenkins GIT client plugin" 1.0.2 and things became really worse: FATAL: tried to access method org.jenkinsci.plugins.gitclient.CliGitAPIImpl.init(Ljava/lang/String;Ljava/io/File;Lhudson/model/TaskListener;Lhudson/EnvVars;)V from class hudson.plugins.git.GitSCM$2java.lang.IllegalAccessError: tried to access method org.jenkinsci.plugins.gitclient.CliGitAPIImpl.init(Ljava/lang/String;Ljava/io/File;Lhudson/model/TaskListener;Lhudson/EnvVars;)V from class hudson.plugins.git.GitSCM$2 Sorry for the format, I've recovered this from a google search, because... Then I tried downgrading to 1.1.26 and now all my "git-based" jobs have disappeared. Literally. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16849) StackOverflowError involving findMailAddressFor
Eloy Lafuente commented on JENKINS-16849 StackOverflowError involving findMailAddressFor Aha, I managed to get the "git-based" jobs back by upgrading again to 1.1.29, and this is the complete output I'm getting: Building in workspace /Users/Shared/Jenkins/Home/git_repositories/master Checkout:master / /Users/Shared/Jenkins/Home/git_repositories/master - hudson.remoting.LocalChannel@7a88174c Using strategy: Default Last Built Revision: Revision aa247695e78c6cd574fdd720ab0aebffc169e2d9 (origin/master) FATAL: tried to access method org.jenkinsci.plugins.gitclient.CliGitAPIImpl.init(Ljava/lang/String;Ljava/io/File;Lhudson/model/TaskListener;Lhudson/EnvVars;)V from class hudson.plugins.git.GitSCM$2 java.lang.IllegalAccessError: tried to access method org.jenkinsci.plugins.gitclient.CliGitAPIImpl.init(Ljava/lang/String;Ljava/io/File;Lhudson/model/TaskListener;Lhudson/EnvVars;)V from class hudson.plugins.git.GitSCM$2 at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:940) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:932) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:932) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1101) at hudson.model.AbstractProject.checkout(AbstractProject.java:1342) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1568) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Ciao This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16861) Add support for the Claim Plugin
Markus Hjerto
commented on JENKINS-16861
Add support for the Claim Plugin
You are right. I should be able to create a script for that, which changes the recipient list based on the claim status.
I've never done any groovy scripts before, but at least I've been able to get the claim status. But after hours of searching, I've not been able to get the users e-mail address from the Jenkins user database. For now, I'll use the returned username as email address (usern...@domain.com), unless you could point me in the right directions? I'm looking for something like hudson.users.getEmailAddress(claim.getClaimedBy()).
For future searchers, this is what I've got so far. It is not production ready - It must be modified to set the email address before it can be used. I'll see if I can attach the finished script when (or if) I'm able to finish it.
def claim = it.getAction("hudson.plugins.claim.ClaimBuildAction")
if (claim != null) {
if (claim.isClaimed() == true) {
%Claimed by: ${claim.getClaimedBy()} (${claim.getClaimedByName()})\n%
if (claim.hasReason() == true ) {
%Reason: ${claim.getReason()}\n%
}
if (claim.hasClaimDate() == true ){
%Claimed at: ${claim.getClaimDate()}\n%
}
} else {
%Not claimed\n%
}
} else {
%Claim not supported for this job\n%
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
Markus Hjerto commented on JENKINS-12421 Add pre-send step to email-ext that can modify the mail message object terryl westerhold, I'm trying to achieve the same goal (JENKINS-16861) but I'm struggling with the script. Do you have something you could share? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16849) StackOverflowError involving findMailAddressFor
Eloy Lafuente edited a comment on JENKINS-16849 StackOverflowError involving findMailAddressFor Aha, I managed to get the "git-based" jobs back by upgrading again to 1.1.29, and this is the complete output I'm getting (1.1.29 with 1.0.2): Building in workspace /Users/Shared/Jenkins/Home/git_repositories/master Checkout:master / /Users/Shared/Jenkins/Home/git_repositories/master - hudson.remoting.LocalChannel@7a88174c Using strategy: Default Last Built Revision: Revision aa247695e78c6cd574fdd720ab0aebffc169e2d9 (origin/master) FATAL: tried to access method org.jenkinsci.plugins.gitclient.CliGitAPIImpl.init(Ljava/lang/String;Ljava/io/File;Lhudson/model/TaskListener;Lhudson/EnvVars;)V from class hudson.plugins.git.GitSCM$2 java.lang.IllegalAccessError: tried to access method org.jenkinsci.plugins.gitclient.CliGitAPIImpl.init(Ljava/lang/String;Ljava/io/File;Lhudson/model/TaskListener;Lhudson/EnvVars;)V from class hudson.plugins.git.GitSCM$2 at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:940) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:932) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.determineRevisionToBuild(GitSCM.java:932) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1101) at hudson.model.AbstractProject.checkout(AbstractProject.java:1342) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1568) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Ciao This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10260) broken externals are not detected
evernat resolved JENKINS-10260 as Duplicate broken externals are not detected this issue duplicates JENKINS-6415 Change By: evernat (20/Feb/13 9:30 AM) 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/groups/opt_out.
[JIRA] (JENKINS-16408) Initial state of the new dashboard view not user friendly
Marco Ambu assigned JENKINS-16408 to Marco Ambu Initial state of the new dashboard view not user friendly Change By: Marco Ambu (20/Feb/13 9:35 AM) Assignee: PeterHayes MarcoAmbu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16408) Initial state of the new dashboard view not user friendly
Marco Ambu commented on JENKINS-16408 Initial state of the new dashboard view not user friendly Agree 100%. We may start with the standard jenkins job view and maybe two others (the most common? if we know which they are). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16300) Dashborad plugin shows 2008R2 / 2012 connected slaves as offline
Marco Ambu commented on JENKINS-16300 Dashborad plugin shows 2008R2 / 2012 connected slaves as offline Can you please provide more info on how this is related to the dashboard view plugin? Can you please provide a screenshot? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15085) Test Trend portlet zeros results for running build
Marco Ambu assigned JENKINS-15085 to Marco Ambu Test Trend portlet zeros results for running build Change By: Marco Ambu (20/Feb/13 9:40 AM) Assignee: PeterHayes MarcoAmbu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16886) 500 Error when type the git url during creating new job
Daniel Lindner commented on JENKINS-16886 500 Error when type the git url during creating new job I experience a similar exception when trying to run a build on an existing job. This is for version 1.1.29 - everything worked with the previously installed version 1.1.26 FATAL: tried to access method org.jenkinsci.plugins.gitclient.CliGitAPIImpl.init(Ljava/lang/String;Ljava/io/File;Lhudson/model/TaskListener;Lhudson/EnvVars;)V from class hudson.plugins.git.GitSCM$2 java.lang.IllegalAccessError: tried to access method org.jenkinsci.plugins.gitclient.CliGitAPIImpl.init(Ljava/lang/String;Ljava/io/File;Lhudson/model/TaskListener;Lhudson/EnvVars;)V from class hudson.plugins.git.GitSCM$2 at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:940) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:932) at hudson.FilePath.act(FilePath.java:865) ... My guess would be that the new git-client plugin is responsible for this behaviour. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14988) Use different status icons in dashboard for disbaled and canceled jobs
Marco Ambu commented on JENKINS-14988 Use different status icons in dashboard for disbaled and canceled jobs Is there a common way to do so in jenkins? What does jenkins show in the standard job view? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14045) Add ability to change dashboard diagrams time-scale grain for Trend charts
Marco Ambu commented on JENKINS-14045 Add ability to change dashboard diagrams time-scale grain for Trend charts When you select "week" as the time unit for showing the results, how would you suggest us computing the result for that week? Should that be the last test result for that week? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Andreas Vogler commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Release 1.502 contains https://github.com/jenkinsci/winstone/pull/6 as well as the fix for JENKINS-16278. Anyone still having problems with this on 1.502? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13933) Arrows in dashboard column headings are inconsistent
Marco Ambu updated JENKINS-13933 Arrows in dashboard column headings are inconsistent I think you are talking about the standard job view. Changing component to core as the dashboard view plugin does not control this feature (it is inherited by jenkins' job view). Change By: Marco Ambu (20/Feb/13 9:52 AM) Component/s: core Component/s: dashboard-view This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12863) dashboard - jobs list portlet - add summary statistics
Marco Ambu updated JENKINS-12863 dashboard - jobs list portlet - add summary statistics If this information is "per project" I suggest adding it to the project stats plugin. If this information is an average of all projects shown in the view, then you have to suggest which portlet you would like to see it in. Change By: Marco Ambu (20/Feb/13 9:55 AM) Assignee: PeterHayes MarcoAmbu Component/s: project-stats This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
Linards L commented on JENKINS-15156 Builds disappear from build history after completion It wouold be better to confirm linked issues first. Then this one. It would be good to keep histroical / hearichal view on this issue as I have feeling this is not last time devs will run in such circular issues ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11989) Build history time line chart doesn't render in Internet Explorer 8.0.6001
Marco Ambu updated JENKINS-11989 Build history time line chart doesnt render in Internet Explorer 8.0.6001 I think this is a core problem, not dashboard view plugin specific. Removed dashboard-view component. Change By: Marco Ambu (20/Feb/13 10:01 AM) Component/s: dashboard-view This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16888) Usage of ObjectID.fromString in computeMergeChangeLog leads to java.lang.IllegalArgumentException: Invalid id
Torsten Beuck
created JENKINS-16888
Usage of ObjectID.fromString in computeMergeChangeLog leads to java.lang.IllegalArgumentException: Invalid id
Issue Type:
Bug
Affects Versions:
current
Assignee:
Nicolas De Loof
Components:
git
Created:
20/Feb/13 10:02 AM
Description:
When configuring a Jenkins job with "merge before build" and setting "Branch to merge to" to develop, the job fails with an "IllegalArgumentException: Invalid id".
In the class hudson.plugins.git.GitSCM the method computeMergeChangeLog is called with the remote branch name as third paramater (called revFrom in the method declaration). In the method computeMergeChangeLog the following code is executed:
if (!git.isCommitInRepo(ObjectId.fromString(revFrom))) {
...
}
If revFrom is the remote branch name (e.g. "origin/develop"), the fromString method of the JGit class ObjectId throws the IllegalArgumentException because "origin/develop" does not have a length of 40.
ObjectId.fromString obviously expects a Git commit ID - which has a length of 40 characters - and not the name of a branch ref.
Project:
Jenkins
Priority:
Major
Reporter:
Torsten Beuck
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10651) Add cppcheck to Dashboard View
Marco Ambu updated JENKINS-10651 Add cppcheck to Dashboard View Hi, we usually go for the other way round. Every plugin can provide a portlet. The dashboard view portlet is a view and does not know anything about the underlying plugin. So it must be implemented in cppcheck plugin (as we do for warnings, coverity, ...). Change By: Marco Ambu (20/Feb/13 10:04 AM) Component/s: cppcheck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16886) 500 Error when type the git url during creating new job
Daniel Lindner commented on JENKINS-16886 500 Error when type the git url during creating new job Reverting back to git plugin version 1.1.26 did not help until I deleted the git-client plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16286) NPE: WARNING: org.jenkinsci.plugins.ghprb.GhprbTrigger.run() failed for gigabase
Honza Brázdil resolved JENKINS-16286 as Fixed NPE: WARNING: org.jenkinsci.plugins.ghprb.GhprbTrigger.run() failed for gigabase Change By: Honza Brázdil (20/Feb/13 10:34 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11054) Support policies for workspace cleanup
James Howe commented on JENKINS-11054 Support policies for workspace cleanup We'd really like the ability to "delete files not under source control", "delete all writeable files" and stuff like that. Deleting and then resycning everything simply takes far too long. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16889) No cleanup SSH connections when slave action occurs
Florent Poinsaut created JENKINS-16889 No cleanup SSH connections when slave action occurs Issue Type: Bug Affects Versions: current Assignee: Philipp Bartsch Components: libvirt-slave, libvirtslave Created: 20/Feb/13 10:58 AM Description: I noticed some days ago that connections to libvirt from java binding with SSH URL leaves an SSH shell opened even after a connection is closed. The version of libvirt-java could be the problem. I think they fixed this behavour after the 0.4.2 version (src: http://libvirt.org/git/?p=libvirt-java.git;a=shortlog). Thank you in advance. Regards, Environment: Debian 6.0.6 x86_64, Jenkins ver. 1.502, Jenkins Libvirt Slaves plugin 1.7 Project: Jenkins Priority: Major Reporter: Florent Poinsaut This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16518) Warning summary gone after plugin update
kutzi commented on JENKINS-16518 Warning summary gone after plugin update Thanks for fixing this. When will it be released? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16886) 500 Error when type the git url during creating new job
Lei Zhang commented on JENKINS-16886 500 Error when type the git url during creating new job One Question: How can i revert to the old version? I din't have the Previously installed version This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Alexander Artemov reopened JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session I still have the same issue in Jenkins 1.502 - every half an hour - hour I am logged off and have to login again. Change By: Alexander Artemov (20/Feb/13 11:30 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16890) Adding memory sections together
Jes Struck created JENKINS-16890 Adding memory sections together Issue Type: Bug Assignee: Praqma Support Components: memory-map Created: 20/Feb/13 11:46 AM Description: It should be possible, in the config page to write eg. "RAML0+RAML1". and that should give ONE result in the graph instead of two Due Date: 20/Feb/13 12:00 AM Environment: ALL Project: Jenkins Priority: Major Reporter: Jes Struck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16877) In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf
Geoff Cummings commented on JENKINS-16877 In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf I am also getting the same problem after upgrading from 1.501 to 1.502 http://jenkins_url/job/job_name/lastSuccessfulBuild/api/xml?xpath=/*/numberreturns the following number100/number http://jenkins_url/job/job_name/lastSuccessfulBuild/api/xml?xpath=/*/number/text() returns ERROR 403: Forbidden This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16890) Adding memory sections together (our case 8625)
Jes Struck updated JENKINS-16890 Adding memory sections together (our case 8625) Change By: Jes Struck (20/Feb/13 11:49 AM) Summary: Addingmemorysectionstogether (ourcase8625) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours No change in behaviour observed with 1.502. Still no persistence of login over browser sessions. It appears the cookie format was a red herring. Has anyone looked into the Active Directory plugin? That seems to be the constant factor for everyone that has this bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16890) Adding memory sections together (our case 8625)
Bue Petersen updated JENKINS-16890 Adding memory sections together (our case 8625) Change By: Bue Petersen (20/Feb/13 12:11 PM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Danny Staple commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours I've not had a moment to try out 1.502 - so cannot confirm this. However - we do not use the active directory plugin in our installation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Hendrik Millner commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session Personally, I do not experience this problem in 1.502. What does your RememberMe cookie look like (contents of ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE)? Please have a look at the expiration date, as 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/groups/opt_out.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
René Charbonneau commented on JENKINS-16746 Unable to send email since Jenkins 1.500 Sorry but I disagree. According to find / -name "jenkins.xml" there is no jenkins.xml on the whole filesystem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16775) Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpl's signer information does not match signer information of other classes in
Thomas Poisl
updated JENKINS-16775
Deployment fails with java.lang.SecurityException: class org.kohsuke.args4j.XmlParser$ArgumentImpls signer information does not match signer information of other classes in the same package
Change By:
Thomas Poisl
(20/Feb/13 12:44 PM)
Environment:
DeploymentwithJenkins1.499works,whileJenkins1.500and
1.501fail
laterfails
todeploy
Description:
WearerunningJenkinsinJBoss6.0.0here,butdeploymentofJenkins1.500
or1.501
andlater
failswiththefollowingerror:{noformat}DEPLOYMENTSINERROR:Deploymentvfs:///srv/jboss/server/default/deploy/jenkins.warisinerrorduetothefollowingreason(s):java.lang.SecurityException:classorg.kohsuke.args4j.XmlParser$ArgumentImplssignerinformationdoesnotmatchsignerinformationofotherclassesinthesamepackageatorg.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1228)[:2.2.0.GA]atorg.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:905)[:2.2.0.GA]atorg.jboss.system.server.profileservice.deployers.MainDeployerPlugin.checkComplete(MainDeployerPlugin.java:87)[:6.0.0.Final]atorg.jboss.profileservice.deployment.ProfileDeployerPluginRegistry.checkAllComplete(ProfileDeployerPluginRegistry.java:107)[:0.2.2]atorg.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:135)[:6.0.0.Final]atorg.jboss.system.server.profileservice.bootstrap.BasicProfileServiceBootstrap.start(BasicProfileServiceBootstrap.java:56)[:6.0.0.Final]atorg.jboss.bootstrap.impl.base.server.AbstractServer.startBootstraps(AbstractServer.java:827)[jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]atorg.jboss.bootstrap.impl.base.server.AbstractServer$StartServerTask.run(AbstractServer.java:417)[jboss-bootstrap-impl-base.jar:2.1.0-alpha-5]atjava.lang.Thread.run(Thread.java:662)[:1.6.0_31]{noformat}SinceIcouldnotfindanyinformationaboutthisproblem,itmightberelatedtooneoftheplug-insweareusing:{noformat}Name↓ Version Enabled Pinnedmailer 1.4 true falseexternal-monitor-job 1.1 true falseldap 1.2 true truepam-auth 1.0 true falseant 1.1 true falsejavadoc 1.0 true falsecvs 2.7 true truejmeter 0.3.0 true falsetoken-macro 1.5.1 true falsemaven-plugin 1.499 true falsem2-extra-steps 1.1.7 true falsegroovy 1.12 true falsepostbuild-task 1.8 true falsegoogleanalytics 1.3 true falsem2release 0.9.1 true falsetwitter 0.6 true falsedownstream-ext 1.7 true falsebatch-task 1.16 true falsescis-ad 1.2 true falsechucknorris 0.5 true falsedashboard-view 2.4 true falsecobertura 1.8 true falsexunit 1.52 true falseperformance 1.8 true falseanalysis-core 1.48 true falseemail-ext 2.25 true falsePrioritySorter 1.3 true falsesubversion 1.45 true trueconfigurationslicing 1.36 true falsemaven-metadata-plugin 1.0.0 true falseperfpublisher 7.97 true falsedeploy 1.9 true falsedynamic-axis 1.0.1 true falsejob-poll-action-plugin 1.0 true falsem2-repo-reaper 1.0 true falsematrixtieparent 1.1 true falseruby-runtime 0.10 true falsepathignore 0.6 true falsetasks 4.35 true falsecheckstyle 3.32 true falsefindbugs 4.45 true falseviolations 0.7.11 true falsepmd 3.33 true falsewarnings 4.21 true falseci-game 1.19 true falseinsight-ci 2.3.3 true falsemaven-repo-cleaner 1.2 true falseparameterized-trigger 2.16 true falsegit 1.1.26 true falsegit-server 1.1 true falsescriptler 2.5.1 true falsepublish-over-ssh 1.9 true falsedry 2.33 true falseanalysis-collector 1.34 true falseemma 1.29 true falseandroid-lint 2.0.2 true falsedynamicparameter 0.2.0 true falsejira 1.35 true falseenvinject 1.82 true falsematrix-reloaded 1.1.0 true falseclone-workspace-scm 0.5 true falsexvnc 1.11 true falsesonatype-ci 1.3 true falsegroovyaxis 0.3 true falsecopyartifact 1.25 true falsetranslation 1.10 true trueport-allocator 1.5 true falsemeasurement-plots 0.1 true falseandroid-emulator 2.8 true falsetemplate-project 1.3 true falseplot 1.5 true falselocale 1.2 true falseartifactory 2.1.4 true falselastfailureversioncolumn 1.1 true falsetestng-plugin 1.1 true falsetestlink 3.1.8 true falsessh-slaves 0.22 true truelastsuccessversioncolumn 1.1 true falserebuild 1.17 true false{noformat}
[JIRA] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
kutzi commented on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content I'm not sure that I understand the issue: Who or what is merging the branch into trunk? And what if you checkout the trunk with command line svn - is the content duplicated, too? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Alexander Artemov commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session It looks like: YWFydGVtb3Y6MTM2MTQyNzY0NDA0OTpjZjdlYjZmNTI2NjA2ZDg1Mzc5NWEwMDkyMGUzODhmMw== It's expiration date it 6.5 hours earlier than the present time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
Chris Withers commented on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content The problems happens if, in a commit which already committed to the subversion server, a branch has been merged into trunk that where some files are added. Who or what is merging the branch into trunk? A developer, on their own machine, which is then committed to svn. And what if you checkout the trunk with command line svn - is the content duplicated, too? no, if you use the command line tools, the checkout is as expected, with no duplicated content. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
kutzi commented on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content Okay. So what would really help to debug the issue would be if you could create a minimal subversion repository which has this characteristics. Ideally also a snapshot of the repository BEFORE and AFTER the branch has been merged. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16886) 500 Error when type the git url during creating new job
Daniel Lindner commented on JENKINS-16886 500 Error when type the git url during creating new job I had to upload the specific hpi-File to Jenkins (in the Plugin Manager, Advanced Tab). Download your version here: http://updates.jenkins-ci.org/download/plugins/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/groups/opt_out.
[JIRA] (JENKINS-16886) 500 Error when type the git url during creating new job
Daniel Lindner commented on JENKINS-16886 500 Error when type the git url during creating new job Another information: I just tried to combination of git plugin version 1.2.0 and git-client plugin version 1.0.2 - Everything seems to work fine at first glance. Perhaps this was a version incompatibility between 1.1.29 and 1.0.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/groups/opt_out.
[JIRA] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Hendrik Millner commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session Whoops.. Well, the token is looking fine, but the expiration date is not. The system clock of your Jenkins is not coincidentally running behind by two weeks and 6.5 hours, relative to your system time? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
Balthasar Nebel edited a comment on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled I am having the same problem with Jenkins 1.502 on Linux (Oracle JDK 1.6.0_39). For some unknown reason not all my jobs are having this problem. The problem disappeared after going back to Jenkins 1.501. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16746) Unable to send email since Jenkins 1.500
Ravi Teja Lokineni commented on JENKINS-16746 Unable to send email since Jenkins 1.500 You can add the same options in bin/catalina.sh under the first line as: #!... JAVA_OPTS=$JAVA_OPTS" -Dmail.debug=true" ...Some copyright info... (OR) #!... JAVA_OPTS=$JAVA_OPTS:"-Dmail.debug=true" ...Some copyright info... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16886) 500 Error when type the git url during creating new job
Lei Zhang commented on JENKINS-16886 500 Error when type the git url during creating new job I tested the 1.1.28 and 1.1.26. It raised another exception. When trying 1.2.0, it seems OK. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
Chris Nogradi
commented on JENKINS-12421
Add pre-send step to email-ext that can modify the mail message object
Looks like you mostly had it in the comments for Jenkins-16861. Here is what we use:
build.actions.each { action -
if(action.class.name == "hudson.plugins.claim.ClaimBuildAction" action.isClaimed()) {
logger.println(action.getClaimedBy());
hudson.model.User user = hudson.model.User.get(action.getClaimedBy());
address = user.getProperty(hudson.tasks.Mailer.UserProperty).getAddress() ;
logger.println("Sending to " + address );
msg.setRecipients(javax.mail.Message.RecipientType.TO, address );
}
}
Note that we use the LDAP plugin to talk to ActiveDirectory.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16891) Add support for space in 'Program memory selection' (our case 8625)
Jes Struck resolved JENKINS-16891 as Fixed Add support for space in Program memory selection (our case 8625) this will be resolved in version 1.0.0 which has just been released Change By: Jes Struck (20/Feb/13 1:49 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16890) Adding memory sections together (our case 8625)
Jes Struck resolved JENKINS-16890 as Fixed Adding memory sections together (our case 8625) this will be resolved in version 1.0.0 which has just been released Change By: Jes Struck (20/Feb/13 1:49 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16825) Move graph labels for memory section of same size sideways - our case 8622
Jes Struck resolved JENKINS-16825 as Fixed Move graph labels for memory section of same size sideways - our case 8622 this will be resolved in version 1.0.0 which has just been released Change By: Jes Struck (20/Feb/13 1:49 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Alexander Artemov commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session No, jenkins runs at the same time as my machine. Jenkins runs on the server which time is the same as on my machine. It's Feb 20, 2013 5:49:00 PM now in Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16822) Support for different scale values - our case 8273
Jes Struck resolved JENKINS-16822 as Fixed Support for different scale values - our case 8273 this will be resolved in version 1.0.0 which has just been released Change By: Jes Struck (20/Feb/13 1:50 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
Chris Nogradi commented on JENKINS-12421 Add pre-send step to email-ext that can modify the mail message object Oh and I suppose I should mention that we occasionally receive emails from Jenkins with the an email title specifying a project which is different from the body of the email so I think there is a bug in this code that is either caused by not locking a shared resource or a cache value is not flushed properly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
Alex Earl commented on JENKINS-12421 Add pre-send step to email-ext that can modify the mail message object Are you on the latest version of email-ext? I made some mods that should resolve this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16810) CLI: java.io.EOFException
Viktor Tarasov updated JENKINS-16810 CLI: java.io.EOFException Change By: Viktor Tarasov (20/Feb/13 2:02 PM) Description: Startingfromjenkins-1.486-55-gb44787danduntiljenkins-1.501 (thelatestthatIcouldbuild) ,everysecondCLIcommandfailswithjava.io.EOFException.Hereisthesequenceoffourattemptstorunthesametestbuild:(itcanbeanyotherCLIcommand.)$java-jar./jenkins-cli.jar-shttps://jenkins.rd.opentrust.com/buildjob-test$java-jar./jenkins-cli.jar-shttps://jenkins.rd.opentrust.com/buildjob-testExceptioninthreadmainjava.io.EOFException atjava.io.DataInputStream.readBoolean(DataInputStream.java:244) athudson.cli.Connection.readBoolean(Connection.java:95) athudson.cli.CLI.authenticate(CLI.java:604) athudson.cli.CLI._main(CLI.java:444) athudson.cli.CLI.main(CLI.java:374)$java-jar./jenkins-cli.jar-shttps://jenkins.rd.opentrust.com/buildjob-test$java-jar./jenkins-cli.jar-shttps://jenkins.rd.opentrust.com/buildjob-testExceptioninthreadmainjava.io.EOFException atjava.io.DataInputStream.readBoolean(DataInputStream.java:244) athudson.cli.Connection.readBoolean(Connection.java:95) athudson.cli.CLI.authenticate(CLI.java:604) athudson.cli.CLI._main(CLI.java:444) athudson.cli.CLI.main(CLI.java:374)Itseemsthatb44787ddeaf203d26baf456cb12603b6f2ad232aisthefirstbadcommit.Kindregards,Viktor. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-12421) Add pre-send step to email-ext that can modify the mail message object
Alex Earl commented on JENKINS-12421 Add pre-send step to email-ext that can modify the mail message object There is already a jira filed by Xavier Nodet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16861) Add support for the Claim Plugin
Alex Earl
commented on JENKINS-16861
Add support for the Claim Plugin
You need to get a property from the user object. This is how it is done internally in the email-ext plugin.
public static String getUserConfiguredEmail(User user) {
String addr = null;
if(user != null) {
Mailer.UserProperty mailProperty = user.getProperty(Mailer.UserProperty.class);
if (mailProperty != null) {
addr = mailProperty.getAddress();
}
}
return addr;
}
Also, just as an FYI, when using groovy, for getters and setters you don't need the get/set; for example: claim.claimedByName is the same as claim.getClaimedByName()
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16892) Git plugin update breaks builds, if SCM Changes are used in other plugins
Denis Syrokvash
created JENKINS-16892
Git plugin update breaks builds, if SCM Changes are used in other plugins
Issue Type:
Bug
Affects Versions:
current
Assignee:
Alex Earl
Attachments:
email-ext-callstack.txt, testflight-callstack.txt
Components:
email-ext, git, testflight
Created:
20/Feb/13 2:21 PM
Description:
After updating Jenkins to 1.502 and Jenkins GIT plugin to 1.1.29, the builds that use email-ext with ${CHANGES...} macro in the body and Testflight (with enabled 'Append changelog to build notes' checkmark} do fail because of stack overflow in GIT related code.
Note, that overflow happens only, if there're changes in SCM from the last build.
Stacktrace for Testflight plugin fail - see testflight-callstack.txt attached
Stacktrace for email-ext plugin fail - see email-ext-callstack.txt attached
Environment:
jenkins v1.502, jenkins GIT plugin 1.1.29
Project:
Jenkins
Priority:
Major
Reporter:
Denis Syrokvash
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16555) Create iframe portlet
SCM/JIRA link daemon commented on JENKINS-16555 Create iframe portlet Code changed in jenkins User: Karol Kanski Path: src/main/java/hudson/plugins/view/dashboard/core/IframePortlet.java src/main/resources/hudson/plugins/view/dashboard/Messages.properties http://jenkins-ci.org/commit/dashboard-view-plugin/bf762466cab54fe770e4745ef057212a6c3e5f3a Log: JENKINS-16555 Create iframe portlet - i18n This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16555) Create iframe portlet
SCM/JIRA link daemon commented on JENKINS-16555 Create iframe portlet Code changed in jenkins User: Karol Kanski Path: src/main/resources/hudson/plugins/view/dashboard/core/IframePortlet/config.jelly src/main/webapp/help/help-configDivStyle.html src/main/webapp/help/help-configUrl.html http://jenkins-ci.org/commit/dashboard-view-plugin/f268d13ce81cecca63e71284b51e5933364f3803 Log: JENKINS-16555 Create iframe portlet - help files updates This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16555) Create iframe portlet
SCM/JIRA link daemon commented on JENKINS-16555 Create iframe portlet Code changed in jenkins User: Karol Kanski Path: src/main/java/hudson/plugins/view/dashboard/core/IframePortlet.java src/main/resources/hudson/plugins/view/dashboard/core/IframePortlet/config.jelly src/main/resources/hudson/plugins/view/dashboard/core/IframePortlet/portlet.jelly src/main/webapp/help/help-configDivStyle.html src/main/webapp/help/help-configUrl.html http://jenkins-ci.org/commit/dashboard-view-plugin/5962d3cb9797b51e26e867f8b72f82fe4e88b4ab Log: JENKINS-16555 Create iframe portlet This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16886) 500 Error when type the git url during creating new job
Robert Dahlström commented on JENKINS-16886 500 Error when type the git url during creating new job Downgrading from 1.1.29 to 1.1.26 solved it for me. I have jenkins git client plugin 1.0.2 installed. Have not tried with the latest 1.2.0 release yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15596) Jenkins will not start as a Windows Service after KB2661254
Adilson Junior commented on JENKINS-15596 Jenkins will not start as a Windows Service after KB2661254 Is there any workaround to deal with this bug? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
Antonios Chalkiopoulos commented on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled Same on here, updating to 1.502 from 1.501 makes this warning also visible. I have repository hooks that trigger the following url: curl https://ci.mysite.com/job/myjob/build?token=MY_TOKEN and this action is not performed due to the warning getting displayed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-6718) Fatal error when you use a slave and try to launch command which need to be in the path after build (after channel stopped).
Michael Pailloncy commented on JENKINS-6718 Fatal error when you use a slave and try to launch command which need to be in the path after build (after channel stopped). Hi, I've exactly the same problem. Jenkins : 1.500 Sonar Plugin : 2.0.1 Do you have found a workaround for this issue ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-6796) mvn No such file or directory
Michael Pailloncy commented on JENKINS-6796 mvn No such file or directory Hi, I've exactly the same problem. Jenkins : 1.500 Sonar Plugin : 2.0.1 Do you have found a workaround for this issue ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Geoff Rowell commented on JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves My environment is Windows 2008 x64 (not R2) and Java SE runtime 64bit 1.6.0_24-b07 (bundled). I'm experiencing the exact same problem. Definitely a critical 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/groups/opt_out.
[JIRA] (JENKINS-16888) Usage of ObjectID.fromString in computeMergeChangeLog leads to java.lang.IllegalArgumentException: Invalid id
Torsten Beuck
updated JENKINS-16888
Usage of ObjectID.fromString in computeMergeChangeLog leads to java.lang.IllegalArgumentException: Invalid id
Change By:
Torsten Beuck
(20/Feb/13 2:50 PM)
Environment:
Jenkinsver.1.480.3,GitPlugin1.1.29
Description:
WhenconfiguringaJenkinsjobwithmergebeforebuildandsettingBranchtomergetotodevelop,thejobfailswithanIllegalArgumentException:Invalidid.Intheclasshudson.plugins.git.GitSCMthemethodcomputeMergeChangeLogiscalledwiththeremotebranchnameasthirdparamater(calledrevFrominthemethoddeclaration).InthemethodcomputeMergeChangeLogthefollowingcodeisexecuted:if(!git.isCommitInRepo(ObjectId.fromString(revFrom))){...}IfrevFromistheremotebranchname(e.g.origin/develop),thefromStringmethodoftheJGitclassObjectIdthrowstheIllegalArgumentExceptionbecauseorigin/developdoesnothavealengthof40.ObjectId.fromStringobviouslyexpectsaGitcommitID-whichhasalengthof40characters-andnotthenameofabranchref.
Thebugwasintroducedwith1.1.27.Installing1.1.26fixedtheproblem.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
kutzi commented on JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves This is a bug in the Java VM and there's probably not much Jenkins can do about it. To have the slightest chance to fix this on Jenkins side, we would need at least the content of the mentioned report file (# An error report file with more information is saved as: C:\Windows\system32\hs_err_pid4408.log) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15596) Jenkins will not start as a Windows Service after KB2661254
Dirk Kuypers commented on JENKINS-15596 Jenkins will not start as a Windows Service after KB2661254 Try to add the following file as jenkins-slave.exe.config to your slave directory: ?xml version="1.0" encoding="utf-8"? configuration runtime generatePublisherEvidence enabled="false"/ /runtime /configuration It disables checking the validity of the Exes signature. At least it helped me as our corporate firewall blocks this sort of checks... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Geoff Rowell commented on JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves Unfortunately, the JVM is lying that file is never created. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16555) Create iframe portlet
Karol Kański resolved JENKINS-16555 as Fixed Create iframe portlet Change By: Karol Kański (20/Feb/13 3:00 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/groups/opt_out.
[JIRA] (JENKINS-16893) Cross Site Scripting Version 1.502
Andrei Colta created JENKINS-16893 Cross Site Scripting Version 1.502 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 20/Feb/13 3:07 PM Description: we found few vulnaribilities. If you append this http://yourdomainname.com:8080//search/suggestOpenSearch?q=%27"%28%29%26%251ScRiPt%20prompt%28'VULN'%29%2fScRiPt Is Vulnerable To Cross Site Scripting This vulnerability affects /search/suggestOpenSearch on Parametter ?q= HTTP Parameter Pollution on builds /loginError HPP attacks consist of injecting encoded query string delimiters into other existing parameters. If the web application does not properly sanitize the user input, a malicious user can compromise the logic of the application to perform either clientside or server-side attacks. Attack details This vulnerability affects /j_acegi_security_check. URL encoded POST input from was set to n990198=v931935 Parameter precedence: last occurrence Affected link: login?from=n990198=v931935 Affected parameter: from= The impact depends on the affected web application. An attacker could Override existing hardcoded HTTP parameters Modify the application behaviors Access and, potentially exploit, uncontrollable variables Bypass input validation checkpoints and WAFs rules Due Date: 20/Feb/13 12:00 AM Environment: Linux Debian Project: Jenkins Labels: jenkins Priority: Critical Reporter: Andrei Colta This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Geoff Rowell updated JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves Found it. The actual path name is: C:\Windows\SysWOW64\hs_err_pid4408.log Change By: Geoff Rowell (20/Feb/13 3:07 PM) Attachment: hs_err_pid4408.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16894) Doxygen publish very slow
Gábor Karsai created JENKINS-16894 Doxygen publish very slow Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: doxygen, publish-over-ssh Created: 20/Feb/13 3:12 PM Description: The publishing step takes forever. We have a master node and a few build nodes. Only the nodes build anything. Nodes are started by master through ssh. Our doxygen generated documentation is 61 MB in size, and 3164 files. And this amount of documentation takes 90 minutes to publish. If I check what jenkins is doing in the 90 minutes nothing stands out, no cpu usage, no io wait nothing. Just extremely slow publish. I can see arriving the files roughly 1 file / second. A remote scp copy from the node to the master takes 6 seconds, on the same directory. Environment: Ubuntu 12.04 Jenkins version 1.501 Latest doxygen plugin. Project: Jenkins Labels: publish doxygen slave Priority: Major Reporter: Gábor Karsai This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Geoff Rowell commented on JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves Looks like the timestamper plugin is triggering the problem. I think Takeji Naigeon's comment is better applied to this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Hendrik Millner commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session You should create a new log recorder to have a closer look at the debugging messages concerning the RememberMe cookie. You can do this at Manage Jenkins Logs. Add a new log recorder with any name you like and then add a logger "org.acegisecurity.ui.rememberme" in its configuration, setting the severity in the drop-down list to "FINE". This log recorder should then present you lots of messages around the RememberMe token. Upon a new login with "remember me" set, you should get a log line like this one: "Feb 20, 2013 4:24:31 PM hudson.security.TokenBasedRememberMeServices2 loginSuccess FINE: Added remember-me cookie for user 'millner', expiry: 'Wed Mar 06 16:24:31 CET 2013'" What expiration date is shown there at your Jenkins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16886) 500 Error when type the git url during creating new job
Andrei Pozolotin commented on JENKINS-16886 500 Error when type the git url during creating new job Downgrading https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin from 1.1.29 to 1.1.26 resolved it for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
Larry Grill commented on JENKINS-15156 Builds disappear from build history after completion Nickolay: I upgraded one of our servers and have not seen the issue come back yet. So I feel comfortable upgrading our other servers with this build. Also tested copying jobs as noted in JENKINS-16735 and my history on the source job did not disappear. No guarantees, but so far it looks good. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
Larry Grill edited a comment on JENKINS-15156 Builds disappear from build history after completion Nickolay: I upgraded one of our servers (with version 1.502) and have not seen the issue come back yet. So I feel comfortable upgrading our other servers with this build. Also tested copying jobs as noted in JENKINS-16735 and my history on the source job did not disappear. No guarantees, but so far it looks good. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15704) Incomplete list of builds when I go to JobName/api/json
Dhawal Bhanushali commented on JENKINS-15704 Incomplete list of builds when I go to JobName/api/json Is there a suggested work around atleast? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Stuart Whelan commented on JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves Thanks for the tip of the path Geoff, found my logs there also. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Stuart Whelan updated JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves Change By: Stuart Whelan (20/Feb/13 4:51 PM) Attachment: hs_err_pid4676.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16528) Jenkins master node crashes often when viewing console logs of builds on slaves
Geoff Rowell edited a comment on JENKINS-16528 Jenkins master node crashes often when viewing console logs of builds on slaves My environment is Windows 2008 x64 (not R2) and Java SE runtime 1.6.0_24-b07 (bundled). I'm experiencing the exact same problem. # A fatal error has been detected by the Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc005) at pc=0x01d58282, pid=4408, tid=5712 # # JRE version: 6.0_24-b07 # Java VM: Java HotSpot(TM) Client VM (19.1-b02 mixed mode windows-x86 ) # Problematic frame: # J org.kohsuke.stapler.jelly.groovy.GroovyFacet$1.dispatch(Lorg/kohsuke/stapler/RequestImpl;Lorg/kohsuke/stapler/ResponseImpl;Ljava/lang/Object;)Z # # An error report file with more information is saved as: # C:\Windows\system32\hs_err_pid4408.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp Definitely a critical issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15704) Incomplete list of builds when I go to JobName/api/json
pedro reis commented on JENKINS-15704 Incomplete list of builds when I go to JobName/api/json Yes, I'm now using "lastBuild" element instead of "builds" element. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16895) Invoke Phing targets not available as post-build action or promoted-builds action
Aaron Hawley created JENKINS-16895 Invoke Phing targets not available as post-build action or promoted-builds action Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: phing, promoted-builds Created: 20/Feb/13 5:33 PM Description: "Invoke Phing targets" is available from the build actions for a Jenkins job, but not as a "Promote builds when..." action for the promoted-builds plugin. Other actions, like "Execute shell", "Invoke Ant" and "Invoke top-level Maven targets" are available but I'd like to run Phing directly. The promoted-builds plugin wants PhingDescriptor to be an instance of hudson.tasks.BuildStepDescriptor hudson.model.Descriptorhudson.tasks.Builder and checks if BuildStepDescriptor.isApplicable() returns true. Environment: Windows Server 2008 R2 6.1 Jenkins 1.500 phing-plugin 0.11 promoted-builds 2.8 Project: Jenkins Priority: Major Reporter: Aaron Hawley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16896) per-project permissions for gerrit triggering of patches
liamjbennett updated JENKINS-16896 per-project permissions for gerrit triggering of patches Change By: liamjbennett (20/Feb/13 6:43 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16896) per-project permissions for gerrit triggering of patches
liamjbennett created JENKINS-16896 per-project permissions for gerrit triggering of patches Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 20/Feb/13 6:43 PM Description: At the moment Jenkins allows per-project permissions to be set for the "Build Now" functionality. With a gerrit-trigger based workflow the permission to allow forcibly triggering a project is set at a global level but not at a project level meaning that users with the permission can trigger projects that do not belong to them. This should be fixed. Project: Jenkins Priority: Minor Reporter: liamjbennett This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16892) Git plugin update breaks builds, if SCM Changes are used in other plugins
Clinton Wolfe commented on JENKINS-16892 Git plugin update breaks builds, if SCM Changes are used in other plugins It's definitely the SCM Changes macro - I see it breaking with IRC plugin, which can use SCM CHanges in IRC 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/groups/opt_out.
[JIRA] (JENKINS-12079) Support master / slave usage
evernat resolved JENKINS-12079 as Fixed Support master / slave usage said as fixed, so resolving as fixed Change By: evernat (20/Feb/13 7:34 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10207) regex doesn't support multiple OR patern
evernat resolved JENKINS-10207 as Incomplete regex doesnt support multiple OR patern No response from the reporter, so resolving as incomplete. Change By: evernat (20/Feb/13 7:45 PM) Status: Open 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/groups/opt_out.
[JIRA] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
vasyl vuy commented on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content I have the same issue, file content is duplicated. update strategy is 'emulate clean...' and I only see this behavior when new files are added after merge. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16897) thinBackup is expecting everything in the jobs folder to be a directory
Paul Carr commented on JENKINS-16897 thinBackup is expecting everything in the jobs folder to be a directory This is an urgent problem, if anyone has accidentally placed a txt file in their jobs folder, their backups from that point on will be broken, and they will not know it until they try to restore ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16897) thinBackup is expecting everything in the jobs folder to be a directory
Paul Carr created JENKINS-16897 thinBackup is expecting everything in the jobs folder to be a directory Issue Type: Bug Affects Versions: current Assignee: Thomas Fürer Components: thinBackup Created: 20/Feb/13 7:57 PM Description: If you have any non-dir files in the jobs folder, thinBackup only backs up a few folders then fails at HudsonBackup.java line 240 resulting in data loss. To Reproduce ... create a txt file in the jobs foldermodify a few jobs so their timestamp is latertake a backup. Due Date: 21/Mar/13 12:00 AM Environment: Jenkins 1.500 linux x64 Project: Jenkins Priority: Major Reporter: Paul Carr This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16659) TriggerBuilder builds based on parameter value should be listed as downstream builds
cjo9900 commented on JENKINS-16659 TriggerBuilder builds based on parameter value should be listed as downstream builds Seeing as you can clone the master repo, there is a pre-merged branch available named 2.17-RC you should be able to swap to use that using git checkout -b 2.17-RC remotes/origin/2.17-RC then do a mvn clean install. Note: this is under testing so make sure you backup any critical jenkins data first and look at the commit log for it to see if any of the other pull requests cause you issues. Otherwise have you tried following the merge commands in the pull request itself. create a branch pull branch from src repo merge into current branch. and for pull 19 this is git checkout -b wolfs-without-deps master git pull git://github.com/wolfs/parameterized-trigger-plugin.git without-deps This will then give you a branch with these changes. and if you then want that branch merged into master git checkout master git merge wolfs-without-deps git push origin master This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16897) thinBackup is expecting everything in the jobs folder to be a directory
Thomas Fürer resolved JENKINS-16897 as Duplicate thinBackup is expecting everything in the jobs folder to be a directory https://issues.jenkins-ci.org/browse/JENKINS-16426 Change By: Thomas Fürer (20/Feb/13 8:20 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/groups/opt_out.
[JIRA] (JENKINS-16897) thinBackup is expecting everything in the jobs folder to be a directory
Thomas Fürer commented on JENKINS-16897 thinBackup is expecting everything in the jobs folder to be a directory Hi paul, please look at the already fixed issue. if it is okay for you how I fixed it I would release a new version shortly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
