Re: is docker pipeline plugin maintained?
Thanks Mark! unfortunately my pipeline is complex enough (uses several withenv, etc...) so the use of sh steps is not feasible. Il giorno lunedì 28 agosto 2023 alle 05:37:26 UTC+2 Mark Waite ha scritto: > On Wednesday, August 23, 2023 at 2:04:20 PM UTC-6 valerio wrote: > > Hi, > > With my team we've started using docker pipeline plugin within jenkins and > it seems working cool! > The plugin main page (https://plugins.jenkins.io/docker-workflow/) states > it's up for adoption > > * Does it mean the plugin is not maintained anymore? > * If yes, is there any maintained plugin alternative to docker pipeline to > run commands inside docker container within a scripted jenkins pipeline? > > Thanks a lot for your support, > Valerio > > > A plugin that is up for adoption has no active maintainer. Plugins that > are up for adoption tend to be less well maintained than plugins that are > not up for adoption. > > Commands can be run inside a Docker container from a scripted Jenkins > Pipeline by using sh steps that perform docker commands. The Docker > pipeline plugin is a good choice for simple use cases. It is used in the > Jenkins tutorials. I think it is a reasonable choice to use. > > Mark Waite > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6aad6255-afb1-4681-af34-2e053778c17cn%40googlegroups.com.
Re: is docker pipeline plugin maintained?
On Wednesday, August 23, 2023 at 2:04:20 PM UTC-6 valerio wrote: Hi, With my team we've started using docker pipeline plugin within jenkins and it seems working cool! The plugin main page (https://plugins.jenkins.io/docker-workflow/) states it's up for adoption * Does it mean the plugin is not maintained anymore? * If yes, is there any maintained plugin alternative to docker pipeline to run commands inside docker container within a scripted jenkins pipeline? Thanks a lot for your support, Valerio A plugin that is up for adoption has no active maintainer. Plugins that are up for adoption tend to be less well maintained than plugins that are not up for adoption. Commands can be run inside a Docker container from a scripted Jenkins Pipeline by using sh steps that perform docker commands. The Docker pipeline plugin is a good choice for simple use cases. It is used in the Jenkins tutorials. I think it is a reasonable choice to use. Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a60464b4-afe0-4e39-9fc1-5705da351c9dn%40googlegroups.com.
is docker pipeline plugin maintained?
Hi, With my team we've started using docker pipeline plugin within jenkins and it seems working cool! The plugin main page (https://plugins.jenkins.io/docker-workflow/) states it's up for adoption * Does it mean the plugin is not maintained anymore? * If yes, is there any maintained plugin alternative to docker pipeline to run commands inside docker container within a scripted jenkins pipeline? Thanks a lot for your support, Valerio -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/afc32e80-b2f4-4278-8eb5-18f79c725564n%40googlegroups.com.
Docker pipeline plugin
Hi everyone,
I'm struggling a little bit with the docker pipeline plugin,
the building of small image goes well, but when I try to push it to my
private dockerhub registry, I get the following
[3-email_feature_jenkinsTest-5LSQUNLKW2A3IQQVQE7P6TOWAJPMB4NKMLQH3CFFATJHMGMXUSZQ]
Running shell script
+ docker tag --force=true hungdo93/testatot
registry.hub.docker.com/hungdo93/testatot:test
unknown flag: --force
See 'docker tag --help'.
+ docker tag hungdo93/testatot registry.hub.docker.com/hungdo93/testatot:test
[3-email_feature_jenkinsTest-5LSQUNLKW2A3IQQVQE7P6TOWAJUJAUKMLQH3CFFATJHMGMXUSZQ]
Running shell script
+ docker push registry.hub.docker.com/hungdo93/testatot:test
The push refers to a repository [registry.hub.docker.com/hungdo93/testatot]
2c55342d652e: Preparing
28baa3bk1903: Preparing
5b1e37e74377: Preparing
04a294je844e: Preparing
denied: requested access to the resource is denied
This is the relevant part of my jenkinsfile
def dockerImage
stage('build docker') {
sh "cp -R src/main/docker target/"
sh "cp target/*.war target/docker/"
dockerImage = docker.build('hungdo93/testatot', 'target/docker')
}
stage('publish docker') {
docker.withRegistry('https://registry.hub.docker.com/',
'docker-hub-hung') {
dockerImage.push 'test'
}
}
}
Ofcourse, I've made a username/password credentials id 'docker-hub-hung'
and my private repo is hungdo93/testatot.
I have used the BlueOcean UI for this.
Thanks in advance!
Hung
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/02fbca3e-f045-4a16-9c74-e21ecc4b6ca0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
How are you using the the docker pipeline plugin ? Is it useful enough for you ? Can i think of scaling with it by starting slave containers on remote docker hosts ?
Hi,
My project consists of a number of services and i have a build-deploy-test
pipeline for each. The infrastructure consists of an array of docker hosts
where applications are deployed and tested and i have no shortage of them.
The build part (mostly maven) happens on Jenkins master node only. For the
deployment n testing, i have a dedicated Ansible machine and a jmeter host
machine which has the latest version of them installed. I would like to
change that to be able to specify a version of Ansible and Jmeter. Now the
deployment and test machines are where i feel the shortage of hardware.
Today i was experimenting with docker pipeline plugin majorly because i
hoped to put the abundant docker machines to do the deployments and tests
as well. I couldn't get it to work because my docker daemons are not
listening on the default or any other port and i will have to get it
changed. I have a few questions that will basically help me decide if this
plugin is of any use in my situation or not.
1- I will be using only remote docker hosts to start slave containers and i
will be implementing everything with pipeline code. During this execution,
is it still going to eat up an executor on master ?
2 - Is this plugin any easier to use than just adding the docker machines
as slaves and start the containers via sh commands and executing what you
need ?
3 - Is Jenkins creating any workspace on remote docker host via this syntax
- docker.withServer('tcp://dockerhost:2376', 'credentials') {...} ? How is
doing it without SSH ?
4 - I do my maven builds on master node and obviously there is a huge
cache. Is there any benefit running the maven build inside a container on
master node after mounting the cache ? It looks like it is only going to
take more resources.
5 - In the docker pipeline syntax, it seems like we have to specify a port
for this temp container - withRun('-p 8080:80')
how do i make sure that different pipelines get a free port everytime
?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/967bf954-0fc2-4eab-bb73-2db10e6566c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Issue getting Docker Pipeline plugin to build an image
Right - I haven't used upstart for some time, but if it is like systemd, it may be placing constraints on child processes (like app armour) that prevent certain things from working. In the log for the build you should see the actual command used to build the image, might be worth noting if it looks any different to what you would run yourself. On Thursday, June 9, 2016 at 4:34:18 PM UTC+10, Lyle Dietz wrote: > > I've made progress, it only happens when I get Upstart to start Jenkins. > If I start Jenkins from within a byobu session it works fine. > > I'm guessing it has something to do with the environment. Now I just have > to track down what that difference is. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9f24c3fc-7ab3-40f6-96b2-6812f4a4149b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue getting Docker Pipeline plugin to build an image
I've made progress, it only happens when I get Upstart to start Jenkins. If I start Jenkins from within a byobu session it works fine. I'm guessing it has something to do with the environment. Now I just have to track down what that difference is. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/405b4f4b-801f-4919-823d-544079eeda03%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue getting Docker Pipeline plugin to build an image
> The original worked fine when using "sh 'docker build..." inside a pipeline script? Yeah, I used that to confirm there wasn't some problem with the daemon because I was starting to get paranoid. --- sh 'docker build -t openshift/wildfly:10 .' --- Works just fine. Mind you, the VM I installed it on was brand new as well. I'm thinking that perhaps I should re-install it, or blow away the Jenkins installation and start again. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6e0554d6-4f29-41b9-99a9-7c0210367da0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue getting Docker Pipeline plugin to build an image
Sanity - well that is much more serious ;)
OK, well new VM to me implies it was to do with the forever problematic
bind mounting and docker (perhaps users and permissions), although this
normally shows up with ".inside" not so much with build that I have seen.
The original worked fine when using "sh 'docker build..." inside a pipeline
script?
On Thursday, June 9, 2016 at 2:38:10 PM UTC+10, Lyle Dietz wrote:
>
> I don't feel stupid anymore, I feel like I'm going insane.
>
> I just set up a brand new VM and the exact same repository builds. Maybe I
> need a holiday.
>
> On the original VM I didn't have any issues with building when using a
> shell command.
>
> On Thursday, 9 June 2016 12:23:49 UTC+10, Michael Neale wrote:
>>
>> Try not to feel stupid ;)
>>
>> The @ directories I believe due to locking - when a direcotry is locked
>> and a step or a build wants to run in there, it appends a number, but I
>> don't think that is your problem.
>>
>> Docker pipeline bind mounts in the workspace, so perhaps how your daemon
>> is running vs the slave don't line up - this can be the case on OSX/windows
>> (pre the "new" docker beta which uses more native virtialisation on osx).
>>
>> Can get the docker image to build if you run "sh 'docker build -t
>> openshift/wildfly:10 .' ?
>>
>> On Wednesday, June 8, 2016 at 3:23:43 PM UTC+10, Lyle Dietz wrote:
>>>
>>> I'm having issues trying to build a Docker image with the Docker
>>> Pipeline plugin.
>>>
>>> I've tried searching, but no-one seems to be having the issue, and all
>>> the documentation I see suggests I'm not doing anything stupid.
>>>
>>> My current Jenkins file is as follows (I've pared it back for
>>> simplicity/debugging):
>>>
>>>
>>> #!groovy
>>>
>>> node {
>>> stage 'checkout'
>>> checkout scm
>>>
>>> stage 'build'
>>> def image = docker.build('openshift/wildfly:10')
>>> }
>>>
>>>
>>> The output from the job is:
>>>
>>> Started by user Lyle Dietz
>>> Cloning the remote Git repository
>>> Cloning repository
>>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
>>> > git init /home/jenkins/.jenkins/workspace/wildfly@script # timeout=10
>>> Fetching upstream changes from
>>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
>>> > git --version # timeout=10
>>> using .gitcredentials to set credentials
>>> > git config --local credential.username jenkins # timeout=10
>>> > git config --local credential.helper store
>>> --file=/tmp/git2241825672262408901.credentials # timeout=10
>>> > git -c core.askpass=true fetch --tags --progress
>>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
>>> +refs/heads/*:refs/remotes/origin/*
>>> > git config --local --remove-section credential # timeout=10
>>> > git config remote.origin.url
>>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git #
>>> timeout=10
>>> > git config --add remote.origin.fetch
>>> +refs/heads/*:refs/remotes/origin/* # timeout=10
>>> > git config remote.origin.url
>>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git #
>>> timeout=10
>>> Fetching upstream changes from
>>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
>>> using .gitcredentials to set credentials
>>> > git config --local credential.username jenkins # timeout=10
>>> > git config --local credential.helper store
>>> --file=/tmp/git4715501803936103145.credentials # timeout=10
>>> > git -c core.askpass=true fetch --tags --progress
>>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
>>> +refs/heads/*:refs/remotes/origin/*
>>> > git config --local --remove-section credential # timeout=10
>>> > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
>>> > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
>>> Checking out Revision 4e21d6895f1505810a35774f7ee6e339658c8252
>>> (refs/remotes/origin/master)
>>> > git config core.sparsecheckout # timeout=10
>>> > git checkout -f 4e21d6895f1505810a35774f7ee6e339658c8252
>>> > git rev-list 4e21d6895f1505810a35774f7ee6e339658c8252 # timeout=10
>>> [Pipeline] node
>>> Running on master in /home/jenkins/.jenk
Re: Issue getting Docker Pipeline plugin to build an image
I don't feel stupid anymore, I feel like I'm going insane.
I just set up a brand new VM and the exact same repository builds. Maybe I
need a holiday.
On the original VM I didn't have any issues with building when using a
shell command.
On Thursday, 9 June 2016 12:23:49 UTC+10, Michael Neale wrote:
>
> Try not to feel stupid ;)
>
> The @ directories I believe due to locking - when a direcotry is locked
> and a step or a build wants to run in there, it appends a number, but I
> don't think that is your problem.
>
> Docker pipeline bind mounts in the workspace, so perhaps how your daemon
> is running vs the slave don't line up - this can be the case on OSX/windows
> (pre the "new" docker beta which uses more native virtialisation on osx).
>
> Can get the docker image to build if you run "sh 'docker build -t
> openshift/wildfly:10 .' ?
>
> On Wednesday, June 8, 2016 at 3:23:43 PM UTC+10, Lyle Dietz wrote:
>>
>> I'm having issues trying to build a Docker image with the Docker Pipeline
>> plugin.
>>
>> I've tried searching, but no-one seems to be having the issue, and all
>> the documentation I see suggests I'm not doing anything stupid.
>>
>> My current Jenkins file is as follows (I've pared it back for
>> simplicity/debugging):
>>
>>
>> #!groovy
>>
>> node {
>> stage 'checkout'
>> checkout scm
>>
>> stage 'build'
>> def image = docker.build('openshift/wildfly:10')
>> }
>>
>>
>> The output from the job is:
>>
>> Started by user Lyle Dietz
>> Cloning the remote Git repository
>> Cloning repository
>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
>> > git init /home/jenkins/.jenkins/workspace/wildfly@script # timeout=10
>> Fetching upstream changes from
>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
>> > git --version # timeout=10
>> using .gitcredentials to set credentials
>> > git config --local credential.username jenkins # timeout=10
>> > git config --local credential.helper store
>> --file=/tmp/git2241825672262408901.credentials # timeout=10
>> > git -c core.askpass=true fetch --tags --progress
>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
>> +refs/heads/*:refs/remotes/origin/*
>> > git config --local --remove-section credential # timeout=10
>> > git config remote.origin.url
>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git #
>> timeout=10
>> > git config --add remote.origin.fetch
>> +refs/heads/*:refs/remotes/origin/* # timeout=10
>> > git config remote.origin.url
>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git #
>> timeout=10
>> Fetching upstream changes from
>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
>> using .gitcredentials to set credentials
>> > git config --local credential.username jenkins # timeout=10
>> > git config --local credential.helper store
>> --file=/tmp/git4715501803936103145.credentials # timeout=10
>> > git -c core.askpass=true fetch --tags --progress
>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
>> +refs/heads/*:refs/remotes/origin/*
>> > git config --local --remove-section credential # timeout=10
>> > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
>> > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
>> Checking out Revision 4e21d6895f1505810a35774f7ee6e339658c8252
>> (refs/remotes/origin/master)
>> > git config core.sparsecheckout # timeout=10
>> > git checkout -f 4e21d6895f1505810a35774f7ee6e339658c8252
>> > git rev-list 4e21d6895f1505810a35774f7ee6e339658c8252 # timeout=10
>> [Pipeline] node
>> Running on master in /home/jenkins/.jenkins/workspace/wildfly
>> [Pipeline] {
>> [Pipeline] stage (checkout)
>> Entering stage checkout
>> Proceeding
>> [Pipeline] checkout
>> Cloning the remote Git repository
>> Cloning repository
>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
>> > git init /home/jenkins/.jenkins/workspace/wildfly # timeout=10
>> Fetching upstream changes from
>> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
>> > git --version # timeout=10
>> using .gitcredentials to set credentials
>> > git config --local credential.username jenkins # timeout=10
>> > git config --local credential.helper store
>> --file=/tmp/git5568879933463267023.credentials # timeout=10
>> > git -c core
Re: Issue getting Docker Pipeline plugin to build an image
Try not to feel stupid ;)
The @ directories I believe due to locking - when a direcotry is locked and
a step or a build wants to run in there, it appends a number, but I don't
think that is your problem.
Docker pipeline bind mounts in the workspace, so perhaps how your daemon is
running vs the slave don't line up - this can be the case on OSX/windows
(pre the "new" docker beta which uses more native virtialisation on osx).
Can get the docker image to build if you run "sh 'docker build -t
openshift/wildfly:10
.' ?
On Wednesday, June 8, 2016 at 3:23:43 PM UTC+10, Lyle Dietz wrote:
>
> I'm having issues trying to build a Docker image with the Docker Pipeline
> plugin.
>
> I've tried searching, but no-one seems to be having the issue, and all the
> documentation I see suggests I'm not doing anything stupid.
>
> My current Jenkins file is as follows (I've pared it back for
> simplicity/debugging):
>
>
> #!groovy
>
> node {
> stage 'checkout'
> checkout scm
>
> stage 'build'
> def image = docker.build('openshift/wildfly:10')
> }
>
>
> The output from the job is:
>
> Started by user Lyle Dietz
> Cloning the remote Git repository
> Cloning repository
> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
> > git init /home/jenkins/.jenkins/workspace/wildfly@script # timeout=10
> Fetching upstream changes from
> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
> > git --version # timeout=10
> using .gitcredentials to set credentials
> > git config --local credential.username jenkins # timeout=10
> > git config --local credential.helper store
> --file=/tmp/git2241825672262408901.credentials # timeout=10
> > git -c core.askpass=true fetch --tags --progress
> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
> +refs/heads/*:refs/remotes/origin/*
> > git config --local --remove-section credential # timeout=10
> > git config remote.origin.url
> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git #
> timeout=10
> > git config --add remote.origin.fetch
> +refs/heads/*:refs/remotes/origin/* # timeout=10
> > git config remote.origin.url
> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git #
> timeout=10
> Fetching upstream changes from
> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
> using .gitcredentials to set credentials
> > git config --local credential.username jenkins # timeout=10
> > git config --local credential.helper store
> --file=/tmp/git4715501803936103145.credentials # timeout=10
> > git -c core.askpass=true fetch --tags --progress
> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
> +refs/heads/*:refs/remotes/origin/*
> > git config --local --remove-section credential # timeout=10
> > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
> Checking out Revision 4e21d6895f1505810a35774f7ee6e339658c8252
> (refs/remotes/origin/master)
> > git config core.sparsecheckout # timeout=10
> > git checkout -f 4e21d6895f1505810a35774f7ee6e339658c8252
> > git rev-list 4e21d6895f1505810a35774f7ee6e339658c8252 # timeout=10
> [Pipeline] node
> Running on master in /home/jenkins/.jenkins/workspace/wildfly
> [Pipeline] {
> [Pipeline] stage (checkout)
> Entering stage checkout
> Proceeding
> [Pipeline] checkout
> Cloning the remote Git repository
> Cloning repository
> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
> > git init /home/jenkins/.jenkins/workspace/wildfly # timeout=10
> Fetching upstream changes from
> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
> > git --version # timeout=10
> using .gitcredentials to set credentials
> > git config --local credential.username jenkins # timeout=10
> > git config --local credential.helper store
> --file=/tmp/git5568879933463267023.credentials # timeout=10
> > git -c core.askpass=true fetch --tags --progress
> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
> +refs/heads/*:refs/remotes/origin/*
> > git config --local --remove-section credential # timeout=10
> > git config remote.origin.url
> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git #
> timeout=10
> > git config --add remote.origin.fetch
> +refs/heads/*:refs/remotes/origin/* # timeout=10
> > git config remote.origin.url
> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git #
> timeout=10
> Fetching upstream changes from
> http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
> using .gitcredent
Issue getting Docker Pipeline plugin to build an image
I'm having issues trying to build a Docker image with the Docker Pipeline
plugin.
I've tried searching, but no-one seems to be having the issue, and all the
documentation I see suggests I'm not doing anything stupid.
My current Jenkins file is as follows (I've pared it back for
simplicity/debugging):
#!groovy
node {
stage 'checkout'
checkout scm
stage 'build'
def image = docker.build('openshift/wildfly:10')
}
The output from the job is:
Started by user Lyle Dietz
Cloning the remote Git repository
Cloning repository
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
> git init /home/jenkins/.jenkins/workspace/wildfly@script # timeout=10
Fetching upstream changes from
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
> git --version # timeout=10
using .gitcredentials to set credentials
> git config --local credential.username jenkins # timeout=10
> git config --local credential.helper store
--file=/tmp/git2241825672262408901.credentials # timeout=10
> git -c core.askpass=true fetch --tags --progress
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
+refs/heads/*:refs/remotes/origin/*
> git config --local --remove-section credential # timeout=10
> git config remote.origin.url
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/*
# timeout=10
> git config remote.origin.url
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git # timeout=10
Fetching upstream changes from
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
using .gitcredentials to set credentials
> git config --local credential.username jenkins # timeout=10
> git config --local credential.helper store
--file=/tmp/git4715501803936103145.credentials # timeout=10
> git -c core.askpass=true fetch --tags --progress
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
+refs/heads/*:refs/remotes/origin/*
> git config --local --remove-section credential # timeout=10
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 4e21d6895f1505810a35774f7ee6e339658c8252
(refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 4e21d6895f1505810a35774f7ee6e339658c8252
> git rev-list 4e21d6895f1505810a35774f7ee6e339658c8252 # timeout=10
[Pipeline] node
Running on master in /home/jenkins/.jenkins/workspace/wildfly
[Pipeline] {
[Pipeline] stage (checkout)
Entering stage checkout
Proceeding
[Pipeline] checkout
Cloning the remote Git repository
Cloning repository
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
> git init /home/jenkins/.jenkins/workspace/wildfly # timeout=10
Fetching upstream changes from
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
> git --version # timeout=10
using .gitcredentials to set credentials
> git config --local credential.username jenkins # timeout=10
> git config --local credential.helper store
--file=/tmp/git5568879933463267023.credentials # timeout=10
> git -c core.askpass=true fetch --tags --progress
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
+refs/heads/*:refs/remotes/origin/*
> git config --local --remove-section credential # timeout=10
> git config remote.origin.url
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/*
# timeout=10
> git config remote.origin.url
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git # timeout=10
Fetching upstream changes from
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
using .gitcredentials to set credentials
> git config --local credential.username jenkins # timeout=10
> git config --local credential.helper store
--file=/tmp/git695409405329882652.credentials # timeout=10
> git -c core.askpass=true fetch --tags --progress
http://gitblit.myorg.local/r/experiments/openshift/wildfly.git
+refs/heads/*:refs/remotes/origin/*
> git config --local --remove-section credential # timeout=10
> git rev-parse refs/remotes/origin/master^{commit} # timeout=10
> git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 4e21d6895f1505810a35774f7ee6e339658c8252
(refs/remotes/origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 4e21d6895f1505810a35774f7ee6e339658c8252
[Pipeline] stage (build)
Entering stage build
Proceeding
[Pipeline] node
Running on master in /home/jenkins/.jenkins/workspace/wildfly@2
[Pipeline] {
[Pipeline] sh
[wildfly@2] Running shell script
+ docker build -t openshift/wildfly:10 .
time="2016-06-08T14:53:04+10:00" level=fatal msg="Cannot locate Dockerfile
