Past attempts to fix JENKINS-30600 without breaking compatibility for
existing users have failed. I'm not very hopeful that we'll be able to fix
JENKINS-30600.
I like Jesse Glick's recommendation for the preferred solution. He
recommends that we allow the pipeline user to have much greater contr
Is there chance, that JENKINS-30600 will ever be fixed? It dates back to
2015, so presumably not?
Until then thanks for
https://issues.jenkins.io/browse/JENKINS-30600?focusedCommentId=383360&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-383360
This was helpful.
--
Yes, you're understanding the message correctly. That is an instance of
JENKINS-30600.
On Thu, Jul 2, 2020 at 2:51 AM Martin Schmude
wrote:
> Hi all,
> I need help with an issue related to the git step in a pipeline job, that
> is executed in a Docker container.
> The pipeline looks like this:
I forgot the versions.
Jenkins: 2.220
git plugin: 4.1.1
Pipeline plugin: 2.6
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googleg
Hi all,
I need help with an issue related to the git step in a pipeline job, that
is executed in a Docker container.
The pipeline looks like this:
node('Docker-capable-node') {
docker.inside('image-with-git-installed').inside {
git credentialsId: 'my-credentials', url:
'https://gitlab.myco
