[JIRA] [svnmerge] (JENKINS-6851) [svnmerge-plugin] Add support for merging from upstream before building.
Hugues Chabot resolved JENKINS-6851 as Fixed [svnmerge-plugin] Add support for merging from upstream before building. Change By: Hugues Chabot (19/Jul/14 4:18 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] [p4] (JENKINS-23890) Error on next changes build
dan tran created JENKINS-23890 Error on next changes build Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: p4 Created: 19/Jul/14 2:58 AM Description: When there is a scm change in the next jenkins build ( no scheduler ATM) jenkins fails to build. I am able to produce it using workshop.perforce.coma an at my own company's depot. Subsequent manual invocation works ( provided that no new scm changes ) Here is console log Started by user anonymous Building in workspace C:\.jenkins\jobs\p4maven\workspace SCM Task: cleanup workspace: dan-laptop-p4maven-jenkins SCM Task: reverting all pending and shelved revisions. ... [list] = revert ... rm [list] | ABANDONED SCM Task: removing all non-versioned files. ... [list] = reconcile -n -a ... rm [list] SCM Task: restoring all missing and changed revisions. ... [list] = reconcile -n SCM Task: syncing files at change: 9725 ... sync C:\.jenkins\jobs\p4maven\workspace/...@9725 ... force update false ... bypass have false Parsing POMs ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com java.lang.NullPointerException at hudson.maven.MavenModuleSetBuild$1.isDescendantOf(MavenModuleSetBuild.java:284) at hudson.maven.MavenModuleSetBuild$1.(MavenModuleSetBuild.java:254) at hudson.maven.MavenModuleSetBuild.getChangeSetFor(MavenModuleSetBuild.java:247) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:701) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535) at hudson.model.Run.execute(Run.java:1732) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) project=hudson.maven.MavenModuleSet@25e0a843[p4maven] project.getModules()=[hudson.maven.MavenModule@44169c4a[p4maven/com.perforce.p4maven:p4maven][p4maven/com.perforce.p4maven:p4maven][relativePath:], hudson.maven.MavenModule@76d0e830[p4maven/com.perforce.p4maven:p4maven-dev][p4maven/com.perforce.p4maven:p4maven-dev][relativePath:p4maven-dev], hudson.maven.MavenModule@57458e21[p4maven/com.perforce.p4maven:p4maven-mojo][p4maven/com.perforce.p4maven:p4maven-mojo][relativePath:p4maven-mojo], hudson.maven.MavenModule@13328cbd[p4maven/com.perforce.p4maven:p4maven-provider][p4maven/com.perforce.p4maven:p4maven-provider][relativePath:p4maven-provider]] project.getRootModule()=hudson.maven.MavenModule@44169c4a[p4maven/com.perforce.p4maven:p4maven][p4maven/com.perforce.p4maven:p4maven][relativePath:] FATAL: null java.lang.NullPointerException at hudson.maven.MavenModuleSetBuild$1.isDescendantOf(MavenModuleSetBuild.java:284) at hudson.maven.MavenModuleSetBuild$1.(MavenModuleSetBuild.java:254) at hudson.maven.MavenModuleSetBuild.getChangeSetFor(MavenModuleSetBuild.java:247) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:701) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535) at hudson.model.Run.execute(Run.java:1732) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Here is another log at build job = A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%208.0/webapps/jenkins/WEB-INF/lib
[JIRA] [p4] (JENKINS-23889) Remove Eclipse generate files from source tree
dan tran created JENKINS-23889 Remove Eclipse generate files from source tree Issue Type: Task Assignee: Unassigned Components: p4 Created: 19/Jul/14 12:23 AM Description: this way eclipse will not complain when user try to use m2e to import the projects Those files are .project, .settings, etc Project: Jenkins Priority: Major Reporter: dan tran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23881) Too much changelog
dan tran commented on JENKINS-23881 Too much changelog looks to me it only happens for the first batch of log, subsequence checks are fine This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-5979) Subversion checkout log is very verbose
John Faith commented on JENKINS-5979 Subversion checkout log is very verbose It seems that the SubversionEventHandlerImpl in java/hudson/scm/SubversionEventHandlerImpl.java could take an option and do nothing if set. Is this method's only job to out.println() strings to look like commnad-line svn? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Adam Crews commented on JENKINS-22820 Changes are not commited when using a recent git client I can also confirm that it seems to be something related to git 1.9. I do not have this issue with git 1.7 nor 1.8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22641) Jenkins no longer kills running processes after job fails
Daniel Beck commented on JENKINS-22641 Jenkins no longer kills running processes after job fails Steven Christou: I merged your fix into a private build of 1.554.3 and verified this fixes the issue as described in my earlier comment from 09/May/14 11:42 PM. Unpatched 1.554.3 doesn't kill 'sleep' on the slave, patched does. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-23888) Add query parameter support for filtering errors based on new, resolved or unchanged
Craig Phillips created JENKINS-23888 Add query parameter support for filtering errors based on new, resolved or unchanged Issue Type: New Feature Assignee: Gregory Boissinot Components: cppcheck Created: 18/Jul/14 10:18 PM Description: For example cppcheckResult/source.All?state=new,resolved Project: Jenkins Priority: Minor Reporter: Craig Phillips This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Tom FENNELLY commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Het Shannon. Thanks for having a look at this. If you have issues you want addressed then either create a PR with a fix, or create a JIRA. If you have feedback/comments then you can email me or post them to the Jenkins dev list. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23877) With 1.572, long consoles will not display 'full' console while build is still running, only a portion
Daniel Beck updated JENKINS-23877 With 1.572, long consoles will not display 'full' console while build is still running, only a portion Change By: Daniel Beck (18/Jul/14 9:58 PM) Assignee: Praqma Support Affects Version/s: current Component/s: core Component/s: logging Component/s: build-monitor Component/s: console-tail This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-monitor] (JENKINS-23877) With 1.572, long consoles will not display 'full' console while build is still running, only a portion
Daniel Beck commented on JENKINS-23877 With 1.572, long consoles will not display 'full' console while build is still running, only a portion Apparently caused by Timestamper plugin not handling the redesign in 1.572 well, according to the mailing lists. Try disabling that plugin in the job config. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20663) file name encoding broken in zip archives
dogfood commented on JENKINS-20663 file name encoding broken in zip archives Integrated in jenkins_main_trunk #3531 [FIXED JENKINS-20663] For now, go back to using ZipOutputStream from Ant that supports setting the filename encoding (present in java.util.zip only in Java 7+). (Revision 84c76253862a2f36f813a7aa45b77d99c1616be4) Result = SUCCESS Jesse Glick : 84c76253862a2f36f813a7aa45b77d99c1616be4 Files : core/src/main/java/hudson/model/DirectoryBrowserSupport.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [project-inheritance] (JENKINS-23887) "View Full Build Flow" does not correctly order build steps
Arun Thomas created JENKINS-23887 "View Full Build Flow" does not correctly order build steps Issue Type: Bug Assignee: Unassigned Components: project-inheritance Created: 18/Jul/14 9:36 PM Description: I have one child project inheriting from two ordered parent projects. The first parent project is responsible for setting up the environment, then the child project runs, and then the second parent project is responsible for moving the artifacts and archiving them. The flow is: 1. Preparation(Parent1) 2. Build(Child) 3. Clean-up/Archive(Parent2) When the build is executed, the steps run correctly in the expected order. The minor issue, however, is in the "View Full Build Flow" list, the projects seem to be out of order. 1. Preparation 2. Clean-up/Archive 3. Build This does not affect the build process which is good. Nonetheless, it is misleading. Environment: Windows 7 64 bit Project: Jenkins Priority: Minor Reporter: Arun Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Daniel Beck edited a comment on JENKINS-23779 Layout in 1.572 is broken in IE9 Re Nexus 7, would be interesting to know what the effective resolution is. Could well try to render web pages on ~800px wide or so if possible to have them remain legible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Daniel Beck commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Shannon: Probably best to create an issue. Emailing me would be the worst option as I have nothing to do with these UI changes other than having reviewed some Re Nexus 7, would be interesting to know what the effective resolution is. Could well try to render web pages on ~800px wide or so if possible to have them remain legible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [project-inheritance] (JENKINS-23886) Last successful build artifacts not showing in the main project page.
Arun Thomas created JENKINS-23886 Last successful build artifacts not showing in the main project page. Issue Type: Improvement Assignee: Unassigned Components: project-inheritance Created: 18/Jul/14 9:27 PM Description: For a simple project, after a build runs and artifacts are created, they show up in the main project window. For inheritance projects, they do not. Please add this feature. Project: Jenkins Priority: Minor Reporter: Arun Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [lastfailureversioncolumn] (JENKINS-23885) Time duration missing for inheritance projects
Arun Thomas updated JENKINS-23885 Time duration missing for inheritance projects Change By: Arun Thomas (18/Jul/14 9:24 PM) Description: The time duration for Last Success and Last Failure are replaced by "N/A" on all the projects created with the inheritance plugin in List View mode . Component/s: project-inheritance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [lastfailureversioncolumn] (JENKINS-23885) Time duration missing for inheritance projects
Arun Thomas created JENKINS-23885 Time duration missing for inheritance projects Issue Type: Bug Assignee: Unassigned Components: lastfailureversioncolumn, lastsuccessdescriptioncolumn Created: 18/Jul/14 9:20 PM Description: The time duration for Last Success and Last Failure are replaced by "N/A" on all the projects created with the inheritance plugin. Environment: Windows 7 64-bit Project: Jenkins Priority: Trivial Reporter: Arun Thomas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr edited a comment on JENKINS-23779 Layout in 1.572 is broken in IE9 Ah, I see. That makes sense. I didn't see this with our production instance of Jenkins (still on an older version). My Nexus 7 displays it the same "new" way (with 1.572), even in landscape, which I wasn't expecting, but I do like it. Thanks for the quick response. Now I know what to expect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Daniel, if I have a trivial, small, cosmetic issue, would you like a ticket or shall I just post it here or email it to 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] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr edited a comment on JENKINS-23779 Layout in 1.572 is broken in IE9 Ah, I see. That makes sense. I didn't see this with our production instance of Jenkins (still on an older version). My Nexus 7 displays it the same "new" way, even in landscape, which I wasn't expecting, but I do like it. Thanks for the quick response. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Ah, I see. That makes sense. I don't see this with our production instance of Jenkins (still on an older version). My Nexus 7 displays it the same "new" way, even in landscape, which I wasn't expecting, but I do like it. Thanks for the quick response. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr edited a comment on JENKINS-23779 Layout in 1.572 is broken in IE9 btw, I see the same layout issues in Chrome on Android 4.4 and L, phone and tablet. Same 1.572 version of Jenkins reported here. Safari desktop and Chrome desktop are fine. I have a screen grab if you want me to post it. btw, switching to desktop mode did not make a difference in the appearance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Daniel Beck commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Shannon Kerr: It's deliberate on small screens. The switch happens at around 985px width on desktop screens for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr edited a comment on JENKINS-23779 Layout in 1.572 is broken in IE9 btw, I see the same layout issues in Chrome on Android 4.4 and L, phone and tablet. Same 1.572 version of Jenkins reported here. Safari desktop and Chrome desktop are fine. I have a screen grab if you want me to post 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] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Shannon Kerr commented on JENKINS-23779 Layout in 1.572 is broken in IE9 btw, I see the same layout issues in Chrome on Android 4.4 and L, phone and tablet. Same 1.572 version of Jenkins reported here. Safari desktop and Chrome desktop are fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) Big thx Daniel! -will try it out asap; then we'll see how we update this very issue accordingly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18935) Make Subversion plugin support Subversion 1.8
Josef Andersson edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 We just upgraded our internal systems, and I can't believe Jenkins, more than one year after it was released, doesn't have full support for Subversion 1.8.This should really be a high priority issue now, hope someone stands up to be a hero and fix the issue. It seems to be the second most popular issue regarding number of votes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20663) file name encoding broken in zip archives
SCM/JIRA link daemon resolved JENKINS-20663 as Fixed file name encoding broken in zip archives Change By: SCM/JIRA link daemon (18/Jul/14 8:46 PM) Status: In Progress 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] [core] (JENKINS-20663) file name encoding broken in zip archives
SCM/JIRA link daemon commented on JENKINS-20663 file name encoding broken in zip archives Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/DirectoryBrowserSupport.java http://jenkins-ci.org/commit/jenkins/84c76253862a2f36f813a7aa45b77d99c1616be4 Log: [FIXED JENKINS-20663] For now, go back to using ZipOutputStream from Ant that supports setting the filename encoding (present in java.util.zip only in Java 7+). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23878) Add in the GUI an option to restart master (same function as /restart url)
Daniel Beck commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) It's so simple it could well be available somewhere to teach people about writing plugins. Hence, it could be sample code. Behold: https://github.com/daniel-beck/unsafe-restart-plugin Just git clone, mvn -DskipTests verify (Maven 3.0.5+) and install the resulting target/unsafe-restart.hpi by uploading on Manage Jenkins » Manage Plugins » Advanced Note that I don't think making this particular URL accessible from a management link in core would be a good idea, as it's quite dangerous in the sense that it would kill builds in progress. Too accident prone for the default config IMO. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21977) "java.io.IOException: Failed to clean up temp dirs" because of "secret.key"
Jesse Glick commented on JENKINS-21977 "java.io.IOException: Failed to clean up temp dirs" because of "secret.key" This code should simply be disabled when Functions.getIsUnitTest(). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23884) Git/GitHub Enterprise (GHE) SCM Polling creates builds with "No Changes" when there are two similarly named branches present
M Chon
created JENKINS-23884
Git/GitHub Enterprise (GHE) SCM Polling creates builds with "No Changes" when there are two similarly named branches present
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git, git-client, github
Created:
18/Jul/14 8:16 PM
Description:
git-client plugin: 1.9.1
github plugin: 1.8
git plugin: 2.2.2
We had a project which was set up to trigger on GHE changes to the "festivus-dev" branch. We noticed that changes being pushed to the "master" branch on GHE was triggering a the "festivus-dev" branch job.
It turns out that there was a second "jdoe/blah/festivus-dev" branch that was present and it appeared to cause the polling command to think there were always changes present.
When we removed the "jdoe/blah/festivus-dev" branch from the repo, polling returned to normal. Changes checked into the "master" branch no longer triggered builds in the "festivus-dev" project.
We also noticed that when the similarly named branch ("jdoe/blah/festivus-dev") was present in the repo, it did not matter what was entered in the branch section of the project. We had a typo in there, and the build was still being triggered.
Prior to removing the similarly-named branch, we saw this in the jenkins.log:
INFO: Poked Festivus_master_CI
Jul 18, 2014 12:04:04 PM com.cloudbees.jenkins.GitHubWebHook processGitHubPayload
INFO: Poked Festivus_festivus-dev_CI
Jul 18, 2014 12:04:04 PM com.cloudbees.jenkins.GitHubWebHook processGitHubPayload
INFO: SCM changes detected in Festivus_festivus-dev_CI. Triggering #1547
Jul 18, 2014 12:04:05 PM com.cloudbees.jenkins.GitHubPushTrigger$1 run
INFO: SCM changes detected in Festivus_master_CI. Triggering #317
Jul 18, 2014 12:04:13 PM hudson.model.Run execute
And we also saw this in the polling log:
Started on Jul 18, 2014 12:04:04 PM
Using strategy: Default
[poll] Last Built Revision: Revision 652d86ee1fb4715c28902b386d32d623c15c77e9 (origin/festivus-dev)
> /usr/bin/git ls-remote -h g...@github.some.where.com:SITE/Festivus.git festivus-dev
Done. Took 0.43 sec
Changes found
And we also saw this on the command line:
git ls-remote -h g...@github.some.where.com:SITE/Festivus.git festivus-dev
849c9e7c5d497816427516146d5bd8f778897641refs/heads/jdoe/blah/festivus-dev
652d86ee1fb4715c28902b386d32d623c15c77e9refs/heads/festivus-dev
After we removed the jdoe/blah/festivus-dev branch,
INFO: Poked Festivus_master_CI
Jul 18, 2014 12:37:55 PM com.cloudbees.jenkins.GitHubWebHook processGitHubPayload
INFO: Poked Festivus_festivus-dev_CI
Jul 18, 2014 12:37:55 PM com.cloudbees.jenkins.GitHubWebHook processGitHubPayload
INFO: SCM changes detected in Festivus_master_CI. Triggering #322
Environment:
Ubuntu
Project:
Jenkins
Labels:
plugin
git
trigger
scm
polling
git-client
ghe
Priority:
Minor
Reporter:
M Chon
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Josef Andersson edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 We just upgraded our internal systems, and I can't believe Jenkins, more than one year after it was released, doesn't have full support for Subversion 1.8?.This should really be a high priority issue now, hope someone stands up to fix the issue. It seems to be the second most popular issue regarding number of votes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-23687) when running build
Jesse Glick resolved JENKINS-23687 as Not A Defect when running build Use the Credentials dropdown to set your username and password, rather than packing them into the URL. Change By: Jesse Glick (18/Jul/14 8:13 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial] (JENKINS-23687) when running build
Jesse Glick updated JENKINS-23687 when running build Change By: Jesse Glick (18/Jul/14 8:12 PM) Component/s: maven2 Component/s: active-directory This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18935) Make Subversion plugin support Subversion 1.8
Josef Andersson edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 We just upgraded our internal systems, and I can't believe Jenkins, more than one year after it was released, doesn't have full support for Subversion 1.8?.This should really be a high priority issue now. It seems to be the second most popular issue regarding number of votes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18935) Make Subversion plugin support Subversion 1.8
Josef Andersson edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 We just upgraded our internal systems, and I can't believe Jenkins, more than one year after it was released, doesn't have full support for Subversion 1.8???. How can this be for such a used version system (even though many use git also). This should really be a high priority issue now. It seems to be the second most popular issue regarding number of votes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-19828) Kill or rework auto refresh
Jesse Glick commented on JENKINS-19828 Kill or rework auto refresh Yeah I would really advocate the first option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18935) Make Subversion plugin support Subversion 1.8
Josef Andersson edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 We just upgraded our internal systems, and I can't believe Jenkins, more than one year after it was released, doesn't have full support for Subversion 1.8???. How can this be for such a used version system (even though many use git also). This should really be a high priority issue now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18935) Make Subversion plugin support Subversion 1.8
Josef Andersson commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 We just upgraded our internal systems, and I can't belive Jenkins, more than one year after it was released, doesn't have full support for Subversion 1.8. How can this be for such a used versioning system (even though many use git also9. This should be a high priority issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) I guess it would; you mean "simple" above right Daniel? (rather than "sample") This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20663) file name encoding broken in zip archives
Jesse Glick started work on JENKINS-20663 file name encoding broken in zip archives Change By: Jesse Glick (18/Jul/14 7:55 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Daniel Beck commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) A plugin that does that is essentially sample code. Would one resolve this issue 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] [core] (JENKINS-18435) Navigating back, then forward, from a job configuration causes loss of config data
Jesse Glick commented on JENKINS-18435 Navigating back, then forward, from a job configuration causes loss of config data I suspect the most appropriate fix is just to add some JS to block the back/forward buttons while on such a 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] [core] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller edited a comment on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) (Working with Christian) -No; this issue is really about an admin button doing just like what the myJenkins/restart url does. So I just updated the component (set it to core); please let me know if that is still wrong though =) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) (Working with Christian) -No; this issue is really about an admin button doing just like what the myJenkins/restart url does. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18435) Navigating back, then forward, from a job configuration causes loss of config data
Jesse Glick commented on JENKINS-18435 Navigating back, then forward, from a job configuration causes loss of config data Lazy-loaded form fragments are added to the DOM by some _javascript_ hooks. Probably these are being run on initial page load but not when revisiting a page, and the browser is throwing out the modified DOM. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23774) Jenkins ver. 1.572 has an exception in hudson.diagnosis.ReverseProxySetupMonitor.
Jesse Glick resolved JENKINS-23774 as Cannot Reproduce Jenkins ver. 1.572 has an exception in hudson.diagnosis.ReverseProxySetupMonitor. Change By: Jesse Glick (18/Jul/14 7:43 PM) Status: Reopened Resolved Resolution: Cannot 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] [core] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Marco Miller updated JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) Change By: Marco Miller (18/Jul/14 7:42 PM) Component/s: core Component/s: safe-restart Component/s: saferestart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23686) Trigger "Build after other projects" does not work
Jesse Glick resolved JENKINS-23686 as Fixed Trigger "Build after other projects" does not work Ought to work in next version of the plugin. (Did not have time to write a test to prove it.) Change By: Jesse Glick (18/Jul/14 7:41 PM) Status: In Progress 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] [conditional-buildstep] (JENKINS-22544) Conditional BuildStep Plugin
Dominik Bartholdi edited a comment on JENKINS-22544 Conditional BuildStep Plugin conditional-buildstep does not implement any conditions, there are currently two separate plugins which provide conditions. So this feature request should go into one of these: run-condition or run-condition-extras This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22544) Conditional BuildStep Plugin
Dominik Bartholdi updated JENKINS-22544 Conditional BuildStep Plugin conditional-buildstep does not implement any conditions, there are currently two separate plugins which provide conditions. So this feature request should go into one of these. Change By: Dominik Bartholdi (18/Jul/14 7:35 PM) Component/s: run-condition Component/s: run-condition-extras This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [repository-connector] (JENKINS-17541) target directory does not expand token macro parameters
Dominik Bartholdi resolved JENKINS-17541 as Fixed target directory does not expand token macro parameters fixed with 0.9.0 Change By: Dominik Bartholdi (18/Jul/14 7:04 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] [repository-connector] (JENKINS-17541) target directory does not expand token macro parameters
Dominik Bartholdi assigned JENKINS-17541 to Dominik Bartholdi target directory does not expand token macro parameters Change By: Dominik Bartholdi (18/Jul/14 7:03 PM) Assignee: Dominik Bartholdi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-21640) scm-sync-configuration plugin doesn't work anymore with Subversion Plugin 2.0
alex mattern commented on JENKINS-21640 scm-sync-configuration plugin doesn't work anymore with Subversion Plugin 2.0 I am having the same issue with Subversion Plugin 2.4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector] (JENKINS-18040) Unable to install repository-connector-plugin
Dominik Bartholdi commented on JENKINS-18040 Unable to install repository-connector-plugin do you still have this issue? do all other plugin work? do you have the token-macro plugin 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] [perforce] (JENKINS-20927) FATAL: <${NODE_NAME}>: Found unresolved macro at '${NODE_NAME}'
pixman20
commented on JENKINS-20927
FATAL: <${NODE_NAME}>: Found unresolved macro at '${NODE_NAME}'
Is there an expected date when this will be released in the perforce plugin? (i.e. 1.3.28)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [managed-scripts] (JENKINS-16335) Managed Script calls other managed script
Dominik Bartholdi commented on JENKINS-16335 Managed Script calls other managed script In the buildstep, you have the chance to give an individual name for each script with the field "Target", so you don't need to know the internal name to refer it. This allows you to use a different name for the same file in every step. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23883) GERRIT_BRANCH not honoured in gerrit trigger config
Ali Al-Shabibi created JENKINS-23883 GERRIT_BRANCH not honoured in gerrit trigger config Issue Type: Bug Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 18/Jul/14 5:46 PM Description: Under Gerrit Trigger config -> Gerrit Project -> Branches using $GERRIT_BRANCH does not work. This would be useful so that we not need to change our Jenkins configuration when we rename/change branches. JENKINSVERSION: 1.559 System Properties Name ↓ Value awt.toolkit sun.awt.X11.XToolkit executable-war /usr/share/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / guice.disable.misplaced.annotation.check true hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/share/jenkins/jenkins.war java.class.version 51.0 java.endorsed.dirs /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-7-openjdk-amd64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.7.0_51-b00 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_51 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.45-b08 jna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true org.apache.commons.logging.Log org.apache.commons.logging.impl.Jdk14Logger os.arch amd64 os.name Linux os.version 3.2.0-25-virtual path.separator : securerandom.source file:/dev/./urandom sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/netx.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/plugin.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/rhino.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/lib/jfr.jar:/usr/lib/jvm/java-7-openjdk-amd64/jre/classes sun.boot.library.path /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.font.fontmanager sun.awt.X11FontManager sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1 sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown svnkit.http.methods Digest,Basic,NTLM,Negotiate svnkit.ssh2.persistent false user.country US user.dir / user.home /var/lib/jenkins user.language en user.name jenkins user.timezone America/Los_Angeles Environment Variables Name ↓ Value _ /usr/bin/daemon HOME /var/lib/jenkins JENKINS_HOME /var/lib/jenkins LANG en_US.UTF-8 LOGNAME jenkins MAIL /var/mail/jenkins MAVEN_OPTS -Xmx1024m -XX:MaxPermSize=128m PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games PWD /var/lib/jenkins SHELL /bin/bash SHLVL 1 TERM xterm-256color USER jenkins XDG_SESSION_COOKIE 4fc027771bffc43dd60e43dc016d90ef-1398202665.418669-1357825637 Plugins Name ↓ Version Enabled Pinned analysis-collector 1.41 true false analysis-core 1.56 true false
[JIRA] [managed-scripts] (JENKINS-20964) Option of disable the call to a managed script
Dominik Bartholdi commented on JENKINS-20964 Option of disable the call to a managed script Although I see the value in this, I don't think we should edd this functionality to every singel plugin, but rather add something to core to enable something like this. Because at the end this requirement could be added toevery single 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] [managed-scripts] (JENKINS-22918) Add option to output executed commands to job console
Dominik Bartholdi commented on JENKINS-22918 Add option to output executed commands to job console the only reason why this works in the "normal" shell build step is when you do not define a shebang on the first line. If you don't do that, then every single line in the textbox is executed on its own an therefore the execution can be logged. If you add a shebang, then the full textbox is treated as a script (as this plugin does) and then you don't get the debug output either. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-monitor] (JENKINS-23877) With 1.572, long consoles will not display 'full' console while build is still running, only a portion
Jesper Jensen commented on JENKINS-23877 With 1.572, long consoles will not display 'full' console while build is still running, only a portion Same seen on Windows 2008 servers, also noted this during the build that the update was slow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ec2] (JENKINS-23850) PATCH: EC2-plugin always starting new slaves instead of restarting existing
SCM/JIRA link daemon commented on JENKINS-23850 PATCH: EC2-plugin always starting new slaves instead of restarting existing Code changed in jenkins User: Andrew Coulton Path: src/main/java/hudson/plugins/ec2/SlaveTemplate.java http://jenkins-ci.org/commit/ec2-plugin/14d537a08728f0baef88ed2d33e73696f681433f Log: [FIXED JENKINS-23850] Workaround AWS bug that hides stopped slaves Use instance.group-name instead of group-name as the describeInstances filter when searching for stopped slaves to restart. Some EC2 regions are incorrectly returning empty describeInstances results when the group-name filter is used. This causes jenkins to start new slaves instead of restarting stopped instances. instance.group-name is functionally identical and seems to work consistently. https://issues.jenkins-ci.org/browse/JENKINS-23850 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ec2] (JENKINS-23850) PATCH: EC2-plugin always starting new slaves instead of restarting existing
SCM/JIRA link daemon resolved JENKINS-23850 as Fixed PATCH: EC2-plugin always starting new slaves instead of restarting existing Change By: SCM/JIRA link daemon (18/Jul/14 5:19 PM) Status: In Progress 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] [safe-restart] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Daniel Beck commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) The funny thing is, the components you chose (incorrectly) for this issue are actually plugins that do the job. (`/safeRestart` only restarts once nothing's running anymore, hence being safer) https://wiki.jenkins-ci.org/display/JENKINS/SafeRestart+Plugin Does the existence of this plugin suffice to resolve this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23881) Too much changelog
dan tran updated JENKINS-23881 Too much changelog Change By: dan tran (18/Jul/14 5:09 PM) Description: Click on 'changes' button takes a long time, and the final outputs contains every thing starting for from root depot path ( ie //mydepot ) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20600) Build issues when folder name (or job name) contains spaces
Jesse Glick updated JENKINS-20600 Build issues when folder name (or job name) contains spaces Change By: Jesse Glick (18/Jul/14 5:03 PM) Labels: folders space Component/s: cloudbees-folder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20600) Build issues when folder name (or job name) contains spaces
Jesse Glick resolved JENKINS-20600 as Not A Defect Build issues when folder name (or job name) contains spaces As designed. Any Maven plugins (etc.) which do not work when run inside a project path containing a space are simply broken. (Has no one ever tried running them inside C:\Documents and Settings\Poor Spacey User\My Maven Projects?) Change By: Jesse Glick (18/Jul/14 5:05 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-parameter] (JENKINS-23473) empty tags / revisions list when using Folders - NullPointerException - getParentProject()
Jesse Glick updated JENKINS-23473 empty tags / revisions list when using Folders - NullPointerException - getParentProject() Change By: Jesse Glick (18/Jul/14 5:02 PM) Labels: folders Component/s: cloudbees-folder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23882) Long build startup
dan tran created JENKINS-23882 Long build startup Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: p4 Created: 18/Jul/14 4:53 PM Description: for my build, the initial scm activities seem to take a long time ~2-3 minute even with no changes Started by user anonymous Building in workspace C:\.jenkins\jobs\dan-maven\workspace SCM Task: cleanup workspace: dan-laptop-maven-jenkins SCM Task: reverting all pending and shelved revisions. ... [list] = revert ... rm [list] | ABANDONED SCM Task: removing all non-versioned files. ... [list] = reconcile -n -a ... rm [list] Project: Jenkins Priority: Major Reporter: dan tran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23881) Too much changelog
dan tran updated JENKINS-23881 Too much changelog Change By: dan tran (18/Jul/14 4:39 PM) Summary: Tool Too much changelog This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23881) Tool much changelog
dan tran created JENKINS-23881 Tool much changelog Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: p4 Created: 18/Jul/14 4:38 PM Description: Click on 'changes' button takes a long time, and the final outputs contains every thing starting for root depot Environment: windows Project: Jenkins Priority: Major Reporter: dan tran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [windows-slaves] (JENKINS-23880) slave.jar should update itself when Jenkins is updated
boris ivan created JENKINS-23880 slave.jar should update itself when Jenkins is updated Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: windows-slaves Created: 18/Jul/14 4:25 PM Description: slave.jar should update itself when Jenkins is updated. I have a large qty of remote build agents, and when we see problems, we never know if the outdated slave.jar is relevant or not. This should be changed once and for all so that it detects the change and auto updates itself when the Jenkins server is updated. Competing CI servers have had this as basic functionality for years, it would be great if Jenkins supported the same. Environment: any Project: Jenkins Priority: Major Reporter: boris ivan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cloudbees-folder] (JENKINS-23879) CLI command to move item(s) into a folder
Jesse Glick created JENKINS-23879 CLI command to move item(s) into a folder Issue Type: Improvement Assignee: Jesse Glick Components: cloudbees-folder Created: 18/Jul/14 4:03 PM Description: Currently only have a REST option. Would also be useful to specify multiple items to move into one folder in bulk. Project: Jenkins Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-monitor] (JENKINS-23877) With 1.572, long consoles will not display 'full' console while build is still running, only a portion
boris ivan created JENKINS-23877 With 1.572, long consoles will not display 'full' console while build is still running, only a portion Issue Type: Bug Affects Versions: current Assignee: Praqma Support Components: build-monitor, console-tail, logging Created: 18/Jul/14 3:40 PM Description: Our jenkins jobs yield hundreds of pages of output. New in 1.572, if we look at 'full' console *while the build is in progress*, only a portion is shown, and we get the spinning icon at bottom of console but nothing else comes. Interestingly, when the job is finished, I can click on the 'full' console and it works. It is only during the time that the job is running, that the 'full' console only shows a portion. The portion that it shows is not the latest, either. Specifically, while the job is running, if we click on 'full' console, I'll see the first pages from the beginning of the build, then it will be stuck. But if we click on 'view console' (NOT the full console), we can see the most recent set of logs (i.e. 'tail'). This problem did not occur in 1.571. Environment: Webserver and build agent on separate Windows 2012 machines. Browsers used: FF and Chrome -- same result. (and did not occur in 1.571) Project: Jenkins Priority: Major Reporter: boris ivan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [safe-restart] (JENKINS-23878) Add in the GUI an option to restart master (same function as /restart url)
Christian Lague created JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: safe-restart, saferestart Created: 18/Jul/14 3:40 PM Description: Add in the GUI option to restart master (same function as /restart url) Suggestion: combine it with a new restart button and the Prepare for Shutdown option into a new submenu under Manage Jenkins. Project: Jenkins Priority: Minor Reporter: Christian Lague This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dashboard-view] (JENKINS-23876) Unable to add a pipeline view in a nested dashboard view
Raj vasikarla
updated JENKINS-23876
Unable to add a pipeline view in a nested dashboard view
Change By:
Raj vasikarla
(18/Jul/14 3:35 PM)
Description:
After
I've installed
the
last updates
dashboard plugin and created a new view for
the
portlet throw the next error:{noformat}WARNING: Caught exception evaluating: it
dashboard
.
getUnstableJobs(jobs) in /. Reason: java.lang.ClassCastException: hudson.maven.MavenModule cannot be cast
In the new view i was able
to
hudson
add a "dasbboard view" which consists of a "pipeline view" and other portlets
.
model
Things are working fine until now
.
TopLev elItemjava.lang.ClassCastException: hudson.maven.MavenModule cannot be cast
Instead of over populating my jenkins main view with too many tabs i decide
to
hudson.model.TopLevelItemat hudson.plugins.
have nested views, and within the nested
view
.
i started creating
dashboard
views
.
core
The capability of adding the pipeline view as one of the portlet is not available when i go with nested view
.
UnstableJobsPortlet.getUnstableJobs(UnstableJobsPortlet.java:44)at hudson.plugins.
The pipeline portlet
view
is only available when i go with the main view
.
dashboard.core.UnstableJobsPortlet.getUnstableJobs(UnstableJobsPortlet.java:46)
at sun.reflect.GeneratedMethodAccessor597.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25){noformat}Seeing
Hope
the
conde and the class hierarchy
above is clear
,
I think that
if not please feel free to let me know i'll add more info to
the
correct method signature for getUnstableJobs is:{code} public Collection getUnstableJobs(Collection allJobs) { ArrayList unstableJobs = new ArrayList(); for (Item item : allJobs) {
above
.
... } }{code}With this change I think that we avoid the error.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [dashboard-view] (JENKINS-23876) Unable to add a pipeline view in a nested dashboard view
Raj vasikarla
created JENKINS-23876
Unable to add a pipeline view in a nested dashboard view
Issue Type:
Bug
Affects Versions:
current
Assignee:
Peter Hayes
Components:
dashboard-view
Created:
18/Jul/14 3:33 PM
Description:
After the last updates the portlet throw the next error:
WARNING: Caught exception evaluating: it.getUnstableJobs(jobs) in /. Reason: java.lang.ClassCastException: hudson.maven.MavenModule cannot be cast to hudson.model.TopLev elItem
java.lang.ClassCastException: hudson.maven.MavenModule cannot be cast to hudson.model.TopLevelItem
at hudson.plugins.view.dashboard.core.UnstableJobsPortlet.getUnstableJobs(UnstableJobsPortlet.java:44)
at hudson.plugins.view.dashboard.core.UnstableJobsPortlet.getUnstableJobs(UnstableJobsPortlet.java:46)
at sun.reflect.GeneratedMethodAccessor597.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
Seeing the conde and the class hierarchy, I think that the correct method signature for getUnstableJobs is:
public Collection getUnstableJobs(Collection allJobs) {
ArrayList unstableJobs = new ArrayList();
for (Item item : allJobs) {
}
}
With this change I think that we avoid the error.
Environment:
Jenkins: 1.572
SO: Ubuntu 12.04 LTS
Project:
Jenkins
Priority:
Major
Reporter:
Raj vasikarla
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-23514) Deadlock in Xstream at Jenkins startup
Jesse Glick resolved JENKINS-23514 as Duplicate Deadlock in Xstream at Jenkins startup Yeah it is a duplicate—this is one possible symptom. Change By: Jesse Glick (18/Jul/14 3:24 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] [parameterized-trigger] (JENKINS-22600) Sub-projects appeared as "Static" and "Other executed recently" at job main page
Vitaliy Baskoff commented on JENKINS-22600 Sub-projects appeared as "Static" and "Other executed recently" at job main page Affects only upstream jobs which are paced in the Jenkins root (https://ci.org/job/A) and trigger jobs which also paced in the Jenkins root (https://ci.org/job/B) As workaround I have moved all downstream jobs into folders(https://ci.org/job/QA/B) and "Other executed recently" items disappeared This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23179) git pre-merge fails with matrix project
Marshall Galbraith edited a comment on JENKINS-23179 git pre-merge fails with matrix project I created a unit test that reproduces the problem, and created a fix. Both are available with this pull request: https://github.com/jenkinsci/git-plugin/pull/235 The fix does not modify the behavior for regular projects, or matrix projects that do not use the git pre-merge feature. The current implementation always uses the decorated revision for the matrix axes. However, the decorated revision only exists in the workspace of the cloned parent build, and does not exist in the cloned workspace for the axes. This fix causes the axes to use the marked revision, rather than the decorated one. The axes then subsequently decorate the marked revision. The only other way that I could think of fixing this problem would require the axes to pull the decorated revision from the parent workspace. However, this would cause all kinds of headaches in particular if working with multiple distributed slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23179) git pre-merge fails with matrix project
Marshall Galbraith edited a comment on JENKINS-23179 git pre-merge fails with matrix project I created a unit test that reproduces the problem, and created a fix. Both are available with this pull request: https://github.com/jenkinsci/git-plugin/pull/235 The fix does not modify the behavior for regular projects, or matrix projects that do not use the git pre-merge feature. The current implementation always uses the decorated revision for the matrix axes. However, the decorated revision only exists in the workspace of the cloned parent build, and does not exist in the cloned workspace for the axes. This fix causes the axes to use the marked revision, rather than the decorated one. The axis then subsequently decorate the marked revision. The only other way that I could think of fixing this problem would require the axes to pull the decorated revision from the parent workspace. However, this would cause all kinds of headaches in particular if working with multiple distributed slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23179) git pre-merge fails with matrix project
Marshall Galbraith updated JENKINS-23179 git pre-merge fails with matrix project Change By: Marshall Galbraith (18/Jul/14 2:38 PM) Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23875) Ability to pass reference repo recursively
Christian Lague created JENKINS-23875 Ability to pass reference repo recursively Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: git Created: 18/Jul/14 2:26 PM Description: Ability to pass reference repo recursively. Right now we have to do submodule update outside of Git plugin as it does not understand reference repo parameter for the submodules, i.e. if the reference repo is passed to the plugin it is not used when cloning/fetching from the submodules A work around is to do git command in the build instead of defining it in the Jenkins UI git section. This do not introduce problem except it is error prone. Project: Jenkins Priority: Major Reporter: Christian Lague This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23791) Wrong timestamp retrieved from git ChangeSet
Dmitry Skorbovenko commented on JENKINS-23791 Wrong timestamp retrieved from git ChangeSet I have just sent pull request https://github.com/jenkinsci/git-plugin/pull/242 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ec2] (JENKINS-20290) IAM Policy on the web site isn't sufficient for the plugin to run
John Dyer commented on JENKINS-20290 IAM Policy on the web site isn't sufficient for the plugin to run I seem to be getting the same thing but my IAM role I assigned has power user access. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [jclouds-jenkins] (JENKINS-23874) Unable to check the image id please check if the credentials you provided are correct
sandy thomas
created JENKINS-23874
Unable to check the image id please check if the credentials you provided are correct
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
jclouds-jenkins
Created:
18/Jul/14 2:11 PM
Description:
When using jCloud plugin after entering the respected fields like identity & secret,test validation passes. but when specifying the image template with id and cross checking against it ends up showing error text as in summary.
However after saving the config and trying to provision vm will end up in below stack trace
Caused by: org.jclouds.http.HttpResponseException: command: GET http://xyz.com/client/api?response=json&command=listProjects&listAll=true&account=abc&domainid=dc0314d4-09aa-4e8f-8a54-419ecf344635 HTTP/1.1 failed with response: HTTP/1.1 531 null; content: [{ "listprojectsresponse" : {"uuidList":[],"errorcode":531,"cserrorcode":4365,"errortext":"Can't list domain id= 2 projects; unauthorized"} }]
at org.jclouds.cloudstack.handlers.CloudStackErrorHandler.handleError(CloudStackErrorHandler.java:50)
Project:
Jenkins
Priority:
Major
Reporter:
sandy thomas
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-23873) extend changeMerged event with merge commit
George Young created JENKINS-23873 extend changeMerged event with merge commit Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 18/Jul/14 1:44 PM Description: as found here: https://bugs.launchpad.net/openstack-ci/+bug/929723 and http://code.google.com/p/gerrit/issues/detail?id=2785 The changeMerged event provides the merged patchset information of a review/change that was merged to its destination branch. Can this event be extended, or a new event created to include the SHA of the merge commit that was written/exists on the destination branch so that an event listener, like the Jenkins Gerrit Trigger Plugin, could fetch the specified branch and rewind to the specific SHA for a per-review-on-the-branch build trigger? The refUpdated event has essentially a rev-list of individual commits with no indication of which were added as a result of review merge Project: Jenkins Priority: Major Reporter: George Young This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23873) extend changeMerged event with merge commit
George Young updated JENKINS-23873 extend changeMerged event with merge commit Change By: George Young (18/Jul/14 1:44 PM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-23823) Trend graph should have percentage value (too)
Nicolas Marcotte commented on JENKINS-23823 Trend graph should have percentage value (too) Both line should be visible too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
Erik Riemers commented on JENKINS-22820 Changes are not commited when using a recent git client Same issue here.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-12540) An option flag in the Jenkins Configuration for "trigger builds even if unstable"
Daniel Beck updated JENKINS-12540 An option flag in the Jenkins Configuration for "trigger builds even if unstable" OK, now I understand the report. Thanks for the response! Reassigning issue to the Maven plugin. Change By: Daniel Beck (18/Jul/14 1:16 PM) Component/s: maven Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12540) An option flag in the Jenkins Configuration for "trigger builds even if unstable"
Gian Mario Contessa commented on JENKINS-12540 An option flag in the Jenkins Configuration for "trigger builds even if unstable" Hi Daniel, we have a multi module maven project that at the moment build all the code in one go using only the configured Maven modules from a parent pom file. Long ago I tried to build each module separately with Jenkins, knowing that it reads and follows the Maven dependency tree. It works well for a normal, non testing build, but when running unit tests, the build chain breaks if one of the upper dependencies is marked as "unstable". In this case we had multiple times where the unit tests were not running at all in all the sub modules, and went back to run the build all in one single project. using the post step build is not an option as the maintenance would be so much and manual to render the effort counterproductive This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23791) Wrong timestamp retrieved from git ChangeSet
Dmitry Skorbovenko
commented on JENKINS-23791
Wrong timestamp retrieved from git ChangeSet
Hi, I have checked code. the issue is in GitChangeSet:isoDateFormat method. git tool returns the time in seconds but java Date class requires milliseconds - so just multiply time by 1000
fix:
/** Convert to iso date format if required */
private String isoDateFormat(String s) {
if (s.length() == 25 /* already in ISO 8601 */) return s;
// legacy mode
int i = s.indexOf(' ');
long time = Long.parseLong(s.substring(0,i));
return FastDateFormat.getInstance(ISO_8601).format(new Date(time * 1000)) + s.substring(i);
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-23409) Crashing api at depth > 0
Craig Phillips commented on JENKINS-23409 Crashing api at depth > 0 I am seeing this as well. I have had to work around the issue by scraping the HTML from the consoleFull output and picking out the anchors and spans associated with failures. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [credentials] (JENKINS-23872) Jenkins users disappeared!
e. cresta created JENKINS-23872 Jenkins users disappeared! Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Components: credentials Created: 18/Jul/14 12:55 PM Description: After upgrade from 1.563 to 1.572, all my Jenkins userid in Uppercase are no longer visible and cannot log in (eg : userid like UL11244) . I can see only user in lowercase (admin). I use Jenkins own database. As a workaround, I have to rename directory in JENKINS_HOME/users folder, eg: mv /build/hudson/users/UL11251 /build/hudson/users/ul11251 and then modify config.xml to find and replace all UL11251 in ul11251. In this case user ul11251 can log in and work. But since I have lot of users, I have to rollback to 1.563. Thanks Due Date: 18/Jul/14 12:00 AM Environment: Linux redhat Server release 5.8 64 bit Apache Tomcat 6.0.18 Jenkins 1.563 Project: Jenkins Priority: Critical Reporter: e. cresta This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23871) Play-back Gerrit events which happened during a Jenkins downtime
Christian Lague created JENKINS-23871 Play-back Gerrit events which happened during a Jenkins downtime Issue Type: Improvement Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 18/Jul/14 12:40 PM Description: Use case: Jenkins become unavailable. In the meantime, there are a number of Gerrit events occurring which are missed. When Jenkins restarts, these missed events should be replayed. E.g. a designer submits a patch set during a Jenkins outage. Since Gerrit trigger is not firing, the patch will never be verified and merged, or will need to be done manually. There is a facility in Gerrit trigger to "manually" query events during a given period, but this will not scale as need to be done for each job. The requirement would be: 1. It shall be possible to replay all "missing" Gerrit events for a given Jenkins master following a downtime of the master 2. It shall be possible to have #1 trigger automatically i.e. that when Jenkins restart, all events that happened since last time it ran will be replayed. 3. It shall be possible to trigger #1 manually. This capability shall be available only to the administrator role Project: Jenkins Priority: Major Reporter: Christian Lague This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20531) Retry count not working in Git plugin 2.0
Christian Lague commented on JENKINS-20531 Retry count not working in Git plugin 2.0 We (Ericsson) would like to support that issue. We have a quite large Gerrit infrastructure that require replication and fetch from mirrors only. In that context it happen that the super project is replicated prior to the submodules, thus causing fail checkout. The SCM checkout retry option is not working in this specific case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ant] (JENKINS-23865) Jenkins Jobs Hanging while running junit tests
Daniel Beck commented on JENKINS-23865 Jenkins Jobs Hanging while running junit tests To clarify, the same issue does not occur on the same machine, same user, same environment, when run from outside 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.
