[JIRA] [core] (JENKINS-19939) Discard Old Builds I/O Performance Issue
Title: Message Title Tomasz Śniatowski commented on JENKINS-19939 Re: Discard Old Builds I/O Performance Issue Hi, thanks a lot for replying. Re 1: I personally do not find it a critical problem that "something" happens after a build status is determined, but before a next build can happen. It might be a bit confusing, but not the largest UI issue here from my POV. Re 2: This is my main gripe. If something bad happens and discarding takes a long time, there is no trace left anywhere. This makes it hard to analyse or report the problem. Re 3: I have no hard data (because without any logs it's difficult for me) but I do get a feeling that the discarding process is far more IO-heavy than it should be. It might worthwhile to mention something in the config section, but waiting for more data is probably fine too. Yesterday we had a transient IO performance issue in our Jenkins master disk hardware, and a job config change that ended up discarding some 20k builds (almost empty: no artifacts; 10 files and <40KB per build directory). This took over an hour, and I could see it deleting a couple build directories per second. Now whether this was solely caused by the hardware, or if discarding is otherwise sub-optimal (like syncing too much), is something I don't know – but shell IO at the time did not feel as bad. I have to admit though that without better data (like the actual time spent discarding, the time it took to just rm equivalent files, whether there was anything else going on, reproducibility, etc.) it's hard to tell. That's why I primarily just would like to have the logging. 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.
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException "Request has expired"
Title: Message Title
James Judd edited a comment on JENKINS-26854
Re: EC2 slave launch stops working after a while with AmazonServiceException "Request has expired"
Thanks for the info Martin.I spent some more time looking into this tonight and I think I found the cause. Even better, I think the fix is quite simple. At the moment, in EC2Cloud: we create an AmazonEC2Client like so{code:Java}AmazonEC2 client = new AmazonEC2Client(credentialsProvider.getCredentials(), config);{code}According to the [Amazon SDK source|https://github.com/aws/aws-sdk-java/blob/84adaca80ee2b974f76816f5d4d9be90a5aa8543/aws-java-sdk-ec2/src/main/java/com/amazonaws/services/ec2/AmazonEC2Client.java#L134-138] this creates a [StaticCredentialsProvider|https://github.com/puppetlabs/aws-sdk-for-java/blob/master/src/main/java/com/amazonaws/internal/StaticCredentialsProvider.java] using the given credentials. From what I can tell, StaticCredentialsProvider never refreshes its credentials, leading to expiration.Instead, you can create an [AmazonEC2Client with a credentials provider directly|https://github.com/aws/aws-sdk-java/blob/84adaca80ee2b974f76816f5d4d9be90a5aa8543/aws-java-sdk-ec2/src/main/java/com/amazonaws/services/ec2/AmazonEC2Client.java#L172-174]. This should, as far as I can tell, refresh the credentials as needed.{code:Java}AmazonEC2 client = new AmazonEC2Client(credentialsProvider, config);{code}This is further supported by [this amazon documentation|http://docs.aws.amazon.com/AWSSdkDocsJava/latest/DeveloperGuide/java-dg-roles.html], which states{quote}*Important*The automatic credentials refresh happens only when you use the default client constructor, which creates its own InstanceProfileCredentialsProvider as part of the default provider chain, _ or _or when you pass an InstanceProfileCredentialsProvider instance directly to the client constructor_. If you use another method to obtain or pass instance profile credentials, you are responsible for checking for and refreshing expired credentials.{quote} [emphasis mine]I just uploaded a version of the plugin with this change to our Jenkins server. I'll let it run and report back tomorrow if I see any errors. If it works, I'll create a pull request.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [ec2-plugin] (JENKINS-26854) EC2 slave launch stops working after a while with AmazonServiceException "Request has expired"
Title: Message Title James Judd commented on JENKINS-26854 Re: EC2 slave launch stops working after a while with AmazonServiceException "Request has expired" Thanks for the info Martin. I spent some more time looking into this tonight and I think I found the cause. Even better, I think the fix is quite simple. At the moment, in EC2Cloud: we create an AmazonEC2Client like so AmazonEC2 client = new AmazonEC2Client(credentialsProvider.getCredentials(), config); According to the Amazon SDK source this creates a StaticCredentialsProvider using the given credentials. From what I can tell, StaticCredentialsProvider never refreshes its credentials, leading to expiration. Instead, you can create an AmazonEC2Client with a credentials provider directly. This should, as far as I can tell, refresh the credentials as needed. AmazonEC2 client = new AmazonEC2Client(credentialsProvider, config); This is further supported by this amazon documentation, which states Important The automatic credentials refresh happens only when you use the default client constructor, which creates its own InstanceProfileCredentialsProvider as part of the default provider chain,_ or when you pass an InstanceProfileCredentialsProvider instance directly to the client constructor_. If you use another method to obtain or pass instance profile credentials, you are responsible for checking for and refreshing expired credentials. [emphasis mine] I just uploaded a version of the plugin with this change to our Jenkins server. I'll let it run and report back tomorrow if I see any errors. If it works, I'll create a pull request. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-28544) Update Center and Jobs Permission Denied
Title: Message Title Alex Shafer updated an issue Jenkins / JENKINS-28544 Update Center and Jobs Permission Denied Change By: Alex Shafer Summary: Update Center and Jobs Permission Denied Component/s: core Labels: core exception jenkins plugins job plugin update 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] [update-sites-manager-plugin] (JENKINS-28544) Update Center Permission Denied
Title: Message Title Alex Shafer commented on JENKINS-28544 Re: Update Center Permission Denied Other directories also needed to be fixed to inorder for jobs to work correctly 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] [update-sites-manager-plugin] (JENKINS-28544) Update Center Permission Denied
Title: Message Title
Alex Shafer updated an issue
Jenkins / JENKINS-28544
Update Center Permission Denied
Change By:
Alex Shafer
When attempting to install plugins using the Update Center, plugins can not be written to /var/lib/jenkins/plugins due to invalid permissions. { { quote} hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/plugins/ssh/2.4/ssh.hpi (redirected to: http://ftp-nyc.osuosl.org/pub/jenkins/plugins/ssh/2.4/ssh.hpi) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:797) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1148) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1309) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:744)Caused by: java.io.FileNotFoundException: /var/lib/jenkins/plugins/ssh.jpi.tmp (Permission denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:206) at java.io.FileOutputStream.(FileOutputStream.java:156) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:763) ... 7 more {quote } } { { quote} ***@*** /var/lib/jenkins $ ls -altotal 80drwxr-xr-x 11 jenkins jenkins4096 May 21 19:27 .drwxr-xr-x 48 root root 4096 May 2 18:23 ..-rw-r--r-- 1 systemd-timesync sambashare0 Apr 10 19:04 atomic3320745316088279947.tmp-rw-r--r-- 1 jenkins jenkins1715 May 21 19:15 config.xml-rw-r--r-- 1 jenkins jenkins 0 May 21 19:10 Download metadata.log-rw-r--r-- 1 systemd-timesync sambashare0 Apr 11 04:16 Fingerprint cleanup.log-rw-r--r-- 1 jenkins jenkins 160 May 21 19:27 hudson.model.UpdateCenter.xml-rw--- 1 systemd-timesync sambashare 1675 Apr 10 19:09 identity.keydrwxr-xr-x 3 jenkins jenkins4096 May 21 19:09 .java-rw-r--r-- 1 jenkins jenkins 138 May 21 19:14 jenkins.model.DownloadSettings.xml-rw-r--r-- 1 jenkins jenkins 169 May 21 19:14 jenkins.security.QueueItemAuthenticatorConfiguration.xmldrwxr-xr-x 2 jenkins jenkins4096 May 21 19:13 jenkins.security.RekeySecretAdminMonitordrwxr-xr-x 2 systemd-timesync sambashare 4096 Apr 10 18:56 jobs-rw-r--r-- 1 jenkins jenkins 907 May 21 19:10 nodeMonitors.xmldrwxr-xr-x 2 jenkins jenkins4096 May 21 19:09 nodes-rw-r--r-- 1 systemd-timesync sambashare 51 Apr 11 15:56 .ownerdrwxr-xr-x 2 systemd-timesync sambashare 4096 Apr 10 18:56 plugins-rw-r--r-- 1 systemd-timesync sambashare 46 Apr 11 16:18 queue.xml.bak-rw-r--r-- 1 systemd-timesync sambashare 64 Apr 10 18:56 secret.keydrwxr-xr-x 4 jenkins jenkins4096 May 21 19:15 secretsdrwxr-xr-x 2 jenkins jenkins4096 May 21 19:28 updatesdrwxr-xr-x 2 systemd-timesync sambashare 4096 Apr 10 19:09 userContentdrwxr-xr-x 3 jenkins jenkins4096 May 21 19:15 users {quote } } Can be fixed by issuing:{ { quote} sudo chown jenkins pluginssudo chown jenkins userContentsudo chgrp jenk
[JIRA] [update-sites-manager-plugin] (JENKINS-28544) Update Center Permission Denied
Title: Message Title
Alex Shafer updated an issue
Jenkins / JENKINS-28544
Update Center Permission Denied
Change By:
Alex Shafer
When attempting to install plugins using the Update Center, plugins can not be written to /var/lib/jenkins/plugins due to invalid permissions. {{ hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/plugins/ssh/2.4/ssh.hpi (redirected to: http://ftp-nyc.osuosl.org/pub/jenkins/plugins/ssh/2.4/ssh.hpi) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:797) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1148) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1309) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:744)Caused by: java.io.FileNotFoundException: /var/lib/jenkins/plugins/ssh.jpi.tmp (Permission denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:206) at java.io.FileOutputStream.(FileOutputStream.java:156) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:763) ... 7 more }} {{***@*** /var/lib/jenkins $ ls -altotal 80drwxr-xr-x 11 jenkins jenkins4096 May 21 19:27 .drwxr-xr-x 48 root root 4096 May 2 18:23 ..-rw-r--r-- 1 systemd-timesync sambashare0 Apr 10 19:04 atomic3320745316088279947.tmp-rw-r--r-- 1 jenkins jenkins1715 May 21 19:15 config.xml-rw-r--r-- 1 jenkins jenkins 0 May 21 19:10 Download metadata.log-rw-r--r-- 1 systemd-timesync sambashare0 Apr 11 04:16 Fingerprint cleanup.log-rw-r--r-- 1 jenkins jenkins 160 May 21 19:27 hudson.model.UpdateCenter.xml-rw--- 1 systemd-timesync sambashare 1675 Apr 10 19:09 identity.keydrwxr-xr-x 3 jenkins jenkins4096 May 21 19:09 .java-rw-r--r-- 1 jenkins jenkins 138 May 21 19:14 jenkins.model.DownloadSettings.xml-rw-r--r-- 1 jenkins jenkins 169 May 21 19:14 jenkins.security.QueueItemAuthenticatorConfiguration.xmldrwxr-xr-x 2 jenkins jenkins4096 May 21 19:13 jenkins.security.RekeySecretAdminMonitordrwxr-xr-x 2 systemd-timesync sambashare 4096 Apr 10 18:56 jobs-rw-r--r-- 1 jenkins jenkins 907 May 21 19:10 nodeMonitors.xmldrwxr-xr-x 2 jenkins jenkins4096 May 21 19:09 nodes-rw-r--r-- 1 systemd-timesync sambashare 51 Apr 11 15:56 .ownerdrwxr-xr-x 2 systemd-timesync sambashare 4096 Apr 10 18:56 plugins-rw-r--r-- 1 systemd-timesync sambashare 46 Apr 11 16:18 queue.xml.bak-rw-r--r-- 1 systemd-timesync sambashare 64 Apr 10 18:56 secret.keydrwxr-xr-x 4 jenkins jenkins4096 May 21 19:15 secretsdrwxr-xr-x 2 jenkins jenkins4096 May 21 19:28 updatesdrwxr-xr-x 2 systemd-timesync sambashare 4096 Apr 10 19:09 userContentdrwxr-xr-x 3 jenkins jenkins4096 May 21 19:15 users}}Can be fixed by issuing:{{sudo chown jenkins pluginssudo chown jenkins userContentsudo chgrp jenkins userContentsudo chgrp jenkins plugins}}
[JIRA] [update-sites-manager-plugin] (JENKINS-28544) Update Center Permission Denied
Title: Message Title
Alex Shafer created an issue
Jenkins / JENKINS-28544
Update Center Permission Denied
Issue Type:
Bug
Assignee:
Unassigned
Components:
update-sites-manager-plugin
Created:
21/May/15 11:57 PM
Environment:
Oracle JDK 8 Debian 8 Installed via Jenkins Deb Package Repository
Priority:
Major
Reporter:
Alex Shafer
When attempting to install plugins using the Update Center, plugins can not be written to /var/lib/jenkins/plugins due to invalid permissions.
{{hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/plugins/ssh/2.4/ssh.hpi (redirected to: http://ftp-nyc.osuosl.org/pub/jenkins/plugins/ssh/2.4/ssh.hpi) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:797) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1148) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1309) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:744) Caused by: java.io.FileNotFoundException: /var/lib/jenkins/plugins/ssh.jpi.tmp (Per
[JIRA] [update-sites-manager-plugin] (JENKINS-28544) Update Center Permission Denied
Title: Message Title
Alex Shafer updated an issue
Jenkins / JENKINS-28544
Update Center Permission Denied
Change By:
Alex Shafer
When attempting to install plugins using the Update Center, plugins can not be written to /var/lib/jenkins/plugins due to invalid permissions. {{ hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/plugins/ssh/2.4/ssh.hpi (redirected to: http://ftp-nyc.osuosl.org/pub/jenkins/plugins/ssh/2.4/ssh.hpi) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:797) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1148) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1309) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1126) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:744)Caused by: java.io.FileNotFoundException: /var/lib/jenkins/plugins/ssh.jpi.tmp (Permission denied) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:206) at java.io.FileOutputStream.(FileOutputStream.java:156) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:763) ... 7 more }} {{***@*** /var/lib/jenkins $ ls -altotal 80drwxr-xr-x 11 jenkins jenkins4096 May 21 19:27 .drwxr-xr-x 48 root root 4096 May 2 18:23 ..-rw-r--r-- 1 systemd-timesync sambashare0 Apr 10 19:04 atomic3320745316088279947.tmp-rw-r--r-- 1 jenkins jenkins1715 May 21 19:15 config.xml-rw-r--r-- 1 jenkins jenkins 0 May 21 19:10 Download metadata.log-rw-r--r-- 1 systemd-timesync sambashare0 Apr 11 04:16 Fingerprint cleanup.log-rw-r--r-- 1 jenkins jenkins 160 May 21 19:27 hudson.model.UpdateCenter.xml-rw--- 1 systemd-timesync sambashare 1675 Apr 10 19:09 identity.keydrwxr-xr-x 3 jenkins jenkins4096 May 21 19:09 .java-rw-r--r-- 1 jenkins jenkins 138 May 21 19:14 jenkins.model.DownloadSettings.xml-rw-r--r-- 1 jenkins jenkins 169 May 21 19:14 jenkins.security.QueueItemAuthenticatorConfiguration.xmldrwxr-xr-x 2 jenkins jenkins4096 May 21 19:13 jenkins.security.RekeySecretAdminMonitordrwxr-xr-x 2 systemd-timesync sambashare 4096 Apr 10 18:56 jobs-rw-r--r-- 1 jenkins jenkins 907 May 21 19:10 nodeMonitors.xmldrwxr-xr-x 2 jenkins jenkins4096 May 21 19:09 nodes-rw-r--r-- 1 systemd-timesync sambashare 51 Apr 11 15:56 .ownerdrwxr-xr-x 2 systemd-timesync sambashare 4096 Apr 10 18:56 plugins-rw-r--r-- 1 systemd-timesync sambashare 46 Apr 11 16:18 queue.xml.bak-rw-r--r-- 1 systemd-timesync sambashare 64 Apr 10 18:56 secret.keydrwxr-xr-x 4 jenkins jenkins4096 May 21 19:15 secretsdrwxr-xr-x 2 jenkins jenkins4096 May 21 19:28 updatesdrwxr-xr-x 2 systemd-timesync sambashare 4096 Apr 10 19:09 userContentdrwxr-xr-x 3 jenkins jenkins4096 May 21 19:15 users}}Can be fixed by issuing:{{sudo chown jenkins pluginssudo chown jenkins userContentsudo chgrp jenkins userContentsudo chgrp jenkins plugins}}
[JIRA] [build-token-root-plugin] (JENKINS-28543) Additional parameters not being passed
Title: Message Title Jay Kah created an issue Jenkins / JENKINS-28543 Additional parameters not being passed Issue Type: Bug Assignee: Jesse Glick Components: build-token-root-plugin Created: 21/May/15 11:46 PM Environment: Jenkins latest, all plugins up-to-date Priority: Minor Reporter: Jay Kah The documentation states that: Trigger the RevolutionTest job with the token TacoTuesday and parameter Type supplied with the value Mexican buildByToken/buildWithParameters?job=RevolutionTest&token=TacoTuesday&Type=Mexican However, when I add the Type parameter with value it is nowhere to be seen. I have tried printing it, passing it, and checking the env variables for it - to no avail. Now I might be looking in the wrong place, and if I am, would appreciate if someone could shed some light on the matter. Thanks!
[JIRA] [git-plugin] (JENKINS-28529) Git polling deletes files in workspace if "clean" and "ignore commits in path" are both enabled
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28529 Git polling deletes files in workspace if "clean" and "ignore commits in path" are both enabled Change By: Mark Waite Summary: Git polling deletes files in workspace if " clean " and " ignore commits in path " are both enabled 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-plugin] (JENKINS-28540) Set git publisher user.name from credentials instead of using global setting
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28540 Set git publisher user.name from credentials instead of using global setting Change By: Mark Waite Summary: Set git publisher fails if user. email and user. name from credentials instead of using global setting 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-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28540 git publisher fails if user.email and user.name Change By: Mark Waite Component/s: git-client-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] [git-client-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28540 git publisher fails if user.email and user.name Change By: Mark Waite Issue Type: Bug New Feature 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-client-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28540 git publisher fails if user.email and user.name Change By: Mark Waite Priority: Major Minor 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] [parameterized-remote-trigger-plugin] (JENKINS-28504) Add Folder Support To the Parameterized Remote Trigger Plugin
Title: Message Title Steven Christou closed an issue as Duplicate Jenkins / JENKINS-28504 Add Folder Support To the Parameterized Remote Trigger Plugin Change By: Steven Christou Status: Open Closed Resolution: Duplicate 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-client-plugin] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-20356 Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service Change By: Mark Waite Assignee: Mark Waite 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-client-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title martinfr62 commented on JENKINS-28540 Re: git publisher fails if user.email and user.name So thanks for the hint about the global configuration - and this does work both for the artifactory plugin and the git publisher. That said I believe the name of the user in the commit should be the owner of the credentials used. Not a generic username called jenkins. From a SOX compliance issue - allowing the username to not match the credentials used is a 'really bad thing'. Being able to trace who made a change to a system and when they did it - and proof that only they could do so (ie they had access to the credentials) is of primary importance where the SOX compliance is required. 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] [aws-lambda-plugin] (JENKINS-28441) refactor project for future feature additions
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28441 Re: refactor project for future feature additions Code changed in jenkins User: cast Path: src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeBuildStep.java src/main/java/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeVariables.java src/main/java/com/xti/jenkins/plugin/awslambda/service/LambdaService.java src/main/java/com/xti/jenkins/plugin/awslambda/upload/LambdaUploadBuildStep.java src/main/resources/com/xti/jenkins/plugin/awslambda/invoke/LambdaInvokeVariables/config.jelly http://jenkins-ci.org/commit/aws-lambda-plugin/0d68c974f1f718f9048e0291cd259042d3b51a7c Log: JENKINS-28441 Fixed Lambda invoke as a build step, awaiting testing 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] [parameterized-remote-trigger-plugin] (JENKINS-28504) Add Folder Support To the Parameterized Remote Trigger Plugin
Title: Message Title Steven Christou updated an issue Jenkins / JENKINS-28504 Add Folder Support To the Parameterized Remote Trigger Plugin Change By: Steven Christou URL: https://cloudbees.zendesk.com/agent/tickets/26401 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] [maven-plugin] (JENKINS-23826) Allow automatic install of Maven 3.2.2
Title: Message Title Arnaud Héritier resolved as Fixed Duplicates INFRA-181 Jenkins / JENKINS-23826 Allow automatic install of Maven 3.2.2 Change By: Arnaud Héritier 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] [git-client-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title Mark Waite commented on JENKINS-28540 Re: git publisher fails if user.email and user.name I don't think that using a globally defined user.name and user.email for git allows someone to forge who made a change any more (or less) than git already allows anyone to "forge" who made a change. Git allows any value to be assigned to the git user.name and user.email. As far as I can tell, Git relies on operating system permissions to defend its repositories, and it relies on human beings (web of trust) to prevent forgery of change authorship. There was a 2009 discussion of using GPG signed commits, but Linus doesn't see value in them. Jenkins provides a place for you to assign the git user.name and user.email which will be used for commits performed by the Jenkins server. You configure that information in the "Configure System" page (for example http://localhost:8080/configure). In my case, I specifically want the commit to be listed as being performed by the Jenkins user, even if I've allowed the Jenkins user to perform certain operations (like "git push") with my credentials. Use of my credentials for the push does not mean that I want my user.name or my user.email placed in the commit message. In a specific case I use at the office, I have the Git Publisher push from a single job to multiple repositories using different credentials for each destination repository. If that job wanted to apply a tag prior to that collection of push operations, which credential should it choose? 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] [snsnotify-plugin] (JENKINS-28542) SNS notifier plugin missing httpcore dependency
Title: Message Title Milo Hyson updated an issue Jenkins / JENKINS-28542 SNS notifier plugin missing httpcore dependency Change By: Milo Hyson Installing the released snsnotify-plugin v1.9 on a completely stock Jenkins v1.614 does not work. Builds using the plugin fail with the following exception on stdout :java.lang.NoClassDefFoundError: org/apache/http/util/Args at org.apache.http.conn.scheme.Scheme.(Scheme.java:90) at org.apache.http.impl.conn.SchemeRegistryFactory.createDefault(SchemeRegistryFactory.java:50) at com.amazonaws.http.ConnectionManagerFactory.createPoolingClientConnManager(ConnectionManagerFactory.java:29) at com.amazonaws.http.HttpClientFactory.createHttpClient(HttpClientFactory.java:104) at com.amazonaws.http.AmazonHttpClient.(AmazonHttpClient.java:198) at com.amazonaws.AmazonWebServiceClient.(AmazonWebServiceClient.java:132) at com.amazonaws.AmazonWebServiceClient.(AmazonWebServiceClient.java:116) at com.amazonaws.services.sns.AmazonSNSClient.(AmazonSNSClient.java:147) at com.amazonaws.services.sns.AmazonSNSClient.(AmazonSNSClient.java:128) at org.jenkinsci.plugins.snsnotify.AmazonSNSNotifier.send(AmazonSNSNotifier.java:156) at org.jenkinsci.plugins.snsnotify.AmazonSNSNotifier.sendSafe(AmazonSNSNotifier.java:102) at org.jenkinsci.plugins.snsnotify.AmazonSNSNotifier.onStarted(AmazonSNSNotifier.java:79) at org.jenkinsci.plugins.snsnotify.BuildListener.onStarted(BuildListener.java:19) at org.jenkinsci.plugins.snsnotify.BuildListener.onStarted(BuildListener.java:8) at hudson.model.listeners.RunListener.fireStarted(RunListener.java:215) at hudson.model.Run.execute(Run.java:1740) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374)Caused by: java.lang.ClassNotFoundException: org.apache.http.util.Args at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1376) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079) at java.lang.ClassLoader.loadClass(ClassLoader.java:358) ... 19 moreAn easy fix is to add the following to the pom.xml and rebuild:org.apache.httpcomponentshttpcore4.4.1 Add Comment
[JIRA] [snsnotify-plugin] (JENKINS-28542) SNS notifier plugin missing httpcore dependency
Title: Message Title Milo Hyson updated an issue Jenkins / JENKINS-28542 SNS notifier plugin missing httpcore dependency Change By: Milo Hyson Priority: Blocker 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] [snsnotify-plugin] (JENKINS-28542) SNS notifier plugin missing httpcore dependency
Title: Message Title Milo Hyson created an issue Jenkins / JENKINS-28542 SNS notifier plugin missing httpcore dependency Issue Type: Bug Assignee: Unassigned Components: snsnotify-plugin Created: 21/May/15 9:22 PM Environment: Stock Jenkins v1.614 snsnotify-plugin v1.9 Priority: Blocker Reporter: Milo Hyson Installing the released snsnotify-plugin v1.9 on a completely stock Jenkins v1.614 does not work. Builds using the plugin fail with the following exception: java.lang.NoClassDefFoundError: org/apache/http/util/Args at org.apache.http.conn.scheme.Scheme.(Scheme.java:90) at org.apache.http.impl.conn.SchemeRegistryFactory.createDefault(SchemeRegistryFactory.java:50) at com.amazonaws.http.ConnectionManagerFactory.createPoolingClientConnManager(ConnectionManagerFactory.java:29) at com.amazonaws.http.HttpClientFactory.createHttpClient(HttpClientFactory.java:104) at com.amazonaws.http.AmazonHttpClient.(AmazonHttpClient.java:198) at com.amazonaws.AmazonWebServiceClient.(AmazonWebServiceClient.java:132) at com.amazonaws.AmazonWebServiceClient.(AmazonWebServiceClient.java:116) at com.amazonaws.services.sns.AmazonSNSClient.(AmazonSNSClient.java:147) at com.amazonaws.services.sns.AmazonSNSClient.(AmazonSNSClient.java:128) at org.jenkinsci.plugins.snsnotify.AmazonSNSNotifier.send(AmazonSNSNotifier.java:1
[JIRA] [coverity-plugin] (JENKINS-28541) [COMMAND LINE ERROR] Undefined option 'dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp
Title: Message Title Shoban Cheekuru updated an issue Jenkins / JENKINS-28541 [COMMAND LINE ERROR] Undefined option 'dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp Change By: Shoban Cheekuru HiI have installed coverity jekins plugin and created coverity job with coverity instance manager with the given instruction in the jenkins plugin siteHere is the consol log Checking Coverity configuration...[Stream] Testcoverity/Test Project for Shoban/New Stream - 1106 : OK (version: 7.5.1)[Node] rtp-wasl-bldex : version 7.5.1Configuration is valid.[EnvInject] - Loading node environment variables.Building remotely on slave1 linux ) in workspace /bms/tools/jenkins/workspace/TestCoverity[Coverity] cmd so far is: [/bms/tools/coverity/7.5.1/cov-analysis-linux64-7.5.1_csco/bin/cov-analyze, --dir, /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp, --java, --all, --ticker-mode, none, --enable-constraint-fpp, --enable-callgraph-metrics, --force, --hfa][TestCoverity] $ /bms/tools/coverity/7.5.1/cov-analysis-linux64-7.5.1_csco/bin/cov-analyze --dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp --java --all --ticker-mode none --enable-constraint-fpp --enable-callgraph-metrics --force --hfa[COMMAND LINE ERROR] Undefined option 'dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp --java --all --ticker-mode none --enable-constraint-fpp --enable-callgraph-metrics --force --hfa'Specify --help for assistance.[Coverity] /bms/tools/coverity/7.5.1/cov-analysis-linux64-7.5.1_csco/bin/cov-analyze returned 2, aborting...Build step 'Coverity' changed build result to FAILUREFinished: FAILURE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [coverity-plugin] (JENKINS-28541) [COMMAND LINE ERROR] Undefined option 'dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp
Title: Message Title Shoban Cheekuru updated an issue Jenkins / JENKINS-28541 [COMMAND LINE ERROR] Undefined option 'dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp Change By: Shoban Cheekuru HiI have installed coverity jekins plugin and created coverity job with coverity instance manager with the given instruction in the jenkins plugin siteHere is the consol log Checking Coverity configuration...[Stream] Testcoverity/Test Project for Shoban/New Stream - 1106 : OK (version: 7.5.1)[Node] rtp-wasl-bldex : version 7.5.1Configuration is valid.[EnvInject] - Loading node environment variables.Building remotely on rtp-wasl-bldex (vm5 rtp slave1 linux) in workspace /bms/tools/jenkins/workspace/TestCoverity[Coverity] cmd so far is: [/bms/tools/coverity/7.5.1/cov-analysis-linux64-7.5.1_csco/bin/cov-analyze, --dir, /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp, --java, --all, --ticker-mode, none, --enable-constraint-fpp, --enable-callgraph-metrics, --force, --hfa][TestCoverity] $ /bms/tools/coverity/7.5.1/cov-analysis-linux64-7.5.1_csco/bin/cov-analyze --dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp --java --all --ticker-mode none --enable-constraint-fpp --enable-callgraph-metrics --force --hfa[COMMAND LINE ERROR] Undefined option 'dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp --java --all --ticker-mode none --enable-constraint-fpp --enable-callgraph-metrics --force --hfa'Specify --help for assistance.[Coverity] /bms/tools/coverity/7.5.1/cov-analysis-linux64-7.5.1_csco/bin/cov-analyze returned 2, aborting...Build step 'Coverity' changed build result to FAILUREFinished: FAILURE Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [groovy-plugin] (JENKINS-28502) Install from http://groovy.codehaus.org installer method failing
Title: Message Title Arnaud Héritier commented on JENKINS-28502 Re: Install from http://groovy.codehaus.org installer method failing The groovy team forgot to move its distributions All of them aren't on bintray They are waiting that Ben Walding give them back a copy of groovy distros to deploy them on Bintray 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] [groovy-plugin] (JENKINS-28502) Install from http://groovy.codehaus.org installer method failing
Title: Message Title Christopher Orr commented on JENKINS-28502 Re: Install from http://groovy.codehaus.org installer method failing aheritier said on IRC that he checked with the Groovy team, and they're going to try and get the old downloads on bintray too at some point. 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-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name
Title: Message Title Mark Waite edited a comment on JENKINS-28506 Re: [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name I believe the breaking change between 2.3.4 and 2.3.5 is [85463e9|https://github.com/jenkinsci/git-plugin/commit/85463e98eb410081222792b4d899c71cfbf42e9d]. More investigation is needed. The investigation is proceeding on my [forked copy|https://github.com/MarkEWaite/git-plugin] of the repository in branches named "master-JENKINS-28506*". 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-client-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title martinfr62 commented on JENKINS-28540 Re: git publisher fails if user.email and user.name So I tested - the email doesnt seem to be recorded - atleast not in stash. But the username is - it even tho we might use the credentials with the name 'bill', if the username is set to fred - that's who will appear to have performed the work. As for use case - it allows someone to 'forge' who made a change. 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-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-28506 [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name Change By: Mark Waite Assignee: Nicolas De Loof Mark Waite 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-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name
Title: Message Title Mark Waite started work on JENKINS-28506 Change By: Mark Waite 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] [coverity-plugin] (JENKINS-28541) [COMMAND LINE ERROR] Undefined option 'dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp
Title: Message Title Shoban Cheekuru created an issue Jenkins / JENKINS-28541 [COMMAND LINE ERROR] Undefined option 'dir /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp Issue Type: Bug Assignee: Ken Dang Components: coverity-plugin Created: 21/May/15 8:37 PM Environment: jenkins version : Jenkins ver. 1.580.3 Coverity Plugin :1.5.0 OS: Linux Browser: Firefox Java: JDK1.7 Coverity Instance: 7.5.x Coverity Analysis tool : 7.5.x Priority: Critical Reporter: Shoban Cheekuru Hi I have installed coverity jekins plugin and created coverity job with coverity instance manager with the given instruction in the jenkins plugin site Here is the consol log Checking Coverity configuration... [Stream] Testcoverity/Test Project for Shoban/New Stream - 1106 : OK (version: 7.5.1) [Node] rtp-wasl-bldex : version 7.5.1 Configuration is valid. [EnvInject] - Loading node environment variables. Building remotely on rtp-wasl-bldex (vm5 rtp slave1 linux) in workspace /bms/tools/jenkins/workspace/TestCoverity [Coverity] cmd so far is: [/bms/tools/coverity/7.5.1/cov-analysis-linux64-7.5.1_csco/bin/cov-analyze, --dir, /bms/tools/jenkins/coverity/temp-3643448916814087209.tmp, --java, --all, --ticker-mode, none, --enable-constraint-fpp, --enable-callgraph-metrics,
[JIRA] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name
Title: Message Title Mark Waite commented on JENKINS-28506 Re: [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name I believe the breaking change between 2.3.4 and 2.3.5 is 85463e9. More investigation is needed. 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-client-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title Mark Waite commented on JENKINS-28540 Re: git publisher fails if user.email and user.name The Jenkins credentials systems doesn't track an e-mail address for a credential, at least as far as I can tell. Can you further explain why the globally configured git user name and git use e-mail are not sufficient for this use case? Is the name of the user that created the tag significant and changing from one job or one run to the next? Is the e-mail of the user that created the tag significant and changing from one job or one run to the next? 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-28532) Jobs get stuck in the queue
Title: Message Title Magnus Sandberg commented on JENKINS-28532 Re: Jobs get stuck in the queue PrioritySorter will only order the Jobs in the Queue and will not interfere with execution/scheduling (if you do not use "Run Exclusive") so this does look like a problem somewhere else. Totally of the topic: You are the first one I see that uses anything else besides "Absolute" sorting - I would be happy if you can share your thought on the Queueing strategy, feel free to email me. Thanks, 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-client-plugin] (JENKINS-28540) git publisher fails if user.email and user.name
Title: Message Title martinfr62 created an issue Jenkins / JENKINS-28540 git publisher fails if user.email and user.name Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin, git-plugin Created: 21/May/15 7:19 PM Environment: Jenkins 1.611, git 2.1.0, git-plugin 2.3.5, git-client-plugin 1.7.1 Priority: Major Reporter: martinfr62 Attempting to use git publisher with command line git - get following error when attempt to use git-plugin with ssh credentials (seems to also happen with username/password). Adding commands git config --global user.email "yy...@.com" git config --global user.name "" as a build step made this work. git publisher/git-client should preset these locally using the ssh-credentials so we dont need to duplicate them by adding a build step or adding to the build slaves - should be provided from the credentials. ERROR: Failed to push merge to origin repository hudson.plugins.git.GitException: Could not apply tag jenkins-ZipManagerTag-12-SUCCESS at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.tag(CliGitAPIImpl.java:1201) at hudson.plugins.git.GitAPI.tag(GitAPI.java:274) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-28436) Running HP ALM installs .exe on linux and tried to run it
Title: Message Title ravi balla commented on JENKINS-28436 Re: Running HP ALM installs .exe on linux and tried to run it Hi Tina, I face the same issue. Any work around so far for you? 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-28531) Out of memory
Title: Message Title Demitrius Nelon commented on JENKINS-28531 Re: Out of memory https://github.com/jenkinsci/docker-plugin/issues/221 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] [accelerated-build-now-plugin] (JENKINS-28539) InvocationTargetException after Upgrade to 1.6 Jenkins
Title: Message Title Darko Palic commented on JENKINS-28539 Re: InvocationTargetException after Upgrade to 1.6 Jenkins maybe related, since they show up after a upgrade from 1.5 to 1.6 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] [accelerated-build-now-plugin] (JENKINS-28539) InvocationTargetException after Upgrade to 1.6 Jenkins
Title: Message Title Darko Palic created an issue Jenkins / JENKINS-28539 InvocationTargetException after Upgrade to 1.6 Jenkins Issue Type: Bug Assignee: Anthony Dahanne Attachments: jenkins.log Components: accelerated-build-now-plugin Created: 21/May/15 6:34 PM Environment: Ubuntu 14.04 LTS x64 Jenkins 1.614 Labels: exception Priority: Critical Reporter: Darko Palic We are facing this issue if we restart the jenkins. Since the jenkins is not working properly anymore, we are not sure where this error comes from. Please see for the detailed view the attached logfile Similar issues: May 21, 2015 7:38:14 PM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluati
[JIRA] [cloudbees-folder-plugin] (JENKINS-28538) CCE after Upgrade to 1.6 Jenkins
Title: Message Title Darko Palic created an issue Jenkins / JENKINS-28538 CCE after Upgrade to 1.6 Jenkins Issue Type: Bug Assignee: Jesse Glick Attachments: jenkins.log Components: cloudbees-folder-plugin Created: 21/May/15 6:21 PM Environment: Ubuntu 14.04 LTS x64 Oracle JDK 1.7 Jenkins 1.614 Labels: exception Priority: Critical Reporter: Darko Palic We have used jenkins for a while successfully, but now we are facing a issue, we cannot handle anymore ourself. Also the Jenkins takes roughly 10 minutes to load now the pages. So we are nearly lost now with the jenkins... basically I am getting similar issues like this (see the attached logfile) WARNING: Caught exception evaluating: it.ge
Ваш E-mail ID выиграл один миллион долларов от Объединенных Нация премии Грант Связаться Mr.robin Стивеном за Претензии
-- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
Title: Message Title James Nord commented on JENKINS-25203 Re: support embedded content in json 1.580 is needed for JENKINS-25280 if you don't care about that it should be possible to back port if you as a dependency on security-144-compat But you should upgrade Jenkins instead �� 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] [findbugs-plugin] (JENKINS-28537) Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.0:sonar (default-cli) on project XXXXX: Can not execute Sonar: Can not execute Findbugs: TimeoutE
Title: Message Title Antonio García created an issue Jenkins / JENKINS-28537 Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.0:sonar (default-cli) on project X: Can not execute Sonar: Can not execute Findbugs: TimeoutException Issue Type: Bug Assignee: Ulli Hafner Components: findbugs-plugin, sonar Created: 21/May/15 6:01 PM Labels: exception plugins jenkins Priority: Major Reporter: Antonio García I am working with jenkins 1.515, SonarSource v.3.2.1, Maven 3.0.4, with SonarQube Plugin 2.0.1. configured on Jenkins: I had not applied any kind of upgrade Recently when construction process job start, it takes more time than previous construcctions. I noticed this when SonarSource Plugin start to analyzing code, i.e. FindBugs,Java AST Scan, etc., and finally an exception is thrown due to: [ERROR] Failed to execute goal org.codehaus.mojo:sonar-maven-plugin:2.0:sonar (default-cli) on project X: Can not execute Sonar: Can not execute Findbugs: TimeoutException -> [Help 1]
[JIRA] [core] (JENKINS-19939) Discard Old Builds I/O Performance Issue
Title: Message Title Daniel Beck edited a comment on JENKINS-19939 Re: Discard Old Builds I/O Performance Issue bq. Hi, I'm hoping this bug can be revisited. Consider addressing my comments to clarify what the issue is.bq. Some sort of info in the log info be very welcome.I'll look into that.bq. Some other plugins that do work after a build completes, such as "Calculation of disk usage of workspace", do log the time they took. I think this plugin should do so as well.It's in core, not in a plugin. That said, the problem with the BuildDiscarder API is that it does not support having a user-visible log at all at the moment. It's not strictly related to a build, and therefore not really expected to write to the build log. After a build finishes is simply a good time to dicard old 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] [core] (JENKINS-19939) Discard Old Builds I/O Performance Issue
Title: Message Title Daniel Beck commented on JENKINS-19939 Re: Discard Old Builds I/O Performance Issue Hi, I'm hoping this bug can be revisited. Consider addressing my comments to clarify what the issue is. Some sort of info in the log info be very welcome. I'll look into that. Some other plugins that do work after a build completes, such as "Calculation of disk usage of workspace", do log the time they took. I think this plugin should do so as well. It's in core, not in a 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] [vsphere-cloud-plugin] (JENKINS-28536) Deploy VM from Template no longer working
Title: Message Title Mark Manning created an issue Jenkins / JENKINS-28536 Deploy VM from Template no longer working Issue Type: Bug Assignee: Unassigned Components: vsphere-cloud-plugin Created: 21/May/15 5:43 PM Environment: Jenkins 1.613 vSphere-cloud-plugin 2.5 VMWare vSphere 5.5 Priority: Minor Reporter: Mark Manning Deploy VM from Template no longer working for me. My configured jobs were working using "Deploy VM from template" with vsphere-cloud-plugin 1.1.12, but stopped working when I upgraded to 2.4. Doesn't work with 2.5 either. Output: >> [vSphere] Performing vSphere build step: "Deploy VM from template" >> [vSphere] Attempting to use server configuration: "vcenterbuild" >> [vSphere] Deploying new vm "TEST123" from template "BaseTemplate" >> [vSphere] Started cloning of VM. Please wait ... >> [vSphere] Exception: org.jenkinsci.plugins.vsphere.tools.VSphereException: vSphere Error: Couldn't clone "BaseTemplate"! Does "TEST123" already exist? Clone task ended with status error The VM TEST123 does not exist and never did exist in my vSphere environment.
[JIRA] [active-directory-plugin] (JENKINS-28535) AD authentication upper case logon name
Title: Message Title rich nahra created an issue Jenkins / JENKINS-28535 AD authentication upper case logon name Issue Type: Bug Assignee: Unassigned Components: active-directory-plugin Created: 21/May/15 5:32 PM Environment: Jenkins Active Directory plugin 1.39 Priority: Minor Reporter: rich nahra when users are provisioned using Matrix-based security within Jenkins and uppercase logon names, the authentication succeeds but users are presented with "overall read permission" error despite being an administrator. Add Comment
[JIRA] [git-plugin] (JENKINS-28506) [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28506 [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch name Change By: Mark Waite Summary: [REGRESSION] Git fails to trigger from polling for refs/heads/ style branch 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] [git-plugin] (JENKINS-28529) Git polling deletes files in workspace if clean and ignore commits in path both enabled
Title: Message Title Mark Waite edited a comment on JENKINS-28529 Re: Git polling deletes files in workspace if clean and ignore commits in path both enabled I've verified that the problem is repeatable if an exclusion path is defined in the job and "clean before checkout" is enabled.My test case was: 1. # Create a git repository with an ant build script that creates a temporary file as its default target 2. # Define a Jenkins job which monitors that repository and runs the ant build script, confirm the workspace has the temporary file after polling 3. # Enable "clean before checkout" on that Jenkins job, confirm the workspace has the temporary file after polling 4. # Enable path exclusion on the Jenkins job, confirm that the temporary file is deleted from the workspace by the next poll 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-plugin] (JENKINS-28529) Git polling deletes files in workspace if clean and ignore commits in path both enabled
Title: Message Title Mark Waite edited a comment on JENKINS-28529 Re: Git polling deletes files in workspace if clean and ignore commits in path both enabled I've verified that the problem is repeatable if an exclusion path is defined in the job and "clean before checkout" is enabled.My test case was: 1. Create a git repository with an ant build script that creates a temporary file as its default target2. Define a Jenkins job which monitors that repository and runs the ant build script, confirm the workspace has the temporary file after polling3. Enable "clean before checkout" on that Jenkins job, confirm the workspace has the temporary file after polling4. Enable path exclusion on the Jenkins job, confirm that the temporary file is deleted from the workspace by the next poll 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-plugin] (JENKINS-28529) Git polling deletes files in workspace if clean and ignore commits in path both enabled
Title: Message Title Mark Waite edited a comment on JENKINS-28529 Re: Git polling deletes files in workspace if clean and ignore commits in path both enabled I've verified that the problem is repeatable if an exclusion path is defined in the job and "clean before checkout" is enabled.My test case was: * 1. Create a git repository with an ant build script that creates a temporary file as its default target * 2. Define a Jenkins job which monitors that repository and runs the ant build script, confirm the workspace has the temporary file after polling * 3. Enable "clean before checkout" on that Jenkins job, confirm the workspace has the temporary file after polling * 4. Enable path exclusion on the Jenkins job, confirm that the temporary file is deleted from the workspace by the next poll 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-28531) Out of memory
Title: Message Title Demitrius Nelon commented on JENKINS-28531 Re: Out of memory The docker plugin was unchecked and when I checked it, I got an error about a missing breadcrumb. I downloaded the 0.8 version of the docker plugin and put it in place and restarted jenkins to get the out of memory exception again... 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] [jenkins-cloudformation] (JENKINS-28534) Adding Proxy adds a password automatically
Title: Message Title suprinder pujji created an issue Jenkins / JENKINS-28534 Adding Proxy adds a password automatically Issue Type: Bug Assignee: Unassigned Components: jenkins-cloudformation Created: 21/May/15 5:07 PM Priority: Blocker Reporter: suprinder pujji Adding Proxy in the Advanced tab of Manage Plugins automatically adds a encrypted string in the password edit box. Whereas I dont have a password asociated with the proxy. Also I cannot submit a proxy settings without the password and I get job failure Add Comment
[JIRA] [git-plugin] (JENKINS-28529) Git polling deletes files in workspace if clean and ignore commits in path both enabled
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28529 Git polling deletes files in workspace if clean and ignore commits in path both enabled Change By: Mark Waite Component/s: git-plugin Component/s: git-client-plugin Environment: Jenkins ver. 1.596, git- plugin 2.3.5,git- client-plugin 1.16.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] [git-client-plugin] (JENKINS-28529) Git polling deletes files in workspace if clean and ignore commits in path both enabled
Title: Message Title Mark Waite commented on JENKINS-28529 Re: Git polling deletes files in workspace if clean and ignore commits in path both enabled I've verified that the problem is repeatable if an exclusion path is defined in the job and "clean before checkout" is enabled. My test case was: Create a git repository with an ant build script that creates a temporary file as its default target Define a Jenkins job which monitors that repository and runs the ant build script, confirm the workspace has the temporary file after polling Enable "clean before checkout" on that Jenkins job, confirm the workspace has the temporary file after polling Enable path exclusion on the Jenkins job, confirm that the temporary file is deleted from the workspace by the next poll 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-client-plugin] (JENKINS-28529) Git polling deletes files in workspace if clean and ignore commits in path both enabled
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28529 Git polling deletes files in workspace if clean and ignore commits in path both enabled Change By: Mark Waite Summary: Git polling deletes files in workspace if clean and ignore commits in path both enabled 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-client-plugin] (JENKINS-28529) Git polling deletes files in workspace if clean and ignore commits in path enabled
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-28529 Git polling deletes files in workspace if clean and ignore commits in path enabled Change By: Mark Waite Summary: Git polling deletes files in workspace if clean and ignore commits in path enabled 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-28531) Out of memory
Title: Message Title Demitrius Nelon commented on JENKINS-28531 Re: Out of memory I renamed the docker-plugin and directory and restarted Jenkins and it came back up. I'm going to attempt to add the docker-plugin again. 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-28531) Out of memory
Title: Message Title Demitrius Nelon commented on JENKINS-28531 Re: Out of memory I'm running: CentOS release 6.6 (Final) There is no GUI for VisualVM to attach to. I've already played with: Xss Xmx Xms The system was working fine last night and this morning I was getting the out of memory and the docker slave containers were sitting at 10+ hours which is very unusual as my builds rarely take more than 5 minutes. 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] [promoted-builds-plugin] (JENKINS-28533) Promoted build does not respect "Restrict where this promotion process can be run" check with empty label
Title: Message Title
juan pablo santos created an issue
Jenkins / JENKINS-28533
Promoted build does not respect "Restrict where this promotion process can be run" check with empty label
Issue Type:
Bug
Assignee:
Unassigned
Components:
promoted-builds-plugin
Created:
21/May/15 4:37 PM
Priority:
Major
Reporter:
juan pablo santos
promoted builds plugin offers a "Restrict where this promotion process can be run" check, which in turn enables an input text label, which is accompanied by a "If not set, the label of the promoted build will be used" text.
So, every time you set the check to restrict where to run the promotion, with an empty label, the promoted job should run in the same node of the label. But if you go to the job's configuration screen, leave it untouched and save it, this parameter is lost and the promotion executes on any given node.
As it turns out, the check to restrict where to run the promotion is enabled or not depending on the value of the label's input text:
/hudson/plugins/promoted_builds/PromotionProcess/process-config.jelly, lines 40-46
"hasAssignedLabel" title="${%Restrict where this promotion process can be run}"
checked="${instance.assignedLabelString!=null}" inline="true">
"${%Label _expression_}"
description="If not set
[JIRA] [core] (JENKINS-28531) Out of memory
Title: Message Title James Howe commented on JENKINS-28531 Re: Out of memory https://wiki.jenkins-ci.org/display/JENKINS/I%27m+getting+OutOfMemoryError 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-28532) Jobs get stuck in the queue
Title: Message Title James Howe updated an issue Jenkins / JENKINS-28532 Jobs get stuck in the queue Change By: James Howe 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] [git-client-plugin] (JENKINS-28529) Git polling deletes files in workspace
Title: Message Title Ronny Schuetz commented on JENKINS-28529 Re: Git polling deletes files in workspace "Force polling to use workspace" isn't configured at all, the GIT plugin configuration just contains the 2 resp. 3 "Additional behavior" modules listed above. "Name" and "Refspec" are empty, "Branch specifier" is "master", git executable is not jgit, the git command line version used is "1.8.0.2" It happens when a workspace is already available. 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-28532) Jobs get stuck in the queue
Title: Message Title James Howe updated an issue Jenkins / JENKINS-28532 Jobs get stuck in the queue Change By: James Howe Unknown if core or plugin issue.Had a group of jobs stuck waiting in the queue.Hovering over them shows triggers and wait time as usual, but no indication of what they're waiting for. Suspicious log entry: May 21, 2015 4:43:19 PM hudson.util.DescribableList buildDependencyGraphSEVERE: Failed to build dependency graph for hudson.model.FreeStyleProject@57fdabe[MyStuckJob]java.lang.NullPointerExceptionat hudson.tasks.Fingerprinter$FingerprintAction.getFingerprints(Fingerprinter.java:373)at hudson.tasks.Fingerprinter$FingerprintAction.getDependencies(Fingerprinter.java:403)at hudson.tasks.Fingerprinter$FingerprintAction.getDependencies(Fingerprinter.java:390)at hudson.tasks.Fingerprinter.buildDependencyGraph(Fingerprinter.java:157)at hudson.util.DescribableList.buildDependencyGraph(DescribableList.java:219)at hudson.model.Project.buildDependencyGraph(Project.java:207)at hudson.model.DependencyGraph.build(DependencyGraph.java:95)at jenkins.model.Jenkins.rebuildDependencyGraph(Jenkins.java:3748)at jenkins.model.Jenkins$25.call(Jenkins.java:3770)at jenkins.model.Jenkins$25.call(Jenkins.java:3766)at java.util.concurrent.FutureTask.run(FutureTask.java:262)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:178)at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:292)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)Possibly caused by deleting some other jobs - they weren't supposed to be in the dependency tree, but coincidentally included identical files that were fingerprinted at some point.Queuing strategy is Weighted Fair Queuing.Weren't in the queue on startup, unless lack of JENKINS-28486 pulling them in would count. Add Comment
[JIRA] [core] (JENKINS-28531) Out of memory
Title: Message Title Demitrius Nelon created an issue Jenkins / JENKINS-28531 Out of memory Issue Type: Bug Assignee: Unassigned Components: core Created: 21/May/15 4:06 PM Environment: Jenkins 1.614-1.1 java -version openjdk version "1.8.0_45" OpenJDK Runtime Environment (build 1.8.0_45-b13) OpenJDK 64-Bit Server VM (build 25.45-b02, mixed mode) ansicolor.jpi cvs.jpi extra-columns.jpi htmlpublisher.jpi matrix-auth.jpi ruby-runtime.jpi token-macro.jpi antisamy-markup-formatter.jpi description-setter.jpi ghprb.jpi javadoc.jpi matrix-project.jpi scm-api.jpi translation.jpi ant.jpi docker-plugin.jpi git-client.jpi jenkins-flowdock-plugin.jpi maven-plugin.jpi script-security.jpi violations.jpi backup.jpi doclinks.jpi github-api.jpi jquery.jpi pam-auth.jpi ssh-agent.jpi windows-slaves.jpi build-pipeline-plugin.jpi durable-task.jpi github.jpi junit.jpi parameterized-trigger.jpi ssh-credentials.jpi ws-cleanup.jpi buildtriggerbadge.jpi email-ext.jpi git.jpi ldap.jpi rake.jpi ssh-slaves.jpi capitomcat.jpi embeddable-build-status.jpi git-parameter.jpi mailer.jpi ruby.jpi subversion.jpi credentials.jpi external-monitor-job.jpi greenballs.jpi mapdb-api.jpi rubyMetrics.jpi text-finder.jpi Priority: Minor Reporter: Demitrius Nelon Jenkins was working at the end of the day yesterday after slogging through the JRE 8 and Docker plugin upgrad
[JIRA] [core] (JENKINS-28531) Out of memory
Title: Message Title Demitrius Nelon updated an issue Jenkins / JENKINS-28531 Out of memory Change By: Demitrius Nelon Priority: Minor Blocker 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-28532) Jobs get stuck in the queue
Title: Message Title James Howe created an issue Jenkins / JENKINS-28532 Jobs get stuck in the queue Issue Type: Bug Assignee: Magnus Sandberg Components: core, prioritysorter-plugin Created: 21/May/15 4:06 PM Environment: Jenkins 1.611, prioritysorter 3.2 Priority: Minor Reporter: James Howe Unknown if core or plugin issue. Had a group of jobs stuck waiting in the queue. Hovering over them shows triggers and wait time as usual, but no indication of what they're waiting for. May 21, 2015 4:43:19 PM hudson.util.DescribableList buildDependencyGraph SEVERE: Failed to build dependency graph for hudson.model.FreeStyleProject@57fdabe[MyStuckJob] java.lang.NullPointerException at hudson.tasks.Fingerprinter$FingerprintAction.getFingerprints(Fingerprinter.java:373) at hudson.tasks.Fingerprinter$FingerprintAction.getDependencies(Fingerprinter.java:403) at hudson.tasks.Fingerprinter$FingerprintAction.getDependencies(Fingerprinter.java:390) at hudson.tasks.Fingerprinter.buildDependencyGraph(Fingerprinter.java:157) at hudson.util.DescribableList.buildDependencyGraph(DescribableList.java:219) at hudson.model.Project.buildDependencyGraph(Project.java:207) at hudson.model.DependencyGraph.build(DependencyGraph.java:95) at jenkins.model.Jenkins.rebuildDependencyGraph(Jenkins.java:3748) at jenkins.model.Jenkins$25.call(Jenkins.java:3770) at jenkins.model.Jen
[JIRA] [robot-plugin] (JENKINS-28530) Jenkins RobotFramework show multiconfiguration results in List View
Title: Message Title James Friedenberger created an issue Jenkins / JENKINS-28530 Jenkins RobotFramework show multiconfiguration results in List View Issue Type: Improvement Assignee: jpiironen Attachments: dashboard.jpg Components: robot-plugin Created: 21/May/15 4:05 PM Labels: dashboard Priority: Major Reporter: James Friedenberger When I have a multi-configured project, it would be nice to see the total test results in the List View column for Robot Results. Right now it shows up as blank and one has to click on the project to see any results from Robot Framework..
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-12092) Allow a job to completely block a category
Title: Message Title Seán Dunne stopped work on JENKINS-12092 Change By: Seán Dunne Status: In Progress Open 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] [throttle-concurrent-builds-plugin] (JENKINS-12092) Allow a job to completely block a category
Title: Message Title Seán Dunne started work on JENKINS-12092 Change By: Seán Dunne 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] [git-client-plugin] (JENKINS-28529) Git polling deletes files in workspace
Title: Message Title Mark Waite commented on JENKINS-28529 Re: Git polling deletes files in workspace Does it do that only when using "Force polling to use workspace", or does it happen when or not a workspace is already available? 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] [ldap-plugin] (JENKINS-4895) AD and LDAP fail due to Referrals
Title: Message Title redmumba commented on JENKINS-4895 Re: AD and LDAP fail due to Referrals I'd like to add--I filed this ticket almost 6 years ago, and I no longer work at the company where this was an issue. I'm sure a lot has changed since then, but at the time, the AD plug-in was not very well rounded, so we had to fall back on LDAP. 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-client-plugin] (JENKINS-28529) Git polling deletes files in workspace
Title: Message Title Ronny Schuetz created an issue Jenkins / JENKINS-28529 Git polling deletes files in workspace Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin Created: 21/May/15 3:43 PM Environment: Jenkins ver. 1.596, git-client-plugin 1.16.1 Priority: Major Reporter: Ronny Schuetz Sample GIT repo with the following content: ./dir1/file1 ./dir1/file3 ./dir2/file2 ./file1 ./file2 When using the following GIT client configuration
[JIRA] [plain-credentials-plugin] (JENKINS-28528) Secret File missing during post build Action
Title: Message Title Simon Devineau updated an issue Jenkins / JENKINS-28528 Secret File missing during post build Action Change By: Simon Devineau Summary: Secret File deleted before missing during post build Action 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] [plain-credentials-plugin] (JENKINS-28528) Secret File deleted before post build Action
Title: Message Title
Simon Devineau created an issue
Jenkins / JENKINS-28528
Secret File deleted before post build Action
Issue Type:
Bug
Assignee:
Jesse Glick
Components:
plain-credentials-plugin, sonar
Created:
21/May/15 3:41 PM
Environment:
Jenkins 1.599 Plain Credentials Plugin 1.1 SonarQube plugin 2.2
Labels:
plugin jenkins slave sonar-plugin
Priority:
Major
Reporter:
Simon Devineau
Hello everyone,
I have a job with a maven goal "clean install" In advanced option I set up the user settings.xml as follow $ {userSettings.xml}
where this variable is a binding from a secret file I created.
During the maven build, the same file is used but with a different uuid clean install
s D:-
---\secretFiles\e9b970a0-46b8-482e-bc1b-aca37e28ec52\settings-jenkins.xml
[JIRA] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Title: Message Title lacostej commented on JENKINS-23958 Re: Pipe Broken Thanks Charles for the logs. I don't know what's happening yet but this should help us a bit. I am surprised to not see more communication. What can I see: Pipe.Chunks are seen up to May 21, 2015 9:26:15 followed by lots of hudson.remoting.UnexportCommand a PingThread kicks in at May 21, 2015 9:27:40 AM a PingThread kicks in at May 21, 2015 9:28:11 AM nothing during 2 min a Pipe.Chunk is sent a Dead is received instead of an Ack Here's a patch to apply to your remoting.jar https://github.com/lacostej/remoting/commit/02969e1271443afc933dcb8e0d472c1dfc9e8856 that could help knowing why the Death. Maybe worth a shot ? This also should help a bit: https://wiki.jenkins-ci.org/display/JENKINS/Remoting+issue although Charles said he couldn't find any specific info in his slaves logs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [ldap-plugin] (JENKINS-4895) AD and LDAP fail due to Referrals
Title: Message Title
Andy Pemberton edited a comment on JENKINS-4895
Re: AD and LDAP fail due to Referrals
I believe the description of this issue is incorrect (at least it is today). This value can be configured by setting an environment variable:{{java.naming.referral=ignore}}Will cause the referrals to ignored. The trouble is that you will still receive a {{PartialResultException}} if AD attempts to return an entry with referrals when referrals are ignored (see here for explanation: http://docs.spring.io/spring-ldap/docs/current/apidocs/org/springframework/ldap/core/LdapTemplate.html). One other workaround may be to change the AD ports from 389 to 3268 (ldap) or from 636 to 3269 (ldaps) [per this SO thread|http://stackoverflow.com/questions/16412236/how-to-resolve-javax-naming-partialresultexception]. I believe the proper fix is to leverage functionality like available in the more recent spring-ldap framework's LdapTemplate.ignorePartialResultException property, perhaps setting that property to true for the Jenkins ldap-plugin's LdapTemplate (or at least set to true if the java.naming.referral property is set to ignore).
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] [cli] (JENKINS-28527) Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error.
Title: Message Title Alex Earl assigned an issue to Unassigned Jenkins / JENKINS-28527 Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error. Change By: Alex Earl Assignee: Alex Earl 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] [cli] (JENKINS-28527) Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error.
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-28527 Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error. Doesn't look like an issue with email-ext itself, so should be assigned to someone else. 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-26761) WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart
Title: Message Title Kenneth Baltrinic commented on JENKINS-26761 Re: WorkflowJob.getSCMs throws NullPointerException from notifyCommit hooks after Jenkins Restart FYI, this problem has yet again disappeared for us, but I will add the loggers and take the other debug steps mentioned should it re-appear. 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] [cli] (JENKINS-28527) Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error.
Title: Message Title
Kenneth Baltrinic created an issue
Jenkins / JENKINS-28527
Configuring mailer via groovy script via CLI fails with spurious 'missing jar' error.
Issue Type:
Bug
Assignee:
Alex Earl
Components:
cli, core, email-ext-plugin
Created:
21/May/15 2:58 PM
Environment:
This is occurring on various machines running 1.596.3 LTS on Centos 6.6. They have various plugins installed, however the likely relevant plugins, (mailer, email-ext) are the latest and greatest on each machine.
Priority:
Minor
Reporter:
Kenneth Baltrinic
We manage our Jenkins infrastructure via Chef which is configured to automatically upgrade the machines to the latest LTS version when it comes out. Chef runs on each machine every 30 min. Immediately following the latest LTS release to 1.596.3, our chef runs started failing frequently but intermittently (about 50% of the time). The run fails at the point where we use the jenkins-cli groovy to configure certain properties of the mailer by means of running a script.
The script template looks like the following:
import jenkins.model.*
def inst = Jenkins.getInstance()
def desc = inst.getDescriptor('hudson.tasks.Mailer')
desc.setSmtpHost("#{node['cvent-jenkins']['ema
[JIRA] [mercurial-plugin] (JENKINS-28526) Build emails reference unrelated changesets
Title: Message Title Kent Johnson created an issue Jenkins / JENKINS-28526 Build emails reference unrelated changesets Issue Type: Bug Assignee: Jesse Glick Components: mercurial-plugin Created: 21/May/15 2:44 PM Environment: Jenkins 1.614, mercurial-plugin 1.52, mercurial 3.4, Windows 64 Priority: Minor Reporter: Kent Johnson Mercurial 3.4 changed the behavior of the log command as used by this plugin. A command such as hg log --rev default:0 --follow --prune 5029 now will show unrelated changesets on other branches (specifically the head of an active branch other than default). This results in build logs and emails that show unrelated changesets and build emails being sent to the authors of unrelated changesets. AFAICT the mercurial changeset is http://hg.intevation.org/mercurial/crew/rev/c260887cdbcd. There is related discussion here: http://thread.gmane.org/gmane.comp.version-control.mercurial.general/36471. I'm not sure why the hg log behaviour changed or even if it is correct, but from the discussion it seems like the command used by this plugin is not correct either. The --follow flag is used to follow changes to a particular file, not to follow the ancestor relationships of changesets. A better command seems to be hg log --rev descendents(5029)::default which directly asks for all the ch
[JIRA] [subversion-plugin] (JENKINS-28525) Subversion plugin doesn't do cleanup
Title: Message Title Pawel Grzegrzolka created an issue Jenkins / JENKINS-28525 Subversion plugin doesn't do cleanup Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 21/May/15 2:32 PM Environment: subversion-plugin: 2.5 Jenkins: 1.609 OS: Windows Server 2013 R2 Labels: plugin svn subversion Priority: Major Reporter: Pawel Grzegrzolka I had an issue quite a few time that checkout has been broken (interrupted during update, etc.) To fix it it's sufficient to do 'svn cleanup'. However subversion-plugin doesn't support it. In case of a broken checkout poll-scm triggers a new build https://repo/svn/project/trunk is at revision 3,211 (changed from 3,210) but SVN doesn't update this repository:
[JIRA] [unity3d-plugin] (JENKINS-23958) Pipe Broken
Title: Message Title Charles Bouchard-Légaré commented on JENKINS-23958 Re: Pipe Broken Here are some logs extracted using the loggers as you suggested. May 21, 2015 9:25:40 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,227) May 21, 2015 9:25:40 AM FINER hudson.remoting.PipeWindow decrease(7806,227)->1048349 May 21, 2015 9:25:40 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,227) May 21, 2015 9:25:40 AM FINER hudson.remoting.PipeWindow increase(7806,227)->1048576 May 21, 2015 9:25:40 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,111) May 21, 2015 9:25:40 AM FINER hudson.remoting.PipeWindow decrease(7806,111)->1048465 May 21, 2015 9:25:40 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,111) May 21, 2015 9:25:40 AM FINER hudson.remoting.PipeWindow increase(7806,111)->1048576 May 21, 2015 9:25:44 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,1395) May 21, 2015 9:25:44 AM FINER hudson.remoting.PipeWindow decrease(7806,1395)->1047181 May 21, 2015 9:25:44 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,1395) May 21, 2015 9:25:44 AM FINER hudson.remoting.PipeWindow increase(7806,1395)->1048576 May 21, 2015 9:25:46 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,39) May 21, 2015 9:25:46 AM FINER hudson.remoting.PipeWindow decrease(7806,39)->1048537 May 21, 2015 9:25:46 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,39) May 21, 2015 9:25:46 AM FINER hudson.remoting.PipeWindow increase(7806,39)->1048576 May 21, 2015 9:25:46 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,358) May 21, 2015 9:25:46 AM FINER hudson.remoting.PipeWindow decrease(7806,358)->1048218 May 21, 2015 9:25:46 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,358) May 21, 2015 9:25:46 AM FINER hudson.remoting.PipeWindow increase(7806,358)->1048576 May 21, 2015 9:25:46 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,776) May 21, 2015 9:25:46 AM FINER hudson.remoting.PipeWindow decrease(7806,776)->1047800 May 21, 2015 9:25:46 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,776) May 21, 2015 9:25:46 AM FINER hudson.remoting.PipeWindow increase(7806,776)->1048576 May 21, 2015 9:25:48 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,39) May 21, 2015 9:25:48 AM FINER hudson.remoting.PipeWindow decrease(7806,39)->1048537 May 21, 2015 9:25:48 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,39) May 21, 2015 9:25:48 AM FINER hudson.remoting.PipeWindow increase(7806,39)->1048576 May 21, 2015 9:25:48 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,352) May 21, 2015 9:25:48 AM FINER hudson.remoting.PipeWindow decrease(7806,352)->1048224 May 21, 2015 9:25:48 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,352) May 21, 2015 9:25:48 AM FINER hudson.remoting.PipeWindow increase(7806,352)->1048576 May 21, 2015 9:25:50 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,390) May 21, 2015 9:25:50 AM FINER hudson.remoting.PipeWindow decrease(7806,390)->1048186 May 21, 2015 9:25:50 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,390) May 21, 2015 9:25:50 AM FINER hudson.remoting.PipeWindow increase(7806,390)->1048576 May 21, 2015 9:25:50 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,388) May 21, 2015 9:25:50 AM FINER hudson.remoting.PipeWindow decrease(7806,388)->1048188 May 21, 2015 9:25:50 AM FINE hudson.remoting.Channel Received ProxyOutputStream.Ack(7806,388) May 21, 2015 9:25:50 AM FINER hudson.remoting.PipeWindow increase(7806,388)->1048576 May 21, 2015 9:25:50 AM FINE hudson.remoting.Channel Send Pipe.Chunk(7806,388) May 21, 2015 9:25:50 AM FINER hudson.remoting.PipeWindow decrease(7806,388)->1048188
[JIRA] [build-flow-plugin] (JENKINS-20843) build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace
Title: Message Title Philipp Strobel commented on JENKINS-20843 Re: build flow plugin does not properly initialize workspace but supports options (SCM) that require a workspace build-flow-plugin 0.17 does not prepare the workspace after SCM checkout. The workspace stays empty. I use the SCM to check for changes on the SCM and to trigger a new Job-Run. However, since the workspace is always empty, each time the SCM is checked for changes it will trigger a new Job-Run. 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] [prioritysorter-plugin] (JENKINS-22267) Upgrade to advanced mode is somehow not persisted to disk
Title: Message Title Julien Carsique commented on JENKINS-22267 Re: Upgrade to advanced mode is somehow not persisted to disk Same issue with Jenkins 1.590 and Priority Sorter 2.9. I was not yet able to determine when it happens, nor why. I submitted JENKINS-28129 to get change history on the Priority Sorter configuration files... I've set an absolute priority up to 10 and created two JobGroups (one based on regexp, one based on view). On disk, I can see 7 jobs with priority >100, obviously not updated. I also found 3 jobs templates setting similar legacy values. Maybe that could be the cause of the issue? What happens when a job is created with a legacy priority value after migration from legacy to absolute? After manual fix of the templates job, I now have: 267 jobs with -2147483647. What means that value? Equivalent to "unset"? 208 jobs with -1 161 jobs with priority between 1 and 10 as expected. 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] [neoload-jenkins] (JENKINS-28524) The Neoload "Performance Test Result" link does not appear on a successful build although the report is getting created at expected location
Title: Message Title Sayantani Das created an issue Jenkins / JENKINS-28524 The Neoload "Performance Test Result" link does not appear on a successful build although the report is getting created at expected location Issue Type: Bug Assignee: Unassigned Attachments: NeoloadDashboardGraphsAvailable.png, NeoloadPerformanceResultLinkNotAvailable.png, neoload_PostBuildSteps.png Components: neoload-jenkins Created: 21/May/15 1:54 PM Environment: Jenkins 1.612, Neoload plugin v 1.0.1 Labels: plugin performance neoload Priority: Major Reporter: Sayantani Das 1. I have installed the Neoload plugin. 2. Created a build step as below: (Execute Windows Batch Command) "D:\Program Files\NeoLoad 5.0\bi
[JIRA] [jobconfighistory-plugin] (JENKINS-28129) Default exclusions should be more precise
Title: Message Title Julien Carsique resolved as Fixed Resolved in version 2.12. Jenkins / JENKINS-28129 Default exclusions should be more precise Change By: Julien Carsique Status: Open Resolved Assignee: Mirko Friedenhagen Julien Carsique 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] [ec2-plugin] (JENKINS-25385) Jenkins EC2 plugin is not able to launch Windows Slaves in AWS
Title: Message Title Tom FENNELLY commented on JENKINS-25385 Re: Jenkins EC2 plugin is not able to launch Windows Slaves in AWS Hi guys. So is this working or not? I just tried it and just sits there waiting: Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-52-17-36-66.eu-west-1.compute.amazonaws.com(52.17.36.66) with WinRM as Waiting for WinRM to come up. Sleeping 10s. Connecting to ec2-52-17-36-66.eu-west-1.compute.amazonaws.com(52.17.36.66) with WinRM as Waiting for WinRM to come up. Sleeping 10s. 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] [dependency-check-jenkins-plugin] (JENKINS-28395) java.lang.NullPointerException after upgrade to v1.2.11
Title: Message Title Shawn Crain commented on JENKINS-28395 Re: java.lang.NullPointerException after upgrade to v1.2.11 Happening for us as well. Jenkins 1.609 on Windows Server 2008 R2 (x86) 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-28523) AD authentication for trusted domain users
Title: Message Title Ankan Saha created an issue Jenkins / JENKINS-28523 AD authentication for trusted domain users Issue Type: Improvement Assignee: Unassigned Components: active-directory-plugin Created: 21/May/15 1:10 PM Environment: Windows 2008, Windows 2003 or all windows Platform Jenkins version 1.598 Active Directory Plugin version 1.39 Priority: Minor Reporter: Ankan Saha In Linux when using Active Directory Plugin I get options for Domain,Domain Controller and Even Bind User and passwd where I specified a common account which will be used to search the account for user to login. In windows I do not get option to set Bind user and passwd. Only Domain name and Domain Controller. As a result I cannot authenticate to Jenkins through Active Directory. The Windows uses the default domain as per your Wiki document. However we use trusted domain for our setup. How can I get the BindUser and Bind Passwd setting which is essential to authenticate for trusted domain The Jenkins server is in one domain but we are authenticating account from another domain which is a trusted domain for the server
[JIRA] [performance-plugin] (JENKINS-28426) JMeterCSV always reports 100% 0f errors
Title: Message Title
Mayank Saini edited a comment on JENKINS-28426
Re: JMeterCSV always reports 100% 0f errors
I think the issue is with the constructor of JMeterCsvParser.I checked the option skipFirstLine in jenkins and print field names is also set to true in jmeter.properties file.In jtl file field name timeStamp is written with capital S while in the constructor if condition is applied with smaller sif ("timestamp".equals(field)) {timestampIdx = i; }I unchecked the option and set print field names to false in jmeter.properties everything works fine
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-28426) JMeterCSV always reports 100% 0f errors
Title: Message Title
Mayank Saini commented on JENKINS-28426
Re: JMeterCSV always reports 100% 0f errors
I think the issue is with the constructor of JMeterCsvParser.I checked the option skipFirstLine in jenkins and print field names is also set to true in jmeter.properties file.
In jtl file field name timeStamp is written with capital S while in the constructor if condition is applied with smaller s if ("timestamp".equals(field)) { timestampIdx = i; }
I unchecked the option and set print field names to false everything works fine
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] [perforce-plugin] (JENKINS-28522) masked variable in p4 passwd causes labelling problem
Title: Message Title
Ankan Saha created an issue
Jenkins / JENKINS-28522
masked variable in p4 passwd causes labelling problem
Issue Type:
Bug
Assignee:
Rob Petti
Components:
perforce-plugin
Created:
21/May/15 12:21 PM
Environment:
Jenkins version 1.598 Perforce Plugin version - 1.3.31 and 1.3.34 Mask Passwords Plugin - 2.7.2 OS - Windows2008R2 x64, Ubuntu details are NAME="Ubuntu" VERSION="12.04.5 LTS, Precise Pangolin" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu precise (12.04.5 LTS)" VERSION_ID="12.04"
Priority:
Minor
Reporter:
Ankan Saha
When we are using masked plugin with Perforce plugin 1.3.31 or 1.3.34 though the sync happens on the common variable labeling files. I define a variable P4USR, P4PWD P4PWD is masked passwd defined in Global Configuration and in Build job we enable the mask plugin checkbox. The sync happens properly but the labeling fails Labelling Build in Perforce using $ {JOB_NAME}
_$ {BUILD_ID}
16:00:11 <$ {P4PWD}>: Found unresolved macro at '${P4PWD}
' 16:00:11 Build step 'Create or Update Label in Perforce' marked build as failure
However instead of P4PWD if I use unmasked variables there is no problem. I wanted to use the Mask Plugin and majority of jobs are configured
[JIRA] [core] (JENKINS-19939) Discard Old Builds I/O Performance Issue
Title: Message Title Tomasz Śniatowski commented on JENKINS-19939 Re: Discard Old Builds I/O Performance Issue Hi, I'm hoping this bug can be revisited. We just spent an unpleasant amount of time trying to figure out why finished builds sometimes seem stuck on a spinner for a random amount of time, turns out it's often the discard old builds step. Some sort of info in the log info be very welcome. It's not very user friendly when jobs are stuck and it's not obvious what's going on. Some other plugins that do work after a build completes, such as "Calculation of disk usage of workspace", do log the time they took. I think this plugin should do so as well. 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] [xfpanel-plugin] (JENKINS-19044) Would like to have a third column of jobs as an option in the eXtreme Feedback panel
Title: Message Title Tomasz Bech assigned an issue to Tomasz Bech Jenkins / JENKINS-19044 Would like to have a third column of jobs as an option in the eXtreme Feedback panel Change By: Tomasz Bech Assignee: Julien RENAUT Tomasz Bech 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] [_test] (JENKINS-28521) Poll SCM
Title: Message Title
Tavant Grubhub created an issue
Jenkins / JENKINS-28521
Poll SCM
Issue Type:
Task
Assignee:
Oleg Nenashev
Components:
_test
Created:
21/May/15 11:48 AM
Priority:
Minor
Reporter:
Tavant Grubhub
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.triggers.SCMTrigger from {"scmpoll_spec":"H/5","ignorePostCommitHooks":false}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hu
