[JIRA] (JENKINS-40323) No SCM selected when adding a shared library
Title: Message Title
Jesse Glick commented on JENKINS-40323
Re: No SCM selected when adding a shared library
James Dumay yes, legacy means
you must use the ${library.NAME.version} hack
there is unlikely to be support for @abc1234 and generally selecting anything other than a branch head
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-40323) No SCM selected when adding a shared library
Title: Message Title James Dumay commented on JENKINS-40323 Re: No SCM selected when adding a shared library Jesse Glick whats the difference as far as the users concerned? Any behavioural difference or is it just a implementation detail? 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-40323) No SCM selected when adding a shared library
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40323 No SCM selected when adding a shared library Change By: Jesse Glick Component/s: workflow-cps-global-lib-plugin Component/s: 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-40323) No SCM selected when adding a shared library
Title: Message Title Jesse Glick commented on JENKINS-40323 Re: No SCM selected when adding a shared library FWIW “legacy” vs. “modern” simply refers to whether the SCM plugin is implementing the recommended APIs, or whether we need to fall back to a workaround compatible with older SCM plugins. 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-40323) No SCM selected when adding a shared library
Title: Message Title Jesse Glick commented on JENKINS-40323 Re: No SCM selected when adding a shared library No good fix without JENKINS-19584. 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-40323) No SCM selected when adding a shared library
Title: Message Title Patrick Wolf commented on JENKINS-40323 Re: No SCM selected when adding a shared library It's based on usage the of scm-api-plugin as far as I know but I'm not 100% sure how it is related. Jesse Glick or Stephen Connolly know more about it than anyone. I think we need a more descriptive term for them but I'm not sure what we could call them. 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-40323) No SCM selected when adding a shared library
Title: Message Title R. Tyler Croy commented on JENKINS-40323 Re: No SCM selected when adding a shared library Yes the issue exists when selecting either "SCM" option. And unfortunately the configuration page will happily save (but not persist any configuration of course) without a validation error. What is "modern scm" vs "legacy scm"? This is some implementation detail about whether a full clone is needed to get the library code or not. Something like that, has nothing to do with the SCM and everything with the SCM plugin from my recollection 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-40323) No SCM selected when adding a shared library
Title: Message Title James Dumay commented on JENKINS-40323 Re: No SCM selected when adding a shared library What is "modern scm" vs "legacy scm"? 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-40323) No SCM selected when adding a shared library
Title: Message Title Patrick Wolf commented on JENKINS-40323 Re: No SCM selected when adding a shared library Is this true for modern SCM, too? Should error on saving if they don't select something. I wouldn't want to choose a default for users. There's too much configuration needed to have a real default. 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-40323) No SCM selected when adding a shared library
Title: Message Title James Dumay commented on JENKINS-40323 Re: No SCM selected when adding a shared library Patrick Wolf we should revisit this and give it some design love. 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-40323) No SCM selected when adding a shared library
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-40323 No SCM selected when adding a shared library Issue Type: Bug Assignee: CloudBees Inc. Attachments: Selection_018.png Components: pipeline Created: 2016/Dec/09 12:31 AM Environment: Jenkins 2.19.4, fresh Pipeline installation as of 2016-12-08 Priority: Minor Reporter: R. Tyler Croy When configuring a Shared Library, after selecting "Legacy SCM" or "Modern SCM" the SCM options are listed with a radio selection UI element. Unfortunately there is no item in that radio selection that is selected by default, meaning if the user doesn't notice nothing has been actually selected in the radio selection, might Save the configuration and be very confused with their Shared Libraries don't work. Add Comment
