[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[1990.a...@gmail.com (JIRA)]

  
Alex Vesely
 edited a comment on  JENKINS-15156


Builds disappear from build history after completion
















Filed https://issues.jenkins-ci.org/browse/JENKINS-17265, as the issue still persists on 1.506.



























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-15156) Builds disappear from build history after completion

[1990.a...@gmail.com (JIRA)]

Alex Vesely
 commented on  JENKINS-15156


Builds disappear from build history after completion















Filed https://issues.jenkins-ci.org/browse/JENKINS-17265



























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-15156) Builds disappear from build history after completion

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 commented on  JENKINS-15156


Builds disappear from build history after completion















Better to not reopen long-running issues like this, which just results in an unreadable mess, and results in confusion about whether fixes were really applied. In this case they were, so it is likely that your problem has a different origin. Please file a fresh issue blocking JENKINS-8754 and clearly stating your Jenkins version, platform, list of plugins, exact observed behavior, and any other information you have which might help developers reproduce the problem or even guess at its cause.



























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-15156) Builds disappear from build history after completion

[alexandru.voicule...@gmail.com (JIRA)]

Voiculescu Bogdan Alexandru
 commented on  JENKINS-15156


Builds disappear from build history after completion















I confirm regression! please re-open this. Is getting annoying. 



























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-15156) Builds disappear from build history after completion

[reg.jenk...@stians.com (JIRA)]

Stian Indal Haugseth
 commented on  JENKINS-15156


Builds disappear from build history after completion















I have this problem in 1.500 and is still there after upgrading to 1.505.

I have several jobs and some or all of them loose all their build history. It seems a bit sporadic and I have not seen a pattern. I have renamed most of my jobs but history with the current name just disappeared on me 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/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[dogf...@java.net (JIRA)]

dogfood
 commented on  JENKINS-15156


Builds disappear from build history after completion















Integrated in  jenkins_main_trunk #2362
 JENKINS-15156 Noting. (Revision c596ed517c3f67bff172cfa0d3ac62e01d35dd54)

 Result = SUCCESS
Jesse Glick : c596ed517c3f67bff172cfa0d3ac62e01d35dd54
Files : 

	changelog.html





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-15156


Builds disappear from build history after completion















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/c596ed517c3f67bff172cfa0d3ac62e01d35dd54
Log:
  JENKINS-15156 Noting.



– 
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.






























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-15156) Builds disappear from build history after completion

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 commented on  JENKINS-15156


Builds disappear from build history after completion















Jenkins changelogs are not particularly trustworthy. The last commit did not add a changelog entry since it was done just to fix a test failure; I never reproduced any user-visible problem. I will add one 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/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[richard_merr...@yahoo.com (JIRA)]

Richard Merrill
 commented on  JENKINS-15156


Builds disappear from build history after completion















This issue number doesn't show up in the changelog for version 1.505 or 1.506. Is it really 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/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[jgl...@cloudbees.com (JIRA)]

  
Jesse Glick
 edited a comment on  JENKINS-15156


Builds disappear from build history after completion
















I think this can be considered fixed (for 1.505+ users), at least for core; plugins defining new project types with nested items (I am thinking of Ivy) may need to be patched too, TBD. Anyway if problems remain in newer builds it may be better to file a new bug linked to JENKINS-8754.



























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-15156) Builds disappear from build history after completion

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 resolved  JENKINS-15156 as Fixed


Builds disappear from build history after completion
















I think this can be considered fixed (for 1.505+ users), at least for core; plugins defining new project types with nested items (I am thinking of Ivy) may need to be patched too, TBD. Anyway if problems remain in newer builds it may be better to file a new bug linked to JENKINS-7854.





Change By:


Jesse Glick
(04/Mar/13 10:06 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/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[de...@ikedam.jp (JIRA)]

ikedam
 commented on  JENKINS-15156


Builds disappear from build history after completion















As described above, this problem seems to be fixed in 1.505 (with 42ee6113b7beff8dccba48593cefe0ad23636051).

But I am so annoyed with this problem that I wrote a plugin to fix the problem in multi-configuration projects.
https://github.com/ikedam/quickfix15156

This may be useful for those that want to fix this problem immediately, or those that do not want to update Jenkins in some reasons.



























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-15156) Builds disappear from build history after completion

[de...@ikedam.jp (JIRA)]

Yasuyuki IKEDA
 commented on  JENKINS-15156


Builds disappear from build history after completion















builds.dir of new created MatrixConfiguration is always set to null.
This causes Jenkins fail to load builds of configurations from the disk (AbstractLazyLoadRunMap.load).

MatrixConfiguration.builds (that is AbstractProject.builds) is initialized with new RunMap(), which sets builds.dir to null.
When the configuration is load from the disk, builds is correctly initialized and dir is set.

When new MatrixConfiguration is created (including the case a new axis is added), MatrixConfiguration.onLoad nor MatrixConfiguration.onCreatedFromScratch seem not called. It may concerned with this problem.



























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-15156) Builds disappear from build history after completion

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 commented on  JENKINS-15156


Builds disappear from build history after completion















@nickolay_martinov: I recently found an issue in matrix projects that was caught by tests under some conditions, and fixed it in trunk (1.505 I think). I cannot say that this will fix your issue, or even that the fix has any effect in real usage; just a hint.



























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-15156) Builds disappear from build history after completion

[finerrecli...@gmail.com (JIRA)]

Dave F
 commented on  JENKINS-15156


Builds disappear from build history after completion















A similar issue is affecting me in version 1.484. I can see all of the previous builds for a job on the left side of the page, but clicking on one of them shows no configurations available (there should be a "default" configuration). Because of this, I cannot view the console output of old builds. This affects all of my builds except for the most recently built job. 

I know the console output exists though because I can see it in $JENKINS_HOME/jobs//configurations/builds//log

Reloading configuration from disk actually made it worse, by losing the link to the most recently built job's build history.



























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-15156) Builds disappear from build history after completion

[nickolay.marti...@hp.com (JIRA)]

Nickolay Martinov
 commented on  JENKINS-15156


Builds disappear from build history after completion















With 1.502 problem is still there but it has changed a bit. Now i can see the history for project on left side but when i select particular build and try to narrow down to particular configuration of multi-configuration project it tells that configuration was never built. From the main page of multi-configuration project when i click on configurations i cannot see the history of builds. Reloading configuration from disk is still a workaround that can be used but still this blocks chained builds that try to copy artifacts from one build to another.



























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-15156) Builds disappear from build history after completion

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-15156


Builds disappear from build history after completion















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/matrix/MatrixProject.java
http://jenkins-ci.org/commit/jenkins/42ee6113b7beff8dccba48593cefe0ad23636051
Log:
  JENKINS-15156 Missing call to onCreatedFromScratch caused failures in MatrixProjectTest (when run from Surefire at least).



– 
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.






























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-15156) Builds disappear from build history after completion

[dogf...@java.net (JIRA)]

dogfood
 commented on  JENKINS-15156


Builds disappear from build history after completion















Integrated in  jenkins_main_trunk #2311
 JENKINS-15156 Missing call to onCreatedFromScratch caused failures in MatrixProjectTest (when run from Surefire at least). (Revision 42ee6113b7beff8dccba48593cefe0ad23636051)

 Result = SUCCESS
Jesse Glick : 42ee6113b7beff8dccba48593cefe0ad23636051
Files : 

	core/src/main/java/hudson/matrix/MatrixProject.java





























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-15156) Builds disappear from build history after completion

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 assigned  JENKINS-15156 to Unassigned



Builds disappear from build history after completion
















Change By:


Jesse Glick
(25/Feb/13 3:48 PM)




Assignee:


Jesse Glick



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 updated  JENKINS-15156


Builds disappear from build history after completion
















Change By:


Jesse Glick
(25/Feb/13 3:47 PM)




Status:


Reopened
Open



























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-15156) Builds disappear from build history after completion

[pedro.r...@mog-solutions.com (JIRA)]

pedro reis
 reopened  JENKINS-15156


Builds disappear from build history after completion
















Still disappearing at 1.502 (at least for failed builds)





Change By:


pedro reis
(25/Feb/13 3:20 PM)




Resolution:


Fixed





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/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[pedro.r...@mog-solutions.com (JIRA)]

pedro reis
 commented on  JENKINS-15156


Builds disappear from build history after completion















Sorry, but failed builds still disappear on Jenkins v1.502...



























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-15156) Builds disappear from build history after completion

[dogf...@java.net (JIRA)]

dogfood
 commented on  JENKINS-15156


Builds disappear from build history after completion















Integrated in  jenkins_main_trunk #2290
 JENKINS-15156 Found a problem with uninitialized run maps in new Maven modules. (Revision 09c7cf6ad7cfb4d88d6d8936f29b13f3ca187875)

 Result = SUCCESS
Jesse Glick : 09c7cf6ad7cfb4d88d6d8936f29b13f3ca187875
Files : 

	maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
	core/src/main/java/hudson/model/AbstractProject.java
	core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java





























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-15156) Builds disappear from build history after completion

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-15156


Builds disappear from build history after completion















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/model/AbstractProject.java
 core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
 maven-plugin/src/main/java/hudson/maven/MavenModuleSetBuild.java
http://jenkins-ci.org/commit/jenkins/09c7cf6ad7cfb4d88d6d8936f29b13f3ca187875
Log:
  JENKINS-15156 Found a problem with uninitialized run maps in new Maven modules.
Not observed in actual usage, but reproducible (for me at least, though apparently not ci.jenkins-ci.org) in a test:
java.lang.AssertionError: null
at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:628)
at jenkins.model.lazy.AbstractLazyLoadRunMap.all(AbstractLazyLoadRunMap.java:581)
at jenkins.model.lazy.AbstractLazyLoadRunMap.entrySet(AbstractLazyLoadRunMap.java:243)
at java.util.AbstractMap$2$1.(AbstractMap.java:378)
at java.util.AbstractMap$2.iterator(AbstractMap.java:377)
at hudson.util.RunList.iterator(RunList.java:103)
at hudson.util.RunList.size(RunList.java:114)
at hudson.maven.MavenProjectTest.testDeleteSetBuildDeletesModuleBuilds(MavenProjectTest.java:159)



– 
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.






























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-15156) Builds disappear from build history after completion

[lmgr...@gmail.com (JIRA)]

  
Larry Grill
 edited a comment on  JENKINS-15156


Builds disappear from build history after completion
















Nickolay: I upgraded one of our servers (with version 1.502) and have not seen the issue come back yet. So I feel comfortable upgrading our other servers with this build. Also tested copying jobs as noted in JENKINS-16735 and my history on the source job did not disappear. No guarantees, but so far it looks good.



























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-15156) Builds disappear from build history after completion

[lmgr...@gmail.com (JIRA)]

Larry Grill
 commented on  JENKINS-15156


Builds disappear from build history after completion















Nickolay: I upgraded one of our servers and have not seen the issue come back yet. So I feel comfortable upgrading our other servers with this build. Also tested copying jobs as noted in JENKINS-16735 and my history on the source job did not disappear. No guarantees, but so far it looks good.



























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-15156) Builds disappear from build history after completion

[linards.liep...@gmail.com (JIRA)]

Linards L
 commented on  JENKINS-15156


Builds disappear from build history after completion















It wouold be better to confirm linked issues first. Then this one. It would be good to keep histroical / hearichal view on this issue as I have feeling this is not last time devs will run in such circular issues ...



























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.
 
 

Re: [JIRA] (JENKINS-15156) Builds disappear from build history after completion

[Atif Ahmed]

Its been a isssue for a while now

On Wed, Feb 20, 2013 at 12:01 AM, nickolay.marti...@hp.com (JIRA) <
nore...@jenkins-ci.org> wrote:

> Nickolay 
> Martinovcommented
>  on [image:
> Bug] JENKINS-15156 
>  *Builds disappear from build history after 
> completion*
>
> Could anyone please confirm that issue is 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/groups/opt_out.
>
>
>

-- 
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-15156) Builds disappear from build history after completion

[nickolay.marti...@hp.com (JIRA)]

Nickolay Martinov
 commented on  JENKINS-15156


Builds disappear from build history after completion















Could anyone please confirm that issue is 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/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[oldel...@java.net (JIRA)]

Richard Mortimer
 commented on  JENKINS-15156


Builds disappear from build history after completion















The fixes made it into the 1.502 release. Its listed in the changelog (lines 67 & 68)

https://github.com/jenkinsci/jenkins/blob/5bca85d99253a85ae6085fc38ac592d97d8e98e6/changelog.html



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[richard_merr...@yahoo.com (JIRA)]

Richard Merrill
 commented on  JENKINS-15156


Builds disappear from build history after completion















Hard to tell if this fix made it in to 1.502 since they forgot to update the changelog. :/
The Build History timeline graphical display still isn't showing all of the builds, so maybe that'll have to be written up as a separate 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/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 commented on  JENKINS-15156


Builds disappear from build history after completion















@richardm_tx: 1.502 I think.



























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-15156) Builds disappear from build history after completion

[richard_merr...@yahoo.com (JIRA)]

Richard Merrill
 commented on  JENKINS-15156


Builds disappear from build history after completion















Did the fix make it into 1.501? I upgraded one of our servers to 1.501 today and haven't noticed any problems so far, but the Build History timeline graphical display isn't showing all of the builds.



























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-15156) Builds disappear from build history after completion

[linards.liep...@gmail.com (JIRA)]

Linards L
 commented on  JENKINS-15156


Builds disappear from build history after completion















Linked another one that might be connected to this issue / side-effects...



























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-15156) Builds disappear from build history after completion

[johno.crawf...@gmail.com (JIRA)]

Johno Crawford
 commented on  JENKINS-15156


Builds disappear from build history after completion















Current build stability is STABLE, see https://ci.jenkins-ci.org/job/jenkins_main_trunk/ .



























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-15156) Builds disappear from build history after completion

[linards.liep...@gmail.com (JIRA)]

Linards L
 commented on  JENKINS-15156


Builds disappear from build history after completion















hmm. Is there any hope to get this fix-set STABLE? 



























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-15156) Builds disappear from build history after completion

[dogf...@java.net (JIRA)]

dogfood
 commented on  JENKINS-15156


Builds disappear from build history after completion















Integrated in  jenkins_main_trunk #2252
 JENKINS-15156 AbstractProject.builds accessed by Maven & matrix module builds before onLoad or onCreatedFromScratch called. (Revision 37bf35b5dbb0ccdc34ad0c3643a0802c17e232dc)

 Result = UNSTABLE
Jesse Glick : 37bf35b5dbb0ccdc34ad0c3643a0802c17e232dc
Files : 

	core/src/main/java/hudson/model/AbstractProject.java





























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-15156) Builds disappear from build history after completion

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-15156


Builds disappear from build history after completion















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/model/AbstractProject.java
http://jenkins-ci.org/commit/jenkins/37bf35b5dbb0ccdc34ad0c3643a0802c17e232dc
Log:
  JENKINS-15156 AbstractProject.builds accessed by Maven & matrix module builds before onLoad or onCreatedFromScratch called.
Seem to need to keep the deprecated no-arg RunMap initializer though it is unclear to me how it could work.





























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-15156) Builds disappear from build history after completion

[linards.liep...@gmail.com (JIRA)]

Linards L
 commented on  JENKINS-15156


Builds disappear from build history after completion















Jesse, is there any code made for this idea?

"there are no validation check for current build number and just created / [successfuly] built and archived artifacts. If there would be simple excistance check that would valida that last build actually created artifacts and they ARE ACCESSIBLE to user, In my build system that would be pretty minor 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/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[dogf...@java.net (JIRA)]

dogfood
 commented on  JENKINS-15156


Builds disappear from build history after completion















Integrated in  jenkins_main_trunk #2249
 JENKINS-15156 Class loading errors can result from OOME if you are not careful. (Revision 74e6409a06531144316f2e36bdc0b069de52b94d)
JENKINS-15156 Massive test failures with NPE. (Revision 7ac15767bca327dae5a904dd66f717e5e6269be6)

 Result = UNSTABLE
Jesse Glick : 74e6409a06531144316f2e36bdc0b069de52b94d
Files : 

	test/src/main/java/org/jvnet/hudson/test/MemoryAssert.java



Jesse Glick : 7ac15767bca327dae5a904dd66f717e5e6269be6
Files : 

	core/src/main/java/hudson/model/AbstractProject.java





























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-15156) Builds disappear from build history after completion

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-15156


Builds disappear from build history after completion















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/model/AbstractProject.java
http://jenkins-ci.org/commit/jenkins/7ac15767bca327dae5a904dd66f717e5e6269be6
Log:
  JENKINS-15156 Massive test failures with NPE.
Seems that the RunMap must be initialized before updateTransientActions, which uses it, is called.


Compare: https://github.com/jenkinsci/jenkins/compare/fad1df3272d2...7ac15767bca3

– 
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.






























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-15156) Builds disappear from build history after completion

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-15156


Builds disappear from build history after completion















Code changed in jenkins
User: Jesse Glick
Path:
 test/src/main/java/org/jvnet/hudson/test/MemoryAssert.java
http://jenkins-ci.org/commit/jenkins/74e6409a06531144316f2e36bdc0b069de52b94d
Log:
  JENKINS-15156 Class loading errors can result from OOME if you are not careful.





























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-15156) Builds disappear from build history after completion

[dogf...@java.net (JIRA)]

dogfood
 commented on  JENKINS-15156


Builds disappear from build history after completion















Integrated in  jenkins_main_trunk #2248
 JENKINS-15156 Add regression test (Revision dbd6b530e7c1a7008dceff4ecc816eda9fc24ef1)
[FIXED JENKINS-15156] Initialize AbstractLazyLoadRunMap.dir for newly created jobs (Revision 2feb19ef3406838806749d65201b84781207555f)
JENKINS-15156 Refactored fix. (Revision fe95fc53f891542e63e24a64c0b7add60ac91c64)
JENKINS-15156 Noting. (Revision fad1df3272d2ad6c01bd8eab2582de38c61d9472)

 Result = UNSTABLE
ju.schmidt : dbd6b530e7c1a7008dceff4ecc816eda9fc24ef1
Files : 

	test/src/test/java/hudson/model/AbstractProjectTest.java



ju.schmidt : 2feb19ef3406838806749d65201b84781207555f
Files : 

	core/src/main/java/hudson/model/AbstractProject.java
	core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java



johno : fe95fc53f891542e63e24a64c0b7add60ac91c64
Files : 

	core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
	test/src/test/java/hudson/model/AbstractProjectTest.java
	core/src/main/java/hudson/model/AbstractProject.java
	test/src/main/java/org/jvnet/hudson/test/MemoryAssert.java



Jesse Glick : fad1df3272d2ad6c01bd8eab2582de38c61d9472
Files : 

	changelog.html





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-15156


Builds disappear from build history after completion















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/fad1df3272d2ad6c01bd8eab2582de38c61d9472
Log:
  JENKINS-15156 Noting.



– 
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.






























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-15156) Builds disappear from build history after completion

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-15156


Builds disappear from build history after completion















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/model/AbstractProject.java
 core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
 test/src/main/java/org/jvnet/hudson/test/MemoryAssert.java
 test/src/test/java/hudson/model/AbstractProjectTest.java
http://jenkins-ci.org/commit/jenkins/25f4c60f967da16607f4653a291c37c9383a301d
Log:
  Merge pull request #696 from johnou/JENKINS-15156

[FIXED JENKINS-15156] Initialize AbstractLazyLoadRunMap.dir for newly created jobs.


Compare: https://github.com/jenkinsci/jenkins/compare/e43e5f338e74...25f4c60f967d

– 
You received this message because you are subscribed to the Google Groups "Jenkins Commits" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.






























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-15156) Builds disappear from build history after completion

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-15156


Builds disappear from build history after completion















Code changed in jenkins
User: Johno Crawford
Path:
 core/src/main/java/hudson/model/AbstractProject.java
 core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
 test/src/main/java/org/jvnet/hudson/test/MemoryAssert.java
 test/src/test/java/hudson/model/AbstractProjectTest.java
http://jenkins-ci.org/commit/jenkins/fe95fc53f891542e63e24a64c0b7add60ac91c64
Log:
  JENKINS-15156 Refactored fix.





























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-15156) Builds disappear from build history after completion

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-15156


Builds disappear from build history after completion















Code changed in jenkins
User: Johno Crawford
Path:
 core/src/main/java/hudson/model/AbstractProject.java
 core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
 test/src/test/java/hudson/model/AbstractProjectTest.java
http://jenkins-ci.org/commit/jenkins/8f62901ee5265079598bc14dc9ade5196b5f066a
Log:
  Merge remote-tracking branch 'tsartarzan/JENKINS-15156' into JENKINS-15156





























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-15156) Builds disappear from build history after completion

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 resolved  JENKINS-15156 as Fixed


Builds disappear from build history after completion
















Change By:


SCM/JIRA link daemon
(07/Feb/13 12:07 AM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-15156


Builds disappear from build history after completion















Code changed in jenkins
User: Julian Schmidt
Path:
 core/src/main/java/hudson/model/AbstractProject.java
 core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
http://jenkins-ci.org/commit/jenkins/2feb19ef3406838806749d65201b84781207555f
Log:
  [FIXED JENKINS-15156] Initialize AbstractLazyLoadRunMap.dir for newly created jobs





























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-15156) Builds disappear from build history after completion

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-15156


Builds disappear from build history after completion















Code changed in jenkins
User: Julian Schmidt
Path:
 test/src/test/java/hudson/model/AbstractProjectTest.java
http://jenkins-ci.org/commit/jenkins/dbd6b530e7c1a7008dceff4ecc816eda9fc24ef1
Log:
  JENKINS-15156 Add regression test





























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-15156) Builds disappear from build history after completion

[jaystan2...@yahoo.com (JIRA)]

Jason Stanley
 commented on  JENKINS-15156


Builds disappear from build history after completion















I have encountered this same problem.
Jenkins 1.499
Server CentOS 6.2
Restarting Jenkins shows missing builds.



























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-15156) Builds disappear from build history after completion

[albin....@huawei.com (JIRA)]

Albin Joy
 commented on  JENKINS-15156


Builds disappear from build history after completion















Sorry for the delay to update this
I observed the same kind of issue today in our Jenkins setup. We are using 1.458 version.

Our setup have more than 60 jobs and master is Linux.

I uploaded one change, but build triggered by that event was not displayed in the BuildHistory.
After restarting Jenkins, the build is displayed in Jenkins.

We are using GerritTrigger plugins to trigger build.
In the job, the builds are running in slave.
The Job was triggering properly. No rename happened for the job.



























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-15156) Builds disappear from build history after completion

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 commented on  JENKINS-15156


Builds disappear from build history after completion















@johno the fix has not been accepted yet; pending review. If I do not get a chance to look at it myself this week I will bring it to Kohsuke’s attention ASAP.



























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-15156) Builds disappear from build history after completion

[johno.crawf...@gmail.com (JIRA)]

Johno Crawford
 commented on  JENKINS-15156


Builds disappear from build history after completion















@jglick can you confirm whether or not the fix will make it for 1.501?



























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-15156) Builds disappear from build history after completion

[linards.liep...@gmail.com (JIRA)]

Linards L
 commented on  JENKINS-15156


Builds disappear from build history after completion















Maybe it is worth to design some test-suite / test-set to debug such bugs as these issues made my department to think about moving to other CI solution... In heavy 5 - 10 minute build re-queing this is simply not accaptable 



























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-15156) Builds disappear from build history after completion

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 commented on  JENKINS-15156


Builds disappear from build history after completion















https://github.com/jenkinsci/jenkins/pull/688



























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-15156) Builds disappear from build history after completion

[linards.liep...@gmail.com (JIRA)]

Linards L
 commented on  JENKINS-15156


Builds disappear from build history after completion















Is there any code coverage taken, that is executed WITH and WITHOUT this lazy loading implementation?



























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-15156) Builds disappear from build history after completion

[nickolay.marti...@hp.com (JIRA)]

Nickolay Martinov
 commented on  JENKINS-15156


Builds disappear from build history after completion















Not sure this is caused by renaming as we do not rename jobs but had this problem very frequently (because of the number of jobs). Reverting back to version before 1.485 made this problem disappear. This is, imho, clear sign that lazy loading could be culprit.

BTW, we don't have shelve plug-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-15156) Builds disappear from build history after completion

[bb...@paychex.com (JIRA)]

bbonn
 commented on  JENKINS-15156


Builds disappear from build history after completion















Hi all,

I have found a way to reproduce in our environment.  Not sure if this will be the same for all of you, but maybe it is a start for debugging.   I noticed recently that while un-shelving a job (plugin we use quite frequently) a job that was running displayed a strange 404 error in the console.  See below

15:27:09  [WARNINGS] Parsing warnings in console log...
15:27:09  Archiving artifacts
Status Code: 404
Exception: 
Stacktrace: 
(none)

I then went back  job page and refreshed and the build had disappeared.  A reload from disk brought it back as usual.  I have recreated a couple of times now, so not sure if the Shelve plugin is the culprit or some other underlying piece that interacts with plugins.  

Also, I don't always get the 404 in the console, sometimes after starting a un-shelving job, the link for the build console goes right tot a generic 404 error page.  

Jenkins 1.480.1  
Windows Server 2008 R2 (Master and Slave)

Can anyone else recreate this 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/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 commented on  JENKINS-15156


Builds disappear from build history after completion















Right, it is entirely possible there are two or more unrelated bugs lumped together here: at least, one present already in older versions of unknown cause; and one triggered by job renaming in 1.485+.



























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-15156) Builds disappear from build history after completion

[jtaylor.deb...@googlemail.com (JIRA)]

Julian Taylor
 commented on  JENKINS-15156


Builds disappear from build history after completion















for me it happens since lazy loading of build records was introduced, so version 1.485.
I haven't verified that reverting back to 84 fixes it.

the issue of jenkinsuserfrance in 483 is probably something else, because the build/ folder is perfectly alright it just does not load whats in there.



























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-15156) Builds disappear from build history after completion

[jenkinsuserfra...@yahoo.com (JIRA)]

jenkinsuserfrance jenkinsuserfrance
 commented on  JENKINS-15156


Builds disappear from build history after completion















Hello,
  We had a similar problem with v 1.483. It happened on several jobs which were never renamed. Reloading the configuration restored the situation for most jobs. For few, some builds were missing in the history. After analysis, the missing builds were also lacking the build.xml in the "build/" folder.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[linards.liep...@gmail.com (JIRA)]

Linards L
 commented on  JENKINS-15156


Builds disappear from build history after completion















Ok. First of all - devs got to understand the point this nonsense started. On my second machine, using v1.454, this has never happened. Others ... ? Seems like Jenkins infrastructure does not have any way to do some regression tests ... like, for example, WineHQ guys got ...



























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-15156) Builds disappear from build history after completion

[richard_merr...@yahoo.com (JIRA)]

Richard Merrill
 commented on  JENKINS-15156


Builds disappear from build history after completion















I have had this issue occur without ever renaming any jobs, so I'm afraid the bug is a little more complicated. When it does happen, it is often for more than one job. Without doing anything, the problem can disappear the next time I open the web interface. Or sometimes it is more persistent and doesn't go away until I reload configuration from disk. I have versions 1.497 and 1.500 running on two separate WS2008R2 servers and it has happend on both. Fortunately, it hasn't happened very often lately...



























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-15156) Builds disappear from build history after completion

[ivaylo.brat...@gmail.com (JIRA)]

Ivaylo Bratoev
 commented on  JENKINS-15156


Builds disappear from build history after completion















As a matter of fact I renamed these builds some time ago as well... This might be one part of the 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/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[linards.liep...@gmail.com (JIRA)]

Linards L
 commented on  JENKINS-15156


Builds disappear from build history after completion















For me fix, using v1.494 was simply copy excisting faulty job to new one.

Probably the renaming of job / project causes this. The ridicilous side effect of this is that there are no validation check for current build number and just created / [successfuly] built and archived artifacts. If there would be simple excistance check that would valida that last build actually created artifacts and they ARE ACCESSIBLE to user, In my build system that would be pretty minor issue. Currently hitting on this is pretty pain-in-ass catogrizable one...

Always wonder why to implement new features instead of simply avoid / fix blockers lurking everywhere in jenkins core :/



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[nn...@neulinger.org (JIRA)]

Nathan Neulinger
 commented on  JENKINS-15156


Builds disappear from build history after completion















Running on fc17 x86_64. 



























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-15156) Builds disappear from build history after completion

[nn...@neulinger.org (JIRA)]

Nathan Neulinger
 commented on  JENKINS-15156


Builds disappear from build history after completion















I've seen it regularly with renamed jobs. We have heavy use of copy artifacts, no matrix use, several ssh slaves. Almost all free-style jobs (though may have a maven one in there too).



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[mdera...@hotmail.com (JIRA)]

michael d
 commented on  JENKINS-15156


Builds disappear from build history after completion















Also experiencing this in 1.499 on RHEL.
Reloading configuration from disk seems to solve it.

Can't find any pattern to reproduce this, and the logs doesn't say anything.
Voodoo



























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-15156) Builds disappear from build history after completion

[aeschbac...@java.net (JIRA)]

aeschbacher
 commented on  JENKINS-15156


Builds disappear from build history after completion















Same main usage for us:

	heavy use of "copy artifacts" plugin,
	matrix projects (with "Matrix tie parent" plugin)
	ssh slaves
At the beginning, we thought indeed this was related to renaming the build job. But the problem also occurs for example when modifying the slaves in the configuration matrix.
But sometimes, it does occur with free-style (not multi-configuration) jobs too.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[nickolay.marti...@hp.com (JIRA)]

Nickolay Martinov
 commented on  JENKINS-15156


Builds disappear from build history after completion















For us it's just random since we do not (and cant) rename jobs. No particular conditions were noted. Right now it's ok but with couple of builds on any jobs history starts disappearing; reload configuration from disk and builds are back. Since copy artifacts plugin affected, i believe this is not a UI problem. We extensively use matrix projects and ssh slaves with matrix tie parent plugin (dont know if this matters). Downgraded back to 1.463 and this problem disappeared.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

[fderu...@gmail.com (JIRA)]

Franck Derunes
 commented on  JENKINS-15156


Builds disappear from build history after completion















I am using 1.493, and I can repro this just by renaming a job.
I am suspicious this could happen also by changing anything in the job config (but this would have to be verified)

I fix that just by restarting Jenkins  http://IP:8080/restart
The history is back with all the jobs.



























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-15156) Builds disappear from build history after completion

[jgl...@cloudbees.com (JIRA)]

Jesse Glick
 updated  JENKINS-15156


Builds disappear from build history after completion
















Does anyone have any clue how to reproduce this from scratch?

There are intimations that this is a regression from lazy loading (JENKINS-8754), yet this was originally filed against an older Jenkins version, so it is possible there are two or more unrelated bugs being lumped together here.





Change By:


Jesse Glick
(23/Jan/13 5:00 PM)




Summary:


Builds
 Disappear
 disappear
 from
 Build History
 build history
 after
 Completion
 completion





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

[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion

[d...@fortysix.ch (JIRA)]

domi
 assigned  JENKINS-15156 to Jesse Glick



Builds Disappear from Build History after Completion
















Sorry Jesse, I'm assigning this to you so that some more core devs are aware of this one...





Change By:


domi
(23/Jan/13 7:21 AM)




Assignee:


Jesse Glick



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion

[jurgen.van.boucha...@gmail.com (JIRA)]

Jurgen Van Bouchaute
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















Same problem on 1.498 version (Linux) - very annoying 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

[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion

[nn...@neulinger.org (JIRA)]

  
Nathan Neulinger
 edited a comment on  JENKINS-15156


Builds Disappear from Build History after Completion
















Same here with 1.499, reload from disk consistently clears it, but hardly an option for automated build chains. Our setup is client/server with 5 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

[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion

[nn...@neulinger.org (JIRA)]

Nathan Neulinger
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















Same here with 1.499, reload from disk consistently clears it, but hardly an option for automated build chains. 



























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-15156) Builds Disappear from Build History after Completion

[oldel...@java.net (JIRA)]

Richard Mortimer
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















I'm wondering if this is due to the failure to re-load of an individual build history in AbstractLazyLoadRunMap.java.

Specifically the search(int, Direction) method does a binary search looking for a specific build. When it finds a match it may have to load() the build record from disk. If this fails then it "silently" removes the build that it tried to load and carries on.


R r = load(idOnDisk.get(pivot), null);
if (r==null) {
// this ID isn't valid. get rid of that and retry pivot
hi--;
if (!clonedIdOnDisk) {// if we are making an edit, we need to own a copy
idOnDisk = new SortedList(idOnDisk);
clonedIdOnDisk = true;
}
idOnDisk.remove(pivot);
continue;
}


Assuming that the failure to load is a (unknown) transient error then that would cause the build to disappear but it would be re-loaded when jenkins is restarted and the on-disk records scanned again.

I haven't seen this failure mode so I'm not able to test directly. If someone is able/willing to take a debug build of the latest jenkins I'll try to find time to add some additional debug logging to see if we can prove/disprove this theory.



























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-15156) Builds Disappear from Build History after Completion

[jo...@joelj.com (JIRA)]

Joel Johnson
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















@Nickolay Martinov: It's been happening to us ever since we upgraded to the Lazy Loading patch (1.485).



























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-15156) Builds Disappear from Build History after Completion

[henri.go...@gmail.com (JIRA)]

  
Henri Gomez
 edited a comment on  JENKINS-15156


Builds Disappear from Build History after Completion
















Same problem here, with 1.498 (powered by Tomcat 7.0.35) under openSUSE Linux.
I noticed this problem appears for jobs built on agents.



























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-15156) Builds Disappear from Build History after Completion

[henri.go...@gmail.com (JIRA)]

Henri Gomez
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















Same problem here, with 1.498, under openSUSE Linux.
I noticed this problem appears for jobs built on agents.



























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-15156) Builds Disappear from Build History after Completion

[nickolay.marti...@hp.com (JIRA)]

Nickolay Martinov
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















Does anyone know version where this bug wasnt introduced yet?



























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-15156) Builds Disappear from Build History after Completion

[martin.danjo...@gmail.com (JIRA)]

Martin d'Anjou
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















We're using 1.492. Suddenly, builds #1 to #9 disappeared. After a day or two we decided to launch a build using a different user account. Now the builds do show up, but only starting at #10. I agree with making this bug a 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

[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion

[nickolay.marti...@hp.com (JIRA)]

Nickolay Martinov
 updated  JENKINS-15156


Builds Disappear from Build History after Completion
















Change By:


Nickolay Martinov
(17/Jan/13 4:39 AM)




Priority:


Critical
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

[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion

[nickolay.marti...@hp.com (JIRA)]

Nickolay Martinov
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















Rearranged links a bit as this issue was marked as duplicate of newer issue that didn't get as much attention...



























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-15156) Builds Disappear from Build History after Completion

[andrzej.pasterc...@gmail.com (JIRA)]

Andrzej Pasterczyk
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















We experience similar issue as joelj mentioned. For regular jobs build history is kept much longer while for matrix jobs it tends to disappear randomly, even right after build completes. Sometimes there's a link for the build in history on master but not on slaves, sometimes it's gone from both nodes, sometimes there's a link but trying to access it returns 404.
Even reloading configuration makes no difference here. Running on Windows Server 2008 x64, Tomcat7.
Is there a way to raise priority on this issue? It is a real blocker especially in terms of keeping tests historical data - we get an email that something failed but it's extremely hard to trace down what was it if there's no history.



























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-15156) Builds Disappear from Build History after Completion

[jo...@joelj.com (JIRA)]

Joel Johnson
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















We have the same problem with 1.499. It happens very frequently with the individual matrix builds. It happens so fast that we run a job, click on the console for the section of the matrix, and IM it to someone else, and by the time they click the link, it's gone.

I don't undertand why this is still an issue, and the issue hasn't even received as much of a comment from someone. This is a huge problem. As a previous commenter stated, it makes people who use Jenkins blame Jenkins for more and more problems. I'm trying my best at the office to keep Jenkins from becoming the scapegoat, but it's bugs like this that make people trust it less and less.

Ubuntu Server 12.04 - Tomcat7 Container.



























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-15156) Builds Disappear from Build History after Completion

[ivaylo.brat...@gmail.com (JIRA)]

Ivaylo Bratoev
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















Same issue on 1.493. Main Jenkins on Windows Server 2008 R2 with 1 child node with same OS. Reload Configuration from Disk fixed the issue at least for now. I also noticed that only the builds running on the child node lost their history, the builds on the master were OK.



























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-15156) Builds Disappear from Build History after Completion

[pet...@standingwave.org (JIRA)]

Peter Loron
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















Also seeing this on 1.498. Linux master. Win2K8 slave.



























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-15156) Builds Disappear from Build History after Completion

[jchat...@acuitus.com (JIRA)]

jchatham
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















For reference, we're seeing this issue under 1.486, on a Maven job running exclusively on the master.  Other apparently identically set up Maven jobs (also running on the master) don't exhibit the same problem, however.

As a possibly-related issue, the jobs where builds disappear have also shown just build status vanishing as well - several early builds had test failures, and every now and then those builds turn up as blue (before eventually vanishing entirely); in both cases, reloading configuration from disk temporarily resolves the 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

[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion

[martin.wiklu...@ericsson.com (JIRA)]

  
Martin Wiklundh
 edited a comment on  JENKINS-15156


Builds Disappear from Build History after Completion
















I made a copy of a broken project and the copy seems to work.
Edit: Renaming the copy broke it, but renaming back again gave the history back.



























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-15156) Builds Disappear from Build History after Completion

[martin.wiklu...@ericsson.com (JIRA)]

  
Martin Wiklundh
 edited a comment on  JENKINS-15156


Builds Disappear from Build History after Completion
















I made a copy of a broken project and the copy seems to work.
Edit: No, it broke after some hours.



























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-15156) Builds Disappear from Build History after Completion

[martin.wiklu...@ericsson.com (JIRA)]

Martin Wiklundh
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















I made a copy of a broken project and the copy seems to work.



























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-15156) Builds Disappear from Build History after Completion

[nickolay.marti...@hp.com (JIRA)]

Nickolay Martinov
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















Reloading history isn't really a solution. Since CI is not for humans (why we need CI then?) but for automation. And this bug makes plugins like "Copy artifact" to fail. All this results in lots of false build failures. Since people cant really do anything about these build failures they tend to start just to ignore "crazy Jenkins". And this ruins whole concept.



























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-15156) Builds Disappear from Build History after Completion

[larry.ca...@gmail.com (JIRA)]

Larry Cai
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















I have this problem in 1.495 as well, master/slave mode



























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-15156) Builds Disappear from Build History after Completion

[damian.di...@gmail.com (JIRA)]

damian dixon
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















This is happening with 1.494.
Reloading the configuration brings back the 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

[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion

[wolfg1...@gmail.com (JIRA)]

Yong Guo
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















(updated) I just upgrade to 1.495, then the history goes back!



























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-15156) Builds Disappear from Build History after Completion

[s.sog...@gmail.com (JIRA)]

sogabe
 updated  JENKINS-15156


Builds Disappear from Build History after Completion
















changed priority to Critical.





Change By:


sogabe
(26/Dec/12 7:03 AM)




Priority:


Major
Critical



























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-15156) Builds Disappear from Build History after Completion

[wolfg1...@gmail.com (JIRA)]

  
Yong Guo
 edited a comment on  JENKINS-15156


Builds Disappear from Build History after Completion
















I have this problem after upgrading to 1.494. Master/Slave setup (all Linux box). Only the job create after upgrading has this problem. Those jobs created before upgrading work well.

(updated) I find all the builds exists in the build directory. The problem is that they are not shown in the build history.



























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-15156) Builds Disappear from Build History after Completion

[wolfg1...@gmail.com (JIRA)]

Yong Guo
 commented on  JENKINS-15156


Builds Disappear from Build History after Completion















I have this problem after upgrading to 1.494. Master/Slave setup (all Linux box). Only the job create after upgrading has this problem. Those jobs created before upgrading work 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