[JIRA] (JENKINS-50284) PlasticSCM - cannot use Plastic repository as Shared Library source

[mikael@kalms.org (JIRA)]

Mikael Kalms created an issue

Jenkins / JENKINS-50284 PlasticSCM - cannot use Plastic repository as Shared Library source Issue Type: Bug Assignee: Unassigned Components: plasticscm-plugin Created: 2018-03-20 12:37 Environment: Jenkins 2.109 Plastic plugin 2.10 Priority: Minor Reporter: Mikael Kalms Jenkins expects any Shared Library repository to have a src/ or a vars/ folder in its root. However, the Plastic plugin enforces a Plastic-workspace name, and places the repository contents within the Plastic-workspace folder (which in turn is within the Jenkins-workspace folder). Since Plastic places all files within an extra folder, Jenkins is unable to find the Shared Library source files. This, in turn, means that Shared Libraries cannot be sourced from Plastic repositories. Add Comment

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

[mikael@kalms.org (JIRA)]

Mikael Kalms updated an issue

Jenkins / JENKINS-50284 PlasticSCM - cannot use Plastic repository as Shared Library source

Change By: Mikael Kalms

Jenkins expects any Shared Library repository to have a src/ or a vars/ folder in its root.

However, the Plastic plugin enforces a Plastic-workspace name, and places the repository contents within the a Plastic-workspace folder (which in turn is within inside of the Jenkins-workspace folder ) .

Since Plastic places all files within an extra folder, Jenkins is unable to find the Shared Library source files. This, in turn, means that Shared Libraries cannot be sourced from Plastic repositories.

Add Comment

[mgonzalez@codicesoftware.com (JIRA)]

Miguel González assigned an issue to Miguel González

Jenkins / JENKINS-50284 PlasticSCM - cannot use Plastic repository as Shared Library source

Change By: Miguel González Assignee: Miguel González

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[mgonzalez@codicesoftware.com (JIRA)]

Miguel González commented on JENKINS-50284

Re: PlasticSCM - cannot use Plastic repository as Shared Library source Hi Mikael Kalms!   I'm glad to notify you that this issue was fixed in plasticscm-plugin version 2.22. Please upgrade to that version and try it out!

Add Comment

[mgonzalez@codicesoftware.com (JIRA)]

Miguel González updated JENKINS-50284

Shared libraries need to have a randomly generated workspace name while keeping the workspace dir easily identifiable. A fix for this issue was released in version 2.22.

Jenkins / JENKINS-50284

PlasticSCM - cannot use Plastic repository as Shared Library source

Change By: Miguel González Status: Open Fixed but Unreleased Resolution: Fixed Released As: plasticscm-plugin-2.22

Add Comment

[mgonzalez@codicesoftware.com (JIRA)]

Miguel González updated JENKINS-50284

Jenkins / JENKINS-50284 PlasticSCM - cannot use Plastic repository as Shared Library source

Change By: Miguel González Status: Fixed but Unreleased Resolved

Add Comment

[mgonzalez@codicesoftware.com (JIRA)]

Miguel González closed an issue as Fixed

Jenkins / JENKINS-50284 PlasticSCM - cannot use Plastic repository as Shared Library source

Change By: Miguel González Status: Resolved Closed

Add Comment

[mikael@kalms.org (JIRA)]

Mikael Kalms assigned an issue to Mikael Kalms

Jenkins / JENKINS-50284 PlasticSCM - cannot use Plastic repository as Shared Library source

Change By: Mikael Kalms Assignee: Miguel González Mikael Kalms

Add Comment

[mikael@kalms.org (JIRA)]

Mikael Kalms commented on JENKINS-50284

Re: PlasticSCM - cannot use Plastic repository as Shared Library source Confirmed, v 2.22 solves our problems with Shared Libraries. We have moved our Shared Libraries from GitHub to Plastic now.

Add Comment