[JIRA] [git-plugin] (JENKINS-34223) Add configuration field to set additional config options

2 views
Skip to first unread message

heiko.thiery@googlemail.com (JIRA)

unread,
Apr 14, 2016, 3:01:03 AM4/14/16
to jenkinsc...@googlegroups.com
Heiko Thiery created an issue
 
Jenkins / Improvement JENKINS-34223
Add configuration field to set additional config options
Issue Type: Improvement Improvement
Assignee: Mark Waite
Components: git-plugin
Created: 2016/Apr/14 7:00 AM
Priority: Minor Minor
Reporter: Heiko Thiery

In our environment we have to clone from a server via https. This server has self-signed certificate that makes it necessary to set the global git sslVerify config option to false.

It would be nice if we can set this option per job in the git plugin that adds the option to the clone command: "-c sslVerify=false".

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

mark.earl.waite@gmail.com (JIRA)

unread,
Apr 14, 2016, 3:29:02 PM4/14/16
to jenkinsc...@googlegroups.com
Mark Waite assigned an issue to Unassigned
Change By: Mark Waite
Assignee: Mark Waite

daniel.black@au.ibm.com (JIRA)

unread,
Oct 19, 2016, 7:27:01 PM10/19/16
to jenkinsc...@googlegroups.com
Daniel Black commented on Improvement JENKINS-34223
 
Re: Add configuration field to set additional config options

I'd like to set submodule.common.url

I have git mirror of a github repo that is being built in numerous ways. This upstream git repo has a large submodule which I've also mirrored. I don't want to pollute the mirror by changing its submodule configuration.

This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

lionel.cabasson@laposte.net (JIRA)

unread,
May 14, 2018, 8:03:02 AM5/14/18
to jenkinsc...@googlegroups.com

Hello,

I am facing a similar problem. We're using a Windows slave and our repository contains files with long path so we have to use "core.longpaths=true" to be able to clone the repo.

I don't see any way to do this with the current plugin implementation.

The possibility to add custom additional configuration options would allow us to deal with that and other scenario that cannot be dealt with the plugin existing options. I would raise the priority of this issue.

Regards

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

heiko.thiery@googlemail.com (JIRA)

unread,
Feb 26, 2020, 9:03:05 AM2/26/20
to jenkinsc...@googlegroups.com

Is there any conclusion on that? how can I per job basis change the git behavior?

Has anyone a glue on setting sslVerify option?

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages