Jenkins

问题 I'm trying to set up a jenkins multibranch pipeline to run all my code validation steps in a docker container, then build the docker image and push it outside of said docker container. Currently, my Jenkinsfile looks sort of like this (slimmed down for readability): pipeline { agent { label 'AWS' } stages { stage('stuff in docker') { agent { dockerfile { filename 'Dockerfile.jenkins' reuseNode true } } steps { stuff } } stage('more stuff in docker') { agent { dockerfile { filename 'Dockerfile

问题 I'm trying to set up a jenkins multibranch pipeline to run all my code validation steps in a docker container, then build the docker image and push it outside of said docker container. Currently, my Jenkinsfile looks sort of like this (slimmed down for readability): pipeline { agent { label 'AWS' } stages { stage('stuff in docker') { agent { dockerfile { filename 'Dockerfile.jenkins' reuseNode true } } steps { stuff } } stage('more stuff in docker') { agent { dockerfile { filename 'Dockerfile

问题 I'm trying to set up a jenkins multibranch pipeline to run all my code validation steps in a docker container, then build the docker image and push it outside of said docker container. Currently, my Jenkinsfile looks sort of like this (slimmed down for readability): pipeline { agent { label 'AWS' } stages { stage('stuff in docker') { agent { dockerfile { filename 'Dockerfile.jenkins' reuseNode true } } steps { stuff } } stage('more stuff in docker') { agent { dockerfile { filename 'Dockerfile

问题 I have 2 jobs (A and B). Job A points to a git repo at URL-A. Job B points to a different git repo, at URL-B. Once job A finishes and is stable, it should trigger job B and pass the git commit hash that was used in job A's build. What is the simplest way to achieve that? (Job B corresponds to a script checked out from URL-B that has 2 parameters: a git commit hash and a JAR artifact that will be wrapped in a Docker image and pushed to Docker hub) 回答1: In Job B, check This project is

问题 I have 2 jobs (A and B). Job A points to a git repo at URL-A. Job B points to a different git repo, at URL-B. Once job A finishes and is stable, it should trigger job B and pass the git commit hash that was used in job A's build. What is the simplest way to achieve that? (Job B corresponds to a script checked out from URL-B that has 2 parameters: a git commit hash and a JAR artifact that will be wrapped in a Docker image and pushed to Docker hub) 回答1: In Job B, check This project is

问题 I've been working on this project for about a week now and I've been searching for 2 days without any clear explanation online. For a school assignment, we need to set up a buildserver with the following programs: Maven, as our build tool. Mercurial as our versioning system. Java (JRE), javac and javadoc. JUnit for unit testing. Jenkins (with JDepend plugin). We need to create 3 jobs, and 1 of those jobs is: Every time the (local) repository of Mercurial gets edited, a build needs to start.

问题 I've been working on this project for about a week now and I've been searching for 2 days without any clear explanation online. For a school assignment, we need to set up a buildserver with the following programs: Maven, as our build tool. Mercurial as our versioning system. Java (JRE), javac and javadoc. JUnit for unit testing. Jenkins (with JDepend plugin). We need to create 3 jobs, and 1 of those jobs is: Every time the (local) repository of Mercurial gets edited, a build needs to start.

问题 I've been working on this project for about a week now and I've been searching for 2 days without any clear explanation online. For a school assignment, we need to set up a buildserver with the following programs: Maven, as our build tool. Mercurial as our versioning system. Java (JRE), javac and javadoc. JUnit for unit testing. Jenkins (with JDepend plugin). We need to create 3 jobs, and 1 of those jobs is: Every time the (local) repository of Mercurial gets edited, a build needs to start.

问题 I am tring to build and publish my job with the help of CloudBees Docker Build and Publish plugin. I added my credentials to Jenkins. When I build the job, it stucks at pushing into Docker by saying authentication error. I checked from cmd that I can login to docker and I could created the image but cannot do it with Jenkins. Do you have any idea about how to solve this problem? Error log is in the following: [jenkins-docker] $ docker tag c89e01bffe59 reponame/imagename:latest [jenkins-docker

问题 I am trying to connect a mac to a raspberry running Jenkins, to start docker build slaves on the mac on demand. But I can't establish the connection in Jenkins' docker cloud configuration. My setup is as follows: raspberry pi at 192.168.2.111: Jenkins running in docker mac mini at 192.168.2.220 using docker for mac: this should run docker containers as build slaves on demand via Jenkins docker plugin The SSH connection from Jenkins to mac works. The mac agent is up and running. Now I want to