[JIRA] (JENKINS-58637) .jenkinsignore
Title: Message Title Kyle Leinen commented on JENKINS-58637 Re: .jenkinsignore Igal Gluh this feature got be really excited as it would solve the same problem for my team that Jesse Glick has. I've found that while the "Cancel build excluded regions strategy" works without issue, I am unable to get the new "Cancel ci by ignore file strategy" working using a .jenkinsignore file that has the same contents. I think these are valid ANT pattern files, so I'm not sure what I am doing wrong. Here is the contents if my .jenkinsignore: *.md LICENSE .gitignore .jenkinsignore review.conf I have also tried the following with no success: *.md /LICENSE /.gitignore /.jenkinsignore /review.conf Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-47773) email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
Title: Message Title
Kyle Leinen commented on JENKINS-47773
Re: email-ext cannot expand ${FAVORITE_USERS_EMAIL} macro in pipeline
How did that text file get generated?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186268.1509557824000.14662.1563387060335%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title Kyle Leinen edited a comment on JENKINS-36195 Re: Pipeline polling ignores special polling rules From reading the original ticket notes belong to along with the responses, I think this one is more in regard to alignment with special rules around a single repository and not multiple repos. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172167.1466697529000.22914.1557457261414%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title Kyle Leinen commented on JENKINS-36195 Re: Pipeline polling ignores special polling rules From reading the original ticket notes belong to the responses, I think this one is more in regard to special rules around a single repository and not multiple repos. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172167.1466697529000.22360.1557422581280%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52854) NPE with Cppcheck plugin 1.23
Title: Message Title Kyle Leinen commented on JENKINS-52854 Re: NPE with Cppcheck plugin 1.23 Marco Steffan Any movement on this fix? I am going to build the snapshot in the interim, but it would be nice to have this merged and officially released. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48556) timestamps() randomly not recognized as a valid option
Title: Message Title Kyle Leinen commented on JENKINS-48556 Re: timestamps() randomly not recognized as a valid option We just saw this on over 15 brand new pipeline builds (new repos in Github with Jenkinsfiles) on a server that was just updated to latest LTS with latest plugins. It only showed up on the first build, subsequent rebuilds worked as expected. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32483) java.io.IOException: Failed to write url on api/xml?depth=1
Title: Message Title Kyle Leinen edited a comment on JENKINS-32483 Re: java.io.IOException: Failed to write url on api/xml?depth=1 My team is also experiencing the same issue. We have verified that it only occurs with multijob and are currently only able to get it to happen when using a "?depth=" argument (we use "?depth=1" with either xml, json, or python; it occurs with all three). Multi-Job Plugin: 1.21 Jenkins: 1.651.3 (LTS)Java: 1.7.0_80-b15OS: RHEL 6.5Any update on if this is being looked at or prioritized? Is this potentially fixed in 1.22? I can give that a try and post back. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32483) java.io.IOException: Failed to write url on api/xml?depth=1
Title: Message Title Kyle Leinen commented on JENKINS-32483 Re: java.io.IOException: Failed to write url on api/xml?depth=1 My team is also experiencing the same issue. We have verified that it only occurs with multijob and are currently only able to get it to happen when using a "?depth=" argument (we use "?depth=1" with either xml, json, or python; it occurs with all three). Jenkins: 1.651.3 (LTS) Java: 1.7.0_80-b15 OS: RHEL 6.5 Any update on if this is being looked at or prioritized? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Kyle Leinen commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module We are also seeing this issue, but we didn't change Jenkins versions, just after updated to Oracle Java 1.8. 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] [multijob-plugin] (JENKINS-26738) Multi Job Plugin failed to inject variables into build
Title: Message Title Kyle Leinen commented on JENKINS-26738 Re: Multi Job Plugin failed to inject variables into build I have also recently seen this problem. I am running Jenkins 1.611 via RHEL6.5/Tomcat7/Java7 using version 1.16 of the plugin. Please let me know if there are any logs/traces that would need to be gathered to help this get resolved. 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] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Kyle Leinen commented on JENKINS-27739 Re: Changes to slave environment variables are ignored by master My team has also been experiencing this issue. Our server is running from RedHat Ent. Linux 6.5/Tomcat7 and we are seeing this on nodes that are both WinXP or Win7. We are not seeing this on nodes that are linux-based. One important item we saw and have confirmed is that new environment variables get added/update/remove just fine, but environment variables at the time the node was first connected seem to be locked in and won't update/remove. Our current workaround is to delete the node in Jenkins and recreate it. 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] [mercurial-plugin] (JENKINS-27316) Exception thrown when using variable in Mercurial Repo URL
Kyle Leinen commented on JENKINS-27316 Exception thrown when using variable in Mercurial Repo URL We currently managed all of our feature branches through the usage of our Job DSL scripting (which we are peeking at the Workflow plugin set for a next revision of that). What our one-off jobs allow for is to have changesets built that don't exist on our central server. This allows for developers to get some CI system time on their changeset without having to create a specific branch and job for their feature. Just to give a view of scale here, if we had to create a branch build for every story we have in flight, we would have over 200 branch build for just one of our projects. Currently we restrict our branch builds to project teams, which still is around 30. Anyways, if being able to "hide" or disable this warning is difficult or not in the direction you want to take, no worries there. We have been thinking of writing a script that parses out and removes that warning from the logs via a cron script. That way it can still be generated but we can throw it away since it is noise for us, but maybe not for others. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-27316) Exception thrown when using variable in Mercurial Repo URL
Kyle Leinen commented on JENKINS-27316 Exception thrown when using variable in Mercurial Repo URL Your assumption is correct. SCM polling is not enabled in this job. The job in question does not participate in polling as it is a "one-off" job, which uses Mercurial's distributed nature to harness our Jenkins instance's processing power for building changesets that are on a developer's local machine and not necessarily on the central Mercurial server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-27316) Exception thrown when using variable in Mercurial Repo URL
Kyle Leinen commented on JENKINS-27316 Exception thrown when using variable in Mercurial Repo URL I realize it may add complexity, but maybe a java opt flag to enable/disable this output would be best. That way those who want to see it can keep it, and those who don't, like my team, can turn it off. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-27316) Exception thrown when using variable in Mercurial Repo URL
Kyle Leinen commented on JENKINS-27316 Exception thrown when using variable in Mercurial Repo URL That is correct. It functionally works great. No complaints there. Hiding this stack trace would be OK IMHO. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-27316) Exception thrown when using variable in Mercurial Repo URL
Kyle Leinen
updated JENKINS-27316
Exception thrown when using variable in Mercurial Repo URL
Change By:
Kyle Leinen
(10/Mar/15 4:11 PM)
Description:
Wehaveone-offjobsconfiguredtoallowforbuildingofchangesetsfromauserslocalrepository,whichmeansthattherepoURLisnotastaticentity,butinsteadaparametertothejob.WealsohavejobsthataretriggeredtopollforchangesbyourHgserver.Thisworksgreat,exceptthattheurlsettingsvaluedoesnotinteractwellwiththepollingfunctionalityoftheMercurialplugin.EverytimeourHgservertellsJenkinstopollforchanges,allofourone-offconfigurationsthrowexceptionstothejenkinslogthatlooklikethefollowing:{code}Mar10,201510:43:46AMhudson.plugins.mercurial.MercurialStatushandleNotifyCommitINFO:for
vtcorefs
foocomponent
.
platform_health-dev.
wr5-arm:http://scm.
isg
foocompany
.
deere.
com/hg/
gsix-components
foocomponent
/
vehiclecommonfs/
[JIRA] [mercurial-plugin] (JENKINS-27316) Exception thrown when using variable in Mercurial Repo URL
Kyle Leinen
created JENKINS-27316
Exception thrown when using variable in Mercurial Repo URL
Issue Type:
Bug
Assignee:
Jesse Glick
Attachments:
mercurial_screenshot.png
Components:
mercurial-plugin
Created:
10/Mar/15 4:09 PM
Description:
We have one-off jobs configured to allow for building of changesets from a user's local repository, which means that the repo URL is not a static entity, but instead a parameter to the job. We also have jobs that are triggered to poll for changes by our Hg server.
This works great, except that the url setting's value does not interact well with the polling functionality of the Mercurial plugin. Everytime our Hg server tells Jenkins to poll for changes, all of our one-off configurations throw exceptions to the jenkins log that look like the following:
Mar 10, 2015 10:43:46 AM hudson.plugins.mercurial.MercurialStatus handleNotifyCommit
INFO: for vtcorefs.platform_health-dev.wr5-arm: http://scm.isg.deere.com/hg/gsix-components/vehiclecommonfs/ vs. ${REP
O_URL}
Mar 10, 2015 10:43:46 AM hudson.plugins.mercurial.MercurialStatus looselyMatches
SEVERE: could not parse repository uri ${REPO_URL}
java.net.URISyntaxException: Illegal character in path at index 1: ${REPO_URL}
at java.net.URI$Parser.fail(Unknown Source)
at java.net.URI$Parser.checkChars(Unknown Source)
at java.net.URI$Parser.parseHierarchical(Unknown Source)
at java.net.URI$Parser.parse(Unknown Source)
at java.net.URI.init(Unknown Source)
at hudson.plugins.mercurial.MercurialStatus.looselyMatches(MercurialStatus.java:60)
at hudson.plugins.mercurial.MercurialStatus.handleNotifyCommit(MercurialStatus.java:105)
at hudson.plugins.mercurial.MercurialStatus.doNotifyCommit(MercurialStatus.java:75)
at sun.reflect.GeneratedMethodAccessor4421.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95)
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 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176)
at
[JIRA] [envinject-plugin] (JENKINS-14437) envinject fails to really set/override build parameters
Kyle Leinen commented on JENKINS-14437 envinject fails to really set/override build parameters We are also experiencing this on multiple systems. Jenkins: 1.593 EnvInject: 1.90 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-monitor] (JENKINS-24048) Ability to set default column count and font size in configure page
Kyle Leinen created JENKINS-24048 Ability to set default column count and font size in configure page Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: build-monitor Created: 30/Jul/14 7:09 PM Description: Since a clearing of the browser cache or reload of the browser seems to clear these settings, it makes viewing the page on automated build screens somewhat hard to manage. It would be nice if the default values for the column count and font size could be defined in the Jenkins view configuration page. That would allow automated screens to be easy to setup without removing the ability for each person to customize per their browser. Project: Jenkins Priority: Major Reporter: Kyle Leinen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-monitor] (JENKINS-20852) Support more build statuses: unstable, not-yet-built
Kyle Leinen commented on JENKINS-20852 Support more build statuses: unstable, not-yet-built I would also find value in this, especially the support for unstable (yellow). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-19705) Credentials support for Mercurial SCM
Kyle Leinen resolved JENKINS-19705 as Fixed Credentials support for Mercurial SCM This method has resolved my issue and brought the functionality that I need. Thanks!! Change By: Kyle Leinen (11/Jun/14 2:02 AM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21317) Build Time Trend doesn't load, always says Computation in Progress
Kyle Leinen created JENKINS-21317 Build Time Trend doesnt load, always says Computation in Progress Issue Type: Bug Assignee: Unassigned Components: core Created: 09/Jan/14 7:59 PM Description: Recently updated from 1.538 to 1.545. Users are now reporting that the build time trend table within any job does not display in Internet Explorer, Firefox, or Chrome. The chart/graph displays just fine with valid information, but the table doesn't ever display. The progress bar that is above where the table would display continually says "Computation in Progress". So far, no user is showing an page load errors and I am not detecting any errors via the server logs. I see that this may be related to JENKINS-20892. Let me know what information that I should gather to help debug this issue. Environment: Jenkins 1.545 Project: Jenkins Priority: Minor Reporter: Kyle Leinen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-10537) java.net.SocketTimeoutException: Read timed out
Kyle Leinen commented on JENKINS-10537 java.net.SocketTimeoutException: Read timed out My team is also seeing this. We are running Jenkins 1.538 with slave version 2.32. The master server is RHEL6 with Oracle Java 1.7.0_05 and the slaves are Win7 running Oracle Java 1.7.0_05. Across 25 JNLP nodes, we see around 10 drop-offs per week. We are seeing the same exception as the others reports above. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-10342) Build triggered by promotion fails
Kyle Leinen commented on JENKINS-10342 Build triggered by promotion fails Still receiving this: downstream-buildview = 1.8 Jenkins = 1.491 Promoted Builds = 2.8 Parameterized Trigger = 2.16 11:07:14 Started by upstream project "/promotion/Deployed" build number 2 11:07:14 FATAL: null 11:07:14 java.lang.NullPointerException 11:07:14 at org.jvnet.hudson.plugins.DownstreamBuildViewUpdateListener.onStarted(DownstreamBuildViewUpdateListener.java:85) 11:07:14 at org.jvnet.hudson.plugins.DownstreamBuildViewUpdateListener.onStarted(DownstreamBuildViewUpdateListener.java:46) 11:07:14 at hudson.model.listeners.RunListener.fireStarted(RunListener.java:188) 11:07:14 at hudson.model.Run.execute(Run.java:1497) 11:07:14 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 11:07:14 at hudson.model.ResourceController.execute(ResourceController.java:88) 11:07:14 at hudson.model.Executor.run(Executor.java:236) I see there is a pull request in Git to have this fixed, but it is over 8 months old. Any chance of getting this in? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-5682) when keeping past reports, project should link to latest build report
Kyle Leinen updated JENKINS-5682 when keeping past reports, project should link to latest build report Change By: Kyle Leinen (09/Jan/13 4:31 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
[JIRA] (JENKINS-11689) HTMLPublisher does not publish latest report to project page if build fails
Kyle Leinen commented on JENKINS-11689 HTMLPublisher does not publish latest report to project page if build fails Any updates on this? I am very interested in getting this corrected or having a setting added to switch the behavior. This message is automatically generated by JIRA. 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-12610) java.io.IOException: Unable to delete - Deleting Project
Kyle Leinen commented on JENKINS-12610 java.io.IOException: Unable to delete - Deleting Project I am also seeing this problem running from Windows XP. It started happenning when I upgraded from 1.471 to 1.480. This message is automatically generated by JIRA. 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-12610) java.io.IOException: Unable to delete - Deleting Project
Kyle Leinen edited a comment on JENKINS-12610 java.io.IOException: Unable to delete - Deleting Project I am also seeing this problem running from Windows XP. It started happening when I upgraded from 1.471 to 1.480. This message is automatically generated by JIRA. 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-14699) hg clone adding @2 to end of clone destination path
Kyle Leinen
updated JENKINS-14699
hg clone adding @2 to end of clone destination path
Change By:
Kyle Leinen
(06/Aug/12 8:20 PM)
Description:
Intermittently,theMercurialplug-inwillattempttoclonetoaworkspacethatdoesntexistbecauseitisadding@2totheendoftheworkspacepath.Thisresultsinaclonethatisunexpectedandunnecessary.CONSOLEOUTPUT--13:55:22StartedbyanSCMchange13:55:22[EnvInject]-Loadingnodeenvironmentvariables.13:55:22BuildingremotelyonNODE_NAME_REMOVEDinworkspace/var/lib/jenkins/workspace/JOBNAME_REMOVED@213:55:22ChangingBUILD_IDvariable(jobbuildtime)withthedatepattern-MM-ddTHH:mm:ssZ.13:55:22$/usr/bin/hgclone--revdefault--noupdatehttp://
wdxivsgsdci01.jdnet.deere.com
SERVER_ADDRESS_REMOVED
/hgweb/hgweb.cgi/GSD/var/lib/jenkins/workspace/JOBNAME_REMOVED@214:24:19Buildwasaborted14:24:19AbortedbyUSERNAME_REMOVED14:24:19Archivingartifacts14:24:19ChangingBUILD_IDvariable(jobbuildtime)withthedatepattern-MM-ddTHH:mm:ssZ.14:24:19addingchangesets14:24:19addingmanifests14:24:19addingfilechanges14:24:19transactionabort!14:24:19Recordingtestresults14:24:19ChangingBUILD_IDvariable(jobbuildtime)withthedatepattern-MM-ddTHH:mm:ssZ.14:24:19Notestreportfileswerefound.Configurationerror?14:24:19Recordingfingerprints14:24:19ChangingBUILD_IDvariable(jobbuildtime)withthedatepattern-MM-ddTHH:mm:ssZ.14:24:19ChangingBUILD_IDvariable(jobbuildtime)withthedatepattern-MM-ddTHH:mm:ssZ.14:24:19Descriptionset:MERCURIAL_REVISION:${MERCURIAL_REVISION}14:24:19ChangingBUILD_IDvariable(jobbuildtime)withthedatepattern-MM-ddTHH:mm:ssZ.14:24:19Finished:ABORTED
This message is automatically generated by JIRA.
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-14699) hg clone adding @2 to end of clone destination path
Kyle Leinen
created JENKINS-14699
hg clone adding @2 to end of clone destination path
Issue Type:
Bug
Affects Versions:
current
Assignee:
Kohsuke Kawaguchi
Components:
mercurial
Created:
06/Aug/12 8:19 PM
Description:
Intermittently, the Mercurial plug-in will attempt to clone to a workspace that doesn't exist because it is adding "@2" to the end of the workspace path. This results in a clone that is unexpected and unnecessary.
CONSOLE OUTPUT
--
13:55:22 Started by an SCM change
13:55:22 EnvInject - Loading node environment variables.
13:55:22 Building remotely on NODE_NAME_REMOVED in workspace /var/lib/jenkins/workspace/JOBNAME_REMOVED@2
13:55:22 Changing BUILD_ID variable (job build time) with the date pattern -MM-dd'T'HH:mm:ssZ.
13:55:22 $ /usr/bin/hg clone --rev default --noupdate http://wdxivsgsdci01.jdnet.deere.com/hgweb/hgweb.cgi/GSD /var/lib/jenkins/workspace/JOBNAME_REMOVED@2
14:24:19 Build was aborted
14:24:19 Aborted by USERNAME_REMOVED
14:24:19 Archiving artifacts
14:24:19 Changing BUILD_ID variable (job build time) with the date pattern -MM-dd'T'HH:mm:ssZ.
14:24:19 adding changesets
14:24:19 adding manifests
14:24:19 adding file changes
14:24:19 transaction abort!
14:24:19 Recording test results
14:24:19 Changing BUILD_ID variable (job build time) with the date pattern -MM-dd'T'HH:mm:ssZ.
14:24:19 No test report files were found. Configuration error?
14:24:19 Recording fingerprints
14:24:19 Changing BUILD_ID variable (job build time) with the date pattern -MM-dd'T'HH:mm:ssZ.
14:24:19 Changing BUILD_ID variable (job build time) with the date pattern -MM-dd'T'HH:mm:ssZ.
14:24:19 Description set: MERCURIAL_REVISION: ${MERCURIAL_REVISION}
14:24:19 Changing BUILD_ID variable (job build time) with the date pattern -MM-dd'T'HH:mm:ssZ.
14:24:19 Finished: ABORTED
Environment:
Master is Jenkins 1.471 running on Windows XP 64-bit using Mercurial 2.0.2 via TortoiseHG 2.2.2.
Slave Node is running (via SSH) on Ubuntu 10.04 64-bit using Mercurial 2.3 via TortoiseHG 2.1.
Project:
Jenkins
Priority:
Major
Reporter:
Kyle Leinen
This message is automatically generated by JIRA.
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-14699) hg clone adding @2 to end of clone destination path
Kyle Leinen
updated JENKINS-14699
hg clone adding @2 to end of clone destination path
Change By:
Kyle Leinen
(06/Aug/12 8:20 PM)
Description:
Intermittently,theMercurialplug-inwillattempttoclonetoaworkspacethatdoesntexistbecauseitisadding@2totheendoftheworkspacepath.Thisresultsinaclonethatisunexpectedandunnecessary.CONSOLEOUTPUT--13:55:22StartedbyanSCMchange13:55:22[EnvInject]-Loadingnodeenvironmentvariables.13:55:22BuildingremotelyonNODE_NAME_REMOVEDinworkspace/var/lib/jenkins/workspace/JOBNAME_REMOVED@213:55:22ChangingBUILD_IDvariable(jobbuildtime)withthedatepattern-MM-ddTHH:mm:ssZ.13:55:22$/usr/bin/hgclone--revdefault--noupdatehttp://
SERVER_ADDRESS_REMOVED
REPO_ADDRESS_REMOVED
/
hgweb/hgweb.cgi/GSD/
var/lib/jenkins/workspace/JOBNAME_REMOVED@214:24:19Buildwasaborted14:24:19AbortedbyUSERNAME_REMOVED14:24:19Archivingartifacts14:24:19ChangingBUILD_IDvariable(jobbuildtime)withthedatepattern-MM-ddTHH:mm:ssZ.14:24:19addingchangesets14:24:19addingmanifests14:24:19addingfilechanges14:24:19transactionabort!14:24:19Recordingtestresults14:24:19ChangingBUILD_IDvariable(jobbuildtime)withthedatepattern-MM-ddTHH:mm:ssZ.14:24:19Notestreportfileswerefound.Configurationerror?14:24:19Recordingfingerprints14:24:19ChangingBUILD_IDvariable(jobbuildtime)withthedatepattern-MM-ddTHH:mm:ssZ.14:24:19ChangingBUILD_IDvariable(jobbuildtime)withthedatepattern-MM-ddTHH:mm:ssZ.14:24:19Descriptionset:MERCURIAL_REVISION:${MERCURIAL_REVISION}14:24:19ChangingBUILD_IDvariable(jobbuildtime)withthedatepattern-MM-ddTHH:mm:ssZ.14:24:19Finished:ABORTED
This message is automatically generated by JIRA.
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-6565) Hudson stuck on inexistent job
[ https://issues.jenkins-ci.org/browse/JENKINS-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162901#comment-162901 ] Kyle Leinen commented on JENKINS-6565: -- I am also seeing this. The job cannot be cleared/cancelled without restarting Jenkins completely, which is a pain. Hudson stuck on inexistent job -- Key: JENKINS-6565 URL: https://issues.jenkins-ci.org/browse/JENKINS-6565 Project: Jenkins Issue Type: Bug Components: locks-and-latches Reporter: rombert Assignee: stephenconnolly Priority: Blocker Attachments: hudon-stuck-system-information.txt, hudson-stuck-enabled-plugins.txt, hudson-stuck-executors.png, hudson-stuck-home-page-queue.png, hudson-stuck-thread-dump.txt After a couple of days, Hudson seems to see a a 'phantom' build queued , which does not execute at all, but it blocks the next job from running. The currently executing build is 'Collectors' and the stuck build is 'SportsEngine-Collection' . The stuck build is a Maven2 build, using the locks-and-latches plugin, polling SVN every minute. -- 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-12732) Fingerprint failure in copy artifact 1.21, even though fingerprinting is turned off in my jobs
[ https://issues.jenkins-ci.org/browse/JENKINS-12732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161974#comment-161974 ] Kyle Leinen commented on JENKINS-12732: --- I am also seeing this with a job that has fingerprinting turned on. It seems to work for many configurations of a matrix job, but it randomly doesn't work for a few of the configurations. The ones it fails on are also random, making this issue very hard to reproduce. 12:36:44 Copied 1 artifact from GSix_Squish_UX » Squish_10in_Desktop,Service_Center_Diagnostic_Address build number 317 12:36:44 Copied 1 artifact from GSix_Squish_UX » Squish_10in_Desktop,Service_Center_Diagnostic_Trouble_Codes build number 317 12:36:44 Copied 1 artifact from GSix_Squish_UX » Squish_10in_Desktop,Service_Center_General build number 317 12:36:44 Copied 1 artifact from GSix_Squish_UX » Squish_10in_Desktop,Shift_Track_Integration build number 317 12:36:44 Copied 1 artifact from GSix_Squish_UX » Squish_10in_Desktop,StraightTrack_Methods build number 317 12:36:44 ERROR: Failed to copy artifacts from GSix_Squish_UX with filter: ** 12:36:44 hudson.util.IOException2: Failed to copy C:\Hudson\jobs\GSix_Squish_UX\configurations\axis-Platform\Squish_10in_Desktop\axis-SuiteName\Third_Party_Apps\builds\2012-04-24_12-04-35\archive\SQUISH_Tests_Results\Third_Party_Apps-RESULTS.xml to C:\Jenkins\workspace\GSix_Squish_Results\SQUISH_Tests_Results\Platform=Squish_10in_Desktop,SuiteName=Third_Party_Apps\Third_Party_Apps-RESULTS.xml 12:36:44at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:91) 12:36:44at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:248) 12:36:44at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:211) 12:36:44at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 12:36:44at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:705) 12:36:44at hudson.model.Build$RunnerImpl.build(Build.java:178) 12:36:44at hudson.model.Build$RunnerImpl.doRun(Build.java:139) 12:36:44at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:475) 12:36:44at hudson.model.Run.run(Run.java:1421) 12:36:44at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 12:36:44at hudson.model.ResourceController.execute(ResourceController.java:88) 12:36:44at hudson.model.Executor.run(Executor.java:238) 12:36:44 Caused by: hudson.util.IOException2: remote file operation failed: C:\Jenkins\workspace\GSix_Squish_Results\SQUISH_Tests_Results\Platform=Squish_10in_Desktop,SuiteName=Third_Party_Apps\Third_Party_Apps-RESULTS.xml at hudson.remoting.Channel@5f6994db:WDXISGGSIXCT1 12:36:44at hudson.FilePath.act(FilePath.java:828) 12:36:44at hudson.FilePath.act(FilePath.java:814) 12:36:44at hudson.FilePath.touch(FilePath.java:1160) 12:36:44at hudson.plugins.copyartifact.FingerprintingCopyMethod.copyOne(FingerprintingCopyMethod.java:79) 12:36:44... 11 more 12:36:44 Caused by: java.io.IOException: Failed to set the timestamp of C:\Jenkins\workspace\GSix_Squish_Results\SQUISH_Tests_Results\Platform=Squish_10in_Desktop,SuiteName=Third_Party_Apps\Third_Party_Apps-RESULTS.xml to 1335287115000 12:36:44at hudson.FilePath$19.invoke(FilePath.java:1166) 12:36:44at hudson.FilePath$19.invoke(FilePath.java:1160) 12:36:44at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154) 12:36:44at hudson.remoting.UserRequest.perform(UserRequest.java:118) 12:36:44at hudson.remoting.UserRequest.perform(UserRequest.java:48) 12:36:44at hudson.remoting.Request$2.run(Request.java:287) 12:36:44at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 12:36:44at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) 12:36:44at java.util.concurrent.FutureTask.run(Unknown Source) 12:36:44at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) 12:36:44at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) 12:36:44at hudson.remoting.Engine$1$1.run(Engine.java:60) 12:36:44at java.lang.Thread.run(Unknown Source) 12:36:44 Build step 'Copy artifacts from another project' marked build as failure 12:36:44 Archiving artifacts 12:36:44 Recording fingerprints Fingerprint failure in copy artifact 1.21, even though fingerprinting is turned off in my jobs -- Key: JENKINS-12732 URL: https://issues.jenkins-ci.org/browse/JENKINS-12732 Project: Jenkins Issue Type: Bug Components: copyartifact Environment: Linux
[JIRA] (JENKINS-10544) shelve project button missing on some projects
[ https://issues.jenkins-ci.org/browse/JENKINS-10544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161670#comment-161670 ] Kyle Leinen commented on JENKINS-10544: --- I am also seeing this on my Jenkins instance (v1.460) running RHEL. Is anyone looking into this? shelve project button missing on some projects Key: JENKINS-10544 URL: https://issues.jenkins-ci.org/browse/JENKINS-10544 Project: Jenkins Issue Type: Bug Components: shelve-project-plugin Reporter: Peter Pawlowski Assignee: ashlux Attachments: config.xml With the Shelve Plugin version 1.2, on many Jenkins versions, we have seen the Shelve Project button missing on some projects. We haven't been able to see any pattern. Most of our projects are matrix builds, and we've seen this issue on some matrix projects but not others. I don't know what to look for or what other info we might provide to help investigate this issue -- ask for anything and I'll do my best to provide it. -- 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
