[JIRA] (JENKINS-57560) Export for JCasC is empty
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57560 Export for JCasC is empty Change By: Oleg Nenashev Labels: jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199471.1558357021000.13512.1559036400310%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57560) Export for JCasC is empty
Title: Message Title Pavel Janoušek closed an issue as Cannot Reproduce Seems working after re-test with core version 2.164.3, CaC 1.15 and Git 3.10. Export contains at least a default git tool configuration now (as I expected previously). Sorry for the confusion Mark. Jenkins / JENKINS-57560 Export for JCasC is empty Change By: Pavel Janoušek Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199471.1558357021000.7251.1558443300341%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57560) Export for JCasC is empty
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-57560 Export for JCasC is empty Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199471.1558357021000.5694.1558380120261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57560) Export for JCasC is empty
Title: Message Title Mark Waite edited a comment on JENKINS-57560 Re: Export for JCasC is empty I can't duplicate the problem you're describing unless I specifically delete the system provided default git tool. Since it is the system provided default git tool, there is no need to list the default in configuration as code. Whether it is configuration as code or not, there will be a default git implementation.Is that the condition you're seeing?More challenging is the JENKINS-57326 bug which won't allow JGit or JGit with Apache authentication to be represented in JCasC. Can you provide more details on the UI that you use to view the "Tools configuration WebGUI page"? I open the JCasC configuration from "Manage Jenkins" -> "Configuration as Code" -> "View Configuration", then I search for the "tools:" section and the "git:" subsection. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199471.1558357021000.5692.1558380060174%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57560) Export for JCasC is empty
Title: Message Title Mark Waite commented on JENKINS-57560 Re: Export for JCasC is empty I can't duplicate the problem you're describing unless I specifically delete the system provided default git tool. Since it is the system provided default git tool, there is no need to list the default in configuration as code. Whether it is configuration as code or not, there will be a default git implementation. Is that the condition you're seeing? More challenging is the JENKINS-57326 bug which won't allow JGit or JGit with Apache authentication to be represented in JCasC. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199471.1558357021000.5436.1558364820166%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57560) Export for JCasC is empty
Title: Message Title Pavel Janoušek created an issue Jenkins / JENKINS-57560 Export for JCasC is empty Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-05-20 12:57 Labels: jcasc-compatibility Priority: Major Reporter: Pavel Janoušek When configured and seen via Tools configuration WebGUI page I expect an exported record like: tool: git: installations: - name: "Default" home: "git" but nothing is produced. Add Comment
