-
Notifications
You must be signed in to change notification settings - Fork 6
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
docker credentials and docker push #11
Comments
- maven step will pull directly from spring-projects/spring-petclinic github. - after building and testing, petclinic WAR is the artifact of this job. - downstream job is docker build. This uses copy artifact plugin to copy upstream artifact WAR into its workspace. - then it takes care of building and pushing image (this part is still WIP, waiting on #11) The advantage of this approach is I dont need to fork petclinic github and add a dockerfile to that project.
To push image using Docker, I have several options: Option 1
This would work but not in an automated Jenkins container scenario. In a Jenkins container I don't have the Option 2 The second option: Use the Docker Build Steps plugin. Option 3 The third option:
Where In this approach I need to feed in additional
Special characters such as Option 4 Trying another plugin, Cloudbees Docker Publish. UpdateThe I frequently get any of the following errors:
|
It is possible that all these problems are because I use the official Jenkins docker image for building my Jenkins docker container. I ran a quick experiment on Saturday and it shows I need to explore building the Jenkins image from scratch. (Issue #12 ) |
- instead of official jenkins image. - hopefully this might affect #11
The |
- the latest built image should be tagged with latest as well as the build number.
While working on #10 I am encountering the following issue
The text was updated successfully, but these errors were encountered: