[JIRA] [dashboard-view] (JENKINS-25039) javax.servlet.ServletException occurs while Editing and saving Sectioned View configuration in Jenkins Version 1.559
Ramakrishna Bejawar updated JENKINS-25039 javax.servlet.ServletException occurs while Editing and saving Sectioned View configuration in Jenkins Version 1.559 Change By: Ramakrishna Bejawar (08/Oct/14 7:04 AM) Summary: Edit view javax.servlet.ServletException occurs while Editing and save changes does'nt work some times saving Sectioned View configuration in Jenkins Version - 1. 599 559 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25039) Edit view and save changes does'nt work some times in Jenkins Version-1.599
Ramakrishna Bejawar created JENKINS-25039 Edit view and save changes does'nt work some times in Jenkins Version-1.599 Issue Type: Bug Assignee: Peter Hayes Attachments: SectinedView_Error_Logs_from__Ramakrishna.txt Components: dashboard-view, sectioned-view Created: 08/Oct/14 7:03 AM Description: javax.servlet.ServletException occurs while Editing and saving Sectioned View configuration. Error Log attached with the ticket. Environment: OS: Red Hat Enterprise Linux Server release 6.2 (Santiago) java version "1.7.0" Jenkins Version 1.559 Project: Jenkins Labels: jenkins sectioned-view Priority: Major Reporter: Ramakrishna Bejawar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [walldisplay] (JENKINS-25022) Walldisplay is not shown, if the project has the same name the current view
SCM/JIRA link daemon commented on JENKINS-25022 Walldisplay is not shown, if the project has the same name the current view Code changed in jenkins User: Pelle Pelster Path: src/main/webapp/walldisplay.js http://jenkins-ci.org/commit/walldisplay-plugin/14716b773144cd82a56ca8599ae612497118c35b Log: JENKINS-25022 Walldisplay is not shown, if the project has the same name the current view This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25040) Unnecessary SCM actions in multi-configuration job on master
Alexander Ziller created JENKINS-25040 Unnecessary SCM actions in multi-configuration job on master Issue Type: Improvement Assignee: rsandell Components: core, multi-slave-config, multijob-plugin Created: 08/Oct/14 7:43 AM Description: I have a multi-configuration Job that has to run on multiple nodes at the same time. I want the job to checkout from CVS, then do build steps on the CVS content. Current situation -Multiple slave nodes are assigned to the job. -Master is NOt assigned to the job. -CVS is accessed by pserver CVSROOT and defined in the job configuration Current behaviour -Master checks out from CVS, then delegates job to the slave nodes, which also do a CVS checkout, then do the job Expected behaviour -Master immediately delegates to the assigned nodes without doing a CVS chekout first. Since the master is not an assigned node of the job, it is not supposed to do anything concerning the job. Environment: Jenkins 1.583, Windows OS Project: Jenkins Priority: Minor Reporter: Alexander Ziller This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25039) javax.servlet.ServletException occurs while Editing and saving Sectioned View configuration in Jenkins Version 1.559
Ramakrishna Bejawar updated JENKINS-25039 javax.servlet.ServletException occurs while Editing and saving Sectioned View configuration in Jenkins Version 1.559 Change By: Ramakrishna Bejawar (08/Oct/14 8:07 AM) Attachment: SectionedView_Error_Logs_from__Ramakrishna.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-24965) Personal builds can encounter deadlock when fetching source
James Clark commented on JENKINS-24965 Personal builds can encounter deadlock when fetching source Hi Heather, thanks for the reply. We're using the 4.0.3 version of the toolkit. There is only ever one instance of a job running at one time. I'm not sure whether the checkout finished or not. I believe the console output in Jenkins keeps saying that's it's fetching the source. I'll have to confirm next time I see it happen. I'm not too sure on the meaning of sandbox here but the when starting a personal build, each user selects their workspace with changes checked in for the build to use. In this respect, each repository workspace is different. All personal builds use the same job workspace as configured in Jenkins, but as there is only one job running at a time, there shouldn't be any overwriting going on. The jobs run on the Jenkins master. Thanks! JC This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
LETS BE GOOD FRIEND
LETS BE GOOD FRIEND Friendship is sharing with laugher & Happiness!Friendship is helping each other when it seems there's no hope!Friendship is taking time to encourage one another! In Friendship you and I can learn from each other also offer good advice to our selves especially in some circumstances that is beyond our control. There's a miracle called "Friendship." Oh what a miracle in just keeping it real! The "Friendship" dwells way down deep in the heart and soul of a person or individuals. You don't know how this "Friendship" happens. It just happens so soulfully. It is a light from the "Friendship" that provides sunlight to the soul whenever it happens. But you know and you have to recognize the gift from above. My name is Juliet Wake from United States of America , hope to tell you more about myself as soon as I hear from you. cya! juliet -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25041) SVN: string index out of range: -1 at hudson.scm.DirAwareSVNXMLLogHandler.sendToHandler(DirAwareSVNXMLLogHandler.java:121)
Stefan Puiu created JENKINS-25041 SVN: string index out of range: -1 at hudson.scm.DirAwareSVNXMLLogHandler.sendToHandler(DirAwareSVNXMLLogHandler.java:121) Issue Type: Bug Assignee: Unassigned Attachments: plugins.xml Components: subversion Created: 08/Oct/14 9:03 AM Description: We're building multiple projects checked out of SVN using Jenkins. Every once in a while they fail with this exception: FATAL: String index out of range: -1 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 For one particular project, which is quite small and involves checking out one item, half of the builds fail. Even when this exception is raised, the checkout seems successful (I compare the output to successful builds). Maybe it fails while trying to determine the list of changes? The checkout strategy is 'always check out a fresh copy'; for build triggers, I've set 'poll SCM' @midnight and 'trigger remotely'. IIRC the exception also happens for builds triggered remotely. Let me know if you need more info. Both the SVN and Jenkins servers are internal to the company. I've attached the XML file I get by querying the plugin list using 'http:///pluginManager/api/xml?depth=1' in a browser (based on http://stackoverflow.com/questions/9815273/how-to-get-a-list-of-installed-jenkins-plugins-with-name-and-version-pair) Checking out at revision '2014-10-08T03:18:06.153 -0500' A License AUbuild_deb.sh A debug [...] A test/python/gb_json_tester.py A test/python/test_simpleCmd.py A test/python/test_cmds.py U. At revision 126377 FATAL: String index out of range: -1 java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1875) at hudson.scm.DirAwareSVNXMLLogHandler.sendToHandler(DirAwareSVNXMLLogHandler.java:121) at hudson.scm.DirAwareSVNXMLLogHandler.handleLogEntry(DirAwareSVNXMLLogHandler.java:83) at org.tmatesoft.svn.core.internal.wc2.compat.SvnCodec$7.receive(SvnCodec.java:167) at org.tmatesoft.svn.core.internal.wc2.compat.SvnCodec$7.receive(SvnCodec.java:164) at org.tmatesoft.svn.core.wc2.SvnReceivingOperation.receive(SvnReceivingOperation.java:78) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.handleLogEntry(SvnRemoteLog.java:199) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.logImpl(SVNRepositoryImpl.java:827) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1035) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:179) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:118) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:735) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:873) at hudson.model.AbstractProject.checkout(AbstractProject.java:1254) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:624) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:530) at hudson.model.Run.execute(Run.java:1740) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:234) Environment: Jenkins 1.575
[JIRA] [build-pipeline] (JENKINS-22665) BuildPipelineView.MyUserIdCause stores entire hudson.model.User
Kim Nyhjem commented on JENKINS-22665 BuildPipelineView.MyUserIdCause stores entire hudson.model.User This is a serious security breach. It not only affects config.xml, but also build.xml's, which means a lot of those dangerous (and very bulky if you have a lot of nested views) elements out there. Please upvote. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clearcase] (JENKINS-25042) Updating a snapshot view triggers a race condition on fast machines
Dirk Kuypers created JENKINS-25042 Updating a snapshot view triggers a race condition on fast machines Issue Type: Bug Assignee: Vincent Latombe Components: clearcase Created: 08/Oct/14 9:11 AM Description: We are currently installing some new and fast hardware and run into snapshot view update problems like below. I can reproduce this on the command line by adding the cleartool endview and cleartool catcs into a batch script, the update almost always fails. If I add a pause of 500 ms between the two commands, everything works reliably. We even see the error on our older and slower machines, but very sporadically. So my question is: Ist this repeated cleartool endview really necessary? Or is it possible to add some (configurable) wait/sleep inbetween the commands? At the moment the new and fast hardware is not usable with the ClearCase plugin for us because updates almost always fail. 10:43:55 [Snapshots] $ cleartool endview -server view_name 10:43:55 10:43:55 [Snapshots] $ cleartool catcs -tag view_name 10:43:55 view_contact call failed: RPC: Unable to receive; errno = [WINSOCK] Connection reset by peer 10:43:55 cleartool: Error: Error trying to contact view_server for view path_to_view_name.vws: No such file or directory 10:43:55 10:43:55 FATAL: Base ClearCase failed. exit code=1 10:43:55 java.io.IOException: cleartool did not return the expected exit code. Command line="catcs -tag view_name", actual exit code=1 10:43:55 at hudson.plugins.clearcase.HudsonClearToolLauncher.run(HudsonClearToolLauncher.java:152) 10:43:55 at hudson.plugins.clearcase.ClearToolExec.runAndProcessOutput(ClearToolExec.java:907) 10:43:55 at hudson.plugins.clearcase.ClearToolExec.catcs(ClearToolExec.java:103) 10:43:55 at hudson.plugins.clearcase.action.BaseSnapshotCheckoutAction.checkout(BaseSnapshotCheckoutAction.java:104) 10:43:55 at hudson.plugins.clearcase.AbstractClearCaseScm.checkout(AbstractClearCaseScm.java:383) 10:43:55 at hudson.model.AbstractProject.checkout(AbstractProject.java:1253) 10:43:55 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) 10:43:55 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 10:43:55 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) 10:43:55 at hudson.model.Run.execute(Run.java:1745) 10:43:55 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 10:43:55 at hudson.model.ResourceController.execute(ResourceController.java:89) 10:43:55 at hudson.model.Executor.run(Executor.java:240) ClearCase version info: 10:41:35 [Snapshots] $ cleartool -version 10:41:35 ClearCase version 8.0.0.01 (Wed Dec 28 01:01:29 EST 2011) (8.0.0.01.00_2011D.FCS) 10:41:35 ClearCase version 8.0.0.02 (Thu Apr 05 18:31:09 EST 2012) (8.0.0.02.00_2012A.FCS) 10:41:35 ClearCase version 8.0.0.03 (Thu Jun 21 16:08:51 EST 2012) (8.0.0.03.00_2012B.FCS) 10:41:35 ClearCase version 8.0.0.04 (Thu Sep 13 15:30:21 EDT 2012) (8.0.0.04.00_2012C.FCS) 10:41:35 ClearCase version 8.0.0.05 (Wed Dec 12 19:09:45 EST 2012) (8.0.0.05.00_2012D.FCS) 10:41:35 ClearCase version 8.0.0.06 (Fri Mar 20 10:35:58 EST 2013) (8.0.0.06.00_2013A.FCS) 10:41:35 ClearCase version 8.0.0.07 (Tue Jun 11 00:01:08 EDT 2013) (8.0.0.07.00_2013B.FCS) 10:41:35 ClearCase version 8.0.0.08 (Mon Sep 23 00:01:21 EDT 2013) (8.0.0.08.00_2013C.FCS) 10:41:35 ClearCase version 8.0.0.09 (Wed Dec 11 00:01:16 EST 2013) (8.0.0.09.00_2013D.FCS) 10:41:35 ClearCase version 8.0.0.10 (Tue Mar 04 20:30:56 EST 2014) (8.0.0.10.00_2014A.D140304) 10:41:36 @(#) MVFS version 8.0.0.10 (Wed Feb 19 21:13:32 2014) 10:41:36 cleartool 8.0.0.10 (Tue Mar 4 21:16:26 2014) 10:41:36 db_server 8.0.0.10 (Tue Feb 25 21:21:26 2014) 10:41:36 VOB database schema versions: 54, 80 Environment: Jenkins 1.583, CC plugin latest, Windows 7, CC 8 Project: Jenkins
[JIRA] [subversion] (JENKINS-25041) SVN: string index out of range: -1 at hudson.scm.DirAwareSVNXMLLogHandler.sendToHandler(DirAwareSVNXMLLogHandler.java:121)
Stefan Puiu commented on JENKINS-25041 SVN: string index out of range: -1 at hudson.scm.DirAwareSVNXMLLogHandler.sendToHandler(DirAwareSVNXMLLogHandler.java:121) After a bit of digging, I've found https://issues.jenkins-ci.org/browse/JENKINS-23146. Will get our Jenkins admins to install SVN plugin 2.4.3 and mark this as duplicate if that works. The symptoms match - we merge code into this particular branch, that's why the build fails every time using poll SCM, but succeeds if I build manually when there are no changes... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-18714) SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable
Daniel Beck
commented on JENKINS-18714
SVN_URL and SVN_REVISION environment variables are missing when repository url contains a variable
I've looked into this a few months ago, and this is what I found:
The problem is that AbstractBuild queries (in that order) EnvironmentContributors, SCM, BuildWrapper.Environments and EnvironmentContributingActions to incrementally build the set of environment variables while a build is started.
SubversionSCM (an SCM) looks for matching entries in the URL -> Revision map during this variable resolution. If so, they are added as SVN_URL_x and SVN_REVISION_x. Why not just add everything? My guess is externals (while listed for a build, only explicitly defined locations have corresponding variables).
Due to the order of resolution, Env-Injected variables are not yet defined. This leads to a warning in the log of the form:
WARNING hudson.scm.SubversionSCM buildEnvVars
no revision found corresponding to ${SVNURL}; known: [https://svn/repo/...]
Afterwards, when the URLs are getting checked out, the variables have already been defined, therefore that works.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-25041) SVN: string index out of range: -1 at hudson.scm.DirAwareSVNXMLLogHandler.sendToHandler(DirAwareSVNXMLLogHandler.java:121)
Daniel Beck resolved JENKINS-25041 as Duplicate SVN: string index out of range: -1 at hudson.scm.DirAwareSVNXMLLogHandler.sendToHandler(DirAwareSVNXMLLogHandler.java:121) Yeah, JENKINS-23146 is the same issue as this. Change By: Daniel Beck (08/Oct/14 9:29 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22665) BuildPipelineView.MyUserIdCause stores entire hudson.model.User
Daniel Beck commented on JENKINS-22665 BuildPipelineView.MyUserIdCause stores entire hudson.model.User JENKINS-24994 suggests disallowing Causes like completely by throwing if the class is anonymous. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25039) javax.servlet.ServletException occurs while Editing and saving Sectioned View configuration in Jenkins Version 1.559
Daniel Beck resolved JENKINS-25039 as Duplicate javax.servlet.ServletException occurs while Editing and saving Sectioned View configuration in Jenkins Version 1.559 You're supposed to search first, then file an issue. Change By: Daniel Beck (08/Oct/14 9:36 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14313) login page redirects to login page
Daniel Beck updated JENKINS-14313 login page redirects to login page Comments indicate easy workaround is available. Change By: Daniel Beck (08/Oct/14 9:39 AM) 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] [cas] (JENKINS-25043) CAS redirects to "nullsecurityRealm" after Jenkins has rebooted
Anthony O. created JENKINS-25043 CAS redirects to "nullsecurityRealm" after Jenkins has rebooted Issue Type: Bug Assignee: Unassigned Components: cas Created: 08/Oct/14 9:41 AM Description: I'm using latest (1.565.1) version of docker image of jenkins (https://registry.hub.docker.com/_/jenkins/). I run it using --env JENKINS_PREFIX=/jenkins, then update all plugins, then install CAS plugin, configure jenkins to point to my CAS in SAML1.1 and configure the attributes mapping. All goes well until I restart my container. After that, when I correctly login to my CAS, it redirects me to https:///cas/login?TARGET=nullsecurityRealm%2FfinishLogin. Project: Jenkins Labels: cas restart Priority: Minor Reporter: Anthony O. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cas] (JENKINS-25043) CAS redirects to "nullsecurityRealm" after Jenkins has rebooted
Anthony O. updated JENKINS-25043 CAS redirects to "nullsecurityRealm" after Jenkins has rebooted Change By: Anthony O. (08/Oct/14 9:49 AM) Priority: Minor Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-3627) Add separate permission to view build logs
Daniel Beck commented on JENKINS-3627 Add separate permission to view build logs FWIW printing passwords in plain text to the console log should never be done and can be considered a bug in the plugin if it still happens. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-3627) Add separate permission to view build logs
Daniel Beck updated JENKINS-3627 Add separate permission to view build logs Change By: Daniel Beck (08/Oct/14 10:08 AM) Summary: Showing too much information Add separate permission to public viewers view build logs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25039) javax.servlet.ServletException occurs while Editing and saving Sectioned View configuration in Jenkins Version 1.559
Ramakrishna Bejawar commented on JENKINS-25039 javax.servlet.ServletException occurs while Editing and saving Sectioned View configuration in Jenkins Version 1.559 Actual Error Log: 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: java.lang.IllegalStateException: Form too large 214576>20 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.s
[JIRA] [analysis-collector] (JENKINS-25044) deployment process(incremental deployment process)
lakshminarayana matti created JENKINS-25044 deployment process(incremental deployment process) Issue Type: Bug Assignee: Ulli Hafner Components: analysis-collector Created: 08/Oct/14 11:38 AM Description: i have configured jenkins for salesforce project. i want to configure continuous integration so that it can only take components which got change part development. Ex: i have 10 components.i made change in 2 components.for the next build processi want to take these 2 components only. Environment: jenkins-1.581,jdk1.6.0_27,windows 7,google chrome, Project: Jenkins Priority: Critical Reporter: lakshminarayana matti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-25044) deployment process(incremental deployment process)
Daniel Beck resolved JENKINS-25044 as Not A Defect deployment process(incremental deployment process) Not a bug, not critical, and has nothing to do with analysis collector plugin. You're making absolutely no sense. Change By: Daniel Beck (08/Oct/14 11:53 AM) 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] [core] (JENKINS-9999) Installing Plugins/Upgrades causes a java.io.IOException: Server returned HTTP response code: 500 for URL: http://updates.jenkins-ci.org/download/plugins/analysis-core/1.2
Daniel Beck resolved JENKINS- as Cannot Reproduce Installing Plugins/Upgrades causes a java.io.IOException: Server returned HTTP response code: 500 for URL: http://updates.jenkins-ci.org/download/plugins/analysis-core/1.22/analysis-core.hpi This was probably a transient issue with the mirrors used to distribute the files. (Recent Jenkins versions now show the mirror URL so you can actually investigate in a useful way, because your wget may well have gotten a different mirror) Change By: Daniel Beck (08/Oct/14 11:54 AM) Status: Open 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] [analysis-collector] (JENKINS-25044) deployment process(incremental deployment process)
lakshminarayana matti commented on JENKINS-25044 deployment process(incremental deployment process) then what makes sense This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-2111) removing a job does not remove the workspace
Oleg Nenashev updated JENKINS-2111 removing a job does not remove the workspace Change By: Oleg Nenashev (08/Oct/14 12:24 PM) Component/s: core Component/s: other This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-10475) Allow job name in the queue to be augumented with additional information
Oleg Nenashev updated JENKINS-10475 Allow job name in the queue to be augumented with additional information The request stills valid. An additional extension point is required. Probably, tasks could modified by TaskListeners Change By: Oleg Nenashev (08/Oct/14 12:26 PM) Issue Type: Improvement New Feature Labels: extension Assignee: Kohsuke Kawaguchi Component/s: core Component/s: other This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-25044) deployment process(incremental deployment process)
Daniel Beck commented on JENKINS-25044 deployment process(incremental deployment process) Requests for assistance should be directed to the jenkinsci-users mailing list, or #jenkins on Freenode. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-10475) Allow job name in the queue to be augumented with additional information
Oleg Nenashev edited a comment on JENKINS-10475 Allow job name in the queue to be augumented with additional information The request stills valid. An additional extension point is required. Tasks display names could be also modified by TaskListeners This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-2111) removing a job does not remove the workspace
Daniel Beck commented on JENKINS-2111 removing a job does not remove the workspace I agree that this is a bug. When a build gets deleted, so should all the data be deleted. This may not be possible in the case of distributed builds (nodes may be offline). It may not be desirable in the case of custom workspaces shared with other projects or not meant to be deleted at all (it happens). I have used Hudson for a long time and now Jenkins, and as far as I remember, the default behaviour always was delete the workspace when deleting jobs. Possibly since new installs use a different top level directory for workspaces than for jobs. It used to be jobs/foo/workspace, now it is workspace/foo, like slave FS layout always was. However, for the master node, this is configurable in global 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-20116) JellyTagException after upgrading from 1.534 to 1.535
Oleg Nenashev resolved JENKINS-20116 as Incomplete JellyTagException after upgrading from 1.534 to 1.535 No response & no info about plugins. Please re-open the issue if you still experience it Change By: Oleg Nenashev (08/Oct/14 12:30 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10475) Allow job name in the queue to be augumented with additional information
Daniel Beck commented on JENKINS-10475 Allow job name in the queue to be augumented with additional information FWIW I recently submitted a patch that shows the build's display name instead of number as it was before. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-25044) deployment process(incremental deployment process)
lakshminarayana matti commented on JENKINS-25044 deployment process(incremental deployment process) thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Shannon Kerr commented on JENKINS-9104 Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed I hit three more instances of this. Two yesterday and one other a week ago. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-13516) Cancelling matrix build jobs only seems reliable from Jenkins front page
Oleg Nenashev resolved JENKINS-13516 as Cannot Reproduce Cancelling matrix build jobs only seems reliable from Jenkins front page There were many changes in matrix-projects and the core after the specified version POST requests from different pages use a single routine, hence the bug should not appear in the logic Closing the case. Please re-open it if you still experience the issue Change By: Oleg Nenashev (08/Oct/14 12:44 PM) Status: Open 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] [matrix-project] (JENKINS-13004) Add an option to remove nonsense configurations in matrix projects
Oleg Nenashev updated JENKINS-13004 Add an option to remove nonsense configurations in matrix projects Not a bug Change By: Oleg Nenashev (08/Oct/14 12:46 PM) Summary: Remove the Add an option to remove nonsense configurations in multi-configuration project matrix projects Issue Type: Bug New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-5444) Matrix project should support configurable degree of concurrency
Oleg Nenashev resolved JENKINS-5444 as Fixed Matrix project should support configurable degree of concurrency Throttle Concurrent Builds Plugin provides such functionality in newest versions Change By: Oleg Nenashev (08/Oct/14 12:52 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] [matrix-project] (JENKINS-21503) Multi-COnfiguration Projects Custom workspace creates seperate paths for all combinations
Oleg Nenashev resolved JENKINS-21503 as Cannot Reproduce Multi-COnfiguration Projects Custom workspace creates seperate paths for all combinations No response... Change By: Oleg Nenashev (08/Oct/14 12:53 PM) Status: Open 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] [matrix-project] (JENKINS-15480) Job starts on master except on slave node
Oleg Nenashev resolved JENKINS-15480 as Incomplete Job starts on master except on slave node No info to analyze / Old request If the issue is actual, see https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue#What%20information%20to%20provide%20for%20Environment%20and%20Description Change By: Oleg Nenashev (08/Oct/14 12:57 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Daniel Beck commented on JENKINS-9104 Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed How are you starting these builds? Batch? MSBuild plugin? What exact commands? If batch, did you try setting BUILD_ID as described on https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-5693) Archived artifacts not accessible for failed builds
Oleg Nenashev resolved JENKINS-5693 as Cannot Reproduce Archived artifacts not accessible for failed builds Cannot reproduce. The use-case works well in newest Jenkins versions Change By: Oleg Nenashev (08/Oct/14 1:03 PM) Status: Open 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] [matrix-project] (JENKINS-14618) ignore the checkout on the master
Oleg Nenashev resolved JENKINS-14618 as Fixed ignore the checkout on the master Duplicates JENKINS-4960 Change By: Oleg Nenashev (08/Oct/14 1:01 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] [matrix-reloaded] (JENKINS-11260) Matrix relaoded does not use test result from original build
Oleg Nenashev updated JENKINS-11260 Matrix relaoded does not use test result from original build Fixed the component. AFAIK the issue stills actual Change By: Oleg Nenashev (08/Oct/14 1:07 PM) Assignee: Praqma Support Component/s: matrix-reloaded Component/s: matrix-project This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-7416) No link to build individual config of a matrix job
Oleg Nenashev resolved JENKINS-7416 as Fixed No link to build individual config of a matrix job Matrix Combinations and Matrix Reloaded plugins provide the required feature Change By: Oleg Nenashev (08/Oct/14 1:05 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] [matrix-project] (JENKINS-23459) Cannot restrict a matrix build job to one node/label
Oleg Nenashev commented on JENKINS-23459 Cannot restrict a matrix build job to one node/label NodeLabel Parameter allows to restrict jobs in a such way This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cas] (JENKINS-25043) CAS redirects to "nullsecurityRealm" after Jenkins has rebooted
Anthony O. commented on JENKINS-25043 CAS redirects to "nullsecurityRealm" after Jenkins has rebooted Here is the workaround: Before restart, go to system configuration (http:///jenkins/configure) and click on "Save". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25026) Console output stops populating after several seconds
Martin Schayna updated JENKINS-25026 Console output stops populating after several seconds Sorry for unclear information, updated components and added previous version where I have seen this working. Change By: Martin Schayna (08/Oct/14 1:32 PM) Description: Console output is populating log in browser window, but after several seconds stops. User has to refresh the page but it happens again. It looks like populating works only when log grown quickly and stops when job doesn't log for a while.It seems that problem is on the server side, browser repeats AJAX requests to progressiveHtml path and all of them have "X-More-Data: true" response header, but the last one hasn't (wrongly, because job logging on server side continues). Latest version I have seen this working: 1.466 Component/s: core 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] [walldisplay] (JENKINS-25022) Walldisplay is not shown, if the project has the same name the current view
Christian Pelster commented on JENKINS-25022 Walldisplay is not shown, if the project has the same name the current view Thanks for your patch, I will release a new version within the next few days This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25026) Console output stops populating after several seconds
Martin Schayna updated JENKINS-25026 Console output stops populating after several seconds Change By: Martin Schayna (08/Oct/14 1:40 PM) Environment: Jenkins 1.582 from Bitnami, running on AWS in m3.medium instance type Server OS: Ubuntu 14.04 64bitJDK: Oracle JDK 1.7.0_67Browser: Chrome 37 64bit This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cas] (JENKINS-25043) CAS redirects to "nullsecurityRealm" after Jenkins has rebooted
Daniel Beck commented on JENKINS-25043 CAS redirects to "nullsecurityRealm" after Jenkins has rebooted So the issue only occurs when you boot up Jenkins for the first time and never review/save the global configuration? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Shannon Kerr commented on JENKINS-9104 Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Batch. In the Jenkins project, we use "Execute Windows Batch Command" to call a batch script that automates a bunch of pre build work and ends up calling the builds via devenv. I did not try the BUILD_ID suggestion as I saw that there were still issues mentioned in this ticket with this work-around. I was trying hang in there until the final solution was provided, but the failures seem to be picking up for us lately. I guess we'll use this work around for 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] [copyartifact] (JENKINS-16847) Support for copying artifacts from other builds being part of the same MultiJob (previous phases)
Krzysztof Trojan commented on JENKINS-16847 Support for copying artifacts from other builds being part of the same MultiJob (previous phases) Ray, while useful, adding a new selector makes it possible to run the job only within MultiJob. What if one wanted to use also in regular pipelines (project triggered both as part of MultiJob and by another project) ? In the sense the original concept would I think work better ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-16847) Support for copying artifacts from other builds being part of the same MultiJob (previous phases)
Krzysztof Trojan updated JENKINS-16847 Support for copying artifacts from other builds being part of the same MultiJob (previous phases) Change By: Krzysztof Trojan (08/Oct/14 1:56 PM) Description: Currently there is no easy way of selecting the right build to copy artifacts from if the project we want to copy from is part of MultiJob.The "Last Successful Build" is prone for selecting the wrong build if the project was build again in the meantime between the MultiJob start and current momentand "Upstream Project That Triggered this Build" does not work as previously executed builds in the same MultiJob are not considered "upstream" (are not listed as "causes").A patch to TriggeredBuildSelector has been created to explicitly support MultiJob plugin pipelines and query it for builds already completed, treating them as if they were "causes". Somewhat dirty (for in for loop :) ), but works correctly and for the number of projects in a pipeline does not matter much.See attachment . Complete project as I did not have and a decent diff on the machine I am writing this on (sorry!) corresponding pull request . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cas] (JENKINS-25043) CAS redirects to "nullsecurityRealm" after Jenkins has rebooted
Anthony O. commented on JENKINS-25043 CAS redirects to "nullsecurityRealm" after Jenkins has rebooted Apparently yes... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-git] (JENKINS-25045) Populate the initial code for team concert git plugin
Krishna Kishore created JENKINS-25045 Populate the initial code for team concert git plugin Issue Type: Task Assignee: Krishna Kishore Components: teamconcert-git Created: 08/Oct/14 2:06 PM Description: Populate the initial plugin code Environment: Team Concert Project: Jenkins Labels: teamconcert Priority: Minor Reporter: Krishna Kishore This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert-git] (JENKINS-25045) Populate the initial code for team concert git plugin
SCM/JIRA link daemon commented on JENKINS-25045 Populate the initial code for team concert git plugin Code changed in jenkins User: kkishore Path: com.ibm.team.git.build.hjplugin/.gitignore com.ibm.team.git.build.hjplugin/pom.xml com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/BuildParameterAction.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/InvalidCredentialsException.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/RTCBuildResultAction.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/RTCConnector.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/RTCGitBuilder.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/RTCGitChangelogAnnotator.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/RTCLoginInfo.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/RTCRunListener.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/RTCUtils.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/RtcJsonUtil.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/http/HttpUtils.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/http/SSLContextUtil.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/scm/ChangeSetData.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/scm/GitScmUtils.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/util/Helper.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/util/RTCHttpConstants.java com.ibm.team.git.build.hjplugin/src/main/java/com/ibm/team/git/build/hjplugin/util/ValidationResult.java com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_cs.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_de.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_es.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_fr.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_hu.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_it.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_ja.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_ko.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_pl.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_pt_BR.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_ru.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_tr.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_zh.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_zh_HK.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/Messages_zh_TW.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/RTCGitBuilder/config.jelly com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/RTCGitBuilder/config.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/RTCGitBuilder/config_cs.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/RTCGitBuilder/config_de.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/RTCGitBuilder/config_es.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/RTCGitBuilder/config_fr.properties com.ibm.team.git.build.hjplugin/src/main/resources/com/ibm/team/git/build/hjplugin/RTCGitBuilder/config_hu.prop
[JIRA] [teamconcert-git] (JENKINS-25045) Populate the initial code for team concert git plugin
Krishna Kishore resolved JENKINS-25045 as Fixed Populate the initial code for team concert git plugin Add the initial plugin code Change By: Krishna Kishore (08/Oct/14 2:15 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25046) Cookie header too long, causing a 413 HTTP error
Eric Citaire created JENKINS-25046 Cookie header too long, causing a 413 HTTP error Issue Type: Bug Assignee: Unassigned Components: core Created: 08/Oct/14 2:20 PM Description: Each time Jenkins (re)starts, its session-cookie name changes (ie JSESSIONID.some_random_string). After a while, the browser have a bunch of session cookies, each one having a different name, causing the "Cookie" request header to be very long. The server returns a HTTP 413 response and a blank page. The user must clean his cookies in order to access Jenkins again. Environment: Jenkins 1.581, launched through the built in Jetty Project: Jenkins Priority: Major Reporter: Eric Citaire This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-24271) Re-execute and Force permissions must be separated
Renate Kazaka assigned JENKINS-24271 to Renate Kazaka Re-execute and Force permissions must be separated Change By: Renate Kazaka (08/Oct/14 2:23 PM) Assignee: Renate Kazaka This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-24271) Re-execute and Force permissions must be separated
Renate Kazaka started work on JENKINS-24271 Re-execute and Force permissions must be separated Change By: Renate Kazaka (08/Oct/14 2:24 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] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Hristo Indzhov commented on JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' I also got the same issue today on ubuntu 14.04 lts Problem accessing /jenkins/;jsessionid=1ki1cxht216p5l2y6foppljd9. Reason: Not Found This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22665) BuildPipelineView.MyUserIdCause stores entire hudson.model.User
Jesse Glick commented on JENKINS-22665 BuildPipelineView.MyUserIdCause stores entire hudson.model.User This class is not anonymous. It is not static, so it gets a bogus reference to the BuildPipelineView.this, but that just makes for messy XML; fixing that would not fix the security hole. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25047) Draft Published event not handled correctly when using replication to slaves
Scott Hebert created JENKINS-25047 Draft Published event not handled correctly when using replication to slaves Issue Type: Bug Assignee: Scott Hebert Components: gerrit-trigger Created: 08/Oct/14 2:35 PM Description: The Draft Published event is marked with the RepositoryModifiedEvent interface therefore Gerrit Trigger will attempt to wait for a replication event from Gerrit. It will never come so the job will eventually timeout. Project: Jenkins Labels: gerrit-trigger Priority: Critical Reporter: Scott Hebert This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24994) Poor error reporting when an anonymous Cause is used
Jesse Glick updated JENKINS-24994 Poor error reporting when an anonymous Cause is used It might make sense for Jenkins to define an annotation indicating abstract types whose implementations are intended to be serialized with XStream (Cause, RunAction2, etc.). An annotation processor could then report an error if an implementation were an anonymous inner class or a non-static nested class, or had fields of various types known to be nonserializable or known to themselves be serialized at top level (User, Run, etc.). Change By: Jesse Glick (08/Oct/14 2:38 PM) Summary: StringIndexOutOfBoundsException if build cause class is Poor error reporting when an anonymous Cause is used Labels: api robustness xstream Component/s: core Component/s: envinject This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-24994) Poor error reporting when an anonymous Cause is used
Jesse Glick assigned JENKINS-24994 to Unassigned Poor error reporting when an anonymous Cause is used Change By: Jesse Glick (08/Oct/14 2:39 PM) Assignee: Gregory Boissinot This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cas] (JENKINS-25043) CAS redirects to "nullsecurityRealm" after Jenkins has rebooted
Anthony O. updated JENKINS-25043 CAS redirects to "nullsecurityRealm" after Jenkins has rebooted Change By: Anthony O. (08/Oct/14 2:52 PM) Priority: Blocker Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-25048) Git plugin ignores included/excluded paths when triggering build on commit nitification
Pavel Baranchikov created JENKINS-25048 Git plugin ignores included/excluded paths when triggering build on commit nitification Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 08/Oct/14 2:54 PM Description: I have a Git repository, which contains of multiple modules, which should be build separately. I have separate Jenkins job for each module. Stash's "Jenkins Webhook plugin" notifies Jenkins about a new commit, which triggers ALL the module job to start. To separate job I've used "polling ignores commits in certain paths", selecting included regions. Seems, like the regions are not used during commit notification triggering. Project: Jenkins Priority: Major Reporter: Pavel Baranchikov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25049) Git plugin ignores Refspec when triggering build on commit nitification
Pavel Baranchikov
created JENKINS-25049
Git plugin ignores Refspec when triggering build on commit nitification
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git
Created:
08/Oct/14 2:59 PM
Description:
Default refspec according to the documentation is
+refs/heads/*:refs/remotes/REPOSITORYNAME/*
When I click on "Trigger build" in Stash's pull request overview, my job fails, because it cannot find commit in the specified refspecs (because commit is in pull requests, not in heads).
> C:\Program Files (x86)\Git\bin\git.exe rev-parse "1c2ead96dfe52f7f0675161f025c2541ede93782^{commit}" # timeout=10
FATAL: Command "C:\Program Files (x86)\Git\bin\git.exe rev-parse "1c2ead96dfe52f7f0675161f025c2541ede93782^{commit}"" returned status code 128:
stdout: 1c2ead96dfe52f7f0675161f025c2541ede93782^{commit}
stderr: fatal: ambiguous argument '1c2ead96dfe52f7f0675161f025c2541ede93782^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
hudson.plugins.git.GitException: Command "C:\Program Files (x86)\Git\bin\git.exe rev-parse "1c2ead96dfe52f7f0675161f025c2541ede93782^{commit}"" returned status code 128:
stdout: 1c2ead96dfe52f7f0675161f025c2541ede93782^{commit}
stderr: fatal: ambiguous argument '1c2ead96dfe52f7f0675161f025c2541ede93782^{commit}': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
Project:
Jenkins
Priority:
Minor
Reporter:
Pavel Baranchikov
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-25049) Git plugin ignores Refspec when triggering build on commit nitification
Pavel Baranchikov updated JENKINS-25049 Git plugin ignores Refspec when triggering build on commit nitification Change By: Pavel Baranchikov (08/Oct/14 3:00 PM) Priority: Minor 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] [doclinks] (JENKINS-25050) Publishing a HTML document inside a subdirectory of the archive
WH created JENKINS-25050 Publishing a HTML document inside a subdirectory of the archive Issue Type: Improvement Assignee: sogabe Components: doclinks Created: 08/Oct/14 3:08 PM Description: I need to archive a directory structure where the published document lies in a sub directory. But this is currently not possible with the plugin. Directory structure to archive: /A/1/2/myIndex.html /A/3/myPage1.html Document to publish: myIndex.html (has hyperlinks to myPage1.html Jenkins doclinks plugin configuration: Directory to archive = A Index file = 1/2/myIndex.html Current result: Viewing of myIndex1.html works, but hyperlink to myPage1.html is broken. Could you please improve the plugin for that situation? Thank you very much! Environment: Jenkins ver. 1.532.1 Jenkins DocLinks plugin 0.6 Project: Jenkins Priority: Major Reporter: WH This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25040) Unnecessary SCM actions in multi-configuration job on master
Oleg Nenashev commented on JENKINS-25040 Unnecessary SCM actions in multi-configuration job on master Your request seems to be similar to JENKINS-4960. Would it resolve your 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] [job-dsl-plugin] (JENKINS-25051) ConcurrentModificationException in DSL plugin 1.2.6
Jeff Storey created JENKINS-25051 ConcurrentModificationException in DSL plugin 1.2.6 Issue Type: Bug Assignee: Daniel Spilker Attachments: concurrentmod.log Components: job-dsl-plugin Created: 08/Oct/14 3:23 PM Description: I upgraded the plugin to the newest version 1.2.6 and the jobs would no longer run and threw a ConcurrentModificationException every time I tried to run them. Log is attached. Environment: OS X 10.9.4 Project: Jenkins Priority: Blocker Reporter: Jeff Storey This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25051) ConcurrentModificationException in DSL plugin 1.2.6
Daniel Spilker commented on JENKINS-25051 ConcurrentModificationException in DSL plugin 1.2.6 The seems to be a similary issue as JENKINS-22708, but only for views. Can you check that your configure blocks for views are escaping calls to properties? Have a look at 4th bullet point on https://github.com/jenkinsci/job-dsl-plugin/wiki/The-Configure-Block#transforming-xml. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Kanstantsin Shautsou updated JENKINS-14193 EnvInject doesn't pass variables defined in prebuild step if maven project is used Change By: Kanstantsin Shautsou (08/Oct/14 3:29 PM) Component/s: maven-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] [envinject] (JENKINS-14193) EnvInject doesn't pass variables defined in prebuild step if maven project is used
Kanstantsin Shautsou commented on JENKINS-14193 EnvInject doesn't pass variables defined in prebuild step if maven project is used Hi, i think this not EnvInject plugin issue, because i injected env and parameter variables with groovy and they are not available in Maven build step. #JENKINS-20884 seems the root of 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] [core] (JENKINS-24955) Quiet period doesn't work
Mathieu Cantin closed JENKINS-24955 as Not A Defect Quiet period doesn't work Change By: Mathieu Cantin (08/Oct/14 3:35 PM) Status: Open Closed 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] [job-dsl-plugin] (JENKINS-25051) ConcurrentModificationException in DSL plugin 1.2.6
Jeff Storey
commented on JENKINS-25051
ConcurrentModificationException in DSL plugin 1.2.6
So I had previously added my own configure block to turn this parameter on before it was supported in the DSL with a block that looks like the following. When I replaced that with the new startsWithParameters block it worked. But I wouldn't think that having a configuration block like that should cause a breakage.
jobFactory.view(type: 'BuildPipelineView') {
name("myPipeline")
showPipelineParameters true
showPipelineParametersInHeaders false
showPipelineDefinitionHeader true
selectedJob("ajob")
configure { pipelineNode ->
pipelineNode << {
startsWithParameters true
}
}
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-24849) Problem in Thread handling for scm-polling jobs
SCM/JIRA link daemon commented on JENKINS-24849 Problem in Thread handling for scm-polling jobs Code changed in jenkins User: Cletus D'Souza Path: src/main/java/hudson/scm/APISession.java http://jenkins-ci.org/commit/integrity-plugin/7f152721e5cafe76c9eb86ce1e45d056de36e84b Log: Per JENKINS-24849 added a catch exception block when CmdRunner is released in APISession.Terminate() This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-25020) Accessing parameters of triggered build has strange syntax
Daniel Beck commented on JENKINS-25020 Accessing parameters of triggered build has strange syntax And just to be sure: a new freestyle project building on the same slave that runs env in a shell build step will include para2 among the variables printed as well? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25020) Accessing parameters of triggered build has strange syntax
Daniel Beck edited a comment on JENKINS-25020 Accessing parameters of triggered build has strange syntax And just to be sure: a new freestyle project (no parameters or anything) building on the same slave that only runs env in a shell build step will include para2 among the variables printed as well? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-25051) ConcurrentModificationException in DSL plugin 1.2.6
Jeff Storey
edited a comment on JENKINS-25051
ConcurrentModificationException in DSL plugin 1.2.6
So I had previously added my own configure block to turn this parameter on before it was supported in the DSL with a block that looks like the following. When I replaced that with the new startsWithParameters block it worked.
jobFactory.view(type: 'BuildPipelineView') {
name("myPipeline")
showPipelineParameters true
showPipelineParametersInHeaders false
showPipelineDefinitionHeader true
selectedJob("ajob")
configure { pipelineNode ->
pipelineNode << {
startsWithParameters true
}
}
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [gitlab] (JENKINS-25052) ssl certificate errors after upgrading gitlab to GitLab 7.3.2 f092e53
Guy Attrill created JENKINS-25052 ssl certificate errors after upgrading gitlab to GitLab 7.3.2 f092e53 Issue Type: Bug Assignee: Unassigned Components: gitlab Created: 08/Oct/14 4:30 PM Description: open a job with git configured and jetty error https://github.com/timols/java-gitlab-api/blob/master/src/main/java/org/gitlab/api/http/GitlabHTTPRequestor.java line 294 This was working fine before we upgraded gitlab Have uninstalled plugin to enable work to continue but this will stop our merge builds from working Environment: jenkins 565.1 latest gitlab plugin gitlab 7.3.2 Project: Jenkins Labels: plugin gitlab ssl error Priority: Major Reporter: Guy Attrill This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-20248) OpenID Plugin redirects REST API requests also
MattRussellUK commented on JENKINS-20248 OpenID Plugin redirects REST API requests also I had this issue, hope this might help someone else: in my case, it was the reverse-proxy stripping out the auth header before reaching Jenkins (we had "RequestHeader unset Authorization" in our Apache config for some reason). It works fine 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] [core] (JENKINS-25026) Console output stops populating after several seconds
Daniel Beck commented on JENKINS-25026 Console output stops populating after several seconds Does the spinner (or "indeterminate progress indicator") at the bottom of the log disappear as well? Does the browser stop sending ajax update requests? IIRC X-More-Data only applies when there's more data, so if logging is quiet, it'll not have more data for a while. The client should still continue polling for changes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-15480) Job starts on master except on slave node
Daniel Beck commented on JENKINS-15480 Job starts on master except on slave node FWIW I don't understand this report. If this still occurs, please provide exact steps to reproduce, using the labels on the Jenkins UI to remove ambiguity. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-10434) Git plugin 1.1.10 fails to parse author information
Dmitry Dmitry reopened JENKINS-10434 Git plugin 1.1.10 fails to parse author information BUILD SUCCESSFUL Total time: 4 minutes 27 seconds FATAL: No author in changeset 59dade5a63276fd0489fa9187e4a0d15ed819fa0tree java.lang.RuntimeException: No author in changeset 59dade5a63276fd0489fa9187e4a0d15ed819fa0tree at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:323) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:350) at hudson.model.AbstractBuild.getCulprits(AbstractBuild.java:346) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:687) at hudson.model.Run.execute(Run.java:1770) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Reproducing always. Is it possible just to return emty string instead of exception, whatever? No matter what the 'author' in build logs or reports, but failed build discards all efforts that was done to setup complete CI staff with Jenkins(( Change By: Dmitry Dmitry (08/Oct/14 4:54 PM) Resolution: Cannot Reproduce Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-proposals] (JENKINS-6641) Fine grained authorizations in hudson is not possible
Daniel Beck commented on JENKINS-6641 Fine grained authorizations in hudson is not possible We need a matrix-based but on a part of jobs or views or a regex, not for all projects. That's what project-based matrix security 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] [durable-task] (JENKINS-22249) Record process ID of spawned process
Jesse Glick commented on JENKINS-22249 Record process ID of spawned process http://serverfault.com/questions/126502/how-to-get-own-process-pid-from-the-command-prompt-in-windows/126643#126643 is the only thing I can find for Windows. Ugly! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-23905) Jenkins Slaves launched with the incorrect environment variables
Mathieu Cantin commented on JENKINS-23905 Jenkins Slaves launched with the incorrect environment variables We had the same issue, but with a job. For example, a job was triggered at about the same time by two different parent jobs with different parameters (run A and run B). During the run B, we had environment variables corresponding to run A. After both runs, the "Environment variables" menu displays the correct parameters. On 1.90 in Jenkins version 1.565.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-25036) maximum number of jenkins user reached
Daniel Beck commented on JENKINS-25036 maximum number of jenkins user reached Get rid of Green Balls plugin, this log is an abomination. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-24145) latest ghprb plugin broken for gihub enterprise users
David Tanner commented on JENKINS-24145 latest ghprb plugin broken for gihub enterprise users Is anyone still experiencing this bug? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-2131) Log user names of failed login attempts
Daniel Beck updated JENKINS-2131 Log user names of failed login attempts Oleg it'd be much more helpful if you checked whether issues are actually still valid (instead of just changing a bit of metadata). Which this one isn't. Change By: Daniel Beck (08/Oct/14 5:44 PM) Component/s: core Component/s: audit-trail This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-21160) Jenkins CLI cannot handle arguments with equals signs ("=")
Damien Nozay
commented on JENKINS-21160
Jenkins CLI cannot handle arguments with equals signs ("=")
Ok, i just upgraded another system (1.532.3 => 1.565.3) and I am able to repro.
I did remove envinject, and disabled token-macro.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-21160) Jenkins CLI cannot handle arguments with equals signs ("=")
Daniel Beck
commented on JENKINS-21160
Jenkins CLI cannot handle arguments with equals signs ("=")
Did removing the plugins help, or did it make no difference? Your comment is unclear.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-23634) Form too large 234222>200000 when submitting user permission update, when using Matrix-based security
Daniel Beck updated JENKINS-23634 Form too large 234222>20 when submitting user permission update, when using Matrix-based security Reducing priority, workaround is to set system property like -Dorg.eclipse.jetty.server.Request.maxFormContentSize=500 See e.g. JENKINS-20327. Change By: Daniel Beck (08/Oct/14 5:48 PM) Priority: Critical Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-14618) ignore the checkout on the master
Daniel Beck commented on JENKINS-14618 ignore the checkout on the master Oleg: I disagree, the other wants 1 SCM checkout, this one wants N checkouts, instead of N+1. This one is actually the exact opposite of JENKINS-4960. They're related, but not duplicate 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] [matrix-project] (JENKINS-25040) Unnecessary SCM actions in multi-configuration job on master
Daniel Beck commented on JENKINS-25040 Unnecessary SCM actions in multi-configuration job on master In this case JENKINS-14618 is a better match. Is this about saving time/space, or does master have connectivity issues or something else preventing successful checkout? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-25040) Unnecessary SCM actions in multi-configuration job on master
Daniel Beck updated JENKINS-25040 Unnecessary SCM actions in multi-configuration job on master Change By: Daniel Beck (08/Oct/14 5:54 PM) Component/s: matrix-project Component/s: core Component/s: multi-slave-config Component/s: multijob-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] [core] (JENKINS-2131) Log user names of failed login attempts
Daniel Beck resolved JENKINS-2131 as Fixed Log user names of failed login attempts Fixed in the mean time by logging jenkins.security.SecurityListener: Oct 08, 2014 7:42:44 PM FINE jenkins.security.SecurityListener failed to authenticate: baduser Oct 08, 2014 7:42:44 PM FINE jenkins.security.SecurityListener failed to log in: baduser Change By: Daniel Beck (08/Oct/14 5:44 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] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Daniel Beck commented on JENKINS-22358 Jenkins 1.556 gives 'Error 404 Not Found' It's not clear what the circumstances are for this problem to occur. I'd like to investigate this, but I have no idea how to reproduce the problem. Jenkins version OS and version How was Jenkins installed? Container and version, if not using the native installer What's the context path (e.g. / or /jenkins), and what's the URL that fails? What's the authentication realm (where are the users coming from, Jenkins User Database, LDAP, PAM, ...) What's the authorization strategy (e.g. matrix auth, logged in users can do anything, ...), and what permissions does anonymous have? Which client OS and web browser (+ versions of each)? What are the exact steps to reproduce this problem in a new browser session (no cookies etc.). Be as precise and exhaustive in these instructions as you can (imagine explaining it to your technologically impaired parents/grandparents/spouse). If you're attaching files, please keep it to PDF, RTF, or plain text. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
