I do understand that CloudBees is probably quite busy... but you have to note this issue has been open on both GitHub and the Jenkins JIRA for over a month without anyone acknowledging it or taking ownership. I understand the correct action for subscribers is mostly "just don't upgrade," but it would be nice if the tickets could be acknowledged. -Alan
On Friday, January 21, 2022 at 6:31:06 AM UTC-7 [email protected] wrote: > Hi, > > While our teams are aware of this issue and we should look into it soon > enough, I can't commit to any precise date. In particular in this case > because the workaround is easy: going back to 1.32 AFAIU. > Many other more pressing priorities are higher than this (e.g. making sure > the hundreds of plugins, many OSS, that CloudBees verifies > <https://docs.cloudbees.com/docs/admin-resources/latest/assurance-program/> > are ready for the next LTS). > > I would say there are 3 options: > > - Wait until somebody picks it up. > - File the fix yourself (or someone in your company, or paying someone > to do it), then we can probably try and fast track the merge & release for > it. > - for CloudBees customers only: use ZenDesk to discuss further > options. > > Hope this helps clarify. > > Le mer. 19 janv. 2022 à 19:44, [email protected] <[email protected]> > a écrit : > >> Appears that no one at CloudBees has looked at the issue with the AWS >> Credentials plugin. The issue is over a month old. Is there a contact at >> CloudBees I could ping to find out options? Thanks. >> -Alan >> >> On Thursday, January 13, 2022 at 2:37:20 PM UTC-7 >> [email protected] wrote: >> >>> Frankly I don’t have any experience doing this… so any help would be >>> appreciated. Thanks for the reply! >>> >>> -Alan >>> >>> >>> >>> *From:* [email protected] <[email protected]> *On >>> Behalf Of *Baptiste Mathus >>> *Sent:* Thursday, January 13, 2022 2:27 PM >>> *To:* [email protected] >>> *Subject:* Re: Support for CloudBees plugins >>> >>> >>> >>> Hi, >>> >>> Thanks for the notice. Reporting the bug in Jira is the right way indeed. >>> >>> I know nothing about this plugin myself, but looking around in the last >>> changes, it looks like >>> https://github.com/jenkinsci/aws-credentials-plugin/pull/88/files#r772008354 >>> >>> could be a good lead. >>> >>> >>> >>> I would recommend creating a PR with something around this. The build >>> will then automatically create an "incremental" and allow you to test this >>> to help fix it. Doing it would be invaluable to at least identify the exact >>> cause for your issue. >>> >>> >>> >>> If you do not know how to do it, I *might* give it a look later this >>> week or next one, but no guarantee. >>> >>> >>> >>> Cheers >>> >>> >>> >>> Le jeu. 13 janv. 2022 à 21:39, [email protected] <[email protected]> >>> a écrit : >>> >>> For last 2 weeks, been trying to get attention on bug with CloudBees AWS >>> credentials plugin 1.33. The external ID feature causes failures for >>> anything using an AWS role without an external ID. >>> >>> >>> >>> I can't seem to get a response on this problem (looks like others have >>> issues too). Is there a process besides opening a ticket and waiting? >>> >>> >>> >>> Issue on Jenkins JIRA: >>> >>> https://issues.jenkins.io/browse/JENKINS-67452 >>> >>> >>> >>> Issue on GitHub: >>> >>> https://github.com/jenkinsci/aws-credentials-plugin/issues/116 >>> >>> >>> >>> Thanks for any advice. >>> >>> -Alan >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" 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-users/be6909de-b449-4d02-8c0f-8042bbe7299an%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-users/be6909de-b449-4d02-8c0f-8042bbe7299an%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" 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-users/CANWgJS6XAJQKwRpNJPjzuH5BK4B-H6sWqS4a7nfbr0_AtpA7cA%40mail.gmail.com >>> >>> <https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6XAJQKwRpNJPjzuH5BK4B-H6sWqS4a7nfbr0_AtpA7cA%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" 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-users/90f76464-31c7-411e-a0fe-9b8422a2f710n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-users/90f76464-31c7-411e-a0fe-9b8422a2f710n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" 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-users/e3ed0d75-a95b-4a1f-8945-12d76c1630e4n%40googlegroups.com.
