Re: Archiving jenkinsci/groovy repo

Thanks! Looks like it was a custom fork for https://github.com/jenkinsci/groovy/commit/73ad9b61697e453fb334f0fe6eb3a9c3d66ce2ab which was integrated into upstream in 2011 https://issues.apache.org/jira/browse/GROOVY-5017 No need to keep it indeed BR, Oleg On Tuesday, January 7, 2020 at

Re: Sending file content explicitly to a remote agent

Ok, FilePath.act. Got it. On Monday, 6 January 2020 19:01:36 UTC-5, Randall Becker wrote: > > Hi all, > > I am trying to modify a custom Jenkins Plugin to automatically upload a > shell script and then execute it to facilitate job execution. Using a > separate plugin is not a viable option for

Re: Archiving jenkinsci/groovy repo

The repo is archived now. It can always be unarchived if the need arises. On 07/01/2020 11.33, Raihaan Shouhell wrote: +1 should have been archived a long time ago. Cheers, Raihaan On Tue, Jan 7, 2020 at 4:17 PM Oliver Gondža > wrote: Thanks to a github

Re: Archiving jenkinsci/groovy repo

+1 should have been archived a long time ago. Cheers, Raihaan On Tue, Jan 7, 2020 at 4:17 PM Oliver Gondža wrote: > Thanks to a github security alert, I find out we have a fork of an > official groovy repo[1] in our org. It is terribly outdated and unused > for over 8 years[2]. > > Are there

Archiving jenkinsci/groovy repo

Thanks to a github security alert, I find out we have a fork of an official groovy repo[1] in our org. It is terribly outdated and unused for over 8 years[2]. Are there any objections to archiving such repositories? The repo will remain readable but it would clearly indicate it is obsolete