i am trying to run liquibase runner using jenkins, when i run it in jenkins master it works great using automatic install, but when i try to run it in a jenkisn agent it shows this error:
Liquibase home: /home/jenkins/agent/tools/org.jenkinsci.plugins.liquibase.install.LiquibaseInstallation/Liquibase
FATAL: Liquibase installation /home/jenkins/agent/tools/org.jenkinsci.plugins.liquibase.install.LiquibaseInstallation/Liquibase is not a valid Liquibase install
Build step 'Liquibase: Update Database' changed build result to NOT_BUILT ```
this is my configuration in the Global Tools Configurations:
[enter image description here][1]
this is my configuration in the freestyle job:
[enter image description here][2]
[1]: https://i.stack.imgur.com/3nt9n.png
[2]: https://i.stack.imgur.com/sSoYc.png
Related
step1:I deploymented jenkins、rancher、gitlab servers in my local environment.I would want to realize CI/CD pipeline.
step2:My project is a web-based management system which used vue and gin.The project source code was pushed into the gitlab repository.I wrote a Dockerfile and a Jenkinsfile in my local IDE.The next is my important description.In my Jenkinsfile:there is some statement like the following shows :
steps {
sh "kubectl set image deployment/gin-vue gin-vue=myhost/containers/gin-vue.${BUILD_NUMBER} -n web"
}
Then executed git commit and git push command.
step3:I created a task in jenkins and clicked the build button to run the corresponding pipeline script.
step4:After end running,the newer image could not be updated into the rancher.
enter image description here
But I executed this command in rancher kubectl client terminal "kubectl set image deployment/gin-vue gin-vue=myhost/containers/gin-vue.${BUILD_NUMBER} -n web" could be successful.
So what's the cause of this problem?And this confused me so many days and not found the solution.Thanks a lot!
I executed this command in rancher kubectl client terminal "kubectl set image deployment/gin-vue gin-vue=myhost/containers/gin-vue.${BUILD_NUMBER} -n web" could be successful.
I created the GitHub Actions self-hosted runner in the Kubernetes cluster with the Maven base image.
But when I am running "mvn clean package" command I am getting "mvn not found error".
Even though I tried giving full maven path still i am getting the same error.
- name: Build with Maven
run: mvn clean package
Maven base image
FROM maven:3.6.0-jdk-11-slim
The error I am getting when I run GitHub Actions.
/runner/_work/_temp/6c9b0c85-4be9-4af0-b168-6dd5bdb998db.sh: line 1: mvn: command not found```
I'm trying to run my build inside a container with azure-pipelines in Azure DevOps Server(onprem). Following the official guide https://learn.microsoft.com/en-us/azure/devops/pipelines/process/container-phases?view=azure-devops-2019
I do have a self-hosted linux agent with ubuntu18.04 installed.
My azure-pipelines.yml
pool: linux-container-build
container: ubuntu:16.04
steps:
- script: whoami
The container initialization works fine and creates the container properly. Afterwards the checkout steps fails without much information.
Picture of pipeline: pipeline
Checkout step just does this:
##[section]Starting: Checkout ***** to s
==============================================================================
Task : Get sources
Description : Get sources from a repository. Supports Git, TfsVC, and SVN repositories.
Version : 1.0.0
Author : Microsoft
Help : [More Information](https://go.microsoft.com/fwlink/?LinkId=798199)
==============================================================================
##[error]Collection was modified; enumeration operation may not execute.
##[section]Finishing: Checkout **** to s
I updated my task definition to:
- checkout: none
This will skip the checkout step and the 'whoami' step succeeds with proper output inside the container
It seems I need git inside my container? ..also probably all other packages..
Can I somehow add git and all required applications to the _work folder or to externels because this will get mounted in the docker volume?
I am getting the Build: SUCCESS message on jenkins Console output, but not the detailed result like Iterations, executed vs failed etc.
i am using "newman run https://www.getpostman.com/collections/559ca99c65470714895de" as 'Execute Windows Batch Command'.
am i missing any plug-ins? please help?
The collection link you have provided is not valid.
Please make sure you have the following configurations before you run newman:
npm and node installed globally on jenkins.
If not refer to Node Installation
newman installed globally on the jenkins.
If not $ npm install -g newman
please execute the command on shell (not on Windows Batch Command)
Mention the cli reporter and exitCode to let jenkins know incase of any falure in the command as $ newman run <your collection goes here> -r cli --exitCode 1
Recommended: Create a node app and run your tests for advanced reporting and easy maintenance. Ex: Sample Newman Node Application with Custom Reporters
I'm trying to set up an sbt build on a CloudBees-hosted Jenkins server. The repository is stored in GitHub, and Jenkins is pulling the repository fine as I can see all the code in the workspace.
However, when I try to run the build I get the following output:
...
Seen branch in repository origin/master
Seen 2 remote branches
Commencing build of Revision 763eecd49a522a50e53c6f24e40e5f2e984d3737 (origin/HEAD, origin/master)
Checking out Revision 763eecd49a522a50e53c6f24e40e5f2e984d3737 (origin/HEAD, origin/master)
Warning : There are multiple branch changesets here
[ProjectName] $ java -Dsbt.log.noformat=true -jar /opt/sbt/sbt-launch-0.7.4.jar clean test
Name: No value provided for Name
Build step 'Build using sbt' changed build result to FAILURE
Build step 'Build using sbt' marked build as failure
Finished: FAILURE
The build runs fine on two other machines, even when run using an equivalent command line to the one Jenkins is using. The project itself is a multi-project build with Play Framework.
THis is probably due to having the incorrect version of the sbt-launch jar in your global config's sbt section. If you update it to say /opt/sbt/sbt-launch-0.13.0.jar that should resolve your problem