[JIRA] [durable-task-plugin] (JENKINS-27152) Store sh control files outside of workspace
Title: Message Title Christoph Obexer commented on JENKINS-27152 Re: Store sh control files outside of workspace Jesse Glick the bat 'cd .. && git clean -fdx' was required for previous versions where the control files were in the current working directory. The 1.8 update broke compatibility with that workaround because the control files moved from the CWD to the parent directory which moved them back to where they can't be. With version 1.8 the bat 'git clean -fdx' is what is needed now. This incompatibility means that the change to the Jenkinsfile needs to be back-ported to all affected versions before they can build a new build successfully, however doing so immediately would trigger maintenance builds unnecessarily (Multi-Branch Pipeline Job) - which makes this incompatibility annoying. And thanks for the long explanation! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33511) env.WORKSPACE should be available within node{} in Pipeline
Title: Message Title
Andrea Baccega commented on JENKINS-33511
Re: env.WORKSPACE should be available within node{} in Pipeline
IMHO this should be fixed too
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title James Femia edited a comment on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" We are having the same issue with slaves running on Win10 in VMWare , already running slave.jar as a scheduled task on login so the suggested workaround does not help us Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Title: Message Title James Femia commented on JENKINS-23852 Re: slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" We are having the same issue, already running slave.jar as a scheduled task on login so the suggested workaround does not help us Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-33541) Provide snippets of code in the compatibility readme
Title: Message Title Andrea Baccega created an issue Jenkins / JENKINS-33541 Provide snippets of code in the compatibility readme Issue Type: Improvement Assignee: Jesse Glick Components: workflow-plugin Created: 15/Mar/16 7:33 AM Priority: Minor Reporter: Andrea Baccega It would be helpful to have brief snippets of code on how to use the compatible plugins to speed up development. Plus, Since I've been using Jenkins and this plugin for only 1 day i'm not able to use some of the plugins within my Jenkinsfile due to my lack of knowledge of how things works Some brief examples might solve my and many other issues. Add Comment
[JIRA] [core] (JENKINS-31162) New item categorization and dynamic choice offering
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-31162 Re: New item categorization and dynamic choice offering gus reiber Let me check it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-33095) Upgrade to folder 5.2.1 + matrix-auth 1.3 results in dead Jenkins
Title: Message Title Slawomir Czarko commented on JENKINS-33095 Re: Upgrade to folder 5.2.1 + matrix-auth 1.3 results in dead Jenkins Matrix Auth 1.3.2 does NOT automatically pull in CloudBees Folders Plugin. Installing CloudBees Folders Plugin manually solves the problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33375) Inline help doesn't work with tabbed configuration page
Title: Message Title Tom FENNELLY resolved as Fixed Jenkins / JENKINS-33375 Inline help doesn't work with tabbed configuration page Change By: Tom FENNELLY Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [zephyr-for-jira-test-management-plugin] (JENKINS-33542) java.lang.ClassCastException
Title: Message Title
Ahmed Charfi created an issue
Jenkins / JENKINS-33542
java.lang.ClassCastException
Issue Type:
Bug
Assignee:
Zephyr Developer
Components:
zephyr-for-jira-test-management-plugin
Created:
15/Mar/16 9:03 AM
Priority:
Major
Reporter:
Ahmed Charfi
i am running a simple calculator project which is located in github. i want to Publish test result to Zephyr for JIRA'. i get always ERROR: Build step failed with exception java.lang.ClassCastException Started by user anonymous Building in workspace /var/lib/jenkins/jobs/JenkiszephyrAutomationProject/workspace > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url https://github.com/AhmedCharfi/charfi.git # timeout=10 Fetching upstream changes from https://github.com/AhmedCharfi/charfi.git > git --version # timeout=10 using .gitcredentials to set credentials > git config --local credential.username AhmedCharfi # timeout=10 > git config --local credential.helper store --file=/tmp/git4288973419038232058.credentials # timeout=10 > git -c core.askpass=true fetch --tags --progress https://github.com/AhmedCharfi/charfi.git +refs/heads/:refs/remotes/origin/ > git config --local --remove-section credential # timeout=10 > git rev-parse refs/remotes/origin/master^ {commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/master^{commit}
# timeout=10 Checking out Revision 3fbf34ac0645f5426d84f992d9607042317922fa (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 3fbf34ac0645f5426d84f992d9607042317922fa > git rev-list 3fbf34ac0645f5426d84f992d9607042317922fa # timeout=10 [workspace] $ mvn clean
[JIRA] [core] (JENKINS-33478) Cleaning or deleting workspace fails with non-ASCII filename
Title: Message Title ickersep commented on JENKINS-33478 Re: Cleaning or deleting workspace fails with non-ASCII filename No, I previously overlooked the suggested workaround of JENKINS-12610. So I tried right now and added -Dfile.encoding=UTF-8 to JAVA_ARGS in /etc/default/jenkins, restarted Jenkins and added -Dfile.encoding=UTF-8 to the JVM options in the slave configuration and relaunched the slave. These settings don't make a difference though. It still can't delete the files. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33474) Pipeline job hanging
Title: Message Title Maciej Gawinecki updated an issue Jenkins / JENKINS-33474 Pipeline job hanging Change By: Maciej Gawinecki Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33474) Pipeline job hanging
Title: Message Title
Maciej Gawinecki commented on JENKINS-33474
Re: Pipeline job hanging
I have the same problem:
I'm using Pipeline plugin latest vrsion 1.15 (https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin) on the latest Jenkins 1.653 with the following pipeline script:
node { timeout(40) { stage concurrency: 1, name: 'Build everything' build 'blablablabla' }
}
The job has been hanging since yesterday on "Build everything" stage despite the defined timeout.
Why is it like that? How can I get more information about the reason of the problem?
Here's the thread dump
Thread #4 at DSL.stage(Native Method) at WorkflowScript.run(WorkflowScript:3) at DSL.timeout(Native Method) at WorkflowScript.run(WorkflowScript:2) at DSL.node(Native Method) at WorkflowScript.run(WorkflowScript:1)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33474) Pipeline job hanging
Title: Message Title
Maciej Gawinecki edited a comment on JENKINS-33474
Re: Pipeline job hanging
I have the same problem:I'm using Pipeline plugin latest vrsion 1.15 (https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin) on the latest Jenkins 1.653 with the following pipeline script: {code:groovy} node {timeout(40) {stage concurrency: 1, name: 'Build everything'build 'blablablabla'}} {code} The job has been hanging since yesterday on "Build everything" stage despite the defined timeout.Why is it like that? How can I get more information about the reason of the problem?Here's the thread dump Thread #4 at DSL.stage(Native Method) at WorkflowScript.run(WorkflowScript:3) at DSL.timeout(Native Method) at WorkflowScript.run(WorkflowScript:2) at DSL.node(Native Method) at WorkflowScript.run(WorkflowScript:1)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33474) Pipeline job hanging
Title: Message Title
Maciej Gawinecki edited a comment on JENKINS-33474
Re: Pipeline job hanging
I have the same problem : . I'm using Pipeline plugin latest vrsion 1.15 (https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin) on the latest Jenkins 1.653 with the following pipeline script: {code :groovy }node {timeout(40) {stage concurrency: 1, name: 'Build everything'build 'blablablabla'}}{code}The job has been hanging since yesterday on "Build everything" stage despite the defined timeout.Why is it like that? How can I get more information about the reason of the problem?Here's the thread dump Thread #4 at DSL.stage(Native Method) at WorkflowScript.run(WorkflowScript:3) at DSL.timeout(Native Method) at WorkflowScript.run(WorkflowScript:2) at DSL.node(Native Method) at WorkflowScript.run(WorkflowScript:1)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33474) Pipeline job hanging
Title: Message Title
Maciej Gawinecki edited a comment on JENKINS-33474
Re: Pipeline job hanging
I have the same problem.I'm using Pipeline plugin latest vrsion 1.15 (https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Plugin) on the latest Jenkins 1.653 with the following pipeline script:{code}node {timeout(40) {stage concurrency: 1, name: 'Build everything'build 'blablablabla'}}{code}The job has been hanging since yesterday on "Build everything" stage despite the defined timeout.Why is it like that? How can I get more information about the reason of the problem?Here's the thread dump {code} Thread #4 at DSL.stage(Native Method) at WorkflowScript.run(WorkflowScript:3) at DSL.timeout(Native Method) at WorkflowScript.run(WorkflowScript:2) at DSL.node(Native Method) at WorkflowScript.run(WorkflowScript:1) {code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32455) Artifacts lost when renaming matrix project with custom Build record directory
Title: Message Title Russell Gallop commented on JENKINS-32455 Re: Artifacts lost when renaming matrix project with custom Build record directory No exception in the log (I've removed messages not related to this job). Build #3 was pre-rename though the log seems to use the new name. (now with jenkins 1.642.2). JENKINS_32455_test_renamed/FOO=bar #3 main build action completed: SUCCESS Mar 15, 2016 9:42:58 AM INFO hudson.model.Run execute JENKINS_32455_test_renamed #3 main build action completed: SUCCESS ... Mar 15, 2016 9:49:38 AM INFO hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness queueChangeSet Queue of changeset A jobs/JENKINS_32455_test/config.xml aborted (scm manipulator not settled !) Mar 15, 2016 9:49:39 AM INFO hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness queueChangeSet Queue of changeset A jobs/JENKINS_32455_test/config.xml aborted (scm manipulator not settled !) Mar 15, 2016 9:49:40 AM INFO hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness queueChangeSet Queue of changeset A jobs/JENKINS_32455_test/config.xml aborted (scm manipulator not settled !) ... Mar 15, 2016 9:53:04 AM INFO hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness queueChangeSet Queue of changeset D jobs/JENKINS_32455_test aborted (scm manipulator not settled !) ... Mar 15, 2016 10:04:41 AM INFO hudson.model.Run execute JENKINS_32455_test_renamed/FOO=bar #4 main build action completed: SUCCESS Mar 15, 2016 10:04:42 AM INFO hudson.model.Run execute JENKINS_32455_test_renamed #4 main build action completed: SUCCESS Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more option
[JIRA] [github-branch-source-plugin] (JENKINS-33530) Pull Requests "submitted from origin repository, skipping" not clear why this is skipping
Title: Message Title Jeff Koenig updated an issue Jenkins / JENKINS-33530 Pull Requests "submitted from origin repository, skipping" not clear why this is skipping Change By: Jeff Koenig The github-branch-source-plugin says that it should build branches and PR's, and from digging through commit history, I see that it is intended for private repos only, and it will not work for remote repos. However I have a private repo, and my PR's are all from origin, and it scans my pull requests, it says "submitted from origin repository, skipping".I've looked through https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md#creating-multibranch-projects , and I've looked at the PR that put this check in place, https://github.com/jenkinsci/github-branch-source-plugin/pull/14 , but no where does it try to explain why we are skipping because it was "submitted from origin repository", isn't that the ideal PR to build? Because we know they have access to that repo since it is from origin?If there is a legit reason for this, then this message should be clarified better.Link to the code that specifies that it should skip a pull request in this situation, https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java#L290-L292 , which is where the PR is coming from someone other then the specifed owner of the repo, but they may still be one of the owners of the repo. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscri
[JIRA] [core] (JENKINS-33474) Pipeline job hanging
Title: Message Title Martin Stolle commented on JENKINS-33474 Re: Pipeline job hanging Maciej Gawinecki Use http://your.jenkins.server/threadDump to get a Thread dump. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33543) very long start and very high hdd usage
Title: Message Title Sergey Solozhentsev created an issue Jenkins / JENKINS-33543 very long start and very high hdd usage Issue Type: Bug Assignee: Unassigned Attachments: jenkins.err.log Components: core Created: 15/Mar/16 10:40 AM Labels: performance startup Priority: Major Reporter: Sergey Solozhentsev I had troubles on my bui;ld machine. After upgrade to lates version of jenkins I found that it restarts very long time (more than hour). And I noticed that hdd load is 100%. There is no a lot data but load is 100% (it also very strange). it seems jenkins creates hude amount of files
[JIRA] [github-branch-source-plugin] (JENKINS-33530) Pull Requests "submitted from origin repository, skipping" not clear why this is skipping
Title: Message Title Jeff Koenig updated an issue Jenkins / JENKINS-33530 Pull Requests "submitted from origin repository, skipping" not clear why this is skipping Change By: Jeff Koenig The github-branch-source-plugin says that it should build branches and PR's, and from digging through commit history, I see that it is intended for private repos only, and it will not work for remote repos. However I have a private repo, and my PR's are all from origin, and it scans my pull requests, it says "submitted from origin repository, skipping".I've looked through https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md#creating-multibranch-projects , and I've looked at the PR that put this check in place, https://github.com/jenkinsci/github-branch-source-plugin/pull/14 , but no where does it try to explain why we are skipping because it was "submitted from origin repository", isn't that the ideal PR to build? Because we know they have access to that repo since it is from origin?If there is a legit reason for this, then this message should be clarified better.Link to the code that specifies that it should skip a pull request in this situation, https://github.com/jenkinsci/github-branch-source-plugin/blob/master/src/main/java/org/jenkinsci/plugins/github_branch_source/GitHubSCMSource.java#L290-L292 . Why would we want to ignore PR's from the origin repo? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and s
[JIRA] [slack-plugin] (JENKINS-32348) Jenkins not starting on slave
Title: Message Title Kurt Madel assigned an issue to Kurt Madel Jenkins / JENKINS-32348 Jenkins not starting on slave Change By: Kurt Madel Assignee: Sam Gleske Kurt Madel Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slack-plugin] (JENKINS-32348) Jenkins not starting on slave
Title: Message Title Kurt Madel commented on JENKINS-32348 Re: Jenkins not starting on slave Not clear how this is a slack-plugin issue. Did this specifically start happening after the slack plugin was installed? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slack-plugin] (JENKINS-30929) UnsupportedOperationException when "Notify Build Start" notification enabled and TFS SCM is used
Title: Message Title Kurt Madel assigned an issue to Kurt Madel Jenkins / JENKINS-30929 UnsupportedOperationException when "Notify Build Start" notification enabled and TFS SCM is used Change By: Kurt Madel Assignee: Sam Gleske Kurt Madel Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33543) very long start and very high hdd usage
Title: Message Title Sergey Solozhentsev commented on JENKINS-33543 Re: very long start and very high hdd usage I found very huge amount of temporary files (It hard to open directory C:\windows\temp even in console ). It seems that jenkins does not remove temporaty files. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves-plugin] (JENKINS-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title joao cravo commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel Hey guys! I'm running Jenkins on AWS EC2 and I got this same problem. I was able to fix it with https://github.com/scala/scala-jenkins-infra/issues/26#issuecomment-73825006 I don't know exactly why, but it fixed.. anyone can explain why? Cheers Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials-binding-plugin] (JENKINS-33544) Support credentials binding for "SSH Username with private key"
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-33544 Support credentials binding for "SSH Username with private key" Issue Type: Improvement Assignee: Jesse Glick Components: credentials-binding-plugin Created: 15/Mar/16 11:20 AM Priority: Minor Reporter: Cyrille Le Clerc "SSH Username with private key" is not supported by the Credentials Binding Plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-s
[JIRA] [core] (JENKINS-33535) It would be nice to show the Jenkins version during the initial setup wizard
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-33535 It would be nice to show the Jenkins version during the initial setup wizard Change By: Daniel Beck Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33369) Recommended plugins for 2.0 should refer to "agents" rather than "slaves"
Title: Message Title Daniel Beck commented on JENKINS-33369 Re: Recommended plugins for 2.0 should refer to "agents" rather than "slaves" I'd love to see how you're going to fix the SSH Slaves Plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-33545) The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0.
Title: Message Title Davy Courvoisier created an issue Jenkins / JENKINS-33545 The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0. Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 15/Mar/16 11:30 AM Environment: TFS Plugin: V 4.1.0 Jenkins: 1.642.1 and 1.609.3 Priority: Blocker Reporter: Davy Courvoisier Upgrading TFS Plugin from version 4.0.0 to 4.1.0 make system unusable. Tried creating a new job from scratch and same error occurs. Workaround is to revert to V4.0.0. This is reproduced on 2 different instances. The following error occurs when the TFS plugin tries to connect to TFS(poll, checkout): FATAL: The SOAP endpoint http://tfsurl:8080/tfs/collection/Services/v1.0/Registration.asmx could not be contacted. HTTP status: 302 com.microsoft.tfs.core.exceptions.TECoreException: The SOAP endpoint http://tfsurl:8080/tfs/collection/Services/v1.0/Registration.asmx could not be contacted. HTTP status: 302 at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:105) at com.microsoft.tfs.core.exceptions.mappers.RegistrationExceptionMapper.map(RegistrationExceptionMapper.java:23) at com.microsoft.tfs.core.clients.registration.RegistrationData.newFromServer(RegistrationData.java:70) at com.microsoft.tfs.core.clients.regist
[JIRA] [core] (JENKINS-33481) build parameters popup flashes and disappears
Title: Message Title Daniel Beck commented on JENKINS-33481 Re: build parameters popup flashes and disappears This looks pretty crazy. Not sure there's a good solution short of having a separate page for pending builds. With these many parameters, chances are screen space is limiting as well, so not sure how much getting rid of the flicker would help. Depending on why you need the information, one option could be to access the remote API for the queue to see the parameters. It may be weird to use, but should work. Something like: /queue/api/xml?tree=items[actions[parameters[*]],params,task[name]] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33546) Regression with build parameters in XML API
Title: Message Title Dominic Bishop created an issue Jenkins / JENKINS-33546 Regression with build parameters in XML API Issue Type: Bug Assignee: Unassigned Components: core Created: 15/Mar/16 11:35 AM Environment: Jenkins 1.652 Ubuntu 15.10 Priority: Major Reporter: Dominic Bishop The structure of runtime build parameters in the XML API for builds has changed in 1.652 Retrieving XML for a job using /job/JobName/api/xml?depth=2 In 1.651 the parameters are returned in the following structure: PARAM_NAME paramvalue In 1.652 (and 1.653) the parameters are returned in the following structure: PARAM_NAME paramvalue The part of the output has disappeared. I do not see any refer
[JIRA] [github-plugin] (JENKINS-33532) Changes on Github Feature Branches Trigger Jobs tracking Master Branch Changes
Title: Message Title Ebrahim Moshaya commented on JENKINS-33532 Re: Changes on Github Feature Branches Trigger Jobs tracking Master Branch Changes I've got polling ignoring changes from our jenkins-ci commits. However, when there's been a push on a feature branch, it triggers the build. The revision will be different as the last commit to master was a maven release and update to poms only by jenkinsci user. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33481) build parameters popup flashes and disappears
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-33481 Re: build parameters popup flashes and disappears May be the popup could have a "safe size" and some link, or something like that, to go to all parameters. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tap-plugin] (JENKINS-32729) TAP Extended Test Results page does not render properly
Title: Message Title
feng yu commented on JENKINS-32729
Re: TAP Extended Test Results page does not render properly
I find that if I use --cdns in yslow command:
phantomjs --cookies-file=cookies.txt ~/yslow.js -i grade --cdns "172.16.250.11,wpa.b.qq.com,combo.b.qq.com" --format tap "${url}"
Tap plugin will parse error:
Processing '/var/lib/jenkins/jobs/aircare_stress_testing/builds/41/tap-master-files/购物车列表页面.tap'
Parsing TAP test result [/var/lib/jenkins/jobs/aircare_stress_testing/builds/41/tap-master-files/购物车列表页面.tap].
org.tap4j.parser.ParserException: Error parsing TAP Stream: Error parsing YAML [ message: Using these CDN hostnames from your preferences: 172.16.250.11,wpa.b.qq.com,combo.b.qq.com
]: null; mapping values are not allowed here; in 'string', line 1, column 62:
... hostnames from your preferences: 172.16.250.11,wpa.b.qq.com,com ...
^
at org.tap4j.parser.Tap13Parser.parse(Tap13Parser.java:221)
at org.tap4j.parser.Tap13Parser.parseFile(Tap13Parser.java:187)
at org.tap4j.plugin.TapParser.parse(TapParser.java:153)
at org.tap4j.plugin.TapPublisher.loadResults(TapPublisher.java:329)
at org.tap4j.plugin.TapPublisher.perform(TapPublisher.java:251)
at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782)
at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723)
at hudson.model.Build$BuildExecution.post2(Build.java:185)
at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668)
at hudson.model.Run.execute(Run.java:1763)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:410)
Caused by: org.tap4j.parser.ParserException: Error parsing YAML [ message: Using these CDN hostnames from your preferences: 172.16.250.11,wpa.b.qq.com,combo.b.qq.com
]: null; mapping values are not allowed here; in 'string', line 1, column 62:
... hostnames from your preferences: 172.16.250.11,wpa.b.qq.com,com ...
^
at org.tap4j.parser.Tap13Parser.parseDiagnostics(Tap13Parser.java:537)
at org.tap4j.parser.Tap13Parser.parseLine(Tap13Parser.java:303)
at org.tap4j.parser.Tap13Parser.parse(Tap13Parser.java:216)
... 13 more
Caused by: mapping values are not allowed here
in 'string', line 1, column 62:
... hostnames from your preferences: 172.16.250.11,wpa.b.qq.com,com ...
^
at org.yaml.snakeyaml.scanner.ScannerImpl.fetchValue(ScannerImpl.java:866)
at org.yaml.snakeyaml.scanner.ScannerImpl.fetchMoreTokens(ScannerImpl.java:360)
at org.yaml.snakeyaml.scanner.ScannerImpl.checkToken(ScannerImpl.java:226)
at org.yaml.snakeyaml.parser.ParserImpl$ParseBlockMappingKey.produce(ParserImpl.java:558)
at org.yaml.snakeyaml.parser.ParserImpl.peekEvent(ParserImpl.java:158)
at org.yaml.snakeyaml.parser.ParserImpl.checkEvent(ParserImpl.java:143)
at org.yaml.snakeyaml.composer.Composer.composeMappingNode(Composer.java:230)
at org.yaml.snakeyaml.composer.Composer.composeNode(Composer.java:159)
at org.yaml.snakeyaml.composer.Composer.composeDocument(Composer.java:122)
at org.yaml.snakeyaml.composer.Composer.getSingleNode(Composer.java:105)
at org.yaml.snakeyaml.constructor.BaseConstructo
[JIRA] [core] (JENKINS-33546) Regression with build parameters in XML API
Title: Message Title Dominic Bishop updated an issue Jenkins / JENKINS-33546 Regression with build parameters in XML API Change By: Dominic Bishop Environment: Jenkins 1.652Ubuntu 15.10 java version "1.7.0_95"OpenJDK Runtime Environment (IcedTea 2.6.4) (7u95-2.6.4-0ubuntu0.15.10.1)OpenJDK 64-Bit Server VM (build 24.95-b01, mixed mode) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21383) Restart feature in update center is brittle
Title: Message Title Andy Wang updated an issue Jenkins / JENKINS-21383 Restart feature in update center is brittle Change By: Andy Wang Labels: plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [saml-plugin] (JENKINS-33427) Help with configuring redirect when user is not logged in via SSO (SAML)
Title: Message Title MICHAEL LUPO commented on JENKINS-33427 Re: Help with configuring redirect when user is not logged in via SSO (SAML) Peter Hayes Thank you for the advice. Your suggestion worked perfectly. Marking this as resolved. Regards, Mike Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [saml-plugin] (JENKINS-33427) Help with configuring redirect when user is not logged in via SSO (SAML)
Title: Message Title MICHAEL LUPO resolved as Fixed Jenkins / JENKINS-33427 Help with configuring redirect when user is not logged in via SSO (SAML) Change By: MICHAEL LUPO Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-33547) Create flag for deploying for builds with parameter
Title: Message Title Andrey Molochnikov created an issue Jenkins / JENKINS-33547 Create flag for deploying for builds with parameter Issue Type: New Feature Assignee: yossis Components: artifactory-plugin Created: 15/Mar/16 12:36 PM Priority: Minor Reporter: Andrey Molochnikov I would like to have ability to deploy or not artifacts by parameter of build start. actions: 1) select "Generic-Artifactory Integration checkbox 2) Configure deploy parameters 3) Select new flag "ask user deploy or not" by default disabled 4) Run build with flag "deploy artifacts to artifactory server" selected Add Comment
[JIRA] [envinject-plugin] (JENKINS-30042) EnvInject doesn't see GIT_COMMIT even after SCM phase
Title: Message Title
Christopher Zee commented on JENKINS-30042
Re: EnvInject doesn't see GIT_COMMIT even after SCM phase
In addition to the comment written by brendon wilder, you will need some additional code to ensure this works safely across concurrent builds if you are trying to access build environment variables (not to be confused with environment variables). As seen in this presentation on slide 8:
def buildMap = build.getBuildVariables() config.putAll(buildMap) def envVarsMap = build.parent.builds[0].properties.get("envVars") config.putAll(envVarsMap)
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-30042) EnvInject doesn't see GIT_COMMIT even after SCM phase
Title: Message Title
Christopher Zee edited a comment on JENKINS-30042
Re: EnvInject doesn't see GIT_COMMIT even after SCM phase
In addition to the comment written by [~rantingpenguin], you will need some additional code to ensure this works safely across concurrent builds if you are trying to access build environment variables (not to be confused with environment variables). As seen in this [presentation|https://www.cloudbees.com/jenkins/juc-2015/presentations/JUC-2015-USEast-Groovy-With-Jenkins-McCollum.pdf] on slide 8:def config = new HashMap()def thr = Thread.currentThread()def build = thr?.executabledef buildMap = build.getBuildVariables()config.putAll(buildMap)def envVarsMap = build.parent.builds[0].properties.get("envVars")config.putAll(envVarsMap) Now all build environment variables and environment variables are accessible in the config HashMap.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33474) Pipeline job hanging
Title: Message Title Maciej Gawinecki commented on JENKINS-33474 Re: Pipeline job hanging Martin Stolle Attached now. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33474) Pipeline job hanging
Title: Message Title Maciej Gawinecki updated an issue Jenkins / JENKINS-33474 Pipeline job hanging Change By: Maciej Gawinecki Attachment: dump-mgawinecki Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-33390) Environment variables created in the global properties are ignored at build time
Title: Message Title Benny Prange commented on JENKINS-33390 Re: Environment variables created in the global properties are ignored at build time I could not reproduce the bug by installing jenkins 1.653 and envinject-plugin 1.92.1. I will update the jenkins instance that is affected by this bug and see if it still occurs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33459) Polling schedule text timestamps ignore "H"
Title: Message Title David Kaelbling commented on JENKINS-33459 Re: Polling schedule text timestamps ignore "H" Poll SCM trigger with Multiple SCMs (all git repos, if that matters). Sorry, I should have mentioned that originally. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-28284) Images for Test Case trends is broken and generate exception
Title: Message Title Nick Vancauwenberghe commented on JENKINS-28284 Re: Images for Test Case trends is broken and generate exception Same exception as in Description. Jenkins: 1.619 Performance plugin 1.13 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [image-gallery-plugin] (JENKINS-33533) Image width value not saved for subsequent builds
Title: Message Title Maninder Singh updated an issue Jenkins / JENKINS-33533 Image width value not saved for subsequent builds Change By: Maninder Singh Summary: Image width value not saved for subsequent build builds Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-33434) no post build step to set status to 'success'
Title: Message Title Jae Gangemi commented on JENKINS-33434 Re: no post build step to set status to 'success' github api: 1.72.1 github plugin: 1.17.1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-keeper-plugin] (JENKINS-33548) Make this plugin runnable in a publisher step.
Title: Message Title Lior Goikhburg created an issue Jenkins / JENKINS-33548 Make this plugin runnable in a publisher step. Issue Type: Bug Assignee: bap Components: build-keeper-plugin Created: 15/Mar/16 1:46 PM Priority: Major Reporter: Lior Goikhburg Currently this plugin runs right after the builder steps. There is no way to tell not to keep the build, If the job fails on the publisher step. For example: I don't want to keep the build if it fails on Junit or Cobertura publishers. How do I configure that ? It would make this plugin a lot more flexible if we could run it as a publisher step, so it can be combined with other plugins such as "Flexible publish". Add Comment
[JIRA] [build-keeper-plugin] (JENKINS-33548) Make this plugin runnable in a publisher step.
Title: Message Title Lior Goikhburg updated an issue Jenkins / JENKINS-33548 Make this plugin runnable in a publisher step. Change By: Lior Goikhburg Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-keeper-plugin] (JENKINS-33298) How do I know that build was marked to be kept ?
Title: Message Title Lior Goikhburg updated an issue Jenkins / JENKINS-33298 How do I know that build was marked to be kept ? Change By: Lior Goikhburg Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33549) Expose Job name for the exception java.lang.IllegalStateException: cannot create a build with number XX since that (or higher) is already in use among [XX]
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-33549 Expose Job name for the exception java.lang.IllegalStateException: cannot create a build with number XX since that (or higher) is already in use among [XX] Issue Type: Bug Assignee: Félix Belzunce Arcos Components: core Created: 15/Mar/16 1:48 PM Priority: Trivial Reporter: Félix Belzunce Arcos If $JENKINS_HOME/jobs/*/nextBuildNumber was somehow reset to a lower value then the stacktrace below will be displayed. It doesn't say what job is affected, so it might be nice to capture this exception and expose the job name. 2016-03-10 13:03:58.785+ [id=4541756] SEVERE hudson.model.Executor#run: Unexpected executor deathjava.lang.IllegalStateException: cannot create a build with number 38 since that (or higher) is already in use among [45] at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361) at hudson.model.RunMap.put(RunMap.java:190) at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178) at hudson.model.AbstractProject.newBuild(AbstractProject.java:1010) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1209) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144) at hudson.model.Executor$1.call(Executor.java:335) at hudson.model.Executor$1.call(Executor.java:317) at hudson.model.Queue._withLock(Queue.java:1399) at hudson.model.Queue.withLock(Queue.java:1264) at hudson.model.Executor.run(Executor.java:317)
[JIRA] [subversion-plugin] (JENKINS-3276) Wrong username used for login to SVN
Title: Message Title Dorian Daumiller commented on JENKINS-3276 Re: Wrong username used for login to SVN Stefan Brausch: Thank you sir, your comment made me look on my server and find an old SVN command line credentials cache, which had led to inexplicable log entries on my SVN server about invalid credentials whenever somebody as much as changed an SVN URL. [Tue Mar 15 13:57:01.547853 2016] [authnz_sspi:error] [pid 123:tid 123] (OS 1326)The user name or password is incorrect. : [client 10.42.28.135:56622] user \\: authentication failure for "/svn/" After your comment on finding the user that starts Jenkins I made the discovery that, on Windows, there is an additional user "local SystemUser" whose AppData directory is not at c:\users\\AppData, but at c:\windows\system32\config\systemprofile\AppData. This was happening only on our Legacy Jenkins (which uses tremendously outdated versions of everything), but upgrading to Credentials Plugin V2.1 did not fix this (hat tip to stephenconnolly). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33549) Expose Job name for the exception java.lang.IllegalStateException: cannot create a build with number XX since that (or higher) is already in use among [XX]
Title: Message Title Félix Belzunce Arcos started work on JENKINS-33549 Change By: Félix Belzunce Arcos Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33549) Expose Job name for the exception java.lang.IllegalStateException: cannot create a build with number XX since that (or higher) is already in use among [XX]
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-33549 Expose Job name for the exception java.lang.IllegalStateException: cannot create a build with number XX since that (or higher) is already in use among [XX] Change By: Félix Belzunce Arcos Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33549) Expose Job name for the exception java.lang.IllegalStateException: cannot create a build with number XX since that (or higher) is already in use among [XX]
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-33549 Expose Job name for the exception java.lang.IllegalStateException: cannot create a build with number XX since that (or higher) is already in use among [XX] Change By: Félix Belzunce Arcos URL: https://github.com/jenkinsci/jenkins/pull/2125 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slack-plugin] (JENKINS-27652) Workflow support for Slack Notifications (Pre and Post build)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27652 Re: Workflow support for Slack Notifications (Pre and Post build) Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/e161fcfbecaccfc517bcf4c5a843a9c50c437046 Log: Merge pull request #364 from kmadel/ JENKINS-27652 JENKINS-27652 Workflow support for Slack Notifications Compare: https://github.com/jenkinsci/workflow-plugin/compare/82e7defa37c0...e161fcfbecac Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slack-plugin] (JENKINS-27652) Workflow support for Slack Notifications (Pre and Post build)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27652 Re: Workflow support for Slack Notifications (Pre and Post build) Code changed in jenkins User: Kurt Madel Path: COMPATIBILITY.md http://jenkins-ci.org/commit/workflow-plugin/46930e3c28fd5e52ca04b3ff8c97f1aaf1d640ec Log: JENKINS-27652 Workflow support for Slack Notifications (Pre and Post build) Slack supports Jenkins Pipeline as of version 2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [chroot-plugin] (JENKINS-33521) Use textbox for chroot name, and allow environment expansion
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33521 Re: Use textbox for chroot name, and allow environment expansion Code changed in jenkins User: Roman Mohr Path: src/main/java/org/jenkinsci/plugins/chroot/builders/ChrootBuilder.java src/main/resources/org/jenkinsci/plugins/chroot/builders/ChrootBuilder/config.jelly http://jenkins-ci.org/commit/chroot-plugin/8fb1bb9f9d2e453ddd73eac3cb8ca74bcbcc2611 Log: Merge pull request #6 from directhex/JENKINS-33521 Use env-expanded text box for chroot selection (JENKINS-33521) Compare: https://github.com/jenkinsci/chroot-plugin/compare/4e12294cfbd8...8fb1bb9f9d2e Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [chroot-plugin] (JENKINS-33519) Job execution fails if "Clear" enabled & chroot does not exist yet
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33519 Re: Job execution fails if "Clear" enabled & chroot does not exist yet Code changed in jenkins User: Jo Shields Path: src/main/java/org/jenkinsci/plugins/chroot/builders/ChrootBuilder.java http://jenkins-ci.org/commit/chroot-plugin/34819b89f921ef33478ab5306cb0d17836ec170d Log: Only try to Clear() environments that exist (JENKINS-33519) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [chroot-plugin] (JENKINS-33519) Job execution fails if "Clear" enabled & chroot does not exist yet
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33519 Re: Job execution fails if "Clear" enabled & chroot does not exist yet Code changed in jenkins User: Roman Mohr Path: src/main/java/org/jenkinsci/plugins/chroot/builders/ChrootBuilder.java http://jenkins-ci.org/commit/chroot-plugin/4e12294cfbd8f2cf85dbaa55f8e7e30ac0541166 Log: Merge pull request #5 from directhex/JENKINS-33519 Only try to Clear() environments that exist (JENKINS-33519) Compare: https://github.com/jenkinsci/chroot-plugin/compare/2644c785f490...4e12294cfbd8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-32500) Failed to parse the build number in the permalink
Title: Message Title
Jonathan Grant commented on JENKINS-32500
Re: Failed to parse the build number in the permalink
Hi Daniel
That was the whole log, nothing before (except Jenkins starting), nothing after.
There is enough information to improve the code that displays "Failed to parse the build number in the permalink" but doesn't output any useful info to help me fix the issue in the local files. Jenkins is running on a Windows 7 machine, it could be the lastSuccessfulBuild file, sometimes that seems to be a genuine file, and sometimes it is a text file containing a build number. It would be more straightforward if Jenkins never used symbolic links.
PeepholePermalink.java:106
Can this be improved to output the exact path and file that was being searched?
catch (NumberFormatException e) { LOGGER.log(Level.WARNING, "Failed to parse the build number in the permalink cache:" + f, e); // if we fail to read the cache, fall back to the re-computation }
catch (IOException e) { // this happens when the symlink doesn't exist // (and it cannot be distinguished from the case when the actual I/O error happened }
Can the LOGGER be updated to output the path of the file please? Thank you, Jon
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-status-plugin] (JENKINS-31050) Slave goes offline during the build
Title: Message Title Roberto Flores commented on JENKINS-31050 Re: Slave goes offline during the build Hi Fernando, it seems I'm having this same problem. How did you get around it? Would really appreciate your help on this Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [branch-api-plugin] (JENKINS-32670) No branch properties for multibranch pipelines
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-32670 No branch properties for multibranch pipelines Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-28652) JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-28652 JaCoCo 0.7.5 incorrectly shows 0% coverage in Jenkins summary Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [branch-api-plugin] (JENKINS-32670) No branch properties for multibranch pipelines
Title: Message Title Jesse Glick started work on JENKINS-32670 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-33550) Active Directory Plugin adding user name as Bind DN
Title: Message Title Michael Miller created an issue Jenkins / JENKINS-33550 Active Directory Plugin adding user name as Bind DN Issue Type: Bug Assignee: Félix Belzunce Arcos Attachments: jenkins.gif Components: active-directory-plugin Created: 15/Mar/16 2:45 PM Environment: Jenkins on Windows Labels: user-experience plugins Priority: Minor Reporter: Michael Miller The Active Directory plugin is adding a admin username as the Bind DN when the user add a new user in Global Security. The following tag gets added to the config file: [USER_NT_USERName] This prevents anyone from logging into Jenkins. By removing that entry from the config, users
[JIRA] [active-directory-plugin] (JENKINS-33550) Active Directory Plugin adding user name as Bind DN
Title: Message Title Michael Miller updated an issue Jenkins / JENKINS-33550 Active Directory Plugin adding user name as Bind DN Change By: Michael Miller Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33296) Initial plugin setup needs to consider implied dependencies
Title: Message Title Keith Zantow started work on JENKINS-33296 Change By: Keith Zantow Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33308) Plugin Manager needs to consider implied plugin dependencies
Title: Message Title Keith Zantow started work on JENKINS-33308 Change By: Keith Zantow Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-33550) Active Directory Plugin adding user name as Bind DN
Title: Message Title Félix Belzunce Arcos commented on JENKINS-33550 Re: Active Directory Plugin adding user name as Bind DN I don't understand this issue. Can you explain what needs to be done to re-produce it, please? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33296) Initial plugin setup needs to consider implied dependencies
Title: Message Title Keith Zantow updated an issue Jenkins / JENKINS-33296 Initial plugin setup needs to consider implied dependencies Change By: Keith Zantow Implied dependencies are not considered at all on the setup dialog. If we think they're so important that we don't allow disabling the plugins when an implied dependent plugin is enabled, we should consider them important enough to install them when such a plugin is installed, no? Otherwise this could result in a giant mess of broken plugins.Assigning to Tom as he wrote the plugin wizard. CC [~kzantow] PR: https://github.com/jenkinsci/jenkins/pull/2122 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [branch-api-plugin] (JENKINS-32670) Improperly filtered branch properties for multibranch pipelines
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-32670 Improperly filtered branch properties for multibranch pipelines Worse than that: when the source is first added, rather than reloading the configuration form, all branch properties are displayed (including ones which multibranch Pipeline does not intend to support), because it == null. Change By: Jesse Glick Summary: No Improperly filtered branch properties for multibranch pipelines Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-33551) Error updating JIRA issues
Title: Message Title Julien Carsique created an issue Jenkins / JENKINS-33551 Error updating JIRA issues Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 15/Mar/16 3:03 PM Environment: Jenkins 1.642.2 JIRA plugin 2.2 JIRA 6.3.14 Priority: Major Reporter: Julien Carsique An NPE is raised while updating JIRA issues. The comment is wrote on JIRA but the NPE makes the plugin continuously write the same comment and remember the issues for the next build. Error updating JIRA issues. Saving issues for next build. java.lang.NullPointerException at hudson.plugins.jira.Updater.submitComments(Updater.java:177) at hudson.plugins.jira.Updater.perform(Updater.java:128) at hudson.plugins.jira.JiraIssueUpdater.perform(JiraIssueUpdater.java:64) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1047)
[JIRA] [jira-plugin] (JENKINS-33551) NPE Error updating JIRA issues
Title: Message Title Julien Carsique updated an issue Jenkins / JENKINS-33551 NPE Error updating JIRA issues Change By: Julien Carsique Summary: NPE Error updating JIRA issues Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33296) Initial plugin setup needs to consider implied dependencies
Title: Message Title Keith Zantow updated an issue Jenkins / JENKINS-33296 Initial plugin setup needs to consider implied dependencies Change By: Keith Zantow Implied dependencies are not considered at all on the setup dialog. If we think they're so important that we don't allow disabling the plugins when an implied dependent plugin is enabled, we should consider them important enough to install them when such a plugin is installed, no? Otherwise this could result in a giant mess of broken plugins.Assigning to Tom as he wrote the plugin wizard. CC [~kzantow] PR: https://github.com/jenkinsci/jenkins/pull/2122 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-33552) Settings validation fails on JiraRestService.getMyPermissions()
Title: Message Title
Julien Carsique created an issue
Jenkins / JENKINS-33552
Settings validation fails on JiraRestService.getMyPermissions()
Issue Type:
Bug
Assignee:
Unassigned
Components:
jira-plugin
Created:
15/Mar/16 3:12 PM
Environment:
Jenkins 1.642.2 JIRA plugin 2.2 JIRA 6.3.14
Priority:
Minor
Reporter:
Julien Carsique
The new validation process introduced in version 2.1 by commit https://github.com/jenkinsci/jira-plugin/commit/1912505a9f2bc723f3910d5a4ab4da89543a721d seems not compliant with JIRA 6.3.14.
Failed to login to JIRA at https://jira.nuxeo.com/
RestClientException{statusCode=Optional.absent(), errorCollections=[]}
at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.claim(DelegatingPromise.java:47)
at hudson.plugins.jira.JiraRestService.getMyPermissions(JiraRestService.java:369)
at hudson.plugins.jira.JiraSession.getMyPermissions(JiraSession.java:385)
at hudson.plugins.jira.JiraSite$DescriptorImpl.doValidate(JiraSite.java:735)
Caused by: RestClientException{statusCode=Optional.absent(), errorCollections=[]}
at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$3.apply(AbstractAsynchronousRestClient.java:188)
at com.atlassian.ji
[JIRA] [core] (JENKINS-33308) Plugin Manager needs to consider implied plugin dependencies
Title: Message Title Keith Zantow assigned an issue to Keith Zantow Jenkins / JENKINS-33308 Plugin Manager needs to consider implied plugin dependencies Change By: Keith Zantow Assignee: Keith Zantow Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19565) dropdownDescriptorSelector is loosing the context of `it`
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-19565 dropdownDescriptorSelector is loosing the context of `it` Change By: Jesse Glick Labels: credentials lts-candidate stapler Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [branch-api-plugin] (JENKINS-32670) Improperly filtered branch properties for multibranch pipelines
Title: Message Title Jesse Glick commented on JENKINS-32670 Re: Improperly filtered branch properties for multibranch pipelines …because of JENKINS-19565 , as used here. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-33545) The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0.
Title: Message Title Davy Courvoisier updated an issue Jenkins / JENKINS-33545 The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0. Change By: Davy Courvoisier Upgrading TFS Plugin from version 4.0.0 to 4.1.0 make system unusable.Tried creating a new job from scratch and same error occurs. Workaround is to revert to V4.0.0. This is reproduced on 2 different linux jenkins instances. V 4.1.0 does not have the issue on a Windows installation. The following error occurs when the TFS plugin tries to connect to TFS(poll, checkout):FATAL: The SOAP endpoint http://tfsurl:8080/tfs/collection/Services/v1.0/Registration.asmx could not be contacted. HTTP status: 302com.microsoft.tfs.core.exceptions.TECoreException: The SOAP endpoint http://tfsurl:8080/tfs/collection/Services/v1.0/Registration.asmx could not be contacted. HTTP status: 302 at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:105) at com.microsoft.tfs.core.exceptions.mappers.RegistrationExceptionMapper.map(RegistrationExceptionMapper.java:23) at com.microsoft.tfs.core.clients.registration.RegistrationData.newFromServer(RegistrationData.java:70) at com.microsoft.tfs.core.clients.registration.RegistrationClient.getRegistrationData(RegistrationClient.java:645) at com.microsoft.tfs.core.clients.registration.RegistrationClient.getRegistrationEntry(RegistrationClient.java:188) at com.microsoft.tfs.core.clients.registration.RegistrationClient.getRegistrationEntry(RegistrationClient.java:167) at com.microsoft.tfs.core.clients.webservices.IdentityManagementService.(IdentityManagementService.java:65) at hudson.plugins.tfs.model.Server.createIdentityManagementService(Server.java:213) at hudson.plugins.tfs.model.Project.getOrCreateUserLookup(Project.java:112) at hudson.plugins.tfs.model.Project.getVCCHistory(Project.java:82) at hudson.plugins.tfs.model.Project.getLatestUncloakedChangeset(Project.java:179) at hudson.plugins.tfs.TeamFoundationServerScm.compareRemoteRevisionWith(TeamFoundationServerScm.java:555) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1450) at hudson.model.AbstractProject.poll(AbstractProject.java:1353) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:510) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:539) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Caused by: com.microsoft.tfs.core.ws.runtime.exceptions.EndpointNotFoundException: The SOAP endpoint http://tfsurl:8080/tfs/collection/Services/v1.0/Registration.asmx could not be contacted. HTTP status: 302 at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineHeadersForFederatedAuthURL(SOAPService.java:1198) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:716) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequest(SOAPService.java:475) a
[JIRA] [shiningpanda-plugin] (JENKINS-33553) tox builder broken
Title: Message Title Michael Howitz created an issue Jenkins / JENKINS-33553 tox builder broken Issue Type: Bug Assignee: Unassigned Components: shiningpanda-plugin Created: 15/Mar/16 3:31 PM Environment: ShiningPanda Plugin 0.22 Jenkins ver. 1.650 Labels: plugin exception regression configuration Priority: Major Reporter: Michael Howitz It tries to use Python 2.4 to create the virtual environment but the used virtualenv.py requires at least Python 2.6 [py27] $ /srv/jenkins/deployment/work/python/bin/python2.4 /srv/jenkins/shiningpanda/jobs/0c9d10f8/virtualenv.py /srv/jenkins/shiningpanda/jobs/0c9d10f8/tools ERROR: None ERROR: this script requires Python 2.6 or greater. Build step 'Tox Builder' marked build as failure Finished: FAILURE
[JIRA] [job-dsl-plugin] (JENKINS-33554) Warning threshold defaults generated by the Job DSL Plugin don't match the GUI defaults
Title: Message Title Dmitry Polyanitsa created an issue Jenkins / JENKINS-33554 Warning threshold defaults generated by the Job DSL Plugin don't match the GUI defaults Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 15/Mar/16 3:32 PM Environment: jenkins 1.625.3 LTS job-dsl plugin 1.42 warnings plugin 4.50 Priority: Minor Reporter: Dmitry Polyanitsa The default values for the thresholds are empty strings in the GUI, while in the Job DSL plugin they are zeroes. An empty threshold means it is not enforced, while a 0 one means there should not be any failures of this kind. Effectively, in the GUI the default is "enforce nothing, any number of errors is fine", while in the default DSL-generated job it's "strictly enforce everything, there should be no errors at all". While this bug is actually enforcing good practices, it is still a bug Faulty job example: Unable to find source-code formatter for language: groovy. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
[JIRA] [job-dsl-plugin] (JENKINS-33554) Warning threshold defaults generated by the Job DSL Plugin don't match the GUI defaults
Title: Message Title
Dmitry Polyanitsa updated an issue
Jenkins / JENKINS-33554
Warning threshold defaults generated by the Job DSL Plugin don't match the GUI defaults
Change By:
Dmitry Polyanitsa
The default values for the thresholds are empty strings in the GUI, while in the Job DSL plugin they are zeroes. An empty threshold means it is not enforced, while a 0 one means there should not be any failures of this kind.Effectively, in the GUI the default is "enforce nothing, any number of errors is fine", while in the default DSL-generated job it's "strictly enforce everything, there should be no errors at all".While this bug is actually enforcing good practices, it is still a bug :)Faulty job example:{code: groovy java }job('threshold-defaults-bug') { publishers {archiveXUnit { jUnit {pattern('test-results.xml') }} }}{code}You can run it here: http://job-dsl.herokuapp.com/. Note that all the generated thresholds have 0s, not empty strings.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33554) Warning threshold defaults generated by the Job DSL Plugin don't match the GUI defaults
Title: Message Title Dmitry Polyanitsa updated an issue Jenkins / JENKINS-33554 Warning threshold defaults generated by the Job DSL Plugin don't match the GUI defaults Change By: Dmitry Polyanitsa Environment: jenkins 1.625.3 LTSjob-dsl plugin 1.42 warnings xunit plugin 4 1 . 50 93 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-33554) Warning threshold defaults generated by the Job DSL Plugin don't match the GUI defaults
Title: Message Title
Dmitry Polyanitsa updated an issue
Jenkins / JENKINS-33554
Warning threshold defaults generated by the Job DSL Plugin don't match the GUI defaults
Change By:
Dmitry Polyanitsa
The default values for the thresholds are empty strings in the GUI, while in the Job DSL plugin they are zeroes. An empty threshold means it is not enforced, while a 0 one means there should not be any failures of this kind.Effectively, in the GUI the default is "enforce nothing, any number of errors is fine", while in the default DSL-generated job it's "strictly enforce everything, there should be no errors at all".While this bug is actually enforcing promoting good practices, it is still a bug :)Faulty job example:{code:java}job('threshold-defaults-bug') { publishers {archiveXUnit { jUnit {pattern('test-results.xml') }} }}{code}You can run it here: http://job-dsl.herokuapp.com/. Note that all the generated thresholds have 0s, not empty strings.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [tfs-plugin] (JENKINS-33545) The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0.
Title: Message Title Davy Courvoisier updated an issue Jenkins / JENKINS-33545 The SOAP endpoint could not be contacted (HTTP status: 302), new in 4.1.0. Change By: Davy Courvoisier Upgrading TFS Plugin from version 4.0.0 to 4.1.0 make system unusable.Tried creating a new job from scratch and same error occurs. Workaround is to revert to V4.0.0. This is reproduced on 2 different linux jenkins instances , with Windows clients .V 4.1.0 does not have the issue on a newly installed Windows installation jenkins 1 . 642.2. The following error occurs when the TFS plugin tries to connect to TFS(poll, checkout):FATAL: The SOAP endpoint http://tfsurl:8080/tfs/collection/Services/v1.0/Registration.asmx could not be contacted. HTTP status: 302com.microsoft.tfs.core.exceptions.TECoreException: The SOAP endpoint http://tfsurl:8080/tfs/collection/Services/v1.0/Registration.asmx could not be contacted. HTTP status: 302 at com.microsoft.tfs.core.exceptions.mappers.TECoreExceptionMapper.map(TECoreExceptionMapper.java:105) at com.microsoft.tfs.core.exceptions.mappers.RegistrationExceptionMapper.map(RegistrationExceptionMapper.java:23) at com.microsoft.tfs.core.clients.registration.RegistrationData.newFromServer(RegistrationData.java:70) at com.microsoft.tfs.core.clients.registration.RegistrationClient.getRegistrationData(RegistrationClient.java:645) at com.microsoft.tfs.core.clients.registration.RegistrationClient.getRegistrationEntry(RegistrationClient.java:188) at com.microsoft.tfs.core.clients.registration.RegistrationClient.getRegistrationEntry(RegistrationClient.java:167) at com.microsoft.tfs.core.clients.webservices.IdentityManagementService.(IdentityManagementService.java:65) at hudson.plugins.tfs.model.Server.createIdentityManagementService(Server.java:213) at hudson.plugins.tfs.model.Project.getOrCreateUserLookup(Project.java:112) at hudson.plugins.tfs.model.Project.getVCCHistory(Project.java:82) at hudson.plugins.tfs.model.Project.getLatestUncloakedChangeset(Project.java:179) at hudson.plugins.tfs.TeamFoundationServerScm.compareRemoteRevisionWith(TeamFoundationServerScm.java:555) at hudson.scm.SCM.poll(SCM.java:397) at hudson.model.AbstractProject._poll(AbstractProject.java:1450) at hudson.model.AbstractProject.poll(AbstractProject.java:1353) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:510) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:539) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)Caused by: com.microsoft.tfs.core.ws.runtime.exceptions.EndpointNotFoundException: The SOAP endpoint http://tfsurl:8080/tfs/collection/Services/v1.0/Registration.asmx could not be contacted. HTTP status: 302 at com.microsoft.tfs.core.ws.runtime.client.SOAPService.examineHeadersForFederatedAuthURL(SOAPService.java:1198) at com.microsoft.tfs.core.ws.runtime.client.SOAPService.executeSOAPRequestInternal(SOAPService.java:716) at com.microsoft.tfs.core.ws.runtime.clien
[JIRA] [core] (JENKINS-33555) Provide option to disable master build executors while starting service
Title: Message Title Suresh Kumar created an issue Jenkins / JENKINS-33555 Provide option to disable master build executors while starting service Issue Type: Improvement Assignee: Unassigned Components: core Created: 15/Mar/16 3:42 PM Labels: jenkins Priority: Minor Reporter: Suresh Kumar Provide option to disable Build executors for Jenkins master when starting service as input and in configure system it should not be editable when the Jenkins service started with this option. If we able to do this we can achieve multi-tenant feature, so that we can block build executions on the Jenkins Master considering load & security issues I have configured the Jenkins like below at different ports(8080,8081,8082) and different JENKINS_HOME /etc/alternatives/java -Djava.awt.headless=true -DJENKINS_HOME=/var/lib/jenkins8081 -jar /usr/lib/jenkins/jenkins.war --httpPort=8081 Configured with Apache Server Reverse Proxy to map each Jenkins instance with each DNS entry.
[JIRA] [active-directory-plugin] (JENKINS-33550) Active Directory Plugin adding user name as Bind DN
Title: Message Title Michael Miller commented on JENKINS-33550 Re: Active Directory Plugin adding user name as Bind DN In our environment, we can reproduce the issue by having the Admin user log into Jenkins, then add a user in Global Security. By doing that, the config gets updated with: [USER_NT_USERName] where [USER_NT_USERName] is the NT login name of the Admin. Immediately, no one can log into Jenkins and we receive the error message in the attached image. By removing the entry, [USER_NT_USERName] , users are able to log into Jenkins Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-33550) Active Directory Plugin adding user name as Bind DN
Title: Message Title Michael Miller commented on JENKINS-33550 Re: Active Directory Plugin adding user name as Bind DN FYI, we are using Project-based Matrix Authorization Strategy Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-changelog-plugin] (JENKINS-33301) git-changelog: specifying references
Title: Message Title Jirong Hu commented on JENKINS-33301 Re: git-changelog: specifying references GIT_PREVIOUS_SUCCESSFUL_COMMIT is not available, I only see these in my Windows environment: GIT_BRANCH=origin/master GIT_COMMIT=a781fbc49bda7083ebc05e28cee60de4e4258b17 GIT_PREVIOUS_COMMIT=a781fbc49bda7083ebc05e28cee60de4e4258b17 GIT_URL=http://github.ooop.com/DevOps/Sample.git And I am having this issue: http://stackoverflow.com/questions/36016043/how-to-set-up-git-changelog-in-jenkins Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-changelog-plugin] (JENKINS-33301) git-changelog: specifying references
Title: Message Title Tomas Bjerre commented on JENKINS-33301 Re: git-changelog: specifying references I guess you are refering to the printout from "GIt Publisher". Try to use the variables in "Git Changelog" task. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33556) exception when loading main page prior to authenticating
Title: Message Title George Sakhnovsky created an issue Jenkins / JENKINS-33556 exception when loading main page prior to authenticating Issue Type: Bug Assignee: Unassigned Components: core Created: 15/Mar/16 4:15 PM Environment: awt.toolkit sun.awt.X11.XToolkit com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 51.0 java.endorsed.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65.x86_64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65.x86_64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.7.0_65-mockbuild_2014_07_23_19_20-b00 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.7 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.7.0_65 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.7 java.vm.vendor Oracle Corporation java.vm.version 24.65-b04 JENKINS_HOME /var/lib/jenkins jna.loaded true jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/local/firefox:/usr/local/lib:/usr/lib64/mysql jnidispatch.path /tmp/jna--1712433994/jna5490154213502416552.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.10.42-52.145.amzn1.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65.x86_64/jre/lib/resources.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65.x86_64/jre/lib/rt.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65.x86_64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.65.x
[JIRA] [envinject-plugin] (JENKINS-33390) Environment variables created in the global properties are ignored at build time
Title: Message Title Benny Prange commented on JENKINS-33390 Re: Environment variables created in the global properties are ignored at build time I've found a way to reproduce this behaviour. This was done using 1.653 and 1.92.1. java -jar jenkins.war In the global options, create the environment value FOO=GLOBAL create a job, shell build step: echo $FOO execute it, console output shows: + echo GLOBAL GLOBAL stop jenkins on the commandline: export FOO=CONSOLE java -jar jenkins.war execute the same job, console output + echo CONSOLE CONSOLE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] [branch-api-plugin] (JENKINS-25240) DeadBranchStrategy should avoid deleting projects with active jobs
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-25240 DeadBranchStrategy should avoid deleting projects with active jobs Change By: Jesse Glick Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [branch-api-plugin] (JENKINS-25240) DeadBranchStrategy should avoid deleting projects with active jobs
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-25240 DeadBranchStrategy should avoid deleting projects with active jobs Change By: Jesse Glick Assignee: Matthew Moore Jesse Glick Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves-plugin] (JENKINS-25858) java.io.IOException: Unexpected termination of the channel
Title: Message Title David Carlton commented on JENKINS-25858 Re: java.io.IOException: Unexpected termination of the channel This bug is tagged as ssh-slaves-plugin, but now that I understand the EC2 plugin, I realize that it replaces the SSH Slaves Plugin; I don't know for sure which plugin the original poster was using, but it seems like the rest of us are using EC2. I've been experimenting for the last week with setting "Connect by SSH Process" (under the advanced options) to true, and I haven't had any problems since I've done that, so I would recommend that to other people who are running into this symptom with the EC2 option. (It was added for exactly this reason, see https://github.com/jenkinsci/ec2-plugin/pull/139 ) There's still presumably a collection of potential underlying non-Jenkins issues - maybe kernel problems, maybe security groups, who knows, probably different for different installations - but it seems to me like the external ssh program is noticeably better at dealing with temporary network glitches than Trilead is. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33556) exception when loading main page prior to authenticating
Title: Message Title Chad Burggraf updated an issue Jenkins / JENKINS-33556 exception when loading main page prior to authenticating Change By: Chad Burggraf Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-33467 CauseAction.causes can become huge Change By: Steven Christou Labels: lts-candidate performance Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-33467) CauseAction.causes can become huge
Title: Message Title Steven Christou commented on JENKINS-33467 Re: CauseAction.causes can become huge I marked this as an lts-candidate, as this can cause memory issues. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
