[JIRA] [git] (JENKINS-25176) I can't store the private hey
ying zhang created JENKINS-25176 I cant store the private hey Issue Type: Bug Assignee: ying zhang Attachments: 1.jpg Components: git Created: 16/Oct/14 5:58 AM Description: when I use firefox config the git job on jenkins,I can't store the private key in the key block.I can't see the "add" button,either the "cancel" Environment: V1.584 centos X64 Firefox33.0 Project: Jenkins Priority: Major Reporter: ying zhang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-25176) I can't store the private hey
Oleg Nenashev updated JENKINS-25176 I cant store the private hey Change By: Oleg Nenashev (16/Oct/14 6:20 AM) Component/s: credentials 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] [matrix-project] (JENKINS-20629) Multiconfig build fails even though individual jobs passed
Oleg Nenashev resolved JENKINS-20629 as Cannot Reproduce Multiconfig build fails even though individual jobs passed No response from the requester, cannot reproduce the issue Change By: Oleg Nenashev (16/Oct/14 6:21 AM) Status: Open Resolved Resolution: CannotReproduce 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-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Jennifer Hofmeister edited a comment on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. I've been experiencing the error with every checkout attempt, and it's persistent. Windows 7 master and slaves. Jenkins 1.565.2 (official latest stable) and Subversion 2.4.3. I decided to upgrade from 1.561/2.0 after encountering some SVN external issues that suddenly occurred (J refused to check out and then complained things were missing). Although it seems like a pure Subversion issue, downgrading Subversion plugin to 2.0 and 1.5.4 didn't help. Eventually, I upgraded it back to 2.4.3 and manually reconfigured all affected jobs in the above way ... but needless to say, that was a drag^^ Edit: I found out that Jenkins sometimes tries to connect to the SVN server without actually giving credentials. Here's from the svn server's connection log: " 190.10.210.20 - jenkins 25/Sep/2014:15:09:06 +0200 ... 190.10.210.20 - jenkins 25/Sep/2014:15:09:06 +0200 ... 190.10.210.20 - - 25/Sep/2014:15:09:06 +0200 ... 190.10.210.20 - - 25/Sep/2014:15:09:06 +0200 ... First two checkouts succeeded, last two didn't. 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-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Jennifer Hofmeister edited a comment on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. I've been experiencing the error with every checkout attempt, and it's persistent. Windows 7 master and slaves. Jenkins 1.565.2 and Subversion 2.4.3. I decided to upgrade from 1.561/2.0 after encountering some SVN external issues (J refusing to check out and then complaining things were missing). Although it seems like a pure Subversion issue, downgrading Subversion plugin to 2.0 and 1.5.4 didn't help. Eventually, I upgraded it back to 2.4.3 and manually reconfigured all affected jobs in the above way ... Edit: I found out that Jenkins sometimes tries to connect to the SVN server without actually giving credentials. Here's from the svn server's connection log: " 190.10.210.20 - jenkins 25/Sep/2014:15:09:06 +0200 ... 190.10.210.20 - jenkins 25/Sep/2014:15:09:06 +0200 ... 190.10.210.20 - - 25/Sep/2014:15:09:06 +0200 ... 190.10.210.20 - - 25/Sep/2014:15:09:06 +0200 ... First two checkouts succeeded, last two didn't. 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-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Jennifer Hofmeister edited a comment on JENKINS-22542 Subversion polling not work with externals or variables in URL - E200015: No credential to try. I've been experiencing the error with every checkout attempt, and it's persistent. Windows 7 master and slaves. Jenkins 1.565.2 and Subversion 2.4.3. I decided to upgrade from 1.561/2.0 after encountering some SVN external issues (J refusing to check out and then complaining things were missing). Although it seems like a pure Subversion issue, downgrading Subversion plugin to 2.0 and 1.5.4 didn't help. Eventually, I upgraded it back to 2.4.3 and manually reconfigured all affected jobs in the above way. The error keeps recurring. Edit: I found out that Jenkins sometimes tries to connect to the SVN server without actually giving credentials. Here's from the svn server's connection log: " 190.10.210.20 - jenkins 25/Sep/2014:15:09:06 +0200 ... 190.10.210.20 - jenkins 25/Sep/2014:15:09:06 +0200 ... 190.10.210.20 - - 25/Sep/2014:15:09:06 +0200 ... 190.10.210.20 - - 25/Sep/2014:15:09:06 +0200 ... First two checkouts succeeded, last two didn't. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-25176) I can't store the private key in job configure page
ying zhang updated JENKINS-25176 I cant store the private key in job configure page Change By: ying zhang (16/Oct/14 6:54 AM) Summary: Icantstoretheprivate hey keyinjobconfigurepage This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-25176) I can't store the private key in job configure page
ying zhang commented on JENKINS-25176 I cant store the private key in job configure page in the credentials page ,I success store the private hey, add in job configure page choose the key I need 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-plugin] (JENKINS-23833) Subversion Plugin - can not checkout project due to OPTIONS request failed
Riddhi Sharma commented on JENKINS-23833 Subversion Plugin - can not checkout project due to OPTIONS request failed Even I am getting the same issue just after updating Jenkins form 1.4x to 1.5x. Downgrading the plugin to 1.4x, would it resolve the issue? Referred to some suggestion over here: http://stackoverflow.com/questions/22068297/jenkins-subversion-error-e200015-no-credential-to-try-authentication-failed I will try updating the Additional realm credentials as per Mark. 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-25172) GIT_SSH not always used for git fetch
Nicolae Ghimbovschi commented on JENKINS-25172 GIT_SSH not always used for git fetch Master: Windows OS Jenkins 1.532.3 Java 1.7.0_25 git plugin2.2.5 git client plugin 1.10.2 Salve: Mac OS X 10.9.5 Java 1.7.0_25-b15 SSH connection For example, does it only happen with bitbucket URLs, or does it also happen with other secured URLs? It happened and with other providers. Can you duplicate the problem on any other operating system besides OS X? No, but I configured a job to run on a windows slave, it will use the same repository. I will monitor it. Are there cases where the problem does not occur, and if so, are there interesting or surprising differences between the failure modes and the success cases? The only difference I noticed is that when it fails the message "using GIT_SSH to set credentials" is not present in the logs. 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-plugin] (JENKINS-21656) Credential issues when using externals after upgrade to subversion plugin 2.0
Riddhi Sharma commented on JENKINS-21656 Credential issues when using externals after upgrade to subversion plugin 2.0 Added Credentials and it worked!!! 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-plugin] (JENKINS-23833) Subversion Plugin - can not checkout project due to OPTIONS request failed
Riddhi Sharma commented on JENKINS-23833 Subversion Plugin - can not checkout project due to OPTIONS request failed Added Credentials and it worked!!! 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-plugin] (JENKINS-23833) Subversion Plugin - can not checkout project due to OPTIONS request failed
KY Lee commented on JENKINS-23833 Subversion Plugin - can not checkout project due to OPTIONS request failed We are still stuck at version 1.42 because of this problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [categorized-view] (JENKINS-25177) Duplicated job title for certain grouping RegExp
Phil Foobar created JENKINS-25177 Duplicated job title for certain grouping RegExp Issue Type: Bug Assignee: Unassigned Components: categorized-view Created: 16/Oct/14 8:37 AM Description: When you set a rule to include all jobs with ".*" the job title gets displayed duplicated like "FoobarFoobar" instead of "Foobar". However if you set Regexp to "^.*$" the title is displayed correctly Environment: categorized-view v1.8 Project: Jenkins Priority: Minor Reporter: Phil Foobar 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-11543) UTF-8 encoding issue of build parameters as soon as including File parameter
SCM/JIRA link daemon commented on JENKINS-11543 UTF-8 encoding issue of build parameters as soon as including File parameter Code changed in jenkins User: Oliver Gondža Path: test/src/test/java/hudson/model/ParametersTest.java http://jenkins-ci.org/commit/jenkins/66dce647d1d7df919f9707b4ce631cd49dc242f7 Log: JENKINS-11543 Unit test (cherry picked from commit 75f5d2180f7340ce2efd4f41c8670afb049eb530) 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] [log-parser] (JENKINS-25178) Make visibility of log content optional, show only the parsed results
KY Lee created JENKINS-25178 Make visibility of log content optional, show only the parsed results Issue Type: Improvement Assignee: rgoren Attachments: Clean_Parsed_Console_Output.png, Parsed_Console_Output.png Components: log-parser Created: 16/Oct/14 8:50 AM Description: The current Parsed Console Output view shows the result of the parse, alongside with the log content in a splitter divided frame. What we are after is really just the parsed result on the left, presented by log_ref.html, but not interested in highlighting the location of the result in the log content, log_content.html. We produce 1.5MB of log for each build and parsing that log already took a lot of time. If we want to look at the console output, we can go to console output. Loading log_content.html is really cumbersome so we would like to avoid that. The option of showing log content can be set at the plugin level at system configuration, or at the job / project settings. I would suggest to allow system configuration settings so log_content.html generation can entirely be avoided to enhance performance of the log parser. Environment: Jenkins 1.565.2 Log parser plugin 1.0.8 Windows Server 2008 R2 Project: Jenkins Priority: Major Reporter: KY Lee This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-18174) Checking of unique Build Parameter names has a hole and only works within a single context
Daniel Spilker commented on JENKINS-18174 Checking of unique Build Parameter names has a hole and only works within a single context Even if there are checks across parameter contexts, there are still templates and configure blocks to be considered to be 100% sure to have only unique parameter definitions. Since the DSL does not do this level of checks for other features, I tend to close this as "won't fix" and actually remove the existing checks since they pretend false 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] [core] (JENKINS-10322) Allow restricting a job to an executor
Gunnar Strand
reopened JENKINS-10322
Allow restricting a job to an executor
I would like to reopen this issue. I have a different reason for wanting a possibility to tie projects or jobs to specific executors:
I have a configuration with parametrized projects with persistent work spaces local to the slave the jobs happen to execute on. The work spaces are based on the ${EXECUTOR} variable to separate them, and are reused by a lot of projects. It can take up to 10 minutes to initialize a workspace (cleaning etc.), and I would like to clean these work spaces from time to time, to reduce initialization time for production jobs. The idea I have to go about this is to trigger cleaning jobs on specific executors, so that each persistent workspace will be cleaned without locking all the executors. I haven't been able to find any way to tie a specific executor for jobs.
Neither neither port allocator nor locks latches or throttle concurrent builds appear to allow this.
Change By:
Gunnar Strand
(16/Oct/14 9:06 AM)
Resolution:
WontFix
Status:
Resolved
Reopened
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [vs-code-metrics] (JENKINS-21848) CyclomaticComplexity/LineOfCodes always 0 if library contains enumeration
Christian Altmeier commented on JENKINS-21848 CyclomaticComplexity/LineOfCodes always 0 if library contains enumeration Hi there! Same problem here. But: It seems that the powertool summarize the cyclomatic complexity for the whole module. The result is in our case a very high cyclomatic complexity of "11.580" in "26.060" lines of code. Is it possible, that the plugin cannot parse these strings with high metric values to integers? Wether the cyclomatic complexity nor the lines of code and class coupling are displayed in graphs in tables for the views "All classed" and "Code metrics by module". Here is our modules metrics node from the powertool XML: Metrics Metric Name="MaintainabilityIndex" Value="83" / Metric Name="CyclomaticComplexity" Value="11.580" / Metric Name="ClassCoupling" Value="969" / Metric Name="DepthOfInheritance" Value="7" / Metric Name="LinesOfCode" Value="26.060" / /Metrics The single members and types are correctly parsed by the plugin an shows correct values in both tables and graph. I think i can provide the whole XML file, if this helps to improve the plugin. By the way: Thanks for this convenient plugin wich allows to gather code metrics in Jenkins so easily! 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] [junit-plugin] (JENKINS-23858) SLF4J StaticLoggerBinder class not found
Daniel Beck commented on JENKINS-23858 SLF4J StaticLoggerBinder class not found Full stack trace and steps to reproduce with a new instance / new Jenkins project are a bare minimum (more is better). 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] [openid] (JENKINS-25179) Starting with OpenID 2.1.1, Google auth. requires you to accept jenkins to access your data at each login
Andrei Costescu commented on JENKINS-25179 Starting with OpenID 2.1.1, Google auth. requires you to accept jenkins to access your data at each login Jenkins is deployed as war inside a Tomcat server. 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] [openid] (JENKINS-25179) Starting with OpenID 2.1.1, Google auth. requires you to accept jenkins to access your data at each login
Andrei Costescu created JENKINS-25179 Starting with OpenID 2.1.1, Google auth. requires you to accept jenkins to access your data at each login Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: openid Created: 16/Oct/14 9:29 AM Description: When I installed openID 2.1.1, after Google login screen, Google asks if it should allow Jenkins to access your account data - each time. It should only as once. After downgrading to openID plugin to 2.1, it started to work again as expected. Login just logs in, doesn't require extra steps each time. Environment: Jenkins 1.584 but the same happened with earlier version Project: Jenkins Priority: Minor Reporter: Andrei Costescu 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-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
uncletall
created JENKINS-25180
Unable to authenticate using LDAP after upgrading to 1.576 or higher
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
16/Oct/14 9:40 AM
Description:
After upgrading to 1.576 or higher LDAP authentication fails. It is very repeatable and downgrading to 1.575 fixes the issue. I have tried 1.576 1.577 1.580 and 1.584 but am unable to log in.
Basically, I disable security and then setup the same config again and am still unable to log in.
I am using ldap 1.6 plugin but have also tried 1.11, both fail once I enable ldap authentication.
This is my configuration from the config.xml
useSecuritytrue/useSecurity
authorizationStrategy class="hudson.security.AuthorizationStrategy$Unsecured"/
securityRealm class="hudson.security.LDAPSecurityRealm" plugin="ldap@1.6"
serverldap://ldap/server
rootDN/rootDN
inhibitInferRootDNfalse/inhibitInferRootDN
userSearchBaseou=users,dc=xxx,dc=com,dc=sg/userSearchBase
userSearchuid={0}/userSearch
groupSearchBaseou=jenkins,ou=groups,dc=xxx,dc=com,dc=sg/groupSearchBase
managerDNcn=admin,dc=xxx,dc=com,dc=sg/managerDN
managerPasswordxxx/managerPassword
disableMailAddressResolverfalse/disableMailAddressResolver
/securityRealm
Environment:
ubuntu 12.04 and 14.04 openldap
Project:
Jenkins
Priority:
Blocker
Reporter:
uncletall
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-22514) Zip generated from all files in zip contains the wrong slashes
Holger Voormann updated JENKINS-22514 Zip generated from all files in zip contains the wrong slashes Detailed test results and scripts/jobs used. See commit f2482b1 and pull request #1408 Change By: Holger Voormann (16/Oct/14 9:58 AM) Attachment: JENKINS-22514_Tests.zip 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-22514) Zip generated from all files in zip contains the wrong slashes
Holger Voormann edited a comment on JENKINS-22514 Zip generated from all files in zip contains the wrong slashes JENKINS-22514_Tests.zip: Detailed test results and scripts/jobs used. See commit f2482b1 and pull request #1408 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-25164) Provide a short $JOB_NAME inside a folder
Dirk Kuypers updated JENKINS-25164 Provide a short $JOB_NAME inside a folder Thanks Jesse, I changed the component and added the label but I am not able to find the related Issue. Too dumb to search... Change By: Dirk Kuypers (16/Oct/14 10:01 AM) Labels: folders Component/s: core Component/s: cloudbees-folder 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-22514) Zip generated from all files in zip contains the wrong slashes
Holger Voormann edited a comment on JENKINS-22514 Zip generated from all files in zip contains the wrong slashes JENKINS-22514_Tests.zip: Detailed test results and scripts/jobs used. See pull request 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.
[JIRA] [core] (JENKINS-25180) Unable to authenticate using LDAP after upgrading to 1.576 or higher
Daniel Beck commented on JENKINS-25180 Unable to authenticate using LDAP after upgrading to 1.576 or higher For a blocker bug this is a bit light on details. What's the error shown in the log? 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-25167) API requests crash with depth greater than 0
Daniel Beck commented on JENKINS-25167 API requests crash with depth greater than 0 SCM Sync appears to be just another filter here. The error is with the job data that is being serialized. JENKINS-25054 appears to be relevant here, that user was able to determine the issue was caused by use of the Warnings plugin. Maybe a similar strategy of determining the cause works for you 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-17231) Remote API: Exception on /computer/xyz/api/json?depth=2 fails when jlnp connection is broken
Daniel Beck resolved JENKINS-17231 as Duplicate Remote API: Exception on /computer/xyz/api/json?depth=2 fails when jlnp connection is broken Appears to duplicate JENKINS-24452 (which has the better stack trace). Change By: Daniel Beck (16/Oct/14 10:51 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] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
cepnyci commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection We experience the same issue with this network topology: Jenkins master @ 10.10.100.204 Jenkins slave 1 @ 10.10.100.205 Jenkins slave 2 @ 10.10.100.207 Jenkins slave 3 @ 10.10.100.193 on the same LAN. Jenkins ver. 1.584 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] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
cepnyci edited a comment on JENKINS-23232 SEVERE: I/O error in channel Chunked connection We experience the same issue with this network topology: Jenkins master @ 10.10.100.204 Jenkins slave 1 @ 10.10.100.205 Jenkins slave 2 @ 10.10.100.207 Jenkins slave 3 @ 10.10.100.193 on the same LAN. Jenkins ver. 1.584 Oct 16, 2014 12:18:27 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel 10.10.100.207 java.io.StreamCorruptedException: invalid stream header: 6E6C6F61 at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:782) at java.io.ObjectInputStream.init(ObjectInputStream.java:279) at hudson.remoting.ObjectInputStreamEx.init(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [batch-task] (JENKINS-25181) batch task should be able to run managed scripts
Sam Liddicott created JENKINS-25181 batch task should be able to run managed scripts Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: batch-task, managed-scripts Created: 16/Oct/14 11:20 AM Description: managed scripts can be invoked as certain "macro" build operations batch tasks should also be able to invoke managed scripts Environment: n/a Project: Jenkins Priority: Minor Reporter: Sam Liddicott 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] [jiratestresultreporter] (JENKINS-25182) HTTP 400 bad request error occurs, while integrate the jira test result reporter plugin with Jenkins tool v1.58.
Praveen Lakshmanan created JENKINS-25182 HTTP 400 bad request error occurs, while integrate the jira test result reporter plugin with Jenkins tool v1.58. Issue Type: Bug Assignee: Unassigned Components: jiratestresultreporter Created: 16/Oct/14 11:21 AM Description: I've configured jira test result reporter plugin with Jenkins, after build gets failed I'm facing HTTP 400 bad request error issue. Versions: Jenkins ver. 1.580 JiraTestResultReporter plugin 1.0.5 JIRA: 6.4 Console Output: JiraTestResultReporter DEBUG JiraTestResultReporter DEBUG Creating issue in project QAA at URL https://guidanz.atlassian.net/rest/api/2/issue/ JiraTestResultReporter INFO Reporting issue. JiraTestResultReporter DEBUG statusLine: HTTP/1.1 400 Bad Request JiraTestResultReporter DEBUG statusCode: 400 ERROR: Publisher JiraTestResultReporter.JiraReporter aborted due to exception java.lang.RuntimeException: JiraTestResultReporter ERROR Failed : HTTP error code : 400 at JiraTestResultReporter.JiraReporter.createJiraIssue(JiraReporter.java:188) at JiraTestResultReporter.JiraReporter.perform(JiraReporter.java:108) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) No emails were triggered. Finished: FAILURE Project: Jenkins Priority: Blocker Reporter: Praveen Lakshmanan 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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
Leandro Lucarella commented on JENKINS-24954 Test PASSed comments added even if Published Jenkins URL I didn't understand very well what you are saying above, David. What I want is to make comments only if setting the github commit status fail. I guess for that, the official way to do it (and what worked before) is to have the "Published Jenkins URL" empty, "Use comments to report results when updating commit status fails" checked and the passed and failed messages with some text. Right now with that configuration I get always a message, even when the statuses are being set correctly (at least I can see them in GitHub). So, what I'm doing now (emptying the failed and passed messages text) is only a hack and I guess it will make that if setting the statuses ever fail, I won't get any comments either. Right? This is not what I want, is just a workaround so I don't get spammed 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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
Leandro Lucarella reopened JENKINS-24954 Test PASSed comments added even if Published Jenkins URL I'm reopening for now, since I don't think this is not an issue, something changed between 1.16 and 1.16-1 that made this plug-in, at least, behave differently. Change By: Leandro Lucarella (16/Oct/14 11:57 AM) Resolution: NotADefect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jiratestresultreporter] (JENKINS-25182) HTTP 400 bad request error occurs, while integrate the jira test result reporter plugin with Jenkins tool v1.58.
Daniel Beck updated JENKINS-25182 HTTP 400 bad request error occurs, while integrate the jira test result reporter plugin with Jenkins tool v1.58. Is there a reason you're reporting everything as a blocker? There's a reason we default to 'Minor' you know. Something simply not working like this is no worse than Major. Change By: Daniel Beck (16/Oct/14 11:59 AM) Priority: Blocker Major 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] [jiratestresultreporter] (JENKINS-25168) Jira reporting issue process is done in Jenkins 1.577+, but issue is not seen in JIRA 6.4
Daniel Beck updated JENKINS-25168 Jira reporting issue process is done in Jenkins 1.577+, but issue is not seen in JIRA 6.4 Also only major, no crash or data loss involved. Change By: Daniel Beck (16/Oct/14 12:00 PM) Priority: Blocker Major 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] [jiratestresultreporter] (JENKINS-25140) JiraTestResultReporter does not work on Jenkins 1.577+
Daniel Beck updated JENKINS-25140 JiraTestResultReporter does not work on Jenkins 1.577+ Change By: Daniel Beck (16/Oct/14 12:00 PM) Priority: Blocker Major 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-10322) Allow restricting a job to an executor
Daniel Beck commented on JENKINS-10322 Allow restricting a job to an executor I would like to clean these work spaces from time to time, to reduce initialization time for production jobs. The idea I have to go about this is to trigger cleaning jobs on specific executors, so that each persistent workspace will be cleaned without locking all the executors. I haven't been able to find any way to tie a specific executor for jobs. I'm fairly sure this is not supported and not intended to be. The common solution to this is just having multiple slaves, each with 1 executor. (Multiple slave processes can run on the same machine.) 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-10322) Allow restricting a job to an executor
Gunnar Strand commented on JENKINS-10322 Allow restricting a job to an executor Right, that would work of course, and may be sufficient. I will have to have a look at it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10322) Allow restricting a job to an executor
Gunnar Strand resolved JENKINS-10322 as Wont Fix Allow restricting a job to an executor See Daniel's comment. Change By: Gunnar Strand (16/Oct/14 12:10 PM) Status: Reopened Resolved Resolution: WontFix 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] [gant] (JENKINS-9127) Spaces in JOB_NAME problematic
Jesse Glick updated JENKINS-9127 Spaces in JOB_NAME problematic Change By: Jesse Glick (16/Oct/14 12:40 PM) Summary: Hudsonenvironmentvariables SpacesinJOB_NAMEproblematic Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25164) Provide a short $JOB_NAME inside a folder
Jesse Glick commented on JENKINS-25164 Provide a short $JOB_NAME inside a folder Well maybe it was not already filed. Perhaps was just discussed somewhere else. 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-25144) Basic Authentication in combination with Session is broken
Jesse Glick updated JENKINS-25144 Basic Authentication in combination with Session is broken Change By: Jesse Glick (16/Oct/14 12:56 PM) Labels: AuthenticationBasicAuth lts-candidate regressionsecurity 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-25144) Basic Authentication in combination with Session is broken
Jesse Glick updated JENKINS-25144 Basic Authentication in combination with Session is broken Change By: Jesse Glick (16/Oct/14 12:56 PM) Labels: AuthenticationBasicAuth regression 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] [core] (JENKINS-20327) “Form too large” errors submitting view configurations with many jobs
marco boschetti reopened JENKINS-20327 “Form too large” errors submitting view configurations with many jobs Sorry, but the problem is still there... I obtain the following error javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 59586420 when I click Save to submit changes to even 1 job using Configuration Slicing plugin (http://myjenkinshost/slicing/jobdisabledbool/sliceconfigSubmit) Jenkins version: 1.584 Configuration Slicing Plugin version: 1.39 Change By: marco boschetti (16/Oct/14 1:17 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20327) “Form too large” errors submitting view configurations with many jobs
Daniel Beck resolved JENKINS-20327 as Fixed “Form too large” errors submitting view configurations with many jobs Clearly a different issue (not view config, but job config slicing). Change By: Daniel Beck (16/Oct/14 1:24 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] [core] (JENKINS-20327) “Form too large” errors submitting view configurations with many jobs
mwebber commented on JENKINS-20327 “Form too large” errors submitting view configurations with many jobs @marco, you should open a separate issue for the job config slicing plugin (this issue is for the core problem). Also, if you read the comments above, you will find a workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-25183) Not able to execute QTP scripts from Jenkins
Shivakumar Balasubramanian
created JENKINS-25183
Not able to execute QTP scripts from Jenkins
Issue Type:
Bug
Assignee:
Ofir Shaked
Components:
hp-application-automation-tools-plugin
Created:
16/Oct/14 1:27 PM
Description:
When running QTP scripts from jenkins, below error message is displayed in the logs
You do not have the required permissions to execute this action.
Function file: QualityCenter\Resources Resources\iNAV\Function Library\iNavLib10.vbs
Line (4447): " QCutil.CurrentTestSetTest.Field("TC_USER_01") = "Test"".
Project:
Jenkins
Priority:
Major
Reporter:
Shivakumar Balasubramanian
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] [jiratestresultreporter] (JENKINS-18572) The plugin can't post REST API request against the latest JIRA v6.1-OD-02
Praveen Lakshmanan commented on JENKINS-18572 The plugin cant post REST API request against the latest JIRA v6.1-OD-02 I'm also facing the same scenario, kindly update if anyone fixed this issue. Versions: Jenkins ver. 1.580 JiraTestResultReporter plugin 1.0.5 JIRA: 6.4 Console Output: JiraTestResultReporter DEBUG JiraTestResultReporter DEBUG Creating issue in project QAA at URL https://guidanz.atlassian.net/rest/api/2/issue/ JiraTestResultReporter INFO Reporting issue. JiraTestResultReporter DEBUG statusLine: HTTP/1.1 400 Bad Request JiraTestResultReporter DEBUG statusCode: 400 ERROR: Publisher JiraTestResultReporter.JiraReporter aborted due to exception java.lang.RuntimeException: JiraTestResultReporter ERROR Failed : HTTP error code : 400 at JiraTestResultReporter.JiraReporter.createJiraIssue(JiraReporter.java:188) at JiraTestResultReporter.JiraReporter.perform(JiraReporter.java:108) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) No emails were triggered. Finished: FAILURE 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] [cvs] (JENKINS-25184) CVS plugin creates hundreds of 'cvs server' processes which kill CVS server
Shrikant Pantina created JENKINS-25184 CVS plugin creates hundreds of cvs server processes which kill CVS server Issue Type: Bug Assignee: Unassigned Attachments: Jenkins Error.jpg Components: cvs Created: 16/Oct/14 2:14 PM Description: The 'CVS plugin creates hundreds of 'cvs server' processes which kill CVS server' seems to have been fixed in version 2.1 of CVS plugin , however i am facing the same issue even though I am using 2.11 version of CVS plugin. https://issues.jenkins-ci.org/browse/JENKINS-12612 Environment: Jenkins Version 1.583 , CVS Installed plugin version 2.11 Project: Jenkins Priority: Critical Reporter: Shrikant Pantina 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-25185) EnvInject does not resolve Windows Variable %ProgramFiles(x86)% correctly
Alexander Ziller created JENKINS-25185 EnvInject does not resolve Windows Variable %ProgramFiles(x86)% correctly Issue Type: Bug Assignee: Gregory Boissinot Components: envinject Created: 16/Oct/14 2:16 PM Description: I am trying to set a variable to the value of the Windows Property "ProgramFiles(x86)" which in my case points to C:\Program Files (x86) However, the pugin sets the variable to C:\Program Files(x86) I believe the error lies with the fact there are 2 variables on a 64 bit windows machine, ProgramFiles and ProgramFiles(x86) It looks like the plugin stops analyzing the variable name afte ProgramFiles because there is a variable with that name. Environment: Windows Project: Jenkins Priority: Minor Reporter: Alexander Ziller 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.
REK::AIX Admin||Raleigh, NC||
Hi, We have a long term requirement with our direct client for AIX Admin on SAP projects Contract Position: AIX Admin on SAP projects Location: Raleigh, NC Duration: 11/17/2014-11/16/2015 *Skills/Experience Required* · 5 or more years of experience as an AIX 6.x, 7.x Administrator · 5 or more years of experience running AIX on p-series midrange to enterprise hardware · 2 or more years of experience in IBM PowerVM · 2 or more years of experience in SAP NetWeaver / Business Suite · Proven experience as end-user for SAP Solution Manager · Ability to manage complex projects and tasks · Ability to lead others providing technical guidance and direction · Proven experience as an Administrator of AIX servers hosting Shared Services applications · Proven experience as an Administrator of the IBM HMC connected to all AIX system · Ability to work with senior level decision-makers on an on-going basis to develop strategic goals · 2 or more years of experience with Tivoli Storage Manager for backup and recovery · Proven understanding of technical issues to design architecture for stable technologies · Proven understanding of computer equipment capacity and limitations to devise or modify procedures to solve complex problems · Proven experience with systems analysis, design and programming · Excellent communication skill (written, verbal, presentations) · Excellent organization, analytical, planning and scheduling skills · Self-starter who can work with a large and diverse team of business, management and IT individuals · Proven experience working with large project team · Microsoft Suite experience (e.g. Word, Excel, PowerPoint, SharePoint, Visio) Thanks Regards, ALEX Sr.RECRUITER Sree Infotech LLC Email: a...@sreeinfotech.com Ph : 972-332-3471 Ext: 102 WWW.sreeinfotech.com Yahoo ID : chakri.sreeinfo Gtalk ID : chakri.sreeinfo Note: We respect your Online Privacy. This mail cannot be considered Spam as long as we include contact information and a method to be removed from our mailing list. To be removed from our mailing list, please reply with REMOVE in the subject line and your -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [coverity] (JENKINS-25186) Coverity plugin
anup ts created JENKINS-25186 Coverity plugin Issue Type: Bug Assignee: Ken Dang Components: coverity Created: 16/Oct/14 2:22 PM Description: Hi Team, I am getting teh following error when i click the check configuration for coverity in the post-action.May i know what i need to configure? A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) 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.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:37) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at org.jenkinsci.plugins.suppress_stack_trace.SuppressionFilter.doFilter(SuppressionFilter.java:34) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:202) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:180) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) 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.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) 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
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-23314) LR Scenario does not return SLA information in results
greg sanchez commented on JENKINS-23314 LR Scenario does not return SLA information in results Hi Terri, It seems that your fix hasn't been merged du to branch issue (see mrmann's response for more detail on : https://github.com/hpsa/hp-application-automation-tools-plugin/pull/1) Can you look at this again please? 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-25167) API requests crash with depth greater than 0
João Vale commented on JENKINS-25167 API requests crash with depth greater than 0 That's pretty close to what I did: I created a copy of the job (through the UI), disabled publishers and ran the job until I found a combination that didn't throw an error. It was simple enough as it is just a Freestlye job that fetches data from git, has a shell build step and calls the Cobertura and Checkstyle plugins. These were the combinations: both plugins: fails with the above trace only Cobertura: succeeds only Checkstyle: fails with the above trace 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.
Requirement: Lead Java Developer || Chicago, IL
Position:* Lead Java Developer* Location: Chicago, IL (Must be able to interview on person – NO SKYPE) Duration: Long Term Pay rate: 55.00 C2C *Must be available ASAP for an in Person Interview. NO SKYPE* *Must have GREAT Communication skills Must have a GO GETTER Personality* * Lead Java Developer* • Lead Java Developer (Must have Lead Experience) • *Must be a FULL Stack Developer* • Must have experience in *Developing an NEW Applications from conception (Scratch) *• Must have hands on Architecture experience • Must have the full stack of *Spring Architecture experience* • Must be very strong with *Spring MVC* • Must be very strong with *Spring Security* • Must be very strong with *Spring Inversion of Control/Dependency injection* • Must be very strong with *Spring Aspect-oriented programming framework* • Must be very strong with *Spring Batch* • Must be strong with *Spring JDBC *• Must be strong with *Spring Web Services * Thanks Regards, ALEX Sr.RECRUITER Sree Infotech LLC Email: a...@sreeinfotech.com Ph : 972-332-3471 Ext: 102 WWW.sreeinfotech.com Yahoo ID : chakri.sreeinfo Gtalk ID : chakri.sreeinfo Note: We respect your Online Privacy. This mail cannot be considered Spam as long as we include contact information and a method to be removed from our mailing list. To be removed from our mailing list, please reply with REMOVE in the subject line and your -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Position: Network Engineer - SAP ERP Hosting Services transition
Hi, We have a requirement with our *direct client* for a Network Engineer - SAP ERP Hosting Services transition Position: Network Engineer - SAP ERP Hosting Services transition Location: Raleigh, NC Duration: 11/17/2015-11/16/2015 Local Candidates Preferred *Skills/Experience Required* · Certified Network Engineer · 5 or more years of experience with F5 BIG IP LTM and GTM · 5 years of experience with Cisco and IBM Core Switches · 5 years of experience with network topology with SAP in an Internet and Intranet configuration · Ability to lead, plan and organize the work of others. · Ability to develop a project plan and manage technical projects involving work of others. · Proven experience with the configuration of routers, DSUs, encryptors, and other multi-vendor network equipment. · Proven understanding of impact of new technologies on current systems · Ability to make recommendations for technical modifications to prevent future problems and to make decisions on appropriate course of action for unique problems · Ability to assess needs of user and recommend small-scale solutions to meet customer needs · Ability to analyze the State’s network and security guidelines to translate them into a physical network layout · Proven understanding of network infrastructure · Ability to maintain and support all aspects of the wide and local area network (LAN/WAN) and corporate data communications · Proven understanding of technical issues to design architecture for stable technologies · Proven experience with analysis, design and programing · Excellent communication skill (written, verbal, presentations) · Excellent organization, analytical, planning and scheduling skills · Self-starter who can work with a large and diverse team of business, management and IT individuals · Demonstrated experience working with large project teams Microsoft Suite experience (e.g, Word, Excel, PowerPoint, SharePoint, Visio) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Position: Network Engineer - SAP ERP Hosting Services transition
Hi, We have a requirement with our *direct client* for a Network Engineer - SAP ERP Hosting Services transition Position: Network Engineer - SAP ERP Hosting Services transition Location: Raleigh, NC Duration: 11/17/2015-11/16/2015 Local Candidates Preferred *Skills/Experience Required* · Certified Network Engineer · 5 or more years of experience with F5 BIG IP LTM and GTM · 5 years of experience with Cisco and IBM Core Switches · 5 years of experience with network topology with SAP in an Internet and Intranet configuration · Ability to lead, plan and organize the work of others. · Ability to develop a project plan and manage technical projects involving work of others. · Proven experience with the configuration of routers, DSUs, encryptors, and other multi-vendor network equipment. · Proven understanding of impact of new technologies on current systems · Ability to make recommendations for technical modifications to prevent future problems and to make decisions on appropriate course of action for unique problems · Ability to assess needs of user and recommend small-scale solutions to meet customer needs · Ability to analyze the State’s network and security guidelines to translate them into a physical network layout · Proven understanding of network infrastructure · Ability to maintain and support all aspects of the wide and local area network (LAN/WAN) and corporate data communications · Proven understanding of technical issues to design architecture for stable technologies · Proven experience with analysis, design and programing · Excellent communication skill (written, verbal, presentations) · Excellent organization, analytical, planning and scheduling skills · Self-starter who can work with a large and diverse team of business, management and IT individuals · Demonstrated experience working with large project teams Microsoft Suite experience (e.g, Word, Excel, PowerPoint, SharePoint, Visio) Thanks Regards, ALEX Sr.RECRUITER Sree Infotech LLC Email: a...@sreeinfotech.com Ph : 972-332-3471 Ext: 102 WWW.sreeinfotech.com Yahoo ID : chakri.sreeinfo Gtalk ID : chakri.sreeinfo Note: We respect your Online Privacy. This mail cannot be considered Spam as long as we include contact information and a method to be removed from our mailing list. To be removed from our mailing list, please reply with REMOVE in the subject line and your -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Contract Position: VMware Windows Administrator - SAP Hosting Services
Hi, We have a requirement with our *direct client* for a VMware Windows Administrator - SAP Hosting Services transition Contract Position: VMware Windows Administrator - SAP Hosting Services transition Location: Raleigh, NC Duration: 11/17/2015-11/16/2015 Local Candidates Preferred *Skills/Experience Required* · Current MCSE in Server Infrastructure - Server 2008 or later · 5 or more years of experience as a Windows Server versions 2003 – 2012 Administrator · 5 or more years of experience with Microsoft Active Directory Technology · 5 or more years of experience with Microsoft Clustering Technologies · 5 or more years of experience with VMWare ESX or related technology · Ability to manage complex projects and tasks · Ability to lead others providing technical guidance and direction · Manage Virtual Machine using VMWare ESX · Ability to work with senior level decision-makers on an on-going basis to develop strategic goals · Proven understanding of technical issues to design architecture for stable technologies · Proven experience with computer equipment capacity and limitations · Proven experience with systems analysis, design and programming · Excellent communication skill (written, verbal, presentations) Thanks Regards, ALEX Sr.RECRUITER Sree Infotech LLC Email: a...@sreeinfotech.com Ph : 972-332-3471 Ext: 102 WWW.sreeinfotech.com Yahoo ID : chakri.sreeinfo Gtalk ID : chakri.sreeinfo Note: We respect your Online Privacy. This mail cannot be considered Spam as long as we include contact information and a method to be removed from our mailing list. To be removed from our mailing list, please reply with REMOVE in the subject line and your -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-7695) archiving throws hudson.util.IOException2: java.io.IOException: request to write '3977' bytes exceeds size in header of '41955006'
Tilman Blumenbach commented on JENKINS-7695 archiving throws hudson.util.IOException2: java.io.IOException: request to write 3977 bytes exceeds size in header of 41955006 We are having this issue as well; we are running Jenkins 1.580. 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] [extended-choice-parameter] (JENKINS-25187) Extended choice parameter multi level select list not populating
Len Isac created JENKINS-25187 Extended choice parameter multi level select list not populating Issue Type: Bug Assignee: vimil Attachments: build_setup_notworking.png Components: extended-choice-parameter Created: 16/Oct/14 3:20 PM Description: Multi-level select list does not populate out of nowhere. It was working before. I tried uninstalling and reinstalling the plugin, running safeRestart, still no luck. I was working on updating the plugin, but never uploaded it to this particular instance of Jenkins, so the version of the plugin and property file have not changed. Just randomly stopped working out of the blue. I tried creating the properties file again as well, but still no luck. Jenkins recognizes the property file when configuring the job with the parameter, but won't display it. Environment: Jenkins ver. 1.554.2 Extended choice parameter plugin ver. 0.33 Windows 7 Chrome ver. 37.0.2062.124 Project: Jenkins Labels: jenkins plugin Priority: Major Reporter: Len Isac 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] [coverity] (JENKINS-25186) Coverity plugin
Daniel Beck updated JENKINS-25186 Coverity plugin Clearly not a blocker. Change By: Daniel Beck (16/Oct/14 3:21 PM) Priority: Blocker Major 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] [checkstyle] (JENKINS-25167) API requests crash with depth greater than 0
Daniel Beck updated JENKINS-25167 API requests crash with depth greater than 0 Right, already mentioned in the original report. My apologies. Reassigning this specific issue to checkstyle. Core (or rather Stapler) could use better error reporting, will try to look into that. That's an improvement though, not a bug. Change By: Daniel Beck (16/Oct/14 3:24 PM) Component/s: checkstyle Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-25185) EnvInject does not resolve Windows Variable %ProgramFiles(x86)% correctly
Daniel Beck
commented on JENKINS-25185
EnvInject does not resolve Windows Variable %ProgramFiles(x86)% correctly
"(" is probably not considered valid part of an environment variable name.
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] [coverity] (JENKINS-25186) Coverity plugin
Daniel Beck commented on JENKINS-25186 Coverity plugin Issue report needs to specify versions of Jenkins and Coverity plugin used. Would be helpful to include screenshot of options for coverity set. "Production" is useless as information, specify OS etc.. Issue title is useless. 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] [coverity] (JENKINS-25186) Coverity plugin
anup ts commented on JENKINS-25186 Coverity plugin Jenkins Version : 1.565.1 Coverity Plugin version : 1.4.1 Should we configure something at the global level? 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-9146) Allow archiving of empty directories to be enabled/disabled
Radka Nepejchalova commented on JENKINS-9146 Allow archiving of empty directories to be enabled/disabled We need to have empty directories as well, is there at least any work-around? 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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
David Tanner resolved JENKINS-24954 as Fixed Test PASSed comments added even if Published Jenkins URL Change By: David Tanner (16/Oct/14 5:04 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] [ghprb] (JENKINS-24954) Test PASSed comments added even if Published Jenkins URL
David Tanner commented on JENKINS-24954 Test PASSed comments added even if Published Jenkins URL Found the bug. PR #50 Added a curly brace to line 167 probably unintentionally. I have fixed the problem, and it will be released with 16-5. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-25176) I can't store the private key in job configure page
Daniel Beck commented on JENKINS-25176 I cant store the private key in job configure page Are you able to scroll down? Or tab navigate to the buttons? 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] [checkstyle] (JENKINS-25167) API requests crash with depth greater than 0
Ulli Hafner updated JENKINS-25167 API requests crash with depth greater than 0 I don't see why this is not a bug in stapler? Until we see what actually is broken I think both components make sense. In my plug-in I just use the suggested annotations. So if these are misplaced this should be reported at compile time. I also don't think that is an improvement in core, this actually is an important fix, since so many plugins are affected... Change By: Ulli Hafner (16/Oct/14 5:21 PM) Priority: Critical Minor Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-21160) Jenkins CLI cannot handle arguments with equals signs (=)
Damien Nozay
commented on JENKINS-21160
Jenkins CLI cannot handle arguments with equals signs (=)
remoting not only depends on args4j but also bundles it.
execution
idbundle-arg4j/id
phaseprocess-classes/phase
goals
goalunpack-dependencies/goal
/goals
configuration
outputDirectory${project.build.outputDirectory}/outputDirectory
includeScopeprovided/includeScope
includeArtifactIdsargs4j/includeArtifactIds
includeGroupIdsargs4j/includeGroupIds
/configuration
/execution
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-9146) Allow archiving of empty directories to be enabled/disabled
Daniel Beck commented on JENKINS-9146 Allow archiving of empty directories to be enabled/disabled Straightforward workaround: Zip/Tar the build result up as part of the build. Archive those files. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-25176) I can't store the private key in job configure page
Daniel Beck updated JENKINS-25176 I cant store the private key in job configure page in the credentials page ,I success store the private hey, add in job configure page choose the key I need Reducing priority because of workaround. Change By: Daniel Beck (16/Oct/14 6:03 PM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-25176) I can't store the private key in job configure page
Daniel Beck commented on JENKINS-25176 I cant store the private key in job configure page Are you planning to work on this yourself, or why did you assign it to yourself? 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-22239) Doesn't create root folder when installing JNLP Windows Service
Oleg Nenashev updated JENKINS-22239 Doesnt create root folder when installing JNLP Windows Service Change By: Oleg Nenashev (16/Oct/14 6:21 PM) Labels: winsw Component/s: core Component/s: slave-setup-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] [checkstyle] (JENKINS-25167) API requests crash with depth greater than 0
Daniel Beck commented on JENKINS-25167 API requests crash with depth greater than 0 Right, the fact it only occurred with Checkstyle lead me to believe it's an issue with that prematurely. I was able to reproduce the reported problem in standalone Jenkins 1.584 with Checkstyle 3.39, in a freestyle job with Git checking out jenkinsci/checkstyle-plugin, Maven checkstyle:checkstyle, and a default checkstyle publicher (otherwise pristine install). /job/foo/api/xml?depth=2 and /job/foo/1/api/xml?depth=1 failed. Debugging into Stapler 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] [build-failure-analyzer] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails
Jason Wong commented on JENKINS-17658 Provide a token so that build failure causes can be included in build failure emails did you ever find out how to do this? I'm also having the same problems. 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-failure-analyzer] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails
Steve Mokris
commented on JENKINS-17658
Provide a token so that build failure causes can be included in build failure emails
I'm using the Email-ext plugin. In the "Editable Email Notification" post-build step, I added this to the "Default Content" box:
${BUILD_FAILURE_ANALYZER, includeTitle=true, includeIndications=true, useHtmlFormat=true}
…which works 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] [core] (JENKINS-25153) Update ssh-slaves and ssh-credentials plugins in war file
Matthew Smith commented on JENKINS-25153 Update ssh-slaves and ssh-credentials plugins in war file Are these the right files to delete to "unsign" it? zip -d /usr/share/jenkins/jenkins.war META-INF/JENKINS.SF zip -d /usr/share/jenkins/jenkins.war META-INF/JENKINS.RSA That did not appear to work, but I may have the wrong files. 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] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Damien Nozay commented on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found It may be related to https://github.com/jenkinsci/jenkins/commit/79c905e6d0b03b075eef5339b73a6e8c55acd620 If you logged in with https:// and had a cookie with secure flag then if you visit the same link with http:// instead, you cannot use the cookie. 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-failure-analyzer] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails
Jason Wong
commented on JENKINS-17658
Provide a token so that build failure causes can be included in build failure emails
Yeah, I got that working as well, the problem I have is when I use the same token in a groovy template. Other tokens work though like ${build.*} etc.
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-25153) Update ssh-slaves and ssh-credentials plugins in war file
Jesse Glick commented on JENKINS-25153 Update ssh-slaves and ssh-credentials plugins in war file Yes, those, plus the file entries (with Name and SHA-256-Digest) in META-INF/MANIFEST.MF. 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-failure-analyzer] (JENKINS-17658) Provide a token so that build failure causes can be included in build failure emails
hugo fonseca commented on JENKINS-17658 Provide a token so that build failure causes can be included in build failure emails No, I still haven't found the solution for this. I tried something like: http://jenkins-ci.361315.n4.nabble.com/Build-Failure-Analyzer-Email-Ext-td4720692.html and when I try the "Email template testing" it works fine but since in the real build the scan is triggered after the email being sent it does not work. :/ 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] [checkstyle] (JENKINS-25167) API requests crash with depth greater than 0
Daniel Beck commented on JENKINS-25167 API requests crash with depth greater than 0 Analysis Core annotates hudson.plugins.analysis.core.AbstractResultAction.getTooltip(int) with @Exported, but Stapler seems incapable of exporting methods with parameters. 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-24357) Jenkins 1.535+ versions do not work on Solaris 10
Bhagyesh Shah commented on JENKINS-24357 Jenkins 1.535+ versions do not work on Solaris 10 I tried with higher permgen of 1024mb, did not work 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] [analysis-core] (JENKINS-25167) API requests crash with depth greater than 0
Daniel Beck updated JENKINS-25167 API requests crash with depth greater than 0 Assigning back to analysis-core to fix the annotation/getter. Improvement in Stapler to e.g. skip methods with arguments despite being @Exported (+ log warning), and/or adding an annotation processor preventing this would certainly be useful improvements, but separate from this specific occurrence. Change By: Daniel Beck (16/Oct/14 8:41 PM) Priority: Minor Major Component/s: analysis-core Component/s: checkstyle Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-core] (JENKINS-25167) API requests crash with depth greater than 0
Ulli Hafner commented on JENKINS-25167 API requests crash with depth greater than 0 Thanks for tracking this down! 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] [warnings] (JENKINS-25054) javax.servlet.ServletException: java.lang.IllegalArgumentException when depth != 0 in job API
SCM/JIRA link daemon commented on JENKINS-25054 javax.servlet.ServletException: java.lang.IllegalArgumentException when depth != 0 in job API Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/AbstractResultAction.java http://jenkins-ci.org/commit/analysis-core-plugin/7d2f63c7c04889ac05c9c4849b67fad9fcc1c449 Log: FIXED JENKINS-25167FIXED JENKINS-25054 Do not export tooltip since it requires parameter. 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] [analysis-core] (JENKINS-25167) API requests crash with depth greater than 0
SCM/JIRA link daemon commented on JENKINS-25167 API requests crash with depth greater than 0 Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/AbstractResultAction.java http://jenkins-ci.org/commit/analysis-core-plugin/7d2f63c7c04889ac05c9c4849b67fad9fcc1c449 Log: FIXED JENKINS-25167FIXED JENKINS-25054 Do not export tooltip since it requires parameter. 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-plugin] (JENKINS-24788) Cannot run program /bin/java on maven 3 projects
Stephane Odul commented on JENKINS-24788 Cannot run program /bin/java on maven 3 projects Issue is still present with 1.584. 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.
Hello
Hello, How are you? hope fine, I Want to introduce my self to you before I go further, My Name is Hassana. I will like to have a good relationship with you, if you wouldn't mind, I will like to hear from you soon through this email address because, I have something very important I will like to tell you. Thanks and God bless you, Miss Hassana, -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact] (JENKINS-25155) NPE during Copy Artifact in Promotion
Bruce Edge
commented on JENKINS-25155
NPE during Copy Artifact in Promotion
I can confirm the same problem.
I downgraded only the copy artifact plugin from 1.32 to 1.32 and the problem goes away.
FWIW here's my stack trace:
Promoting Reader-Android-build-develop #546
FATAL: null
java.lang.NullPointerException
at hudson.plugins.copyartifact.CopyArtifact$EnvAction.add(CopyArtifact.java:512)
at hudson.plugins.copyartifact.CopyArtifact$EnvAction.access$500(CopyArtifact.java:502)
at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:296)
at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:280)
at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:222)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
at hudson.model.Run.execute(Run.java:1754)
at hudson.model.Run.run(Run.java:1692)
at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:172)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
and my promotion config:
buildSteps
hudson.plugins.copyartifact.CopyArtifact plugin="copyartifact@1.30"
project${PROMOTED_JOB_NAME}/project
filter**/*release*.apk,**/*-debug-unaligned*.apk/filter
target/u0/releases/Reader-Android/${GIT_BRANCH}/QA/${PROMOTED_NUMBER}/target
selector class="hudson.plugins.copyartifact.PermalinkBuildSelector"
idQA/id
/selector
flattentrue/flatten
doNotFingerprintArtifactsfalse/doNotFingerprintArtifacts
/hudson.plugins.copyartifact.CopyArtifact
hudson.plugins.copyartifact.CopyArtifact plugin="copyartifact@1.30"
project${PROMOTED_JOB_NAME}/project
filter**/build/outputs/proguard/**/filter
target/u0/releases/Reader-Android/${GIT_BRANCH}/QA/${PROMOTED_NUMBER}/target
selector class="hudson.plugins.copyartifact.PermalinkBuildSelector"
idQA/id
/selector
doNotFingerprintArtifactsfalse/doNotFingerprintArtifacts
/hudson.plugins.copyartifact.CopyArtifact
hudson.plugins.copyartifact.CopyArtifact plugin="copyartifact@1.30"
project${PROMOTED_JOB_NAME}/project
filter**/src/androidTest/**,**/lib/**,**/build.gradle/filter
target/u0/releases/Reader-Android/${GIT_BRANCH}/QA/${PROMOTED_NUMBER}/target
selector class="hudson.plugins.copyartifact.PermalinkBuildSelector"
idQA/id
/selector
doNotFingerprintArtifactsfalse/doNotFingerprintArtifacts
/hudson.plugins.copyartifact.CopyArtifact
hudson.tasks.Shell
commandgit push --tag || true/command
/hudson.tasks.Shell
/buildSteps
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] [copyartifact] (JENKINS-25155) NPE during Copy Artifact in Promotion
Bruce Edge
edited a comment on JENKINS-25155
NPE during Copy Artifact in Promotion
I can confirm the same problem.
I downgraded only the copy artifact plugin from 1.32 to 1.31 and the problem goes away.
FWIW here's my stack trace:
Promoting Reader-Android-build-develop #546
FATAL: null
java.lang.NullPointerException
at hudson.plugins.copyartifact.CopyArtifact$EnvAction.add(CopyArtifact.java:512)
at hudson.plugins.copyartifact.CopyArtifact$EnvAction.access$500(CopyArtifact.java:502)
at hudson.plugins.copyartifact.CopyArtifact.perform(CopyArtifact.java:296)
at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:280)
at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:222)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533)
at hudson.model.Run.execute(Run.java:1754)
at hudson.model.Run.run(Run.java:1692)
at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:172)
at hudson.model.ResourceController.execute(ResourceController.java:89)
at hudson.model.Executor.run(Executor.java:240)
and my promotion config:
buildSteps
hudson.plugins.copyartifact.CopyArtifact plugin="copyartifact@1.30"
project${PROMOTED_JOB_NAME}/project
filter**/*release*.apk,**/*-debug-unaligned*.apk/filter
target/u0/releases/Reader-Android/${GIT_BRANCH}/QA/${PROMOTED_NUMBER}/target
selector class="hudson.plugins.copyartifact.PermalinkBuildSelector"
idQA/id
/selector
flattentrue/flatten
doNotFingerprintArtifactsfalse/doNotFingerprintArtifacts
/hudson.plugins.copyartifact.CopyArtifact
hudson.plugins.copyartifact.CopyArtifact plugin="copyartifact@1.30"
project${PROMOTED_JOB_NAME}/project
filter**/build/outputs/proguard/**/filter
target/u0/releases/Reader-Android/${GIT_BRANCH}/QA/${PROMOTED_NUMBER}/target
selector class="hudson.plugins.copyartifact.PermalinkBuildSelector"
idQA/id
/selector
doNotFingerprintArtifactsfalse/doNotFingerprintArtifacts
/hudson.plugins.copyartifact.CopyArtifact
hudson.plugins.copyartifact.CopyArtifact plugin="copyartifact@1.30"
project${PROMOTED_JOB_NAME}/project
filter**/src/androidTest/**,**/lib/**,**/build.gradle/filter
target/u0/releases/Reader-Android/${GIT_BRANCH}/QA/${PROMOTED_NUMBER}/target
selector class="hudson.plugins.copyartifact.PermalinkBuildSelector"
idQA/id
/selector
doNotFingerprintArtifactsfalse/doNotFingerprintArtifacts
/hudson.plugins.copyartifact.CopyArtifact
hudson.tasks.Shell
commandgit push --tag || true/command
/hudson.tasks.Shell
/buildSteps
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] [copyartifact] (JENKINS-25155) NPE during Copy Artifact in Promotion
ikedam assigned JENKINS-25155 to ikedam NPE during Copy Artifact in Promotion Change By: ikedam (16/Oct/14 11:03 PM) Assignee: ikedam 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] [active-directory] (JENKINS-22358) Jenkins 1.556 gives 'Error 404 Not Found'
Liam Reimers commented on JENKINS-22358 Jenkins 1.556 gives Error 404 Not Found Damien: That jives - I see that the 404 is an http: page, and when I replace that with https: (and remove the jsessionid cruft) it works as expected. 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-24046) Updating a WAR should unpin a plugin which is now older than the bundled plugin
Kohsuke Kawaguchi started work on JENKINS-24046 Updating a WAR should unpin a plugin which is now older than the bundled plugin Change By: Kohsuke Kawaguchi (17/Oct/14 12:16 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24046) Updating a WAR should unpin a plugin which is now older than the bundled plugin
Kohsuke Kawaguchi assigned JENKINS-24046 to Kohsuke Kawaguchi Updating a WAR should unpin a plugin which is now older than the bundled plugin Change By: Kohsuke Kawaguchi (17/Oct/14 12:17 AM) Assignee: KohsukeKawaguchi 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.
