[JIRA] (JENKINS-61127) More freely defined advanced clone behaviours
Title: Message Title Tor Christian Solevågseide created an issue Jenkins / JENKINS-61127 More freely defined advanced clone behaviours Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2020-02-18 13:38 Priority: Major Reporter: Tor Christian Solevågseide There is a need for a "More advanced clone behaviors" The current "Advanced clone behaviours" takes us just part of the way when needing to configure the clone operation. There are a lot of options on git clone that is not possible to set. Ref https://git-scm.com/docs/git-clone Example: We currently have the need to do a shallow clone, but need to include all branches. Meaning that we want to add the --no-single-branch option. We cannot see any other way of achieving this right now. I assume this request will solve JENKINS-61109 and similar issues as well. Add Comment
[JIRA] (JENKINS-41359) Global methods in pipeline shared-library fails when invoked
Title: Message Title
Tor Christian Solevågseide resolved as Not A Defect
Not a bug Solved by correcting my library import as described in doc @ https://jenkins.io/doc/book/pipeline/shared-libraries/ :
For Shared Libraries which only define Global Variables (vars/), or a Jenkinsfile which only needs a Global Variable, the annotation pattern @Library('my-shared-library') _ may be useful for keeping code concise. In essence, instead of annotating an unnecessary import statement, the symbol _ is annotated.
It is not recommended to import a global variable/function, since this will force the compiler to interpret fields and methods as static even if they were intended to be instance. The Groovy compiler in this case can produce confusing error messages.
Jenkins / JENKINS-41359
Global methods in pipeline shared-library fails when invoked
Change By:
Tor Christian Solevågseide
Status:
Open Resolved
Resolution:
Not A Defect
Add Comment
[JIRA] (JENKINS-41359) Global methods in pipeline shared-library fails when invoked
Title: Message Title Tor Christian Solevågseide updated an issue Jenkins / JENKINS-41359 Global methods in pipeline shared-library fails when invoked Change By: Tor Christian Solevågseide Labels: pipeline 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.
[JIRA] (JENKINS-41359) Global methods in pipeline shared-library fails when invoked
Title: Message Title
Tor Christian Solevågseide created an issue
Jenkins / JENKINS-41359
Global methods in pipeline shared-library fails when invoked
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2017/Jan/24 7:51 AM
Environment:
Jenkins version 2.41 Pipeline plugin 2.4
Priority:
Minor
Reporter:
Tor Christian Solevågseide
As documented in https://jenkins.io/doc/book/pipeline/shared-libraries/, I've created the file vars/acme.groovy in a library project checked into our SVN.
def setName(value) {
this.name = value;
}
def getName() {
return this.name;
}
def caution(message) {
echo "Hello, ${this.name}! CAUTION: ${message}"
}
My pipeline script in a Jenkins2 pipeline project:
acme.name = 'Alice'
echo acme.name
acme.caution 'The queen is angry!'
The two first lines, setting and getting the name works fine. But when I include the last line, calling the "caution" function, the script fails with
hudson.remoting.ProxyException:
