Even though the last message in the DockerHub log:
Successfully built 73dfc9054b7e
DockerHub states that the status is 'Build Error'. The image builds correctly on multiple local machines, and the last message from the log has no errors. What could be the reason for the build error? Does anyone know if there is there another place besides the DockerHub log where we can see why the build was not successful?
Docker seems to be very promising but these types of errors make us hesitate when thinking about migrating some of our nodes to docker containers.
Thanks.
I did search your issue through the build id, and tried reproducing the bug. You might have seen me forking your public GitHub branch. We found and resolved the issue.
If you see the latest build for anaconda-plus, it succeeded.
If you encounter such issue again, please create a support ticket.
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?
Today I noticed that several of our Jenkins jobs (which are independant, different projects and everything) failed.I investigated an finally listed all processes on the machine that Jenkins uses with the top command. It showed me a very greedy process launched by Jenkins, which name is iLmBjh. Not very clear, isn't it?I tried some things and finally killed it. But it appeared again when I launched a new Jenkins job.Do someone know what this process does? It's the first time I see it on the processes list...
Ok, I guess I found the problem and it's kind of surprising. On our Jenkins instance, we had the JiraTestReporter plugin installed. Our Jira licence ended today. And when I checked the Jenkins logs, it was full of Jira error messages.What is disturbing is that we weren't using it at all... in any of our jobs!I uninstalled it and was able to run my job again. The iLmBjh process did not come back.
(I understand this question is somewhat out of scope for stack overflow, because contains more problems and somewhat vague. Suggestions to ask it in the proper ways are welcome.)
I have some open source projects depending in each other.
The code resides in github, the builds happen in shippable, using docker images which in turn are built on docker hub.
I have set up an artifact repo and a debian repository where shippable builds put the packages, and docker builds use them.
The build chain looks like this in terms of deliverables:
pre-zenta docker image
zenta docker image (two steps of docker build because it would time out otherwise)
zenta debian package
zenta-tools docker image
zenta-tools debian package
xslt docker image
adadocs artifacts
Currently I am triggering the builds by pushing to github and sometimes rerunning failed builds on shippable after the docker build ran.
I am looking for solutions for the following problems:
Where to put Dockerfiles? Now they are in the repo of the package needing the resulting docker image for build. This way all information to build the package are in one place, but sometimes I have to trigger an extra build to have the package actually built.
How to trigger build automatically?
..., in a way supporting git-flow? For example if I change the code in zenta develop branch, I want to make sure that zenta-tools will build and test with the development version of it, before merging with master.
Are there a tool with which I can overview the health of the whole build chain?
Since your question is related to Shippable, I've created a support issue for you here - https://github.com/Shippable/support/issues/2662. If you are interested in discussing the best way to handle your scenario, you can also send me an email at support#shippable.com You can set up your entire flow, including building the docker images, using Shippable.
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 currently seeing an issue in jenkins that even if there is a change in the build, it always says 'No changes from last build'(which is taken from perforce). And in the console output I see that mail is triggered to concerned people who have modified the file in the latest build.
Any Idea what could be the reason ?
Thanks in adv
Have you seen this issue reported on the Jenkins site: 'Polling builds project regardless of changes'?
Perhaps it is related to the issue you are having.