Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
At first I thought this was due to errors an incorrectly upgraded plug-in, but even new jobs using the bare minimum of plugins (Vagrant, IRC) sometimes disappear after a reboot.
Comments
Comment #1
ergonlogicAlso note: #2078533: ci.aegirproject.org cannot send notifications to #aegir
Comment #2
anarcat CreditAttribution: anarcat commentedi fixed the IRC issue it seems, see that other issue for details.
now it seems that jenkins was running as root (ouch!). i restarted it as the jenkins user, but had to do the following:
and start jenkins with:
without -Xmx2048m -XX:MaxPermSize=2048M i was getting memory errors.
the memory usage of jenkins is ridiculous:
so now i can start jenkins (!?).
but the problem with older jobs being lost remains, and this is why:
i.e. i have no freaking clue why.
Comment #3
anarcat CreditAttribution: anarcat commentedit turns out that the vagrant plugin is messed up: we had the 1.5-SNAPSHOT plugin installed, but that plugin isn't actually available from jenkins-ci.org. https://wiki.jenkins-ci.org/display/JENKINS/Vagrant+Plugin# -> says that the latest is 0.1.4. if you look at their github (https://github.com/rtyler/vagrant-plugin) however, you see that they are, in their minds at 0.1.6, but that never got pushed to the central repo, it seems.
now we have the choice, either we learn how to build and use jenkins / ruby plugins, or we ditch that plugin and do things by hand.
Comment #4
anarcat CreditAttribution: anarcat commentedso it turns out jenkins was automatically upgraded during a nightly upgrade, which broke the vagrant plugin.
i opened an issue upstream in that plugin: https://github.com/rtyler/vagrant-plugin/issues/35
but in the meantime the only solution we've found is to run jenkins by hand.
Comment #5
anarcat CreditAttribution: anarcat commenteddisabled the following jobs:
those were already disabled, i think:
Comment #6
anarcat CreditAttribution: anarcat commentedwhat's up with this?
from what i remember, the next step was to recreate those tasks by hand without using the vagrant plugin... on which there is no update, btw.
Comment #7
helmo CreditAttribution: helmo commentedThe repo and issue mentioned in #4seem to have little to no activity.
There are some forks though: https://github.com/rtyler/vagrant-plugin/network Anything usefull there?
Or could we do without the vagrant plugin, like: http://larrycaiyu.com/blog/2011/10/21/make-ci-easier-with-jenkins-ci-and...
Comment #8
ergonlogicThis appears to be fixed. Also, we're rebuilding our tests to be as self-contained as possible, in order to make recovery from anything like this much quicker.
We can follow up in #1912248: cleanup jenkins build scripts.