[JIRA] [slave-setup] (JENKINS-22006) Slave not persistent in 1.532.2 stable release
Martin Kutter commented on JENKINS-22006 Slave not persistent in 1.532.2 stable release I'm running Jenkins-1.532.2 LTS on Tomcat 7 with IBM JDK 7 on AIX, and I'm unable to reproduce this. Are the slaves written to config.xml in JENKINS_HOME? Are there errors in Catalina.out on startup? I had something similar with all views disappearing - turned out that my config.xml had a corrupted entry (bad reference), and Jenkins didn't load anything past this entry. Does the error also occur with a fresh Jenkins (no previous 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] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
Mantas Balnys commented on JENKINS-23693 Cannot delete workspace Same here: ERROR: Cannot delete workspace: java.io.IOException: Cannot run program "": java.io.IOException: error=13, Permission denied Note that by default xml is saved as: Though that does not change the behavior of the plugin. I would recommend to 1st check for null, 2nd trim leading trailing spaces and check for empty string. 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-23722) Anonymous treated like "Everybody" no as just Anonymous
Igor Pavlov edited a comment on JENKINS-23722 Anonymous treated like "Everybody" no as just Anonymous Do you want to see only configurable jobs in ListViews. If yes, you can just... 1) Create a view with permission filters you need 2) Make this view default in Jenkins global configuration I should have different default views for each Project role. I'm suppose that's not possible? For me Anonymous user is deanonymised, when he's authorized. Why not add user special user? Probably the best solution here is to have 3 default user's by behavior than: 1. Anonymous 2. Everyone 3. authenticated I understand the need for backward compatibility since 2008 so it's impossible to change Anonymous and authenticated names. But probably it is possible to add user for real Anonymous case? Like that: 1. notauthenticated → is really Anonymous 2. Anonymous → is really Everyone 3. authenticated → is really authenticated 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-23722) Anonymous treated like "Everybody" no as just Anonymous
Igor Pavlov commented on JENKINS-23722 Anonymous treated like "Everybody" no as just Anonymous not sure if the name (notauthenticated) for not logged in user that I've suggested is good, but I hope you get my point 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-23722) Anonymous treated like "Everybody" no as just Anonymous
Igor Pavlov commented on JENKINS-23722 Anonymous treated like "Everybody" no as just Anonymous Do you want to see only configurable jobs in ListViews. If yes, you can just... 1) Create a view with permission filters you need 2) Make this view default in Jenkins global configuration I should have several default views for each Project role. I'm suppose that's not possible? For me Anonymous user is deanonymised, when he's authorized. Why not add user special user? Probably the best solution here is to have 3 default user's by behavior than: 1. Anonymous 2. Everyone 3. authenticated I understand the need for backward compatibility since 2008 so it's impossible to change Anonymous and authenticated names. But probably it is possible to add user for real Anonymous case? Like that: 1. notauthenticated → is really Anonymous 2. Anonymous → is really Everyone 3. authenticated → is really authenticated 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] [conditional-buildstep] (JENKINS-23719) Adding a system groovy conditional build step causes "angry jenkins" stacktrace
Oleg Nenashev updated JENKINS-23719 Adding a system groovy conditional build step causes "angry jenkins" stacktrace Change By: Oleg Nenashev (09/Jul/14 5:28 AM) Assignee: Dominik Bartholdi Component/s: conditional-buildstep Component/s: groovy Component/s: 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-23722) Anonymous treated like "Everybody" no as just Anonymous
Oleg Nenashev commented on JENKINS-23722 Anonymous treated like "Everybody" no as just Anonymous The behavior has been introduced by JENKINS-2745. Currently, this behavior is being widely used, so the fix won't be reverted Do you want to see only configurable jobs in ListViews. If yes, you can just... 1) Create a view with permission filters you need 2) Make this view default in Jenkins global 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] [core] (JENKINS-23722) Anonymous treated like "Everybody" no as just Anonymous
Oleg Nenashev updated JENKINS-23722 Anonymous treated like "Everybody" no as just Anonymous Change By: Oleg Nenashev (09/Jul/14 5:21 AM) Labels: security Component/s: core Component/s: security 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] [security] (JENKINS-23722) Anonymous treated like "Everybody" no as just Anonymous
Igor Pavlov created JENKINS-23722 Anonymous treated like "Everybody" no as just Anonymous Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: security Created: 09/Jul/14 4:26 AM Description: Probably renewal of bug https://issues.jenkins-ci.org/browse/JENKINS-2745 Also I am using Role Strategy plugin https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin I need a global permission to Anonymous user to see all jobs and download artifacts For each Project Role group I want to have only jobs, that are possible to edit etc. So: Anonymous have Global overall read access and jobs read access. authenticated user have only Global overall read + Project role access to all project pattern jobs. Expected: When not logged in all jobs readonly When logged in only configurable jobs are present Actual: When not logged in all jobs readonly When logged in all jobs are present No easy workaround is present. Environment: Platform: All, OS: All Project: Jenkins Priority: Major Reporter: Igor Pavlov 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-23721) fix out-of-order builds does not use custom build record root dir
Steve Roth
created JENKINS-23721
fix out-of-order builds does not use custom build record root dir
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
09/Jul/14 3:10 AM
Description:
Using version 1.570 along with a custom build record root dir (under configure system, at the top, under advanced...) I noticed that the 'fix out-of-order builds' action is not using the custom build record root dir.
Settings:
home dir: /foo/jenkins
workspace root dir: /foo/jenkinsworkspace/${ITEM_FULLNAME}
build record root dir: /foo/jenkinsarchive/${ITEM_FULLNAME}/builds
Output example:
Renaming /foo/jenkinsarchive/somejob/builds/2014-03-03_20-00-42
-> /foo/jenkins/jobs/somejob/outOfOrderBuilds/2014-03-03_20-00-42
Project:
Jenkins
Priority:
Minor
Reporter:
Steve Roth
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-22205) Jenkins failed to rotate log error -- unable to delete .nfsxxxxx file with NAS Build Record Root directory
Steve Roth commented on JENKINS-22205 Jenkins failed to rotate log error -- unable to delete .nfsx file with NAS Build Record Root directory I have not seen this issue in more than a month – closing as CNR. 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-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Steve Roth closed JENKINS-21905 as Cannot Reproduce intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream Change By: Steve Roth (09/Jul/14 3:01 AM) Status: Open Closed 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] [core] (JENKINS-22205) Jenkins failed to rotate log error -- unable to delete .nfsxxxxx file with NAS Build Record Root directory
Steve Roth closed JENKINS-22205 as Cannot Reproduce Jenkins failed to rotate log error -- unable to delete .nfsx file with NAS Build Record Root directory Change By: Steve Roth (09/Jul/14 3:02 AM) Status: Open Closed 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] [core] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream
Steve Roth commented on JENKINS-21905 intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream I have not seen this in more than a month – closing. 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] [subversion] (JENKINS-23320) "No subversion jobs using repository" for only one of several SVN repos
chikigai commented on JENKINS-23320 "No subversion jobs using repository" for only one of several SVN repos I am experiencing the same issue using Jenkins 1.554.3 + Subversion Plugin 2.4 + Windows7. 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] [hipchat] (JENKINS-23720) jenkins hipchat plugin does not support hosted hipchat
Andy Sagax created JENKINS-23720 jenkins hipchat plugin does not support hosted hipchat Issue Type: Bug Assignee: Unassigned Components: hipchat Created: 09/Jul/14 12:54 AM Description: if you host your own hipchat (beta feature) jenkins hipchat plugin does not support any way to put in a custom url for the api call. Project: Jenkins Priority: Major Reporter: Andy Sagax 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] [parameterized-trigger] (JENKINS-23717) Add link to specific build ID in console output
ikedam updated JENKINS-23717 Add link to specific build ID in console output Change By: ikedam (09/Jul/14 12:19 AM) Issue Type: Bug Improvement 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-timeout] (JENKINS-21543) "Likely stuck" timed out the build after 0 minutes
ikedam commented on JENKINS-21543 "Likely stuck" timed out the build after 0 minutes I cannot get what's a problem. It looks work correct. 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-22777) Pass in Flag to indicate if Jenkins "Emergency reroute" is non-blank
Frank Merrow commented on JENKINS-22777 Pass in Flag to indicate if Jenkins "Emergency reroute" is non-blank Just a reminder: hoping to see this addressed in next release . . . it there an ETA on when that release might be done? 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] (JENKINS-23661) github webhook failing
Nukul Bhasin edited a comment on JENKINS-23661 github webhook failing I explained here what exactly happened here. https://github.com/github/github-services/commit/19a3c876e483e2470f21f756ac9ee0499b5c4322#diff-96256a1827d9dfd0cd6a1f068b18831dR12 I will put up a new fix for the plugin, for now the change in github services will suffice to get folks rolling. 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] (JENKINS-23661) github webhook failing
Nukul Bhasin commented on JENKINS-23661 github webhook failing https://github.com/github/github-services/commit/19a3c876e483e2470f21f756ac9ee0499b5c4322#diff-96256a1827d9dfd0cd6a1f068b18831dR12 I will put up a new fix for the plugin, for now the change in github services will suffice to get folks rolling. 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] (JENKINS-23662) Github Plugin 1.9 broke webhook trigger
Steve Jansen commented on JENKINS-23662 Github Plugin 1.9 broke webhook trigger Duplicate of JENKINS-23661 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] (JENKINS-23661) github webhook failing
Steve Jansen commented on JENKINS-23661 github webhook failing Good news, it looks like the GitHub service for the "Jenkins (GitHub plugin)" was just updated. The change @ https://github.com/github/github-services/blame/master/lib/services/jenkins_github.rb#L16 looks like it will fix this problem for the plugin v1.9. I'm not sure if this change is live on GitHub.com, or if you will need to recreate the Jenkins service on the "Webhooks & Services" setting panel @ https://github.com/:org-or-user/:repo/settings/hooks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23718) Unable to use ${NODE_NAME} as a Workspace name
Ryan Hummer
updated JENKINS-23718
Unable to use ${NODE_NAME} as a Workspace name
Change By:
Ryan Hummer
(08/Jul/14 11:14 PM)
Description:
When trying to use ${NODE_NAME} as a value for the workspace name
in a Static workspace behavior environment,
and running
a
the
job the following error will output from the job:{quote}17:15:16 Building remotely on build117 in workspace c:\trees17:15:18 Unable to setup workspace: java.lang.Exception: Undefined workspace: ${NODE_NAME}{quote}We used this functionality with the other Perforce Plugin as we generally do not lock our jobs to specific machines. We would like to see this behavior exist with the new plugin 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] [p4] (JENKINS-23718) Unable to use ${NODE_NAME} as a Workspace name
Ryan Hummer
assigned JENKINS-23718 to Paul Allen
Unable to use ${NODE_NAME} as a Workspace name
Change By:
Ryan Hummer
(08/Jul/14 11:12 PM)
Assignee:
Paul Allen
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23718) Unable to use ${NODE_NAME} as a Workspace name
Ryan Hummer
updated JENKINS-23718
Unable to use ${NODE_NAME} as a Workspace name
Change By:
Ryan Hummer
(08/Jul/14 10:41 PM)
Description:
When trying to use ${NODE_NAME} as a value for the workspace name and running a job the following error will output from the job:{
code
quote
}17:15:16 Building remotely on build117 in workspace c:\trees17:15:18 Unable to setup workspace: java.lang.Exception: Undefined workspace: ${NODE_NAME}{
code
quote
}We used this functionality with the other Perforce Plugin as we generally do not lock our jobs to specific machines. We would like to see this behavior exist with the new plugin 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] [core] (JENKINS-23098) Slaves hanging with Maven jobs
Tony Bridges commented on JENKINS-23098 Slaves hanging with Maven jobs That latter hang, by the way, is not present with the maven plugin 2.1 after a downgrade. That might be a useful data point. 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-23098) Slaves hanging with Maven jobs
Tony Bridges commented on JENKINS-23098 Slaves hanging with Maven jobs This looks very similar to what I am seeing on Windows master/slave running 1.554.3 with maven plugin 2.4. I'm also seeing a particular maven job (not all) consistently hanging up after metadata collection. 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] [plugin] (JENKINS-23719) Adding a system groovy conditional build step causes "angry jenkins" stacktrace
Christian Goetze created JENKINS-23719 Adding a system groovy conditional build step causes "angry jenkins" stacktrace Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: plugin Created: 08/Jul/14 10:22 PM Description: Caused by: java.lang.IllegalArgumentException: Failed to convert the scriptSource parameter of the constructor public hudson.plugins.groovy.SystemGroovy(hudson.plugins.groovy.ScriptSource,java.lang.String,java.lang.String) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:686) at org.kohsuke.stapler.RequestImpl.access$100(RequestImpl.java:81) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:587) Environment: 1.558 Jenkins 1.15 Groovy Plugin 1.3.3 Conditional Buildstep Plugin Project: Jenkins Priority: Major Reporter: Christian Goetze This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-23718) Unable to use ${NODE_NAME} as a Workspace name
Ryan Hummer
created JENKINS-23718
Unable to use ${NODE_NAME} as a Workspace name
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
p4
Created:
08/Jul/14 10:22 PM
Description:
When trying to use ${NODE_NAME} as a value for the workspace name and running a job the following error will output from the job:
17:15:16 Building remotely on build117 in workspace c:\trees
17:15:18 Unable to setup workspace: java.lang.Exception: Undefined workspace: ${NODE_NAME}
We used this functionality with the other Perforce Plugin as we generally do not lock our jobs to specific machines. We would like to see this behavior exist with the new plugin as well.
Project:
Jenkins
Priority:
Major
Reporter:
Ryan Hummer
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] [parameterized-trigger] (JENKINS-23717) Add link to specific build ID in console output
David Ishee updated JENKINS-23717 Add link to specific build ID in console output Change By: David Ishee (08/Jul/14 9:49 PM) Environment: Jenkins 1.554.3 parameterized-trigger plugin 2.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] [parameterized-trigger] (JENKINS-23717) Add link to specific build ID in console output
David Ishee created JENKINS-23717 Add link to specific build ID in console output Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger Created: 08/Jul/14 9:48 PM Description: When I am using the parametrized trigger plugin and I trigger a new build of another job, the console output says something like this: Triggering a new build of COMMON-Start-Stop #5366 The COMMON-Start-Stop text is a link, but the build ID isn't. I would like to have the build ID be a link to the console output of that build. The build ID info was there in order to print it, so it should be an easy fix. We call the "COMMON-Start-Stop" job with parameters for the node to run on, and it might get called many times. You have to remember the build ID when you click on the "COMMON-Start-Stop" link if you want to investigate the console output. Environment: Jenkins 1.554.3 Project: Jenkins Priority: Major Reporter: David Ishee 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] (JENKINS-23661) github webhook failing
Chris Manson commented on JENKINS-23661 github webhook failing Thanks @Gennady, I never even knew you could roll back a plugin version! I also got a little snagged by not restarting Jenkins after the downgrade. I'm all back up and running again though so thanks to both of you This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17459) Little red/yellow/green icons should get you to Console everywhere
evernat updated JENKINS-17459 Little red/yellow/green icons should get you to Console everywhere And changing this issue to be a priority bug (not an improvement). 2 against 1 is not a valid argument. But consistency in web usability is certainly a valid argument. Daniel, consider this change back as an encouragement. After all, we are just discussing with you about a link or not a link on a bullet in a web page. Change By: evernat (08/Jul/14 9:23 PM) Issue Type: Improvement Bug 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] (JENKINS-23661) github webhook failing
Gennady Feldman commented on JENKINS-23661 github webhook failing Rolling back to 1.8 solved the issue for me. 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] (JENKINS-23661) github webhook failing
Gennady Feldman edited a comment on JENKINS-23661 github webhook failing Rolling back to 1.8 solved the issue for me. Thanks for the tip @steve. 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] (JENKINS-23661) github webhook failing
Andrew Manson commented on JENKINS-23661 github webhook failing @steve are you saying that there is some sort of workaround for this? Are there any known workarounds or are we just waiting for a fix? We're quite eager for a fix on this one so if there is anything I can do to help out just let me know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-23134) Mixed separators fail for Linux paths
Diego Costantini commented on JENKINS-23134 Mixed separators fail for Linux paths Windows master, 2 Ubuntu slaves. 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-23134) Mixed separators fail for Linux paths
Josh Cohen commented on JENKINS-23134 Mixed separators fail for Linux paths The master is running Windows, and I have two slaves (one Linux and one Mac OSX) running builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-23716) View not correctly displaying branches of the workflow
Jeff Fiser created JENKINS-23716 View not correctly displaying branches of the workflow Issue Type: Bug Affects Versions: current Assignee: Patrik Boström Attachments: Screen Shot 2014-07-08 at 1.06.08 PM.png Components: delivery-pipeline Created: 08/Jul/14 8:56 PM Description: View does not correctly display branches of workflow when more than one project in the workflow has the same downstream project. This is not a circular reference issue and can be demonstrated like this. The workflow starts with the A project: A --> B --> D --> C --> D --> D See the attachment for a visual on how the Build Pipeline displays this (side by side with delivery pipeline). Due Date: 31/Jul/14 12:00 AM Environment: Redhat Enterprise 6.5 / Java 1.7 / Apache Project: Jenkins Labels: plugin Priority: Major Reporter: Jeff Fiser 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-23134) Mixed separators fail for Linux paths
Christopher Orr commented on JENKINS-23134 Mixed separators fail for Linux paths I haven't been able to reproduce this problem so far. For people having this issue, what OS is the master running on, and where are builds running? If on separate slaves, which OS are they using? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldapemail] (JENKINS-5492) Security issue ("Bind Password" text field should be a password field on config page)
SCM/JIRA link daemon
commented on JENKINS-5492
Security issue ("Bind Password" text field should be a password field on config page)
Code changed in jenkins
User: Yukun Su
Path:
pom.xml
src/main/java/com/mtvi/plateng/hudson/ldap/Configuration.java
src/main/resources/com/mtvi/plateng/hudson/ldap/PluginImpl/config.jelly
src/test/java/com/mtvi/plateng/hudson/ldap/BaseLdapSearchTestCase.java
src/test/java/com/mtvi/plateng/hudson/ldap/LdapSearchTest.java
http://jenkins-ci.org/commit/ldapemail-plugin/2f20ffd213601a4d7545c8b2d382c430e0ecc24b
Log:
[FIXED JENKINS-5492] Hide & encrypt Bind Password.
Hide the Bind Password by changing text field to password field in config.jelly.
Encrypt the Bind Password by changing password type from String to Secret.
Upgrade the core version to 1.436 in pom.xml file to support JDK 7 or higher and
to use jenkinsRule in the LdapSearchTest.
Add jenkinsRule and annotations for the tests to solve the NullPointer Exception
caused by password type changing.
When the user upgrades the plugin, they need to click save in the config page in
order to encrypt the password on the file system.
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] [ldapemail] (JENKINS-5492) Security issue ("Bind Password" text field should be a password field on config page)
SCM/JIRA link daemon
resolved JENKINS-5492 as Fixed
Security issue ("Bind Password" text field should be a password field on config page)
Change By:
SCM/JIRA link daemon
(08/Jul/14 8:19 PM)
Status:
Open
Resolved
Resolution:
Fixed
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldapemail] (JENKINS-5492) Security issue ("Bind Password" text field should be a password field on config page)
SCM/JIRA link daemon
commented on JENKINS-5492
Security issue ("Bind Password" text field should be a password field on config page)
Code changed in jenkins
User: Marco Miller
Path:
pom.xml
src/main/java/com/mtvi/plateng/hudson/ldap/Configuration.java
src/main/resources/com/mtvi/plateng/hudson/ldap/PluginImpl/config.jelly
src/test/java/com/mtvi/plateng/hudson/ldap/BaseLdapSearchTestCase.java
src/test/java/com/mtvi/plateng/hudson/ldap/LdapSearchTest.java
http://jenkins-ci.org/commit/ldapemail-plugin/2397c4edb38e342f83ba864a25c8f289800d93b1
Log:
Merge pull request #1 from YukunSu/passwordFix
[FIXED JENKINS-5492] Hide & encrypt Bind Password.
Compare: https://github.com/jenkinsci/ldapemail-plugin/compare/ef4c92e20cf8...2397c4edb38e
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-23134) Mixed separators fail for Linux paths
Josh Cohen commented on JENKINS-23134 Mixed separators fail for Linux paths Was anyone able to resolve this issue? This is a big problem for the tests running on my Linux slaves. 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-23715) Multiple recipients list
Alex Earl commented on JENKINS-23715 Multiple recipients list The GUI is not very good, I will be the first to admit that. I haven't found a better way to organize things at this point though. 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-23715) Multiple recipients list
Ken Garland closed JENKINS-23715 as Not A Defect Multiple recipients list Change By: Ken Garland (08/Jul/14 6:21 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] [email-ext] (JENKINS-23715) Multiple recipients list
Ken Garland resolved JENKINS-23715 as Not A Defect Multiple recipients list Change By: Ken Garland (08/Jul/14 6:20 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] [email-ext] (JENKINS-23715) Multiple recipients list
Ken Garland edited a comment on JENKINS-23715 Multiple recipients list How do you make new lists appear in the dropdown for Send To? EDIT: Nevermind, I see the 2nd Advanced button 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] [email-ext] (JENKINS-23715) Multiple recipients list
Alex Earl
commented on JENKINS-23715
Multiple recipients list
You don't need to do that, just put ${YOUR_LIST_NAME} in the recipients field.
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-23715) Multiple recipients list
Ken Garland edited a comment on JENKINS-23715 Multiple recipients list How do you make new lists appear in the dropdown for Send To? Nevermind, I see the 2nd Advanced button 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] [ldapemail] (JENKINS-5492) Security issue ("Bind Password" text field should be a password field on config page)
Yukun Su
assigned JENKINS-5492 to Yukun Su
Security issue ("Bind Password" text field should be a password field on config page)
Change By:
Yukun Su
(08/Jul/14 6:18 PM)
Assignee:
justinedelson
Yukun Su
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-23715) Multiple recipients list
Ken Garland commented on JENKINS-23715 Multiple recipients list How do you make new lists appear in the dropdown for Send To? 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-23715) Multiple recipients list
Alex Earl commented on JENKINS-23715 Multiple recipients list You can do this now with environment variables. 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-22805) Version .6.22 prompts for "ACCUREV_CLIENT_PATH" with job rebuilder plugin
Walter Kacynski commented on JENKINS-22805 Version .6.22 prompts for "ACCUREV_CLIENT_PATH" with job rebuilder plugin This is fixed by pull request #15 https://github.com/jenkinsci/accurev-plugin/pull/15 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-23715) Multiple recipients list
Ken Garland created JENKINS-23715 Multiple recipients list Issue Type: Improvement Affects Versions: current Assignee: Alex Earl Components: email-ext Created: 08/Jul/14 5:48 PM Description: I'd like to have multiple recipients lists. For example one would contain managers, another would have project leads and so on. This way Each trigger could contain more specific notification groups. Not everyone wants to be notified of the same things. Ultimately it would be great to be able to name these lists when creating them as well. Due Date: 18/Jul/14 12:00 AM Environment: Amazon AMI 2014.3, Jenkins 1.571 Fix Versions: current Project: Jenkins Labels: email-ext Priority: Trivial Reporter: Ken Garland This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-23711) Jenkins GIT fetch failing
Mark Waite resolved JENKINS-23711 as Not A Defect Jenkins GIT fetch failing Please use the jenkins-dev mailing list for questions specific to your installation, rather than submitting a bug report asking the question. Change By: Mark Waite (08/Jul/14 4:35 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] [git-client] (JENKINS-23711) Jenkins GIT fetch failing
Mark Waite closed JENKINS-23711 as Not A Defect Jenkins GIT fetch failing Change By: Mark Waite (08/Jul/14 4:36 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] [git-client] (JENKINS-23345) Git Plugin should have an option to use clone instead of init/fetch
Mark Waite commented on JENKINS-23345 Git Plugin should have an option to use clone instead of init/fetch dserodio I think "least surprise" includes "don't break workflows for the 3+ installations of the git plugin and git client plugin" and also includes "don't hang the git command line by prompting for authentication". In one sense, it is a hack, since git does not have a "--no-interactive" option to prevent the git command from prompting for authentication. The subversion command line has that option, but git hasn't yet reached the point of adding that option. It would really be great to be able to use "git clone" instead of "git init + git fetch", but I think it is more important to not break existing users than it is to switch from "git init + git fetch" to "git clone". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-21330) java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful
Sylvain Mougenot commented on JENKINS-21330 java.nio.file.DirectoryNotEmptyException: /home/dev/.jenkins/jobs/MyBuild/lastSuccessful Yes : [JENKINS] Archiving disabled ln builds/lastSuccessfulBuild /opt/jenkins/jobs/.../XXX.pe$pe-metier/lastSuccessful failed java.nio.file.DirectoryNotEmptyException: /opt/jenkins/jobs/.../XXX.pe$pe-metier/lastSuccessful at sun.nio.fs.UnixFileSystemProvider.implDelete(UnixFileSystemProvider.java:242) at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(AbstractFileSystemProvider.java:108) at java.nio.file.Files.deleteIfExists(Files.java:1116) at sun.reflect.GeneratedMethodAccessor51.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.Util.createSymlinkJava7(Util.java:1146) at hudson.Util.createSymlink(Util.java:1064) at hudson.model.Run.createSymlink(Run.java:1775) at hudson.model.Run.updateSymlinks(Run.java:1756) at hudson.maven.MavenBuild$ProxyImpl2.end(MavenBuild.java:570) On : jenkins 1.549 centos 6.5 java 1.7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23709) Make the internal Plugin API accessible for System Groovy Scripts
Michael Rumpf commented on JENKINS-23709 Make the internal Plugin API accessible for System Groovy Scripts In order to create a role you need to determine a list of valid permissions. The question is where to get that from. Is there a Jenkins REST API for that or does the role-strategy plugin need to provide this method as well: "GET .../permissions" 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] [scm-api] (JENKINS-23714) specified git branch to checkout/build is not used
Lothar Schulz
created JENKINS-23714
specified git branch to checkout/build is not used
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
branches_to_build.png, check_out_local_branch.png, textParameter_GIT_BRANCH_NAME.png
Components:
scm-api
Created:
08/Jul/14 3:08 PM
Description:
Failure
specified git branch to checkout/build is not used
Reproducible by
a defined job including text parameter “GIT_BRANCH_NAME” (textParameter_GIT_BRANCH_NAME.png)
use git as source code management
Branches to build: origin/${GIT_BRANCH_NAME} (branches_to_build.png)
* check out to specific local branch
** Branch name: ${GIT_BRANCH_NAME} (check_out_local_branch.png)
provide an existing remote branch (other than remote master) is provided as parameter
remote master branch is check out and build
Expected behavior
branch provided by text parameter “GIT_BRANCH_NAME” is checked out and build
Details
Jenkins ver. 1.554.2
Ubuntu precise (12.04.2 LTS)
Project:
Jenkins
Labels:
git
Priority:
Major
Reporter:
Lothar Schulz
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] [windows-slaves] (JENKINS-22692) Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues
Ryan Croom commented on JENKINS-22692 Jenkins Windows-Slave throwing exception on shutdown causes connection reset issues So, I think this is a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-22932, updating to 1.568 (which contains this fix) seemed to fix the issue for me. Can anyone else confirm that it now works for them? 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-13348) EnvInject overriding WORKSPACE variable
lacostej commented on JENKINS-13348 EnvInject overriding WORKSPACE variable I am hitting the same issue. EnvInject 1.89 and jenkins 1.532.3 and WORKSPACE got set into hudson.EnvVars.masterEnvVars which caused lots of strange build issues. This is really a bummer. 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-23713) Remove AbstractProject-ness from BuildStep
Kohsuke Kawaguchi created JENKINS-23713 Remove AbstractProject-ness from BuildStep Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: core, workflow Created: 08/Jul/14 2:39 PM Description: To allow existing BuildSteps to work with the workflow plugin, consider refactoring BuildStep and generalize it. Also see https://trello.com/c/xAsq2mNn/11-serious-look-at-buildstep-interop Depending on how this turns out, it may help JENKINS-1392 Project: Jenkins Priority: Major Reporter: Kohsuke Kawaguchi 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-1392) Extension of "Monitor an external job" jobs.
Kohsuke Kawaguchi commented on JENKINS-1392 Extension of "Monitor an external job" jobs. JENKINS-23713 is the latest incarnation of this issue in the context of the workflow 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] [delivery-pipeline] (JENKINS-23589) Error running a manual pipeline step
Roy Miller edited a comment on JENKINS-23589 Error running a manual pipeline step The fix works for me, too. Well done there. The only issue I have now is that the arrows between stages no longer show up, either in FF or Chrome. (I can't seem to attach a screenshot to a ticket comment.) My custom stylesheet isn't the problem, because the arrows also don't appear when I'm not using my stylesheet. The same problem exists for fullscreen view and non-fullscreen. Did something change when you fixed this ticket that might have broken the arrows? 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] [vsphere-cloud] (JENKINS-21647) In Vsphere Cloud I can not create a machine from a template
Jason Swager resolved JENKINS-21647 as Fixed In Vsphere Cloud I can not create a machine from a template If no resource pool is specified, the default Resources will be used. Change By: Jason Swager (08/Jul/14 2:23 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] [delivery-pipeline] (JENKINS-23589) Error running a manual pipeline step
Roy Miller commented on JENKINS-23589 Error running a manual pipeline step The fix works for me, too. Well done there. The only issue I have now is that the arrows between stages no longer show up. (I can't seem to attach a screenshot to a ticket comment.) My custom stylesheet isn't the problem, because the arrows also don't appear when I'm not using my stylesheet. The same problem exists for fullscreen view and non-fullscreen. Did something change when you fixed this ticket that might have broken the arrows? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-23345) Git Plugin should have an option to use clone instead of init/fetch
dserodio commented on JENKINS-23345 Git Plugin should have an option to use clone instead of init/fetch I came across this ticket while searching for the reason why Jenkins is doing init+fetch instead of clone. I understand the reasoning, but I feels like a hack. For instance, it seems I need to set Additional behaviours > Check out to specific local branch to master so the Jenkins workspace is not left in a "detached head" situation. If the default value for Branches to build is */master, why do I have to specify this twice? Case in point: I'm trying to troubleshoot a release script (editing a version file, tagging, pushing the tag, etc) that works on my machine™ but not in Jenkins, because the repository is setup differently in Jenkins — I don't even know how to simulate the Jenkins behaviour on my computer. So, while I understand that having both options (init+fetch or clone) would double the possible bugs and necessary tests, I believe having only the clone option would be the best choice — and compliant to the principle of least surprise 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] [cluster-stats] (JENKINS-23712) Exceptions in multi-conf jobs and concurrents executions
Henri Gomez updated JENKINS-23712 Exceptions in multi-conf jobs and concurrents executions Change By: Henri Gomez (08/Jul/14 1:57 PM) Summary: Exceptions in multi-conf jobs and concurrents executions 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] [cluster-stats] (JENKINS-23712) Exceptions
Henri Gomez created JENKINS-23712 Exceptions Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cluster-stats Created: 08/Jul/14 1:54 PM Description: I get more and more exception like this in Jenkins log : WARNING: RunListener failed java.lang.RuntimeException: Failed to serialize org.zeroturnaround.stats.ClusterStatisticsPlugin#statsData for class org.zeroturnaround.stats.ClusterStatisticsPlugin at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:214) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:182) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:167) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:108) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1015) at com.thoughtworks.xstream.XStream.toXML(XStream.java:988) at hudson.XmlFile.write(XmlFile.java:178) at hudson.Plugin.save(Plugin.java:250) at org.zeroturnaround.stats.ClusterStatisticsPlugin.maybeSave(ClusterStatisticsPlugin.java:57) at org.zeroturnaround.stats.StartCompleteListener.onCompleted(StartCompleteListener.java:50) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199) at hudson.model.Run.execute(Run.java:1735) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.lang.RuntimeException: Failed to serialize org.zeroturnaround.stats.model.StatsData#runStats for class org.zeroturnaround.stats.model.StatsData at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:214) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:182) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:167) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:108) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:223) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:210) ... 21 more Caused by: java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372) at java.util.AbstractList$Itr.next(AbstractList.java:343) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:73) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:223) at hudson.util.RobustReflectionConverter$2.writeField
[JIRA] [role-strategy] (JENKINS-23709) Make the internal Plugin API accessible for System Groovy Scripts
Michael Rumpf commented on JENKINS-23709 Make the internal Plugin API accessible for System Groovy Scripts A public API via REST would be even better. I started using the internal API as there was no sign of a public API in the current codebase. Yes the above mentioned operations would be sufficient for what I want to 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] [role-strategy] (JENKINS-23709) Make the internal Plugin API accessible for System Groovy Scripts
Oleg Nenashev commented on JENKINS-23709 Make the internal Plugin API accessible for System Groovy Scripts I wouldn't like to make existing methods and classes public. Since the plugin has significant performance issues, it's highly likely that the implementation will be refactored at some point. The new public API class is the only way I consider This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-11864) Renaming a JDK/Maven Installation does not adjust Jobs which use it
Marc Günther updated JENKINS-11864 Renaming a JDK/Maven Installation does not adjust Jobs which use it Change By: Marc Günther (08/Jul/14 12:51 PM) Summary: Renaming a JDK/ Maven Installation does not adjust Jobs which use it Description: We have several Maven installations, which are defined in the Jenkins Global Settings.When I rename one of the installations, the jobs that had been configured to use it are not updated, and switch to the "(Default)" Maven installation, causing those builds to fail later on. EDIT: same is true for JDK Installations. I renamed our JDK8 installation, and now tons of jobs failed because they used the default JDK6. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-23711) Jenkins GIT fetch failing
arpit jain created JENKINS-23711 Jenkins GIT fetch failing Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: Untitled1.png Components: git-client Created: 08/Jul/14 12:09 PM Description: My Jenkins server is failing while fetching data from GIT repo. It is giving timeout error after 10 minutes. The size of the repo is not enough that it should take 10 minutes. It was working fine till last day but not working now. Here is the error that I am getting in attachment. Due Date: 10/Jul/14 12:00 AM Environment: Microsoft Windows Server 2008 Git plugin in Jenkins 2.2.1 Fix Versions: current Project: Jenkins Labels: jenkins exception git-client Priority: Major Reporter: arpit jain This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22486) API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception.
heymjo commented on JENKINS-22486 API change in maven 3.2.1 causes builds with the parallel (-T option) to fail with an exception. still an issue on LTS 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] [role-strategy] (JENKINS-23709) Make the internal Plugin API accessible for System Groovy Scripts
Daniel Beck edited a comment on JENKINS-23709 Make the internal Plugin API accessible for System Groovy Scripts Oleg: "for system groovy scripts". It's about making methods public rather than package-private. I can understand if you don't want to provide a stable API though, so I guess higher-level CLI/REST operations would do as well. Or just provide a big fat warning that the internal API isn't stable and that users are on their own when their scripts break This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23709) Make the internal Plugin API accessible for System Groovy Scripts
Daniel Beck commented on JENKINS-23709 Make the internal Plugin API accessible for System Groovy Scripts Oleg: "for system groovy scripts". It's about making methods public rather than package-private. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23709) Make the internal Plugin API accessible for System Groovy Scripts
Oleg Nenashev commented on JENKINS-23709 Make the internal Plugin API accessible for System Groovy Scripts Could you provide a list of operations, which you would like to have in API? I see following operations role-create role-update role-delete role-assign role-unassign 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] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
Daniel Beck commented on JENKINS-23693 Cannot delete workspace I'm probably wrong about this: An empty entry of EnvironmentVariablesNodeProperty maps "" to "", and I got an NPE trying to pass null to get(String)... 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] [shelve-project-plugin] (JENKINS-10986) Symlinks in a shelved project are archived as directories on Unix platforms
James Howe commented on JENKINS-10986 Symlinks in a shelved project are archived as directories on Unix platforms Please merge the fix, this is quite a serious 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] [template-project] (JENKINS-23710) The plugin does not support plugins implementing the DependencyDeclarer interface
William Bernardet commented on JENKINS-23710 The plugin does not support plugins implementing the DependencyDeclarer interface Fix proposal https://github.com/jenkinsci/template-project-plugin/pull/9 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] [shelve-project-plugin] (JENKINS-17046) Queue shelve jobs
James Howe commented on JENKINS-17046 Queue shelve jobs To clarify, if you mark Jenkins for shutdown, then the shelve jobs will enter the queue and be processed according to free executors when the shutdown is cancelled. Otherwise, they all start immediately. 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] [template-project] (JENKINS-23710) The plugin does not support plugins implementing the DependencyDeclarer interface
William Bernardet created JENKINS-23710 The plugin does not support plugins implementing the DependencyDeclarer interface Issue Type: Bug Affects Versions: current Assignee: huybrechts Components: template-project Created: 08/Jul/14 9:33 AM Description: At the moment the ProxyBuilder and ProxyPublisher do not support the DependencyDeclarer interface, which means plugin implementing it will not behave properly when used from a template, like the parametrized build trigger plugin. Project: Jenkins Priority: Critical Reporter: William Bernardet 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-16737) java.lang.RuntimeException: No author in changeset null
Thomas Carsuzan commented on JENKINS-16737 java.lang.RuntimeException: No author in changeset null Ok, I could finally debug it. The problem comes from the lines passed to GitChangeSet.parseCommit(List lines) I got only these : commit 51ffaaa7d9cd227d6a3a1da44118306276ab1af6 tree bea0dd38c05f1d22c9b7fe4cc430a052beb68 So neither author nor commiter. I will try to understand why and what can be the solution. 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] [role-strategy] (JENKINS-23709) Make the internal Plugin API accessible for System Groovy Scripts
Michael Rumpf
updated JENKINS-23709
Make the internal Plugin API accessible for System Groovy Scripts
Change By:
Michael Rumpf
(08/Jul/14 9:24 AM)
Description:
I' currently trying to automate the role creation and assignment.As the plugin does not provide a REST API, the only chance was to execute a System Groovy Script via Jenkins' script console.The ugly thing is that the Plugin API seems to be aimed at internal usage only. The Role constructors are package protected so that I was forced to use "setAccessible(true)" in order to make them accessible.The following script shows a first draft which only creates a role without any permissions yet:{code}import Hudson.*import java.util.*import com.michelin.cio.hudson.plugins.rolestrategy.*import java.lang.reflect.*import hudson.security.*def authStrategy = Hudson.instance.getAuthorizationStrategy()if(authStrategy instanceof RoleBasedAuthorizationStrategy){ println "Role Strategy Plugin found!" RoleBasedAuthorizationStrategy roleAuthStrategy = (RoleBasedAuthorizationStrategy) authStrategy // Make constructors accessible Constructor[] constrs = Role.class.getConstructors(); for (Constructor c : constrs) {c.setAccessible(true); } // create the new role Set permissions = new HashSet(); permissions.add("");
// TODO: Pass list of Permissions
Role newRole = new Role("test", "test.*",
null
permissions
); roleAuthStrategy.addRole(RoleBasedAuthorizationStrategy.PROJECT, newRole); // Role, Set def globalRoles = roleAuthStrategy.getGrantedRoles(RoleBasedAuthorizationStrategy.GLOBAL) def projectRoles = roleAuthStrategy.getGrantedRoles(RoleBasedAuthorizationStrategy.PROJECT) def slaveRoles = roleAuthStrategy.getGrantedRoles(RoleBasedAuthorizationStrategy.SLAVE) println "GLOBAL:" for (r in globalRoles) {println " " + r.key.name } println "PROJECT:" for (r in projectRoles) {println " " + r.key.name } println "SLAVE:" for (r in slaveRoles) {println " " + r.key.name }}else { println "not found"}{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23709) Make the internal Plugin API accessible for System Groovy Scripts
Michael Rumpf
updated JENKINS-23709
Make the internal Plugin API accessible for System Groovy Scripts
Change By:
Michael Rumpf
(08/Jul/14 9:23 AM)
Description:
I' currently trying to automate the role creation and assignment.As the plugin does not provide a REST API, the only chance was to execute a System Groovy Script via Jenkins' script console.The ugly thing is that the Plugin API seems to be aimed at internal usage only. The Role constructors are package protected so that I was forced to use "setAccessible(true)" in order to make them accessible.
The following script shows a first draft which only creates a role without any permissions yet:
{code}import Hudson.*import java.util.*import com.michelin.cio.hudson.plugins.rolestrategy.*import java.lang.reflect.*import hudson.security.*def authStrategy = Hudson.instance.getAuthorizationStrategy()
if(authStrategy instanceof RoleBasedAuthorizationStrategy){ println "Role Strategy Plugin found!" RoleBasedAuthorizationStrategy roleAuthStrategy = (RoleBasedAuthorizationStrategy) authStrategy // Make constructors
available
accessible
Constructor[] constrs = Role.class.getConstructors(); for (Constructor c : constrs) {c.setAccessible(true); } // create the new role Set permissions = new HashSet(); permissions.add(""); // TODO: Pass list of Permissions Role newRole = new Role("test", "test.*", null); roleAuthStrategy.addRole(RoleBasedAuthorizationStrategy.PROJECT, newRole); // Role, Set def globalRoles = roleAuthStrategy.getGrantedRoles(RoleBasedAuthorizationStrategy.GLOBAL) def projectRoles = roleAuthStrategy.getGrantedRoles(RoleBasedAuthorizationStrategy.PROJECT) def slaveRoles = roleAuthStrategy.getGrantedRoles(RoleBasedAuthorizationStrategy.SLAVE) println "GLOBAL:" for (r in globalRoles) {println " " + r.key.name } println "PROJECT:" for (r in projectRoles) {println " " + r.key.name } println "SLAVE:" for (r in slaveRoles) {println " " + r.key.name }}else { println "not found"}{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23709) Make the internal Plugin API accessible for System Groovy Scripts
Michael Rumpf
created JENKINS-23709
Make the internal Plugin API accessible for System Groovy Scripts
Issue Type:
Improvement
Assignee:
Oleg Nenashev
Components:
role-strategy
Created:
08/Jul/14 9:21 AM
Description:
I' currently trying to automate the role creation and assignment.
As the plugin does not provide a REST API, the only chance was to execute a System Groovy Script via Jenkins' script console.
The ugly thing is that the Plugin API seems to be aimed at internal usage only. The Role constructors are package protected so that I was forced to use "setAccessible(true)" in order to make them accessible.
import Hudson.*
import java.util.*
import com.michelin.cio.hudson.plugins.rolestrategy.*
import java.lang.reflect.*
import hudson.security.*
def authStrategy = Hudson.instance.getAuthorizationStrategy()
if(authStrategy instanceof RoleBasedAuthorizationStrategy){
println "Role Strategy Plugin found!"
RoleBasedAuthorizationStrategy roleAuthStrategy = (RoleBasedAuthorizationStrategy) authStrategy
// Make constructors available
Constructor[] constrs = Role.class.getConstructors();
for (Constructor c : constrs) {
c.setAccessible(true);
}
// create the new role
Set permissions = new HashSet();
permissions.add("");
// TODO: Pass list of Permissions
Role newRole = new Role("test", "test.*", null);
roleAuthStrategy.addRole(RoleBasedAuthorizationStrategy.PROJECT, newRole);
// Role, Set
def globalRoles = roleAuthStrategy.getGrantedRoles(RoleBasedAuthorizationStrategy.GLOBAL)
def projectRoles = roleAuthStrategy.getGrantedRoles(RoleBasedAuthorizationStrategy.PROJECT)
def slaveRoles = roleAuthStrategy.getGrantedRoles(RoleBasedAuthorizationStrategy.SLAVE)
println "GLOBAL:"
for (r in globalRoles) {
println " " + r.key.name
}
println "PROJECT:"
for (r in projectRoles) {
println " " + r.key.name
}
println "SLAVE:"
for (r in slaveRoles) {
println " " + r.key.name
}
}
else {
println "not found"
}
Project:
Jenkins
Priority:
Major
Reporter:
Michael Rumpf
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] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
vjuranek commented on JENKINS-23693 Cannot delete workspace quickly looking into the code, it would probably result into behavior described in this issue, but IMHO this should never happen, as env. var. expansion should return null for null param: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/Util.java#L143 Anyway, will check it more carefully in the eventing. Thanks for good pointer! 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] [jacoco] (JENKINS-23708) Unable to view JaCoCo report and history graph
Ján Ondrušek created JENKINS-23708 Unable to view JaCoCo report and history graph Issue Type: Bug Affects Versions: current Assignee: Ognjen Bubalo Components: jacoco Created: 08/Jul/14 8:41 AM Description: Coverage report is empty and graph is generated with both lines on Y=0. java.lang.NullPointerException at hudson.plugins.jacoco.report.CoverageReport.(CoverageReport.java:65) at hudson.plugins.jacoco.JacocoBuildAction.getResult(JacocoBuildAction.java:227) at hudson.plugins.jacoco.report.CoverageReport.getPreviousResult(CoverageReport.java:221) at hudson.plugins.jacoco.report.CoverageReport.getPreviousResult(CoverageReport.java:38) at hudson.plugins.jacoco.model.CoverageObject$1.createDataSet(CoverageObject.java:379) at hudson.plugins.jacoco.model.CoverageObject$GraphImpl.createGraph(CoverageObject.java:418) at hudson.util.Graph.render(Graph.java:87) at hudson.util.Graph.doPng(Graph.java:98) at hudson.plugins.jacoco.model.CoverageObject.doGraph(CoverageObject.java:373) 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:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) 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.tryInvoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) 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.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at huds
[JIRA] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
Daniel Beck commented on JENKINS-23693 Cannot delete workspace What happens when this line returns an empty string instead of null? Could that happen with empty node properties (i.e. empty string as key and value)? https://github.com/jenkinsci/ws-cleanup-plugin/blob/master/src/main/java/hudson/plugins/ws_cleanup/Cleanup.java#L35 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-23707) subversion plugin caused an error "NullPointerException" in configuration of scm-sync-plugin
Justyna Burzyńska
updated JENKINS-23707
subversion plugin caused an error "NullPointerException" in configuration of scm-sync-plugin
Change By:
Justyna Burzyńska
(08/Jul/14 8:15 AM)
Description:
Plugin scm-sync-configuration does not work with Subversion
Plug-in
Plugin
2.4. After selection SCM: Subversion in SCM Sync configuration (on jenkins /configure page) and entering URL error appears:{code}Stack tracejavax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFi
[JIRA] [subversion] (JENKINS-23707) subversion plugin caused an error "NullPointerException" in configuration of scm-sync-plugin
Justyna Burzyńska created JENKINS-23707 subversion plugin caused an error "NullPointerException" in configuration of scm-sync-plugin Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 08/Jul/14 8:14 AM Description: Plugin scm-sync-configuration does not work with Subversion Plug-in 2.4. After selection SCM: Subversion in SCM Sync configuration (on jenkins /configure page) and entering URL error appears: Stack trace javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:135) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.Chaine
[JIRA] [core] (JENKINS-13253) Slave connection reset issues since 1.456
Bipin Jethwani commented on JENKINS-13253 Slave connection reset issues since 1.456 It was indeed a network issue. It's resolved for me. 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-17232) Jenkins mixes-up form fields when "Back" browser button is used
Daniel Beck resolved JENKINS-17232 as Duplicate Jenkins mixes-up form fields when "Back" browser button is used JENKINS-18435 has more watchers, so resolving this report. Change By: Daniel Beck (08/Jul/14 7:36 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
vjuranek commented on JENKINS-23693 Cannot delete workspace thanks for double check. I'll go through the code once again and try to figure out the reason how this can happen 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] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
Hua Zhang commented on JENKINS-23693 Cannot delete workspace I added a screenshot of the job configuration. The input field "External Deletion Command" is empty, no whitespaces in there. And in config.xml: "ws-cleanup@0.20"> APPLICATION/artifacts INCLUDE true Nothing looks suspicious to me. I will try upgrade again to see if this is only an one-time issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19828) Kill or rework auto refresh
Daniel Beck commented on JENKINS-19828 Kill or rework auto refresh http://jenkins-ci.org/content/thinking-about-moving-servlet-30 says (with many inline links): Jenkins devs are thinking about ways to update page contents post load, for example so that the list view will keep updating as stuff happens. WebSocket was discussed as an option, and then server-side events, which seems to be the current favorite. 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] [plugin] (JENKINS-17480) Copying a job should disable the copy while editing it
Daniel Beck edited a comment on JENKINS-17480 Copying a job should disable the copy while editing it (obsolete: missed the last paragraph of the last comment) 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.
