[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Stephen Connolly resolved as Fixed I claim fixed in 2.1.0 release Jenkins / JENKINS-36029 multibranch-job deleted when bitbucket communication fails Change By: Stephen Connolly Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Stephen Connolly assigned an issue to Stephen Connolly Jenkins / JENKINS-36029 multibranch-job deleted when bitbucket communication fails Change By: Stephen Connolly Assignee: Antonio Muñiz Stephen Connolly Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Ben Fortuna commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Stephen Connolly new issue created for github: JENKINS-42000 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Stephen Connolly commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Ben Fortuna to the best of my knowledge the Git, GitHub and Subversion implementations do the correct thing and propagate IO errors as exceptions. Certainly when I run out of rate limit the scan is aborted and no repositories or branches are deleted. If you have a reproducible test case or an example log where there was an API error and the scan / index completed as success (which would then cause the missing branches to be removed) please create an issue for it in JIRA as that kind of data loss is highest priority IMHO (i.e. this is why I am working on this issue ahead of all others at present - because it is a data loss issue) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Ben Fortuna commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Stephen Connolly Will this fix also apply for Git/Github repositories? I suspect most of these plugins will just swallow exceptions when they can't connect to a repository, so perhaps the design needs to be rethought.. (possibly require an exception/explicit return value before deleting the job?) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Stephen Connolly started work on JENKINS-36029 Change By: Stephen Connolly Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Stephen Connolly commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails I have a fix for this under test. If anyone wants to assist in doing some early testing the code is on https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/35 (though at this point it doesn't build) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Stephen Connolly commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails OK this seems to be a case of the BitBucketBranchSource not actually propagating exceptions. Basically the BitbucketCloudApiClient and BitbucketServerAPIClient methods that might invoke network operations do not declare throwing IOException or InterruptedException and instead opt for the "friendly" returning of "dummy" values or null This defeats the intended behaviour of branch api (which was verified in JENKINS-40767 e.g. see this test https://github.com/jenkinsci/branch-api-plugin/blob/d55f2b4369e0fe9b3b0441654e632eaf8bb5920f/src/test/java/integration/EventsTest.java#L287-L321 as evidence that a propagated exception prevents the orphaned item strategy from kicking in) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Anders Båtstrand commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Same issue for my team: After Bitbucket Server was down, all jobs reset their build numbers. We used the build number as versioning, but due to this bug we have to use the timestamp instead, which is less human friendly. It would be nice if the plugin could see the difference between a branch not being present, and the Bitbucket server not answering. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Ben Fortuna commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Antonio Muñiz Yes, this is a semi-workaround which I use - currently set to 7 day expiry. However for some projects the develop branch isn't built so frequently (i.e. greater than 7 days between builds) so the build history is lost (i.e. resets to build #1 which causes other issues such as versioning conflicts). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Antonio Muñiz commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails A workaround for this issue is to set the "Orphaned Item Strategy -> Days to keep old items" to something different than 0, for example 1 day. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Rene Kok commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails We are using BitBucket cloud. Our scan bitbucket over 100+repositories randomly fails because the API rate limit is reached (https://confluence.atlassian.com/bitbucket/rate-limits-668173227.html). With the current implementation of the plugin we can do nothing but wait one hour (rate limit is measured per hour) and then try again to recover the lost build jobs. I.m.o. the request rate can be reduced a lot (preventing hitting the API rate limit) if the scan logic is changed to only add jobs or branches that do not exist yet. A separate scan could do nightly cleanups of removed branches/repositories. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Rene Kok edited a comment on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails We are using BitBucket cloud. Our scan bitbucket over 100+repositories randomly fails because the API rate limit is reached (https://confluence.atlassian.com/bitbucket/rate-limits-668173227.html). With the current implementation of the plugin we can do nothing but wait one hour (rate limit is measured per hour) and then try again to recover the lost build jobs.I.m.o. the request rate can be reduced a lot (preventing hitting the API rate limit) if the scan logic is changed to only add jobs or branches that do not exist yet. A separate scan could do nightly cleanups of removed branches/repositories. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title davidkarlsen commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Any progress on this? We´re a paying support customer with CB and have an issue open there as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Sanjeev Nithyanandam commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Experiencing the same issue. Currently have indexing turned off in multibranch plugin so we constantly don't end up deleting jobs. Waiting for the fix for this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Coltrey Mather commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Any ETA on fixing the delete issue? Deleting all the build history when there's a transient bitbucket error is impacting me as well. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Alik Kurdyukov commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Well, for me it works. I've built and installed plugin with this patch and haven't got any SSL errors in a week or so. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Antonio Muñiz commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails No, that PR is not fixing this. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Alik Kurdyukov commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/14/files seems to be a fix for the problem described Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Javier Martín commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails That's right, if you rerun folder computation after a failed connection it works again, but with the build numbers restarted. As Antonio Muñiz said, I think the problem is similar as the one resolved for github-branch-source. Regards! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Vladimir Rozhkov commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Antonio Muñiz: this fix is about github availability, there is only one check – "github == unavailable ? abort job : proceed job". Our issue is different. Our issue is about single requests failing sporadically that's why I'm talking about retries. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Antonio Muñiz commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Already fixed in github-branch-source https://github.com/jenkinsci/github-branch-source-plugin/pull/57 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Antonio Muñiz edited a comment on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Already fixed in github-branch-source https://github.com/jenkinsci/github-branch-source-plugin/pull/57 The fix needed here is similar. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Vladimir Rozhkov commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Javier Martín: sorry then for misunderstanding. Does simple retry fix the issue, how do you think? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Antonio Muñiz commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Right, the fix is the same for any "connection issue". Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Javier Martín commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails The title of the issue is "multibranch-job deleted when bitbucket communication fails" and I think this is the same issue. The log says unauthorized request, but this is due to a communication problem between bitbucket and jira and therefore bitbucket-branch-source-plugin behaves in the same way as the open issue. The credentials are placed correctly and works fine almost always. Maybe I neet to create another issue because this is only because SSL handshake, but seems pretty close to me, the problem is that when bitbucket communication fails jenkins deletes all multibranch-jobs and restarts build numbers when the computation folder runs again. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Vladimir Rozhkov commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Javier Martin this is not the same issue. The issue is about ssl handshake failure and yours is about auth failure. Make sure you've setup credentials correctly. Meanwhile, I'm working on PR to fix the SSL handshake issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title
Javier Martín edited a comment on JENKINS-36029
Re: multibranch-job deleted when bitbucket communication fails
We are experiencing this issue as well. As we delegate our User Directory to JIRA, when this instance is not available an Unauthorized Error 401 appears rising the following error:{{ com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: No Autorizado.{"errors":[{"context":null,"message":"Authentication failed. Please check your credentials and try again.","exceptionName":"com.atlassian.bitbucket.auth.AuthenticationSystemException"}]} at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getRequest(BitbucketServerAPIClient.java:382) at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getBranches(BitbucketServerAPIClient.java:258) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:384) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:245) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:75) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:206) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE }}Then we need to run the folder computation again and all build numbers are restarted. We use this parameter as a complement to version number so there is a way to retain build numbers when this happens? This is not a case when a Jenkinsfile is not present in a branch (I assume when this happens the multibranch job is deleted), this is a temporary issue with the scan credentials and I think it wouln't be that way.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title
Javier Martín edited a comment on JENKINS-36029
Re: multibranch-job deleted when bitbucket communication fails
We are experiencing this issue as well. As we delegate our User Directory to JIRA, when this instance is not available an Unauthorized Error 401 appears rising the following error: {{ com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: No Autorizado.{"errors":[{"context":null,"message":"Authentication failed. Please check your credentials and try again.","exceptionName":"com.atlassian.bitbucket.auth.AuthenticationSystemException"}]} at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getRequest(BitbucketServerAPIClient.java:382) at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getBranches(BitbucketServerAPIClient.java:258) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:384) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:245) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:75) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:206) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410)Finished: FAILURE }} Then we need to run the folder computation again and all build numbers are restarted. We use this parameter as a complement to version number so there is a way to retain build numbers when this happens? This is not a case when a Jenkinsfile is not present in a branch (I assume when this happens the multibranch job is deleted), this is a temporary issue with the scan credentials and I think it wouln't be that way.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title
Javier Martín commented on JENKINS-36029
Re: multibranch-job deleted when bitbucket communication fails
We are experiencing this issue as well. As we delegate our User Directory to JIRA, when this instance is not available an Unauthorized Error 401 appears rising the following error: {{ com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: No Autorizado. {"errors":[ {"context":null,"message":"Authentication failed. Please check your credentials and try again.","exceptionName":"com.atlassian.bitbucket.auth.AuthenticationSystemException"} ]} at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getRequest(BitbucketServerAPIClient.java:382) at com.cloudbees.jenkins.plugins.bitbucket.server.client.BitbucketServerAPIClient.getBranches(BitbucketServerAPIClient.java:258) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:384) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:245) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:75) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:206) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Finished: FAILURE }} Then we need to run the folder computation again and all build numbers are restarted. We use this parameter as a complement to version number so there is a way to retain build numbers when this happens? This is not a case when a Jenkinsfile is not present in a branch (I assume when this happens the multibranch job is deleted), this is a temporary issue with the scan credentials and I think it wouln't be that way.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Michael Fowler updated an issue Jenkins / JENKINS-36029 multibranch-job deleted when bitbucket communication fails Change By: Michael Fowler Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Vladimir Rozhkov commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails I have a lot of repositories in our team account (kinda 30) and I'm very annoyed that I have to re-run folder computation 10 times to get all my repos configured. Will some retry logic work here? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Antonio Muñiz commented on JENKINS-36029 Re: multibranch-job deleted when bitbucket communication fails Counterpart of JENKINS-34776 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails
Title: Message Title Asgeir Frimannsson created an issue Jenkins / JENKINS-36029 multibranch-job deleted when bitbucket communication fails Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Jun/17 3:23 AM Environment: Jenkins 2.8 Priority: Major Reporter: Asgeir Frimannsson I'm trying out the "Bitbucket team/project" feature: I have an issue where some of my jobs keeps being deleted and recreated randomly, and it seems to be related to situations where communicating with bitbucket fails. I would not expect Jenkins to delete my multibranch-job when e.g. Bitbucket or some network link is down. Relevant log: Proposing ansible-docker Connecting to https://bitbucket.org using hidden-org-name/** (hidden-org-name bitbucket credentials) Looking up hidden-org-name/ansible-docker for branches Checking branch jenkins-test from hidden-org-name/ansible-docker Met criteria ERROR: Failed to create or update a subproject ansible-docker com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: Communication error: javax.net.ssl.SSLHandshakeException: Remote host closed connection during handshake at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:421) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRepository(BitbucketCloudApiClient.java:173) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.getRepositoryType(BitbucketSCMSource.java:254) at
