date:20140704















































Daniel Beck
 commented on  JENKINS-23683


Jenkins needs to check whether the war's directory is writeable before offering to upgrade















Harald: For me, it was because I installed from RPM and decided I want Jenkins to be auto-upgradeable. So I ran chown jenkins /usr/lib/jenkins/jenkins.war. The button to Upgrade Automatically did appear, as did the exception after I clicked 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] [core] (JENKINS-23683) Jenkins needs to check whether the war's directory is writeable before offering to upgrade













































  
Daniel Beck
 edited a comment on  JENKINS-23683


Jenkins needs to check whether the war's directory is writeable before offering to upgrade
















Harald: For me, it was because I installed from RPM and decided I want Jenkins to be auto-upgradeable. So I ran chown jenkins /usr/lib/jenkins/jenkins.war. The button to Upgrade Automatically did appear, as did the exception after I clicked it. The jenkins user needs write access to the containing folder, as that is where the downloaded file is stored.

An alternative solution have been to download to a guaranteed writable file in the temp dir, but being able to rename the .war to .bak (backup file) before upgrading seems like a good idea as well, so now the button only shows up when the folder is writable as well.



























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] [github-oauth] (JENKINS-23324) GitHub OAuth 0.17 requires private access to all repositories

2014-07-04 Thread m...@mikemcquaid.com (JIRA)















































Mike McQuaid
 commented on  JENKINS-23324


GitHub OAuth 0.17 requires private access to all repositories















Can you just revoke to the old permissions model until you fix this? We're on 0.19 now and it's still asking for access to private repos.



























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







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

[JIRA] [email-ext] (JENKINS-23660) Attached log in Jenkins email incomplete

2014-07-04 Thread reinhard.kar...@unify.com (JIRA)















































Reinhard Karbas
 updated  JENKINS-23660


Attached log in Jenkins email incomplete
















Change By:


Reinhard Karbas
(04/Jul/14 10:37 AM)




Priority:


Minor
Major





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] [email-ext] (JENKINS-23660) Attached log in Jenkins email incomplete

2014-07-04 Thread reinhard.kar...@unify.com (JIRA)















































Reinhard Karbas
 commented on  JENKINS-23660


Attached log in Jenkins email incomplete















The problem is not caused by the newer Jenkins version, but by a bug in the email-ext plugin
I downgraded my plugin from 2.38.1 to 2.37.2.2 and the email is working correctly
The log is zipped, attached and is complete
The problem seems to happen when log files reach a certain size (2 MB?)



























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-7803) Findbugs Plugin does not work with IBM Java

2014-07-04 Thread jdrawn...@nationaltheatre.org.uk (JIRA)















































Martin Kutter
 commented on  JENKINS-7803


Findbugs Plugin does not work with IBM Java 















I tried to reproduce the issue on our system (AIX 7.1.0, Tomcat 7), with the following combinations: 


	IBM JDK 7 SR 6, Jenkins 1.565, Findbugs 4.56
	IBM JDK 6 SR 16, Jenkins 1.565, Findbugs 4.56



The issue did not occur - so it's probably 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-23689) Spot slaves not applying IAM role















































John-Paul Drawneek
 created  JENKINS-23689


Spot slaves not applying IAM role















Issue Type:


Bug



Affects Versions:


current



Assignee:


Francis Upton



Components:


ec2



Created:


04/Jul/14 11:25 AM



Description:


We are using spot slave as well as normal.

Normal slave get their IAM role when they are created, spot instances having them missing.

We use spot request for our Windows testing so we this feature is needed for our workflow.




Project:


Jenkins



Priority:


Major



Reporter:


John-Paul Drawneek

























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] [jenkinswalldisplay] (JENKINS-23620) The periodic refresh shows "loading jobs.."

2014-07-04 Thread l...@foldspace.nu (JIRA)















































Lars Hagström
 commented on  JENKINS-23620


The periodic refresh shows "loading jobs.." 















I believe that I was on 0.6.24 or possibly 0.6.25..



























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







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

[JIRA] [envinject] (JENKINS-23666) Inject environment variables build step uses the wrong property file

2014-07-04 Thread wilco.gre...@ibridge.nl (JIRA)















































Wilco Greven
 updated  JENKINS-23666


Inject environment variables build step uses the wrong property file
















Change By:


Wilco Greven
(04/Jul/14 11:55 AM)




Description:


We have a job that uses an 'inject environment variables' build step to inject environment variables from a property file 'target/build.properties'. This property file was verified to exist in the workspace. At first this worked fine.Then by accident someone created a file /target/build.properties in the root of the file system. What happened next is that the 'inject environment variables' build step would use this new file instead of the file in the job's workspace.
 The cause of this behaviour is that the plugin first tries to resolve the path as a relative path against the current working directory (of the jenkins instance). In our case the current working directory was the root directory, which explains why it used /target/build.properties. Only when this file doesn't exist it will lookup the property file relative to the workspace.



























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







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

[JIRA] [envinject] (JENKINS-23666) Inject environment variables build step uses the wrong property file

2014-07-04 Thread wilco.gre...@ibridge.nl (JIRA)















































Wilco Greven
 updated  JENKINS-23666


Inject environment variables build step uses the wrong property file
















Change By:


Wilco Greven
(04/Jul/14 11:56 AM)




Description:


We have a job that uses an 'inject environment variables' build step to inject environment variables from a property file 'target/build.properties'. This property file was verified to exist in the workspace. At first this worked fine.Then by accident someone created a file /target/build.properties in the root of the file system. What happened next is that the 'inject environment variables' build step would use this new file instead of the file in the job's workspace. The cause of this behaviour is that the plugin first tries to resolve the path as a relative path against the current working directory (of the jenkins instance). In our case the current working directory was the root directory, which explains why it used /target/build.properties. Only when this file doesn't exist it will lookup the property file relative to the workspace.
 My expectation was that relative paths would only be looked up in the workspace.



























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







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

[JIRA] [email-ext] (JENKINS-23660) Attached log in Jenkins email incomplete

2014-07-04 Thread slide.o....@gmail.com (JIRA)















































Alex Earl
 commented on  JENKINS-23660


Attached log in Jenkins email incomplete















Your initial description was incorrect then. You stated it was when you upgraded to a newer version of Jenkins that the issue started happening. It still could be a bug in core, they may have changed the way certain functions work to retrieve the log file. There was a change in 2.38.1 to how the log files were retrieved from 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] [core] (JENKINS-17311) Expand and encourage use of hash syntax in crontabs

2014-07-04 Thread wi...@ceilfors.com (JIRA)















































Wisen Tanasa
 commented on  JENKINS-17311


Expand and encourage use of hash syntax in crontabs















I have written a script to hashify all the jobs: https://github.com/ceilfors/jenkins-scripts/blob/master/scriptler/hashifyAllScmTriggers.groovy. 

It should be available from scriptler catalog once the pull request is accepted.



























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-22525) A Slave disappears every time Jenkins boots up on IBM Java

Martin Kutter
edited a comment on JENKINS-22525

A Slave disappears every time Jenkins boots up on IBM Java

The ConversionException: Could not call hudson.EnvVars.readObject() : Invalid reference above is probably unrelated: It looks like my config had invalid references. After cleaning them up, this message disappeared.

However, the IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" could be the reason for this issue.

I reproduced the issue with Jenkins-1.656 with the following JDKs:

IBM JDK 6 SR 16 on AIX 7.1
IBM JDK 7 SR 6 on AIX 7.1
IBM JDK 7 SR 7 (latest). on AIX 7.1
IBM JDK 7 (build 2.6) on Windows.

In my case, the "missing" slave is always the first slave in the config.xml, so I would assume that loading a Slave from disk (and creating a hudsom.model.Queue$ItemList) does not work the first time,
but works on subsequent tries.

I've also found that the same error is thrown when creating a new slave on a fresh jenkins (on save / doCreateItem):

A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.

Stack trace

javax.servlet.ServletException: java.lang.IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)

The slave is saved nonetheless.

Subsequent slaves can be created without this error.

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-22525) A Slave disappears every time Jenkins boots up on IBM Java

Martin Kutter
commented on JENKINS-22525

A Slave disappears every time Jenkins boots up on IBM Java

However, the IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" could be the reason for this issue.

I reproduced the issue with Jenkins-1.656 with the following JDKs:

IBM JDK 6 SR 16 on AIX 7.1
IBM JDK 7 SR 6 on AIX 7.1
IBM JDK 7 SR 7 (latest). on AIX 7.1
IBM JDK 7 (build 2.6) on Windows.

I've also found that the same error is thrown when creating a new slave on a fresh jenkins (on save / doCreateItem):

Stack trace

The slave is saved nonetheless.

Subsequent slaves can be created without this error.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java

Martin Kutter
edited a comment on JENKINS-22525

A Slave disappears every time Jenkins boots up on IBM Java

However, the IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" could be the reason for this issue.

I reproduced the issue with Jenkins-1.656 with the following JDKs:

IBM JDK 6 SR 16 on AIX 7.1
IBM JDK 7 SR 6 on AIX 7.1
IBM JDK 7 SR 7 (latest). on AIX 7.1
IBM JDK 7 (build 2.6) on Windows.

I've also found that the same error is thrown when creating a new slave on a fresh jenkins (on save / doCreateItem):

Stack trace

The slave is saved nonetheless.

Subsequent slaves can be created without this error.

[JIRA] [core] (JENKINS-22525) A Slave disappears every time Jenkins boots up on IBM Java

Martin Kutter
edited a comment on JENKINS-22525

A Slave disappears every time Jenkins boots up on IBM Java

However, the IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" could be the reason for this issue.

I reproduced the issue with Jenkins-1.656 with the following JDKs:

IBM JDK 6 SR 16 on AIX 7.1
IBM JDK 7 SR 6 on AIX 7.1
IBM JDK 7 SR 7 (latest). on AIX 7.1
IBM JDK 7 (build 2.6) on Windows.

I've also found that the same error is thrown when creating the first slave node on a fresh jenkins instance (on save / doCreateItem):

Stack trace

The slave is saved nonetheless.

Subsequent slaves can be created without this error.

[JIRA] [jobconfighistory] (JENKINS-23527) Job configuration history is missing (not recorded) for some jobs

2014-07-04 Thread stefan.brau...@1und1.de (JIRA)















































Stefan Brausch
 commented on  JENKINS-23527


Job configuration history is missing (not recorded) for some jobs















Sorry, saw this issue to late.
Is already fixed with this pull request: https://github.com/jenkinsci/jobConfigHistory-plugin/pull/34
But isn't released yet.

Workaround is to activate "Save folder configuration changes" in your jenkins system configuration.



























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] [jobconfighistory] (JENKINS-23527) Job configuration history is missing (not recorded) for some jobs

2014-07-04 Thread stefan.brau...@1und1.de (JIRA)
















































Stefan Brausch
 assigned  JENKINS-23527 to Stefan Brausch



Job configuration history is missing (not recorded) for some jobs
















Change By:


Stefan Brausch
(04/Jul/14 2:17 PM)




Assignee:


Mirko Friedenhagen
Stefan Brausch



























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-22525) A Slave disappears every time Jenkins boots up on IBM Java













































  
Martin Kutter
 edited a comment on  JENKINS-22525


A Slave disappears every time Jenkins boots up on IBM Java
















The ConversionException: Could not call hudson.EnvVars.readObject() : Invalid reference above is probably unrelated: It looks like my config had invalid references. After cleaning them up, this message disappeared.

However, the IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue" could be the reason for this issue.

I reproduced the issue with Jenkins-1.656 with the following JDKs:


	IBM JDK 6 SR 16 on AIX 7.1
	IBM JDK 7 SR 6 on AIX 7.1
	IBM JDK 7 SR 7 (latest). on AIX 7.1
	IBM JDK 7 (build 2.6) on Windows.



In my case, the "missing" slave is always the first slave in the config.xml, so I would assume that loading a Slave from disk (and creating a hudsom.model.Queue$ItemList) does not work the first time,
but works on subsequent tries.

I've also found that the same error is thrown when creating the first slave node on a fresh jenkins instance (on save / doCreateItem):


 
Stack trace (excerpt):

Caused by: java.lang.IncompatibleClassChangeError: incompatible InnerClasses attribute between "hudson.model.Queue$ItemList" and "hudson.model.Queue"
	at java.lang.Class.getDeclaringClass(Class.java:821)
	at sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl.(ParameterizedTypeImpl.java:52)
	at sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl.make(ParameterizedTypeImpl.java:95)
	at sun.reflect.generics.factory.CoreReflectionFactory.makeParameterizedType(CoreReflectionFactory.java:105)
	at sun.reflect.generics.visitor.Reifier.visitClassTypeSignature(Reifier.java:140)
	at sun.reflect.generics.tree.ClassTypeSignature.accept(ClassTypeSignature.java:49)
	at sun.reflect.generics.repository.FieldRepository.getGenericType(FieldRepository.java:85)
	at java.lang.reflect.Field.getGenericType(Field.java:237)
	at com.thoughtworks.xstream.mapper.AnnotationMapper.processTypes(AnnotationMapper.java:224)
	at com.thoughtworks.xstream.mapper.AnnotationMapper.processAnnotations(AnnotationMapper.java:182)
	at com.thoughtworks.xstream.mapper.AnnotationMapper.serializedClass(AnnotationMapper.java:129)
	at hudson.util.xstream.MapperDelegate.serializedClass(MapperDelegate.java:39)
	at com.thoughtworks.xstream.mapper.MapperWrapper.serializedClass(MapperWrapper.java:26)
	at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:62)
	at hudson.slaves.NodeList$ConverterImpl.marshal(NodeList.java:151)




The slave is saved nonetheless. 

Subsequent slaves can be created without this error.



























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-23655) Jenkins Windows Service SVN checkout permissions problem
















































Daniel Beck
 resolved  JENKINS-23655 as Not A Defect


Jenkins Windows Service SVN checkout permissions problem
















This is a support request, not a bug report, so resolving as Not A Defect. This should be best handled on IRC or the jenkinsci-users mailing list.

You don't mention that you're restarting the service after changing the user name it runs as, did you forget to do that?





Change By:


Daniel Beck
(04/Jul/14 3:53 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























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







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

[JIRA] [ec2] (JENKINS-23680) New instance types not handled

2014-07-04 Thread cr...@clearbooks.co.uk (JIRA)
















































Craig Bass
 assigned  JENKINS-23680 to Craig Bass



New instance types not handled
















Change By:


Craig Bass
(04/Jul/14 3:55 PM)




Assignee:


Francis Upton
Craig Bass



























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-23680) New instance types not handled

2014-07-04 Thread cr...@clearbooks.co.uk (JIRA)















































Craig Bass
 started work on  JENKINS-23680


New instance types not handled
















Change By:


Craig Bass
(04/Jul/14 3:56 PM)




Status:


Open
In Progress



























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







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

[JIRA] [ec2] (JENKINS-23680) New instance types not handled

2014-07-04 Thread cr...@clearbooks.co.uk (JIRA)















































Craig Bass
 commented on  JENKINS-23680


New instance types not handled















https://github.com/jenkinsci/ec2-plugin/pull/95



























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] [ruby] (JENKINS-23679) Jenkins stops responding















































Daniel Beck
 updated  JENKINS-23679


Jenkins stops responding
















Change By:


Daniel Beck
(04/Jul/14 4:01 PM)




Component/s:


ruby





Component/s:


rvm





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] [core] (JENKINS-23646) Show validation warning on token trigger when anonymous has no read access to current job















































Daniel Beck
 updated  JENKINS-23646


Show validation warning on token trigger when anonymous has no read access to current job
















Edited issue description based on agreement in comments.





Change By:


Daniel Beck
(04/Jul/14 4:07 PM)




Summary:


Build tokens should be replaced by build
Show validation warning on
 token
 root plugin
 trigger when anonymous has no read access to current job





Issue Type:


Task
New Feature





Priority:


Major
Minor





Description:


As it stands -
Jenkins should warn users when
 the
 build
 remote (
 token
 plugin is
) trigger would
 not
 useful in any realistic scenario. As soon as you put any sort of security over jenkins - it will not
 work
 and build token-root plugin will be needed
 (i
.
 Why
e. the job is
 not
 depracate build token plugin
 readable by anonymous)
, and
 make build token root the only replacement
 maybe suggest use of Build Token Root plugin
.
 



























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-23456) I'm getting 23456!!!















































Daniel Beck
 commented on  JENKINS-23456


I'm getting 23456!!!















Can we close this now?



























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-23655) Jenkins Windows Service SVN checkout permissions problem

2014-07-04 Thread jonathan.gr...@renesas.com (JIRA)















































Jonathan Grant
 commented on  JENKINS-23655


Jenkins Windows Service SVN checkout permissions problem















Thanks for your reply.

Yes, I restarted the Service. Also I rebooted since then too.

I've asked on the users list now.



























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







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

[JIRA] [cppcheck] (JENKINS-17450) "warning" and "performance" not counted

2014-07-04 Thread ja...@howeswho.co.uk (JIRA)















































James Howe
 reopened  JENKINS-17450


"warning" and "performance" not counted
















Not fixed as far as I can see in 1.18

I have a report with 1 "error", 93 "warning", 56 "performance" and 152 "style" rows.
However, the summary table lists 0 for "Warning" and "Performance", and 149 for "No category"





Change By:


James Howe
(04/Jul/14 4:30 PM)




Resolution:


Fixed





Status:


Closed
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] [cppcheck] (JENKINS-17450) "warning" and "performance" not counted

2014-07-04 Thread ja...@howeswho.co.uk (JIRA)













































  
James Howe
 edited a comment on  JENKINS-17450


"warning" and "performance" not counted
















Not fixed as far as I can see in 1.18

I have a report with 1 "error", 93 "warning", 56 "performance" and 152 "style" rows.
However, the summary table lists 0 for "Warning" and "Performance", and 149 for "No category".

The Advanced configuration is unchanged from the default, with no thresholds and all boxes ticked.



























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] [shiningpanda] (JENKINS-23690) virtualenv builder doesn't have correct %PATH% set up on windows















































Chris Withers
 created  JENKINS-23690


virtualenv builder doesn't have correct %PATH% set up on windows















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


shiningpanda



Created:


04/Jul/14 4:41 PM



Description:


The virtualenv path in the xshell-type builder appears not to activate properly on Windows, giving the following type of problem:

[75011716] $ cmd.exe /c call C:\Users\jenkins\AppData\Local\Temp\shiningpanda7607611870788630234.bat

C:\Jenkins\workspace\testfixtures-virtualenv\75011716>pip install -e .[test,build] 
'pip' is not recognized as an internal or external command,
operable program or batch file.




Environment:


Jenkins ver. 1.554.3, ShingingPanda 0.21, Mac OS X master, Win7 slave.




Project:


Jenkins



Labels:


plugin
windows




Priority:


Major



Reporter:


Chris Withers

























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] [shiningpanda] (JENKINS-23690) virtualenv builder doesn't have correct %PATH% set up on windows
















































Chris Withers
 resolved  JENKINS-23690 as Duplicate


virtualenv builder doesn't have correct %PATH% set up on windows
















This looks like a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-16176





Change By:


Chris Withers
(04/Jul/14 4:45 PM)




Status:


Open
Resolved





Assignee:


Chris Withers





Resolution:


Duplicate



























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







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

[JIRA] [shiningpanda] (JENKINS-22902) Cannot create virtualenv with python3.4
















































Chris Withers
 closed  JENKINS-22902 as Fixed


Cannot create virtualenv with python3.4
















Verified as working for me, I was experiencing this problem.





Change By:


Chris Withers
(04/Jul/14 4:46 PM)




Status:


Resolved
Closed



























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







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

[JIRA] [shiningpanda] (JENKINS-22968) Cannot build Virtualenvs for Python 3.4
















































Chris Withers
 closed  JENKINS-22968 as Duplicate


Cannot build Virtualenvs for Python 3.4
















See #22902





Change By:


Chris Withers
(04/Jul/14 4:47 PM)




Status:


Resolved
Closed



























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







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

[JIRA] [shiningpanda] (JENKINS-16176) ShiningPanda PATH update uses wrong separator on Windows