[JIRA] (JENKINS-50822) docker.build should support URL parameter for docker build
Title: Message Title Christian Beushausen created an issue Jenkins / JENKINS-50822 docker.build should support URL parameter for docker build Issue Type: Improvement Assignee: Unassigned Components: docker-workflow-plugin Created: 2018-04-16 11:12 Priority: Minor Reporter: Christian Beushausen I want to be able to use/specify a Git repository containing the relevant Dockerfile when writing the Pipeline script and not having to integrate identical Dockerfiles in every repository that we are handling in this way. https://docs.docker.com/engine/reference/commandline/build/ Add Comment
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Christian Beushausen edited a comment on JENKINS-42959 Re: Failed known_hosts verification for SSH agent I see the same issue now on one of our Jenkins 2.32.3 installations, slave was connected fine but I had to reconnect it for reasons and since then I get this same error message.Following [~pvohmann]'s advice I added the RSA key to my known_hosts file, but was not able to solve the issue. Error still persists. Update: Nevermind. I did not read carefully and only executed this on the slave and not on the master ... after properly updating the known_hosts file on the Jenkins master connection can be established again. Sorry for any confusion. Would also propose to update the documentation to make it easier understandable. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42959) Failed known_hosts verification for SSH agent
Title: Message Title Christian Beushausen commented on JENKINS-42959 Re: Failed known_hosts verification for SSH agent I see the same issue now on one of our Jenkins 2.32.3 installations, slave was connected fine but I had to reconnect it for reasons and since then I get this same error message. Following Peter Vohmann's advice I added the RSA key to my known_hosts file, but was not able to solve the issue. Error still persists. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38005) Using archiveArtifacts with a non-matching pattern silently fails the build
Title: Message Title
Christian Beushausen commented on JENKINS-38005
Re: Using archiveArtifacts with a non-matching pattern silently fails the build
I would like to add that it looks to me that archiveArtifacts also (silently) fails when using absolute paths:
def myfile1 = "foobar"
sh "echo foobar > ${myfile1}"
archiveArtifacts artifacts: "${myfile1}", fingerprint: true
works correctly,
def myfile1 = "${WORKSPACE}/foobar"
sh "echo foobar > ${myfile1}"
archiveArtifacts artifacts: "${myfile1}", fingerprint: true
on the other hand does not.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
