[JIRA] [ec2] (JENKINS-18855) EC2 plugin does not work behind proxy server

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 resolved  JENKINS-18855 as Fixed


EC2 plugin does not work behind proxy server
















Change By:


SCM/JIRA link daemon
(28/Jun/14 2:23 AM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ec2] (JENKINS-18855) EC2 plugin does not work behind proxy server

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-18855


EC2 plugin does not work behind proxy server















Code changed in jenkins
User: OHTAKE Tomohiro
Path:
 src/main/java/hudson/plugins/ec2/ssh/EC2UnixLauncher.java
http://jenkins-ci.org/commit/ec2-plugin/e1f37936a18dc3e6a371009c3a6a2ac7d5512c2c
Log:
  [FIXED JENKINS-18855] Enable proxy for SSH to EC2 instance

It uses HTTP proxy defined in Plugin configuration.
SOCKS proxy is not supported.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ec2] (JENKINS-18855) EC2 plugin does not work behind proxy server

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-18855


EC2 plugin does not work behind proxy server















Code changed in jenkins
User: OHTAKE Tomohiro
Path:
 pom.xml
 src/main/java/hudson/plugins/ec2/EC2Cloud.java
http://jenkins-ci.org/commit/ec2-plugin/4ecd4a30587f8f2682a9f0a639cb05b0173c3005
Log:
  JENKINS-18855 Enable proxy for AWS API endpoint

Upgrading Jenkins to 1.447 LTS since `ProxyConfiguration#noProxyHost` was introduced in 1.443.





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ec2] (JENKINS-18855) EC2 plugin does not work behind proxy server

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-18855


EC2 plugin does not work behind proxy server















Code changed in jenkins
User: Francis Upton
Path:
 pom.xml
 src/main/java/hudson/plugins/ec2/EC2Cloud.java
 src/main/java/hudson/plugins/ec2/ssh/EC2UnixLauncher.java
http://jenkins-ci.org/commit/ec2-plugin/d471878724b32b8cc449f7b9be19af509507bf4c
Log:
  Merge pull request #90 from ohtake/18855-proxy

JENKINS-18855 Support HTTP Proxy


Compare: https://github.com/jenkinsci/ec2-plugin/compare/64a8c741d09d...d471878724b3




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [dynamic-search-view] (JENKINS-19588) Automatic refresh flushes the entered filters

[o.v.nenas...@gmail.com (JIRA)]

Oleg Nenashev
 resolved  JENKINS-19588 as Fixed


Automatic refresh flushes the entered filters
















Fixed in 0.2.1





Change By:


Oleg Nenashev
(27/Jun/14 10:51 PM)




Status:


Reopened
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [simple-parameterized-builds-report] (JENKINS-23604) NullPointerException when a project's builds don't all have parameter data

[jwag...@ciena.com (JIRA)]

Justin Wagner
 commented on  JENKINS-23604


NullPointerException when a project's builds don't all have parameter data















I can confirm that on this same Jenkins instance when a project has always had parameters defined for every build I don't get this exception.  So the issue is clearly that the code doesn't handle the case where some builds don't have parameter data.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23470) empty description in CodeMirror preview on Jenkins main page if auto-refresh is enabled

[o.v.nenas...@gmail.com (JIRA)]

Oleg Nenashev
 updated  JENKINS-23470


empty description in CodeMirror preview on Jenkins main page if auto-refresh is enabled
















Change By:


Oleg Nenashev
(27/Jun/14 10:07 PM)




Component/s:


core



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion] (JENKINS-9086) Public key authentication with username fails

[o.v.nenas...@gmail.com (JIRA)]

Oleg Nenashev
 resolved  JENKINS-9086 as Fixed


Public key authentication with username fails
















Change By:


Oleg Nenashev
(27/Jun/14 9:42 PM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion] (JENKINS-16008) .Net based Builds are failing on Slave machine

[o.v.nenas...@gmail.com (JIRA)]

Oleg Nenashev
 resolved  JENKINS-16008 as Won't Fix


.Net based Builds are failing on Slave machine

















"c:\jenkins\workspace\Mesa 4.0\HoldsRadar.sln" (Rebuild;Package target) (1) ->
"c:\jenkins\workspace\Mesa 4.0\HoldsRadar\HoldsRadar.csproj" (Rebuild target) (2) ->
(CoreCompile target) -> 
  HoldsRadar\NotifyTracking.cs(4,32): error CS0234: The type or namespace name 'Lot' does not exist in the namespace 'Micron.Manufacturing.MES' (are you missing an assembly reference?) [c:\jenkins\workspace\Mesa 4.0\HoldsRadar\HoldsRadar.csproj]
  HoldsRadar\MonitorSwrSplit.cs(10,32): error CS0234: The type or namespace name 'SWR' does not exist in the namespace 'Micron.Manufacturing.MES' (are you missing an assembly reference?) [c:\jenkins\workspace\Mesa 4.0\HoldsRadar\HoldsRadar.csproj]

This is a code issue in the project.
Seems it is not related to Jenkins at all





Change By:


Oleg Nenashev
(27/Jun/14 9:39 PM)




Status:


Open
Resolved





Resolution:


Won't Fix



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-23606) Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits

[t...@starmobileinc.com (JIRA)]

Trey Duskin
 updated  JENKINS-23606


Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits
















Change By:


Trey Duskin
(27/Jun/14 9:01 PM)




Description:


We have a single Git repository with several projects in a directory structure.  I have created build jobs with polling enabled for each project and have included the appropriate directory structure in the "Included Regions" option in the git plugin setup.  I have also turned on "Force Polling using Workspace" as indicated in https://issues.jenkins-ci.org/browse/JENKINS-20569.We are using a git-flow type development process, and the jobs are all configured to watch the '*/dev' branch.  All commits made to this branch are merges.  It appears that whenever a merge commit is made, it will trigger all of the jobs, regardless of if the merge only contained changes to one of the projects' directories.I looked into the polling log and it looks like the way that the plugin is getting the commit log and checking the paths may be causing the issue.  Here is the command that the job runs in the polling log: > /usr/bin/git log --full-history --no-abbrev --format=raw -M -m --raw ff0ec94a066cee23c13faa16b38b247911cd5ee7..f47993565f701a4f28174c4ea81f35d0e1103590If I run this command manually, I can see that the returned paths for each commit also includes paths from other commits.  I'm not sure why this is, but from the 'git' documentation, it looks like the '
\
-m' parameter will do a full diff on both parents of a merge commit.  If I leave off the '-m' parameter, or if I include '
\
-
\
-first-parent', the list of paths in the commits only shows the actual affected files made by the commit which triggered the job.  Perhaps this option needs to be included in the job config?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-23606) Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits

[mark.earl.wa...@gmail.com (JIRA)]

Mark Waite
 updated  JENKINS-23606


Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits
















Change By:


Mark Waite
(27/Jun/14 9:02 PM)




Component/s:


git-client



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered

[t...@starmobileinc.com (JIRA)]

Trey Duskin
 commented on  JENKINS-20569


Polling with excluded regions don't prevent job triggered















Thanks.  I did some more experimentation and I think my issue is specific to merge commits.  My new bug is here: https://issues.jenkins-ci.org/browse/JENKINS-23606



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-23606) Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits

[t...@starmobileinc.com (JIRA)]

Trey Duskin
 created  JENKINS-23606


Git Polling Jobs with Included Regions being triggered unnecessarily with merge commits















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git



Created:


27/Jun/14 8:58 PM



Description:


We have a single Git repository with several projects in a directory structure.  I have created build jobs with polling enabled for each project and have included the appropriate directory structure in the "Included Regions" option in the git plugin setup.  I have also turned on "Force Polling using Workspace" as indicated in https://issues.jenkins-ci.org/browse/JENKINS-20569.

We are using a git-flow type development process, and the jobs are all configured to watch the '*/dev' branch.  All commits made to this branch are merges.  It appears that whenever a merge commit is made, it will trigger all of the jobs, regardless of if the merge only contained changes to one of the projects' directories.

I looked into the polling log and it looks like the way that the plugin is getting the commit log and checking the paths may be causing the issue.  Here is the command that the job runs in the polling log:

 > /usr/bin/git log --full-history --no-abbrev --format=raw -M -m --raw ff0ec94a066cee23c13faa16b38b247911cd5ee7..f47993565f701a4f28174c4ea81f35d0e1103590

If I run this command manually, I can see that the returned paths for each commit also includes paths from other commits.  I'm not sure why this is, but from the 'git' documentation, it looks like the 'm' parameter will do a full diff on both parents of a merge commit.  If I leave off the '-m' parameter, or if I include '-first-parent', the list of paths in the commits only shows the actual affected files made by the commit which triggered the job.  Perhaps this option needs to be included in the job config?




Environment:


Git Plugin 2.2.2, client plugin 1.9.1, Jenkins 1.568




Project:


Jenkins



Priority:


Minor



Reporter:


Trey Duskin

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-21747) Artifact archiving fails with java.lang.NoClassDefFoundError

[gabe.bl...@jdsu.com (JIRA)]

Gabriel Black
 commented on  JENKINS-21747


Artifact archiving fails with java.lang.NoClassDefFoundError















Saw this same issue when upgrading.  Downgrading fixed it.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jclouds-jenkins] (JENKINS-17891) Add floating IP support and ability to set the keyPairName to openstack-nova cloud.

[foudil.bre...@in2p3.fr (JIRA)]

foudil foudil
 commented on  JENKINS-17891


Add floating IP support and ability to set the keyPairName to openstack-nova cloud.















This has been partially resolved by PR #43, which adds KeyPairName and FloatingIP attributes to templates.

But still, the master tries to ssh to the private IP, where as it should try to ssh to the floating IP in the first place.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered

[mark.earl.wa...@gmail.com (JIRA)]

Mark Waite
 commented on  JENKINS-20569


Polling with excluded regions don't prevent job triggered















Trey Duskin could you open a separate bug report for your use case?

This bug report is focused on excluded regions and on the implicit requirement that include and exclude regions implicitly require "Force polling using workspace".  As far as I can tell, the exclude regions are working as expected (at least as described by this bug report) so long as "Force polling using workspace" is enabled.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22529) IndexOutOfBoundsException in executor threads

[fdewee...@cloudmark.com (JIRA)]

Frederik Deweerdt
 commented on  JENKINS-22529


IndexOutOfBoundsException in executor threads















Done: https://github.com/jenkinsci/jenkins/pull/1300

Thanks,
Frederik



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22529) IndexOutOfBoundsException in executor threads

[dan...@beckweb.net (JIRA)]

Daniel Beck
 commented on  JENKINS-22529


IndexOutOfBoundsException in executor threads















Frederik: Please consider submitting a pull request on Github.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22529) IndexOutOfBoundsException in executor threads

[fdewee...@cloudmark.com (JIRA)]

  
Frederik Deweerdt
 edited a comment on  JENKINS-22529


IndexOutOfBoundsException in executor threads
















Hi,

I'm seeing this with an even older version: 1.480.3. The trace is slightly difference, but similar:
java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
at java.util.ArrayList.rangeCheck(ArrayList.java:571)
at java.util.ArrayList.get(ArrayList.java:349)
at hudson.model.queue.MappingWorksheet$ReadOnlyList.get(MappingWorksheet.java:102)
at hudson.model.queue.MappingWorksheet$ExecutorChunk.execute(MappingWorksheet.java:150)
at hudson.model.queue.MappingWorksheet$ExecutorChunk.access$000(MappingWorksheet.java:110)
at hudson.model.queue.MappingWorksheet$Mapping.execute(MappingWorksheet.java:298)
at hudson.model.Queue.maintain(Queue.java:1045)
at hudson.model.Queue.pop(Queue.java:863)
at hudson.model.Executor.grabJob(Executor.java:285)
at hudson.model.Executor.run(Executor.java:206)
more info

In particular, the MappingWorksheet bits are the same.

This issue https://issues.jenkins-ci.org/browse/JENKINS-19799 seems to be exactly the same as well, and I agree with the assement made there: if isAvailable is false, there's nothing preventing 'e' to go out of bounds in ExecutorChunk.execute().

Attaching a patch against lastest git



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22529) IndexOutOfBoundsException in executor threads

[fdewee...@cloudmark.com (JIRA)]

Frederik Deweerdt
 updated  JENKINS-22529


IndexOutOfBoundsException in executor threads
















Make sure e doesn't go out of bounds.





Change By:


Frederik Deweerdt
(27/Jun/14 6:54 PM)




Attachment:


patch-22529



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22529) IndexOutOfBoundsException in executor threads

[fdewee...@cloudmark.com (JIRA)]

Frederik Deweerdt
 commented on  JENKINS-22529


IndexOutOfBoundsException in executor threads















Hi,

I'm seeing this with an even older version: 1.480.3. The trace is slightly difference, but similar:
java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
at java.util.ArrayList.rangeCheck(ArrayList.java:571)
at java.util.ArrayList.get(ArrayList.java:349)
at hudson.model.queue.MappingWorksheet$ReadOnlyList.get(MappingWorksheet.java:102)
at hudson.model.queue.MappingWorksheet$ExecutorChunk.execute(MappingWorksheet.java:150)
at hudson.model.queue.MappingWorksheet$ExecutorChunk.access$000(MappingWorksheet.java:110)
at hudson.model.queue.MappingWorksheet$Mapping.execute(MappingWorksheet.java:298)
at hudson.model.Queue.maintain(Queue.java:1045)
at hudson.model.Queue.pop(Queue.java:863)
at hudson.model.Executor.grabJob(Executor.java:285)
at hudson.model.Executor.run(Executor.java:206)
more info

In particular, the MappingWorksheet bits are the same.

This issue https://issues.jenkins-ci.org/browse/JENKINS-19799 seems to be exactly the same as well, and I agree with the assement made there: if isAvailable is false, there's nothing preventing 'e' to go out of bounds in ExecutorChunk.execute().

Here's a patch against current git:
diff --git a/core/src/main/java/hudson/model/queue/MappingWorksheet.java b/core/src/main/java/hudson/model/queue/MappingWorksheet.java
index 0e21fa3..0516161 100644
— a/core/src/main/java/hudson/model/queue/MappingWorksheet.java
+++ b/core/src/main/java/hudson/model/queue/MappingWorksheet.java
@@ -159,9 +159,12 @@ public class MappingWorksheet {
 assert capacity() >= wc.size();
 int e = 0;
 for (SubTask s : wc) {

	while (!get(e).isAvailable())
+while (e < size() && !get(e).isAvailable()) {
 e++;
-get(e++).set(wuc.createWorkUnit(s));
+		}
+		if (e < size()) {
+get(e++).set(wuc.createWorkUnit(s));
+		}
 }
 }
 }





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-22529) IndexOutOfBoundsException in executor threads

[fdewee...@cloudmark.com (JIRA)]

  
Frederik Deweerdt
 edited a comment on  JENKINS-22529


IndexOutOfBoundsException in executor threads
















Hi,

I'm seeing this with an even older version: 1.480.3. The trace is slightly difference, but similar:
java.lang.IndexOutOfBoundsException: Index: 1, Size: 1
at java.util.ArrayList.rangeCheck(ArrayList.java:571)
at java.util.ArrayList.get(ArrayList.java:349)
at hudson.model.queue.MappingWorksheet$ReadOnlyList.get(MappingWorksheet.java:102)
at hudson.model.queue.MappingWorksheet$ExecutorChunk.execute(MappingWorksheet.java:150)
at hudson.model.queue.MappingWorksheet$ExecutorChunk.access$000(MappingWorksheet.java:110)
at hudson.model.queue.MappingWorksheet$Mapping.execute(MappingWorksheet.java:298)
at hudson.model.Queue.maintain(Queue.java:1045)
at hudson.model.Queue.pop(Queue.java:863)
at hudson.model.Executor.grabJob(Executor.java:285)
at hudson.model.Executor.run(Executor.java:206)
more info

In particular, the MappingWorksheet bits are the same.

This issue https://issues.jenkins-ci.org/browse/JENKINS-19799 seems to be exactly the same as well, and I agree with the assement made there: if isAvailable is false, there's nothing preventing 'e' to go out of bounds in ExecutorChunk.execute().

Here's a patch against current git:
{{
diff --git a/core/src/main/java/hudson/model/queue/MappingWorksheet.java b/core/src/main/java/hudson/model/queue/MappingWorksheet.java
index 0e21fa3..0516161 100644
— a/core/src/main/java/hudson/model/queue/MappingWorksheet.java
+++ b/core/src/main/java/hudson/model/queue/MappingWorksheet.java
@@ -159,9 +159,12 @@ public class MappingWorksheet {
 assert capacity() >= wc.size();
 int e = 0;
 for (SubTask s : wc) {

	while (!get(e).isAvailable())
+while (e < size() && !get(e).isAvailable()) {
 e++;
-get(e++).set(wuc.createWorkUnit(s));
+		}
+		if (e < size()) {
+get(e++).set(wuc.createWorkUnit(s));
+		}
 }
 }
 }
}}





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [android-emulator] (JENKINS-12821) android.device

[roberto.andr...@gmail.com (JIRA)]

Roberto Andrade
 commented on  JENKINS-12821


android.device 















I reopened https://issues.jenkins-ci.org/browse/JENKINS-11952 as it seems to be a better fit for the issue description, but I think it might have been caused by the changes that fixed this issue.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [android-emulator] (JENKINS-7693) Problem detecting that emulator is started.

[roberto.andr...@gmail.com (JIRA)]

Roberto Andrade
 commented on  JENKINS-7693


Problem detecting that emulator is started.















I'm seeing the same behavior again and reopened https://issues.jenkins-ci.org/browse/JENKINS-11952



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb

[roberto.andr...@gmail.com (JIRA)]

Roberto Andrade
 reopened  JENKINS-11952


Emulator occasionally hangs indefinitely on startup, unable to connect adb
















Seeing this again with the latest Android Emulator plugin (2.11.1), Jenkins (1.569) and Android SDK (rev 23).


[android] Using Android SDK: /Users/Shared/Jenkins/Home/tools/android-sdk
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb start-server
[android] Starting Android emulator
[android] Erasing existing emulator data...
$ /Users/Shared/Jenkins/Home/tools/android-sdk/tools/emulator -no-boot-anim -ports 5818,5819 -avd jenkins -no-snapshot-load -no-snapshot-save -wipe-data
* daemon not running. starting it now on port 5820 *
* daemon started successfully *
HAX is working and emulator runs in fast virt mode
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
[android] Waiting for emulator to finish booting...
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb -s emulator-5818 shell getprop dev.bootcomplete
error: device offline
error: device offline
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb -s emulator-5818 shell getprop dev.bootcomplete
error: device offline
error: device offline
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb -s emulator-5818 shell getprop dev.bootcomplete
error: device offline
error: device offline
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb disconnect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb -s emulator-5818 shell getprop dev.bootcomplete
error: device offline
error: device offline
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb -s emulator-5818 shell getprop dev.bootcomplete
error: device offline
error: device offline
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb -s emulator-5818 shell getprop dev.bootcomplete
error: device offline
error: device offline
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb disconnect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb -s emulator-5818 shell getprop dev.bootcomplete
error: device offline
error: device offline
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb -s emulator-5818 shell getprop dev.bootcomplete
error: device offline
error: device offline
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb -s emulator-5818 shell getprop dev.bootcomplete
error: device offline
error: device offline
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb disconnect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb -s emulator-5818 shell getprop dev.bootcomplete
error: device offline
error: device offline
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb -s emulator-5818 shell getprop dev.bootcomplete
error: device offline
error: device offline
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb -s emulator-5818 shell getprop dev.bootcomplete
error: device offline
error: device offline
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb disconnect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb -s emulator-5818 shell getprop dev.bootcomplete
error: device offline
error: device offline
$ /Users/Shared/Jenkins/Home/tools/android-sdk/platform-tools/adb connect emulator-5818
$ /Users/Shared/Jenkins/Home/to

[JIRA] [core] (JENKINS-23543) Launchctl does not load Jenkins on OS X 10.10 Yosemite

[dan...@beckweb.net (JIRA)]

Daniel Beck
 commented on  JENKINS-23543


Launchctl does not load Jenkins on OS X 10.10 Yosemite















Right, please remember to update this issue once it's been released.

Just looked at the error message... 0xd is hex for carriage return in ASCII – are you using Windows line breaks in your LaunchDaemon/LaunchAgent plist file? Could well be a coincidence, but maybe not.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [delivery-pipeline] (JENKINS-23605) Support for sidebar links

[pmatig...@successfactors.com (JIRA)]

Patrice Matignon
 updated  JENKINS-23605


Support for sidebar links
















Change By:


Patrice Matignon
(27/Jun/14 5:50 PM)




Labels:


link sidebar



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [delivery-pipeline] (JENKINS-23605) Support for sidebar links

[pmatig...@successfactors.com (JIRA)]

Patrice Matignon
 created  JENKINS-23605


Support for sidebar links















Issue Type:


Bug



Affects Versions:


current



Assignee:


Patrik Boström



Components:


delivery-pipeline, sidebar-link



Created:


27/Jun/14 5:49 PM



Description:


The Sidebar-links plugin lets the admin define custom links showing in the left margin area. This works fine in most view types, but the delivery pipeline views do not display these links unfortunately.

Quick note (may or may not be relevant to the fix here) a pending improvement for the sidebar-link plugin is to allow per-view links, or custom inks that are specific to each view (currently, it's global for all views), so most likely the Edit View screen will have to include a section provided by the sidebar-link plugin.




Project:


Jenkins



Priority:


Minor



Reporter:


Patrice Matignon

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed

[ever...@free.fr (JIRA)]

evernat
 resolved  JENKINS-23442 as Cannot Reproduce


Jenkins 1.568 can not start when monitoring plugin is installed
















OK, so I resolve as can not reproduce. Please reopen if you reproduce.

My test was with monitoring plugin v1.51 and Jenkins 1.568.
I think that your issue was something "temporary", since many users probably have the same versions as you.





Change By:


evernat
(27/Jun/14 5:05 PM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [android-emulator] (JENKINS-12821) android.device

[roberto.andr...@gmail.com (JIRA)]

Roberto Andrade
 commented on  JENKINS-12821


android.device 















I just upgraded to 2.11(.1) specifically because I started having this issue recently and am now facing another weird one which seems related:

After the plugin starts the emulator, its subsequent attempts to "connect" to it fail and ends up timing out. I see the emulator window available, but the sequence of "adb connect emulator-" and "adb -s emulator- shell getprop dev.bootcomplete" keeps on failing with a "error: device offline" error.

any tips as to what could be the problem?




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [simple-parameterized-builds-report] (JENKINS-23604) NullPointerException when a project's builds don't all have parameter data

[jwag...@ciena.com (JIRA)]

Justin Wagner
 created  JENKINS-23604


NullPointerException when a project's builds don't all have parameter data















Issue Type:


Bug



Assignee:


Unassigned


Components:


simple-parameterized-builds-report



Created:


27/Jun/14 4:14 PM



Description:


Here is the relevant part of the NullPointerException report:


Caused by: java.lang.NullPointerException
	at com.nullin.jenkins.spbr.SimpleParameterizedBuildsReportAction.getParameterValues(SimpleParameterizedBuildsReportAction.java:102)
	at com.nullin.jenkins.spbr.SimpleParameterizedBuildsReportAction.getBuildsMap(SimpleParameterizedBuildsReportAction.java:76)
	at com.nullin.jenkins.spbr.SimpleParameterizedBuildsReportAction$getBuildsMap.call(Unknown Source)
	at com.nullin.jenkins.spbr.SimpleParameterizedBuildsReportAction.index.showTable(index.groovy:24)
	at com.nullin.jenkins.spbr.SimpleParameterizedBuildsReportAction.index.this$6$showTable(index.groovy)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)






Environment:


Project was created without the "This build is parameterized" option, a few builds were ran, and then the parameter option got turned on and a few more builds were ran.




Project:


Jenkins



Priority:


Major



Reporter:


Justin Wagner

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gradle-jpi-plugin] (JENKINS-23603) instance-identity dependency is missing

[m...@daniel-spilker.com (JIRA)]

Daniel Spilker
 commented on  JENKINS-23603


instance-identity dependency is missing















See https://github.com/jenkinsci/gradle-jpi-plugin/pull/9 for a fix.

I tested the fix with the job-dsl-plugin. The plugin still builds with core 1.480 and also with 1.509: https://github.com/jenkinsci/job-dsl-plugin/tree/build-with-higher-core



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gradle-jpi-plugin] (JENKINS-23603) instance-identity dependency is missing

[m...@daniel-spilker.com (JIRA)]

Daniel Spilker
 commented on  JENKINS-23603


instance-identity dependency is missing















I think the problem is that the instance-identity module is excluded in JpiPlugin for the jenkinsTest configuration.

https://github.com/jenkinsci/gradle-jpi-plugin/blob/000f571032d83e8da098459a94cf54098d0afc68/src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy#L259



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [gradle-jpi-plugin] (JENKINS-23603) instance-identity dependency is missing

[m...@daniel-spilker.com (JIRA)]

Daniel Spilker
 created  JENKINS-23603


instance-identity dependency is missing















Issue Type:


Bug



Assignee:


abayer



Components:


gradle-jpi-plugin



Created:


27/Jun/14 3:04 PM



Description:


The job-dsl-plugin currently uses the gradle-jpi-plugin with jenkins-core 1.480 and everything is fine. But when trying to update to jenkins-core 1.509, all tests using JenkinsRule fail because the class org.jenkinsci.main.modules.instance_identity.InstanceIdentity is missing.


INFO: Loaded all jobs
Jun 27, 2014 4:59:18 PM hudson.ExtensionFinder$GuiceFinder 
SEVERE: Failed to create Guice container from all the plugins
com.google.common.collect.ComputationException: java.lang.NoClassDefFoundError: Lorg/jenkinsci/main/modules/instance_identity/InstanceIdentity;
at com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:887)
at com.google.inject.internal.FailableCache.get(FailableCache.java:49)
at com.google.inject.internal.MembersInjectorStore.get(MembersInjectorStore.java:66)
at com.google.inject.internal.ConstructorInjectorStore.createConstructor(ConstructorInjectorStore.java:73)
at com.google.inject.internal.ConstructorInjectorStore.access$000(ConstructorInjectorStore.java:29)
at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:36)
at com.google.inject.internal.ConstructorInjectorStore$1.create(ConstructorInjectorStore.java:33)
at com.google.inject.internal.FailableCache$1.apply(FailableCache.java:38)
at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:356)
at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:182)
at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:151)
at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:67)
at com.google.common.collect.MapMaker$ComputingMapAdapter.get(MapMaker.java:883)
at com.google.inject.internal.FailableCache.get(FailableCache.java:49)
at com.google.inject.internal.ConstructorInjectorStore.get(ConstructorInjectorStore.java:49)
at com.google.inject.internal.ConstructorBindingImpl.initialize(ConstructorBindingImpl.java:127)
at com.google.inject.internal.InjectorImpl.initializeBinding(InjectorImpl.java:506)
at com.google.inject.internal.AbstractBindingProcessor$Processor$1.run(AbstractBindingProcessor.java:171)
at com.google.inject.internal.ProcessedBindingData.initializeBindings(ProcessedBindingData.java:44)
at com.google.inject.internal.InternalInjectorCreator.initializeStatically(InternalInjectorCreator.java:123)
at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
at com.google.inject.Guice.createInjector(Guice.java:94)
at com.google.inject.Guice.createInjector(Guice.java:71)
at hudson.ExtensionFinder$GuiceFinder.(ExtensionFinder.java:282)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:374)
at net.java.sezpoz.IndexItem.instance(IndexItem.java:181)
at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:625)
at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:600)
at hudson.ExtensionFinder._find(ExtensionFinder.java:151)
at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:318)
at hudson.ExtensionList.load(ExtensionList.java:295)
at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248)
at hudson.ExtensionList.iterator(ExtensionList.java:138)
at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:311)
at hudson.ExtensionList.loa

[JIRA] [nunit] (JENKINS-14864) NUnit Plugin 0.14 - won't merge multiple xmls

[a...@lycus.org (JIRA)]

Alex Rønne Petersen
 commented on  JENKINS-14864


NUnit Plugin 0.14 - won't merge multiple xmls















We are having this issue in the Mono project too. We run thousands of tests for each .NET profile (2.0, 4.0, 4.5, etc) and the results from previous profiles appear to be overwritten by profiles tested later in the process.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered

[t...@starmobileinc.com (JIRA)]

Trey Duskin
 commented on  JENKINS-20569


Polling with excluded regions don't prevent job triggered















Oh, and to be clear, I am only using Included Paths.  I am not specifying any Excluded Paths.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-21437) Failed to update /computer/xxxxxxxxxxx/builds

[fjmartinsan...@gmail.com (JIRA)]

Fran Martín
 commented on  JENKINS-21437


Failed to update /computer/xxx/builds















Hello, the same to me when I upgrade to 1.554.2:

uname -p
x86_64
java -version
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit Server VM (build 19.1-b02, mixed mode)
 




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [update-center] (JENKINS-21872) Cannot update jenkins up to 1.543 --- builds history crashes.

[fjmartinsan...@gmail.com (JIRA)]

  
Fran Martín
 edited a comment on  JENKINS-21872


Cannot update jenkins up to 1.543  --- builds history crashes.
















-



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [update-center] (JENKINS-21872) Cannot update jenkins up to 1.543 --- builds history crashes.

[fjmartinsan...@gmail.com (JIRA)]

Fran Martín
 commented on  JENKINS-21872


Cannot update jenkins up to 1.543  --- builds history crashes.















Hello,

The same to me in Centos and when I upgrade to 1.554.2.




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [accurev] (JENKINS-13817) Jenkins Displays Accurev Password in Logs

[davidcsim...@gmail.com (JIRA)]

David Simmon
 commented on  JENKINS-13817


Jenkins Displays Accurev Password in Logs















I too have found this password unmasked in the emails that are sent.  I've never used GitHub, so I don't know if this is something I can look for, and submit a but fix too, but I wanted to add where I was seeing this issue.

We had a network connectivity issue, and when it sent an email that the build failed it included the command that was executed twice.  The first time it masked the password.
Authenticating with Accurev server...
[workspace] $ "C:\Program Files (x86)\AccuRev\bin\accurev.exe" login -H ACCUREVSERVERNAME:5050 dsimmon 

Then at the bottom of the email it dumped out the full command with the password unmasked.
FATAL: login ("C:\Program Files (x86)\AccuRev\bin\accurev.exe" login -H ACCUREVSERVERNAME:5050 dsimmon UNMASKEDPASSWORDWASDISPLAYEDHERE) failed with exit code 1




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered

[t...@starmobileinc.com (JIRA)]

Trey Duskin
 commented on  JENKINS-20569


Polling with excluded regions don't prevent job triggered















My case differs from your example in a few ways.

First, my jobs are set up to only check out a specific branch (e.g. '*/dev' instead of 'master').  There could be other commits in the history which are going into other branches, but I don't care about those and I only want to watch for commits in a specific branch which have changes in specific paths.

Second, we are using git-flow style development, and so most of the commits are merges of feature branches into the the branch I am watching.

If I look at the git polling log on a job which should not have been triggered, I can see it trying to get a history between the last build revision and the commit which triggered the poll (we are using web-hooks from our git provider, Assembla).  However, if I repeat the command it uses to get the commit history (e.g. /usr/bin/git log --full-history --no-abbrev --format=raw -M -m --raw ff0ec94a066cee23c13faa16b38b247911cd5ee7..f47993565f701a4f28174c4ea81f35d0e1103590), I see the commits i expect, but weirdly, I also see a commit listed twice - once containing the paths which the commit affected, and another (same hash) which contain paths from some other commit in some other branch!  Is this a problem with my git provider?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23543) Launchctl does not load Jenkins on OS X 10.10 Yosemite

[daniel....@fuegoondemand.com (JIRA)]

Daniel Roy
 commented on  JENKINS-23543


Launchctl does not load Jenkins on OS X 10.10 Yosemite















It works fine on official releases of OS X.  Care or not, I thought it was worth logging in case the problem persists after the final release of Yosemite.  



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23176) IBM J9 seems to be unsupported on Jenkins

[blue.jag...@hotmail.com (JIRA)]

John Tal
 commented on  JENKINS-23176


IBM J9 seems to be unsupported on Jenkins















Hi Daniel, thanks for the hint/reminder about running specific jobs to specific JDK.  We are now able to build what we need to under IBM J9.  The criticality of this issue is lessened for us.  And now others who come to this issue will also have a workaround.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [sitemonitor] (JENKINS-23602) Site Monitor Plugin changes

[k.govindra...@accenture.com (JIRA)]

kalaivanan govindarajan
 created  JENKINS-23602


Site Monitor Plugin changes















Issue Type:


Improvement



Affects Versions:


current



Assignee:


cliffano



Components:


sitemonitor



Created:


27/Jun/14 1:20 PM



Description:


I am planning to extend site monitoring plugin to show machine/server name details in the site monitor report. The main motive of the change is that i have my application code that is deployed in multiple servers and my load balancer handles the request .So we need to make sure that the health monitoring is done on which particular server ,this server name will be shown in a new td column (Server name). 




Environment:


Windows Machine. Jenkins is running as a windows Service.




Fix Versions:


current



Project:


Jenkins



Labels:


plugin




Priority:


Major



Reporter:


kalaivanan govindarajan

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [tap] (JENKINS-17488) java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult

[s...@wapice.com (JIRA)]

Sami Paavilainen
 commented on  JENKINS-17488


java.lang.ClassCastException: org.tap4j.model.TestResult cannot be cast to org.tap4j.model.TestResult















We're also seeing this in our setup, Jenkins 1.567 with TAP Plugin 1.18 and TestLink plugin 3.10.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [jobgenerator] (JENKINS-23575) Post-Build-Step "Publish Cppcheck results" not available in job generator project

[lukas.goorm...@dlr.de (JIRA)]

Lukas Goormann
 assigned  JENKINS-23575 to Sylvain Benner



Post-Build-Step "Publish Cppcheck results" not available in job generator project
















Guess its not too difficult, but I have no experience in any Jenkins Plugin Programming...





Change By:


Lukas Goormann
(27/Jun/14 12:00 PM)




Assignee:


Sylvain Benner



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [perforce] (JENKINS-23599) Perforce plugin should replace variables from matrix configuration

[krizleeb...@java.net (JIRA)]

krizleebear
 commented on  JENKINS-23599


Perforce plugin should replace variables from matrix configuration















I tested CloudBees build #126 and it works like a charm! Thanks for this extremely useful improvement! So now I'm really looking forward to the official release! 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [redmine] (JENKINS-18110) even the redmine project exists the pluging marks all builds as failure

[jenkins...@dev-eth0.de (JIRA)]

Alex Muthmann
 commented on  JENKINS-18110


even the redmine project exists the pluging marks all builds as failure















You can find the fix on github and build the plugin with maven: https://github.com/deveth0/redmine-plugin 

or download a prebuild version from my site: https://dev-eth0.de/?attachment_id=2008



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [redmine] (JENKINS-23483) java.lang.NoSuchMethodError: com.taskadapter.redmineapi.RedmineManager.getTransport()

[jenkins...@dev-eth0.de (JIRA)]

Alex Muthmann
 commented on  JENKINS-23483


java.lang.NoSuchMethodError: com.taskadapter.redmineapi.RedmineManager.getTransport()















You can find the fix on github and build the plugin with maven: https://github.com/deveth0/redmine-plugin 

or download a prebuild version from my site: https://dev-eth0.de/?attachment_id=2008



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ssh-slaves] (JENKINS-13237) Unsuccessful SSH slave start do not timeout and cannot be retry, even manually

[kay.abendr...@epages.com (JIRA)]

Kay Abendroth
 commented on  JENKINS-13237


Unsuccessful SSH slave start do not timeout and cannot be retry, even manually















Log entries for that slave that look unusual:

Jun 26, 2014 11:52:36 PM com.cloudbees.jenkins.support.SupportPlugin$ComputerListenerImpl onOnline
WARNING: Could not install root log handler on node: cd-vm-test-master-01
hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
	at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41)
	at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34)
	at hudson.remoting.Request.call(Request.java:174)
	at hudson.remoting.Channel.call(Channel.java:739)
	at com.cloudbees.jenkins.support.SupportPlugin$ComputerListenerImpl.onOnline(SupportPlugin.java:480)
	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:512)
	at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:349)
	at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:712)
	at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:498)
	at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:232)
	at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:744)
Caused by: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown
	at hudson.remoting.Request.abort(Request.java:299)
	at hudson.remoting.Channel.terminate(Channel.java:802)
	at hudson.remoting.Channel$CloseCommand.execute(Channel.java:951)
	at hudson.remoting.Channel$2.handle(Channel.java:475)
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60)
Caused by: hudson.remoting.Channel$OrderlyShutdown
	... 3 more
Caused by: Command close created at
	at hudson.remoting.Command.(Command.java:56)
	at hudson.remoting.Channel$CloseCommand.(Channel.java:945)
	at hudson.remoting.Channel$CloseCommand.(Channel.java:943)
	at hudson.remoting.Channel.close(Channel.java:1026)
	at hudson.remoting.Channel.close(Channel.java:1009)
	at hudson.remoting.Channel$CloseCommand.execute(Channel.java:950)
	... 2 more




Jun 26, 2014 8:53:19 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run
SEVERE: I/O error in channel cd-vm-test-master-01
java.io.IOException: Unexpected termination of the channel
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50)
Caused by: java.io.EOFException
	at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325)
	at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794)
	at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801)
	at java.io.ObjectInputStream.(ObjectInputStream.java:299)
	at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40)
	at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [ssh-slaves] (JENKINS-13237) Unsuccessful SSH slave start do not timeout and cannot be retry, even manually

[kay.abendr...@epages.com (JIRA)]

Kay Abendroth
 commented on  JENKINS-13237


Unsuccessful SSH slave start do not timeout and cannot be retry, even manually















I don't think this is related to JENKINS-13131 as the description there indicates the slave connection will be established after 15 to 20 minutes eventually.

We're facing the same issue (as described within here) in our environment:

	a test node is configured being connected to via SSH (In demand delay: 3, Idle delay: 5),
	a Job loads a virtual machine snapshot and triggers another Job, which triggers the In demand delay,
	this leads to the following behavior sometimes:
	
		On the slave detail page you see the icon blinking and
		the message This node is being launched appears, but
		in reality nothing happens or some kind of endless connection attempt is being made. Logging into the machine via SSH from local workstation works.
		Clicking on the button Relaunch slave agent in Jenkins doesn't help.
		Only workaround for us so far: Restarting Jenkins.
	
	





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Images and links not coming

[merlin]

Hello,

In my jenkins, no images nor the links are coming, it seems whole page is
broken
Any help

Thank You



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Images-and-links-not-coming-tp4708369.html
Sent from the Jenkins issues mailing list archive at Nabble.com.

-- 
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-23437) NPE when binding JSON form data without 'properties' field

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-23437


NPE when binding JSON form data without 'properties' field















Code changed in jenkins
User: Oleg Nenashev
Path:
 changelog.html
http://jenkins-ci.org/commit/jenkins/0b260dad8c26268f3fc01e1d6016712053645130
Log:
  Noting #1296 an #1280 (FIXED JENKINS-23437)

Signed-off-by: Oleg Nenashev 





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8

[kessler.mich...@gmx.net (JIRA)]

miks miks
 commented on  JENKINS-18935


Make Subversion plugin support Subversion 1.8















+1 need it too



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [perforce] (JENKINS-23599) Perforce plugin should replace variables from matrix configuration

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 resolved  JENKINS-23599 as Fixed


Perforce plugin should replace variables from matrix configuration
















Change By:


SCM/JIRA link daemon
(27/Jun/14 10:24 AM)




Status:


Open
Resolved





Resolution:


Fixed



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [perforce] (JENKINS-23599) Perforce plugin should replace variables from matrix configuration

[o.v.nenas...@gmail.com (JIRA)]

Oleg Nenashev
 commented on  JENKINS-23599


Perforce plugin should replace variables from matrix configuration
















Master Job checkout behaviour:
As there is currently no way to omit the checkout in the Master Matrix Job, the first value of the axes should be used.

SCMCheckoutStrategy allows to implement such feature.
Implementation: https://wiki.jenkins-ci.org/display/JENKINS/Extension+points#Extensionpoints-jenkins.scm.SCMCheckoutStrategy
AFAIK, there was an issue for the new strategy implementation

Commit in Perforce: https://github.com/jenkinsci/perforce-plugin/commit/a35f1fe507ac86a08f857fe0e03a36d658a66138




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [perforce] (JENKINS-23599) Perforce plugin should replace variables from matrix configuration

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-23599


Perforce plugin should replace variables from matrix configuration















Code changed in jenkins
User: Oleg Nenashev
Path:
 src/main/java/hudson/plugins/perforce/utils/MacroStringHelper.java
http://jenkins-ci.org/commit/perforce-plugin/a35f1fe507ac86a08f857fe0e03a36d658a66138
Log:
  [FIXED JENKINS-23599] - Substitute Matrix Axis values in PerforceSCM

Behavior:

	MatrixConfiguration: Inject Values
	MatrixProject: Inject the first value or empty string if it is not available



Signed-off-by: Oleg Nenashev 





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [audit-trail] (JENKINS-23601) Modify Audit Trail plugin to log information based on user type

[silas.jonat...@gmail.com (JIRA)]

David Thomas
 created  JENKINS-23601


Modify Audit Trail plugin to log information based on user type















Issue Type:


Improvement



Assignee:


Unassigned


Components:


audit-trail



Created:


27/Jun/14 10:01 AM



Description:


I believe, the plugin would currently log activities as per configuration. This includes actions of all the users.

I'm looking at having a configuration where we could tell the plugin by passing on a configuration to log only the admin users or all authenticated users or any users based on the roles mapped to each of them.




Project:


Jenkins



Priority:


Major



Reporter:


David Thomas

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [android-emulator] (JENKINS-23600) SDK repositories and emulator images do not install

[tilen.faga...@me.com (JIRA)]

Tilen Faganel
 created  JENKINS-23600


SDK repositories and emulator images do not install 















Issue Type:


Bug



Affects Versions:


current



Assignee:


Christopher Orr



Components:


android-emulator



Created:


27/Jun/14 9:53 AM



Description:


Google has updated its Android SDK Platform-tools to version 20 and since then, whenever I do a first time setup of the Android SDK, the plugin automatically uses the latest version and that seems to break the installation of the android/google support repositories and emulator images (ABI).

---

My emulator settings:



---

Console:

Downloading and installing Android SDK from http://dl.google.com/android/android-sdk_r22.6.2-linux.tgz
[android] Base SDK installed successfully
[android] Going to install required Android SDK components...
[android] Installing the 'platform-tool' SDK component(s)...
$ /var/lib/jenkins/tools/android-sdk/tools/android update sdk -u -a -t platform-tool
Refresh Sources:
  Fetching https://dl-ssl.google.com/android/repository/addons_list-2.xml
  Validate XML
  Parse XML
  Fetched Add-ons List successfully
  Refresh Sources
  Fetching URL: https://dl-ssl.google.com/android/repository/repository-9.xml
  Validate XML: https://dl-ssl.google.com/android/repository/repository-8.xml
  Parse XML:https://dl-ssl.google.com/android/repository/repository-8.xml
  Fetching URL: https://dl-ssl.google.com/android/repository/addon.xml
  Validate XML: https://dl-ssl.google.com/android/repository/addon.xml
  Fetching URL: https://dl-ssl.google.com/android/repository/addon-6.xml
  Validate XML: https://dl-ssl.google.com/android/repository/addon-6.xml
  Parse XML:https://dl-ssl.google.com/android/repository/addon-6.xml
  Fetching URL: https://dl-ssl.google.com/glass/gdk/addon.xml
  Validate XML: https://dl-ssl.google.com/glass/gdk/addon.xml
  Parse XML:https://dl-ssl.google.com/glass/gdk/addon.xml
  Fetching URL: https://dl-ssl.google.com/android/repository/extras/intel/addon.xml
  Validate XML: https://dl-ssl.google.com/android/repository/extras/intel/addon.xml
  Parse XML:https://dl-ssl.google.com/android/repository/extras/intel/addon.xml
  Fetching URL: https://dl-ssl.google.com/android/repository/sys-img/android/sys-img.xml
  Validate XML: https://dl-ssl.google.com/android/repository/sys-img/android/sys-img.xml
  Fetching URL: https://dl-ssl.google.com/android/repository/sys-img/android-wear/sys-img.xml
  Validate XML: https://dl-ssl.google.com/android/repository/sys-img/android-wear/sys-img.xml
  Fetching URL: https://dl-ssl.google.com/android/repository/sys-img/android-tv/sys-img.xml
  Validate XML: https://dl-ssl.google.com/android/repository/sys-img/android-tv/sys-img.xml
  Fetching URL: https://dl-ssl.google.com/android/repository/sys-img/x86/addon-x86.xml
  Validate XML: https://dl-ssl.google.com/android/repository/sys-img/x86/addon-x86.xml
  Parse XML:https://dl-ssl.google.com/android/repository/sys-img/x86/addon-x86.xml
Refresh Sources:
  Fetching URL: https://dl-ssl.google.com/android/repository/addon.xml
  Validate XML: https://dl-ssl.google.com/android/repository/addon.xml
  Fetching URL: https://dl-ssl.google.com/android/repository/sys-img/android/sys-img.xml
  Validate XML: https://dl-ssl.google.com/android/repository/sys-img/android/sys-img.xml
  Fetching URL: https://dl-ssl.google.com/android/repository/sys-img/android-wear/sys-img.xml
  Validate XML: https://dl-ssl.google.com/android/repository/sys-img/android-wear/sys-img.xml
  Fetching URL: https://dl-ssl.google.com/android/repository/sys-img/android-tv/sys-img.xml
  Validate XML: https://dl-ssl.google.com/android/repository/sys-img/android-tv/sys-img.xml
---
License id: android-sdk-license-5be876d5
Used by: 

	Android SDK Platform-tools, revision 20
---



Installing Archives:
  Preparing to install archives
  Downloading Android SDK Platform-tools, revision 20
  Installing Android SDK Platform-tools, revision 20

[JIRA] [perforce] (JENKINS-23599) Perforce plugin should replace variables from matrix configuration

[krizleeb...@java.net (JIRA)]

krizleebear
 created  JENKINS-23599


Perforce plugin should replace variables from matrix configuration















Issue Type:


Improvement



Assignee:


Oleg Nenashev



Components:


perforce



Created:


27/Jun/14 9:46 AM



Description:


It would be nice to be able to build software from different branches using matrix configuration.

I would like to have a parameter in the client view map, like this:

//mib2_com/${BRANCH}/sqlite3/... //WRK/sqlite3/...

and this should be replaced with the actual branch, e.g. "dev/main", "rel/2014", ...

Master Job checkout behaviour:
As there is currently no way to omit the checkout in the Master Matrix Job, the first value of the axes should be used.

As we're doing a lot of branches in our company, I would appreciate this behaviour a lot! This would make our configuration so much more light weight 


Thanks in advance,
Christian




Environment:


Linux, Perforce




Project:


Jenkins



Priority:


Major



Reporter:


krizleebear

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [mailer] (JENKINS-23598) Expose a few more (crucial) SMTP properties

[viktor.be...@kishonti.net (JIRA)]

Viktor Berke
 created  JENKINS-23598


Expose a few more (crucial) SMTP properties















Issue Type:


Bug



Assignee:


Unassigned


Components:


mailer



Created:


27/Jun/14 9:45 AM



Description:


Hi,

Office 365 servers are notorious for their slow responses. Recently I get a lot of these:


ERROR: Could not connect to SMTP host: podx.outlook.com, port: 587
javax.mail.MessagingException: Could not connect to SMTP host: podx.outlook.com, port: 587;
  nested exception is:
java.net.SocketTimeoutException: connect timed out
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1934)
at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:638)
at javax.mail.Service.connect(Service.java:317)
at javax.mail.Service.connect(Service.java:176)
at javax.mail.Service.connect(Service.java:125)
at javax.mail.Transport.send0(Transport.java:194)
at javax.mail.Transport.send(Transport.java:124)
at hudson.tasks.MailSender.execute(MailSender.java:117)
at hudson.tasks.Mailer.perform(Mailer.java:137)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776)
at hudson.model.Build$BuildExecution.post2(Build.java:183)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725)
at hudson.model.Run.execute(Run.java:1709)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
Caused by: java.net.SocketTimeoutException: connect timed out
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:579)
at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:286)
at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:231)
at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1900)
... 17 more
Finished: FAILURE

So now I'd like to increase the SMTP timeout value but apparently that's not possible as of now.

Another ugly problem is that Office 365 uses STARTTLS without SMTPS so to make mailer work I gotta hack on /etc/default/jenkins and add -Dmail.smtp.starttls.enable=true to JAVA_ARGS otherwise it won't work. (Hmm, come to think of it, timeout might also be set this way, too...)

So all I ask for is to expose the mail.smtp.connectiontimeout, mail.smtp.timeout and mail.smtp.starttls.enable properties under settings instead of always using the Java defaults.

Thanks in advance!

Viktor




Environment:


Ubuntu 13.10 x64

Jenkins 1.554.2

Mailer 1.8




Project:


Jenkins



Labels:


smtp
timeout
starttls




Priority:


Major



Reporter:


Viktor Berke

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more 

[JIRA] [gui] (JENKINS-23595) makeFlash applies fill to alpha channel

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-23595


makeFlash applies fill to alpha channel















Code changed in jenkins
User: Harald Albers
Path:
 war/images/makeFlash.sh
http://jenkins-ci.org/commit/jenkins/a43b96341410e9095ccd70f35cb658cc6e3f7112
Log:
  Merge pull request #1299 from kbeal/master

JENKINS-23595 - Fix makeFlash script bug with ImageMagick v6.7.9+


Compare: https://github.com/jenkinsci/jenkins/compare/5ab3742d528d...a43b96341410




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-restrictions] (JENKINS-23597) Job restrictions based on folders plugin (job restrictions plugin, folders plugin)

[scm_issue_l...@java.net (JIRA)]

SCM/JIRA link daemon
 commented on  JENKINS-23597


Job restrictions based on folders plugin (job restrictions plugin, folders plugin)















Code changed in jenkins
User: Oleg Nenashev
Path:
 src/main/java/com/synopsys/arc/jenkinsci/plugins/jobrestrictions/util/QueueHelper.java
http://jenkins-ci.org/commit/job-restrictions-plugin/574cc4f631e01018ba7d54fe30c83192cfdd7895
Log:
  Merge pull request #4 from joakimahle/master

JENKINS-23597 - General full path support


Compare: https://github.com/jenkinsci/job-restrictions-plugin/compare/abc856c9d289...574cc4f631e0




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-restrictions] (JENKINS-23597) Job restrictions based on folders plugin (job restrictions plugin, folders plugin)

[o.v.nenas...@gmail.com (JIRA)]

Oleg Nenashev
 updated  JENKINS-23597


Job restrictions based on folders plugin (job restrictions plugin, folders plugin)
















PR: https://github.com/jenkinsci/job-restrictions-plugin/pull/4





Change By:


Oleg Nenashev
(27/Jun/14 8:50 AM)




URL:


https://github.com/jenkinsci/job-restrictions-plugin/pull/4



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-restrictions] (JENKINS-23597) Job restrictions based on folders plugin (job restrictions plugin, folders plugin)

[o.v.nenas...@gmail.com (JIRA)]

Oleg Nenashev
 assigned  JENKINS-23597 to Joakim Ahle



Job restrictions based on folders plugin (job restrictions plugin, folders plugin)
















Change By:


Oleg Nenashev
(27/Jun/14 8:50 AM)




Assignee:


Joakim Ahle



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-restrictions] (JENKINS-23597) Job restrictions based on folders plugin (job restrictions plugin, folders plugin)

[o.v.nenas...@gmail.com (JIRA)]

Oleg Nenashev
 started work on  JENKINS-23597


Job restrictions based on folders plugin (job restrictions plugin, folders plugin)
















Change By:


Oleg Nenashev
(27/Jun/14 8:51 AM)




Status:


Open
In Progress



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [JIRA] Closed: (JENKINS-10455) Klocwork plugin running on linux master cannot retrieve report files from windows slave

[ciprian_vintea01]

Hello,
I still have the same problem with version 1.15 (latest version). Did I
mistake something?
 



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/JIRA-Created-JENKINS-10455-Klocwork-plugin-running-on-linux-master-cannot-retrieve-report-files-frome-tp3695692p4708349.html
Sent from the Jenkins issues mailing list archive at Nabble.com.

-- 
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] [klocwork] (JENKINS-10455) Klocwork plugin running on linux master cannot retrieve report files from windows slave

[ciprian.vin...@continental-corporation.com (JIRA)]

Ciprian Vintea
 commented on  JENKINS-10455


Klocwork plugin running on linux master cannot retrieve report files from windows slave















One correction from the previous comment. I thought that 1.2 is 1.20. So I'm using the latest version and I still have this problem. Some ideas? Thanks.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [core] (JENKINS-23442) Jenkins 1.568 can not start when monitoring plugin is installed

[jbrej...@praqma.net (JIRA)]

Jens  Brejner
 commented on  JENKINS-23442


Jenkins 1.568 can not start when monitoring plugin is installed















It was probably 1.50.0, I had to remove it to be able to work. But please resolve case if you can not reproduce with current Jenkins version and latest plugin version.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [klocwork] (JENKINS-10455) Klocwork plugin running on linux master cannot retrieve report files from windows slave

[ciprian.vin...@continental-corporation.com (JIRA)]

Ciprian Vintea
 commented on  JENKINS-10455


Klocwork plugin running on linux master cannot retrieve report files from windows slave















Hello, I also have the problem reported with version 1.15. I can't find any other new version (1.2 for example). What should I do?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-restrictions] (JENKINS-23597) Job restrictions based on folders plugin (job restrictions plugin, folders plugin)

[joakim.a...@sonymobile.com (JIRA)]

Joakim Ahle
 updated  JENKINS-23597


Job restrictions based on folders plugin (job restrictions plugin, folders plugin)
















Change By:


Joakim Ahle
(27/Jun/14 7:39 AM)




Description:


When using job restrictions plugin, I want to be able to restrict slaves to only run jobs that are in a certain folder. This should be an easy change.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [job-restrictions] (JENKINS-23597) Job restrictions based on folders plugin (job restrictions plugin, folders plugin)

[joakim.a...@sonymobile.com (JIRA)]

Joakim Ahle
 created  JENKINS-23597


Job restrictions based on folders plugin (job restrictions plugin, folders plugin)















Issue Type:


Improvement



Assignee:


Unassigned


Components:


job-restrictions, plugin



Created:


27/Jun/14 7:38 AM



Project:


Jenkins



Priority:


Major



Reporter:


Joakim Ahle

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [credentials] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.

[dan...@beckweb.net (JIRA)]

Daniel Beck
 reopened  JENKINS-22542


Subversion polling not work with externals or variables in URL -  E200015: No credential to try.
















That 'Additional Credentials' is required for a default location does not make sense. It's only a workaround, the bug remains.





Change By:


Daniel Beck
(27/Jun/14 7:26 AM)




Resolution:


Fixed





Status:


Resolved
Reopened



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] [build-pipeline] (JENKINS-21188) Build Pipeline Plugin (1.4.2) throws ServletException: Need to log in to access for not-logged in users

[janis.balo...@gmail.com (JIRA)]

Jānis Balodis
 commented on  JENKINS-21188


Build Pipeline Plugin (1.4.2) throws ServletException: Need to log in to access  for not-logged in users















Also same problem.

The combination to reproduce this problem is:

	Jenkins 1.554.2
	Build pipeline plugin 1.4.2 or higher. I tried it with 1.4.3 and 1.4.4-snapshot (27.06.2014)
	Enabled security with 'Role-Based Strategy'




	Create a global role for all users with Overall: read, Job: discovery, View: read permission and assign it to all your users;
	Create project roles with Job: read and whatever else you need and assign it selected users;
	Create a build pipeline view and you will get the error for all the users who do not have Job: read for the job with build pipeline.



Works like a charm with Build pipeline v 1.4.1



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.