[JIRA] (JENKINS-16700) [cppccheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException
Eric Brito created JENKINS-16700 [cppccheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException Issue Type: Bug Assignee: Gregory Boissinot Components: cppcheck Created: 08/Feb/13 12:23 PM Description: If I use --enable=style or --enable=all I get this error: Cppcheck Starting the cppcheck analysis. Cppcheck Processing 1 files with the pattern 'cppcheck-result2.xml'. Cppcheck Parsing throws exceptions. javax.xml.bind.UnmarshalException with linked exception: com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 3-byte UTF-8 sequence. Build step 'Publish Cppcheck results' changed build result to FAILURE Build step 'Publish Cppcheck results' marked build as failure how I run cppcheck: cppcheck --enable=style --xml-version=2 %workspace%\Main\ 2 cppcheck-result2.xml this works fine: cppcheck --xml-version=2 %workspace%\Main\ 2 cppcheck-result2.xml Environment: Windows XP, Jenkins 1.498, cppcheck plug-in 1.13, Cppcheck 1.57 Project: Jenkins Priority: Major Reporter: Eric Brito This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito commented on JENKINS-16373 email-ext cant access SVN_REVISION_1 I only have one build set up. All I did was include several repositories on the same build. Then I added one build step: windows batch file. That step runs a few metrics apps and then calls the company's older bat file that actually builds the application. That older bat can access the environment variables listed here: http://yourjenkinsURL/env-vars.html/ and while SVN_REVISION_1 isn't listed, it works. Email-ext is a post-build step. Is it possible the variable becomes unavailable after building? my build log is kind of big, but the email bit is this: 16:47:14 Email was triggered for: Success 16:47:14 Sending email for trigger: Success 16:47:14 Sending email to: myemailhere 16:47:21 Finished: SUCCESS This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16388) Regarding SVN_REVISION_1 and SVN_URL_1
Eric Brito created JENKINS-16388 Regarding SVN_REVISION_1 and SVN_URL_1 Issue Type: Improvement Assignee: Unassigned Components: subversion Created: 17/Jan/13 10:23 AM Description: Two things: First, I think SVN_REVISION_# should be listed here: http://yourJenkinsURL/env-vars.html That would make things easier for people who have more than one repository on the same build. Right now I don't thinks it's documented anywhere. Second, I'm having trouble accessing SVN_REVISION_1. I created a ticket about it, but maybe the problem is with the subversion plugin not making this variable available to other plugins? https://issues.jenkins-ci.org/browse/JENKINS-16373 Environment: Windows XP, Jenkins ver. 1.498, Jenkins Subversion Plug-in 1.44, email-ext 2.25 Project: Jenkins Priority: Minor Reporter: Eric Brito This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito
commented on JENKINS-16373
email-ext cant access SVN_REVISION_1
Actually, ${ENV, var="SVN_REVISION_1"} DOES work. I was aborting the project in order to force the email SVN_REVISION_1 was never created. Sorry for wasting your time.
But if you do have some time, I still haven't been able to use these correctly (email has all these lines, none seem to be working):
${CHANGES, showPaths="true", format="%a: %r %p \n--\ %m\", pathFormat="\n\t- %p"}
${CHANGES, showPaths="true", format="%a: %r %p %m\", pathFormat="\t%p\n"}
${CHANGES, showPaths="true", showDependencies="false", format="%a: %r %p \n--\"%m\", pathFormat="\n\t- %p"}
${CHANGES, "true", "false", "%a: %r %p \n--\ %m\", "\n\t- %p"}
${CHANGES, "true", "true", "%a: %r %p %m\", "\n\t- %p"}
${BUILD_LOG_MULTILINE_REGEX, "error", "10", "true", null, "false", null}
${BUILD_LOG_MULTILINE_REGEX, "error", "10", "true"}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16388) Regarding SVN_REVISION_1 and SVN_URL_1
Eric Brito commented on JENKINS-16388 Regarding SVN_REVISION_1 and SVN_URL_1 The second thing is working, ignore it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito
created JENKINS-16373
email-ext cant access SVN_REVISION_1
Issue Type:
Bug
Assignee:
Slide-O-Mix
Components:
email-ext
Created:
16/Jan/13 11:55 AM
Description:
I'm building a project with multiple SVN repositories. Using the Email-ext plugin to email when a job is successfull or failed.
When I use the token ${SVN_REVISION} all I get is the number 400, which isn't the build number nor any of the repositories' revision number.
What I want to use is the same variable the svn plugin provides: %SVN_REVISION_1%, but neither ${ENV, var="SVN_REVISION_1"} nor ${ENV, var="%SVN_REVISION_1%"} work. Both show up as blanks
Also, when I list the variables (${ENV, var=""}) I can't find SVN_REVISION or SVN_REVISION_1.
The email needs to have SVN_REVISION_1 on the subject, or else it'll be quite a hassle to find what version was built.
Are there any workarounds?
Environment:
Windows XP, Jenkins ver. 1.498, Jenkins Subversion Plug-in 1.44, email-ext 2.25
Project:
Jenkins
Priority:
Major
Reporter:
Eric Brito
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito commented on JENKINS-16373 email-ext cant access SVN_REVISION_1 I understand. I can access it through a batch file (build step), does that mean it's been made available? And where does the 400 come from when I use $(SVN_REVISION) ? (doesn't svn_revision come from jenkin's built-in svn plugin, just like svn_revision_1) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito edited a comment on JENKINS-16373 email-ext cant access SVN_REVISION_1 I understand. I can access it through a batch file (build step), does that mean it's been made available? And where does the 400 come from when I use $(SVN_REVISION) ? (doesn't svn_revision come from jenkin's built-in svn plugin, just like svn_revision_1?) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito commented on JENKINS-16373 email-ext cant access SVN_REVISION_1 This is from the Subversion Plugin. Doesn't this mean it should be available? Subversion Revision and URL information as Environment Variables The Subversion SCM plugin exports the svn revisions and URLs of the build's subversion modules as environment variables. These are $SVN_REVISION_n and $SVN_URL_n, where n is the 1-based index of the module in the configuration. For backwards compatibility if there's only a single module, its values are also exported as $SVN_REVISION and $SVN_URL. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito
commented on JENKINS-16373
email-ext cant access SVN_REVISION_1
No space, even though the examples I posted above had them. just tried with and without spaces, the results are the same as below:
when I try these 3 lines:
${ENV,var="SVN_REVISION_1"} - blank
${ENV,var="SVN_REVISION"} - blank
${ENV,var=""} - doesn't have SVN_REVISION, SVN_URL
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16373) email-ext can't access SVN_REVISION_1
Eric Brito
commented on JENKINS-16373
email-ext cant access SVN_REVISION_1
sorry for posting something off-topic, but while I have your attention: what is wrong with these lines? none of them are working, the email just the entire line as I typed it, no change report:
${CHANGES, showPaths=true, format="%a: %r %p \n--\"%m\", pathFormat="\n\t- %p"}
${CHANGES, showPaths=true, format="%a: %r %p "%m\", pathFormat="\t%p\n"}
${CHANGES, showPaths=true, showDependencies=false, format="%a: %r %p \n--\"%m\", pathFormat="\n\t- %p"}
${CHANGES, true, false, "%a: %r %p \n--\"%m\", "\n\t- %p"}
(would love if there were examples on the tokens reference.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16298) DRY FATAL: null java.lang.StackOverflowError
Eric Brito commented on JENKINS-16298 DRY FATAL: null java.lang.StackOverflowError No such file is created when the error happens. I changed the threshold from the default value (6) to 50 lines and it worked. 30 and 10 also worked. 8 caused it to crash, 6177 warnings. 9 worked, 4795 warnings. At 10, the dry-warningsxml file is 43 Mbytes (3878 warnings). at 9, it's 78 Mbytes (6177 warnings). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16298) DRY FATAL: null java.lang.StackOverflowError
Eric Brito edited a comment on JENKINS-16298 DRY FATAL: null java.lang.StackOverflowError No such file is created when the error happens. I changed the threshold from the default value (6) to 50 lines and it worked. 30 and 10 also worked. 8 caused it to crash, 6177 warnings. 9 worked, 4795 warnings. At 10, the dry-warningsxml file is 43 Mbytes (3878 warnings). at 9, it's 78 Mbytes (4795 warnings). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16298) DRY FATAL: null java.lang.StackOverflowError
Eric Brito commented on JENKINS-16298 DRY FATAL: null java.lang.StackOverflowError Jenkins ver. 1.498 Duplicate Code Scanner Plug-in 2.33 It´s a freestyle project, building is done through windows batch files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16298) DRY FATAL: null java.lang.StackOverflowError
Eric Brito commented on JENKINS-16298 DRY FATAL: null java.lang.StackOverflowError This is how I call simian: C:\Simian\bin\simian-2.3.33.exe -formatter=xml:%WORKSPACE%\simian.xml "C:\Jenkins\jobs\QiBuilder\workspace\QiBuilder.c" "C:\Jenkins\jobs\QiBuilder\workspace\QiBuilder.h" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16298) DRY FATAL: null java.lang.StackOverflowError
Eric Brito updated JENKINS-16298 DRY FATAL: null java.lang.StackOverflowError here's the XML file Change By: Eric Brito (10/Jan/13 11:25 AM) Attachment: simian.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
