[JIRA] (JENKINS-57098) JSON Exchange format for import/export?
Title: Message Title
Jeremie Bresson edited a comment on JENKINS-57098
Re: JSON Exchange format for import/export?
This is released in {{edu.hm.hafner:analysis-model:5.1.0}}In the Jenkins plugin:* This is fixed with commit https://github.com/jenkinsci/warnings-ng-plugin/commit/7063463459661cddf65e8e0c1c9b6e6ef6fec05a on the {{master}} branch, but not released yet. * {{io.jenkins.plugins:warnings-ng:5.1.0}} is using {{edu.hm.hafner:analysis-model:5.0.0}} as dependency.
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.198843.16000.21632.1559716920120%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57098) JSON Exchange format for import/export?
Title: Message Title Jeremie Bresson commented on JENKINS-57098 Re: JSON Exchange format for import/export? This is fixed with commit https://github.com/jenkinsci/warnings-ng-plugin/commit/7063463459661cddf65e8e0c1c9b6e6ef6fec05a on the master branch, but not released yet. 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.198843.16000.21629.1559716320128%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57098) JSON Exchange format for import/export?
Title: Message Title Jeremie Bresson updated JENKINS-57098 Jenkins / JENKINS-57098 JSON Exchange format for import/export? Change By: Jeremie Bresson Status: Resolved Fixed but Unreleased 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.198843.16000.21620.1559716200440%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57098) JSON Exchange format for import/export?
Title: Message Title Jeremie Bresson updated an issue Jenkins / JENKINS-57098 JSON Exchange format for import/export? Change By: Jeremie Bresson Released As: 5.1.0 (analysis-model and warnings-ng) 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.198843.16000.21623.1559716200477%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57854) With "Warnings Plugin Native Format" tool, the expected input xml is not consistent with the exported xml
Title: Message Title Jeremie Bresson created an issue Jenkins / JENKINS-57854 With "Warnings Plugin Native Format" tool, the expected input xml is not consistent with the exported xml Issue Type: Bug Assignee: Ulli Hafner Attachments: Screenshot 2019-06-05 at 06.52.04.png Components: warnings-ng-plugin Created: 2019-06-05 06:13 Priority: Minor Reporter: Jeremie Bresson Introduced with JENKINS-56510, when selecting "Warnings Plugin Native Format" as "Tool" the "Warning NG Plugins" should import an xml exported by the API: /joball/api/xml The problem is that this API exports the report of issues as: "io.jenkins.plugins.analysis.core.restapi.ReportApi"> 2 And the plugin expect "report/issue" as xmlIssueRoot (sort of x-path query) to find the issues. In other words this can be imported: "io.jenkins.plugins.analysis.core.restapi.ReportApi"> 2
[JIRA] (JENKINS-57098) JSON Exchange format for import/export?
Title: Message Title Jeremie Bresson updated JENKINS-57098 Jenkins / JENKINS-57098 JSON Exchange format for import/export? Change By: Jeremie Bresson Status: Fixed but Unreleased Resolved Released As: 5.1.0 (analysis-model and warnings-ng) 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.198843.16000.21593.1559714640241%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57098) JSON Exchange format for import/export?
Title: Message Title Jeremie Bresson commented on JENKINS-57098 Re: JSON Exchange format for import/export? I have created a PR: https://github.com/jenkinsci/analysis-model/pull/168 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-57098) JSON Exchange format for import/export?
Title: Message Title Jeremie Bresson commented on JENKINS-57098 Re: JSON Exchange format for import/export? For the moment Asciidoctor is logging to the console and provide an API to implement a custom Log-Handler. I think that for the time being, having a small extension that logs to the JSON format is an appropriate way to do it. 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-57098) JSON Exchange format for import/export?
Title: Message Title Jeremie Bresson commented on JENKINS-57098 Re: JSON Exchange format for import/export? Thank you for your feedback. Is Asciidoctor already a Jenkins Plugin? Note that in this case you can also can consider to directly create the issues using the API rather then working with files at all. Then you do not need to think about flushing of the console log... I have no idea if there is an Asciidoctor plugin. Like many java developers and I prefer to orchestrate my build with a tool like maven or gradle. This way I can run it locally and have the CI server (Jenkins) to reproduce it at server side. So for me having the build tool flushing logs to a file and having Jenkins to read this file is a valid approach. 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-56510) Provide generic issue parser for custom tools
Title: Message Title Jeremie Bresson commented on JENKINS-56510 Re: Provide generic issue parser for custom tools I have similar needs, I have made a proposal for a JSON based format in JENKINS-57098. 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-57098) JSON Exchange format for import/export?
Title: Message Title
Jeremie Bresson created an issue
Jenkins / JENKINS-57098
JSON Exchange format for import/export?
Issue Type:
Improvement
Assignee:
Ulli Hafner
Components:
analysis-model
Created:
2019-04-18 06:28
Priority:
Major
Reporter:
Jeremie Bresson
Having the Groovy based warnings parser is a great way to support new tools that reports warnings. It might be useful when you write the report (because you write the static analyser or because you plug something into an existing tool). — Example: For example I have create an extension for Asciidoctor, that collects the issues reported and put them into a file like this.
/tmp/file.adoc|5|ERROR|include file not found: /tmp/other.adoc
/tmp/file.adoc|7|HIGH|list item index: expected 1, got 8
UNKNOWN|0|HIGH|skipping reference to missing attribute: bla
Thank to the Groovy based warnings parser, I can use a regex ((.)|(\d+)|(.)|(.*)) to parse the log that I have created. Read more about this: https://jmini.github.io/asciidoctorj-file-logger/ — The next step for me would be to contribute the parser to this project, so that it no longer rely on a config in Jenkins. But before doing this, I would like to challenge the format that is used... I could not find any discussion about this. One idea that I have: a collection of JSON structures on each line:
{"fileName": "/tmp/file.adoc", "lineStart": "5", "severity": "ERROR", "message": "include file not found: /tmp/other.adoc"}
{"fileName": "/tmp/file.adoc", "lineStart": "7", "severity": "HIGH",
[JIRA] (JENKINS-41392) disableConcurrentBuilds should take an optional boolean parameter that defaults to "true"
Title: Message Title Jeremie Bresson commented on JENKINS-41392 Re: disableConcurrentBuilds should take an optional boolean parameter that defaults to "true" Jesse Glick: this would be trivial in Scripted Can you please explain here how "enable concurrent builds" can be activate with in a Scripted Pipeline? 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-37794) JGit filter tags with "/" in their name
Title: Message Title Jeremie Bresson created an issue Jenkins / JENKINS-37794 JGit filter tags with "/" in their name Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2016/Aug/30 5:24 AM Priority: Major Reporter: Jeremie Bresson As discussed in JENKINS-37635, there is a difference between the JGit and the native git implementation: Take this demo repository as example: https://github.com/klimas7/Learn It contains 3 tags: v1.0.0, release/v.1.0.0 and release-tags/v.1.0.0 Depending on the git client used (JGit or native git) the results are not the same. JGit only find v1.0.0. Add Comment
[JIRA] (JENKINS-37635) Git Tags with "/" in their name are not displayed
Title: Message Title Jeremie Bresson commented on JENKINS-37635 Re: Git Tags with "/" in their name are not displayed Thank you, I have opened JENKINS-37794 to continue to track this issue. 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-37635) Git Tags with "/" in their name are not displayed
Title: Message Title Jeremie Bresson commented on JENKINS-37635 Re: Git Tags with "/" in their name are not displayed Thank you for your help and the idea to use some public repo. I have configured a Job exactly as you did and first I was not successful. I figured out that this was due to the global git configuration in my Jenkins. JGit was configured to be used first (see screenshot)When I removed it, it now works as for you. Can you point me out the Git Method you are using, this way I can file an issue against the git-client-plugin, because their implementation is not working. I think this issue can be closed "works as expected". 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-37635) Git Tags with "/" in their name are not displayed
Title: Message Title Jeremie Bresson updated an issue Jenkins / JENKINS-37635 Git Tags with "/" in their name are not displayed Change By: Jeremie Bresson Attachment: Git_intallation.png 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-37635) Git Tags with "/" in their name are not displayed
Title: Message Title
Jeremie Bresson created an issue
Jenkins / JENKINS-37635
Git Tags with "/" in their name are not displayed
Issue Type:
Bug
Assignee:
Boguslaw Klimas
Components:
git-parameter-plugin
Created:
2016/Aug/23 6:23 PM
Priority:
Minor
Reporter:
Jeremie Bresson
I have two tags in one git repository:
v1.0.0
release-tags/v1.0.0
When the plugin is retrieving tags (we are building on slaves, so the workspace is not present. With the version 0.6.2 this is no longer a problem thanks to the resolution of JENKINS-16290) The second tag ("release-tags/v1.0.0") is not presented in the list-box. My guess is that this is because of the slash "/" contained in the tag name. I hope anyone can confirm that this is the case. I will continue my investigations and try to find a Stacktrace or the corresponding line in the code (but I am not familiar with the Jenkins code base).
Add Comment
[JIRA] (JENKINS-37370) Retrieving Git references do not work with variable in "Repository URL"
Title: Message Title Jeremie Bresson commented on JENKINS-37370 Re: Retrieving Git references do not work with variable in "Repository URL" Hi Boguslaw Klimas, Thank you so much for this bugfix. I have seen the PR has been merged. I am not really able to build the branch locally and to test it in a local Jenkins (I never did it and I should first create the complete local setup). I will definitively test it (and report here) when the fix is included in a release. 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-37370) Retrieving Git references do not work with variable in "Repository URL"
Title: Message Title Jeremie Bresson created an issue Jenkins / JENKINS-37370 Retrieving Git references do not work with variable in "Repository URL" Issue Type: Bug Assignee: Boguslaw Klimas Components: git-parameter-plugin Created: 2016/Aug/12 9:28 AM Priority: Minor Reporter: Jeremie Bresson My job is configured to use a Git Repository. In the "Repository URL" field, I use following variable: $GIT_REPO_URL defined as Global variable "in the Jenkins /configure Page" (this is a convention across several teams and Jenkins instance in our company). I am also in the case described and solved in JENKINS-16290 (we are building on slaves, so the workspace is not present. With the version 0.6.2 I am now using this is not a problem anymore). To work around this issue, I have use the real url in "Repository URL" instead of the indirection with the variable. Aug 12, 2016 11:07:57 AM SEVERE net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition generateContents Unexpected error! hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.InvalidRemoteException: Invalid remote: $GIT_REPO at org.jenkinsci.plugins.gitclient.JGitAPIImpl$5.execute(JGitAPIImpl.java:1450) at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.clone(AbstractGitAPIImpl.java:67) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.clone(JGitAPIImpl.java:135) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.initWorkspace(GitParameterDefinition.java:381) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition.generateContents(GitParameterDefinition.java:260) at net.uaznia.lukanus.hudson.plugins.gitparameter.GitParameterDefinition$DescriptorImpl.doFillValueItems(GitParameterDefinition.java:447) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at
