[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Mads Mohr Christensen commented on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down This issue also deleted my build history because of a temporary outage at a bad time. I have opened a [PR|https://github.com/jenkinsci/mercurial-plugin/pull/144] implementing the suggestion by Dave E Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187660.1515518637000.15992.1587566460427%40Atlassian.JIRA.
[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Mads Mohr Christensen edited a comment on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down This issue also deleted my build history because of a temporary outage at a bad time.I have opened a [ PR | [https://github.com/jenkinsci/mercurial-plugin/pull/144] ] implementing the suggestion by [~brewmook] Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187660.1515518637000.15994.1587566460462%40Atlassian.JIRA.
[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E edited a comment on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down I got this too.Short-term workaround, either of the following under "Orphaned Item Strategy": * Switch off "Discard old items" entirely, and take care of that by hand * Set positive number in "Max # of old items to keep"/"Days to keep old items".Your mileage may vary depending on how often your Mercurial server goes down.Having dug into this a bit, I believe the orphaned item stuff is behaving as expected.The curious bit is the "Could not use caches, not fetching branch heads" error. Looking in [MercurialSCMSource.java|https://github.com/jenkinsci/mercurial-plugin/blob/65ba1fe95fc95670a153a551b434d26365a0130c/src/main/java/hudson/plugins/mercurial/MercurialSCMSource.java#L211], it the retrieve methods simply returns if the cache is null. Should this not be throwing an exception instead? The knock-on effect seems to be that the orphaned item strategy kicks in and all the branches are marked as closed. I would expect the polling/indexing to abort entirely if the cache is not available/working. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E edited a comment on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down I got this too.Short-term workaround, either of the following under "Orphaned Item Strategy": * Switch off "Discard old items" entirely, and take care of that by hand * Set positive number in "Max # of old items to keep"/"Days to keep old items".Your mileage may vary depending on how often your Mercurial server goes down.Having dug into this a bit, I believe the orphaned item stuff is behaving as expected.The curious bit is the "Could not use caches, not fetching branch heads" error. Looking in [MercurialSCMSource.java| https://github.com/jenkinsci/mercurial-plugin/blob/65ba1fe95fc95670a153a551b434d26365a0130c/src/main/java/hudson/plugins/mercurial/MercurialSCMSource.java #L211], ] it simply returns if the cache is null. Should this not be throwing an exception instead? The knock-on effect seems to be that the orphaned item strategy kicks in and all the branches are marked as closed. I would expect the polling/indexing to abort entirely if the cache is not available/working. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E commented on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down It doesn't help that the next consequence of this is a build storm when the mercurial server comes back up. All branches are marked as reopened and everything rebuilds. We currently have some issues with our hg server, and it reboots several times a week, so the build storms are proving to be the most frustrating consequence. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E edited a comment on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down I got this too.Short-term workaround, either of the following under "Orphaned Item Strategy": * Switch off "Discard old items" entirely, and take care of that by hand * Set positive number in "Max # of old items to keep"/"Days to keep old items".Your mileage may vary depending on how often your Mercurial server goes down.Having dug into this a bit, I believe the orphaned item stuff is behaving as expected.The curious bit is the "Could not use caches, not fetching branch heads" error. Looking in [MercurialSCMSource.java| [https://github.com/jenkinsci/mercurial-plugin/blob/65ba1fe95fc95670a153a551b434d26365a0130c/src/main/java/hudson/plugins/mercurial/MercurialSCMSource.java #L211],] it simply returns if the cache is null. Should this not be throwing an exception instead? The knock-on effect seems to be that the orphaned item strategy kicks in and all the branches are marked as closed. I would expect the polling /indexing to abort entirely if the cache is not available/working. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48867) Mercurial multibranch pipeline deletes all branches when repository is down
Title: Message Title Dave E commented on JENKINS-48867 Re: Mercurial multibranch pipeline deletes all branches when repository is down I got this too. Short-term workaround, either of the following under "Orphaned Item Strategy": Switch off "Discard old items" entirely, and take care of that by hand Set positive number in "Max # of old items to keep"/"Days to keep old items". Your mileage may vary depending on how often your Mercurial server goes down. Having dug into this a bit, I believe the orphaned item stuff is behaving as expected. The curious bit is the "Could not use caches, not fetching branch heads" error. Looking in MercurialSCMSource.java it simply returns if the cache is null. Should this not be throwing an exception instead? The knock-on effect seems to be that the orphaned item strategy kicks in and all the branches are marked as closed. I would expect the polling to abort entirely if the cache is not available/working. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
