There's a suggestion here on how to fix it: https://github.com/jenkinsci/bom/issues/561
Just needs someone to test it out On Wed, 16 Jun 2021 at 07:02, Tim Jacomb <[email protected]> wrote: > Not saying it’s the best fix but many of us have turned off the windows ci > as it’s too unreliable > > On Wed, 16 Jun 2021 at 02:35, Bryan Stopp <[email protected]> wrote: > >> Sorry for the delay. I was seeing it since I took over the major dev >> effort on this plugin. At least every other build failed due to a network >> issue of not being able to download during the build step. (Almost always >> on the Windows side) >> >> I haven't seen it since then though - but i'm not pushing a commit every >> hour to prep for finalizing a release.... >> >> -Stopp >> >> On Friday, June 11, 2021 at 12:59:09 AM UTC-5 [email protected] wrote: >> >>> I had to re run a build for the dependency issue just before I replied >>> to you last night… >>> >>> I haven’t seen this dependency issue before, how long have you been >>> seeing it? >>> >>> On Fri, 11 Jun 2021 at 01:16, Bryan Stopp <[email protected]> wrote: >>> >>>> Yeah - basically i have to monitor the runs on a merge to main because >>>> if i don't and it fails, i can't re-run. Which defeats the whole idea of CD >>>> :( >>>> >>>> Hopefully the network issues are resolved now and the errors my builds >>>> were experiencing won't happen anymore. >>>> >>>> -Stopp >>>> >>>> On Thursday, June 10, 2021 at 2:51:01 PM UTC-5 [email protected] >>>> wrote: >>>> >>>>> Right I see, there's so many check_run events GitHub hides the >>>>> ci.jenkins.io check in the UI: >>>>> >>>>> https://github.com/jenkinsci/adobe-cloud-manager-plugin/runs/2777413446 >>>>> >>>>> not sure... :( >>>>> >>>>> On Thu, 10 Jun 2021 at 20:41, Tim Jacomb <[email protected]> wrote: >>>>> >>>>>> You should be able to run it from the page for the master build =/ >>>>>> >>>>>> This is what I see on a plugin I have with CD enabled: >>>>>> >>>>>> [image: image.png] >>>>>> >>>>>> On Wed, 9 Jun 2021 at 17:51, Bryan Stopp <[email protected]> wrote: >>>>>> >>>>> I'm still not seeing what you are seeing. >>>>>>> >>>>>>> Yes, if i look at a failed PR run >>>>>>> <https://github.com/jenkinsci/adobe-cloud-manager-plugin/pull/15/checks?check_run_id=2785016505>I >>>>>>> see that i can re-run that job. >>>>>>> >>>>>>> But if i click on the X next to my master commit, click on the >>>>>>> Details for any step in the run, it takes me to the Run page >>>>>>> <https://github.com/jenkinsci/adobe-cloud-manager-plugin/runs/2777413446>. >>>>>>> But on the left all that is listed are a bunch of "cd on: check_run" >>>>>>> builds, which are successful. I am not able to navigate from that page >>>>>>> to >>>>>>> anywhere that allows me to Re-run the Jenkins CI that failed. >>>>>>> >>>>>>> If i go to the Actions page directly, the only workflows that are >>>>>>> listed are the CD configured ones. Nothing about the Jenkins CI builds. >>>>>>> >>>>>>> (This wouldn't be much of an issue if my builds didn't constantly >>>>>>> fail due to the CI server not being able to download dependencies) >>>>>>> >>>>>>> -Stopp >>>>>>> >>>>>>> On Sunday, June 6, 2021 at 11:43:12 AM UTC-5 [email protected] >>>>>>> wrote: >>>>>>> >>>>>>>> There’s a button on the actions page once you click on CD for >>>>>>>> re-run all jobs >>>>>>>> >>>>>>>> On Sun, 6 Jun 2021 at 15:56, Bryan Stopp <[email protected]> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Tried this. There is no re-run option on for me on the failed >>>>>>>>> Continuous Delivery job. And it is only showing the CD Jenkins job. >>>>>>>>> Not >>>>>>>>> the post-master merge build which is required to pass for the CD >>>>>>>>> Workflow >>>>>>>>> to perform its release. >>>>>>>>> >>>>>>>>> I can re-run PR Merge checks. But not the post-PR merge build. >>>>>>>>> >>>>>>>>> Project in question: >>>>>>>>> https://github.com/jenkinsci/adobe-cloud-manager-plugin >>>>>>>>> >>>>>>>>> >>>>>>>>> -Stopp >>>>>>>>> >>>>>>>>> On Sunday, June 6, 2021 at 1:20:42 AM UTC-5 [email protected] >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> From the GitHub repo click on the x next to the commit, then >>>>>>>>>> click on Jenkins. >>>>>>>>>> >>>>>>>>>> That will take you to the GitHub checks page >>>>>>>>>> People with write access can click re-run from there >>>>>>>>>> >>>>>>>>>> On Sun, 6 Jun 2021 at 04:22, Bryan Stopp <[email protected]> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> How does one restart a build on the Jenkins CI system? I have >>>>>>>>>>> been getting failures due to the build being unable to download >>>>>>>>>>> artifacts >>>>>>>>>>> from the Jenkins repo. >>>>>>>>>>> >>>>>>>>>>> Specifically one of my CD release builds failed this way and i >>>>>>>>>>> have no idea how to boot it again without doing another push to the >>>>>>>>>>> main >>>>>>>>>>> branch. >>>>>>>>>>> >>>>>>>>>>> Thanks again everyone! >>>>>>>>>>> >>>>>>>>>>> -Stopp >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> You received this message because you are subscribed to the >>>>>>>>>>> Google Groups "Jenkins Developers" group. >>>>>>>>>>> To unsubscribe from this group and stop receiving emails from >>>>>>>>>>> it, send an email to [email protected]. >>>>>>>>>>> To view this discussion on the web visit >>>>>>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/80090907-4ba7-4e8d-ab6c-4abc4920fd0bn%40googlegroups.com >>>>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/80090907-4ba7-4e8d-ab6c-4abc4920fd0bn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>>>> . >>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>> You received this message because you are subscribed to the Google >>>>>>>>> Groups "Jenkins Developers" group. >>>>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>>>> send an email to [email protected]. >>>>>>>>> >>>>>>>> To view this discussion on the web visit >>>>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/27c4a2f4-f901-4e94-87c6-fdf82d8b4e6dn%40googlegroups.com >>>>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/27c4a2f4-f901-4e94-87c6-fdf82d8b4e6dn%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>>> . >>>>>>>>> >>>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "Jenkins Developers" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to [email protected]. >>>>>>> >>>>>> To view this discussion on the web visit >>>>>>> https://groups.google.com/d/msgid/jenkinsci-dev/ae77d96a-833b-45ba-bfb9-620dd2b9d4d6n%40googlegroups.com >>>>>>> <https://groups.google.com/d/msgid/jenkinsci-dev/ae77d96a-833b-45ba-bfb9-620dd2b9d4d6n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>> . >>>>>>> >>>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "Jenkins Developers" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> >>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/jenkinsci-dev/4ff063c4-0dc6-4b40-8841-256e6cae4a0en%40googlegroups.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/4ff063c4-0dc6-4b40-8841-256e6cae4a0en%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/c3fdf8a1-f5e0-47bf-8438-9304ece708a2n%40googlegroups.com >> <https://groups.google.com/d/msgid/jenkinsci-dev/c3fdf8a1-f5e0-47bf-8438-9304ece708a2n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAH-3BicgTtKQYFL0s50HUs2EqoMSjFOv%3DCV89W7rW4STBnNGOQ%40mail.gmail.com.
