-
-
Notifications
You must be signed in to change notification settings - Fork 1
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
Modernize jenkins.plone.org #235
Comments
@tisto all nice and dandy, but as every time we talk about it: who has the time to invest on it? Regarding Jenkinsfiles, it reduces the core jobs, but you still have to keep mr.roboto around to automatically ping it. Or did I miss something? |
@gforcada I just added this as a roadmap/plan. I am aware that someone needs to do this and we are all short on time. :) The really nice thing about the Github-plugin is that usually, you don't have to worry about anything. As sait, it automatically creates all the triggers and automatically detects and new branches, Jenkinsfiles and also takes care of the pull request updates on Jenkins. The integration is as good as with Travis. Though, mr.roboto is, of course, a different beast. I guess we have to somehow keep the manual triggering we have right now. I'd recommend to go step by step and decide along the way what to do exactly... |
@gforcada are you going to make it to Tokyo? If not, maybe we can plan a CI sprint next year to tackle this... |
No tokyo for me no 😞 a sprint next year would be great yes 👍 |
@gforcada Too bad! Yeah, then let's try to get together next year. There will also be the Beethoven sprint in Bonn again and we would love to have you there! |
@tisto regarding the first point... do they told you of an actual hard deadline? 🤔 we just get moving that fast even if it takes one year to shut down that vServer. And given the cheapness of the servers currently on hetzner it should not be a problem. |
Long-term roadmap:
The text was updated successfully, but these errors were encountered: