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.
Related
I ran a build yesterday, hoping I would read some logs today.
I came today, and got an error 404 when trying to access the build. Strange.
Running another build, shows my build actually did run, but it is unreachable.
Is there a way to get my hands on the logs?
Notice build #10 is missing, even though it did start.
Probably a windows update is to blame for this.
The broken link is http://192.168.80.10:8080/job/Dev_git/10
More information on a run can usually be found using the context menu under Console Output. This is only accessible if you have the correct permissions set in Jenkins.
This of course does not work, if a build is missing. One reason could be that your Jenkins is configured in a way that only a certain number of historic builds are kept, see Build History Missing in Jenkins for an explanation how to deal with that.
However, your case seems to be different, because a build in the middle of the history is missing. For this, I suggest to look around in the jobs directory of your Jenkins installation where it stores all the configuration and run data.
References
https://wiki.jenkins.io/display/JENKINS/Administering+Jenkins
Where does Jenkins store configuration files for the jobs it runs?
I'm new to jenkins.
For that sake I installed the latest version of jenkins i.e. 1.632 on my ubuntu and deployed a war using post build actions in the configuration part. That worked fine for me.
Then I changed a few things in the build making sure that it fails when deployed and it effectively did and I'm not able to access the application die to deployment failure.
But I'm curious here, I have heard that in case of a build failure jenkins makes sure that the previous build remains deployed so that the application is always up and running. Please clarify if I'm wrong or doing anything wrong in my deployment steps.
I did searched a lot about this but couldn't find a valuable answer.
Haven't done much with the deploy plugin but it states this in the docs
Now when you trigger this job you can enter the build number (or use
any other available selector) to select which build to redeploy.
So you can set up a build on failure which will redeploy the last stable version. Here is also an example how to get the last stable build number:
http://<JENKINS>/job/<JOB_NAME>/lastStableBuild/buildNumber
I am working on a research project where I am going to analyze several of the commits in the version control history for Ruby on Rails. I would like to see which commits pass or fail Rails' test scripts. If it is possible, I would also like to see which commits can be built.
For example, if I were analyzing a Java project, I would try to compile the project at each commit. If the compilation process failed, then I would know that the commit broke the build. Then, on a successful build, I could run the test scripts.
I know that most Ruby projects do not have a build process in the same sense that Java projects do because Ruby is interpreted. So an error that a compiler could check, like a syntax error or type error, will always be found at runtime. Because of this, I'm not sure whether Rails has a build process and if it does, what that process is. Does Rails have a build process or a process that is analogous to compiling a project in a compiled language?
Yes and no. There are definitely some setup steps before you can run any tests.
Like all good open source projects if you scroll down on the README page at the link you included in your question, you'll see the Contributing section. That links to everything you need to know in order to set up Rails and start either developing, or doing your test research project thing.
I am on a redhat linux box. I recently updated Jenkins to version 1.509 only to find that after doing so it has "forgotten" two of my jobs/projects. The jobs can still be found on my Jenkins machine under /var/lib/jenkins/jobs, but they no longer show up in the Jenkins GUI. I attempted to re-create them based off the configuration file I have, but I am not confident I have totally re-created the functionality they had.
I also tried to copy the job and or rename it hoping that would get jenkins to see it, but no luck. I had tried cp -r /var/lib/jenkins/jobs/JOB1 /var/lib/jenkins/jobs/JOB2. I also restarted the service a number of times. Finally I updated all of my plugins on the off chance that was somehow related.
So my question is "How can I get Jenkins to notice these jobs?" or failing that "can I run these jobs from in the terminal?"
NOTE: I am not discouraging others from upgrading Jenkins. After I upgraded Jenkins did complain about a number of things which I didn't pay enough attention to which I believe got me into this mess in the first place.
If I were you, I would try the Jenkins CLI (from $JENKINS_URL/cli) and use the create-job command and feed the job configuration file to the cli's stdin.
If that does not help, I would inspect Jenkins log files (you are saving stdout and stderr of Jenkins somewhere, right?) for any errors or clues. If the job failed to load because of some tag that you can guess is provided by a plugin, try to remove that part from the config file.
If that does not help, I would upgrade Jenkins. I think there might be some fixes related to this in the LTS version changelog since 1.509.
And above all... if I were you, I would start making backups of the job configuration files.
I regularly back up the global config.xml, all the job config.xml files and all the plugins. Using these I can set up my Jenkins from scratch. And I do that to set up a test instance where I try any plugin or Jenkins core upgrade. If I see no problems after running a few of the trickiest builds, I know I can upgrade the production instance with much more confidence.
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.