[JIRA] (JENKINS-56056) SCM polling fails when project path includes accented chars
Title: Message Title José Lamas updated an issue Jenkins / JENKINS-56056 SCM polling fails when project path includes accented chars Change By: José Lamas Released As: https://github.com/jenkinsci/genexus-plugin/releases/tag/genexus- 1.8 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.197479.1549640183000.1237.1581977880056%40Atlassian.JIRA.
[JIRA] (JENKINS-56056) SCM polling fails when project path includes accented chars
Title: Message Title José Lamas resolved as Fixed Jenkins / JENKINS-56056 SCM polling fails when project path includes accented chars Change By: José Lamas Status: In Progress Resolved Resolution: Fixed Released As: 1.8 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.197479.1549640183000.1236.1581977760163%40Atlassian.JIRA.
[JIRA] (JENKINS-60560) Compatibility with Pipeline
Title: Message Title José Lamas created an issue Jenkins / JENKINS-60560 Compatibility with Pipeline Issue Type: New Feature Assignee: José Lamas Components: genexus-plugin Created: 2019-12-20 14:49 Priority: Major Reporter: José Lamas Implement and validate compatibility with Pipeline as described in https://github.com/jenkinsci/pipeline-plugin/blob/541faf611659e1e6b8f2cbbd3435756b27633db4/COMPATIBILITY.md Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-57791) Database credentials in Build Step configuration
Title: Message Title José Lamas created an issue Jenkins / JENKINS-57791 Database credentials in Build Step configuration Issue Type: New Feature Assignee: José Lamas Components: genexus-plugin Created: 2019-05-31 13:54 Priority: Minor Reporter: José Lamas The MSBuild script invoked for the KB build step uses the OpenKnowledgeBase task, with no database credentials, so that they are taken from the knowledgebase.connection file. In some cases the build step may need to use custom database credentials but there is currently no way to specify them. Add Comment
[JIRA] (JENKINS-56056) SCM polling fails when project path includes accented chars
Title: Message Title José Lamas started work on JENKINS-56056 Change By: José Lamas Status: Open In Progress 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56056) SCM polling fails when project path includes accented chars
Title: Message Title José Lamas created an issue Jenkins / JENKINS-56056 SCM polling fails when project path includes accented chars Issue Type: Bug Assignee: José Lamas Components: genexus-plugin Created: 2019-02-08 15:36 Priority: Minor Reporter: José Lamas This was reported in BuildAndDeploy forum https://groups.google.com/a/genexus.com/d/msg/buildanddeploy/m5Hcyahcfbk/1GcZy4LUEwAJ If the path to scm-polling.txt contains accented characters (for example, if the project name contains them) the XML parsing fails. For example, using Ôsçár as the name project will attempt (and fail) to parse "C:\Dev\genexus-plugin\work\workspace\Ôsçár\scm-polling.txt". Add Comment
[JIRA] (JENKINS-55921) When SCM polling fails, the result is logged as "no changes"
Title: Message Title José Lamas resolved as Fixed Jenkins / JENKINS-55921 When SCM polling fails, the result is logged as "no changes" Change By: José Lamas Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/genexus-plugin/releases/tag/genexus-1.5 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55921) When SCM polling fails, the result is logged as "no changes"
Title: Message Title José Lamas created an issue Jenkins / JENKINS-55921 When SCM polling fails, the result is logged as "no changes" Issue Type: Improvement Assignee: José Lamas Components: genexus-plugin Created: 2019-02-01 21:14 Priority: Minor Reporter: José Lamas This was reported in BuildAndDeploy forum https://groups.google.com/a/genexus.com/forum/#!msg/buildanddeploy/mFdIsnRLQKE/MJjUrFD8AQAJ There's also a similar issue about git-client-plugin at https://issues.jenkins-ci.org/browse/JENKINS-32712 When a project uses SCM polling, if the polling fails (eg: bad credentials) although the plugin throws an exception, the engine takes that as "no changes", the build is not triggered and it's hard to note the problem. Add Comment
[JIRA] (JENKINS-53393) Support for master-slave configuration
Title: Message Title José Lamas started work on JENKINS-53393 Change By: José Lamas Status: Open In Progress 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53393) Support for master-slave configuration
Title: Message Title José Lamas resolved as Fixed Jenkins / JENKINS-53393 Support for master-slave configuration Change By: José Lamas Status: In Progress Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/genexus-plugin/releases/tag/genexus-1.3 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53393) Support for master-slave configuration
Title: Message Title José Lamas created an issue Jenkins / JENKINS-53393 Support for master-slave configuration Issue Type: Improvement Assignee: José Lamas Components: genexus-plugin Created: 2018-09-03 17:42 Priority: Minor Reporter: José Lamas Current plugin implementation does not work when workspace is on a slave node. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-51640) Optimization in query used to get current revision info
Title: Message Title José Lamas resolved as Fixed Fixed on version 1.2 Jenkins / JENKINS-51640 Optimization in query used to get current revision info Change By: José Lamas Status: In Progress Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/genexus-plugin/releases/tag/genexus-1.2 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. For more options, visit https://groups.google.com/d/optout.
