[JIRA] (JENKINS-47958) Closed branches clone again and try build
Title: Message Title Michael Neale commented on JENKINS-47958 Re: Closed branches clone again and try build thanks Christian Ewald for fix, thanks all for trying it out and thanks Vivek Pandey Antonio Muñiz rsandell for review/release, mercurial users should be in a better state now with closed branches. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47958) Closed branches clone again and try build
Title: Message Title Joseph Petersen resolved as Fixed Fixed in Bitbucket Branch Source Plugin 2.2.10 Jenkins / JENKINS-47958 Closed branches clone again and try build Change By: Joseph Petersen Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47958) Closed branches clone again and try build
Title: Message Title Christian Ewald commented on JENKINS-47958 Re: Closed branches clone again and try build Michael Neale: Absolutely reasonable. Thx Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47958) Closed branches clone again and try build
Title: Message Title Michael Neale commented on JENKINS-47958 Re: Closed branches clone again and try build ah thanks Christian Ewald - I think it makes sense now, so, excuse my ignorance of hg, but could I clarify: 2.0 api is shifted to with newer releases, which DOES list closed branches, 1.0 did not in hg a closed branch is idiomatically like a delete in say github in Bitbucket you can delete git branches - but in hg they are closed? A future RFE could be to build closed branches, but this is about as odd as building deleted github branches (sort of, as they still live in github for a little while) Reasonable summary? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47958) Closed branches clone again and try build
Title: Message Title Ben Dean edited a comment on JENKINS-47958 Re: Closed branches clone again and try build It is really disheartening that [~hubble1942]'s [jenkinsci/bitbucket-branch-source-plugin#106|https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/106] was closed without being merged. I get it that [~amuniz]'s concerns about being able to turn this on or off are worthwhile, but why then don't the people that us use Bitbucket and git complain about not having all their closed branches?I mean, if Jenkins itself was maintained in Bitbucket as a Mercurial repo, can you imagine having every old build for every PR branch anyone made forever? That cannot possibly be the desired default behavior. In fact, the build for Christian's branch itself is marked as an item to be deleted in the github folder on the main jenkins ci server: [https://ci.jenkins.io/job/Plugins/job/bitbucket-branch-source-plugin/view/change-requests/] PR-106 may be gone from there soon because it's closed. _That_ _seems like the desired behavior!_ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47958) Closed branches clone again and try build
Title: Message Title Ben Dean edited a comment on JENKINS-47958 Re: Closed branches clone again and try build It is really disheartening that [~hubble1942]'s [jenkinsci/bitbucket-branch-source-plugin#106|https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/106] was closed without being merged. I get it that [~amuniz]'s concerts concerns about being able to turn this on or off are worthwhile, but why then don't the people that us Bitbucket and git complain about not having all their closed branches?I mean, if Jenkins itself was maintained in Bitbucket as a Mercurial repo, can you imagine having every old build for every PR branch anyone made forever? That cannot possibly be the desired default behavior. In fact, the build for Christian's branch itself is marked as an item to be deleted in the github folder on the main jenkins ci server: [https://ci.jenkins.io/job/Plugins/job/bitbucket-branch-source-plugin/view/change-requests/] PR-106 may be gone from there soon because it's closed. _That_ _seems like the desired behavior!_ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47958) Closed branches clone again and try build
Title: Message Title Ben Dean commented on JENKINS-47958 Re: Closed branches clone again and try build It is really disheartening that Christian Ewald's jenkinsci/bitbucket-branch-source-plugin#106 was closed without being merged. I get it that Antonio Muñiz's concerts about being able to turn this on or off are worthwhile, but why then don't the people that us Bitbucket and git complain about not having all their closed branches? I mean, if Jenkins itself was maintained in Bitbucket as a Mercurial repo, can you imagine having every old build for every PR branch anyone made forever? That cannot possibly be the desired default behavior. In fact, the build for Christian's branch itself is marked as an item to be deleted in the github folder on the main jenkins ci server: https://ci.jenkins.io/job/Plugins/job/bitbucket-branch-source-plugin/view/change-requests/ PR-106 may be gone from there soon because it's closed. That seems like the desired behavior! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47958) Closed branches clone again and try build
Title: Message Title Rinat Muhamedgaliev commented on JENKINS-47958 Re: Closed branches clone again and try build Dear Christian Ewald I downloaded source from your GitHub repository and builded it. It work fine! Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47958) Closed branches clone again and try build
Title: Message Title Christian Ewald commented on JENKINS-47958 Re: Closed branches clone again and try build As it looks like, it will take a bit longer to get a patch into the official release. So I decided to build my own patched version. It is based on V2.2.9 and works as expected. You may download it from my drive (No warranty, use at your own risk, no responsibility for data corruption/losses etc.) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
