date:20150814

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29899 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: change cookie path from / to rootURL  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Steven Brown Path: src/main/resources/hudson/plugins/timestamper/annotator/TimestampAnnotatorFactory/script.js http://jenkins-ci.org/commit/timestamper-plugin/d64fd051781675b94c8b55705f0ae99757231eb2 Log: [FIXED JENKINS-29899] Change cookie path from '/' to the root URL of Jenkins 
Patch contributed by Kiyoshi Ohgishi. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [timestamper-plugin] (JENKINS-29899) change cookie path from / to rootURL

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29899 
 
 
 
  change cookie path from / to rootURL  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 Open 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] [timestamper-plugin] (JENKINS-29899) change cookie path from / to rootURL

2015-08-14 Thread stevengbr...@java.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 stevengbrown commented on  JENKINS-29899 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: change cookie path from / to rootURL  
 
 
 
 
 
 
 
 
 
 
Thanks! Your patch will be included in the next release, 1.7.2. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [websphere-deployer-plugin] (JENKINS-29201) Webspherer deploy error - could not bind resource refs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Peters resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29201 
 
 
 
  Webspherer deploy error - could not bind resource refs  
 
 
 
 
 
 
 
 
 

Change By:
 
 Greg Peters 
 
 
 

Status:
 
 Open 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] [websphere-deployer-plugin] (JENKINS-29201) Webspherer deploy error - could not bind resource refs

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Peters commented on  JENKINS-29201 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Webspherer deploy error - could not bind resource refs  
 
 
 
 
 
 
 
 
 
 
Try version 1.3.1. This should fix your issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [websphere-deployer-plugin] (JENKINS-29155) Add to "update the application" option.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Peters resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29155 
 
 
 
  Add to "update the application" option.  
 
 
 
 
 
 
 
 
 

Change By:
 
 Greg Peters 
 
 
 

Status:
 
 Open 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] [websphere-deployer-plugin] (JENKINS-29155) Add to "update the application" option.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Peters commented on  JENKINS-29155 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Add to "update the application" option.  
 
 
 
 
 
 
 
 
 
 
Supported added in v1.3.1(beta). Plugin can be manually installed for testing. Comment below if you have any additional questions or concerns 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-29921) "Failed to get git executable" During Git Installation

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-29921 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Failed to get git executable" During Git Installation  
 
 
 
 
 
 
 
 
 
 
So long as you successfully run the "sudo yum install -y git" and that actually installs and configures a working git at /usr/bin/git, then it should work. If it is failing, then you might check if /usr/bin/git is not being installed. 
Git works on the CentOS machines I use. Git works on the Debian and Ubuntu machines I use. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-29964) EC2 plugin floods AWS with API calls if it references a deleted AMI

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Carter Sanders created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29964 
 
 
 
  EC2 plugin floods AWS with API calls if it references a deleted AMI  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Francis Upton 
 
 
 

Components:
 

 ec2-plugin 
 
 
 

Created:
 

 15/Aug/15 1:44 AM 
 
 
 

Environment:
 

 Jenkins 1.609.1  Amazon EC2 plugin 1.28 
 
 
 

Labels:
 

 ec2-plugin aws 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Carter Sanders 
 
 
 
 
 
 
 
 
 
 
If an AMI referenced in a cloud is deleted but a reference to it is retained in the cloud config, following behavior is observed 
 

A build requesting the orphaned cloud's label will wait in the queue
 

Jenkins will flood the associated amazon account with a sufficient number of API calls to trigger rate limiting on the account, effectively taking it out of service

[JIRA] [ec2-plugin] (JENKINS-29921) "Failed to get git executable" During Git Installation

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse DeRose commented on  JENKINS-29921 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Failed to get git executable" During Git Installation  
 
 
 
 
 
 
 
 
 
 
JGit will work for our implementation, I was just hoping to get the actual Git client working too. Assuming the default ec2-user user can't get admin permissions in the /usr/bin directory, is there another user I can configure Jenkins to use for the Git client installation? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-trigger-plugin] (JENKINS-27741) Jenkins fails to report gerrit notifications spontaneously and on restart.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Carter Sanders commented on  JENKINS-27741 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins fails to report gerrit notifications spontaneously and on restart.  
 
 
 
 
 
 
 
 
 
 
Since upgrading to gerrit trigger plugin version 2.12.0, I have not seen this condition spontaneously occur again. I have however, seen failed notifications after a restart. The next time it happens, I will try to capture new logs. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-trigger-plugin] (JENKINS-25608) Intermittent gerrit trigger NPE on Jenkins restart

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Carter Sanders closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25608 
 
 
 
  Intermittent gerrit trigger NPE on Jenkins restart  
 
 
 
 
 
 
 
 
 

Change By:
 
 Carter Sanders 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-trigger-plugin] (JENKINS-25608) Intermittent gerrit trigger NPE on Jenkins restart

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Carter Sanders resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Problem is no longer seen after running gerrit trigger plugin version 2.12.  
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-25608 
 
 
 
  Intermittent gerrit trigger NPE on Jenkins restart  
 
 
 
 
 
 
 
 
 

Change By:
 
 Carter Sanders 
 
 
 

Status:
 
 Open 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] [gerrit-trigger-plugin] (JENKINS-26010) Workflow plugin not working with with Gerrit event

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-26010 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Workflow plugin not working with with Gerrit event  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Robert Sandell Path: pom.xml src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/ChangeIdAnnotator.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritRebuildValidator.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/PluginImpl.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/dependency/BecauseDependentBuildIsBuilding.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/dependency/DependencyQueueTaskDispatcher.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/events/ManualPatchsetCreated.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/events/lifecycle/GerritEventLifecycle.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/events/lifecycle/GerritEventLifecycleListener.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/GerritMessageProvider.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/GerritNotifier.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/NotificationFactory.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpander.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListener.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/job/rest/BuildStartedRestCommandJob.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/job/ssh/BuildStartedCommandJob.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/BuildMemory.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/EventListener.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritItemListener.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerBuildChooser.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerParameters.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTriggerTimerTask.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/actions/RetriggerAction.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/actions/RetriggerAllAction.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/actions/manual/TriggerMonitor.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/data/TriggerContext.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/data/TriggeredItemEntity.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/replication/ReplicationQueueTaskDispatcher.java src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger/config.jelly src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/dependency/DependencyQueueTaskDispatcherTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ParameterExpanderTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/ToGerritRunListenerTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/job/rest/BuildCompletedRestCommandJobHudsonTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/BuildMemoryTest.java src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/gerritnotifier/model/MemoryImprintTest.java src/test/java/com/sonyerics

[JIRA] [gerrit-trigger-plugin] (JENKINS-26010) Workflow plugin not working with with Gerrit event

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-26010 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Workflow plugin not working with with Gerrit event  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Tom Fennelly Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/EventListener.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/4fe3786915d0cdfcdecae7bbfa2cd6342a052a73 Log: Merge pull request #1 from jacob-keller/JENKINS-26010 
add actions to schedule2 for Workflow Jobs 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cmakebuilder-plugin] (JENKINS-29267) CMAKE_BUILD_TOOL is deprecated in cmake version 3.0

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29267 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CMAKE_BUILD_TOOL is deprecated in cmake version 3.0  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: 15knots Path: src/main/resources/hudson/plugins/cmake/BuildToolStep/config.jelly src/main/resources/hudson/plugins/cmake/BuildToolStep/help-args.html src/main/resources/hudson/plugins/cmake/BuildToolStep/help-envVars.html src/main/resources/hudson/plugins/cmake/BuildToolStep/help-withCmake.html src/main/resources/hudson/plugins/cmake/CmakeBuilder/config.jelly src/main/resources/hudson/plugins/cmake/CmakeBuilder/help-generator.html src/main/resources/hudson/plugins/cmake/CmakeBuilder/help-runTool.html src/main/resources/hudson/plugins/cmake/CmakeBuilder/help.html http://jenkins-ci.org/commit/cmakebuilder-plugin/995633bce33e8b934b2eae6781ec179bf220cf41 Log: JENKINS-29267 CMAKE_BUILD_TOOL: added online doc according to solution #1 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-29594) Permit specifying an SCM Configuration as an Advanced setting under SCM Polling Trigger

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29594 
 
 
 
  Permit specifying an SCM Configuration as an Advanced setting under SCM Polling Trigger  
 
 
 
 
 
 
 
 
 

Change By:
 
 Mark Waite 
 
 
 

Component/s:
 
 git-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [envinject-plugin] (JENKINS-29905) EnvInject always override build parameters in the Build::getEnvironment() API

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29905 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EnvInject always override build parameters in the Build::getEnvironment() API  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/test/java/org/jenkinsci/plugins/envinject/EnvInjectJobPropertyTest.java http://jenkins-ci.org/commit/envinject-plugin/d00eed29268faec671600a6d85e7ef0595bd48da Log: Add tne tests for EnvInjectJobProperty including a direct test for JENKINS-29905 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ghprb-plugin] (JENKINS-29963) MatrixProject builds previous revision in pull request

2015-08-14 Thread galbr...@mit.edu (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Marshall Galbraith assigned an issue to Honza Brázdil 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29963 
 
 
 
  MatrixProject builds previous revision in pull request  
 
 
 
 
 
 
 
 
 

Change By:
 
 Marshall Galbraith 
 
 
 

Component/s:
 
 ghprb-plugin 
 
 
 

Component/s:
 
 github-pullrequest-plugin 
 
 
 

Assignee:
 
 Kanstantsin Shautsou Honza Brázdil 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [github-pullrequest-plugin] (JENKINS-29963) MatrixProject builds previous revision in pull request

2015-08-14 Thread galbr...@mit.edu (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Marshall Galbraith created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29963 
 
 
 
  MatrixProject builds previous revision in pull request  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Kanstantsin Shautsou 
 
 
 

Components:
 

 github-pullrequest-plugin 
 
 
 

Created:
 

 14/Aug/15 10:39 PM 
 
 
 

Environment:
 

 Jenkins 1.624, GitHub Pull Request Builder 1.26.2 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Marshall Galbraith 
 
 
 
 
 
 
 
 
 
 
First I just want to say this is a really amazing plugin and aside from this one problem our group is really happy with it. 
We currently have a matrix project to test on multiple systems. Unfortunately we have a problem when new commits are pushed to a pull request. The main build of the matrix project will always get the correct revision, but the matrix builds end up building the the previous revision. The matrix builds are consistently one revision behind. I suspect it has something to do with the interaction between this line of code in GhprbTrigger.java 
 // add the previous pr BuildData as an action so that the correct change log is generated by the GitSCM plugin // note that this will be removed from the Actions list after the job is completed so that the old (and incorrect) // one isn't there return this.job.scheduleBuild2(job.getQuietPeriod(), cause, new ParametersAction(values), findPreviousBuildForPullId(pullIdPv));

[JIRA] [core] (JENKINS-19720) Jenkins Loses Build History

2015-08-14 Thread o.v.nenas...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-19720 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Jenkins Loses Build History  
 
 
 
 
 
 
 
 
 
 
Amit Bhardwaj, it should be another issue. Please create a new JIRA ticket and attach the system logs there 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [compress-build-log-plugin] (JENKINS-29861) compress-build-log doesn't delete file "log" but leaves "log.gz"

2015-08-14 Thread o.v.nenas...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Oleg Nenashev commented on  JENKINS-29861 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: compress-build-log doesn't delete file "log" but leaves "log.gz"  
 
 
 
 
 
 
 
 
 
 
There should not be such conflicts between publishers. BTW it may be caused by the file descriptor leak. It makes sense to run the tests and reproduce the issue manually. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-29962) Found invalid crumb

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hany Fahim commented on  JENKINS-29962 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Found invalid crumb  
 
 
 
 
 
 
 
 
 
 
I've confirmed via developer tools that the request is being made to the right URL: 
https://ci.hostname.com/jenkins/$stapler/bound/8a619a33-bce4-4c9f-81fb-5c98ddd556c7/render 
Any ideas? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-29962) Found invalid crumb

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hany Fahim reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Hi, 
I'm not sure why this was closed so quickly, but we are accessing it from the same URL. Under "Jenkins URL" in the Jenkins Location header, we have: 
https://ci.hostname.com/jenkins/ 
And the server is being accessed from this URL. We are still getting the same error. Can you clarify what you mean? 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29962 
 
 
 
  Found invalid crumb  
 
 
 
 
 
 
 
 
 

Change By:
 
 Hany Fahim 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-29962) Found invalid crumb

2015-08-14 Thread db...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck resolved as Not A Defect 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Access Jenkins using the URL you specified in its global configuration. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-29962 
 
 
 
  Found invalid crumb  
 
 
 
 
 
 
 
 
 

Change By:
 
 Daniel Beck 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Not A Defect 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-29962) Found invalid crumb

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hany Fahim created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29962 
 
 
 
  Found invalid crumb  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 14/Aug/15 9:53 PM 
 
 
 

Environment:
 

 Jenkins 1.620 with nginx as proxy, SSL enabled. 
 
 
 

Labels:
 

 jenkins gui 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Hany Fahim 
 
 
 
 
 
 
 
 
 
 
When trying to configure a new job, adding a new parameter using the drop-down results in a 403 error message being returned: 
403 No valid crumb was included in the request 
The logs show: 
WARNING: Found invalid crumb , . Will check remaining parameters for a valid one... Aug 14, 2015 5:32:06 PM hudson.security.csrf.CrumbFilter doFilter WARNING: No valid crumb was included in request for /jenkins//$stapler/bound/dd7670cf-db32-481d-b6f3-6fcdfde6e658/render. Returning 403. 
Curiously, when examining the request headers, the crumb is actually being dupli

[JIRA] [ec2-plugin] (JENKINS-29921) "Failed to get git executable" During Git Installation

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite edited a comment on  JENKINS-29921 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Failed to get git executable" During Git Installation  
 
 
 
 
 
 
 
 
 
 I'm at a loss.  Your configuration is enough different from mine that I don't have any reasonable guesses to offer of what you might try.  I think you've already used the typical diagnostic techniques I use, like# Run a "hello world" job on the slave with no SCM# Run a "hello world" job on the slave with git SCM and JGit using a repository which requires no authentication# Run a "hello world" job on the slave with git SCM and command line git using a repository which requires no authentication# Run a checkout job that clones your desired repo with JGit# Run a checkout job that clones your desired repo with command line git# Run a compilation job that clones and compiles your desired repo with JGit# Run a compilation job that clones and compiles your desired repo with command line git  Since I think you've already done all those steps, I don't have much else to offer.  Sorry... 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-29921) "Failed to get git executable" During Git Installation

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-29921 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Failed to get git executable" During Git Installation  
 
 
 
 
 
 
 
 
 
 
I'm at a loss. Your configuration is enough different from mine that I don't have any reasonable guesses to offer of what you might try. I think you've already used the typical diagnostic techniques I use, like 
 

Run a "hello world" job on the slave with no SCM
 

Run a "hello world" job on the slave with git SCM and JGit using a repository which requires no authentication
 

Run a "hello world" job on the slave with git SCM and command line git using a repository which requires no authentication
 

Run a checkout job that clones your desired repo with JGit
 

Run a checkout job that clones your desired repo with command line git
 

Run a compilation job that clones and compiles your desired repo with JGit
 

Run a compilation job that clones and compiles your desired repo with command line git Since I think you've already done all those steps, I don't have much else to offer. Sorry...
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [collabnet-plugin] (JENKINS-29314) Improving teamforge-collabnet plugin.

2015-08-14 Thread jeanne.ange...@panasonic.aero (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jeanne Angeles commented on  JENKINS-29314 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Improving teamforge-collabnet plugin.  
 
 
 
 
 
 
 
 
 
 
I hope this gets approved soon. This is a change we want to leverage. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-29921) "Failed to get git executable" During Git Installation

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse DeRose commented on  JENKINS-29921 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Failed to get git executable" During Git Installation  
 
 
 
 
 
 
 
 
 
 
Correct, I'm automating the Git installation on my slaves via JGit. The slaves do not already have Git installed on them without me explicitly installing it via the slave's init script (which I removed for the purpose of testing installation via JGit). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-18032) "Delete Project" link fails with 403 Exception: No valid crumb was included in the request

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hany Fahim edited a comment on  JENKINS-18032 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Delete Project" link fails with 403 Exception: No valid crumb was included in the request  
 
 
 
 
 
 
 
 
 
 This issue also appears to affect 1.620. Are there any  workaround  workarounds  for this? I can confirm that the crumb header makes it through with other requests, just not when deleting, and possibly others as well. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-18032) "Delete Project" link fails with 403 Exception: No valid crumb was included in the request

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Hany Fahim commented on  JENKINS-18032 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Delete Project" link fails with 403 Exception: No valid crumb was included in the request  
 
 
 
 
 
 
 
 
 
 
This issue also appears to affect 1.620. Are there any workaround for this? I can confirm that the crumb header makes it through with other requests, just not when deleting, and possibly others as well. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [websphere-deployer-plugin] (JENKINS-22256) Parameters or Jenkins Environment Variable not recognized in Webpshere plugin

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Peters resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in Beta v1.3 version 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-22256 
 
 
 
  Parameters or Jenkins Environment Variable not recognized in Webpshere plugin  
 
 
 
 
 
 
 
 
 

Change By:
 
 Greg Peters 
 
 
 

Status:
 
 In Progress 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] [ec2-plugin] (JENKINS-29921) "Failed to get git executable" During Git Installation

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Mark Waite commented on  JENKINS-29921 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Failed to get git executable" During Git Installation  
 
 
 
 
 
 
 
 
 
 
Are you attempting some form of automated install of git on your slave? Since git is already installed, you don't need Jenkins to install it for you. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [logstash-plugin] (JENKINS-29961) Logstash plug-in is not pushing the [Finished: FAILURE] message to elasticsearch

2015-08-14 Thread aiale...@yahoo.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aditya Inapurapu updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29961 
 
 
 
  Logstash plug-in is not pushing the [Finished: FAILURE] message to elasticsearch  
 
 
 
 
 
 
 
 
 

Change By:
 
 Aditya Inapurapu 
 
 
 

Environment:
 
 Elasticsearch 1.4 or Elasticsearch 1.5logstash 1.0.4Jenkins 1. 613 596.2 LTS 
 
 
 
 
 
 
 
 
 
 I  install  setup  the  logstash  plugin  and try  as detailed in my comment on 6/7/2015 on https://issues.jenkins-ci.org/browse/JENKINS-28546.The jenkins build data is getting pushed  to  access  elasticsearch through logstash. But, when  the  server and there  result  is  no activity in  'FAILURE',  the  log file with default logging  failure keyword is not showing up in elasticsearch . Example:   I  am using an  see this message in the  elasticsearch  server without  data on  a  password  successful build: message":["Finished: SUCCESS"]I am expecting this message on a failed build: message":["Finished: FAILURE"]and I am not seeing it .  Perhaps that is the issue.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.c

[JIRA] [logstash-plugin] (JENKINS-29961) Logstash plug-in is not pushing the [Finished: FAILURE] message to elasticsearch

2015-08-14 Thread aiale...@yahoo.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Aditya Inapurapu created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29961 
 
 
 
  Logstash plug-in is not pushing the [Finished: FAILURE] message to elasticsearch  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 logstash-plugin 
 
 
 

Created:
 

 14/Aug/15 7:22 PM 
 
 
 

Environment:
 

 Elasticsearch 1.4 or Elasticsearch 1.5  logstash 1.0.4  Jenkins 1.613 
 
 
 

Labels:
 

 elasticsearch logstash 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Aditya Inapurapu 
 
 
 
 
 
 
 
 
 
 
I install the plugin and try to access the server and there is no activity in the log file with default logging. I am using an elasticsearch server without a password. Perhaps that is the issue.

[JIRA] [websphere-deployer-plugin] (JENKINS-29725) Application starting issue websphere application server 8.5 after deployment Jenkins

2015-08-14 Thread asw...@sunamerica.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Ansuman Swain commented on  JENKINS-29725 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Application starting issue websphere application server 8.5 after deployment Jenkins  
 
 
 
 
 
 
 
 
 
 
Please find the below stack trace from the IBM WebSphere logs for the same: - [8/14/15 2:15:19:395 PDT] 0063 ApplicationMg A   WSVR0204I: Application: InternetApp_war  Application build level: Unknown 
[8/14/15 2:15:19:979 PDT] 0063 ExtensionPoin I   CWXRS0034I: Extension com.ibm.wsspi.extension.webservices_app-depl-providers connected with Extension Point com.ibm.wsspi.extension.app-depl-providers 
[8/14/15 2:15:19:980 PDT] 0063 ExtensionPoin I   CWXRS0034I: Extension com.ibm.wsspi.extension.ibmautogeneratedidentifier1 connected with Extension Point com.ibm.wsspi.extension.impl-factory 
[8/14/15 2:15:20:001 PDT] 0063 webcontainer  E com.ibm.ws.webcontainer.VirtualHostImpl addWebApplication SRVE0164E: Web Application InternetApp_war#SACOM uses the context root /SACOM/*, which is already in use by Web Application VDEV3-InternetDev_war#SACOM. Web Application SACOM will not be loaded. 
[8/14/15 2:15:20:007 PDT] 0063 DeployedAppli W   WSVR0206E: Module, InternetApp.war, of application, InternetApp_war.ear/deployments/InternetApp_war, failed to start 
[8/14/15 2:15:20:017 PDT] 0063 ApplicationMg W   WSVR0101W: An error occurred starting, InternetApp_war 
[8/14/15 2:15:20:017 PDT] 0063 ApplicationMg A   WSVR0217I: Stopping application: InternetApp_war 
[8/14/15 2:15:20:074 PDT] 0063 ApplicationMg A   WSVR0220I: Application stopped: InternetApp_war 
[8/14/15 2:15:20:097 PDT] 0063 CompositionUn E   WSVR0194E: Composition unit WebSphere:cuname=InternetApp_war in BLA WebSphere:blaname=InternetApp_war failed to start. 
[8/14/15 2:30:54:903 PDT] 00e4 FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /app/IBM/WASV85/profiles/DEV2/logs/ffdc/VDEV-3_bfd0218b_15.08.14_02.30.54.8923790543432167547850.txt com.ibm.ws.webcontainer.filter.WebAppFilterManager.loadFilter 298 
[8/14/15 2:30:54:908 PDT] 00e4 FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /app/IBM/WASV85/profiles/DEV2/logs/ffdc/VDEV-3_bfd0218b_15.08.14_02.30.54.904902540229061048630.txt com.ibm.ws.webcontainer.filter.WebAppFilterManager.loadFilter 380 
[8/14/15 2:30:54:912 PDT] 00e4 FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /app/IBM/WASV85/profiles/DEV2/logs/ffdc/VDEV-3_bfd0218b_15.08.14_02.30.54.908369556023795729291.txt com.ibm.ws.webcontainer.filter.WebAppFilterManager.getFilterInstanceWrapper 166 
[8/14/15 2:30:54:913 PDT] 00e4 FfdcProvider  W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /app/IBM/WASV85/profiles/DEV2/logs/ffdc/VDEV-3_bfd0218b_15.08.14_02.30.54.9138975011598560680289.txt com.ibm.ws.webcontainer.filter.WebAppFilterManager.invokeFilters -SE 1078 
[8/14/15 2:30:54:913 PDT] 00e4 webapp    E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[GenericServletWrapper]: java.lang.ClassNotFoundException:

[JIRA] [cmakebuilder-plugin] (JENKINS-29329) Visual Studio/MSBuild projects can not be built implicitly anymore

2015-08-14 Thread fifteenknots...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Weber started work on  JENKINS-29329 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Martin Weber 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-25276) Job Disappears from ListView after rename

2015-08-14 Thread db...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Daniel Beck commented on  JENKINS-25276 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job Disappears from ListView after rename  
 
 
 
 
 
 
 
 
 
 
Just don't push branches to jenkinsci. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-25276) Job Disappears from ListView after rename

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick reopened an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Argh, link daemon… 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-25276 
 
 
 
  Job Disappears from ListView after rename  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-25276) Job Disappears from ListView after rename

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25276 
 
 
 
  Job Disappears from ListView after rename  
 
 
 
 
 
 
 
 
 

Change By:
 
 SCM/JIRA link daemon 
 
 
 

Status:
 
 In Progress 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] [core] (JENKINS-25276) Job Disappears from ListView after rename

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-25276 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job Disappears from ListView after rename  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/ListView.java http://jenkins-ci.org/commit/jenkins/9300dab566131e002657bdba606c99ddb10a97c1 Log: [FIXED JENKINS-25276] NestedView extends View implements ViewGroup, so need to search recursively. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-25276) Job Disappears from ListView after rename

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick started work on  JENKINS-25276 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-25276) Job Disappears from ListView after rename

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick assigned an issue to Jesse Glick 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25276 
 
 
 
  Job Disappears from ListView after rename  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-25276) Job Disappears from ListView after rename

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-25276 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Job Disappears from ListView after rename  
 
 
 
 
 
 
 
 
 
 
Jenkins.onRenamed still calls View.onJobRenamed for compatibility, so NestedView could still implement it. But this will only work for simple renames at top level. It would be better for the nested view to be included in the ListView listener (both for location change and delete). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [websphere-deployer-plugin] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)

2015-08-14 Thread raju.gandhi+jenkins...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Peters resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
Fixed in Beta v1.3. Please test and validate by installing this plugin version manually. 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-21643 
 
 
 
  Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)  
 
 
 
 
 
 
 
 
 

Change By:
 
 Greg Peters 
 
 
 

Status:
 
 Reopened 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] [cmakebuilder-plugin] (JENKINS-29329) Visual Studio/MSBuild projects can not be built implicitly anymore

2015-08-14 Thread fifteenknots...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Weber updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29329 
 
 
 
  Visual Studio/MSBuild projects can not be built implicitly anymore  
 
 
 
 
 
 
 
 
 

Change By:
 
 Martin Weber 
 
 
 

Priority:
 
 Major Blocker 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [cmakebuilder-plugin] (JENKINS-29267) CMAKE_BUILD_TOOL is deprecated in cmake version 3.0

2015-08-14 Thread fifteenknots...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Weber commented on  JENKINS-29267 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: CMAKE_BUILD_TOOL is deprecated in cmake version 3.0  
 
 
 
 
 
 
 
 
 
 
Are you using msbuild? If so, you might have hit JENKINS-29329  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ws-cleanup-plugin] (JENKINS-29960) Workspace Cleanup Plugin does not copy over "Post-build Actions"

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raju Gandhi updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29960 
 
 
 
  Workspace Cleanup Plugin does not copy over "Post-build Actions"   
 
 
 
 
 
 
 
 
 

Change By:
 
 Raju Gandhi 
 
 
 
 
 
 
 
 
 
 This is a *fresh* install of Jenkins. I installed all the plugins (listed above).I then created a Job. * Under {{Build Environment}} I checked {{Delete workspace before build starts}}* In the {{Post-build Actions}} I simply selected {{Delete workspace when build is done}} with no additional changes (That is I did *not* click on the {{Advanced}} button)With that in place, I went to Jenkins->New Job and entered a new name, and then picked {{Copy existing Item}} giving it the name of the previously created job. Upon inspecting the configuration I noticed that * Under {{Build Environment}} {{Delete workspace before build starts}} is correctly selected* *However* under {{Post-build Actions}} there is nothing.Inspecting the {{config.xml}} file of the newly created job tells me that that portion of the configuration did not port over.Here is the relevant portion of the *ORIGINAL* job's configuration{code:xml}  falsefalsetruetruetruetruetruefalsefalsefalse  {code}Here is the same portion of the *NEW* job's configuration{code:xml}  false  {code}As a final attempt I programmatically {{POST}}ed the configuration of the original job to *another* job and I see the same thing happening. For some reason the {{Post-build Actions}} are not being applied. Just to be sure, I tweaked the original job to have 2 {{Post-build Actions}} - and then created a *New Job* that simply is a Copy of the original one. Again, it did not port over the {{Delete workspace before build starts}} in {{Post-build Actions}} - However the other action did port over. If there are any other details you like me to report on, please let me know.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[JIRA] [ws-cleanup-plugin] (JENKINS-29960) Workspace Cleanup Plugin does not copy over "Post-build Actions"

2015-08-14 Thread raju.gandhi+jenkins...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Raju Gandhi created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29960 
 
 
 
  Workspace Cleanup Plugin does not copy over "Post-build Actions"   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 vjuranek 
 
 
 

Components:
 

 ws-cleanup-plugin 
 
 
 

Created:
 

 14/Aug/15 6:07 PM 
 
 
 

Environment:
 

 Jenkins ver. 1.60  Workspace Cleanup Plugin ver. 0.26   Other plugins that I have installed (on top of the ones that Jenkins ships with)   conditional-buildstep 1.3.3  GIT plugin 2.4.0  GitHub API Plugin 1.69  GitHub plugin 1.12.1  Multiple SCMs 0.5  Parameterized Trigger plugin 2.28  promoted builds plugincriteria 2.21  Run Condition Plugin 1.0  SCM API Plugin 0.2  Token Macro Plugin 1.10 
 
 
 

Labels:
 

 plugin plugins 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Raju Gandhi 
 
 
 
 
 
 
 
 
 
 
This is a fresh install of Jenkins. I installed all the plugins (listed above). 
I then created a Job.  
 

Under Build Environment I checked Delete workspace before build starts

[JIRA] [slack-plugin] (JENKINS-29949) Configuration should not require a trailing slash on Build Server URL

2015-08-14 Thread sam.mxra...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Gleske commented on  JENKINS-29949 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Configuration should not require a trailing slash on Build Server URL  
 
 
 
 
 
 
 
 
 
 
Agreed. It should properly format the value the way it is expecting and not require a human to worry about something trivial like a trailing slash. I don't actively develop this plugin but I do maintain pull requests and releases. Contributions are welcome to resolve this issue. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [deployment-notification-plugin] (JENKINS-28632) Workflow support for Deployment Notification trigger

2015-08-14 Thread svano...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Van Oort started work on  JENKINS-28632 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Sam Van Oort 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [deployment-notification-plugin] (JENKINS-28632) Workflow support for Deployment Notification trigger

2015-08-14 Thread svano...@cloudbees.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Sam Van Oort assigned an issue to Sam Van Oort 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28632 
 
 
 
  Workflow support for Deployment Notification trigger  
 
 
 
 
 
 
 
 
 

Change By:
 
 Sam Van Oort 
 
 
 

Assignee:
 
 Sam Van Oort 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [doxygen-plugin] (JENKINS-29938) Unable to serialize is reported when publishing doxygen generate html files

2015-08-14 Thread darinpant...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Darin Pantley commented on  JENKINS-29938 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to serialize is reported when publishing doxygen generate html files  
 
 
 
 
 
 
 
 
 
 
Oops. I was giving it the path to the published HTML files instead of the Doxyfile. I've switched my job to use "Publish Javadoc" instead of "Publish Doxygen" and no longer face this issue. 
The error thrown by this code is not helpful. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [workflow-plugin] (JENKINS-26055) DurableTaskStep

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-26055 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: DurableTaskStep  
 
 
 
 
 
 
 
 
 
 
A more general change that might be useful here is to allow a BodyInvoker to invoke another StepExecution rather than a regular body. Then you could have a step which runs (for example) ToolStep, then sets up some context including EnvironmentExpander and ConsoleLogFilter, then runs ShellStep (for example) with some preconfigured command. 
This would have been useful here too. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-27919) Split HistoryWidget from core

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27919 
 
 
 
  Split HistoryWidget from core  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Labels:
 
 split-plugins-from-core  workflow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-29594) Permit specifying an SCM Configuration as an Advanced setting under SCM Polling Trigger

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29594 
 
 
 
  Permit specifying an SCM Configuration as an Advanced setting under SCM Polling Trigger  
 
 
 
 
 
 
 
 
 
 
Not a goal for Workflow. You should never parameterize your SCM this way; polling cannot work if you. If what you were trying to accomplish is to handle multiple branches/forks of what is logically one repository, you should use the Workflow: Multibranch plugin (currently in beta). For freestyle-ish projects, you can use one of the other branch-api integrations. 
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Component/s:
 
 workflow-plugin 
 
 
 

Labels:
 
 hook polling pollscm scm  workflow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.c

[JIRA] [doxygen-plugin] (JENKINS-29938) Unable to serialize is reported when publishing doxygen generate html files

2015-08-14 Thread darinpant...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Darin Pantley commented on  JENKINS-29938 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Unable to serialize is reported when publishing doxygen generate html files  
 
 
 
 
 
 
 
 
 
 
I am seeing the same behavior in Linux (Doxygen-plugin 0.17, Jenkins ver. 1.580.3): 

 
Publishing Doxygen HTML results.
FATAL: error
java.io.IOException: remote file operation failed: /work/jenkins/workspace/pipeline_generate-doxygen at hudson.remoting.Channel@11de1573:il-slave11: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@54b78bf8
	at hudson.FilePath.act(FilePath.java:976)
	at hudson.FilePath.act(FilePath.java:958)
	at hudson.plugins.doxygen.DoxygenArchiver._perform(DoxygenArchiver.java:223)
	at hudson.plugins.doxygen.DoxygenArchiver.perform(DoxygenArchiver.java:177)
	at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
	at hudson.model.Run.execute(Run.java:1770)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)
Caused by: java.io.IOException: Unable to serialize hudson.FilePath$FileCallableWrapper@54b78bf8
	at hudson.remoting.UserRequest.serialize(UserRequest.java:169)
	at hudson.remoting.UserRequest.(UserRequest.java:63)
	at hudson.remoting.Channel.call(Channel.java:750)
	at hudson.FilePath.act(FilePath.java:969)
	... 12 more
Caused by: java.io.NotSerializableException: hudson.plugins.doxygen.DoxygenEnvironmentVariableExpander
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1183)
	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547)
	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508)
	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431)
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177)
	at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1547)
	at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1508)
	at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1431)
	at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1177)
	at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:347)
	at hudson.remoting.UserRequest._serialize(UserRequest.java:158)
	at hudson.remoting.UserRequest.serialize(UserRequest.java:167)
	... 15 more
Build step 'Publish Doxygen' changed build result to FAILURE
Finished: FAILURE
 

 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [websphere-deployer-plugin] (JENKINS-29725) Application starting issue websphere application server 8.5 after deployment Jenkins

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Greg Peters commented on  JENKINS-29725 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Application starting issue websphere application server 8.5 after deployment Jenkins  
 
 
 
 
 
 
 
 
 
 
Please provide the stack trace from the IBM WebSphere logs so I can see the failures 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-29921) "Failed to get git executable" During Git Installation

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse DeRose commented on  JENKINS-29921 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Failed to get git executable" During Git Installation  
 
 
 
 
 
 
 
 
 
 
Addendum: The EC2 slave default user (e.g. ec2-user) does not have write permissions in the "/usr/bin" directory. If Jenkins is using the ec2-user user for the Git installation process on the slave, this could why I'm seeing the "Failed to create a temp file on /usr/bin/git" error. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [p4-plugin] (JENKINS-28421) Information provided to email-ext should be perforce email address, not perforce username

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-28421 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Information provided to email-ext should be perforce email address, not perforce username  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/changes/P4ChangeEntry.java src/main/java/org/jenkinsci/plugins/p4/client/ConnectionHelper.java http://jenkins-ci.org/commit/p4-plugin/5f936ad0fffc3212a1960b1d7c67c3807c657fe4 Log: Add Perforce User's email to Jenkins User property. 
JENKINS-28421 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ec2-plugin] (JENKINS-29921) "Failed to get git executable" During Git Installation

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse DeRose commented on  JENKINS-29921 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: "Failed to get git executable" During Git Installation  
 
 
 
 
 
 
 
 
 
 
FYI, my Jenkins slaves are running: 
java version "1.7.0_85" OpenJDK Runtime Environment (amzn-2.6.1.3.61.amzn1-x86_64 u85-b01) OpenJDK 64-Bit Server VM (build 24.85-b03, mixed mode) 
As for the unreleased git plugin, I installed it and received this message during my Jenkins build (using the Git client rather than JGit): 
Failed to get git executable: java.io.IOException: Failed to create a temp file on /usr/bin/git 
It looks like it's trying to create a temp file in the "Path to Git Executable" path (which I currently have listed as "/usr/bin/git" since that's where the Git executable lives on my Jenkins slaves). However, if I remove the Git Client installation options (and just use JGit), the build finishes successfully. Any ideas why the Git client wouldn't work but JGit would here? (I assume it's due to the "Path to Git Executable" I've set, since that's where it's erroring out above.) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [deployment-notification-plugin] (JENKINS-28632) Workflow support for Deployment Notification trigger

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick stopped work on  JENKINS-28632 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Status:
 
 In Progress Open 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-flow-plugin] (JENKINS-29595) Build-flow project not sending mail notification

2015-08-14 Thread slide.o....@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Alex Earl commented on  JENKINS-29595 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build-flow project not sending mail notification  
 
 
 
 
 
 
 
 
 
 
Based on the build log you provided, the build flow plugin is not initiating the email-ext plugin.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-flow-plugin] (JENKINS-29595) Build-flow project not sending mail notification

2015-08-14 Thread manojo...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manoj Kumar commented on  JENKINS-29595 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Build-flow project not sending mail notification  
 
 
 
 
 
 
 
 
 
 
Not sure how this will effect. But my earlier problem was on Email-ext plugin + Bluid flow plugin. The Buildflow project was not sending mails after build completion. 
Regards, Manoj 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [warnings-plugin] (JENKINS-29959) Make Warnings Plugin compatible with Workflow

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29959 
 
 
 
  Make Warnings Plugin compatible with Workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 As Jenkins user, I would like to use [ Checkstyle Warnings  Plugin|https://wiki.jenkins-ci.org/display/JENKINS/ Checkstyle Warnings +Plugin] from a workflow script (flow). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [warnings-plugin] (JENKINS-29959) Make Warnings Plugin compatible with Workflow

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto started work on  JENKINS-29959 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [checkstyle-plugin] (JENKINS-29959) Make Warnings Plugin compatible with Workflow

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29959 
 
 
 
  Make Warnings Plugin compatible with Workflow  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 
 Manuel Jesús Recena Soto 
 
 
 

Components:
 

 checkstyle-plugin 
 
 
 

Created:
 

 14/Aug/15 3:43 PM 
 
 
 

Labels:
 

 workflow 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Manuel Jesús Recena Soto 
 
 
 
 
 
 
 
 
 
 
As Jenkins user, I would like to use Checkstyle Plugin from a workflow script (flow). 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment

[JIRA] [warnings-plugin] (JENKINS-29959) Make Warnings Plugin compatible with Workflow

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29959 
 
 
 
  Make Warnings Plugin compatible with Workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Component/s:
 
 warnings-plugin 
 
 
 

Component/s:
 
 checkstyle-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [envinject-plugin] (JENKINS-29817) Inject environment variables for a Job

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29817 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Inject environment variables for a Job  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: recena Path: pom.xml src/main/java/org/jenkinsci/plugins/envinject/EnvInjectBuildVariableContributor.java src/main/java/org/jenkinsci/plugins/envinject/EnvInjectEnvVarsContributor.java src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectBuildWrapper/config.jelly src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectBuildWrapper/help-propertiesContent.html src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectBuildWrapper/help-propertiesContent_ja.html src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectBuildWrapper/help-propertiesFilePath.html src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectJobProperty/help-keepBuildVariables.html src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectJobProperty/help-keepJenkinsSystemVariables.html src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectJobProperty/help-propertiesContent.html src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectJobProperty/help-propertiesContent_ja.html src/main/webapp/help.html src/test/java/org/jenkinsci/plugins/envinject/EnvInjectEnvVarsContributorTest.java http://jenkins-ci.org/commit/envinject-plugin/b34ae597b8f908872b044a728e0597d676f9014a Log: JENKINS-29817 Inject environment variables for a Job 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [envinject-plugin] (JENKINS-29817) Inject environment variables for a Job

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-29817 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Inject environment variables for a Job  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Manuel Recena Path: pom.xml src/main/java/org/jenkinsci/plugins/envinject/EnvInjectBuildVariableContributor.java src/main/java/org/jenkinsci/plugins/envinject/EnvInjectEnvVarsContributor.java src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectBuildWrapper/config.jelly src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectBuildWrapper/help-propertiesContent.html src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectBuildWrapper/help-propertiesContent_ja.html src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectBuildWrapper/help-propertiesFilePath.html src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectJobProperty/help-keepBuildVariables.html src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectJobProperty/help-keepJenkinsSystemVariables.html src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectJobProperty/help-propertiesContent.html src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectJobProperty/help-propertiesContent_ja.html src/main/webapp/help.html src/test/java/org/jenkinsci/plugins/envinject/EnvInjectEnvVarsContributorTest.java http://jenkins-ci.org/commit/envinject-plugin/95c1f0eac808580d21c9e71e9fe9b55ab085cb85 Log: Merge pull request #56 from recena/JENKINS-29817 
JENKINS-29817 Inject environment variables for a Job 
Compare: https://github.com/jenkinsci/envinject-plugin/compare/abca0ed5091e...95c1f0eac808 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [active-directory-plugin] (JENKINS-29958) Azure AD / MSA authentication

2015-08-14 Thread viktor.be...@kishonti.net (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Viktor Berke created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29958 
 
 
 
  Azure AD / MSA authentication  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  New Feature 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 active-directory-plugin 
 
 
 

Created:
 

 14/Aug/15 3:19 PM 
 
 
 

Labels:
 

 authentication ad azure msa microsoft 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Viktor Berke 
 
 
 
 
 
 
 
 
 
 
Hi, I'm not sure the component is right but you'll tell me. 
I'm in the process of migrating our systems to the cloud, and one of those is our directory. 
Jenkins already supports LDAP and AD so it may be a logical next step to add support for Azure AD (that also supports the OpenID and OAuth standards). 
There are plenty of resources for doing this: 
[ Docs ] [ Example ] [ Libs ] 
Even better, now Azure AD and MSA can be supported with the same API. 
[ The Converged Microsoft Account and Azure Active Directory Programming Model ] 
What do you guys think?

[JIRA] [core] (JENKINS-27034) BuildableItems (Subtasks) are miscounted in the queue

2015-08-14 Thread gentoo.inte...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou commented on  JENKINS-27034 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: BuildableItems (Subtasks) are miscounted in the queue  
 
 
 
 
 
 
 
 
 
 
Upping to critical as description looks very obvious and i think some bug reports to cloud plugins depends on it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [core] (JENKINS-27034) BuildableItems (Subtasks) are miscounted in the queue

2015-08-14 Thread gentoo.inte...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Kanstantsin Shautsou updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27034 
 
 
 
  BuildableItems (Subtasks) are miscounted in the queue  
 
 
 
 
 
 
 
 
 

Change By:
 
 Kanstantsin Shautsou 
 
 
 

Priority:
 
 Major Critical 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [envinject-plugin] (JENKINS-29817) Inject environment variables for a Job

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto commented on  JENKINS-29817 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Inject environment variables for a Job  
 
 
 
 
 
 
 
 
 
 
This PR has been merged. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [envinject-plugin] (JENKINS-29817) Inject environment variables for a Job

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29817 
 
 
 
  Inject environment variables for a Job  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Status:
 
 In Progress 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] [p4-plugin] (JENKINS-28421) Information provided to email-ext should be perforce email address, not perforce username

2015-08-14 Thread pal...@perforce.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen edited a comment on  JENKINS-28421 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Information provided to email-ext should be perforce email address, not perforce username  
 
 
 
 
 
 
 
 
 
 I'm curious if I can set hudson.tasks.Mailer.UserProperty.UserProperty.  MailAddressResolver claims to look for the email as a UserProperty:  * {noformat}  So the common technique for a mail address resolution is to define your own {@link UserProperty} types and  *  add it to {@link User} objects where more context is available. For example, an {@link SCM} implementation  *  can have a lot more information about a particular user during a check out, so that would be a good place  *  to capture information as {@link UserProperty}, which then later used by a {@link MailAddressResolver}. {noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [ssh-agent-plugin] (JENKINS-28689) Make SSH Agent Plugin compatible with Workflow

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-28689 
 
 
 
  Make SSH Agent Plugin compatible with Workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Summary:
 
 Make  SSH Agent Plugin  compatible with Workflow  plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [p4-plugin] (JENKINS-28421) Information provided to email-ext should be perforce email address, not perforce username

2015-08-14 Thread pal...@perforce.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Paul Allen commented on  JENKINS-28421 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Information provided to email-ext should be perforce email address, not perforce username  
 
 
 
 
 
 
 
 
 
 
I'm curious if I can set hudson.tasks.Mailer.UserProperty.UserProperty. MailAddressResolver claims to look for the email as a UserProperty: 
 

So the common technique for a mail address resolution is to define your own {@link UserProperty} types and * add it to {@link User} objects where more context is available. For example, an {@link SCM} implementation * can have a lot more information about a particular user during a check out, so that would be a good place * to capture information as {@link UserProperty} 
, which then later used by a  {@link MailAddressResolver} 
.
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [docker-custom-build-environment-plugin] (JENKINS-29674) Maven project not supported by the build environment plugin

2015-08-14 Thread nicolas.del...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Nicolas De Loof commented on  JENKINS-29674 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Maven project not supported by the build environment plugin  
 
 
 
 
 
 
 
 
 
 
Proposed https://github.com/jenkinsci/maven-plugin/pull/51 - extension point so other plugins can contribute discovery of the maven -> slave agent callback socket host IP. If/when approved, could use it to declare "dockerhost" as hostname to connect to. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [log-parser-plugin] (JENKINS-27208) Make Log Parser Plugin compatible with Workflow

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27208 
 
 
 
  Make Log Parser Plugin compatible with Workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Summary:
 
 Add workflow compatibility to log-parser Make Log Parser Plugin compatible with Workflow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [dependency-check-jenkins-plugin] (JENKINS-29908) Make OWASP Dependency-Check Plug-in compatible with Workflow

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29908 
 
 
 
  Make OWASP Dependency-Check Plug-in compatible with Workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Summary:
 
 Male Make  OWASP Dependency-Check Plug-in compatible with Workflow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [checkstyle-plugin] (JENKINS-29648) Make Checkstyle Plugin compatible with Workflow

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Manuel Jesús Recena Soto updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29648 
 
 
 
  Make Checkstyle Plugin compatible with Workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Manuel Jesús Recena Soto 
 
 
 

Labels:
 
 workflow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [websphere-deployer-plugin] (JENKINS-29725) Application starting issue websphere application server 8.5 after deployment Jenkins

2015-08-14 Thread asw...@sunamerica.com (JIRA)

Title: Message Title

Ansuman Swain commented on JENKINS-29725

Re: Application starting issue websphere application server 8.5 after deployment Jenkins

Dear Greg,
Thank you...It worked ! When Application is in down state the plugin is able to uninstall,install,start the application successfully. However if application is in running state (From WAS Console) , the deployment fails and gives the below error. Also the status of the application is showing as stopped in WAS Console even after jenkins deployment/start up is successful.
There might be a possibility that the stopping of the application is handled differently by Jenkins and by WAS console which is the cause of IllegalstateException.
Starting New Application 'InternetApp_war'... Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Could not start artifact 'InternetApp_war': java.lang.IllegalStateException: Start of the application was not successful. WAS JVM logs should contain the detailed error message. at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.startArtifact(WebSphereDeploymentService.java:309)

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] [hp-application-automation-tools-plugin] (JENKINS-29957) Could not create scheduler

2015-08-14 Thread i.qua...@itecor.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Imran Quaine created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29957 
 
 
 
  Could not create scheduler  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Ofir Shaked 
 
 
 

Components:
 

 hp-application-automation-tools-plugin 
 
 
 

Created:
 

 14/Aug/15 2:19 PM 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Imran Quaine 
 
 
 
 
 
 
 
 
 
 
Hi all, 
We are migrating our whole automated testing infrastructure from HP UFT11.53+ALM11.00 to HP UFT12.02& ALM12.20. We have a Win7 64-bit VM with UFT12.02, on which Jenkins v1.624 is installed with the latest version of the HP ALM plug-in.  And we have a Win2008 64-bit VM used for ALM12.20 Patch level 1 (it's configured to use port 80, and NOT the default port 8080). We used to have the equivalent for the v11 infra. 
We've been running tests using Jenkins onto the same VM on the v11 infra, and it worked well. Now, on the v12 infra, we're getting the infamous error: 
Could not create scheduler, please verify ALM client installation on run machine by downloading and in installing the add-in form: http://ALM_SERVER/qcbin/TDConnectivity_index.html Build step 'Execute HP functional tests from HP ALM' changed build result to FAILURE 
We have been digging deep into the matter: 
 

We've followed the instruction given by the error message above, by installing the TDConnect with Admin rights.
 

We'v

[JIRA] [p4-plugin] (JENKINS-26650) Canceling an in progress build does not stop a sync.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 SCM/JIRA link daemon commented on  JENKINS-26650 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Canceling an in progress build does not stop a sync.  
 
 
 
 
 
 
 
 
 
 
Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/client/ConnectionHelper.java src/main/java/org/jenkinsci/plugins/p4/console/P4Progress.java src/main/java/org/jenkinsci/plugins/p4/tasks/AbstractTask.java http://jenkins-ci.org/commit/p4-plugin/360b789cdc0636531441786c16fa40123c524e0f Log: Trap User Abort and stop Perforce. 
Uses the ‘tick’ function on Progress to check if the Thread has been interrupted. If a user aborts the build then the Perforce connection is dropped at the next tick. 
JENKINS-26650 
Compare: https://github.com/jenkinsci/p4-plugin/compare/7bc19f9ca1b7...360b789cdc06 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [dependency-check-jenkins-plugin] (JENKINS-29908) Male OWASP Dependency-Check Plug-in compatible with Workflow

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-29908 
 
 
 
  Male OWASP Dependency-Check Plug-in compatible with Workflow  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Labels:
 
 workflow 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [hp-operations-orchestration-automation-execution-plugin] (JENKINS-29930) a canceled job doesn't show on the jenkins side

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Remus Golgot commented on  JENKINS-29930 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: a canceled job doesn't show on the jenkins side   
 
 
 
 
 
 
 
 
 
 
Aborting the Jenkins job cannot ( and should not ) influence the OO execution. Once the job is aborted, the OO Build Step does not run anymore and it cannot cancel the OO execution anyway. 
However, if the timeout is reached in the job, the user could in theory choose to automatically cancel the execution and having an option to do so in the Plugin build step would be desirable. This enhancement will be present in a future version of the plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [hp-operations-orchestration-automation-execution-plugin] (JENKINS-29927) Cant pass parameters to flows

2015-08-14 Thread s.dier...@prologistik.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Diercks stopped work on  JENKINS-29927 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Stefan Diercks 
 
 
 

Status:
 
 In Progress Open 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [hp-operations-orchestration-automation-execution-plugin] (JENKINS-29927) Cant pass parameters to flows

2015-08-14 Thread s.dier...@prologistik.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Stefan Diercks started work on  JENKINS-29927 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 

Change By:
 
 Stefan Diercks 
 
 
 

Status:
 
 Open In Progress 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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.

UPDATED HOT LIST (8-14-2015)

2015-08-14 Thread phani

*Hello Partner,*

*This is Phani from Humac Inc.*

*Here is the Updated list of available consultants for your requirements.*

*Please send requirements to ph...@humacinc.com  or
call me at 623-748-1724*

*Name*

*Experience*

*Job Title*

*Location*

*Re Loc.*

*Avail*

*Visa*

*Anushree*

*9+Yrs*

*Sr.SAS (Clinical)*

*Caremore, CA*

*Open*

*Immediately*

*H1B*

*Anu*

*9+Yrs*

*Sr.Hadoop Admin*

*Booz Allen Hamilton *

*Open*

*Immediately*

*H1B*

*Anushree*

*9+Yrs*

*Sr. SAS Programmer*

*Caremore, CA*

*Open*

*Immediately*

*H1B*

*Tripti*

*8 Yrs*

*Sr. Java UI Developer*

*Phoenix , AZ*

*Open*

*Immediately*

*H1B*

*Nuthana*

*8 Yrs*

*Sr.Java developer*

*Phoenix , AZ*

*AZ*

*Immediately*

*H1B*

*Ruchi*

*8+Yrs*

*Sr.Cognos BI dev*

*OH*

*Only NC*

*Immediately*

*H1B*






-- 

-- 
Thanks & Regards  ……… *?*

*Phani *
*HUMAC INC*
*Technical Recruiter*
(623) 748-1724
 ph...@humacinc.com
Gtalk- phani.humacinc

-- 
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] [hp-operations-orchestration-automation-execution-plugin] (JENKINS-29928) when the flow is timed our, the job results with a success.

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Remus Golgot commented on  JENKINS-29928 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: when the flow is timed our, the job results with a success.  
 
 
 
 
 
 
 
 
 
 
This will be done as soon as possible in the current version of the plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [view-job-filters-plugin] (JENKINS-20522) Should use DescriptorVisibilityFilter from JobTypeFilter

2015-08-14 Thread jacob.robertson.w...@gmail.com (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jacob Robertson commented on  JENKINS-20522 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Should use DescriptorVisibilityFilter from JobTypeFilter  
 
 
 
 
 
 
 
 
 
 
Yes please take over from here. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [subversion-plugin] (JENKINS-29597) Subversion plug-in update error - Inconsistent file length

2015-08-14 Thread fmateomarad...@santafe.gov.ar (JIRA)

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Facundo Mateo commented on  JENKINS-29597 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Subversion plug-in update error - Inconsistent file length  
 
 
 
 
 
 
 
 
 
 
Same problem here.  Jenkins : 1.6.24 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [nested-view-plugin] (JENKINS-25315) Nested views do not properly round-trip through REST or CLI due to missing View.owner

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick assigned an issue to Jesse Glick 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-25315 
 
 
 
  Nested views do not properly round-trip through REST or CLI due to missing View.owner  
 
 
 
 
 
 
 
 
 

Change By:
 
 Jesse Glick 
 
 
 

Assignee:
 
 Jesse Glick 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [hp-operations-orchestration-automation-execution-plugin] (JENKINS-29927) Cant pass parameters to flows

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Remus Golgot commented on  JENKINS-29927 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Cant pass parameters to flows  
 
 
 
 
 
 
 
 
 
 
please refer to the plugin guide at : 
https://wiki.jenkins-ci.org/display/JENKINS/HP+Operations+Orchestration+Automation+Execution+Plugin 
in order to understand how to add parameters to an execution 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [view-job-filters-plugin] (JENKINS-20522) Should use DescriptorVisibilityFilter from JobTypeFilter

Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Jesse Glick commented on  JENKINS-20522 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Should use DescriptorVisibilityFilter from JobTypeFilter  
 
 
 
 
 
 
 
 
 
 
It is going on a year now with no movement. Do you intend to maintain this plugin? Should I consider it abandoned and cut a fresh release myself? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [hp-operations-orchestration-automation-execution-plugin] (JENKINS-29929) the new version doesn't add a link to the flow report on OO