Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] JIPP docker: command not found
Hi Jakub,

All JIPPs have access to the /shared/common folder where we install common build tools. You can see the content of this folder online at the address http://build.eclipse.org/common/

As you can see, we already provide a couple of versions of Node. If you need a specific version of Node or any other tool that you can't find, feel free to just open a bug here https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=CI-Jenkins.

Regarding Docker, we plan to provide support hopefully by the end of the year. As you may know, providing such a support in an open and secure way is not the easiest task, so please bear with us ;)

Cheers,

--
Mikaël Barbero - Eclipse Foundation
IT Services - Release Engineering
📱 (+33) 642 028 039
🐦 @mikbarbero

Le 12 avr. 2018 à 21:05, Jakub Siberski <jakub.siberski@xxxxxxxxx> a écrit :

Hi Mikaël.

Well, the job I have linked was just an experiment to see what is provided by CBI.

What we (N4JS) actually need is:
 - maven 3+
 - Ant
 - JDK 8
 - Xvfb
 - Node.js 8 (LTS)

Managing all those and other build node configurations is annoying. That is why the project uses docker
to manage build infrastructure. Actually, in the Jenkinsfile we configure agent by building docker image on
the fly and then it is used as environment in which actual build is running.

Are you saying that CBI is not providing docker, and there are not plans to provided that?

If so, what about other tools I have mentioned? I have seen that maven, Ant and JDK are provided,
but what about the rest? 

Node.js is mandatory for us. We are interfacing with it a lot. In some cases external processes
are started which need to locate and trigger Node.js on their own.
Can we request Node.js installation?


Cheers,
Jakub


On Thu, Apr 12, 2018 at 9:17 AM, Mikaël Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Jakub,

Unfortunately, we currently don't provide Docker on JIPP. I see that you're using "maven:3-alpine", so I guess it will be good enough to use a maven step. If the maven pipeline plugin is not install on n4js, please open a bug on Community > CI-Jenkins (https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=CI-Jenkins) and we will do that for you.

Cheers,

--
Mikaël Barbero - Eclipse Foundation
IT Services - Release Engineering
📱 (+33) 642 028 039
🐦 @mikbarbero

Le 11 avr. 2018 à 10:27, Jakub Siberski <jakub.siberski@xxxxxxxxx> a écrit :

Hi.

I am setting up build jobs for N4JS project using our JIPP: https://ci.eclipse.org/n4js/

We want to use Jenkins Pipeline + Docker, but it seems that docker is not available?

I have small job https://ci.eclipse.org/n4js/job/wip/ with Jenkinsfile (inlined in config):
pipeline {
    agent {
        docker {
            image 'maven:3-alpine'
            args '-v $HOME/.m2:/root/.m2'
        }
    }
    stages {
        stage('Preparation') {
            steps {
                git 'https://github.com/jglick/simple-maven-project-with-tests.git'
            }
        }
        stage('Build') {
             steps {
                    sh "mvn -Dmaven.test.failure.ignore clean package"
             }
        }
        stage('Results') {
             steps {
                junit '**/target/surefire-reports/TEST-*.xml'
                archive 'target/*.jar'
            }
        }
    }
}

running this on JIPP fails :
https://ci.eclipse.org/n4js/job/wip/9/console
Started by user jakub.siberski@xxxxxxxxx
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on Jenkins in /home/hudson/genie.n4js/.jenkins/jobs/wip/workspace
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Agent Setup)
[Pipeline] sh
[workspace] Running shell script
+ docker pull maven:3-alpine
/home/hudson/genie.n4js/.jenkins/jobs/wip/workspace@tmp/durable-40a6d622/script.sh: line 2: docker: command not found
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 127
Finished: FAILURE


I had impression that docker is available as part of the pipeline workflow
as https://wiki.eclipse.org/Jenkins mentions:
  • docker-commons
  • docker-workflow


So, in short:
Does docker needs to be requested as extra tool,
or am I approaching this the wrong way?


Best,
Jakub


--
Jakub
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev


_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev



--
Jakub
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cbi-dev

Attachment: signature.asc
Description: Message signed with OpenPGP

Back to the top