[JIRA] (JENKINS-40695) Allow lightweight or remote checkout for Groovy libraries

1 view
Skip to first unread message

jglick@cloudbees.com (JIRA)

unread,
Jun 5, 2018, 6:39:01 PM6/5/18
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
 
Jenkins / New Feature JENKINS-40695
Allow lightweight or remote checkout for Groovy libraries

The issue title is misleading. Yes you can use the load step.

The standard library retrievers could probably be made to use lightweight checkouts with supported SCMs like GitHub, thus avoiding the need to maintain a local copy anywhere. Not sure if retrieval of source files could be made lazy, though.

Making the library step use a contextual node might work, with some API changes, though it would introduce security issues if not done carefully—could not be offered for trusted libraries. Also would not work for @Library which must be done prior to script parsing.

Change By: Jesse Glick
Summary: Allow running Pipeline shared library functions on executor lightweight or remote checkout for Groovy libraries
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

ordiel1910@gmail.com (JIRA)

unread,
Jun 10, 2019, 3:35:04 PM6/10/19
to jenkinsc...@googlegroups.com
Cesar Martinez commented on New Feature JENKINS-40695
 
Re: Allow lightweight or remote checkout for Groovy libraries

Similar use case here; I am trying to identify the files changed on my last (git scm) changeset, and perform some greps on them, but they are on a different node.

Would it be possible to get an ETA for this? (in case it will be implemented) 

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages