[JIRA] [job-restrictions-plugin] (JENKINS-26374) Upstream checks - NPE may happen if the upstream build has been deleted by logrotate operation
SCM/JIRA link daemon resolved JENKINS-26374 as Fixed Upstream checks - NPE may happen if the upstream build has been deleted by logrotate operation Change By: SCM/JIRA link daemon (16/Jan/15 7:43 AM) 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] [job-restrictions-plugin] (JENKINS-25771) Add "started by a member of group" JobRestriction
SCM/JIRA link daemon commented on JENKINS-25771 Add "started by a member of group" JobRestriction Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/AbstractUserCauseRestriction.java src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByMemberOfGroupRestriction.java src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByUserRestriction.java src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/GroupSelector.java src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/QueueHelper.java src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/UserSelector.java src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/Messages.properties src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByMemberOfGroupRestriction/config.jelly src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByMemberOfGroupRestriction/config.properties src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByUserRestriction/config.jelly src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByUserRestriction/config.properties src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/GroupSelector/config.jelly src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/GroupSelector/help-selectedGroup.html src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/UserSelector/config.jelly src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/UserSelector/help-selectedUserId.html http://jenkins-ci.org/commit/job-restrictions-plugin/676733704a43502ba60f5c36bc18cce988a548a1 Log: Merge pull request #5 from jenkinsci/JENKINS-25726 [JENKINS-25726, JENKINS-25771] - StartedByUser and StartedByMemberOfGroup restrictions Compare: https://github.com/jenkinsci/job-restrictions-plugin/compare/47b292fd4ffc...676733704a43 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] [job-restrictions-plugin] (JENKINS-26374) Upstream checks - NPE may happen if the upstream build has been deleted by logrotate operation
SCM/JIRA link daemon commented on JENKINS-26374 Upstream checks - NPE may happen if the upstream build has been deleted by logrotate operation Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/jobs/UpstreamCauseRestriction.java src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/jobs/UpstreamCauseRestriction/config.jelly src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/jobs/UpstreamCauseRestriction/config.properties src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/jobs/UpstreamCauseRestriction/help-skipCheckForMissingInfo.html http://jenkins-ci.org/commit/job-restrictions-plugin/132867751ce0c72446b82d34e440f27b366558d5 Log: Merge pull request #7 from oleg-nenashev/JENKINS-26374 [FIXED JENKINS-26374] - Avoid NPE for deleted builds in UpstreamCauseRestriction for jobs Compare: https://github.com/jenkinsci/job-restrictions-plugin/compare/676733704a43...132867751ce0 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] [job-restrictions-plugin] (JENKINS-25726) Add "started by a user" JobRestriction
SCM/JIRA link daemon commented on JENKINS-25726 Add "started by a user" JobRestriction Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByUserRestriction.java src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/QueueHelper.java src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/UserSelector.java src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartdByUserRestriction/config.jelly src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/UserSelector/config.jelly src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/UserSelector/help-selectedUserId.html http://jenkins-ci.org/commit/job-restrictions-plugin/36e0003492d701375ad1bce0a07d987d251fce5f Log: [WiP] - Non-tested draft for JENKINS-25726 Signed-off-by: Oleg Nenashev 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] [job-restrictions-plugin] (JENKINS-25726) Add "started by a user" JobRestriction
SCM/JIRA link daemon commented on JENKINS-25726 Add "started by a user" JobRestriction Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/AbstractUserCauseRestriction.java src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByMemberOfGroupRestriction.java src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByUserRestriction.java src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/GroupSelector.java src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/QueueHelper.java src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/UserSelector.java src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/Messages.properties src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByMemberOfGroupRestriction/config.jelly src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByMemberOfGroupRestriction/config.properties src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByUserRestriction/config.jelly src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByUserRestriction/config.properties src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/GroupSelector/config.jelly src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/GroupSelector/help-selectedGroup.html src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/UserSelector/config.jelly src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/UserSelector/help-selectedUserId.html http://jenkins-ci.org/commit/job-restrictions-plugin/676733704a43502ba60f5c36bc18cce988a548a1 Log: Merge pull request #5 from jenkinsci/JENKINS-25726 [JENKINS-25726, JENKINS-25771] - StartedByUser and StartedByMemberOfGroup restrictions Compare: https://github.com/jenkinsci/job-restrictions-plugin/compare/47b292fd4ffc...676733704a43 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] [job-restrictions-plugin] (JENKINS-26374) Upstream checks - NPE may happen if the upstream build has been deleted by logrotate operation
SCM/JIRA link daemon commented on JENKINS-26374 Upstream checks - NPE may happen if the upstream build has been deleted by logrotate operation Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/jobs/UpstreamCauseRestriction.java src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/jobs/UpstreamCauseRestriction/config.jelly src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/jobs/UpstreamCauseRestriction/config.properties src/main/resources/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/jobs/UpstreamCauseRestriction/help-skipCheckForMissingInfo.html http://jenkins-ci.org/commit/job-restrictions-plugin/b5c25e3e8189eada092c916103c0c347bdb9fa1f Log: [FIXED JENKINS-26374] - Avoid NPE for deleted builds in UpstreamCauseRestriction for jobs Signed-off-by: Oleg Nenashev 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] [job-restrictions-plugin] (JENKINS-26374) Upstream checks - NPE may happen if the upstream build has been deleted by logrotate operation
SCM/JIRA link daemon commented on JENKINS-26374 Upstream checks - NPE may happen if the upstream build has been deleted by logrotate operation Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByMemberOfGroupRestriction.java http://jenkins-ci.org/commit/job-restrictions-plugin/03b9d59d127f58c9d2cd3e74363c5dc54f84ea5c Log: Merge pull request #8 from csms/JENKINS-25726 JENKINS-26374 - Fallback to realm for principal groups Compare: https://github.com/jenkinsci/job-restrictions-plugin/compare/1d776d7f4d01...03b9d59d127f 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] [job-restrictions-plugin] (JENKINS-25726) Add "started by a user" JobRestriction
SCM/JIRA link daemon commented on JENKINS-25726 Add "started by a user" JobRestriction Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/restrictions/job/StartedByMemberOfGroupRestriction.java http://jenkins-ci.org/commit/job-restrictions-plugin/03b9d59d127f58c9d2cd3e74363c5dc54f84ea5c Log: Merge pull request #8 from csms/JENKINS-25726 JENKINS-26374 - Fallback to realm for principal groups Compare: https://github.com/jenkinsci/job-restrictions-plugin/compare/1d776d7f4d01...03b9d59d127f 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-plugin] (JENKINS-26456) Using cppcheck with CI with gerrit is dispirit
Roman G created JENKINS-26456 Using cppcheck with CI with gerrit is dispirit Issue Type: Improvement Assignee: Gregory Boissinot Components: cppcheck-plugin Created: 16/Jan/15 7:31 AM Description: cppcheck is oriented on linear history and provide useful feature for it: trend color highlighting for diff between current and previous checks gerrit usage mean that CI will be done on non-series commit, non-linear history and diff highlighting in gerrit case is pretty dispirit It will be very nice to have possibility to switch off diff and diff highlighting and see only cppchecks warnings from current runs Environment: jenkins 1.5x cppcheck 1.2x Project: Jenkins Priority: Minor Reporter: Roman G 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-plugin] (JENKINS-26455) Removing .p4config file during force clean
Alexey Larsky created JENKINS-26455 Removing .p4config file during force clean Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 16/Jan/15 7:12 AM Project: Jenkins Priority: Major Reporter: Alexey Larsky 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] [ownership-plugin] (JENKINS-23947) Make ownership injection default
Oleg Nenashev commented on JENKINS-23947 Make ownership injection default Hubert, could you evaluate the feature? 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] [email-ext-plugin] (JENKINS-26286) Can not use token (like WARNINGS_NEW) in pre-send script email
Alex Earl resolved JENKINS-26286 as Fixed Can not use token (like WARNINGS_NEW) in pre-send script email Added support for this for 2.40 Change By: Alex Earl (16/Jan/15 3:03 AM) 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] [email-ext-plugin] (JENKINS-26293) email-ext-plugin FILE token macro apostrophe escaping
Alex Earl resolved JENKINS-26293 as Fixed email-ext-plugin FILE token macro apostrophe escaping Will be fixed in 2.40 Change By: Alex Earl (16/Jan/15 3:02 AM) 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] [email-ext-plugin] (JENKINS-23990) Output more helpful messages for cases where emails can't or won't be sent
Alex Earl resolved JENKINS-23990 as Incomplete Output more helpful messages for cases where emails can't or won't be sent Need more information on suitable logging location. Change By: Alex Earl (16/Jan/15 3:03 AM) Status: Open Resolved Resolution: Incomplete 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] [email-ext-plugin] (JENKINS-18693) Add support for periodic spamming rather than all or nothing
Alex Earl resolved JENKINS-18693 as Incomplete Add support for periodic spamming rather than all or nothing I believe this is doable now, if not, please reopen with more information. Change By: Alex Earl (16/Jan/15 2:57 AM) Status: Open Resolved Resolution: Incomplete 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] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
Alex Earl resolved JENKINS-18567 as Fixed Add Watch button to Job summary screen Watching will be in 2.40 Change By: Alex Earl (16/Jan/15 2:56 AM) 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] [email-ext-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
Alex Earl resolved JENKINS-21861 as Fixed option to include attachment with console.txt from failed slaves Should be in 2.40 Change By: Alex Earl (16/Jan/15 2:56 AM) Status: In Progress 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] [email-ext-plugin] (JENKINS-21861) option to include attachment with console.txt from failed slaves
SCM/JIRA link daemon commented on JENKINS-21861 option to include attachment with console.txt from failed slaves Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/AttachmentUtils.java src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherMatrixTest.java src/test/java/hudson/plugins/emailext/ExtendedEmailPublisherTest.java http://jenkins-ci.org/commit/email-ext-plugin/8a47a78f5ed91c15f18e3a0cf2e2696b48514bec Log: Fix JENKINS-21861 Add check for MatrixBuild Compare: https://github.com/jenkinsci/email-ext-plugin/compare/6acb6e2e76d8...8a47a78f5ed9 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] [email-ext-plugin] (JENKINS-25926) Can't update admin email address
SCM/JIRA link daemon commented on JENKINS-25926 Can't update admin email address Code changed in jenkins User: Alex Earl Path: pom.xml src/main/java/hudson/plugins/emailext/AttachmentUtils.java src/main/java/hudson/plugins/emailext/EmailExtTemplateAction.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/java/hudson/plugins/emailext/plugins/CssInliner.java src/main/java/hudson/plugins/emailext/plugins/EmailTrigger.java src/main/java/hudson/plugins/emailext/plugins/EmailTriggerDescriptor.java src/main/java/hudson/plugins/emailext/plugins/trigger/AbstractScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/PreBuildScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/ScriptTrigger.java src/main/java/hudson/plugins/emailext/watching/EmailExtWatchAction.java src/main/java/hudson/plugins/emailext/watching/EmailExtWatchJobProperty.java src/main/resources/hudson/plugins/emailext/EmailExtTemplateAction/action.groovy src/main/resources/hudson/plugins/emailext/EmailExtTemplateAction/action.jelly src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/global.groovy src/main/resources/hudson/plugins/emailext/Messages.properties src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/help-triggers.html src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/help-triggers_ja.html src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/help-triggers_zh_TW.html src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/index.groovy src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/index.properties src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/jobMain.groovy src/main/webapp/help/globalConfig/watching.html src/test/java/hudson/plugins/emailext/EmailTypeTest.java src/test/java/hudson/plugins/emailext/plugins/CssInlinerTest.java src/test/java/hudson/plugins/emailext/plugins/content/JellyScriptContentTest.java src/test/java/hudson/plugins/emailext/plugins/content/ScriptContentChangeLogSet.java src/test/java/hudson/plugins/emailext/plugins/content/ScriptContentTest.java src/test/java/hudson/plugins/emailext/plugins/recipients/MockUtilities.java src/test/resources/recipient-provider-upgrade2.xml http://jenkins-ci.org/commit/email-ext-plugin/bb0053d79fec59f34d3014117883282d6c2239dc Log: Fix JENKINS-18567, JENKINS-25926 and JENKINS-25719 Added ability for users to watch a job. Fixup the html content coming from CssInliner Remove adminAddress field for global config 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] [email-ext-plugin] (JENKINS-25719) bad html content after upgrading to Email Extension Plugin v2.39
SCM/JIRA link daemon commented on JENKINS-25719 bad html content after upgrading to Email Extension Plugin v2.39 Code changed in jenkins User: Alex Earl Path: pom.xml src/main/java/hudson/plugins/emailext/AttachmentUtils.java src/main/java/hudson/plugins/emailext/EmailExtTemplateAction.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/java/hudson/plugins/emailext/plugins/CssInliner.java src/main/java/hudson/plugins/emailext/plugins/EmailTrigger.java src/main/java/hudson/plugins/emailext/plugins/EmailTriggerDescriptor.java src/main/java/hudson/plugins/emailext/plugins/trigger/AbstractScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/PreBuildScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/ScriptTrigger.java src/main/java/hudson/plugins/emailext/watching/EmailExtWatchAction.java src/main/java/hudson/plugins/emailext/watching/EmailExtWatchJobProperty.java src/main/resources/hudson/plugins/emailext/EmailExtTemplateAction/action.groovy src/main/resources/hudson/plugins/emailext/EmailExtTemplateAction/action.jelly src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/global.groovy src/main/resources/hudson/plugins/emailext/Messages.properties src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/help-triggers.html src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/help-triggers_ja.html src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/help-triggers_zh_TW.html src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/index.groovy src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/index.properties src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/jobMain.groovy src/main/webapp/help/globalConfig/watching.html src/test/java/hudson/plugins/emailext/EmailTypeTest.java src/test/java/hudson/plugins/emailext/plugins/CssInlinerTest.java src/test/java/hudson/plugins/emailext/plugins/content/JellyScriptContentTest.java src/test/java/hudson/plugins/emailext/plugins/content/ScriptContentChangeLogSet.java src/test/java/hudson/plugins/emailext/plugins/content/ScriptContentTest.java src/test/java/hudson/plugins/emailext/plugins/recipients/MockUtilities.java src/test/resources/recipient-provider-upgrade2.xml http://jenkins-ci.org/commit/email-ext-plugin/bb0053d79fec59f34d3014117883282d6c2239dc Log: Fix JENKINS-18567, JENKINS-25926 and JENKINS-25719 Added ability for users to watch a job. Fixup the html content coming from CssInliner Remove adminAddress field for global config 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] [email-ext-plugin] (JENKINS-18567) Add Watch button to Job summary screen
SCM/JIRA link daemon commented on JENKINS-18567 Add Watch button to Job summary screen Code changed in jenkins User: Alex Earl Path: pom.xml src/main/java/hudson/plugins/emailext/AttachmentUtils.java src/main/java/hudson/plugins/emailext/EmailExtTemplateAction.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/java/hudson/plugins/emailext/plugins/CssInliner.java src/main/java/hudson/plugins/emailext/plugins/EmailTrigger.java src/main/java/hudson/plugins/emailext/plugins/EmailTriggerDescriptor.java src/main/java/hudson/plugins/emailext/plugins/trigger/AbstractScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/PreBuildScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/ScriptTrigger.java src/main/java/hudson/plugins/emailext/watching/EmailExtWatchAction.java src/main/java/hudson/plugins/emailext/watching/EmailExtWatchJobProperty.java src/main/resources/hudson/plugins/emailext/EmailExtTemplateAction/action.groovy src/main/resources/hudson/plugins/emailext/EmailExtTemplateAction/action.jelly src/main/resources/hudson/plugins/emailext/ExtendedEmailPublisher/global.groovy src/main/resources/hudson/plugins/emailext/Messages.properties src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/help-triggers.html src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/help-triggers_ja.html src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/help-triggers_zh_TW.html src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/index.groovy src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/index.properties src/main/resources/hudson/plugins/emailext/watching/EmailExtWatchAction/jobMain.groovy src/main/webapp/help/globalConfig/watching.html src/test/java/hudson/plugins/emailext/EmailTypeTest.java src/test/java/hudson/plugins/emailext/plugins/CssInlinerTest.java src/test/java/hudson/plugins/emailext/plugins/content/JellyScriptContentTest.java src/test/java/hudson/plugins/emailext/plugins/content/ScriptContentChangeLogSet.java src/test/java/hudson/plugins/emailext/plugins/content/ScriptContentTest.java src/test/java/hudson/plugins/emailext/plugins/recipients/MockUtilities.java src/test/resources/recipient-provider-upgrade2.xml http://jenkins-ci.org/commit/email-ext-plugin/bb0053d79fec59f34d3014117883282d6c2239dc Log: Fix JENKINS-18567, JENKINS-25926 and JENKINS-25719 Added ability for users to watch a job. Fixup the html content coming from CssInliner Remove adminAddress field for global config 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-plugin] (JENKINS-26448) Cannot use git in Jenkins
Mark Waite commented on JENKINS-26448 Cannot use git in Jenkins As far as I can tell, this is not a bug of the git-client-plugin. Since you're running an older weekly build version (almost 9 months old), and not a long term support version, you might consider updating to the latest Jenkins long term support release (1.580 based currently). That will allow you to update to the most recent git plugin (2.3 series) as well, and should allow you to update to the latest version of the credentials plugin. Since you're running on Ubuntu, you can also simplify your life by using the Debian/Ubuntu package to install that long term support version. 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] [svn-tag-plugin] (JENKINS-26217) Enable support for HEAD (v2.5) Subversion plugin.
william dutton commented on JENKINS-26217 Enable support for HEAD (v2.5) Subversion plugin. Have created pull request in git to get this patch applied. https://github.com/jenkinsci/svn-tag-plugin/pull/7 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] [svn-tag-plugin] (JENKINS-26217) Enable support for HEAD (v2.5) Subversion plugin.
william dutton updated JENKINS-26217 Enable support for HEAD (v2.5) Subversion plugin. snapshot with applied patch so that you don't need to download all of the test jars to build from source. Change By: william dutton (16/Jan/15 1:58 AM) Attachment: svn-tag.hpi 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] [svn-tag-plugin] (JENKINS-26217) Enable support for HEAD (v2.5) Subversion plugin.
william dutton commented on JENKINS-26217 Enable support for HEAD (v2.5) Subversion plugin. Ran into this while building a new build box on latest ubuntu which is now using subversion 1.8 and found that this same error was occurring. 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] [sbt-plugin] (JENKINS-26454) Spaces are added after quotes
Sumit Khanna created JENKINS-26454 Spaces are added after quotes Issue Type: Bug Assignee: uzilan Components: sbt-plugin Created: 16/Jan/15 1:04 AM Description: For the sbt action I'm attempting the following: ";set target := file(\"$WORKSPACE/package/deb-upstart\"); set serverLoading in Debian := com.typesafe.sbt.packager.archetypes.ServerLoader.Upstart; debian:packageBin; set target := file(\"$WORKSPACE/package/deb-systemv\"); set serverLoading in Debian := com.typesafe.sbt.packager.archtypes.ServerLoader.SystemV; debian:packageBin; set target := file(\"$WORKSPACE/package/rpm-systemd\"); rpm:packageBin" I'm basically resetting the target directory for each package type I call for sbt-native-package plugin tasks. The trouble is that random spaces seem to be injected around the quotes. I'm guessing the sbt-plugin has some code to add some space around quotes to separate out parameters, but as you can see, the second quote isn't a closing quote. It's another opening quote that's escaped. This command runs fine from the shell I prepended with sbt (you can checkout the project: https://github.com/bigsense/BigSense) Environment: Jenkins ver. 1.596 on Ubuntu 14.04 Project: Jenkins Priority: Minor Reporter: Sumit Khanna 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] [flexible-publish-plugin] (JENKINS-26452) Flexible Publish NPE with no publishers for a conditional publisher
ikedam
commented on JENKINS-26452
Flexible Publish NPE with no publishers for a conditional publisher
This should be a problem in {ConditionalPublisher.DescriptorImpl#newInstance}.
https://github.com/jenkinsci/flexible-publish-plugin/blob/flexible-publish-0.13/src/main/java/org/jenkins_ci/plugins/flexible_publish/ConditionalPublisher.java#L278
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] [google-play-android-publisher-plugin] (JENKINS-26453) Add ability to read release notes from a file
Christopher Orr
created JENKINS-26453
Add ability to read release notes from a file
Issue Type:
Improvement
Assignee:
Christopher Orr
Components:
google-play-android-publisher-plugin
Created:
15/Jan/15 11:57 PM
Description:
A user asked in the wiki comments:
How can I upload file content in the "Recent Changes" section,
I tried ${FILE, path="releaseNotes.txt"} but no luck...
So it would be nice if we supported this syntax, which (presumably) other plugins already have the ability to do — the syntax looks similar to other token macro plugins, e.g. "Set build name", so perhaps this is already built-in somewhere.
Project:
Jenkins
Priority:
Minor
Reporter:
Christopher Orr
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] [flexible-publish-plugin] (JENKINS-19985) Flexible Publish NPE
ikedam commented on JENKINS-19985 Flexible Publish NPE Thanks for the report. That looks an issue introduced in 0.13, and generates another stracktrace reported in this issue. I created another issue in JENKINS-26452. 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] [flexible-publish-plugin] (JENKINS-26452) Flexible Publish NPE with no publishers for a conditional publisher
ikedam updated JENKINS-26452 Flexible Publish NPE with no publishers for a conditional publisher Change By: ikedam (15/Jan/15 11:42 PM) Summary: Flexible Publish NPE with no publishers for a conditional publisher Description: (Copiied from JENKINS-19985)Steps to reproduce:# Create a new freestyle project# Add the Flexible publish as a post build action.# Save the project without any actions for a conditional publishers action .# It will throw an exception, however the save happens!#* In Jenkins 1.425, the exception is recorded only in the system log.#* In Jenkins 1.580.1, the exception is displayed also on the browser.# Execute a build and it will throw the NPE.Another way you can get this NPE:# Same steps as 1, 2, 3, 4.# Restarting Jenkins throws this NPE, however the project will fail to load and show an error about project actions.I set this to Critical, as this cause jobs lost for the latter problem. 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] [flexible-publish-plugin] (JENKINS-26452) Flexible Publish NPE with no conditional
ikedam created JENKINS-26452 Flexible Publish NPE with no conditional Issue Type: Bug Assignee: ikedam Attachments: config.xml, ExceptionOnBoot.txt, ExceptionOnBuild.txt, ExceptionOnSave.txt Components: flexible-publish-plugin Created: 15/Jan/15 11:37 PM Description: (Copiied from JENKINS-19985) Steps to reproduce: Create a new freestyle project Add the Flexible publish as a post build action. Save the project without any conditional publishers. It will throw an exception, however the save happens! In Jenkins 1.425, the exception is recorded only in the system log. In Jenkins 1.580.1, the exception is displayed also on the browser. Execute a build and it will throw the NPE. Another way you can get this NPE: Same steps as 1, 2, 3, 4. Restarting Jenkins throws this NPE, however the project will fail to load and show an error about project actions. I set this to Critical, as this cause jobs lost for the latter problem. Environment: Flexible Publish 0.13 tested with Jenkins 1.425, Jenkins 1.580.1 Project: Jenkins Priority: Critical Reporter: ikedam 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] [job-dsl-plugin] (JENKINS-26451) Warn user when generated jobs are changed manually
Wisen Tanasa created JENKINS-26451 Warn user when generated jobs are changed manually Issue Type: New Feature Assignee: Wisen Tanasa Components: job-dsl-plugin Created: 15/Jan/15 11:12 PM Description: New users in Jenkins might not noticed that their manual configuration will get overridden by a seed job. A warning after a manual configuration will be helpful. Project: Jenkins Priority: Minor Reporter: Wisen Tanasa 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] [jabber-plugin] (JENKINS-26444) Support Off-the-Record (OTR) encryption in XMPP
kutzi assigned JENKINS-26444 to Unassigned Support Off-the-Record (OTR) encryption in XMPP Unlikely that I'll work on that feature anytime in the near or medium future. If you need it, you should write it yourself and create a PR. Change By: kutzi (15/Jan/15 10:51 PM) Assignee: kutzi 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] [jabber-plugin] (JENKINS-26444) Support Off-the-Record (OTR) encryption in XMPP
kutzi updated JENKINS-26444 Support Off-the-Record (OTR) encryption in XMPP Change By: kutzi (15/Jan/15 10:49 PM) Issue Type: Bug New Feature 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] [delivery-pipeline-plugin] (JENKINS-23550) Pipeline view distorted in Internet Explorer
Curt Connell commented on JENKINS-23550 Pipeline view distorted in Internet Explorer I have tested with ie10 and ie11. 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] [envinject-plugin] (JENKINS-18297) Can not set PATH environment variable on master node
Sebastian Schuberth edited a comment on JENKINS-18297 Can not set PATH environment variable on master node Still present in EnvInject 1.90, Jenkins 1.580.2. Environment variables set globally or at the node level in the standard Jenkins fields to not get propagated to jobs anymore, even if EnvInject's "Prepare jobs environment" is disabled. Also enabling "Prepare jobs environment" but disabling "Unset System Environment Variables" (which is checked by default) does not help. 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] [envinject-plugin] (JENKINS-18297) Can not set PATH environment variable on master node
Sebastian Schuberth edited a comment on JENKINS-18297 Can not set PATH environment variable on master node Still present in EnvInject 1.90, Jenkins 1.580.2. Environment variables set globally or at the node level in the standard Jenkins field to not get propagated to jobs anymore, even if EnvInject's "Prepare jobs environment" is disabled. 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] [maven-plugin] (JENKINS-26450) Equivalent to blockTriggerWhenBuilding configured on downstream side
Jesse Glick created JENKINS-26450 Equivalent to blockTriggerWhenBuilding configured on downstream side Issue Type: New Feature Assignee: Unassigned Components: maven-plugin Created: 15/Jan/15 8:32 PM Description: JENKINS-21903 (specifically 8aed1aa) added a blockTriggerWhenBuilding flag which is checked on the upstream project, regardless of the identity of the downstream project. For some use cases it is more appropriate to configure this on the downstream project, to be checked regardless of the identity of the upstream project. Project: Jenkins Labels: snapshot trigger Priority: Major Reporter: Jesse Glick 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] [delivery-pipeline-plugin] (JENKINS-23550) Pipeline view distorted in Internet Explorer
Patrik Boström commented on JENKINS-23550 Pipeline view distorted in Internet Explorer Great! Which version of IE are you using? 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] [sauce-ondemand-plugin] (JENKINS-25067) Embed Sauce OnDemand reports option doesn't exist for Publish NUnit test result report section
apgray commented on JENKINS-25067 Embed Sauce OnDemand reports option doesn't exist for Publish NUnit test result report section Thanks Ross. 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] [workflow-plugin] (JENKINS-25851) Richer return value for build step
Jesse Glick commented on JENKINS-25851 Richer return value for build step Should also be able to access build variables (for an AbstractBuild) as a Map. 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] [ownership-plugin] (JENKINS-23947) Make ownership injection default
Oleg Nenashev started work on JENKINS-23947 Make ownership injection default Change By: Oleg Nenashev (15/Jan/15 8:03 PM) Status: Open In Progress 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] [ownership-plugin] (JENKINS-23926) Job Ownership not available if VCS fails
Oleg Nenashev started work on JENKINS-23926 Job Ownership not available if VCS fails Change By: Oleg Nenashev (15/Jan/15 8:02 PM) Status: Open In Progress 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] [dashboard-view-plugin] (JENKINS-26325) Invalid test results link
Dirk Thomas edited a comment on JENKINS-26325 Invalid test results link Duplicate of https://issues.jenkins-ci.org/browse/JENKINS-23583 (I seem to be unable to mark it as a duplicate myself and close this ticekt.) 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-21605) Logging all UpstreamCause's floods Jenkins in large setups
Jesse Glick assigned JENKINS-21605 to Unassigned Logging all UpstreamCause's floods Jenkins in large setups Change By: Jesse Glick (15/Jan/15 6:47 PM) Assignee: Jesse Glick 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-21605) Logging all UpstreamCause's floods Jenkins in large setups
Jesse Glick updated JENKINS-21605 Logging all UpstreamCause's floods Jenkins in large setups Change By: Jesse Glick (15/Jan/15 6:47 PM) Labels: performance regression 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-21605) Logging all UpstreamCause's floods Jenkins in large setups
Dirk Thomas commented on JENKINS-21605 Logging all UpstreamCause's floods Jenkins in large setups On of our latest builds generated a 154 MB `log` file. The corresponding `build.xml` file is another 108 MB. The actual output of the build is only a few KB. Please see the example job yourself: http://54.183.26.131:8080/view/Manage/job/Irel_sync-packages-to-testing_saucy_i386/1/console 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] [dashboard-view-plugin] (JENKINS-26325) Invalid test results link
Dirk Thomas commented on JENKINS-26325 Invalid test results link Duplicate of https://issues.jenkins-ci.org/browse/JENKINS-23583 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] [grails-plugin] (JENKINS-22508) grails.work.dir breaks if the job has spaces in the name
Kurt Devlin commented on JENKINS-22508 grails.work.dir breaks if the job has spaces in the name JENKINS-24629 and JENKINS-22508 are the same 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] [grails-plugin] (JENKINS-24629) Incorrect quoting of environment variables
Kurt Devlin commented on JENKINS-24629 Incorrect quoting of environment variables JENKINS-24629 and JENKINS-22508 are the same 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] [grails-plugin] (JENKINS-24629) Incorrect quoting of environment variables
Kurt Devlin updated JENKINS-24629 Incorrect quoting of environment variables Raised the Priority of this. It is not cosmetic and there isn't a workaround. We are trying to use the user build parameters for additional Jenkins functionality, but were forced to remove them (as would anyone with parameters with spaces). Change By: Kurt Devlin (15/Jan/15 6:11 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] [envinject-plugin] (JENKINS-14437) envinject fails to "really" set/override build parameters
Daniel Beck commented on JENKINS-14437 envinject fails to "really" set/override build parameters Recent versions of the plugin added a switch to Prepare an environment to enable/disable overriding already defined environment variables (or something like that). Maybe that's related. The UI is a bit weird, as it affects everything envinject does in a job, not just the Prepare step, and you don't need to have anything else in there for the option to be effective. 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] [grails-plugin] (JENKINS-24629) Incorrect quoting of environment variables
Kurt Devlin updated JENKINS-24629 Incorrect quoting of environment variables Change By: Kurt Devlin (15/Jan/15 6:09 PM) Priority: Trivial 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] [grails-plugin] (JENKINS-24629) Incorrect quoting of environment variables
Kurt Devlin commented on JENKINS-24629 Incorrect quoting of environment variables I experienced this when we tried using the Build User Vars Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Build+User+Vars+Plugin) The new system properties are escaped correctly in other plugins, but the Grails plugin breaks with an incorrectly quoted BUILD_USER parameter. See a snippet of the log results below. [workspace] $ /apps/grails-2.2.3/bin/grails -DBUILD_USER_LAST_NAME=Doe -DBUILD_USER_FIRST_NAME=John "-DBUILD_USER=John Doe" -DBUILD_USER_EMAIL=john@mycompany.com -DBUILD_USER_ID=jDoe dev war myProject.war --non-interactive Loading Grails 2.2.3 Configuring classpath Running pre-compiled script Error Script not found: Doe Pulling out the Grails plugin and calling Grails directly with Execute Shell, I used the "Possible Fix" suggested in the description and it worked. Putting -DBUILD_USER=\"John Doe\" in the shell command, translated to '-DBUILD_USER="John' 'Doe"' being displayed in the output of the script and the build executed successfully. 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-26445) Browser freezes when clicking more link on a job to see other builds
Daniel Beck commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds So the issue is performance with a very large number of builds. The changes implemented in recent Jenkins make the build history display much better when build names or multiple badges are used, at the cost of additional processing. And I'm fairly sure we want to keep it, as it was pretty bad in some situations before. A possible solution would be to change how 'more' works to only reveal an additional 50-100 builds each time rather than all of them, assuming the problem is the number of newly added builds to the list, rather than their total number. I pinged Tom FENNELLY about this, who did all the recent work on the build history widget. 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-26445) Browser freezes when clicking more link on a job to see other builds
Daniel Beck commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Try ?tree=allbuilds (or allBuilds) instead. There's some performance optimization to prevent excessive loading of builds. 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] [tfs-plugin] (JENKINS-26449) Team Foundation Server Plugin: Team System Web Access repository browser links broken for TFS 2012 and 2013
Jesse Jacob
created JENKINS-26449
Team Foundation Server Plugin: Team System Web Access repository browser links broken for TFS 2012 and 2013
Issue Type:
Bug
Assignee:
redsolo
Components:
tfs-plugin
Created:
15/Jan/15 5:58 PM
Description:
When using TFS and you change the "Repository Browser" field in the Source Code Management section of a job config to "Team System Web Access", it generates links to the repository browser on the Changes screen of each job run.
The problem is that the link builder for the TFS plugin is for some specific (undocumented?) version of TFS. The plugin should either support more versions of TFS (and be capable of inferring them) or maybe add version-specific browser options.
For example, the plugin doesn't specifically support TFS 2012+, so if you select Team System Web Access and provide the TFS server url of "https://tfs.com/tfs", it drops the path anyway and generates the following links for each changeset:
https://tfs.com/cs.aspx?cs={changeset number}
and for each file link:
https://tfs.com/view.aspx?path={TFS file Path}&cs={changeset number}
and for each diff link:
https://tfs.com/diff.aspx?opath={TFS file Path}&ocs={previous change set #}&mpath={TFS file Path}&mcs={current change set #}
However, TFS 2012 and 2013 require changeset URLs in the following format:
https://tfs.com/tfs/{CollectionName}/{ProjectName}/_versionControl/changeset/{change set #}
CollectionName and ProjectName can probably be extracted from the TFS path from the job, but maybe you should allow the user to provide the entire project path and just add everything after that (/_versionControl/changeset/nnn). ProjectName can literally be any valid project in the collection, but CollectionName needs to be an exact match.
File content and compare views use an URL hash:
{changesetUrL}#path={TFS file path}&_a=contents
{changesetUrl}#path={TFS file path}&_a=compare
Maybe the plugin links are only supposed to work for codeplex or very old versions of TFS?
Environment:
Windows 7, Windows Server 2012 R2, TFS Server 2012/2013
Project:
Jenkins
Labels:
tfs
windows
repositorybrowser
Priority:
Minor
Reporter:
Jesse Jacob
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-plugin] (JENKINS-26448) Cannot use git in Jenkins
Guy Van Sanden commented on JENKINS-26448 Cannot use git in Jenkins Jenkins ver. 1.557 GIT plugin 2.2.12 GIT client plugin 1.15.0 OS: Ubuntu 14.04 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-plugin] (JENKINS-26448) Cannot use git in Jenkins
Guy Van Sanden created JENKINS-26448 Cannot use git in Jenkins Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin Created: 15/Jan/15 5:39 PM Description: I'm trying to use a git repo in a build, but it ends with a stacktrace. I believe the cause is the credentials plugin, I have entered credentials but cannot select any in the dropdown when creating a build plan. My git repo does not require credentials Stack trace: Stack trace javax.servlet.ServletException: java.lang.NoClassDefFoundError: org.jenkinsci.plugins.gitclient.GitClient at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedCha
[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta edited a comment on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds /job/JOBNAME/api/xml?tree=builds returns 100 lines. however i believe we have a lot more than that. When i do RSS of all i get about 694 items. 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-plugin] (JENKINS-25556) Deploy p4jenkins test artifact
dan tran commented on JENKINS-25556 Deploy p4jenkins test artifact Forgot to mention, it will be used by p4maven. Thanks 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] [credentials-plugin] (JENKINS-26099) Configurable ID for Credentials
Jesse Glick resolved JENKINS-26099 as Fixed Configurable ID for Credentials Changes to credentials and plain-credentials released. Changes to ssh-credentials merged, ready for release. Change By: Jesse Glick (15/Jan/15 5:19 PM) Status: In Progress 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] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds /job/JOBNAME/api/xml?tree=builds returns 100 lines. 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] [role-strategy-plugin] (JENKINS-19934) Add "Job Create" permission to project roles
mwebber commented on JENKINS-19934 Add "Job Create" permission to project roles Actually, the job should be created, but the user has no permission to access it, as it does not match the name pattern. This seems to be a limitation inherent in how Role Strategy works. You are probably correct. I guess the problem here is in the Role Strategy UI - on my Jenkins, there are 19 different privileges that can be selected for a "role". "Role"s have a jobname pattern associated with them, and 1 of those 19 privileges, "Job/Create", it does not behave like the others, without any visual clue. > A friendlier error message would be nice, as well. May be possible if you give the user the Discover permission globally. Otherwise, Jenkins will simply deny there is such a job, as the user is not allowed to see it, and not allowed to learn of its existence. I tested this. With global Discover permission added, the user then gets a more sensible message: Access Denied Please login to access job dummy-job The message is not completely sensible, of course: the users is already logged in! The user then reported that the tabbed views at the top of the Jenkins page had disappaeared! This was shown to me. REMOVING the global "Discover" permission restored the view tabs. I cannot imagine what would cause that, I'm half doubting the evidence of my eyes, but it seemed to be as reported. 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-26445) Browser freezes when clicking more link on a job to see other builds
Daniel Beck commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds /job/JOBNAME/api/xml?xpath=count%28*/build%29, but you may need to install the Secure Requester Whitelist Plugin to allow this XPath request. Alternatively, /job/JOBNAME/api/xml?tree=builds and count the number of elements (lines, basically) in the returned 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 -- 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] [subversion-plugin] (JENKINS-26443) Checkout to root directory deletes ALL files in the directory
Daniel Beck commented on JENKINS-26443 Checkout to root directory deletes ALL files in the directory Please provide a sample job configuration and relevant build log excerpts. 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds The job config allows 2k but i don't know how many exist right now. Is there a WS call that can return the current total? 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-26445) Browser freezes when clicking more link on a job to see other builds
Daniel Beck updated JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Change By: Daniel Beck (15/Jan/15 4:54 PM) Labels: _javascript_ user-experience 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-26445) Browser freezes when clicking more link on a job to see other builds
Daniel Beck commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds How many builds does the job have in total? 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] [credentials-plugin] (JENKINS-24631) Credentials store API cannot browse into domains
Johannes Wienke commented on JENKINS-24631 Credentials store API cannot browse into domains Any progress on this? We desperately need this. Or is there any way to access the required attributes with the tree parameter? 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] [ssh-plugin] (JENKINS-26447) Remote shell script should be killed when build is aborted
Eric Citaire created JENKINS-26447 Remote shell script should be killed when build is aborted Issue Type: Bug Assignee: Unassigned Components: ssh-plugin Created: 15/Jan/15 4:51 PM Description: When the build is aborted, the remote shell should be killed or gracefully stopped. Project: Jenkins Priority: Minor Reporter: Eric Citaire 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] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Thierry-Dimitri Roy edited a comment on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I can reproduce the problem rather easily. We run our tests continuously and we get connection error one fifth of the time. OS the Jenkins build is running on: Mac OS X 10.8.5 Logs: 02:27:47 [android] Using Android SDK: /android/sdk/ 02:27:47 [android] Creating Android AVD: /Users/jenkins/workspace/replica_dev_stable/.android/avd/hudson_fr-CA_160_WXGA800_android-17_x86.avd 02:27:47 [android] /android/sdk//tools/android create avd -f -a -c 1024M -s WXGA800 -n hudson_fr-CA_160_WXGA800_android-17_x86 -t android-17 --abi x86 02:28:06 [android] Setting hardware properties: 02:28:06 hw.gpu.enabled: yes 02:28:06 hw.ramSize: 1907M 02:28:06 vm.heapSize: 128 02:28:06 hw.lcd.density: 160 02:28:06 hw.dPad: yes 02:28:06 hw.mainKeys: yes 02:28:06 skin.dynamic: no 02:28:06 skin.name: 1280x800 02:28:06 skin.path: 1280x800 02:28:06 $ /android/sdk//platform-tools/adb start-server 02:28:09 * daemon not running. starting it now on port 5632 * 02:28:09 * daemon started successfully * 02:28:09 $ /android/sdk//platform-tools/adb start-server 02:28:09 [android] Starting Android emulator 02:28:09 $ /android/sdk//tools/emulator64-x86 -no-boot-anim -ports 5630,5631 -prop persist.sys.language=fr -prop persist.sys.country=CA -avd hudson_fr-CA_160_WXGA800_android-17_x86 -no-snapshot-load -no-snapshot-save -wipe-data 02:28:14 HAX is working and emulator runs in fast virt mode 02:28:15 emulator: emulator window was out of view and was recentered ... 02:39:23 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:39:23 error: device not found 02:39:37 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:39:37 error: device not found 02:39:50 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:39:50 error: device not found 02:40:04 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:40:04 error: device not found 02:40:18 [android] Timed-out after waiting 720 seconds for emulator 02:40:18 [android] Stopping Android emulator 02:40:18 $ /android/sdk//platform-tools/adb kill-server — Any suggestion? I'm more than willing to help you. ... — [UPDATE] Here's a log with a connection that worked: 06:11:12 $ /android/sdk//tools/android list target 06:11:24 [android] Using Android SDK: /android/sdk/ 06:11:24 [android] Creating Android AVD: /Users/jenkins/workspace/replica_dev_stable/.android/avd/hudson_fr-CA_160_WXGA800_android-17_x86.avd 06:11:24 [android] /android/sdk//tools/android create avd -f -a -c 1024M -s WXGA800 -n hudson_fr-CA_160_WXGA800_android-17_x86 -t android-17 --abi x86 06:11:44 [android] Setting hardware properties: 06:11:44 hw.gpu.enabled: yes 06:11:44 hw.ramSize: 1907M 06:11:44 vm.heapSize: 128 06:11:44 hw.lcd.density: 160 06:11:44 hw.dPad: yes 06:11:44 hw.mainKeys: yes 06:11:44 skin.dynamic: no 06:11:44 skin.name: 1280x800 06:11:44 skin.path: 1280x800 06:11:44 $ /android/sdk//platform-tools/adb start-server 06:11:47 * daemon not running. starting it now on port 5749 * 06:11:47 * daemon started successfully * 06:11:47 $ /android/sdk//platform-tools/adb start-server 06:11:47 [android] Starting Android emulator 06:11:47 $ /android/sdk//tools/emulator64-x86 -no-boot-anim -ports 5747,5748 -prop persist.sys.language=fr -prop persist.sys.country=CA -avd hudson_fr-CA_160_WXGA800_android-17_x86 -no-snapshot-load -no-snapshot-save -wipe-data 06:11:53 HAX is working and emulator runs in fast virt mode 06:11:54 emulator: emulator window was out of view and was recentered 06:11:54 06:11:55 $ /android/sdk//platform-tools/adb connect emulator-5747 06:11:55 [android] Waiting for emulator to finish booting... 06:11:55 $ /android/sdk//platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete 06:11:55 error: device offline 06:12:09 $ /android/sdk//platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete 06:12:09 error: device offline 06:12:22 $ /android/sdk//platform-tools/adb -s emulator-5747 shell getprop dev.bootcomplete 06:12:22 $ /android/sdk//platform-tools/adb -s emulator-5747 logcat -v time 06:12:22 [android] Emulator is ready for use (took 35 seconds) This message is automatica
[JIRA] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Thierry-Dimitri Roy commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I can reproduce the problem rather easily. We run our tests continuously and we get connection error one fifth of the time. OS the Jenkins build is running on: Mac OS X 10.8.5 Logs: 02:27:47 [android] Using Android SDK: /android/sdk/ 02:27:47 [android] Creating Android AVD: /Users/jenkins/workspace/replica_dev_stable/.android/avd/hudson_fr-CA_160_WXGA800_android-17_x86.avd 02:27:47 [android] /android/sdk//tools/android create avd -f -a -c 1024M -s WXGA800 -n hudson_fr-CA_160_WXGA800_android-17_x86 -t android-17 --abi x86 02:28:06 [android] Setting hardware properties: 02:28:06 hw.gpu.enabled: yes 02:28:06 hw.ramSize: 1907M 02:28:06 vm.heapSize: 128 02:28:06 hw.lcd.density: 160 02:28:06 hw.dPad: yes 02:28:06 hw.mainKeys: yes 02:28:06 skin.dynamic: no 02:28:06 skin.name: 1280x800 02:28:06 skin.path: 1280x800 02:28:06 $ /android/sdk//platform-tools/adb start-server 02:28:09 * daemon not running. starting it now on port 5632 * 02:28:09 * daemon started successfully * 02:28:09 $ /android/sdk//platform-tools/adb start-server 02:28:09 [android] Starting Android emulator 02:28:09 $ /android/sdk//tools/emulator64-x86 -no-boot-anim -ports 5630,5631 -prop persist.sys.language=fr -prop persist.sys.country=CA -avd hudson_fr-CA_160_WXGA800_android-17_x86 -no-snapshot-load -no-snapshot-save -wipe-data 02:28:14 HAX is working and emulator runs in fast virt mode 02:28:15 emulator: emulator window was out of view and was recentered ... 02:39:23 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:39:23 error: device not found 02:39:37 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:39:37 error: device not found 02:39:50 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:39:50 error: device not found 02:40:04 $ /android/sdk//platform-tools/adb -s emulator-5630 shell getprop dev.bootcomplete 02:40:04 error: device not found 02:40:18 [android] Timed-out after waiting 720 seconds for emulator 02:40:18 [android] Stopping Android emulator 02:40:18 $ /android/sdk//platform-tools/adb kill-server — Any suggestion? I'm more than willing to help you. ... 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-plugin] (JENKINS-25556) Deploy p4jenkins test artifact
Paul Allen closed JENKINS-25556 as Fixed Deploy p4jenkins test artifact Change By: Paul Allen (15/Jan/15 4:21 PM) Status: Open Closed 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-plugin] (JENKINS-25968) False positive changes trigger builds
Paul Allen closed JENKINS-25968 as Fixed False positive changes trigger builds Change By: Paul Allen (15/Jan/15 4:20 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] [p4-plugin] (JENKINS-25968) False positive changes trigger builds
Paul Allen resolved JENKINS-25968 as Fixed False positive changes trigger builds Fixed Polling for Slaves in 1.1.2 Change By: Paul Allen (15/Jan/15 4:19 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-plugin] (JENKINS-25682) Using Credentials as attributes shows all perforce credentials with same description
Paul Allen closed JENKINS-25682 as Fixed Using Credentials as attributes shows all perforce credentials with same description Change By: Paul Allen (15/Jan/15 4:18 PM) Status: Reopened Closed 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-plugin] (JENKINS-26418) perforce software plugin returns "Unable to update workspace" when in multiconfig project
Paul Allen
commented on JENKINS-26418
perforce software plugin returns "Unable to update workspace" when in multiconfig project
Do you use unique Perforce (client) workspaces for each configuration?
In most cases using '${JOB_NAME}' for the 'Workspace name' field is unique.
Please can you try version 1.1.2 and provide the full console log.
Thanks,
Paul
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] [credentials-plugin] (JENKINS-26099) Configurable ID for Credentials
SCM/JIRA link daemon commented on JENKINS-26099 Configurable ID for Credentials Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsProvider.java src/main/java/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials.java src/main/java/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl.java src/main/java/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl.java src/main/resources/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials/help-description.html src/main/resources/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials/help-description_ja.html src/main/resources/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials/help-id.html src/main/resources/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials/id-and-description.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials/id-and-description_de.properties src/main/resources/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials/id-and-description_ja.properties src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/credentials.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/credentials_de.properties src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/credentials_ja.properties src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/help-description.html src/main/resources/com/cloudbees/plugins/credentials/impl/CertificateCredentialsImpl/help-description_ja.html src/main/resources/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl/credentials.jelly src/main/resources/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl/credentials_de.properties src/main/resources/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl/credentials_ja.properties src/main/resources/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl/help-description.html src/main/resources/com/cloudbees/plugins/credentials/impl/UsernamePasswordCredentialsImpl/help-description_ja.html src/test/java/com/cloudbees/plugins/credentials/MockFolderCredentialsProvider.java src/test/java/com/cloudbees/plugins/credentials/impl/BaseStandardCredentialsTest.java http://jenkins-ci.org/commit/credentials-plugin/f2639a47ab25274069c6d1fc7ee10e1817724f95 Log: Merge pull request #21 from jenkinsci/config-id-JENKINS-26099 [FIXED JENKINS-26099] Pick an ID for credentials Compare: https://github.com/jenkinsci/credentials-plugin/compare/fc7055dd1795...f2639a47ab25 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-plugin] (JENKINS-26373) Cannot checkout using change list
Paul Allen commented on JENKINS-26373 Cannot checkout using change list Interesting feature; please will you provide me with some details on a typical use-case? If you rely on any other Jenkins plugins as part of the use-case let me know. 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-plugin] (JENKINS-26373) Cannot checkout using change list
Paul Allen updated JENKINS-26373 Cannot checkout using change list Change By: Paul Allen (15/Jan/15 4:06 PM) Issue Type: Bug New Feature 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] [global-variable-string-parameter-plugin] (JENKINS-26446) Global environment variables not resolving when referenced at the beginning of any configuration line
Shubham Sakhuja created JENKINS-26446 Global environment variables not resolving when referenced at the beginning of any configuration line Issue Type: Bug Assignee: Unassigned Attachments: console_output.png, global_env_variables.png, project_config.png Components: global-variable-string-parameter-plugin Created: 15/Jan/15 3:52 PM Description: Global environment variables resolve fine for the most part, unless they are referenced at the beginning of the first line of a configuration. I have included screenshots that show an example of this. Note that only the first variable is not resolved, however the remaining are. This is for a multi-configuration project. This may be related to JENKINS-13277 since I have the same issue when trying to reference a variable in the mail recipient list using the same mailer plugin. Project: Jenkins Priority: Major Reporter: Shubham Sakhuja 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-26411) Improve error reporting when channel closed
Jesse Glick updated JENKINS-26411 Improve error reporting when channel closed Change By: Jesse Glick (15/Jan/15 3:47 PM) Labels: remoting robustness user-experience 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] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb Though as ever, I can only rarely reproduce these issues, which makes testing ever-so-slightly difficult. Maybe I need to try it on a Mac or Windows? For anybody who has this issue, it would be nice to know what config is being used: OS the Jenkins build is running on Emulator config: API level screen resolution target ABI emulator options emulator executable 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] [envinject-plugin] (JENKINS-14437) envinject fails to "really" set/override build parameters
Kyle Leinen commented on JENKINS-14437 envinject fails to "really" set/override build parameters We are also experiencing this on multiple systems. Jenkins: 1.593 EnvInject: 1.90 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] [workflow-plugin] (JENKINS-26185) Reusing workspaces between stages and nodes
Jesse Glick commented on JENKINS-26185 Reusing workspaces between stages and nodes Not sure why you were using step when you could be using the specialized archive step, but either should work the same, just a matter of style. It sounds like there are two issues here. First of all, ArtifactUnarchiverStepExecution.copy does not appear to handle symlinks as written. This should be filed as a separate bug, especially if you can find a quick way to reproduce on a minimal test case. I suspect the best that can be done against current Jenkins core versions is to skip over symlinks (emitting a warning from the step); VirtualFile can be asked isFile, which I think would be false for a symlink (even if its target was an existing file), but it would require a core API change for it to report the target of the symlink. Second, as you say the whole agent/dist/ subdirectory should never have been archived to begin with. I suspect something wrong with your include/exclude patterns, which ought to be reproducible in a freestyle project with the same workspace contents and an archiving post-build action. Try exclude: 'agent/dist/' rather than exclude: 'agent/dist/**/*'; they may seem synonymous but the behavior (implemented in Ant) might be different where symlinks are concerned. (agent/dist/ is merely shorthand for agent/dist/**, meaning “anything starting with agent/dist/, so prune at agent/dist”. agent/dist/**/* means “look through all subdirectories of agent/dist and match all individual files you find in them”.) Also rather than unarchive mapping: ['**/*': '.'] I would use unarchive mapping: ['desiredFileOrDir': '.'] (known to work) or unarchive mapping: ['*': '.'] (might work) to see if that makes any difference. Mapping '**/*': '.' is probably wrong here, since this would mean to copy all files at whatever directory depth into the root of the workspace (“flattening”). 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] [android-emulator-plugin] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb
Christopher Orr commented on JENKINS-11952 Emulator occasionally hangs indefinitely on startup, unable to connect adb I was just prompted to look at the connection code again and noticed that — contrary to what I wrote in my commit just above — we're not actually using the same port range that the emulator listens on and that adb checks for emulator-* instances. From double-checking the qemu and adb source, the port range should be 5554 to 5681 (the number of concurrent emulators was increased (though not 100% consistently throughout the code) from 16 to 64 a while ago). I wonder whether using this port range would help fix the adb amnesia problem where it somehow forgets devices (i.e. changes from "device offline" to "device not found". Perhaps if we use the "blessed" port range, adb will automatically re-connnect? 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds I have tried various browsers Firefox, Chrome, Safari and the client is running Max 10.10.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 -- 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta created JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Issue Type: Bug Assignee: Unassigned Components: core Created: 15/Jan/15 3:19 PM Description: When we click more link on a job to see other builds the browser freezes and prompts saying _javascript_ is taking too long to execute. I started seeing after upgrading to 1.595 unfortunately i cannot recall what version i was on before. We see a similar issue when we go to a job that has a lot of jobs in the pending queue. We are not able to scroll on the screen. Environment: CentOS 6, Jenkins v 1.595 Project: Jenkins Priority: Critical Reporter: Arpit Gupta 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds This is one of the warnings we get from browser A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue. Script: http://IP:8080/static/e7000966/scripts/hudson-behavior.js:1965 and A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue. Script: http://IP:8080/static/e7000966/scripts/prototype.js:2371 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-25657) JUnit crashes during recording of test results in 1.580.1
Krzysztof Malinowski commented on JENKINS-25657 JUnit crashes during recording of test results in 1.580.1 Yes, it occurs still with 1.596 with matrix projects. JUnit in bundled version (1.2-beta-4), xUnit 1.93. Didn't occur with JUnit 1.1, but it's incompatible with current core. We don't have plain JUnit results, we use xUnit XSLT transform to parse results and JUnit plugin to get aggregation on Matrix parent level. 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] [google-login-plugin] (JENKINS-26279) google login plugin just shows a alert message on top asking username password
recampbell resolved JENKINS-26279 as Not A Defect google login plugin just shows a alert message on top asking username password This looks like a prompt for http basic authentication, perhaps from some kind of proxy. I'm closing this as as it doesn't seem to be related to the google-login plugin. If you still feel like this is a bug in the google-login plugin, please provide the output from 'curl -v ' to help us understand the issue. Change By: recampbell (15/Jan/15 3:10 PM) Status: Open Resolved Resolution: Not A Defect 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] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Reky Silva edited a comment on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap I have encountered a similar problem in our environment, where we have a main jenkins server (called 'master' or 'build') and a slave (called 'build2'). We realise that the exception described above (Caused by: java.lang.IllegalAccessError: class com.google.common.collect.AbstractMapBasedMultimap cannot access its superclass com.google.common.collect.AbstractMultimap) is only thrown when the job runs on build2. build2 was replaced recently which made us compare the versions of maven installed. The conclusion was that master and build2 have different versions of maven: 3.0.4 and 3.0.5 respectively. Not sure if coincidence or not, but the guava libraries under maven repo ($MAVEN_HOME/lib, where MAVEN_HOME=/ush/share/maven) for each build server had different versions: master: build:/usr/share/java$ ls /usr/share/java/gua* /usr/share/java/guava.jar -> guava-r09.jar /usr/share/java/guava-r09.jar build2: build2:/usr/share/java$ ls guava* guava.jar guava-15.0.jar -> guava.jar and that was the reason why the job on build2 (checkstyle and pmd) throws an exception; build2 is a slave of master; In order to run a job on build2, a slave.jar is downloaded from master (https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds) but the maven repo used is the one on build2. That slave.jar expects that the guava library available in the maven repo to be r09 (like master). Because it is not, this exception is being thrown. To fix this issue, I have copied the guava.jar from master to build2: build2:/usr/share/java$ ls guava* guava.jar guava-r09.0.jar -> guava.jar And now the job runs seamlessly for both master and build2 (without the need to create a freestyle job)!! System info: Jenkins 1.546 Maven Integration plugin 2.1 PMD plugin 3.37 checkstyle plugin 3.38 Static Analysis Utilities 1.65 FindBugs-jsr305 Hope this explanation helps. 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] [maven-plugin] (JENKINS-22252) Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap
Reky Silva commented on JENKINS-22252 Maven 3.2.1: IllegalAccessError on AbstractMapBasedMultimap I have encountered a similar problem in our environment, where we have a main jenkins server (called 'master' or 'build') and a slave (called 'build2'). We realise that the exception described above (Caused by: java.lang.IllegalAccessError: class com.google.common.collect.AbstractMapBasedMultimap cannot access its superclass com.google.common.collect.AbstractMultimap) is only thrown when the job runs on build2. build2 was replaced recently which made us compare the versions of maven installed. The conclusion was that master and build2 have different versions of maven: 3.0.4 and 3.0.5 respectively. Not sure if coincidence or not, but the guava libraries under each build server had different versions: master: build:/usr/share/java$ ls /usr/share/java/gua* /usr/share/java/guava.jar -> guava-r09.jar /usr/share/java/guava-r09.jar build2: build2:/usr/share/java$ ls guava* guava.jar guava-15.0.jar -> guava.jar and that was the reason why the job on build2 (checkstyle and pmd) throws an exception; build2 is a slave of master; In order to run a job on build2, a slave.jar is downloaded from master (https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds) but the maven repo used is the one on build2. That slave.jar expects that the guava library available in the maven repo to be r09 (like master). Because it is not, this exception is being thrown. To fix this issue, I have copied the guava.jar from master to build2: build2:/usr/share/java$ ls guava* guava.jar guava-r09.0.jar -> guava.jar And now the job runs seamlessly for both master and build2 (without the need to create a freestyle job)!! System info: Jenkins 1.546 Maven Integration plugin 2.1 PMD plugin 3.37 checkstyle plugin 3.38 Static Analysis Utilities 1.65 FindBugs-jsr305 Hope this explanation helps. 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] [jabber-plugin] (JENKINS-26444) Support Off-the-Record (OTR) encryption in XMPP
Robert Buchholz created JENKINS-26444 Support Off-the-Record (OTR) encryption in XMPP Issue Type: Bug Assignee: kutzi Components: jabber-plugin Created: 15/Jan/15 2:46 PM Description: Currently, the Jabber plugin notifies recipients without employing end to end encryption. It should allow to create a key and ideally to pin a set of keys for the recipients to avoid MITM attacks. Project: Jenkins Priority: Minor Reporter: Robert Buchholz 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] [workflow-plugin] (JENKINS-26185) Reusing workspaces between stages and nodes
Nikita Salnikov-Tarnovski commented on JENKINS-26185 Reusing workspaces between stages and nodes Jesse, I still have problems with this. Current problem is that I try to archive the whole workspace with some excludes: step([$class: 'ArtifactArchiver', artifacts: '**/*', exclude: 'agent/dist/**/*']) And then unarchive it on another node: unarchive mapping: ['**/*': '.'] And this fails with: java.io.FileNotFoundException: /var/lib/jenkins/jobs/DashboardWorkflow/builds/2015-01-15_15-34-25/archive/agent/dist/plumbr/lib/mac/32/libplumbr.dylib (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.(FileInputStream.java:146) at jenkins.util.VirtualFile$FileVF.open(VirtualFile.java:264) at org.jenkinsci.plugins.workflow.steps.ArtifactUnarchiverStepExecution.copy(ArtifactUnarchiverStepExecution.java:67) at org.jenkinsci.plugins.workflow.steps.ArtifactUnarchiverStepExecution.run(ArtifactUnarchiverStepExecution.java:58) at org.jenkinsci.plugins.workflow.steps.ArtifactUnarchiverStepExecution.run(ArtifactUnarchiverStepExecution.java:21) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start(AbstractSynchronousStepExecution.java:34) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:137) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:98) libplumbr.dylib file is a symlink, if this makes any difference. But it should be excluded anyway. What am I doing wrong? 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] [subversion-plugin] (JENKINS-26443) Checkout to root directory deletes ALL files in the directory
Dave Taddei created JENKINS-26443 Checkout to root directory deletes ALL files in the directory Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 15/Jan/15 2:13 PM Description: When this plugin does a checkout (and on some occasions an update) it first deletes all files and folders in the checkout directory. The delete operation includes files and folders which are unrelated to the svn checkout. This causes problems when checking out SonarQube scripts and when using local maven repositories in the workspace. Some maven tasks also require the checkout directory to be the same as the build location. Environment: Jenkins 1.596, subversion-plugin 2.4.5 Project: Jenkins Priority: Major Reporter: Dave Taddei 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-26442) Localize menu hiddes buttons on configure page
Daniel Beck resolved JENKINS-26442 as Duplicate Localize menu hiddes buttons on configure page Change By: Daniel Beck (15/Jan/15 2:01 PM) Status: Open Resolved Resolution: Duplicate 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] [envinject-plugin] (JENKINS-18297) Can not set PATH environment variable on master node
Sebastian Schuberth commented on JENKINS-18297 Can not set PATH environment variable on master node Still present in EnvInject 1.90, Jenkins 1.580.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] [core] (JENKINS-26442) Localize menu hiddes buttons on configure page
Nicolai Ødum created JENKINS-26442 Localize menu hiddes buttons on configure page Issue Type: Bug Assignee: Unassigned Attachments: Screenshot.png Components: core Created: 15/Jan/15 1:50 PM Description: After upgrading from 1.594 to 1.596 I have problems seeing the buttons on the bottom of all configure screens I have tried both firefox and Chrome browsers Environment: Ubuntu 14.10 Google Chrome Version 39.0.2171.95 (64-bit) Firefox 34.0 Jenkins 1.596 Project: Jenkins Priority: Minor Reporter: Nicolai Ødum 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.
