[JIRA] [claim-plugin] (JENKINS-28722) Integrate the Build Failure Analyzer plugin with Claim plugin
Title: Message Title Scott Hebert updated an issue Jenkins / JENKINS-28722 Integrate the Build Failure Analyzer plugin with Claim plugin Change By: Scott Hebert *Given*afailedbuild* When And *theBuildFailureAnalyzerpluginisinstalledontheJenkinsinstance* And When *ausernavigatestothe failed build*And*theuserclaimsthebuild*Then*theuserispresentedwiththedefinedFailureCausesintheBFAKnowledgeBase*And*aFailureCausecanbeselected*And*theIndicationisstoredbyBFA Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-failure-analyzer-plugin] (JENKINS-28721) Ability for a user to mark a build with a failure cause AFTER a build is completed
Title: Message Title Scott Hebert created an issue Jenkins / JENKINS-28721 Ability for a user to mark a build with a failure cause AFTER a build is completed Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 03/Jun/15 3:26 PM Priority: Minor Reporter: Scott Hebert Given a build which has failed for an obscure reason which CANNOT be determined by a build log message. When a user navigates to the build Then the user can choose to mark the build with a known Failure Cause from the Knowledge Base And the indication is stored to the configured BFA storage type. Add Comment
[JIRA] [claim-plugin] (JENKINS-28722) Integrate the Build Failure Analyzer plugin with Claim plugin
Title: Message Title Scott Hebert created an issue Jenkins / JENKINS-28722 Integrate the Build Failure Analyzer plugin with Claim plugin Issue Type: New Feature Assignee: Christian Bremer Components: claim-plugin Created: 03/Jun/15 3:28 PM Priority: Minor Reporter: Scott Hebert Given a failed build When the Build Failure Analyzer plugin is installed on the Jenkins instance And a user navigates to the build And the user claims the build Then the user is presented with the defined Failure Causes in the BFA KnowledgeBase And a Failure Cause can be selected And the Indication is stored by BFA Add Comment
[JIRA] [artifactdeployer-plugin] (JENKINS-28622) Artifact Deployer stores deployed artifact list in Build Object causing memory bloat
Title: Message Title Scott Hebert created an issue Jenkins / JENKINS-28622 Artifact Deployer stores deployed artifact list in Build Object causing memory bloat Issue Type: Bug Assignee: Gregory Boissinot Components: artifactdeployer-plugin Created: 28/May/15 12:59 PM Environment: v0.33 and below. Priority: Critical Reporter: Scott Hebert Artifact Deployer stores deployed artifact list in Build Object causing memory bloat. On Jenkins instances with many jobs with many builds which deploys thousands of small files, this results in extraordinary heap usage. A fix would be make the list available just in time or on-demand. Please see a related fix for the Valgrind plugin - https://issues.jenkins-ci.org/browse/JENKINS-18950
[JIRA] [artifactdeployer-plugin] (JENKINS-28622) Artifact Deployer stores deployed artifact list in Build Object causing memory bloat
Title: Message Title Scott Hebert commented on JENKINS-28622 Re: Artifact Deployer stores deployed artifact list in Build Object causing memory bloat I created a workaround script. It can be found here: https://wiki.jenkins-ci.org/display/JENKINS/Remove+Deployed+Artifacts+Actions Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gerrit-plugin] (JENKINS-28583) Pre 2.14 gerrit-trigger.xml files cannot be loaded with 2.14+
Title: Message Title Scott Hebert started work on JENKINS-28583 Change By: Scott Hebert Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [gerrit-plugin] (JENKINS-28583) Pre 2.14 gerrit-trigger.xml files cannot be loaded with 2.14+
Title: Message Title Scott Hebert created an issue Jenkins / JENKINS-28583 Pre 2.14 gerrit-trigger.xml files cannot be loaded with 2.14+ Issue Type: Bug Assignee: Scott Hebert Components: gerrit-plugin, gerrit-trigger-plugin Created: 26/May/15 6:49 PM Priority: Blocker Reporter: Scott Hebert When a pre 2.14 gerrit-trigger.xml configuration is loaded, the gerrit-trigger plugin fails to load due to a null pointer exception. INFO: Starting Gerrit-Trigger Plugin May 26, 2015 1:10:27 PM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading plugin gerrit-trigger java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:394) at hudson.PluginManager$2$1$1.run(PluginManager.java:357) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:905) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Unable to read /home/escoheb/jenkins_home_gt/gerrit-trigger.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at hudson.Plugin.load(Plugin.java:241) at com.sonyericsson.hudson.plugins.gerrit.trigger.PluginImpl.load(PluginImpl.java:494) at com.sonyericsson.hudson.plugins.gerrit.trigger.PluginImpl.start(PluginImpl.java:475) at
[JIRA] [gerrit-trigger-plugin] (JENKINS-23871) Play-back Gerrit events which happened during a Jenkins downtime
Title: Message Title Scott Hebert resolved as Fixed Will be released as part of 2.14 Jenkins / JENKINS-23871 Play-back Gerrit events which happened during a Jenkins downtime Change By: Scott Hebert Status: InProgress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [acceptance-test-harness] (JENKINS-23326) LocalController does not inherit http proxy settings specified on command line
Title: Message Title Scott Hebert resolved as Duplicate Jenkins / JENKINS-23326 LocalController does not inherit http proxy settings specified on command line Change By: Scott Hebert Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-19022) GIT Plugin (any version) heavily bloats memory use and size of build.xml with BuildData fields
Scott Hebert commented on JENKINS-19022 GIT Plugin (any version) heavily bloats memory use and size of build.xml with BuildData fields Hi, I have updated http://scriptlerweb.appspot.com/script/show/326001 to support Matrix Project types. Thanks Scott 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] [gerrit-trigger] (JENKINS-25047) Draft Published and ChangeMerged events not handled correctly when using replication to slaves
Scott Hebert updated JENKINS-25047 Draft Published and ChangeMerged events not handled correctly when using replication to slaves Change By: Scott Hebert (09/Oct/14 7:04 PM) Summary: DraftPublished event andChangeMergedevents nothandledcorrectlywhenusingreplicationtoslaves Description: TheDraftPublishedeventismarkedwiththeRepositoryModifiedEventinterfacethereforeGerritTriggerwillattempttowaitforareplicationeventfromGerrit.Itwillnevercomesothejobwilleventuallytimeout. TheChangeMergedeventisNOTmarkedwiththeRepositoryModifiedEventinterfacethereforeGerritTriggerwillnotattempttowaitforareplicationeventfromGerritwhileitshould. 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] [gerrit-trigger] (JENKINS-25047) Draft Published event not handled correctly when using replication to slaves
Scott Hebert created JENKINS-25047 Draft Published event not handled correctly when using replication to slaves Issue Type: Bug Assignee: Scott Hebert Components: gerrit-trigger Created: 08/Oct/14 2:35 PM Description: The Draft Published event is marked with the RepositoryModifiedEvent interface therefore Gerrit Trigger will attempt to wait for a replication event from Gerrit. It will never come so the job will eventually timeout. Project: Jenkins Labels: gerrit-trigger Priority: Critical Reporter: Scott Hebert 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] [rebuild] (JENKINS-24491) Regression: parameters not retrieved when rebuilding a gitlab-merge-request-builder triggered job
Scott Hebert assigned JENKINS-24491 to Scott Hebert Regression: parameters not retrieved when rebuilding a gitlab-merge-request-builder triggered job Change By: Scott Hebert (01/Oct/14 7:13 PM) Assignee: ragesh_nair ScottHebert 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] [rebuild] (JENKINS-24491) Regression: parameters not retrieved when rebuilding a gitlab-merge-request-builder triggered job
Scott Hebert started work on JENKINS-24491 Regression: parameters not retrieved when rebuilding a gitlab-merge-request-builder triggered job Change By: Scott Hebert (01/Oct/14 7:13 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rebuild] (JENKINS-24468) Rebuild should offer parameters not currently defined on the job
Scott Hebert commented on JENKINS-24468 Rebuild should offer parameters not currently defined on the job Please note that I have attempted to fix the related issue JENKINS-24491 with https://github.com/jenkinsci/rebuild-plugin/pull/29 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Scott Hebert
created JENKINS-24304
Enable/Disable verbose Git command logging in Jenkins build log
Issue Type:
Improvement
Assignee:
Nicolas De Loof
Components:
git
Created:
18/Aug/14 2:58 PM
Description:
The git plugin currently prints out the git commands that it executes.
git rev-parse master^{commit} # timeout=10
In some cases, these commands can be numerous and thus distract the user from other pertinent information in the build log.
It would be very valuable to be able to enable or disable this verbose output via a option in the job configuration.
Project:
Jenkins
Priority:
Minor
Reporter:
Scott Hebert
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-24304) Enable/Disable verbose Git command logging in Jenkins build log
Scott Hebert updated JENKINS-24304 Enable/Disable verbose Git command logging in Jenkins build log Change By: Scott Hebert (18/Aug/14 3:26 PM) Component/s: git-client Component/s: git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-23875) Ability to pass reference repo recursively
Scott Hebert commented on JENKINS-23875 Ability to pass reference repo recursively Hi, Scott here, working with Christian (the reporter)... Our use case is such that our reference repo is really a reference repo for the overall project including sub modules. Therefore, the request should be amended to specify that the reference repo specified in the job's configuration can be optionally passed to all submodule operations. 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-24259) Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins
Scott Hebert stopped work on JENKINS-24259 Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins Change By: Scott Hebert (15/Aug/14 3:51 PM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24259) Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins
Scott Hebert resolved JENKINS-24259 as Not A Defect Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins Change By: Scott Hebert (15/Aug/14 3:51 PM) Status: Open Resolved Resolution: NotADefect 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-24259) Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins
Scott Hebert edited a comment on JENKINS-24259 Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins I believe I was initially swayed by the fact that there are a couple of places in the core where the default site is forced to be first site in the UpdateSite list: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/PluginManager.java#L767 This actually has the effect of putting the jenkinsci default site as the first one in the UI even though it is not the first in the config file. Updating the URL from UI alters the URL in the persisted config file but does not change its site order. Seems a bit confusing. In any event, Daniel, you are right! If I use the update center's self-reported ID as its ID in Jenkins, as follows: ?xml version='1.0' encoding='UTF-8'? sites site idcompany-default/id urlhttps://update-center.company.com/update-center.json/url /site site iddefault/id urlhttp://updates.jenkins-ci.org/stable/update-center.json/url /site Then as long as https://update-center.company.com/update-center.json uses company-default as its ID, the corporate blessed plugin scenario works! I will resolve this 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] [core] (JENKINS-24259) Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins
Scott Hebert commented on JENKINS-24259 Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins I believe I was initially swayed by the fact that there are a couple of places in the core where the default site is forced to be first site in the UpdatSite list: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/PluginManager.java#L767 This actually has the effect of putting the jenkinsci default site as the first one in the UI even though it is not the first in the config file. Updating the URL from UI alters the URL in the persisted config file but does not change its site order. Seems a bit confusing. In any event, Daniel, you are right! If I use the update center's self-reported ID as its ID in Jenkins, as follows: ?xml version='1.0' encoding='UTF-8'? sites site idcompany-default/id urlhttps://update-center.company.com/update-center.json/url /site site iddefault/id urlhttp://updates.jenkins-ci.org/stable/update-center.json/url /site Then as long as https://update-center.company.com/update-center.json uses company-default as its ID, the corporate blessed plugin scenario works! I will resolve this 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] [core] (JENKINS-24259) Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins
Scott Hebert started work on JENKINS-24259 Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins Change By: Scott Hebert (14/Aug/14 2:11 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24259) Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins
Scott Hebert created JENKINS-24259 Unable to use custom update center as primary and jenkinsCI update center as secondary to install new plugins Issue Type: Improvement Affects Versions: current Assignee: Scott Hebert Components: core Created: 14/Aug/14 2:03 AM Description: In our corporate environment, we have a custom update center that contains a small set of blessed plugins whose versions we want to enforce. This update center serves as the primary. In addition, we want to make use of the JenkinsCI update center as the secondary to allow users to install optional plugins that are not part of the blessed corporate plugin baseline. We have updated our hudson.model.UpdateCenter.xml to contain: ?xml version='1.0' encoding='UTF-8'? sites site iddefault/id urlhttps://update-center.company.com/update-center.json/url /site site idjenkinsci-stable/id urlhttp://updates.jenkins-ci.org/stable/update-center.json/url /site /sites When attempting to install a new plugin that is only located in jenkinsci-stable using the above configuration, the following error is seen: No such plugin: timestamper.default The reason for this is due to the fact that id that is used to identify the plugin is the id from the update-center.json itself rather than the id from the config file hudson.model.UpdateCenter.xml Project: Jenkins Priority: Major Reporter: Scott Hebert 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-23878) Add in the GUI an option to restart master (same function as /restart url)
Scott Hebert assigned JENKINS-23878 to Scott Hebert Add in the GUI an option to restart master (same function as /restart url) Change By: Scott Hebert (23/Jul/14 6:41 PM) Assignee: MarcoMiller ScottHebert 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-23878) Add in the GUI an option to restart master (same function as /restart url)
Scott Hebert commented on JENKINS-23878 Add in the GUI an option to restart master (same function as /restart url) (Working with Christian and Marco)... I tried out the plugin and it works flawlessly as expected I made a minor change in that I changed the icon that is used on the Manage Jenkins page. I will go ahead and provide this to my user who requested this functionality. Going forwarding, would we be able to make this a JenkinsCI plugin and contribute to it? Thanks Daniel! 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] [acceptance-test-harness] (JENKINS-23326) LocalController does not inherit http proxy settings specified on command line
Scott Hebert reopened JENKINS-23326 LocalController does not inherit http proxy settings specified on command line Change By: Scott Hebert (16/Jul/14 3:44 PM) Resolution: Duplicate Status: Resolved Reopened 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] [acceptance-test-harness] (JENKINS-23780) ActiveDirectoryTest should support to selection of Group Lookup Strategy
Scott Hebert started work on JENKINS-23780 ActiveDirectoryTest should support to selection of Group Lookup Strategy Change By: Scott Hebert (14/Jul/14 5:59 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-23780) ActiveDirectoryTest should support to selection of Group Lookup Strategy
Scott Hebert created JENKINS-23780 ActiveDirectoryTest should support to selection of Group Lookup Strategy Issue Type: New Feature Assignee: Scott Hebert Components: acceptance-test-harness Created: 14/Jul/14 5:59 PM Description: The Acceptance Test Harness test case for Active Directory should support the selection of the Group Lookup Strategy that was introduced in version 1.38 of the AD plugin. Project: Jenkins Priority: Minor Reporter: Scott Hebert 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] [acceptance-test-harness] (JENKINS-23754) As a user, I would like to consult a report of plugins and plugin versions used during a run of the Acceptance Test Harness
Scott Hebert started work on JENKINS-23754 As a user, I would like to consult a report of plugins and plugin versions used during a run of the Acceptance Test Harness Change By: Scott Hebert (11/Jul/14 6:08 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-23754) As a user, I would like to consult a report of plugins and plugin versions used during a run of the Acceptance Test Harness
Scott Hebert created JENKINS-23754 As a user, I would like to consult a report of plugins and plugin versions used during a run of the Acceptance Test Harness Issue Type: New Feature Assignee: Scott Hebert Components: acceptance-test-harness Created: 10/Jul/14 6:50 PM Description: Given a set of ATH tests When the tests are executed Then a report is created listing the plugins and their versions that were used during testing. Project: Jenkins Priority: Minor Reporter: Scott Hebert 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] [acceptance-test-harness] (JENKINS-23326) LocalController does not inherit http proxy settings specified on command line
Scott Hebert resolved JENKINS-23326 as Duplicate LocalController does not inherit http proxy settings specified on command line Change By: Scott Hebert (09/Jul/14 8:05 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] [acceptance-test-harness] (JENKINS-23326) LocalController does not inherit http proxy settings specified on command line
Scott Hebert created JENKINS-23326 LocalController does not inherit http proxy settings specified on command line Issue Type: Improvement Assignee: Scott Hebert Components: acceptance-test-harness Created: 05/Jun/14 2:29 AM Description: Certain tests require the HTTP proxy settings to be specified in order to function correctly. Project: Jenkins Priority: Minor Reporter: Scott Hebert 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] [acceptance-test-harness] (JENKINS-23113) It shall be possible to use a http proxy with the acceptance test harness
Scott Hebert started work on JENKINS-23113 It shall be possible to use a http proxy with the acceptance test harness Change By: Scott Hebert (26/May/14 12:58 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-23113) It shall be possible to use a http proxy with the acceptance test harness
Scott Hebert created JENKINS-23113 It shall be possible to use a http proxy with the acceptance test harness Issue Type: Improvement Assignee: Scott Hebert Components: acceptance-test-harness Created: 20/May/14 8:10 PM Description: It shall be possible to configure the acceptance test harness to be able to use a corporate http proxy so that plugins can be downloaded from the jenkins update center. Project: Jenkins Priority: Minor Reporter: Scott Hebert 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.
