[JIRA] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Joshua Moody commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception UPDATE: The project I am working on has submodules. If I remove the Advanced Submodule Processing options (or disable processing), I don't get this NPE. Of course, my build then fails downstream. I am sponsoring a fix for 50USD. 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Joshua Moody commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Is it only happening when there isn't a previous build? Confirmed. Once the job has changes, I no longer see this NPE. 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] [ghprb] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Joshua Moody commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception I am seeing this as well. jenkins 1.575, 1.574 ghprb - 1.13, 1.13-1 GitHub Plugin - 1.9, 1.9.1 GitHub API plugin - 1.56 RE: more logs - I see the same logs as Frank K. 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Joshua Moody commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception re: previous build Interesting. I had to blow away my workspace for a completely unrelated reason. Every build since has failed (b/c a vagrant box cannot be provisioned) and ended with the NPE describe above. Despite having several (failing) runs, I always see: "First time build. Skipping changelog." after the pull from GitHub. So, maybe it is only happening when there isn't a previous build. I will push on this a little harder later today. 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Joshua Moody commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Yes. It appears that this is only happening if there is no last built revisin. 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Joshua Moody edited a comment on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Yes. It appears that this is only happening if there is no last built revision. 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Joshua Moody edited a comment on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception Yes. It appears that this is only happening if there is no last built revision. The blame for that line is back in 2012-10-22 - http://git.io/mq-TlA I will look up stream to see why there is no last built revision; for this job, it looks like there should be one. 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] (JENKINS-6856) Git builds with detached head no matter what
Joshua Moody commented on JENKINS-6856 Git builds with detached head no matter what I second what Michael Floering says. I don't believe this has been fixed. The detached head state is causing a bunch of problems for us. 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] [core] (JENKINS-19246) Configure Project loading overloay not hiding error invalid gitTool selection Default
Joshua Moody commented on JENKINS-19246 Configure Project loading overloay not hiding error invalid gitTool selection Default I still see this problem in 1.559. MacOS 10.9.2 git version 1.9.2 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] (JENKINS-6856) Git builds with detached head no matter what
Joshua Moody edited a comment on JENKINS-6856 Git builds with detached head no matter what I second what Michael Floering says. I don't believe this has been fixed. The detached head state is causing a bunch of problems for us. UPDATE: After sleeping on the problem I, made a changes which I think resolved the detached head problem: In the Git plugin Advanced Options, I added: "Checkout to a specific local branch" and provided a branch name. 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] [ghprb] (JENKINS-22550) GHPRB NoSuchMethodError
Joshua Moody commented on JENKINS-22550 GHPRB NoSuchMethodError I am also seeing this on: Jenkins: 1.559 GHPRB:1.11.2 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-13449) version number of ipa and dSYM.zip is incorrect
Joshua Moody created JENKINS-13449:
--
Summary: version number of ipa and dSYM.zip is incorrect
Key: JENKINS-13449
URL: https://issues.jenkins-ci.org/browse/JENKINS-13449
Project: Jenkins
Issue Type: Bug
Components: xcode
Affects Versions: current
Environment: MacOS 10.7.3
Xcode 4.3.2
Jenkins 1.459
Xcode Integration Plugn 1.3.1
Reporter: Joshua Moody
Attachments: 2012-04-13_23-20-25.png
I have attached a screenshot of my Xcode build step.
Below the output of an ls -al inside my build directory. As you can see, the
version is number is incorrect (it is `$($PlistBuddyPath -c Print
CFBundleGetInfoString $INFOPLIST_FILE)nnelsennecho Skipping the
modification of $INFOPLIST_FILE for _jenkinsnnfinn?1.0`).
Let me know if you need more information.
{noformat}
_jenkins daemon 1752936 Apr 13 23:07 RiseUp-AdHoc-$($PlistBuddyPath -c
Print CFBundleGetInfoString $INFOPLIST_FILE)nnelsennecho Skipping the
modification of $INFOPLIST_FILE for _jenkinsnnfinn?1.0-dSYM.zip
_jenkins daemon 75161604 Apr 13 23:07 RiseUp-AdHoc-$($PlistBuddyPath -c
Print CFBundleGetInfoString $INFOPLIST_FILE)nnelsennecho Skipping the
modification of $INFOPLIST_FILE for _jenkinsnnfinn?1.0.ipa
{noformat}
It occurs to me that it is possible that I do not understand how to populate
the Marketing Version and Technical Version fields of the build step. I left
them blank, expecting from the instructions that my plist would be read.
Please advise.
Thanks for the effort! This is a great plugin.
jjm
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13449) version number of ipa and dSYM.zip is incorrect
[
https://issues.jenkins-ci.org/browse/JENKINS-13449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161589#comment-161589
]
Joshua Moody commented on JENKINS-13449:
Using ${BUILD_NUMBER} in the Marketing and Technical Version fields gave me an
.ipa and .app.DSYM.zip file with a readable name.
However, I am concerned that you are changing Info plist. What is the
motivation behind this? I can sort of see why you might want to do this, but
there are many cases where you would not. Can this be disabled? I will open
a feature request once someone responds.
Cheers!
jjm
version number of ipa and dSYM.zip is incorrect
---
Key: JENKINS-13449
URL: https://issues.jenkins-ci.org/browse/JENKINS-13449
Project: Jenkins
Issue Type: Bug
Components: xcode
Affects Versions: current
Environment: MacOS 10.7.3
Xcode 4.3.2
Jenkins 1.459
Xcode Integration Plugn 1.3.1
Reporter: Joshua Moody
Attachments: 2012-04-13_23-20-25.png
I have attached a screenshot of my Xcode build step.
Below the output of an ls -al inside my build directory. As you can see, the
version is number is incorrect (it is `$($PlistBuddyPath -c Print
CFBundleGetInfoString $INFOPLIST_FILE)nnelsennecho Skipping the
modification of $INFOPLIST_FILE for _jenkinsnnfinn?1.0`).
Let me know if you need more information.
{noformat}
_jenkins daemon 1752936 Apr 13 23:07 RiseUp-AdHoc-$($PlistBuddyPath -c
Print CFBundleGetInfoString $INFOPLIST_FILE)nnelsennecho Skipping the
modification of $INFOPLIST_FILE for _jenkinsnnfinn?1.0-dSYM.zip
_jenkins daemon 75161604 Apr 13 23:07 RiseUp-AdHoc-$($PlistBuddyPath -c
Print CFBundleGetInfoString $INFOPLIST_FILE)nnelsennecho Skipping the
modification of $INFOPLIST_FILE for _jenkinsnnfinn?1.0.ipa
{noformat}
It occurs to me that it is possible that I do not understand how to populate
the Marketing Version and Technical Version fields of the build step. I left
them blank, expecting from the instructions that my plist would be read.
Please advise.
Thanks for the effort! This is a great plugin.
jjm
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
