Bamboo build failing after intalling Clover plugin for Grails - grails

After installing clover plugin my builds have started failing with the following error message:
“Failed to install plugin [clover-3.0.2]. Plugin has missing JAR dependencies.”
Any Ideas? As far as I can tell its missing hibernate core 3.1.1 GA but i am pretty sure i got that since grails runs fine.

Sometimes I have this kind of mess up. For me it helps to wipe out my .grails home directory for the specific project. I think that the download was not completed somehow.
Try to delete .grails\1.3.7\projects\<PROJECTNAME>\plugins\clover-3.0.2 from your home directory. If this does not help, try to wipe out this plugins folder completely. I guess it will help. Good luck :-)

I had an admin clear .ivy2 cache and it worked at least for now.

Related

Jenkins plugin updates are unavailable

I have updated my jenkins server and see the following message for some plugins. I am not sure how to fix this. I looked at the dependencies section for that plugin and I see they are already installed. Not sure what else is missing so I can see the update available. Dependency for this is Mailer which is already installed on my server.
That is frustrating but you can try uploading plugins manually.
You can download plugins from here link to plugin storage.
Of course you have to roughly see what version of the plugin goes with your jenkins version.
Once you downloaded 'proper' plugin version, you go to manage plugins, advanced tab and there you can upload the plugin file. After that restart jenkins and check changes. You should really go to manage plugins, updated plugin tab and update selected plugins...
It could be guess work, but I'm sure after a couple of guesses you'll get to the version of Jenkins you have.
You might need to upgrade jenkins.. here are all jenkins war files:
https://get.jenkins.io/war-stable/
Last but not least... don't try to fix all dependencies.. fix those you use, rest is optional.

Unable to upgrade git-client plugin in jenkins

It appears I am unable to fix this situation. It seems jenkins thinks I should have a newer version of a git plugin, one that is not out yet. I do not see an option to upgrade.
Any idea how to fix this?
The first thing to check is your Jenkins version itself.
Try and upgrade Jenkins (war-stable/latest/jenkins.war) to see if the core client allows for those dependencies to be resolved.

Jenkins plugin not showing up

probably a newbish question, but that's what I am. I need to run a post build script, so I installed the post-build-task plugin onto my Jenkins server (v2.5). For some reason, when I go to the job configuration page, there is no checkbox or anything for the plugin. Is there some common pitfall I am stepping into or something?
Edit: I have restarted the server.
So it was a blatantly simple issue. The job I was working in was a pipeline, and it needed to be a freestyle project.
Restarting will update the plugins..

Running Stardog-examples, build issues

I'm getting extremely frustrated. I've been trying to learn semantic web programming for the entire weekend and I've gotten no where. Nothing seems to build or work.
I'm new to using maven and gradle but I've followed all the steps.
Trying to build the stardog-example code
https://github.com/clarkparsia/stardog-examples
But when I run the gradle command, it says
"Url to Stardog repository is not defined, Set up the property 'stardogRepo' in gradle.properties.
I can't even find gradle.properties. Looked everyhere =/ It's not in the gradle folder either.
Any help will be appreciated
Sorry, those examples are in flux as we get ready for the Stardog 3 release.
Your best bet is to go back and check out the 2.2.x version of the examples.
We'll have it finalized for the release or shortly thereafter.

jenkins missing jobs after removal of plugins

I have a Jenkins Server (1.510) on Win 2008 with ~100 jobs.
After installing and then uninstalling the CloudBees (Plugin_1, Plugin_2) set of plugins + restart I have the following issues:
half of the Jobs are now missing.
many plugins are not functioning well, for example the green-balls plugin is not working and also the entry to launch the backup plugin is missing
many built in Jenkins buttons such the new "Credentials" is missing from the "Jenkins Configure" Menu.
Looking at the FS, i still see all the jobs.
I already tried :
Using the reload configuration
Reinstalling the plugins
Reinstalling Jenkins with the same version once again
Still the jobs are missing
Any idea how to solve it?
Thanks,
Doron
When job is loaded, many of the related Java classes get instantiated. If instantiation fails, usually because some plugin has been removed and that class is no longer available at all, then the job is hidden.
I suspect you have accidentally removed some other plugin too.
Note: Before actually doing anything, take full backup! Easiest is to backup entire Jenkins folder, where the jobs, configuration etc reside.
Easiest solution might be to just install Jenkins from scratch, install the plugins you do need (see below for troubleshooting if you're missing some), then copy the jobs subfolder to the new Jenkins. It might be best to do any configuration under Manage Jenkins by hand, but you can also just try copying the related XML config files.
If you are missing a plugin and can't figure out which one, you should look at jenkins.out.log and jenkins.err.log log files and search for exceptions happening after Jenkins is started. That may give you a clue on what plugin you are missing.
You can also try editing the job XML files to remove build steps you identified from the exceptions (remember to take backups first!), then restart Jenkins or select Reload configuration from disk from Manage Jenkins page.
If not solved, but you find relevant-looking exceptions or something else interesting, please update the question with details.
After I upgraded Jenkins, one of my jobs disappeared. I found out that although my job directory still existed, the config.xml file inside had somehow gone missing.
I restored this file from a backup, after updating all the plugins that needed updating, and reloaded the configuration, and the job reappeared in Jenkins.

Resources