| Mark Waite I was able to spin up a jenkins locally and reproduce this issue with the artifactory plugin, I'll update a somewhat redacted config.xml and try to remember all of the steps I went through. 1. I started from dockerized jenkins
docker run -it \
-p 8080:8080 \
-v "$PWD/home":/var/jenkins_home \
jenkins/jenkins:latest
2. Setup (uninstalled most plugins that weren't necessary)
3. Install the artifactory plugin
4. Add credentials for:
i. Private key for SSH agent
ii. API key for our GitHub Enterprise
iii. API key for our artifactory instance
5. In Manage Jenkins -> Configure System, add an artifactory instance with our artifactory hostname and the credential from (4,iii)
6. In Manage Jenkins -> Global Tool Configuration, add a maven installation
7. Create a node for the SSH agent and connect to it
8. Create a Maven job
i. Restrict it to run on the agent I created
ii. Add git configuration for a repo with a test maven project that I have permission to push version changes to and set the credentials to (4,ii)
iii. Set the maven targets to "-U clean package"
iv. Check and configure "Enable Artifactory release management"
v. (Probably Optional) Check and configure "Resolve artifacts from Artifactory"
vi. (Maybe Optional) Add a Post-build Action for "Deploy artifacts to Artifactory"
9. Click "Build Now", it should build without errors
10. Click "Artifactory Release Staging", fill out form, and run release build. It fails with the above exceptions after building with maven and when attempting to push version updates to git. In the uploaded config, anything in curly braces "{}" has been redacted: config.xml |
