[JIRA] (JENKINS-37456) xcode build fails when using NodeLabel plugin with FAILURE in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-10179/DVTFoundation/MacroExpansion/DVTMacroDefini
Title: Message Title
Dirk Hain created an issue
Jenkins / JENKINS-37456
xcode build fails when using NodeLabel plugin with FAILURE in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-10179/DVTFoundation/MacroExpansion/DVTMacroDefinitionConditionSet.mm:154
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Components:
nodelabelparameter-plugin
Created:
2016/Aug/16 11:19 PM
Priority:
Blocker
Reporter:
Dirk Hain
Blocker because xcode ios builds cannot be run when the NodeLabel plugin is used in the job. We were able to isolate the issue to the use of the NodeLabel plugin and were baffled that this plugin could have this side effect. We are using a standard xcode build running on a MacPro connected to our jenkins master. This is what we see in the console: xcodebuild[6784:2033931] [MT] DVTAssertions: ASSERTION FAILURE in /Library/Caches/com.apple.xbs/Sources/DVTFrameworks/DVTFrameworks-10179/DVTFoundation/MacroExpansion/DVTMacroDefinitionConditionSet.mm:154 15:54:41 Details: stringRep should be a non-empty string, but it's an empty string 15:54:41 Object: 15:54:41 Method: +conditionSetFromStringRepresentation:getBaseMacroName:error: 15:54:41 Thread: {number = 1, name = main} 15:54:41 Hints: None 15:54:41 Backtrace: 15:54:41 0 -[DVTAssertionHandler handleFailureInMethod:object:fileName:lineNumber:assertionSignature:messageFormat:arguments:] (in DVTFoundation) 15:54:41 1 _DVTAssertionHandler (in DVTFoundation) 15:54:41 2 _DVTAssertionFailureHandler (in DVTFoundation)
[JIRA] (JENKINS-29487) stringRep should be a non-empty string, but it's an empty string
Title: Message Title Dirk Hain commented on JENKINS-29487 Re: stringRep should be a non-empty string, but it's an empty string We were running into this issue and were able to isolate the problem to the fact that the NodeLabel plugin (https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin) is enabled for this build or not. Once we disabled the plugin for this build the ios build started working without the above 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] [git-parameter-plugin] (JENKINS-26799) Multiple SCMs plugin support
Dirk Hain commented on JENKINS-26799 Multiple SCMs plugin support I can confirm the same issue. This plugin would be great but I cannot use it because I need to fetch 2 git repositories. 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/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-26799) Multiple SCMs plugin support
Dirk Hain updated JENKINS-26799 Multiple SCMs plugin support Change By: Dirk Hain (13/Mar/15 8:46 PM) Priority: Minor Major 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/d/optout.
[JIRA] [jenkins-multijob-plugin] (JENKINS-18768) Multijob plugin doesn't aggregate test results from downstream projects
Dirk Hain commented on JENKINS-18768 Multijob plugin doesnt aggregate test results from downstream projects I am using Jenkins 1.548 with multijob-plugin 1.11 and am running into the same problem. I tried the automatic aggregation as well as listing out the relevant projects explicitly but no success. Here is the build log of the post build tasks: POST BUILD TASK : SUCCESS END OF POST BUILD TASK : 0 Checking for post-build Performing post-build step Checking if email needs to be generated Email was triggered for: Unstable Email was triggered for: Still Unstable Trigger Unstable was overridden by another trigger and will not send an email. Sending email for trigger: Still Unstable Overriding default server settings, creating our own session messageContentType = text/html; charset=UTF-8 Adding recipients from recipient list Successfully created MimeMessage This issues seems to be open for a while now. Any progress on why the aggregation is failing? 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] [email-ext] (JENKINS-20804) showDependencies for ${CHANGES} doesn't seem to work
Dirk Hain
commented on JENKINS-20804
showDependencies for ${CHANGES} doesnt seem to work
Ok, I was able to resolve the issue by creating a correct chain of fingerprinting across my builds. The piece that was missing was that the build where I was not able to see dependent changes did not have a copy of the artifacts in the workspace. Although that particular build does not require the artifacts Jenkins needs them in the workspace to establish the connection that the build is dependent on a previous build that created the artifact. Since Jenkins does not support fingerprinting outside the workspace directory it is easiest just to use the "Copy artifacts from another build" option and tick the fingerprinting option.
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] [email-ext] (JENKINS-20804) showDependencies for ${CHANGES} doesn't seem to work
Dirk Hain
commented on JENKINS-20804
showDependencies for ${CHANGES} doesnt seem to work
Cool with me.
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] [email-ext] (JENKINS-20804) showDependencies for ${CHANGES} doesn't seem to work
Dirk Hain
commented on JENKINS-20804
showDependencies for ${CHANGES} doesnt seem to work
Thanks for your comment, Alex. I checked the dependency graph and it is populated correctly. However, in the job that has the test failures I am copying test artifacts around. Not sure if that is the problem, I enabled fingerprinting of the copied artifacts to no avail. The fact that the dependent changes are shown correctly IF the job does not complete (no tests run) but does not show dependent changes IF the job completes unstable (tests are run with some failing) indicates that the root cause could be the copying of files. I will try to investigate further and see if I can get it working.
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] [email-ext] (JENKINS-20804) showDependencies for ${CHANGES} doesn't seem to work
Dirk Hain
commented on JENKINS-20804
showDependencies for ${CHANGES} doesnt seem to work
I am running into a similar issue with
Jenkins: 1.548
email-ext: 2.37.2
However, for me the email-ext plugin will return changes with dependencies IF the build ends with a FAILURE. If the build is unstable the changes will not be populated. Here are the settings I am using:
${CHANGES, showDependencies=true, format="[%a] %d, %r: %m\\n %p\\n"}
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.
