-
-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://twitter.com/jenkins_release is many weeks behind #3085
Comments
Currently checking as we have no knowledge of this account and the associated (assuming there is one) bot. Ping @oleg-nenashev @olblak @rtyler @halkeye do you happen to know how this account is managed? |
Possibly @kohsuke ? |
it says its managed by dlvr.it, so I would contact https://dlvrit.com/ and see if they can help you recover the account. This bot is super super super old. |
https://groups.google.com/g/jenkinsci-dev/c/twpI9vfBfbI/m/YBibmOpaCwAJ pretty much says the same thing |
https://groups.google.com/g/jenkinsci-dev/c/nlw7DHoWoWk/m/LesxKCHmAwAJ says rtyler set it up |
At some point I offered to introduce Twitter as code for that repo. But had no time to finally work on it |
Does that mean you have access to the account, or that you don’t? |
At some point I offered to introduce Twitter as code for that repo. But had no time to finally work on it. The flow for this account is pretty much broken, and I don't think there is much value for users |
Twitter as code was for the jenkins account wasn’t it? Not for the releases one? Which is just based off of the RSS feed |
Sent an email to @rtyler and @kohsuke (with @MarkEWaite and @halkeye ) to check if they have access. Without any feedback middle september, we'll contact dlvr.it to try to recover the account. |
Got the email/password of the Twitter from Kohsuke privately, many thanks! Shared in the 1 password vault, but I still need a hand from KK to change the email to private jenkins infra email, because it asks for a validation when trying to log in. |
Email sent to dlvr.it support in order to retrieve the corresponding account. |
It's probably better to send @kohsuke an email. He is usually pretty responsive because I gues he'll be busy next week with other things |
I have already but no response yet. I should meet him next week at DevopsWorld I'll ask him again. |
As we couldn't met last week, I'll look into automating ourselves the publication of these releases. |
https://github.com/umputun/rss2twitter seems a good candidate. Gave a look at its code, short and fine, should be easy to deploy, currently testing the app locally. |
when i looked into it, the issue is its history is inmemory, so if the process restarts, it re-posts (I think). I was going to try to submit a PR to make it look at the body of the last few posts ($rss.length) and see if the post body matches. If so skip. That way if a service gets restarted, we don't get it spamming people |
Thanks for the feedback!
Started in dry mode, it seems to take only the current day content in account, not totally sure still testing.
Interesting, worth another look. |
I don't think restarts are an issue, cf my local test logs from yesterday and the restart today: Complete log after 3 days and 2 manual restarts:
Preparing a chart to deploy it on prodpublick8s. |
Configured in dry mode for now. Ref: jenkins-infra/helpdesk#3085"
* feat: deploy `rss2twitter` service on `prodpublick8s` Configured in dry mode for now. Ref: jenkins-infra/helpdesk#3085" * feat: deploy `rss2twitter` service on `prodpublick8s` Configured in dry mode for now. Co-authored-by: Damien Duportal <damien.duportal@gmail.com>
Gotta fix the formatting but here is the first tweet from the rss2twitter service: https://twitter.com/jenkins_release/status/1586462810107744257 |
The last tweet looks good, closing this issue 🙂 |
Service(s)
Other
Summary
https://twitter.com/jenkins_release just announced the release of Artifactory Plugin 3.16.1.
That version
https://www.jenkins.io/releases.rss looks reasonable at a glance, so something's wrong with whatever is processing the feed.
Reproduction steps
No response
The text was updated successfully, but these errors were encountered: