[JIRA] [git-plugin] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title
G. Ann Campbell edited a comment on JENKINS-17614
Re: Jenkins triggers builds on git SCM changes, but nothing changed
I just encountered this problem (on Cloudbees, so I don't know the versin #) and fixed it by updating branch from the default {{**}} to a specific branch name, "master" in my case.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-plugin] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title G. Ann Campbell commented on JENKINS-17614 Re: Jenkins triggers builds on git SCM changes, but nothing changed I just encountered this problem and fixed it by updating branch from the default ** to a specific branch name, "master" in my case. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory] (JENKINS-20511) hudson.maven.MavenBuild MissingFieldException: No field 'targetType' found in class 'hudson.plugins.jobConfigHistory.JobConfigBadgeAction'
G. Ann Campbell commented on JENKINS-20511 hudson.maven.MavenBuild MissingFieldException: No field targetType found in class hudson.plugins.jobConfigHistory.JobConfigBadgeAction After upgrading to 2.5 I see 1) old data warnings 2) loss of build badges This happens on all freestyle jobs I checked. (I don't have any Maven jobs). I roll back to 2.4 both conditions reverse. I'm on Jenkins ver. 1.513, on CentOS. I'm not using Build Trigger Badge Plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15799) loosing matrix sub builds
G. Ann Campbell edited a comment on JENKINS-15799 loosing matrix sub builds I'm seeing this with freestyle builds after our recent upgrade to 1.513. Note that I initially reported this issue in JENKINS-15979, which has been marked a duplicate of this ticket. My initial report (although I didn't think to mention it) was about freestyle builds. As with JENKINS-15979, what we saw on 1.513 was that the build history was missing from the renamed job and builds fired after the rename would be available in history for a while, then disappear. However, the builds were all there on disk. Once again, restarting fixed the problem. Linux (CentOS). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.
G. Ann Campbell commented on JENKINS-13995 Would like the ability to disable hover-over context menus. I've just installed 1.512 feedback was requested. I'm not seeing the mouseover popup of build queue items and/or jobs currently being run. I was under the impression that would come back. As for the "v", I still don't like it, but it seems to work as designed. However, the spacing is a little crowded in the list of running jobs. It also looks crowded on the build number in the last failure/last success column. Haven't looked exhaustively at other places. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.
G. Ann Campbell commented on JENKINS-13995 Would like the ability to disable hover-over context menus. @Jesse: Please, please, please don't turn single-clicks into double-clicks! I like the OP's request best: make the context menu behavior a setting (user-level? system-level?) I love the hover menus. Clearly others hate it. But why make half the crowd unhappy? Make it configurable, default to whatever pleases the loudest group of agitators. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.
G. Ann Campbell commented on JENKINS-13995 Would like the ability to disable hover-over context menus. I agree that the 'v' is hard to use. If I can't have the old functionality back (which I loved) how about you don't have to click on the 'v' it just drops down automatically? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13995) Would like the ability to disable hover-over context menus.
G. Ann Campbell commented on JENKINS-13995 Would like the ability to disable hover-over context menus. Was the queue time popup for jobs in the build queue supposed to be incorporated into the now-non-default context menu? Since the context menu is now a separate function, I'd like to see the queue time popup return. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15799) loosing matrix sub builds
G. Ann Campbell commented on JENKINS-15799 loosing matrix sub builds The ticket I opened got closed as a duplicate of this one. I saw this "forgetting" behavior with a renamed, top-level, non-matrix job. Right after renaming the job, the builds showed in the history, but ... several hours later they were gone (altho still there on disk.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15998) builds assigned to wrong job
G. Ann Campbell created JENKINS-15998 builds assigned to wrong job Issue Type: Bug Assignee: vjuranek Components: build-publisher Created: 30/Nov/12 6:22 PM Description: We have jobs with similar names: longishName and longishName_2_3_4 The one without the number at the end is a head build. The with the number is a branch. After upgrading this week from 1.472 to 1.491 and then subsequently downgrading, we found branch builds populated (subdirectories created under builds) into the head job. We could tell at a glance that there was a problem since we use the formatted version number as the build display name. Also, the head build job was on build # 13, but the build history contained builds with numbers in the 40's and 60's - although not everything from 40-70, just a frightening, confusing handful. Project: Jenkins Priority: Critical Reporter: G. Ann Campbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15998) builds copied to wrong job
G. Ann Campbell updated JENKINS-15998 builds copied to wrong job Change By: G. Ann Campbell (30/Nov/12 6:23 PM) Summary: builds assigned copied towrongjob Description: Wehavejobswithsimilarnames:longishNameandlongishName_2_3_4Theonewithoutthenumberattheendisaheadbuild.Thewiththenumberisabranch.Afterupgradingthisweekfrom1.472to1.491andthensubsequentlydowngrading,wefoundbranchbuildspopulated(subdirectoriescreatedunderbuilds)intotheheadjob.Wecouldtellataglancethattherewasaproblemsinceweusetheformattedversionnumberasthebuilddisplayname.Also,theheadbuildjobwasonbuild#13,butthebuildhistorycontainedbuildswithnumbersinthe40sand60s-althoughnoteverythingfrom40-70,justafrightening,confusinghandful. Thecopiedbuildsstillexisted,unmolested,intheiractualparentjobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15979) forgets builds, workspace of renamed job
G. Ann Campbell created JENKINS-15979 forgets builds, workspace of renamed job Issue Type: Bug Affects Versions: current Assignee: vjuranek Components: build-publisher Created: 29/Nov/12 2:25 PM Description: I renamed a job yesterday on 1.491 and this morning, Jenkins showed it as having no builds - even though I could see them on the file system. Immediately after the renaming, Jenkins seemed to have "lost sight" of the existing workspace. So I fired another build and all was good. But this morning, it had "forgotten" both that build and the workspace again. Restarting Jenkins seems to have fixed it. (Hope I picked the right component...) Project: Jenkins Priority: Minor Reporter: G. Ann Campbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14750) permissions tweaking
G. Ann Campbell commented on JENKINS-14750 permissions tweaking I'm happy to put this on my list, but I've got a backlog at the moment, so it could take a while! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14750) permissions tweaking
G. Ann Campbell created JENKINS-14750 permissions tweaking Issue Type: New Feature Assignee: Unassigned Components: monitoring Created: 09/Aug/12 2:51 PM Description: I would like my users with universal read permissions to be able to get to /monitoring, perhaps with the GC link removed or inactivated. Alternately, it would be great if there were a "view monitoring" checkbox in the permissions grid Or... a "configure monitoring" section in the global config to allow me to twiddle access perms Project: Jenkins Priority: Minor Reporter: G. Ann Campbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13358) Timeout not working
G. Ann Campbell created JENKINS-13358: - Summary: Timeout not working Key: JENKINS-13358 URL: https://issues.jenkins-ci.org/browse/JENKINS-13358 Project: Jenkins Issue Type: Bug Components: sitemonitor Affects Versions: current Environment: CentOS 5.6; Sun Java 1.6.0_26 Reporter: G. Ann Campbell Assignee: cliffano Twice now I've had jobs hang because sitemonitor was waiting for a response from the server. Stop/starting the server in question allowed the job to complete. In both cases, a 503 response code was recorded to the console. My timeout is set to the default. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13017) Invalid date On startup after install. Changelogs disappear from GUI
G. Ann Campbell created JENKINS-13017: - Summary: Invalid date On startup after install. Changelogs disappear from GUI Key: JENKINS-13017 URL: https://issues.jenkins-ci.org/browse/JENKINS-13017 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Reporter: G. Ann Campbell Just tried to upgrade to 2.0. Jenkinks log give exceptions on startup none of my projects display any changes / change logs. Reverting restores change logs. Here's a sample stacktrace java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.beanutils.PropertyUtilsBean.invokeMethod(PropertyUtilsBean.java:2155) at org.apache.commons.beanutils.PropertyUtilsBean.setSimpleProperty(PropertyUtilsBean.java:2141) at org.apache.commons.beanutils.PropertyUtilsBean.setNestedProperty(PropertyUtilsBean.java:1948) at org.apache.commons.beanutils.PropertyUtilsBean.setProperty(PropertyUtilsBean.java:2054) at org.apache.commons.beanutils.BeanUtilsBean.setProperty(BeanUtilsBean.java:1015) at org.apache.commons.beanutils.BeanUtils.setProperty(BeanUtils.java:456) at org.apache.commons.digester.BeanPropertySetterRule.end(BeanPropertySetterRule.java:197) at org.apache.commons.digester.Digester.endElement(Digester.java:1130) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragment ScannerImpl.java:1782) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocu mentFragmentScannerImpl.java:2938) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentSc annerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at org.apache.commons.digester.Digester.parse(Digester.java:1631) at hudson.scm.CVSChangeLogSet.parse(CVSChangeLogSet.java:113) at hudson.scm.CVSChangeLogParser.parse(CVSChangeLogParser.java:43) at hudson.scm.CVSChangeLogParser.parse(CVSChangeLogParser.java:38) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:808) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:782) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:356) at hudson.model.User.getBuilds(User.java:390) at hudson.WebAppMain$2$1.doRun(WebAppMain.java:225) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: java.lang.RuntimeException: Invalid date at hudson.scm.CVSChangeLogSet$CVSChangeLog.setDate(CVSChangeLogSet.java:235) ... 34 more Caused by: java.text.ParseException: Unparseable date: 2012-02-29 at java.text.DateFormat.parse(DateFormat.java:337) at hudson.scm.CVSChangeLogSet$CVSChangeLog.setDate(CVSChangeLogSet.java:232) ... 34 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13017) Invalid date On Jenkins startup after CVS plugin 2.0 upgrade. Changelogs disappear from GUI
[ https://issues.jenkins-ci.org/browse/JENKINS-13017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] G. Ann Campbell updated JENKINS-13017: -- Summary: Invalid date On Jenkins startup after CVS plugin 2.0 upgrade. Changelogs disappear from GUI (was: Invalid date On startup after install. Changelogs disappear from GUI) Environment: Jenkins 1.451 CentOs Invalid date On Jenkins startup after CVS plugin 2.0 upgrade. Changelogs disappear from GUI - Key: JENKINS-13017 URL: https://issues.jenkins-ci.org/browse/JENKINS-13017 Project: Jenkins Issue Type: Bug Components: cvs Affects Versions: current Environment: Jenkins 1.451 CentOs Reporter: G. Ann Campbell Just tried to upgrade to 2.0. Jenkinks log give exceptions on startup none of my projects display any changes / change logs. Reverting restores change logs. Here's a sample stacktrace java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.commons.beanutils.PropertyUtilsBean.invokeMethod(PropertyUtilsBean.java:2155) at org.apache.commons.beanutils.PropertyUtilsBean.setSimpleProperty(PropertyUtilsBean.java:2141) at org.apache.commons.beanutils.PropertyUtilsBean.setNestedProperty(PropertyUtilsBean.java:1948) at org.apache.commons.beanutils.PropertyUtilsBean.setProperty(PropertyUtilsBean.java:2054) at org.apache.commons.beanutils.BeanUtilsBean.setProperty(BeanUtilsBean.java:1015) at org.apache.commons.beanutils.BeanUtils.setProperty(BeanUtils.java:456) at org.apache.commons.digester.BeanPropertySetterRule.end(BeanPropertySetterRule.java:197) at org.apache.commons.digester.Digester.endElement(Digester.java:1130) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(AbstractSAXParser.java:601) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(XMLDocumentFragment ScannerImpl.java:1782) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocu mentFragmentScannerImpl.java:2938) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentSc annerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) at org.apache.commons.digester.Digester.parse(Digester.java:1631) at hudson.scm.CVSChangeLogSet.parse(CVSChangeLogSet.java:113) at hudson.scm.CVSChangeLogParser.parse(CVSChangeLogParser.java:43) at hudson.scm.CVSChangeLogParser.parse(CVSChangeLogParser.java:38) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:808) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:782) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:356) at hudson.model.User.getBuilds(User.java:390) at hudson.WebAppMain$2$1.doRun(WebAppMain.java:225) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:512) at java.util.TimerThread.run(Timer.java:462) Caused by: java.lang.RuntimeException: Invalid date at hudson.scm.CVSChangeLogSet$CVSChangeLog.setDate(CVSChangeLogSet.java:235) ... 34 more Caused by: java.text.ParseException: Unparseable date: 2012-02-29 at java.text.DateFormat.parse(DateFormat.java:337) at hudson.scm.CVSChangeLogSet$CVSChangeLog.setDate(CVSChangeLogSet.java:232) ... 34 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
