[JIRA] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Michal Turek started work on JENKINS-23575 Post-Build-Step Publish Cppcheck results not available in job generator project Change By: Michal Turek (19/Jul/14 10:44 AM) Status: Open InProgress 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] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Michal Turek assigned JENKINS-23575 to Michal Turek Post-Build-Step Publish Cppcheck results not available in job generator project Change By: Michal Turek (19/Jul/14 10:44 AM) Assignee: GregoryBoissinot MichalTurek 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] [buildtriggerbadge] (JENKINS-22366) BuildTriggerBadge should have a dedicated icon for Gerrit Trigger
Dominik Bartholdi commented on JENKINS-22366 BuildTriggerBadge should have a dedicated icon for Gerrit Trigger thats easy, but as I don't know gerrit I need some information... the gerrit plugin seems to have quite some different types of causes (Gerrit Cause, GerritUserCause, GerritManualCause,...). can you please attach some build.xml's of the different builds you would like to have cause expressed with an icon. these builds should be from jobs having the "Build Trigger Badge Plugin" active. Actually, I'm only interessted in this section of the build.xml's: org.jenkinsci.plugins.buildtriggerbadge.BuildTriggerBadgeAction plugin="buildtriggerbadge@1.3-SNAPSHOT" cause class="hudson.model.Cause$UserIdCause" reference="../../hudson.model.CauseAction/causes/hudson.model.Cause_-UserIdCause"/ /org.jenkinsci.plugins.buildtriggerbadge.BuildTriggerBadgeAction 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] [cli] (JENKINS-18824) Build Causer doesn't resolve CLI based usernames
Dominik Bartholdi updated JENKINS-18824 Build Causer doesnt resolve CLI based usernames This has nothing to do with the "Build Trigger Badge Plugin", but with the implementaton of CLI. The CLI cause does seems not contain the correct information. - hudson.cli.BuildCommand.CLICause.getShortDescription() Change By: Dominik Bartholdi (19/Jul/14 11:03 AM) Component/s: cli Component/s: buildtriggerbadge 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] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
SCM/JIRA link daemon commented on JENKINS-23575 Post-Build-Step Publish Cppcheck results not available in job generator project Code changed in jenkins User: Michal Turek Path: pom.xml src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckPublisher.java http://jenkins-ci.org/commit/cppcheck-plugin/b1662312bb370706732e79fef75d63941a49bdee Log: JENKINS-23575 Post-Build-Step "Publish Cppcheck results" not available in job generator project isApplicable() returns true, to make Cppcheck publisher available in a whatever job type. Dependencies to maven and ivy plugins removed. 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] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
SCM/JIRA link daemon commented on JENKINS-23575 Post-Build-Step Publish Cppcheck results not available in job generator project Code changed in jenkins User: Michal Turek Path: .gitignore pom.xml src/main/java/com/thalesgroup/hudson/plugins/cppcheck/util/CppcheckUtil.java src/main/java/org/jenkinsci/plugins/cppcheck/CppcheckPublisher.java http://jenkins-ci.org/commit/cppcheck-plugin/b70bb5abc9ddccbea3ad19459f647f31fd6e77fa Log: Merge pull request #18 from mixalturek/master JENKINS-23575 Post-Build-Step "Publish Cppcheck results" not available in job generator project Compare: https://github.com/jenkinsci/cppcheck-plugin/compare/bbae9dfc10ff...b70bb5abc9dd 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] [cppcheck] (JENKINS-23575) Post-Build-Step Publish Cppcheck results not available in job generator project
Michal Turek resolved JENKINS-23575 as Fixed Post-Build-Step Publish Cppcheck results not available in job generator project Implemented, will be released in version 1.19. Change By: Michal Turek (19/Jul/14 12:07 PM) Status: InProgress Resolved Fix Version/s: current Resolution: Fixed 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] [cppcheck] (JENKINS-23247) Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin.
Michal Turek updated JENKINS-23247 Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin. Change By: Michal Turek (19/Jul/14 12:16 PM) Priority: Blocker Minor 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] [cppcheck] (JENKINS-23247) Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin.
Michal Turek commented on JENKINS-23247 Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin. I have updated the priority from "Blocker" to "Minor". If I understand correctly, everything works as expected and this is only a feature request for showing only last N builds in the trend graph. 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] [cppcheck] (JENKINS-23891) Redesign of configuration page
Michal Turek created JENKINS-23891 Redesign of configuration page Issue Type: Improvement Affects Versions: current Assignee: Michal Turek Components: cppcheck Created: 19/Jul/14 12:38 PM Description: Remove second "Advanced" button, update texts to be more understandable for new users, etc. Environment: all Project: Jenkins Priority: Major Reporter: Michal Turek 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] [cppcheck] (JENKINS-23891) Redesign of configuration page
Michal Turek started work on JENKINS-23891 Redesign of configuration page Change By: Michal Turek (19/Jul/14 12:40 PM) Status: Open InProgress 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-client] (JENKINS-23860) allow for custom flags to be passed to git
Mark Waite closed JENKINS-23860 as Wont Fix allow for custom flags to be passed to git Change By: Mark Waite (19/Jul/14 12:50 PM) Status: Resolved Closed 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-client] (JENKINS-23860) allow for custom flags to be passed to git
Mark Waite stopped work on JENKINS-23860 allow for custom flags to be passed to git Change By: Mark Waite (19/Jul/14 12:50 PM) Status: InProgress Open 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-client] (JENKINS-23860) allow for custom flags to be passed to git
Mark Waite resolved JENKINS-23860 as Wont Fix allow for custom flags to be passed to git Change By: Mark Waite (19/Jul/14 12:50 PM) Status: Open Resolved Resolution: WontFix 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-client] (JENKINS-23860) allow for custom flags to be passed to git
Mark Waite started work on JENKINS-23860 allow for custom flags to be passed to git Change By: Mark Waite (19/Jul/14 12:50 PM) Status: Open InProgress 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-23020) Manage-Cancel Shutdown requests POST method and even POST fails due to invalid crumb if CSRF protection is enabled
Jesse Glick commented on JENKINS-23020 Manage-Cancel Shutdown requests POST method and even POST fails due to invalid crumb if CSRF protection is enabled no way to cancel from shutdown mode if CSRF protection is enabled You can use the CLI command. 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-23020) Manage-Cancel Shutdown requests POST method and even POST fails due to invalid crumb if CSRF protection is enabled
Jesse Glick updated JENKINS-23020 Manage-Cancel Shutdown requests POST method and even POST fails due to invalid crumb if CSRF protection is enabled Change By: Jesse Glick (19/Jul/14 5:54 PM) Labels: regression URL: https://github.com/jenkinsci/jenkins/pull/1306 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-23884) Git/GitHub Enterprise (GHE) SCM Polling creates builds with No Changes when there are two similarly named branches present
Mark Waite resolved JENKINS-23884 as Fixed Git/GitHub Enterprise (GHE) SCM Polling creates builds with No Changes when there are two similarly named branches present Fixed in git-client-plugin 1.10.0 Change By: Mark Waite (19/Jul/14 8:41 PM) Status: Open Resolved Resolution: Fixed 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-23884) Git/GitHub Enterprise (GHE) SCM Polling creates builds with No Changes when there are two similarly named branches present
Mark Waite commented on JENKINS-23884 Git/GitHub Enterprise (GHE) SCM Polling creates builds with No Changes when there are two similarly named branches present The git-client-plugin 1.10.0 release will include a change which allows the job to specify branch names more precisely. So that we don't break compatibility with existing job definitions, the more specific branch name needs to use a different string. Plugin versions prior to 1.10.0 typically used "Branch to build" arguments like "origin/master" or "/develop". Those values had all text left of the right-most slash removed, then the remaining text was used to match branch names. That allowed multiple branches to match a single "branch to build", even if that was not the intention of the job definer. It did not allow precise specification of a single branch, especially when namespaces were used. In your example, it caused "jdoe/blah/festivus-dev" and "festivus-dev" to both match. That form of "branch to build" is still supported, but now the "Branches to build" also accepts arguments like "refs/heads/origin/master" and "refs/heads/origin//develop". The "refs/heads" format allows precise specification of the branch to build, without breaking backward compatibility. In your case, you'd specify the branch to build as "refs/heads/festivus-dev". Would you be willing to try a pre-release version of 1.10.0 to confirm it fixes your issue? 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-23266) GitSCM rebuilds all the time while using poll scm
Mark Waite edited a comment on JENKINS-23266 GitSCM rebuilds all the time while using poll scm Refer to JENKINS-23884 for a description of the change that will be included in git-client-plugin which will allow you to more precisely specify the branch to build. 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-23266) GitSCM rebuilds all the time while using poll scm
Mark Waite commented on JENKINS-23266 GitSCM rebuilds all the time while using poll scm Refer to https://issues.jenkins-ci.org/browse/JENKINS-23884?focusedCommentId=206087page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-206087 for a description of the change that will be included in git-client-plugin which will allow you to more precisely specify the branch to build. 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-23266) GitSCM rebuilds all the time while using poll scm
Mark Waite resolved JENKINS-23266 as Fixed GitSCM rebuilds all the time while using poll scm Fixed in git-client-plugin 1.10.0 Change By: Mark Waite (19/Jul/14 8:43 PM) Status: Open Resolved Resolution: Fixed 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] [p4] (JENKINS-23890) Error on build with SCM changes
dan tran updated JENKINS-23890 Error on build with SCM changes Change By: dan tran (19/Jul/14 10:34 PM) Summary: Erroron nextchanges build withSCMchanges 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.
