I am building Jenkins Maven project. In the Jenkinsfile if I use mvn clean pom.xml and mvn install pom.xml in separate lines, the build is successful. However , mvn clean install pom.xml fails.
What is the reason for this?
Related
I am new on protractor platform and I tried to install and run the protractor locally on window, but I had no luck yet. Can anybody please tell me the exact step? I am able to install and run it globally.
For you
Create an empty folder as project base dir
Open a terminal and cd into the new folder
Execute npm init to generate package.json
Execute npm install -S protractor to install protractor locally and add it into project's dependencies. (you can check protractor will appear in package.json)
Prepare test script
Commit test script with package.json together
For others who want to run you code locally,
Clone your code to local
Open terminal and cd project base dir
Execute npm install to install dependencies to local
Execute protractor cli to execute test
We have gradle and npm installed on Linux box inside jenkins container where I am able to build through gulp build command but when I run
"gradle build"
Execution failed for task ':themes:portlet-layout:-portal-layouttpl:npmInstall'.
A problem occurred starting process 'command '/var/jenkins/workspace/Portal_RTC/liferay-workspace/build/node/node..
,I have got gradle npm installed and PATH set.I can say this running by npm --v , node --version.
I want to know what configuration I am missing to make it work.Also everytime I checked out the code I need to install modules again specially gulp else it start download from webhttp://mirrors.lax.liferay.com/nodejs.org/dist/v8.10.0/node-v8.10.0-linux-x64.tar.gz
when I define gradle-gulp plugin in build.gradle it says node is already installed. The imp things is the whole setup work on Developer machine on windows. Though they have copied node_modules folder from nodeJs home to their individual projects.
thanks
The documentation doesn't mention this specifity:
yarn install is used to install all dependencies for a project. This
is most commonly used when you have just checked out code for a
project, or when another developer on the project has added a new
dependency that you need to pick up.
Yarn install : Install all the dependencies listed within package.json in the local node_modules folder.
I have this script
echo builing deployme for branch $SourceBranch
rm -Rf project1
rm -Rf project2
git clone ssh://git#gitlab.yyy.com:2222/xxx/project1.git
cd project1
mvn --settings .m2/settings.xml clean package
cd ..
git clone ssh://git#gitlab.yyy.com:2222/xxx/project2.git
cd project2
mvn --settings .m2/settings.xml clean package
which is working in Jenkins.
Is there an easy/fast way to execute this in GitLab CI for some testing the process? Thx!
I am trying to build zeppelin locally with windows and babun/cygwin. This site got me headed in the right direction, but I run into the following error when the build gets to Web Application:
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:0.0.23:bower (bower install) on project zeppelin-web: Failed to run task: 'bower --allow-root install' failed. (error code 8) -> [Help 1]
I can go into the zeppelin-web directory and run bower install successfully, but I'm not sure where to go from here? If I try to do mvn install -DskipTests, it tries to run the bower command again.
If I try to "move on" and attempt to build under ../zeppelin-server it will say that it can't find the zeppelin-web dependency.
I think I would like to run bower install manually, as suggested by the site above, but I'm not sure where to go from there? Is it possible to pick up mvn where it left off? Any help or guidance would be greatly appreciated.
I ran into the same problem. First try to go to the zeppeling-web component and run there mvn package -DskipTests. It should give you more details about what is failing:
cd zeppelin-web
mvn package -DskipTests
In my case it was a problem with git proxies, since I am working in a corporate environment. At the console, issuing the command:
git config --global url."https://".insteadOf git://
did the trick.
You have to run the build command with sudo
This worked for me: run the following as a non-root user, (replace <goals> with your -P and -D flags, or remove for standalone install):
sudo env "PATH=$PATH" mvn clean install <goals> -DskipTests
sudo env "PATH=$PATH" mvn clean install <goals> -DskipTests -rf :zeppelin-web