[JIRA] [maven] (JENKINS-21903) Not all maven downstream jobs get triggered
Stephane Odul commented on JENKINS-21903 Not all maven downstream jobs get triggered Still present in 1.553. I have a job with 15 downstream projects listed and only 5 are actually triggered. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc] (JENKINS-22105) [xvnc] Client is not authorized to connect to Server
Levon Saldamli commented on JENKINS-22105 [xvnc] Client is not authorized to connect to Server @Stephane, are you also running TightVNC? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21509) Create new item: NumberFormatException: for InputString
Philip Helger commented on JENKINS-21509 Create new item: NumberFormatException: for InputString Still happening in Version 1.554 - anyone can please fix this minimum error with maximum impact??? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21509) Create new item fails: NumberFormatException: for InputString
Philip Helger updated JENKINS-21509 Create new item fails: NumberFormatException: for InputString Change By: Philip Helger (11/Mar/14 6:40 AM) Summary: Createnewitem fails :NumberFormatException:forInputString This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvnc] (JENKINS-22105) [xvnc] Client is not authorized to connect to Server
Stephane Odul commented on JENKINS-22105 [xvnc] Client is not authorized to connect to Server Yes: TightVNC Server version 1.3.9 The OS is Ubuntu 12.04 LTS AMD64 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
su shi created JENKINS-22119 Fail to update update git repository with stored credential Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git, git-client Created: 11/Mar/14 6:58 AM Description: After upgrade to git plugin 2.0.4, git client plugin 1.6.4 All the jobs with https repository url and using stored credential failed, refer to following log. Downgrade to git:2.0.3, git-client 1.6.3, the issue has gone. 00:00:00.002 Started by user anonymous 00:00:00.003 EnvInject - Loading node environment variables. 00:00:00.004 Building on master in workspace xxx 00:00:00.108 Fetching changes from the remote Git repository 00:00:00.141 Fetching upstream changes from https://xxx.git 00:00:01.667 FATAL: Failed to fetch from https://xxx.git 00:00:01.668 hudson.plugins.git.GitException: Failed to fetch from https://.git 00:00:01.669 at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:621) 00:00:01.669 at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:853) 00:00:01.669 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:878) 00:00:01.669 at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) 00:00:01.669 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) 00:00:01.669 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) 00:00:01.669 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) 00:00:01.669 at hudson.model.Run.execute(Run.java:1676) 00:00:01.669 at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) 00:00:01.669 at hudson.model.ResourceController.execute(ResourceController.java:88) 00:00:01.669 at hudson.model.Executor.run(Executor.java:231) 00:00:01.669 at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) 00:00:01.669 Caused by: hudson.plugins.git.GitException: Failed to connect to https://.git using credentials (status = 401) 00:00:01.669 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.checkCredentials(CliGitAPIImpl.java:1725) 00:00:01.669 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1030) 00:00:01.669 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:88) 00:00:01.669 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:219) 00:00:01.669 at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:619) 00:00:01.669 ... 11 more Environment: Jenkins 1.553 Mac slave Project: Jenkins Priority: Critical Reporter: su shi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-21554) NPE if MavenMailer/recipients is undefined
Juha Syrjälä edited a comment on JENKINS-21554 NPE if MavenMailer/recipients is undefined We are also missing "recipients" element from "hudson.maven.reporters.MavenMailer". It also seems that you can't add recipients value via UI. When adding value to E-mail notification - Recipients, the value will be blank after saving the configuration. We are currently using Maven Project Plugin 2.0 (and Mailer plugin 1.6). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer] (JENKINS-21554) NPE if MavenMailer/recipients is undefined
Juha Syrjälä updated JENKINS-21554 NPE if MavenMailer/recipients is undefined Change By: Juha Syrjälä (11/Mar/14 7:25 AM) Component/s: mailer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-22120) Confusing disk usage row on project page
Anders Hammar
created JENKINS-22120
Confusing disk usage row on project page
Issue Type:
Improvement
Assignee:
Lucie Votypkova
Components:
disk-usage
Created:
11/Mar/14 7:51 AM
Description:
The displayed disk usage wor (above the graph) on the project page is difficult to understand.
Here's an example:
Disk Usage: Workspace 1196106074, Builds {all=647897209, locked=30513133}, Job directory 647922733
What unit are the figures in? Also, I can't get the Workspace size to match the figure printed in the Build History box (says 35 MB for the latest build) as the docs (https://wiki.jenkins-ci.org/display/JENKINS/Disk+Usage+Plugin) says.
Environment:
plugin v0.23 on Windows server with Jenkins LTS 1.532.2
Project:
Jenkins
Priority:
Major
Reporter:
Anders Hammar
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-22121) Items order in graph legend should match listed order in disk usage row
Anders Hammar created JENKINS-22121 Items order in graph legend should match listed order in disk usage row Issue Type: Improvement Assignee: Lucie Votypkova Components: disk-usage Created: 11/Mar/14 8:01 AM Description: The disk usage row lists the calcualted items in this order: workspace, builds, job directory The graph legend lists the items in this order: job directory, build directory, all jobs workspaces To simplify reading, the order here should be the same. Also, it would probably also cause less confusion if the name is the same in both places (compare "workspace" vs. "all jobs workspaces" for example). Environment: plugin v0.23 Project: Jenkins Priority: Minor Reporter: Anders Hammar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [disk-usage] (JENKINS-22122) Update plugin's doc page
Anders Hammar created JENKINS-22122 Update plugins doc page Issue Type: Task Assignee: Lucie Votypkova Components: disk-usage Created: 11/Mar/14 8:03 AM Description: The plugin's doc page (https://wiki.jenkins-ci.org/display/JENKINS/Disk+Usage+Plugin) does not list the latest released versions. Also, "Missing features and known bugs" is outdated and listed issues are fixed. Some of the text on the page is now also incorrect, like the screen shots. Environment: n/a Project: Jenkins Priority: Major Reporter: Anders Hammar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-21991) create new job(maven2/3 project) and Copy Maven Project ERROR:
elian fish updated JENKINS-21991 create new job(maven2/3 project) and Copy Maven Project ERROR: Change By: elian fish (11/Mar/14 8:12 AM) Summary: javax.servlet.ServletException:java.lang.NoSuchMethodError:hudson.maven.reporters.MavenMailer.init createnewjob ( Ljava maven2 / lang/String;ZZZ 3project ) V andCopyMavenProjectERROR: This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22123) Edit View - OK not working after update to v1.554
Rene Hess created JENKINS-22123 Edit View - OK not working after update to v1.554 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 11/Mar/14 8:12 AM Description: After updating to v1.554 the following behavior emerges: Opening 'edit view' dialog, modifying 'Description' field, then clicking 'OK' results in an empty (completely empty) page. Browser URL line showing ...'/configSubmit'. Modifications are not being saved. Reopening the dialog shows old configuration. Environment: running on Ubuntu, installed via apt-get Project: Jenkins Priority: Major Reporter: Rene Hess This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22123) Edit View - OK not working after update to v1.554
Rene Hess updated JENKINS-22123 Edit View - OK not working after update to v1.554 Change By: Rene Hess (11/Mar/14 8:15 AM) Environment: runningonUbuntu,installedviaapt-get Browser:Chromeaffected;workingcorrectlyinSafari This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-18951) Problems with too long paths
O H commented on JENKINS-18951 Problems with too long paths Thanks again. This solution now works perfectly so far! Far better than JGit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ivy] (JENKINS-22124) IvyPlugin seems defect / no downstream triggers
Jens Villadsen created JENKINS-22124 IvyPlugin seems defect / no downstream triggers Issue Type: Bug Assignee: Timothy Bingaman Components: ivy Created: 11/Mar/14 8:50 AM Description: The content inside the modules folder for each ivy-created job is not generated when using the ivy-plugin v1.23.2. This goes for the latest Jenkins LTS (v1.532.2). As this content is not generated, no build triggers are generated for downstream projects. Environment: CentOS 6.4 Project: Jenkins Labels: plugin Priority: Major Reporter: Jens Villadsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-22125) FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23
mwebber created JENKINS-22125 FATAL: Illegal choice: incremental caused by Parameterized Trigger Plugin 2.23 Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 11/Mar/14 9:03 AM Description: After I upgraded the Parameterized Trigger Plugin from 2.22 to 2.23, I had a number of jobs that failed immediately with FATAL: Illegal choice: incremental java.lang.IllegalArgumentException: Illegal choice: incremental at hudson.model.ChoiceParameterDefinition.checkValue(ChoiceParameterDefinition.java:75) at hudson.model.ChoiceParameterDefinition.createValue(ChoiceParameterDefinition.java:87) at hudson.model.ChoiceParameterDefinition.createValue(ChoiceParameterDefinition.java:19) at hudson.plugins.parameterizedtrigger.ProjectSpecificParameterValuesActionTransform.convertToDefinedType(ProjectSpecificParameterValuesActionTransform.java:62) at hudson.plugins.parameterizedtrigger.ProjectSpecificParameterValuesActionTransform.transformParametersAction(ProjectSpecificParameterValuesActionTransform.java:28) at hudson.plugins.parameterizedtrigger.ProjectSpecificParametersActionFactory.getProjectSpecificBuildActions(ProjectSpecificParametersActionFactory.java:32) at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.getBuildActions(BuildTriggerConfig.java:290) at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.perform2(BuildTriggerConfig.java:336) at hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig.perform2(BlockableBuildTriggerConfig.java:57) at hudson.plugins.parameterizedtrigger.TriggerBuilder.perform(TriggerBuilder.java:85) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) at hudson.model.Run.execute(Run.java:1676) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Downgrading the Parameterized Trigger Plugin back to 2.22 fixed the problem. All the failing jobs have build steps of type Trigger/call builds on other projects. Project: Jenkins Priority: Critical Reporter: mwebber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22104) Deploy to maven Repository does not update Snapshot maven-metadata.xml
Steve Eckerlein commented on JENKINS-22104 Deploy to maven Repository does not update Snapshot maven-metadata.xml After further investigation, the problem occur only if "unique version" if disabled in the job configuration. The maven-metadata.xml is correctly generated if the checkbox is checked. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep] (JENKINS-22045) Shell Variable WORKSPACE not set
Axel Bodemer commented on JENKINS-22045 Shell Variable WORKSPACE not set We used the Jenkins ver. 1.525. The information about a installed plugin "EnvInject" are strange, because in the file path exist the version "1.89". The jenkins-plugin-manager said, that it is not installed and it is not listed for an installation or an update. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22104) Deploy to maven Repository does not update Snapshot maven-metadata.xml
Steve Eckerlein updated JENKINS-22104 Deploy to maven Repository does not update Snapshot maven-metadata.xml Change By: Steve Eckerlein (11/Mar/14 9:56 AM) Description: wemigratefromArtifactoryaweekago,andwewereusingArtifactoryDeployPlugintopostbuilddeployourartifact.AswewenttoNexus,wenowusethePostbuilddeployfeatureofembeddedMavenProjectplugin.Everythingseemstoworks,butthemaven-metadata.xmlarenotupdatedwhenartifactsareuploaded. - Irunmanytests,andminingintologs(aswegotaApacheFrontofourNexus),andisawthattheplugindownload(twice)themaven-metadatafromNexus,anduploadonejustafter(thatthenormalbehaviour-exceptthetwicething). - Afterre-readingtheapachelogs,themetadataissimplynotdeployed.Thelogshowthemetadataoftheartifactversion,notthemave-metadata.xmlwithallversion.Wehavetestedwithoutnexus,bydeployinginafilesystem.Thebehaviouristhesame,andtheissueisstillhere.SoNexusisnotinvolved. Butwhenilookintothefile(maven-metadata.xml)thenewsnapshotversionisnotpresent.Asourintegrationprocessrelyonthismetadata,wearesomekindofblocked(theworkaroundistoscheduleataskinNexustorebuildmetadata,butthisisnotlive)AmImissingsomething?Hereistheapachelog:XXX.XXX.XXX.XXX--[10/Mar/2014:11:22:50+0100]GET/nexus/content/repositories/snapshots/com/socgen/fwk/socle/socle-architecture-transverse/2.13.0-SNAPSHOT/maven-metadata.xmlHTTP/1.1200341XXX.XXX.XXX.XXX--[10/Mar/2014:11:22:50+0100]GET/nexus/content/repositories/snapshots/com/socgen/fwk/socle/socle-architecture-transverse/2.13.0-SNAPSHOT/maven-metadata.xml.sha1HTTP/1.120040XXX.XXX.XXX.XXX--[10/Mar/2014:11:22:50+0100]PUT/nexus/content/repositories/snapshots/com/socgen/fwk/socle/socle-architecture-transverse/2.13.0-SNAPSHOT/socle-architecture-transverse-2.13.0-SNAPSHOT.pomHTTP/1.1201-XXX.XXX.XXX.XXX--[10/Mar/2014:11:22:50+0100]PUT/nexus/content/repositories/snapshots/com/socgen/fwk/socle/socle-architecture-transverse/2.13.0-SNAPSHOT/socle-architecture-transverse-2.13.0-SNAPSHOT.pom.md5HTTP/1.1201-XXX.XXX.XXX.XXX--[10/Mar/2014:11:22:51+0100]PUT/nexus/content/repositories/snapshots/com/socgen/fwk/socle/socle-architecture-transverse/2.13.0-SNAPSHOT/socle-architecture-transverse-2.13.0-SNAPSHOT.pom.sha1HTTP/1.1201-XXX.XXX.XXX.XXX--[10/Mar/2014:11:22:51+0100]GET/nexus/content/repositories/snapshots/com/socgen/fwk/socle/socle-architecture-transverse/2.13.0-SNAPSHOT/maven-metadata.xmlHTTP/1.1200341XXX.XXX.XXX.XXX--[10/Mar/2014:11:22:51+0100]GET/nexus/content/repositories/snapshots/com/socgen/fwk/socle/socle-architecture-transverse/2.13.0-SNAPSHOT/maven-metadata.xml.sha1HTTP/1.120040XXX.XXX.XXX.XXX--[10/Mar/2014:11:22:51+0100]PUT/nexus/content/repositories/snapshots/com/socgen/fwk/socle/socle-architecture-transverse/2.13.0-SNAPSHOT/maven-metadata.xmlHTTP/1.1201-XXX.XXX.XXX.XXX--[10/Mar/2014:11:22:51+0100]PUT/nexus/content/repositories/snapshots/com/socgen/fwk/socle/socle-architecture-transverse/2.13.0-SNAPSHOT/maven-metadata.xml.md5HTTP/1.1201-XXX.XXX.XXX.XXX--[10/Mar/2014:11:22:51+0100]PUT/nexus/content/repositories/snapshots/com/socgen/fwk/socle/socle-architecture-transverse/2.13.0-SNAPSHOT/maven-metadata.xml.sha1HTTP/1.1201-hereistheJenkinslogs:Mar10,201411:22:51AMorg.apache.maven.cli.logging.Slf4jLoggerinfoINFO:Uploadingrepositorymetadatafor:snapshotcom.socgen.fwk.socle:socle-architecture-transverse:2.13.0-SNAPSHOTSomeattachment:-ascreenofasectionofmyrepo,andatthesamethecorrespondingmaven-metadata.xml-theconfigurationofmypostdeploytask(notuniqueversion-evenifinstable) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22107) java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction
Ulli Hafner commented on JENKINS-22107 java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction Which version of the pmd plug-in and analysis core is installed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs] (JENKINS-21102) Findbugs throws FileNotFoundException
Ulli Hafner resolved JENKINS-21102 as Cannot Reproduce Findbugs throws FileNotFoundException Please reopen if you have more details. Change By: Ulli Hafner (11/Mar/14 10:09 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [checkstyle] (JENKINS-19395) Failed Loading plugin findbugs
Ulli Hafner resolved JENKINS-19395 as Not A Defect Failed Loading plugin findbugs Needs to be fixed in websphere class path. Change By: Ulli Hafner (11/Mar/14 10:10 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22107) java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction
Ulli Hafner resolved JENKINS-22107 as Fixed java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction PMD 5.1 contains a fix. Change By: Ulli Hafner (11/Mar/14 10:14 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/d/optout.
[JIRA] [dry] (JENKINS-15593) Both DryPublisher and PmdPublisher abort due to exception
Ulli Hafner resolved JENKINS-15593 as Fixed Both DryPublisher and PmdPublisher abort due to exception This should be fixed in PMD 5.1.0 Change By: Ulli Hafner (11/Mar/14 10:19 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/d/optout.
[JIRA] [findbugs] (JENKINS-12330) Occasionally,collecting findbugs analysis files will take very long time, event two more hours.
Ulli Hafner commented on JENKINS-12330 Occasionally,collecting findbugs analysis files will take very long time, event two more hours. Please attach your files sp I can try to reproduce... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs] (JENKINS-15386) Cannot tag builds using cvs plugin
Monique Maker edited a comment on JENKINS-15386 Cannot tag builds using cvs plugin Hello Michael, We are using CVS Plug-in v.2.11 and unfortunately on the page of CVS Tag plug-in (at the moment of this writing) is hanging "WARNING: CVS Tagging plugin currently does not work with CVS Plugin 2.0 or later." And once the tagging functionality is already available in CVS plug-in, isn't it better to provide an interface to it than to use an additional plug-in supported by another developer? Cheers, Monique This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21437) Failed to update /computer/xxxxxxxxxxx/builds
martin brook commented on JENKINS-21437 Failed to update /computer/xxx/builds I have the same error here, SLES 11 SP1, Java 6 (JRE) 1.549 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11370) The directory name is invalid on Windows slaves
Oleg Nenashev
updated JENKINS-11370
The directory name is invalid on Windows slaves
Updated the issue.
I suppose it is not related to pre-scm-buildstep, because it also appears in other build steps
Change By:
Oleg Nenashev
(11/Mar/14 11:52 AM)
Summary:
pre-scm-buildstepassumesworkspaceexists
ThedirectorynameisinvalidonWindowsslaves
Labels:
slave
Environment:
OSX
1.509.4
Priority:
Minor
Major
Description:
Olddescription:{quote}
pre-scm-buildstepassumesthatthedirectoryworkspaceexistswhenitsrunning.However,whensettingupaproject,itdoesnotexist,andthusthisstepwillfailunlesstheadmincreatesmanually.Properbehaviourshouldbetocheckifitexists,andcreateitifitdoesnt.Otherwise,ifitdoesnotexist,theexecuteshellwillfail
{quote}Theissuealsoappliestosystemcallsinvokedfromotherplaces
Component/s:
core
Component/s:
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/d/optout.
[JIRA] [analysis-collector] (JENKINS-22107) java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction
Facundo Mateo updated JENKINS-22107 java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction Change By: Facundo Mateo (11/Mar/14 12:17 PM) Description: AfteramavenbuildinJenkins,inthe analisys analysis resultpanelIgetanexceptionwithanembeddederrorpage.ThiswasworkingfineuntilIupdatejenkinstoversion1.552. TheproblemseemstobeintheanalysiscollectorpluginwhenIttriestoPublishacombinedanalysisresult(Findbugs,Duplicatecode,checkstyle). Imusing:StaticAnalysisCollectorPlug-inv1.40Findbugspluginv4.51StaticAnalysisUtilitiesv1.55TaskScannerPlug-inv4.39DuplicateCodeScannerPlug-inv2.39CheckstylePlug-inv3.39Actually,IdonthavePMDplugininstalled. Aproblemoccurredwhileprocessingtherequest.Pleasecheckourbugtrackertoseeifasimilarproblemhasalreadybeenreported.Ifitisalreadyreported,pleasevoteandputacommentonittoletusgaugetheimpactoftheproblem.Ifyouthinkthisisanewissue,pleasefileanewissue.Whenyoufileanissue,makesuretoaddtheentirestacktrace,alongwiththeversionofJenkinsandrelevantplugins.Theuserslistmightbealsousefulinunderstandingwhathashappened.Stacktracejavax.servlet.ServletException:org.apache.commons.jelly.JellyTagException:jar:file:path-to-jenkins-config-dir/jenkins/plugins/maven-plugin/WEB-INF/lib/classes.jar!/hudson/maven/MavenModuleSet/index.jelly:71:70:st:includehudson/plugins/pmd/PmdProjectAction atorg.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) atorg.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:858) atorg.kohsuke.stapler.Stapler.invoke(Stapler.java:631) atorg.kohsuke.stapler.Stapler.service(Stapler.java:225) atjavax.servlet.http.HttpServlet.service(HttpServlet.java:722) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) athudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) athudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) athudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:91) atorg.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) atorg.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) athudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atjenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79) athudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) atorg.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
[JIRA] [analysis-collector] (JENKINS-22107) java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction
Facundo Mateo reopened JENKINS-22107 java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction Ulli, I don't have PMD plugin installed. Actually, I'm not using pmd... just Asigned the wrong component my mistake. I have updated the components field and added extra information about the problems and my jenkins configuration: I'm using: Static Analysis Collector Plug-in v1.40 Findbugs plugin v4.51 Static Analysis Utilities v1.55 Task Scanner Plug-in v4.39 Duplicate Code Scanner Plug-in v2.39 Checkstyle Plug-in v3.39 The problem happens when I publish a "Combined analysis result" Change By: Facundo Mateo (11/Mar/14 12:20 PM) 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/d/optout.
[JIRA] [analysis-collector] (JENKINS-22107) java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction
Facundo Mateo edited a comment on JENKINS-22107 java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction Ulli, I don't have PMD plugin installed. Actually, I'm not using pmd... just Asigned the wrong component my mistake. I have updated the components field and added extra information about the problems and my jenkins configuration: I'm using: Static Analysis Collector Plug-in v1.40 Findbugs plugin v4.51 Static Analysis Utilities v1.55 Task Scanner Plug-in v4.39 Duplicate Code Scanner Plug-in v2.39 Checkstyle Plug-in v3.39 The problem happens when I publish a "Combined analysis result". I don't understand why I'm getting PMD class not found If I take in account than I'm not using pmd. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22089) android userdata.img not found and skin name not valid
Mr Cinquero commented on JENKINS-22089 android userdata.img not found and skin name not valid https://code.google.com/p/android/issues/detail?id=66980 Hint: try to omit the abi definition on the command line. Should be selected through the target. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
Mark Waite commented on JENKINS-22119 Fail to update update git repository with stored credential I believe the 401 error code in the stack trace indicates that the request was not authorized by the web server. The git-client-plugin 1.6.4 switched from an obsolete version of an http library to a newer supported version of that http library. It also added support the NTLM credentials and for Team Foundation Server git repositories. If you'd be willing to perform the test, I'd appreciate having you attempt to upgrade just the git-client-plugin, without upgrading git-plugin. If it fails then that will point to changes in git-client-plugin as the most likely cause. If it passes, then it will need to be investigated in both. Does the https server use a self-signed certificate? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrents] (JENKINS-22127) Exceptions for certain nodes
Sam Halliday created JENKINS-22127 Exceptions for certain nodes Issue Type: New Feature Assignee: abayer Components: throttle-concurrents Created: 11/Mar/14 12:35 PM Description: This plugin is great, thank you! We wanted to throttle a certain high-resource task to one per node, but then received a much more powerful machine that could potentially run 5 at once. There doesn't appear to be any way to override the throttling rules on a per-node basis. Project: Jenkins Priority: Major Reporter: Sam Halliday This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-22107) java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction
Facundo Mateo commented on JENKINS-22107 java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction Installed PMD plugin just to try to get rid of the exception ... afterwards I get a new exception... javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Users/fmateo/Documents/desarrollo/servers/apache-tomcat-7.0.30/custom/jenkins/plugins/maven-plugin/WEB-INF/lib/classes.jar!/hudson/maven/MavenModuleSet/index.jelly:71:70: st:include hudson/plugins/warnings/AggregatedWarningsProjectAction at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:91) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:79) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at
[JIRA] [analysis-collector] (JENKINS-22107) java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction
Facundo Mateo updated JENKINS-22107 java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction Change By: Facundo Mateo (11/Mar/14 12:40 PM) Component/s: analysis-core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
Heather Fraser-Dube commented on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart I am not entirely sure what is going wrong on the slave. I think it should be able to find the jars for the toolkit (I assume it did before). I also don't think I ever saw this problem when I was testing with the slaves. Only thing I can suggest is to turn on debugging for the slave and see if anything strange is happening wrt class loading. On the Slave while we log messages at level FINER, the logs never come back. We have support for a debug flag which will result in the debug output going into a build's console log Environment variable "com.ibm.team.build.debug" with the value "true" will activate the debug logging To configure on a single Slave Jenkins Manage Jenkins Manage nodes Hover over the link of the node to configure. Choose Configure from the popup context menu In the Node properties section, select and check the Environment variables checkbox Click the Add button beside the List of key value pairs. Supply "com.ibm.team.build.debug" as the name and "true" as the value Click the Save button. Alternately to configure on the Master and all Slaves Jenkins Manage Jenkins Configure System In the Global Properties section, select and check the Environment variables checkbox Click the Add button beside the List of key value pairs. Supply "com.ibm.team.build.debug" as the name and "true" as the value Click the Save button. The debug flag currently only logs information relating to the class loader setup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-22110) Jenkins RTC SCM Jobs error out after Master Restart
Heather Fraser-Dube edited a comment on JENKINS-22110 Jenkins RTC SCM Jobs error out after Master Restart I am not entirely sure what is going wrong on the slave. I think it should be able to find the jars for the toolkit (I assume it did before). I also don't think I ever saw this problem when I was testing with the slaves. Only thing I can suggest is to turn on debugging for the slave and see if anything strange is happening wrt class loading. On the Slave while we log messages at level FINER, the logs never come back. We have support for a debug flag which will result in the debug output going into a build's console log Environment variable "com.ibm.team.build.debug" with the value "true" will activate the debug logging To configure on a single Slave Jenkins Manage Jenkins Manage nodes Hover over the link of the node to configure. Choose Configure from the popup context menu In the Node properties section, select and check the Environment variables checkbox Click the Add button beside the List of key value pairs. Supply "com.ibm.team.build.debug" as the name and "true" as the value Click the Save button. Alternately to configure on the Master and all Slaves Jenkins Manage Jenkins Configure System In the Global Properties section, select and check the Environment variables checkbox Click the Add button beside the List of key value pairs. Supply "com.ibm.team.build.debug" as the name and "true" as the value Click the Save button. The debug flag currently only logs information relating to the class loader setup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
michael soukup updated JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Change By: michael soukup (11/Mar/14 1:03 PM) Attachment: Jenkins-credentials.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [exclusion] (JENKINS-22128) Lowercase resource appears twice in Resource dropdown list
Csaba Szabo created JENKINS-22128 Lowercase resource appears twice in Resource dropdown list Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Screen Shot 2014-03-11 at 14.08.42.png, Screen Shot 2014-03-11 at 14.08.52.png Components: exclusion Created: 11/Mar/14 1:16 PM Description: How to reproduce: Create a resource with not uppercase name, like: 'iOS7 Simulator' Add this resource to an another job Actual result: The resource is duplicated, there is a non-uppercase and an uppercase version, but on Exclusion control panel only the uppercase version is available. Environment: Ubuntu Server Project: Jenkins Priority: Major Reporter: Csaba Szabo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
michael soukup commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials @chikigai: the mistake I at first made was to enter the complete url to the external subproject as realm. you have to enter it like in the screenshot I attached: make sure to include the pointy brackets and to enter the title the server responses when you access it through the web interface (as Daniel said in comment-196363) Our server provides this dialog so "VisualSVN Server" is what I entered after the host-url (which is the one under the white rectangle). This works for us and as we have a repository structure very similar to yours hopefully also works for you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-16868) Icons are not displayed with a reverse proxy
Walter Kacynski commented on JENKINS-16868 Icons are not displayed with a reverse proxy I have the same behavior that Matt is experiencing. My apache reverse proxy is configured as: ProxyPass/jenkins/ http://TSTJENK001..com:8080/jenkins/ nocanon ProxyPassReverse /jenkins/ http://TSTJENK001..com:8080/jenkins/ Why do all of the URL links have absolute paths as opposed to relative paths like the rest of the images in the page? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-16868) Icons are not displayed with a reverse proxy
Walter Kacynski edited a comment on JENKINS-16868 Icons are not displayed with a reverse proxy I have the same behavior that Matt is experiencing. My apache reverse proxy is configured as: ProxyPass/jenkins/ http://TSTJENK001..com:8080/jenkins/ nocanon ProxyPassReverse /jenkins/ http://TSTJENK001..com:8080/jenkins/ Why do all of the Images have absolute paths as opposed to relative paths like the rest of the images in the page? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Aapo Romu commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING I was able to fix the problem by deleting rm -rf jenkins/jobs/project_name/modules/* and then restarting Jenkins. You should be able to script that easily if you have a lot of projects This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19569) Git polling builds even when includes section doesn't include the changes
Alexander Uvizhev commented on JENKINS-19569 Git polling builds even when includes section doesnt include the changes I got a similar issue. Set only included region (like mydir/.*) but builds are triggered on every change. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing] (JENKINS-20126) Add Support for Heavy Jobs Slicing
Walter Kacynski updated JENKINS-20126 Add Support for Heavy Jobs Slicing Change By: Walter Kacynski (11/Mar/14 1:48 PM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core] (JENKINS-21769) NoClassDefFoundError on Job page when checkstyle not installed
Ulli Hafner reopened JENKINS-21769 NoClassDefFoundError on Job page when checkstyle not installed Change By: Ulli Hafner (11/Mar/14 1:51 PM) 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/d/optout.
[JIRA] [analysis-collector] (JENKINS-22107) java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction
Ulli Hafner commented on JENKINS-22107 java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction Sorry, my comment on PMD 5.1 was for the wrong issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-22107) java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction
Ulli Hafner commented on JENKINS-22107 java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction Your problem is a duplicate of JENKINS-21769. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Alexander Uvizhev commented on JENKINS-20569 Polling with excluded regions dont prevent job triggered So Included/Excluded Regions doesn't work without "Force polling using workspace", is it? If so, should the first option at least mention it or even forcibly enable the second one? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered
Mark Waite commented on JENKINS-20569 Polling with excluded regions dont prevent job triggered Yes, included/excluded regions require "Force polling using workspace". You're welcome to submit a pull request with an improvement to the help, or with forcible enablement of using a workspace for polling. Currently there are pull requests under review and discussion around the issue, including https://github.com/jenkinsci/git-plugin/pull/93 and https://github.com/jenkinsci/git-plugin/pull/89 . Both pull requests may need further work before they can be pulled, and they may be mutually exclusive, but you could consider them . Neither of them do precisely what you've proposed, but they may give you an idea where to investigate in the code. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plot] (JENKINS-21493) NullPointerException in Publisher
SCM/JIRA link daemon commented on JENKINS-21493 NullPointerException in Publisher Code changed in jenkins User: Kevin German Path: src/test/java/hudson/plugins/plot/XMLSeriesTest.java src/test/resources/test3.xml http://jenkins-ci.org/commit/plot-plugin/60b081b05e0f75548afce58063cdb7da298198bd Log: test to replicate JENKINS-21493 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plot] (JENKINS-21493) NullPointerException in Publisher
SCM/JIRA link daemon commented on JENKINS-21493 NullPointerException in Publisher Code changed in jenkins User: Kevin German Path: src/main/java/hudson/plugins/plot/XMLSeries.java src/test/java/hudson/plugins/plot/XMLSeriesTest.java http://jenkins-ci.org/commit/plot-plugin/96f1acc161a6c536e0b4b4f66e646fd724edf308 Log: reimplement loadSeries to support all cases described in tests - fix JENKINS-21493 rename test methods to descibe use case being asserted cleanup use of Double.parseDouble and replace with Scanner becuase it extract block to handle case for coalescing nodes in a Nodeset supports LOCALES, does not throw, handles commas appropriately for locale and doesn't throw. Tests updated where comparisons were failing for number format. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plot] (JENKINS-21493) NullPointerException in Publisher
SCM/JIRA link daemon resolved JENKINS-21493 as Fixed NullPointerException in Publisher Change By: SCM/JIRA link daemon (11/Mar/14 2:15 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/d/optout.
[JIRA] [plot] (JENKINS-21493) NullPointerException in Publisher
SCM/JIRA link daemon commented on JENKINS-21493 NullPointerException in Publisher Code changed in jenkins User: ericbn Path: src/main/java/hudson/plugins/plot/XMLSeries.java src/test/java/hudson/plugins/plot/XMLSeriesTest.java src/test/resources/test3.xml http://jenkins-ci.org/commit/plot-plugin/7274fce3884ed0bd750d4b962f6348adc7de2ba3 Log: Merge pull request #9 from ludyte/master FIXED JENKINS-21493 Compare: https://github.com/jenkinsci/plot-plugin/compare/07babd8fdf32...7274fce3884e This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jenkins-reviewbot] (JENKINS-19642) ReviewBot plugin fails after 'apply patch'
Dan Albu commented on JENKINS-19642 ReviewBot plugin fails after apply patch @ dinesh : can you tell me how did you configure the plugin so you won't get the java.io.IOException: ?? THe plugin is great but i can see a bright future for it This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator] (JENKINS-22058) Infinite loop on hanging rebase (our case 10651)
Mads Nielsen resolved JENKINS-22058 as Fixed Infinite loop on hanging rebase (our case 10651) Change By: Mads Nielsen (11/Mar/14 2:30 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [schedule-build] (JENKINS-22129) H/2 * * * * is polling every second minute, but H/1 * * * * only once per hour
Markus KARG created JENKINS-22129 H/2 * * * * is polling every second minute, but H/1 * * * * only once per hour Issue Type: Bug Assignee: Andreas K Components: schedule-build Created: 11/Mar/14 2:37 PM Description: H/2 * * * * is polling every second minute. H/1 * * * * is polling once per hour. This is confusing. H/1 * * * * should instead poll once per minute, but with an offset of a random number of seconds. Environment: SVN, Windows, 1.532.2 Project: Jenkins Priority: Major Reporter: Markus KARG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode] (JENKINS-22130) keychain with the same name already exists error with Multi-configuration and developer profile import
Trey Duskin created JENKINS-22130 keychain with the same name already exists error with Multi-configuration and developer profile import Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: xcode Created: 11/Mar/14 2:51 PM Description: I have a multi-configuration build set up using the Xcode plugin with a user-defined axis for build targets in the Xcode project, as well as the slave axis to force the builds to execute on my OSX build slave (and not anywhere else). The first build step in this job is to import the developer profile using the "Import Developer Profile" function. When I set it up this way, the first time I execute the build, the child jobs launch and complete successfully. The second time I try to run this build, however, all the child jobs fail at the "import developer profile" step. The console log for one of the child builds shows the following: $ security list-keychains $ security create-keychain -p jenkins-iOS-Client-app=TargetA,label=osx security: SecKeychainCreate jenkins-iOS-Client-app=TargetA,label=osx: A keychain with the same name already exists. ERROR: Failed to create a keychain Finished: FAILURE The other child jobs show the same errors for their respective build targets. If I manually run the 'security list-keychains' on the build slave as the build user (jenkins), I don't see any keychains listed: $ sudo -u jenkins security list-keychains Password: "/Library/Keychains/System.keychain" I'm guessing this is why the Xcode plugin tries to re-create the keychain. This is a major issue for us as, without us being able to use multi-configuration jobs with Xcode, we have to create a new job for every individual build target, which is unscalable for us. Environment: Ubuntu 12.04.3 (Master), OSX Mavericks 10.9.2 (slave) Project: Jenkins Priority: Major Reporter: Trey Duskin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
su shi commented on JENKINS-22119 Fail to update update git repository with stored credential yes, with only git-client upgraded to 1.6.4, git fetch failed. The server is not using self-signed cert. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
su shi commented on JENKINS-22119 Fail to update update git repository with stored credential yes, with only git-client upgraded to 1.6.4, git fetch failed. The server is not using self-signed cert. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22131) Extract generic features from AbstractProject/AbstractBuild
Jesse Glick started work on JENKINS-22131 Extract generic features from AbstractProject/AbstractBuild Change By: Jesse Glick (11/Mar/14 3:27 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22131) Extract generic features from AbstractProject/AbstractBuild
Jesse Glick created JENKINS-22131 Extract generic features from AbstractProject/AbstractBuild Issue Type: New Feature Assignee: Jesse Glick Components: core Created: 11/Mar/14 3:27 PM Description: Specialized job types such as are defined in async-job-plugin, branch-api-plugin, or external-monitor-job-plugin do not extend AbstractProject / AbstractBuild because these classes make very specific assumptions about build semantics: that you have a CI job (SCM), an assigned workspace, and so on. Yet without extending those classes you currently have a hard time picking up generic features like parameter definitions trigger definitions manual or REST build causes lazy-loading of runs Those features should be decoupled so that they are available à la carte for other Job / Run types. Project: Jenkins Labels: api Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22131) Extract generic features from AbstractProject/AbstractBuild
Jesse Glick updated JENKINS-22131 Extract generic features from AbstractProject/AbstractBuild Change By: Jesse Glick (11/Mar/14 3:27 PM) URL: https://github.com/jenkinsci/jenkins/pull/1146/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core] (JENKINS-21769) NoClassDefFoundError on Job page when checkstyle not installed
SCM/JIRA link daemon commented on JENKINS-21769 NoClassDefFoundError on Job page when checkstyle not installed Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/collector/AnalysisProjectAction.java http://jenkins-ci.org/commit/analysis-collector-plugin/1bb54874708360ec1b5edfb09e69a16e55e6a576 Log: FIXED JENKINS-21769 Don't load classes of optional plug-ins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core] (JENKINS-21769) NoClassDefFoundError on Job page when checkstyle not installed
SCM/JIRA link daemon resolved JENKINS-21769 as Fixed NoClassDefFoundError on Job page when checkstyle not installed Change By: SCM/JIRA link daemon (11/Mar/14 3:50 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core] (JENKINS-21769) NoClassDefFoundError on Job page when checkstyle not installed
SCM/JIRA link daemon commented on JENKINS-21769 NoClassDefFoundError on Job page when checkstyle not installed Code changed in jenkins User: Ulli Hafner Path: .idea/libraries/Maven__org_jvnet_hudson_plugins_findbugs_library_2_0_4.xml findbugs http://jenkins-ci.org/commit/analysis-suite-plugin/5221be58b6fa7f8caef97de8c7cc99f5109c9b71 Log: FIXED JENKINS-21769 Don't load classes of optional plug-ins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-22107) java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction
Ulli Hafner resolved JENKINS-22107 as Fixed java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction Fixed in 1.41. Change By: Ulli Hafner (11/Mar/14 3:52 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-22107) java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction
Facundo Mateo commented on JENKINS-22107 java.lang.NoClassDefFoundError: hudson/plugins/pmd/PmdProjectAction The second exception is a duplicate from JENKINS-21769. But does it means that I need to have installed pmd plugin even though i'm not using it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22071) 'pull_request' type webhook from Github throws an exception
Kohsuke Kawaguchi commented on JENKINS-22071 pull_request type webhook from Github throws an exception It sounds like the original comment is about a bug (where Jenkins thinks there's no payload when there is one), while Dr. Kibitz is talking about a possible RFE. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
SCM/JIRA link daemon commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/hudson/maven/MavenModuleSetBuild.java http://jenkins-ci.org/commit/maven-plugin/4bdfef299f07fabedcb43b902d5ddfc05d62f8cd Log: FIXED JENKINS-21279 Not sure packaging doesn't defeault to "jar", which seems to be the default, but being defensive. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
SCM/JIRA link daemon resolved JENKINS-21279 as Fixed java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING Change By: SCM/JIRA link daemon (11/Mar/14 4:27 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/d/optout.
[JIRA] [periodic-reincarnation] (JENKINS-22132) Ratchet back PeriodicReincarnation logging or run periodicity
Daniel Kirkdorffer created JENKINS-22132 Ratchet back PeriodicReincarnation logging or run periodicity Issue Type: Bug Assignee: Unassigned Components: periodic-reincarnation Created: 11/Mar/14 4:49 PM Description: Is it possible to reduce the logging from this plugin? Mar 11, 2014 9:44:13 AM INFO hudson.model.AsyncPeriodicWork$1 run Started PeriodicReincarnation Mar 11, 2014 9:44:13 AM INFO hudson.model.AsyncPeriodicWork$1 run Finished PeriodicReincarnation. 0 ms It runs every minute, producing this log output. If not, if there a way to have it run less often? Project: Jenkins Priority: Minor Reporter: Daniel Kirkdorffer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [periodic-reincarnation] (JENKINS-22132) Ratchet back PeriodicReincarnation logging or run periodicity
Daniel Kirkdorffer updated JENKINS-22132 Ratchet back PeriodicReincarnation logging or run periodicity Change By: Daniel Kirkdorffer (11/Mar/14 4:49 PM) Description: Isitpossibletoreducetheloggingfromthisplugin?Mar11,20149:44:13AMINFOhudson.model.AsyncPeriodicWork$1runStartedPeriodicReincarnationMar11,20149:44:13AMINFOhudson.model.AsyncPeriodicWork$1runFinishedPeriodicReincarnation.0msItrunseveryminute,producingthislogoutput.Ifnot possible , if is thereawayto have atleastconfigure it to runlessoften? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [security] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Kohsuke Kawaguchi resolved JENKINS-16278 as Fixed Remember me on this computer does not work, cookie is not accepted in new session The last comment from Alexander Artemov seems to indicate the problem is resolved, so I'm marking it closed until we hear otherwise. Change By: Kohsuke Kawaguchi (11/Mar/14 5:04 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [checkstyle] (JENKINS-20516) No description available. Please upgrade checkstyle version
Alexander Obuhovich updated JENKINS-20516 No description available. Please upgrade checkstyle version Change By: Alexander Obuhovich (11/Mar/14 5:11 PM) Attachment: Jenkins_CodeStyle_Hint.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [checkstyle] (JENKINS-20516) No description available. Please upgrade checkstyle version
Alexander Obuhovich commented on JENKINS-20516 No description available. Please upgrade checkstyle version I'm having the same hint on Codestyle. I'm using PHP_CodeSniffer to generate codestyle.xml. The URL of the page: http://www.website.tld/job/jobName/lastBuild/checkstyleResult/new/file.331601383/source.22025/#43 See image attached. Jenkins ver. 1.554 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [checkstyle] (JENKINS-20516) No description available. Please upgrade checkstyle version
Alexander Obuhovich reopened JENKINS-20516 No description available. Please upgrade checkstyle version Change By: Alexander Obuhovich (11/Mar/14 5:27 PM) Resolution: Incomplete Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22119) Fail to update update git repository with stored credential
Mark Waite commented on JENKINS-22119 Fail to update update git repository with stored credential Thanks. That indicates the problem is likely in the git-client-plugin changes from 1.6.3 to 1.6.4. We'll need you to do deeper investigation to try to narrow the failure modes. Some of the questions which may help narrow the failure modes include: Does the problem also appear on a copy of the failing job? Does the problem also appear on a newly created job using the same git URL and credentials? Does the problem also appear with other https git repositories in your environment? Does the problem also appear for you with https git repositories outside your environment? (like github or bitbucket) Is there a public URL which can be used to see the same problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-file-provider] (JENKINS-16706) Configure provided settings.xml at the Maven plugin level, not at the Maven job level
Dominik Bartholdi commented on JENKINS-16706 Configure provided settings.xml at the Maven plugin level, not at the Maven job level This is not a bug, the "Use default maven settings" are the "vanilla" settings.xml in the .m2 directory - so it actually works as designed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Kohsuke Kawaguchi commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Discovering my own comment in JENKINS-11643 that this is disabled in Active Directory plugin when Jenkins cannot load details of users by name. That is, either it needs to be running on Windows (where Jenkins can obtain information about other users through ADSI that uses the host computer's credential) or bind DN/password would have to be provided, where Jenkins can obtain information about other users by using this credential. So the cause is at least known. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flexible-publish] (JENKINS-22133) Add Run on configuration option for matrix projects
Oleg Nenashev created JENKINS-22133 Add Run on configuration option for matrix projects Issue Type: New Feature Assignee: bap Components: flexible-publish Created: 11/Mar/14 6:02 PM Description: Sometimes we need to run publishers on parent builds only. Example: aggregate results inside groovy scripts Project: Jenkins Labels: matrix Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-22025) VM cannot be started repeatedly with vSphere plugin
Bryan Havenstein commented on JENKINS-22025 VM cannot be started repeatedly with vSphere plugin Thanks for the info Jason! I do believe that is the issue. I was able to reproduce the issue specifically by starting some heavy activity on the ESXI host (file copy/export), which did cause the task to take longer than the limit (16 sec). I can't say exactly what is causing this error regularly, but our host isn't the fastest in the world and it's pretty heavily loaded at times, so most likely this timeout is the culprit. I tried the same again and got the same error, but the elapsed time was only 12 sec according to vSphere client, so can't really explain that one. Assume there is more overhead somewhere. BTW, we don't have any vCenter in this setup. The plugin is talking to ESXI directly if that makes any difference. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scriptler] (JENKINS-22134) Add data-bound builder's constructor to support conditional build steps
Oleg Nenashev created JENKINS-22134 Add data-bound builders constructor to support conditional build steps Issue Type: Improvement Assignee: Dominik Bartholdi Components: scriptler Created: 11/Mar/14 6:27 PM Description: Conditional Build Step plugin requires a DataBoundConstructor to allow the execution of build steps inside conditional steps. It also affects Flexible Publish plugin (via Any Build Step) It makes sense to add support of scriptler steps, which don't require extensive validation inside the newInstance() handler. Project: Jenkins Priority: Major Reporter: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scriptler] (JENKINS-22134) Add data-bound builder's constructor to support conditional build steps
Dominik Bartholdi resolved JENKINS-22134 as Duplicate Add data-bound builders constructor to support conditional build steps Change By: Dominik Bartholdi (11/Mar/14 6:34 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-22025) VM cannot be started repeatedly with vSphere plugin
Jason Swager commented on JENKINS-22025 VM cannot be started repeatedly with vSphere plugin The funny thing is that another user has a similar problem - but their start failure is for slaves, not the build steps. Same problem in both cases; host or vCenter under load or taking longer than expected to complete the operation. Solution is the same in both cases: increase the timeout. I hope to have a fix out for this in an official release in the next day or two. By the way, you don't need a full vCenter to perform the work - you can talk directly to ESXi. It has to be a license ESXi; not the free one you can get from VMware. The free one won't accept SDK commands that the vSphere Plugin uses. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scriptler] (JENKINS-22134) Add data-bound builder's constructor to support conditional build steps
Oleg Nenashev closed JENKINS-22134 as Duplicate Add data-bound builders constructor to support conditional build steps Sorry... I've missed this issue Change By: Oleg Nenashev (11/Mar/14 6:46 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-22071) 'pull_request' type webhook from Github throws an exception
Nukul Bhasin commented on JENKINS-22071 pull_request type webhook from Github throws an exception Kohshuke, thanks for having a look. I am simply interested in finding out why Jenkins (at least the github plugin) is unable to get the payload. Obviously I will need to write the parsing of the pull_request type webhook myself and I happy to contribute that back into the plugin. I just need help figuring out why its not getting a payload. If you can help me debug or give me some pointer I would greatly appreciate. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scriptler] (JENKINS-15975) Allow Scriptler to be used in Conditional BuildStep plugin
Oleg Nenashev commented on JENKINS-15975 Allow Scriptler to be used in Conditional BuildStep plugin Workaround: Use "Template Project" plugin. You can include Scriptler calls from a remote job inside conditional steps This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-11643) v1.21 produces exception shortly after login: org.acegisecurity.AuthenticationServiceException: Unable to retrieve the user information without bind DN/passwo
SCM/JIRA link daemon commented on JENKINS-11643 v1.21 produces exception shortly after login: org.acegisecurity.AuthenticationServiceException: Unable to retrieve the user information without bind DN/password configured Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/security/TokenBasedRememberMeServices2.java test/src/test/groovy/hudson/security/TokenBasedRememberMeServices2Test.groovy http://jenkins-ci.org/commit/jenkins/2dbd6eca7f8c19222a04f68b548d54a163883ba0 Log: JENKINS-11643 An unexpected failure in processing remember me cookie should be handled gracefully. In particular, possibly problematic cookie should be removed, or else the browser will keep bombarding the server with the same cookie, and will never be able to get through. It's much better to just drop the cookie. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-15061) Wrong LIBPATH when running ssh slave on AIX
James Short commented on JENKINS-15061 Wrong LIBPATH when running ssh slave on AIX The slave configuration via "Environment Variables" does not let me 'unset' LIBPATH. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-15061) Wrong LIBPATH when running ssh slave on AIX
James Short edited a comment on JENKINS-15061 Wrong LIBPATH when running ssh slave on AIX The slave configuration via "Environment Variables" does not let me 'unset' LIBPATH. EDIT: ^^^ Ignore that, slave process had to be restarted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-22136) Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security
chris vecchione
created JENKINS-22136
Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security
Issue Type:
Bug
Assignee:
Thorsten Heit
Components:
crowd2
Created:
11/Mar/14 8:20 PM
Description:
The Jenkins Crowd2 plugin security plugin functionality NOT working as described (expected) in the 'Project-based Matrix Authorization Strategy':
1) Crowd group (call the group "X_TEST") given read-only permissions for all jobs in the Project-based Matrix Authorization Strategy within the jenkins application's 'Configuration Global Security' link.
2) While configuring a job (project) called "JobX_test" , I checked (true) the 'Enable project-based security' option and added crowd group "X_TEST" to the 'User/group' with all job related permissions (read | discover | build | workspace | configure...etc.). Saved it.
3) Note: No other group is enabled within the job ("JobX_test").
4) User "X" who is part of the "X_TEST" group only logs in and can NOT configure (nor build) the job ("jobX_test").
5) IF I increase the overall group's ("X_TEST") permissions to build and configure in the application's 'Configuration Global Security' link, THEN the user can build or configure the job ("JobX_test")!
So, bottom line, application permissions overrides the individual 'project-based security' permissions! It should be the opposite functionality in which individual 'project' permissions supercedes the applications's security settigns for the group (or user) as described in the following link:
https://wiki.jenkins-ci.org/display/JENKINS/2012/01/03/Allow+access+to+specific+projects+for+Users(Assigning+security+for+projects+in+Jenkins)
Project:
Jenkins
Priority:
Critical
Reporter:
chris vecchione
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-22136) Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security
chris vecchione updated JENKINS-22136 Jenkins Crowd2 plugin Project-based Matrix Authorization Strategy functionally issue - application permissions override the project-based security Change By: chris vecchione (11/Mar/14 8:22 PM) Description: TheJenkinsCrowd2pluginsecuritypluginfunctionalityNOTworkingasdescribed(expected)intheProject-basedMatrixAuthorizationStrategy:1)Crowdgroup(callthegroupX_TEST)givenread-onlypermissionsforalljobsintheProject-basedMatrixAuthorizationStrategywithinthejenkinsapplicationsConfigurationGlobalSecuritylink.2)Whileconfiguringajob(project)calledJobX_test,Ichecked(true)theEnableproject-basedsecurityoptionandadded thesame crowdgroupX_TESTtotheUser/group security withalljobrelatedpermissions(read|discover|build|workspace|configure...etc.).Savedit.3)Note:Noothergroupisenabledwithinthe job project (JobX_test).4)UserXwhoispartoftheX_TESTgrouponlylogsinandcanNOTconfigure(norbuild)thejob(jobX_test).5)IFIincreasetheoverallgroups(X_TEST)permissionstobuildandconfigureintheapplicationsConfigurationGlobalSecuritylink,THENtheusercanbuildorconfigurethejob(JobX_test)!So,bottomline,applicationpermissionsoverridestheindividualproject-basedsecuritypermissions!Itshouldbetheoppositefunctionalityinwhichindividualprojectpermissionssupercedestheapplicationsssecuritysettignsforthegroup(oruser)asdescribedinthefollowinglink:https://wiki.jenkins-ci.org/display/JENKINS/2012/01/03/Allow+access+to+specific+projects+for+Users(Assigning+security+for+projects+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/d/optout.
[JIRA] [all-changes] (JENKINS-22031) Opening the 'All changes' page causes JellyTagException (caused by NumberFormatException)
Sven Claussner updated JENKINS-22031 Opening the All changes page causes JellyTagException (caused by NumberFormatException) Change By: Sven Claussner (11/Mar/14 8:25 PM) Summary: all- OpeningtheAll changes oops pagecausesJellyTagException(causedbyNumberFormatException) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [all-changes] (JENKINS-22031) Opening the 'All changes' page causes JellyTagException (caused by NumberFormatException)
Sven Claussner commented on JENKINS-22031 Opening the All changes page causes JellyTagException (caused by NumberFormatException) I'm having the same problem with Jenkins LTS (version 1.532.2). After clicking the 'All changes' link in the sidebar of a job the 'Oops' page with the stack trace opens. If the plug-in worked: would it be possible to configure it to track all changes from the latest git tag on a branch (to see what has happened since the last release?). Environment: OS: Debian Jessie (64 bit) Java: 1.7 locale: en_US timezone: Etc/UTC This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [all-changes] (JENKINS-22031) Opening the 'All changes' page causes JellyTagException (caused by NumberFormatException)
Sven Claussner edited a comment on JENKINS-22031 Opening the All changes page causes JellyTagException (caused by NumberFormatException) I'm having the same problem with Jenkins LTS (version 1.532.2). After clicking the 'All changes' link in the sidebar of a job the 'Oops' page with the stack trace opens. If the plug-in worked: would it be possible to configure it to track all changes from the latest git tag on a branch (to see what has happened since the last release?). Environment: SCM to poll: Git OS: Debian Jessie (64 bit) Java: 1.7 locale: en_US timezone: Etc/UTC This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [all-changes] (JENKINS-22031) Opening the 'All changes' page causes JellyTagException (caused by NumberFormatException)
Sven Claussner updated JENKINS-22031 Opening the All changes page causes JellyTagException (caused by NumberFormatException) Stacktrace to comment #2. Change By: Sven Claussner (11/Mar/14 8:34 PM) Attachment: 22031-Stacktrace.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22137) Broken feature: Check non-reviewed patchsets
Dilip M
created JENKINS-22137
Broken feature: Check non-reviewed patchsets
Issue Type:
Bug
Affects Versions:
current
Assignee:
rsandell
Components:
gerrit-trigger
Created:
11/Mar/14 8:52 PM
Description:
This feature "Check non-reviewed patchsets", allows checking and running un-reviewed ("approvals") patches when connection is established. If an un-reviewed patchset has been created during Jenkins server down time, will Jenkins trigger "patchset created"-event normally when connection is created.
Issues:
1. This feature, doesn't take watchdog settings into account. It re-triggers all un-reviewed patches whenever watchdog re-establishes the connection.
2. Huge no. of jobs triggered on every re-connection:
Ex: on first re-connection, 3 jobs are triggered. On second re-connection 3+3 jobs are triggered and this keeps on accumulating..
Dilip
Environment:
Jenkins ver. 1.509.4
Project:
Jenkins
Labels:
gerrit
gerrit-trigger
Priority:
Critical
Reporter:
Dilip M
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
