[JIRA] [core] (JENKINS-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
Steffen Sledz created JENKINS-25788 WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with Issue Type: Bug Assignee: Unassigned Components: core Created: 26/Nov/14 8:56 AM Description: Since the latest update the server log contains the following warnings for various jobs. WARNING: hudson.model.FreeStyleProject@9a4e77f[projectX] did not contain projectX #584 to begin with Environment: Fedora release 20 (Heisenbug) x86_64 OpenJDK Runtime Environment 1.7.0_71-mockbuild_2014_10_15_17_02-b00 Jenkins ver. 1.591 Project: Jenkins Labels: warnings free-style Priority: Minor Reporter: Steffen Sledz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
Steffen Sledz commented on JENKINS-25788 WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with see also https://github.com/jenkinsci/jenkins/pull/1440 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
Steffen Sledz commented on JENKINS-25788 WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with It seems that this is related to an incomplete Last Changes list. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25788) WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with
Steffen Sledz commented on JENKINS-25788 WARNING: hudson.model.FreeStyleProject@9a4e77f[...] did not contain ... #584 to begin with In jobs where this warning occurs the displayed Last Changes list does contain items for older builds only. The most recent changes are missing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-25787) Repository Browser broken with Multiple SCMs plugin
Steffen Sledz commented on JENKINS-25787 Repository Browser broken with Multiple SCMs plugin What a pity. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25787) Repository Browser broken with Multiple SCMs plugin
Steffen Sledz created JENKINS-25787 Repository Browser broken with Multiple SCMs plugin Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 26/Nov/14 7:18 AM Description: If Multiple SCMs is choosen in the Source-Code-Management section it is not possible to select a Repository Browser. The only option is (Auto). If Git is choosen the selection works well. Environment: Fedora release 20 (Heisenbug) x86_64 OpenJDK Runtime Environment 1.7.0_71-mockbuild_2014_10_15_17_02-b00 Jenkins ver. 1.591 git plugin 2.3 multiple-scms plugin 0.3 Project: Jenkins Labels: git-plugin scm multiple-scms Priority: Major Reporter: Steffen Sledz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25758) NPE when triggering downstream job (again)
Steffen Sledz created JENKINS-25758 NPE when triggering downstream job (again) Issue Type: Bug Assignee: Unassigned Components: core Created: 24/Nov/14 2:30 PM Description: We've some trigger-only jobs which check for repo changes only without any build step. They are used to trigger some downstream jobs only but fire this NPE: First time build. Skipping changelog. Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered FATAL: null java.lang.NullPointerException at hudson.model.Result.isBetterOrEqualTo(Result.java:125) at jenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:133) at jenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:83) at jenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:140) at hudson.tasks.BuildTrigger.execute(BuildTrigger.java:243) at hudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:699) at hudson.model.Build$BuildExecution.cleanUp(Build.java:194) at hudson.model.Run.execute(Run.java:1805) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) There are a lot of JENKINS-Issues related to similar problems. But all of them are resolved fixed, cannot reproduce, or duplicated. So this seems to be a new problem. Environment: Jenkins 1.590 Fedora release 20 (Heisenbug) x86_64 OpenJDK Runtime Environment 1.7.0_71-mockbuild_2014_10_15_17_02-b00 Project: Jenkins Priority: Major Reporter: Steffen Sledz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25758) NPE when triggering downstream job (again)
Steffen Sledz
updated JENKINS-25758
NPE when triggering downstream job (again)
Change By:
Steffen Sledz
(24/Nov/14 2:54 PM)
Description:
Wevesome
trigger-only
jobswhichcheckforrepochangesonlywithoutanybuildstep.Theyareusedtotriggersomedownstreamjobs
onlybut
.Butinsteadoftriggeringthejobsthey
firethisNPE:
{noformat}Firsttimebuild.Skippingchangelog.Warning:youhavenopluginsprovidingaccesscontrolforbuilds,sofallingbacktolegacybehaviorofpermittinganydownstreambuildstobetriggeredFATAL:nulljava.lang.NullPointerException athudson.model.Result.isBetterOrEqualTo(Result.java:125) atjenkins.triggers.ReverseBuildTrigger.shouldTrigger(ReverseBuildTrigger.java:133) atjenkins.triggers.ReverseBuildTrigger.access$000(ReverseBuildTrigger.java:83) atjenkins.triggers.ReverseBuildTrigger$1.shouldTriggerBuild(ReverseBuildTrigger.java:140) athudson.tasks.BuildTrigger.execute(BuildTrigger.java:243) athudson.model.AbstractBuild$AbstractBuildExecution.cleanUp(AbstractBuild.java:699) athudson.model.Build$BuildExecution.cleanUp(Build.java:194) athudson.model.Run.execute(Run.java:1805) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:240){noformat}TherearealotofJENKINS-Issuesrelatedtosimilarproblems.Butallofthemareresolved*fixed*,*cannotreproduce*,or*duplicated*.Sothisseemstobeanewproblem.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-25758) NPE when triggering downstream job (again)
Steffen Sledz resolved JENKINS-25758 as Duplicate NPE when triggering downstream job (again) Change By: Steffen Sledz (25/Nov/14 7:54 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-25758) NPE when triggering downstream job (again)
Steffen Sledz commented on JENKINS-25758 NPE when triggering downstream job (again) You're right. After resetting the result options for all downstream projects everything works 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-23466) 15 Minutes inactivity after Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to b
Steffen Sledz created JENKINS-23466 15 Minutes inactivity after Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 17/Jun/14 12:36 PM Description: After a Jenkins update we noticed that our jobs which trigger other jobs print out a warning "Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered" And after that the job idles for about 15 minutes before it ends a the triggered job starts. Environment: Linux, Fedora release 20, x86_64, java-1.7.0-openjdk-1.7.0.60-2.4.7.0.fc20.x86_64 Project: Jenkins Priority: Major Reporter: Steffen Sledz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-23466) 15 Minutes inactivity after Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to b
Steffen Sledz updated JENKINS-23466 15 Minutes inactivity after Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered Here it is (see attachment stackdump-jenkins.txt). The initial job in this case is hipos-dfe-closed-hikirk and it should trigger hipos-dfe-closed-publish. Change By: Steffen Sledz (17/Jun/14 1:37 PM) Attachment: stackdump-jenkins.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] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Steffen Sledz commented on JENKINS-21394 Avoid queuing request for workspace while node is offline @Mads I'have to correct my previous statements. Downgrade Jenkins itself to 1.559 or earlier leads to a different behaviour. The "We need to schedule ... (all_suitable_nodes_are_offline)" is gone. But instead the affected jobs are triggered cyclic in a loop (each time scm checks for updates). Downgrade multiple SCM plugin to 0.2 has no influence. Downgrade GIT plugin to 2.0 completely fixes the problem(s). So may be we have two different (but related ?) problems here. Sorry for the confusion. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-21394) Avoid queuing request for workspace while node is offline
Steffen Sledz commented on JENKINS-21394 Avoid queuing request for workspace while node is offline Same issue here with 1.560 and Multiple SCMs plugin (0.3) and GIT plugin (2.2.1) runninf a master without any slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21394) Avoid queuing request for workspace while node is offline
Steffen Sledz commented on JENKINS-21394 Avoid queuing request for workspace while node is offline @Mads We run jenkins 1.560 on CentOS (Linux). I tried to reproduce the behaviour with your testing repo. But this one worked without problems. One difference is that our repo uses git submodules. BTW, I've tried various downgrades: Downgrade Jenkins itself to 1.559 or earlier does not help. Downgrade multiple SCM plugin to 0.2 does not help. Downgrade GIT plugin to 2.0 does help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-21394) Avoid queuing request for workspace while node is offline
Steffen Sledz commented on JENKINS-21394 Avoid queuing request for workspace while node is offline https://groups.google.com/forum/#!topic/jenkinsci-users/HmNjml8LH20 describes workaround which works for me too. It is not really a good solution because it requires changes in all job 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] (JENKINS-10407) builds/1234, lastSuccessful and lastStable symlinks not created
Steffen Sledz commented on JENKINS-10407 builds/1234, lastSuccessful and lastStable symlinks not created Ping! The problem still exists in 1.505. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-13442) Default icon size should be configurable
Steffen Sledz commented on JENKINS-13442 Default icon size should be configurable Such an improvement would be great. This message is automatically generated by JIRA. 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-12316) git plugin should NOT tag every build by default
[ https://issues.jenkins-ci.org/browse/JENKINS-12316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161469#comment-161469 ] Steffen Sledz commented on JENKINS-12316: - Can't find this checkbox in Jenkins 1.459. :( Where did it went to? git plugin should NOT tag every build by default Key: JENKINS-12316 URL: https://issues.jenkins-ci.org/browse/JENKINS-12316 Project: Jenkins Issue Type: Bug Components: git Reporter: Alexey Java Assignee: abayer Attachments: jenkins git plugin fail.txt Git plugin automatically tries to add tags to my Git repository for every build (every 15 minutes or so!). that's very weird it does it automatically by default without me configuring this. I don't need hundreds of tags in Git repo... I suggest turning this OFF by default and allowing to configure it in Jenkins UI per build job. -- 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
