[JIRA] [email-ext-template] (JENKINS-23866) Templates are not saved to disk after an edit
thomas olsen updated JENKINS-23866 Templates are not saved to disk after an edit Change By: thomas olsen (18/Jul/14 6:53 AM) Description: I have created a template and saved it. So far all good. Then I edit it and the changes are kept in memory but not saved to disk and when I have to force a restart it starts up with the initial version of the template.The current work around is to open the file in a text editor and edit the template in JENKINS_HOME.OS: Windows Server 2008 Service pack 1 - its run it runs as a servicejenkins: 1.570Email Extension Plugin: 2.38.1Email Extension Template Plugin: 0.2And let me know if you need any additional information (This is the first time i have left the web interface so I have most likely missed to attach some log files but have not been able to locate any that seems to contain information regarding the plugin) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-template] (JENKINS-23866) Templates are not saved to disk after an edit
thomas olsen created JENKINS-23866 Templates are not saved to disk after an edit Issue Type: Bug Assignee: Alex Earl Components: email-ext-template, emailext-template Created: 18/Jul/14 6:49 AM Description: I have created a template and saved it. So far all good. Then I edit it and the changes are kept in memory but not saved to disk and when I have to force a restart it starts up with the initial version of the template. The current work around is to open the file in a text editor and edit the template in JENKINS_HOME. OS: Windows Server 2008 Service pack 1 - its run as a service jenkins: 1.570 Email Extension Plugin: 2.38.1 Email Extension Template Plugin: 0.2 And let me know if you need any additional information (This is the first time i have left the web interface so I have most likely missed to attach some log files but have not been able to locate any that seems to contain information regarding the plugin) Project: Jenkins Priority: Major Reporter: thomas olsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23435) Job scheduled with 'H' breaks with Invalid input expecting EOF
Stefan Brausch updated JENKINS-23435 Job scheduled with 'H' breaks with Invalid input expecting EOF Change By: Stefan Brausch (18/Jul/14 6:25 AM) Component/s: core Component/s: periodic-reincarnation This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23435) Job scheduled with 'H' breaks with Invalid input expecting EOF
Stefan Brausch commented on JENKINS-23435 Job scheduled with 'H' breaks with Invalid input expecting EOF Wrong component. Set it from periodic-reincarnation to core. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [periodic-reincarnation] (JENKINS-22132) Ratchet back PeriodicReincarnation logging or run periodicity
SCM/JIRA link daemon resolved JENKINS-22132 as Fixed Ratchet back PeriodicReincarnation logging or run periodicity Change By: SCM/JIRA link daemon (18/Jul/14 6:19 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [periodic-reincarnation] (JENKINS-22132) Ratchet back PeriodicReincarnation logging or run periodicity
SCM/JIRA link daemon commented on JENKINS-22132 Ratchet back PeriodicReincarnation logging or run periodicity Code changed in jenkins User: Stefan Brausch Path: pom.xml src/main/java/org/jenkinsci/plugins/periodicreincarnation/PeriodicReincarnation.java http://jenkins-ci.org/commit/periodic-reincarnation-plugin/808198ab360b31dbcd44ce03a071970ec3763078 Log: [FIXED JENKINS-22132] Remove spam entries from log file This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [periodic-reincarnation] (JENKINS-22132) Ratchet back PeriodicReincarnation logging or run periodicity
Stefan Brausch assigned JENKINS-22132 to Stefan Brausch Ratchet back PeriodicReincarnation logging or run periodicity Change By: Stefan Brausch (18/Jul/14 6:18 AM) Assignee: Stefan Brausch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant] (JENKINS-23865) Jenkins Jobs Hanging while running junit tests
Easwar Muthu created JENKINS-23865 Jenkins Jobs Hanging while running junit tests Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: ant Created: 18/Jul/14 6:05 AM Description: When jobs runs its building java classes and test classes. Test started running. After 19-20 min, its stuck always. When comment particular class, it's stuck again in another test class at same 19-20 min time. Due Date: 21/Jul/14 12:00 AM Environment: Jboss server/Ant build/Junit test Project: Jenkins Priority: Major Reporter: Easwar Muthu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23800) Xvfb won't activate
Archimedes Trajano closed JENKINS-23800 as Not A Defect Xvfb won't activate Change By: Archimedes Trajano (18/Jul/14 4:29 AM) Status: Open Closed Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23800) Xvfb won't activate
Archimedes Trajano commented on JENKINS-23800 Xvfb won't activate Can't really figure out what is causing the RebuildValidator, so i just deleted my Jenkins installation and started over and xfvb is working now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23864) Environment variables are not set in init script
Craig Ringer edited a comment on JENKINS-23864 Environment variables are not set in init script It looks like the best solution might be to use hudson.Launcher on a VirtualChannel set up by the ec2-plugin and use hudson.EnvVars . I think that might make Windows command launching work too, though that's not much good if the slave agent can't be started. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23864) Environment variables are not set in init script
Craig Ringer commented on JENKINS-23864 Environment variables are not set in init script It looks like the best solution might be to use hudson.Launcher on a VirtualChannel set up by the ec2-plugin. I think that might make Windows command launching work too, though that's not much good if the slave agent can't be started. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23864) Environment variables are not set in init script
Craig Ringer commented on JENKINS-23864 Environment variables are not set in init script It looks like initScript execution is done by ssh/EC2UnixLauncher.java in launch(...). So we'd need to inject slave and global environment variables on the remote end of the SSH call there. The Trilead ssh wrapper doesn't seem to support setting env vars, so the simplest option would be to prepend them to the init script. I could add that part fairly trivially. My problem is that I have no idea how to get the environment variables configured on a node. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23864) Environment variables are not set in init script
Craig Ringer edited a comment on JENKINS-23864 Environment variables are not set in init script It looks like initScript execution is done by ssh/EC2UnixLauncher.java in launch(...). So we'd need to inject slave and global environment variables on the remote end of the SSH call there. The Trilead ssh wrapper doesn't seem to support setting env vars, so the simplest option would be to prepend them to the init script. I could add that part fairly trivially. My problem is that I have no idea how to get the environment variables configured on a node, or get the global environment vars from the Jenkins configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23864) Environment variables are not set in init script
Craig Ringer
updated JENKINS-23864
Environment variables are not set in init script
Change By:
Craig Ringer
(18/Jul/14 2:58 AM)
Description:
It looks like init-scripts don't get the environment variables defined for a node, or global environment variables defined in the main Configure Jenkins page, injected. At least for EC2 nodes.The environment variables are present when running jobs, but not when running init scripts. Even when those environment variables are shown in the "Enviroment Variables" list under "System Information" for a node, an init script that has a line like:{code}env > /tmp/init-environ{code}will print an environment that doesn't include them, and shell substitutions won't use them.In case they were set but not exported I tested with:{code}set > /tmp/set-environ{code}but the vars weren't present there either.This makes it harder to parameterize init scripts.
The environment that was set was:{code}SHELL=/bin/bashTERM=dumbUSER=rootSUDO_USER=rootSUDO_UID=0USERNAME=rootMAIL=/var/mail/rootPATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/binPWD=/home/adminDEBIAN_PRIORITY=criticalSHLVL=1SUDO_COMMAND=/bin/bashHOME=/rootLOGNAME=rootDEBIAN_FRONTEND=noninteractiveSUDO_GID=0_=/usr/bin/env{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23864) Environment variables are not set in init script
Craig Ringer
updated JENKINS-23864
Environment variables are not set in init script
Change By:
Craig Ringer
(18/Jul/14 2:59 AM)
Labels:
ec2 environment environment-variables init-script
Description:
It looks like init-scripts don't get the environment variables defined for a node, or global environment variables defined in the main Configure Jenkins page, injected. At least for EC2 nodes.The environment variables are present when running jobs, but not when running init scripts. Even when those environment variables are shown in the "Enviroment Variables" list under "System Information" for a node, an init script that has a line like:{code}env > /tmp/init-environ{code}will print an environment that doesn't include them, and shell substitutions won't use them.In case they were set but not exported I tested with:{code}set > /tmp/set-environ{code}but the vars weren't present there either.This makes it harder to parameterize init scripts.The environment that was set was:{code}SHELL=/bin/bashTERM=dumbUSER=rootSUDO_USER=
root
admin
SUDO_UID=
0
1000
USERNAME=rootMAIL=/var/mail/rootPATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/binPWD=/home/admin
DEBIAN_PRIORITY=critical
SHLVL=1SUDO_COMMAND=/
bin
tmp
/
bash
init.sh
HOME=/rootLOGNAME=root
DEBIAN_FRONTEND=noninteractive
SUDO_GID=
0
1000
_=/usr/bin/env{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23864) Environment variables are not set in init script
Craig Ringer
updated JENKINS-23864
Environment variables are not set in init script
Change By:
Craig Ringer
(18/Jul/14 2:57 AM)
Description:
It looks like init-scripts don't get the environment variables defined for a node, or global environment variables defined in the main Configure Jenkins page, injected.
At least for EC2 nodes.
The environment variables are present when running jobs, but not when running init scripts. Even when those environment variables are shown in the "Enviroment Variables" list under "System Information" for a node, an init script that has a line like:{code}env > /tmp/init-environ{code}will print an environment that doesn't include them, and shell substitutions won't use them.In case they were set but not exported I tested with:{code}set > /tmp/set-environ{code}but the vars weren't present there either.This makes it harder to parameterize init scripts.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23864) Environment variables are not set in init script
Craig Ringer created JENKINS-23864 Environment variables are not set in init script Issue Type: Bug Assignee: Francis Upton Components: ec2, slave-setup Created: 18/Jul/14 2:57 AM Description: It looks like init-scripts don't get the environment variables defined for a node, or global environment variables defined in the main Configure Jenkins page, injected. The environment variables are present when running jobs, but not when running init scripts. Even when those environment variables are shown in the "Enviroment Variables" list under "System Information" for a node, an init script that has a line like: env > /tmp/init-environ will print an environment that doesn't include them, and shell substitutions won't use them. In case they were set but not exported I tested with: set > /tmp/set-environ but the vars weren't present there either. This makes it harder to parameterize init scripts. Environment: EC2-plugin 1.23, Jenkins 1.572 Project: Jenkins Priority: Minor Reporter: Craig Ringer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23850) PATCH: EC2-plugin always starting new slaves instead of restarting existing
Craig Ringer updated JENKINS-23850 PATCH: EC2-plugin always starting new slaves instead of restarting existing Change By: Craig Ringer (18/Jul/14 2:28 AM) Summary: PATCH: EC2-plugin always starting new slaves instead of restarting existing This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23787) EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline"
Craig Ringer commented on JENKINS-23787 EC2-plugin not spooling up stopped nodes - "still in the queue ... all nodes of label ... are offline" I do have an instance cap, but neither the per-node-type nor global instance caps are being reached. It's an issue with restarting existing stoppped nodes, not with starting new ones. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-23863) HTTP requests hang indefinitely after some time running
André Arko created JENKINS-23863 HTTP requests hang indefinitely after some time running Issue Type: Bug Assignee: Unassigned Attachments: jmap-heap.txt, jstack-F.txt Components: gui Created: 18/Jul/14 12:37 AM Description: Jenkins 1.570 (and many previous versions) stop responding to any HTTP requests after running for somewhere between 5 minutes and an hour. Increasing the heap size didn't seem to help, and jmap -heap seems to indicate that there is enough memory available. jstack -F (jstack failed without -F) seems to indicate that all the threads are blocked, but I can't tell why Jenkins doesn't respond to HTTP requests, or even if there is anything I can do to fix it other than restarting the entire Java VM. Environment: > uname -a SunOS jenkins101.demo 5.11 joyent_20131218T184706Z i86pc i386 i86pc Solaris Project: Jenkins Labels: gui jenkins Priority: Major Reporter: André Arko This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Daniel Beck commented on JENKINS-21335 Forward slashes in a File Parameter's file location cause parameter download links to break Eric: Does org.apache.tomcat.util.buf.UDecoder.ALLOW_ENCODED_SLASH help? http://permalink.gmane.org/gmane.comp.jakarta.tomcat.user/157941 Further reference: http://tomcat.apache.org/security-5.html#Fixed_in_Apache_Tomcat_5.5.22,_5.0.SVN This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23850) EC2-plugin always starting new slaves instead of restarting existing
Andrew Coulton started work on JENKINS-23850 EC2-plugin always starting new slaves instead of restarting existing Change By: Andrew Coulton (17/Jul/14 8:56 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23850) EC2-plugin always starting new slaves instead of restarting existing
Andrew Coulton stopped work on JENKINS-23850 EC2-plugin always starting new slaves instead of restarting existing Change By: Andrew Coulton (17/Jul/14 8:54 PM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23850) EC2-plugin always starting new slaves instead of restarting existing
Andrew Coulton commented on JENKINS-23850 EC2-plugin always starting new slaves instead of restarting existing I've identified that this happens when using the eu-west-1 region, because the describeInstances API does not return results when used with the group-name filter. The same behaviour has been observed at https://github.com/aws/aws-sdk-java/issues/213 and I have opened a discussion on the AWS forum. Per the EC2 API docs the instance.group-name filter is functionally identical, and I have found that this query does produce expected results in eu-west-1 and elsewhere. I've submitted a 1-line pull request to switch to the instance.group-name filter at https://github.com/jenkinsci/ec2-plugin/pull/99 which I think will resolve this issue ahead of any response/resolution by the AWS team. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23850) EC2-plugin always starting new slaves instead of restarting existing
Andrew Coulton started work on JENKINS-23850 EC2-plugin always starting new slaves instead of restarting existing Change By: Andrew Coulton (17/Jul/14 8:54 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
Steven Christou commented on JENKINS-22641 Jenkins no longer kills running processes after job fails This looks to be a regression in commons-io library. I logged IO-453 to track the changes for the commons-io library. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22397) A Trigger should be able to be a DependencyDeclarer
SCM/JIRA link daemon commented on JENKINS-22397 A Trigger should be able to be a DependencyDeclarer Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/maven/MavenModuleSet.java http://jenkins-ci.org/commit/maven-plugin/9ac66ee95d401330f99e1c0fd1fecc35e4c61227 Log: [FIXED JENKINS-23686] Fix of JENKINS-22397 not automatically available to overriders of buildDependencyGraph unless they were using 1.558+ and calling super. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-23686) Trigger "Build after other projects" does not work
SCM/JIRA link daemon commented on JENKINS-23686 Trigger "Build after other projects" does not work Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/maven/MavenModuleSet.java http://jenkins-ci.org/commit/maven-plugin/9ac66ee95d401330f99e1c0fd1fecc35e4c61227 Log: [FIXED JENKINS-23686] Fix of JENKINS-22397 not automatically available to overriders of buildDependencyGraph unless they were using 1.558+ and calling super. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21335) Forward slashes in a File Parameter's file location cause parameter download links to break
Eric Anker commented on JENKINS-21335 Forward slashes in a File Parameter's file location cause parameter download links to break Sorry for the delay. Thanks for following up. That scenario appears to work! So there's something not right with my fairly stock tomcat instance then? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-23861) Parameterized remote trigger should allow setting parent build status based on downstream build status
Dima Spivak edited a comment on JENKINS-23861 Parameterized remote trigger should allow setting parent build status based on downstream build status It would also be useful for the parameterized remote trigger plugin to set the same environmental variables that the parameterized plugin sets: LAST_TRIGGERED_JOB_NAME="Last project started" TRIGGERED_JOB_NAMES="Comma separated list of all triggered projects" TRIGGERED_BUILD_NUMBER_="Last build number triggered" TRIGGERED_BUILD_NUMBERS_="Comma separated list of build numbers triggered" TRIGGERED_BUILD_RESULT_="Last triggered build result of project" TRIGGERED_BUILD_RESULT_RUN= "Result of triggered build for build number" TRIGGERED_BUILD_RUN_COUNT_= "Number of builds triggered for the project" (Realized this has already filed as JENKINS-22384.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-23793) New buttons do not do anything; Leads to credentials not able to be added.
Peter Tee commented on JENKINS-23793 New buttons do not do anything; Leads to credentials not able to be added. Works for me, thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-22997) Use bars instead of dots in build history
Daniel Beck commented on JENKINS-22997 Use bars instead of dots in build history Actually, the build history does show duration for me. Could you provide a screenshot and highlight what you mean specifically? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-18524) Too many open files caused Jenkins crashed
Daniel Beck commented on JENKINS-18524 Too many open files caused Jenkins crashed Are you using the Jenkins CLI (e.g. JENKINS-23572)? Does this issue also occur on current Jenkins versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-23860) allow for custom flags to be passed to git
Mark Waite commented on JENKINS-23860 allow for custom flags to be passed to git I think the request is infeasible, unless we provide a "command line arguments" field for every git command we invoke, in every context where it is invoked. For example, the current git commands used by the plugin include: --version branch checkout clone config describe fetch init log merge notes rev-parse submodule add submodule init submodule sync tag Those commands are used in specific contexts, with some used in multiple contexts. I don't see how we could represent a user interface to the user which would describe the location of the usage, without fully describing the details of that usage so that they knew the context. The user interface to allow command line control of each of those contexts is much more work and much more difficult to explain to users than the current, simplified model. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-23478) Could not find artifact javax.xml:jaxrpc-api:jar:1.1.3 in central
Daniel Beck resolved JENKINS-23478 as Not A Defect Could not find artifact javax.xml:jaxrpc-api:jar:1.1.3 in central Report is not a Jenkins issue. Change By: Daniel Beck (17/Jul/14 8:08 PM) Status: Open Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-23686) Trigger "Build after other projects" does not work
Jesse Glick assigned JENKINS-23686 to Jesse Glick Trigger "Build after other projects" does not work Change By: Jesse Glick (17/Jul/14 8:08 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-23686) Trigger "Build after other projects" does not work
Jesse Glick started work on JENKINS-23686 Trigger "Build after other projects" does not work Change By: Jesse Glick (17/Jul/14 8:08 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-23852) slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed"
Daniel Beck updated JENKINS-23852 slave builds repeatedly broken by "hudson.remoting.ChannelClosedException: channel is already closed" Change By: Daniel Beck (17/Jul/14 8:05 PM) Labels: connection exception jenkins slave remoting This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23829) Layout: Job history may overlap main job status
Daniel Beck updated JENKINS-23829 Layout: Job history may overlap main job status Seems to affect builds list with build name set to something long. Change By: Daniel Beck (17/Jul/14 8:04 PM) Assignee: Tom FENNELLY Priority: Major Minor Component/s: core Component/s: ui-changes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ui-changes] (JENKINS-23837) logout links style hard to read
Daniel Beck resolved JENKINS-23837 as Duplicate logout links style hard to read Fix is scheduled for 1.574. Change By: Daniel Beck (17/Jul/14 8:03 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
Jesse Glick updated JENKINS-22641 Jenkins no longer kills running processes after job fails Change By: Jesse Glick (17/Jul/14 7:37 PM) Labels: lts-candidate regression This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
Jesse Glick started work on JENKINS-22641 Jenkins no longer kills running processes after job fails Change By: Jesse Glick (17/Jul/14 7:37 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails
Jesse Glick updated JENKINS-22641 Jenkins no longer kills running processes after job fails Change By: Jesse Glick (17/Jul/14 7:38 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-status] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Patricia Wright commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted Looks like a regression, or sporadic issue. I'm experiencing this now. In our environment, ubuntu master, windows slaves. Jenkins: 1.572 slave.jar version: 2.43 (the version on the master) java.io.IOException: NioChannelHub is not currently running at org.jenkinsci.remoting.nio.NioChannelHub$1.makeTransport(NioChannelHub.java:446) at hudson.remoting.ChannelBuilder.negotiate(ChannelBuilder.java:220) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:149) at hudson.remoting.ChannelBuilder.build(ChannelBuilder.java:159) at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:36) at org.jenkinsci.remoting.nio.NioChannelBuilder.build(NioChannelBuilder.java:52) at jenkins.slaves.JnlpSlaveAgentProtocol$Handler.jnlpConnect(JnlpSlaveAgentProtocol.java:120) at jenkins.slaves.DefaultJnlpSlaveReceiver.handle(DefaultJnlpSlaveReceiver.java:63) at jenkins.slaves.JnlpSlaveAgentProtocol2$Handler2.run(JnlpSlaveAgentProtocol2.java:57) at jenkins.slaves.JnlpSlaveAgentProtocol2.handle(JnlpSlaveAgentProtocol2.java:31) at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:157) In our environment slaves get disconnected after a suite of tests complete (and revert to a clean vSphere snapshot) and then reconnect. It runs fine for a while, with many disconnects/reconnects. Then starts tossing these exceptions and nothing can connect until a restart. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-23813) Need to run Perforce command before polling
Haiqing Zhang commented on JENKINS-23813 Need to run Perforce command before polling thanks. it's a better to have feature. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Tom FENNELLY resolved JENKINS-23779 as Fixed Layout in 1.572 is broken in IE9 Change By: Tom FENNELLY (17/Jul/14 7:08 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Tom FENNELLY commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Thanks Daniel. Believe it or not ... I've been told there are a few CloudBees customers still using IE8 as a "corporate standard" I pushed some tweaks for IE wrt compatibility mode (de6ea1a). Two parts to it... 1. Forcing the Browser Compatibility mode from within the document (via a tag). 2. Warning IE users if the Document Compatibility mode is set to something other than the default for that browser version. Hopefully that will work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-11600) Implement Entry functions for email-ext support
SCM/JIRA link daemon commented on JENKINS-11600 Implement Entry functions for email-ext support Code changed in jenkins User: Paul Tankard Path: src/main/java/hudson/plugins/perforce/PerforceChangeLogEntry.java http://jenkins-ci.org/commit/perforce-plugin/fda9b707c2fcc4afff0a37c6d83aa23451b6d3ca Log: Fix for JENKINS-11600, email-ext now queries getTimestamp and getCommitId This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-11600) Implement Entry functions for email-ext support
SCM/JIRA link daemon commented on JENKINS-11600 Implement Entry functions for email-ext support Code changed in jenkins User: Rob Petti Path: src/main/java/hudson/plugins/perforce/PerforceChangeLogEntry.java http://jenkins-ci.org/commit/perforce-plugin/e49e9cb874d9536210aa9c90119c96ce50a1ad82 Log: Merge pull request #49 from HexTank/master Fix for JENKINS-11600, email-ext now queries getTimestamp and getCommite... Compare: https://github.com/jenkinsci/perforce-plugin/compare/2da2bf91851f...e49e9cb874d9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ui-changes] (JENKINS-23862) when viewing console output, way too much screen real estate wasted
boris ivan created JENKINS-23862 when viewing console output, way too much screen real estate wasted Issue Type: Improvement Affects Versions: current Assignee: Unassigned Attachments: jenkins-console.jpg Components: ui-changes Created: 17/Jul/14 6:33 PM Description: When viewing console output for any build, somewhere between 1/3 - 1/4 of the browser screen is wasted, especially when scrolling down. Specifically, the menu selections on the upper left side of the screen: Back To Project Status Changes Console Output (etc) — there is a very large amount of space dedicated to these options. And it gets worse: when we scroll down to review more of the console output, the menu options are gone (scrolled away), but the amount of space dedicated to them still remains. The net effect is that somewhere between 1/3 and 1/4 of the screen (the left hand side) is blank and unused. This looks poor (especially when the menu items aren't even there because we've scrolled down) but is truly a hindrance when trying to review large console outputs. I'd love to see a 'collapse' icon or any other kind of solution that would allow that menu to collapse to a small icon or relocate to the top center of the window or any other solution that ends up not producing empty blank space. It seems that in the most recent release (1.572), the behavior changed somewhat, but it doesn't really fix it. It seems that now if we make the browser window narrower, the menu items will jump to the top and stop indenting the entire left portion of the window. But since this only happens when we narrow the window, this doesn't help us view large console output, since we want to make that window wider in the first place.. Please excuse the ugly blackout scribbling on the attachment. But note all the unused space on the left Environment: any Project: Jenkins Priority: Major Reporter: boris ivan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-23861) Parameterized remote trigger should allow setting parent build status based on downstream build status
Dima Spivak edited a comment on JENKINS-23861 Parameterized remote trigger should allow setting parent build status based on downstream build status It would also be useful for the parameterized remote trigger plugin to set the same environmental variables that the parameterized plugin sets: LAST_TRIGGERED_JOB_NAME="Last project started" TRIGGERED_JOB_NAMES="Comma separated list of all triggered projects" TRIGGERED_BUILD_NUMBER_="Last build number triggered" TRIGGERED_BUILD_NUMBERS_="Comma separated list of build numbers triggered" TRIGGERED_BUILD_RESULT_="Last triggered build result of project" TRIGGERED_BUILD_RESULT_RUN= "Result of triggered build for build number" TRIGGERED_BUILD_RUN_COUNT_= "Number of builds triggered for the project" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-23861) Parameterized remote trigger should allow setting parent build status based on downstream build status
Dima Spivak commented on JENKINS-23861 Parameterized remote trigger should allow setting parent build status based on downstream build status It would also be useful for the parameterized remote trigger plugin to set the same environmental variables that the parameterized plugin sets: -LAST_TRIGGERED_JOB_NAME="Last project started" -TRIGGERED_JOB_NAMES="Comma separated list of all triggered projects" -TRIGGERED_BUILD_NUMBER_="Last build number triggered" -TRIGGERED_BUILD_NUMBERS_="Comma separated list of build numbers triggered" -TRIGGERED_BUILD_RESULT_="Last triggered build result of project" -TRIGGERED_BUILD_RESULT_RUN= "Result of triggered build for build number" -TRIGGERED_BUILD_RUN_COUNT_= "Number of builds triggered for the project" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger] (JENKINS-23861) Parameterized remote trigger should allow setting parent build status based on downstream build status
abayer created JENKINS-23861 Parameterized remote trigger should allow setting parent build status based on downstream build status Issue Type: Improvement Assignee: abayer Components: parameterized-remote-trigger Created: 17/Jul/14 5:52 PM Description: Basically it should have the same functionality as you get from the parameterized trigger plugin when blocking on the downstream build. Project: Jenkins Priority: Major Reporter: abayer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-23858) SLF4J StaticLoggerBinder class not found
ANIL Bonu started work on JENKINS-23858 SLF4J StaticLoggerBinder class not found Change By: ANIL Bonu (17/Jul/14 5:32 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-23858) SLF4J StaticLoggerBinder class not found
ANIL Bonu stopped work on JENKINS-23858 SLF4J StaticLoggerBinder class not found Change By: ANIL Bonu (17/Jul/14 5:32 PM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-23813) Need to run Perforce command before polling
Rob Petti assigned JENKINS-23813 to Haiqing Zhang Need to run Perforce command before polling Change By: Rob Petti (17/Jul/14 5:26 PM) Assignee: Rob Petti Haiqing Zhang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-23813) Need to run Perforce command before polling
Rob Petti commented on JENKINS-23813 Need to run Perforce command before polling You cannot run any command before p4 poll. I need the error message so we can have it run automatically. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-23813) Need to run Perforce command before polling
Rob Petti updated JENKINS-23813 Need to run Perforce command before polling Lowering priority since there's a workaround available. Change By: Rob Petti (17/Jul/14 5:26 PM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-23813) Need to run Perforce command before polling
Haiqing Zhang commented on JENKINS-23813 Need to run Perforce command before polling Actually the command need to run is "p4 trust -y -f" as IT changed the phrases. I have manually run the command on each node so unfortunately i don't have the error message anymore. I'd like to know if i can run any command before the p4 poll. thanks, hq This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-23860) allow for custom flags to be passed to git
Aaron Simmons created JENKINS-23860 allow for custom flags to be passed to git Issue Type: New Feature Assignee: Nicolas De Loof Components: git-client Created: 17/Jul/14 5:06 PM Description: There are so many flags that can be passed to git, it seems impossible for the git plugin to keep up. For example, see JENKINS-21248 which asks to get shallow clone support for submodules (e.g., passing --depth 1 for submodule inits). Who knows when this ticket is going to be addressed? If we just had a text area where we could input custom flags to the git command, we could bypass this need for the plugin to represent every flag in git with a checkbox. Project: Jenkins Labels: plugin git git-plugin git-client Priority: Major Reporter: Aaron Simmons This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21248) Add shallow update init for submodule
Aaron Simmons commented on JENKINS-21248 Add shallow update init for submodule It seems Muranaka's fix for this was rejected . Can we get this feature implemented? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Tom FENNELLY commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Cool. Thanks guys. However, I'm thinking there are going to be issues with IE8 One bridge at a time This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Daniel Beck commented on JENKINS-23779 Layout in 1.572 is broken in IE9 IE 8 is is no longer supported, and (with the exception of Server 2003, not a typical client OS) there's no still supported OS that cannot run a newer version. IMO you'd just waste your time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand] (JENKINS-23859) extraneous tests showing up in job report
James Parker created JENKINS-23859 extraneous tests showing up in job report Issue Type: Bug Assignee: Kohsuke Kawaguchi Attachments: Selection_002.png Components: sauce-ondemand Created: 17/Jul/14 4:40 PM Description: After running tests and console logging sauce job ids for sauce plugin seemingly random additional sauce job ids from jobs that have run in the past will job up in the job report. Environment: Windows OS Project: Jenkins Priority: Major Reporter: James Parker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit] (JENKINS-23858) SLF4J StaticLoggerBinder class not found
ANIL Bonu created JENKINS-23858 SLF4J StaticLoggerBinder class not found Issue Type: Bug Assignee: Unassigned Components: junit Created: 17/Jul/14 4:12 PM Description: Hi, I have an ant script related to my project to build and run the JUNITs. I am able to succesfully ran the ant script from the Command prompt and the all the testcases got executed. But when integrate this with Jenkins I am getting the NoClassDefinitionFound for 'SL4J' - java.lang.NoClassDefFoundError: org.slf4j.impl.StaticLoggerBinder. I have all the required jars in the class path. Version of Jenkins : 1.7 Project: Jenkins Priority: Blocker Reporter: ANIL Bonu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Steve Mitchell commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Hi, looks good to me now I've changed the doc mode. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-oauth] (JENKINS-20845) Github Authorization Settings, users in "Participant in Organization" not given READ
Andrew Langhorn commented on JENKINS-20845 Github Authorization Settings, users in "Participant in Organization" not given READ I experienced a very similar issue this morning. Did anyone find anything else of use? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-23857) Coverage Breakdown by Maven Module
Akos Kozak created JENKINS-23857 Coverage Breakdown by Maven Module Issue Type: Bug Assignee: Ognjen Bubalo Components: jacoco Created: 17/Jul/14 2:49 PM Description: It would be perfect to see the Coverage per Maven module. We got a bigger project with many-many packages. So, it is not perfect, because we are not able to see which module has bad coverage and which not. Project: Jenkins Priority: Major Reporter: Akos Kozak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-23838) Caught exception communicating with perforce. Connect to server failed; check $P4PORTcom.tek42.perforce.PerforceException: Connect to server failed; check $P4PORT
Rob Petti resolved JENKINS-23838 as Not A Defect Caught exception communicating with perforce. Connect to server failed; check $P4PORTcom.tek42.perforce.PerforceException: Connect to server failed; check $P4PORT Change By: Rob Petti (17/Jul/14 2:46 PM) Status: Open Resolved Fix Version/s: current Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plot] (JENKINS-23856) Plots from CSV files do not work with matrix / multi-configuration builds
Sebastian Schuberth created JENKINS-23856 Plots from CSV files do not work with matrix / multi-configuration builds Issue Type: Bug Affects Versions: current Assignee: nidaley Components: plot Created: 17/Jul/14 2:29 PM Description: Plots from CSV files do not seem to work with matrix builds. No matter how I specify the "Data series file", I don't see any plots being generated. It's a bit inconvenient to debug this as the build will not fail if the specified "Data series file" does not exist. There's only a dynamic "tool tip" displayed by Jenkins below the text field if the file does not exist at the time of filling in the "Data series file" field. As an example see the job at [1]. Usually, I would expect the file to be looked up relative to the matrix child workspace. That is, if I have a matrix job with two "FLAVOR"s called "debug" and "release", the child workspaces WRT the parent workspace are at "$PARENT_WORKSPACE/FLAVOR/debug" [2] and "$PARENT_WORKSPACE/FLAVOR/release" [3]. If I now specify "data.csv" as the "Data series file", it should be looked up at "$PARENT_WORKSPACE/FLAVOR/debug/data.csv" and "$PARENT_WORKSPACE/FLAVOR/release/data.csv", respectively. But obviously that's not the way it works as if I just enter "data.csv" I get the aforementioned "tool tip" saying "‘data.csv’ doesn’t match anything, but ‘FLAVOR/debug/data.csv’ does. Perhaps that’s what you mean?". However, entering "FLAVOR/debug/data.csv" also does not work. While it makes the error "tool tip" go away, there still is no plot. Besides that, hard-coding the path that way would not work for the "release" flavor. My guess is that some code parts of the plugin assume "data.csv" to be relative to the parent workspace root, while other code parts assume "data.csv" to be relative to the child workspace root. At least there's some inconsistency. Maybe it makes sense to look at the alternative matrix job implementation at [4] and [5] again to see whether they would work / what they do differently? To double-check against any issues on my side, I've also configured a simple (non-matrix) job at [6] which is working fine. [1] http://mingwgitdevenv.cloudapp.net/view/Playground/job/plot-matrix [2] http://mingwgitdevenv.cloudapp.net/view/Playground/job/plot-matrix/ws/FLAVOR/debug/ [3] http://mingwgitdevenv.cloudapp.net/view/Playground/job/plot-matrix/ws/FLAVOR/release/ [4] https://github.com/jenkinsci/plot-plugin/pull/5 [5] https://github.com/jenkinsci/plot-plugin/pull/6 [6] https://mingwgitdevenv.cloudapp.net/view/Playground/job/plot-simple/ Project: Jenkins Priority: Major Reporter: Sebastian Schuberth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
Jesse Glick resolved JENKINS-21797 as Fixed Subversion-Tagging Plugin can't create tag because of missing credentials 1.17 released. Change By: Jesse Glick (17/Jul/14 2:18 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23800) Xvfb won't activate
Archimedes Trajano commented on JENKINS-23800 Xvfb won't activate Thanks for confirming that it may be a local issue. I will test it out when I get the chance tonight and close this if I am able to get it working. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gui] (JENKINS-23855) Add build step before other step
Maciej Jaros created JENKINS-23855 Add build step before other step Issue Type: New Feature Assignee: Unassigned Components: gui Created: 17/Jul/14 2:13 PM Description: Some of builds have 20 something steps. It's very cumbersome to modify the list if you need to add some step in the middle of the list - you need to scroll down all the way to "Add build step" and then drag the action back to top. So it would be very helpful if above all steps would be a button like "Add build step here". Project: Jenkins Priority: Minor Reporter: Maciej Jaros This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-18588) Git polling builds same branch multiple times when 'Execute concurrent builds if necessary' turned on
Richard van der Hoff commented on JENKINS-18588 Git polling builds same branch multiple times when 'Execute concurrent builds if necessary' turned on See also JENKINS-21464 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-20128) HTTP two-way remoting does not work (jenkins-cli.jar without JNLP)
Nico Mommaerts commented on JENKINS-20128 HTTP two-way remoting does not work (jenkins-cli.jar without JNLP) Same problem on 1.554.3. Is there a separate bug filed or not? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cppcheck] (JENKINS-23247) Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin.
Senthil Nagarajan commented on JENKINS-23247 Display trends graph last 10/20 sucessful/fail builds in CPPcheck plugin. Hi > During From 50 to 337 all builds are failed. yes. > Nope we have configured only 30 builds or 15 days builds alone archiving. > In the trend graph, I would like to view only the recent builds as per I would like to configure. For example, The graph trend shows from 50 to 337 which doesnt required instead of that the graph has to show only the recent 5 or 10 builds say (330 to 337) as per the configurable count. > I used 1.18 version on the same, platform linux, C++. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-21086) jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown
Roman Shiryaev commented on JENKINS-21086 jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown The workaround really works for me too. Thank you so much! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-23854) analysis collector doesn't take the results
nagarjuna sudi reopened JENKINS-23854 analysis collector doesn't take the results Change By: nagarjuna sudi (17/Jul/14 1:20 PM) Resolution: Duplicate Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
George Bloggs commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Tom Good spot. I can confirm the key here appears to be the Document Mode. In the developer toolbar (F12) with Document Mode set to anything other than Internet Explorer 9 Standards, the page renders wrongly. IF the Document Mode is set to Internet Explorer 9 Standards, the page renders correctly regardless of the browser mode. It seems like the Document Mode is the key to rendering correctly in IE9. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-23854) analysis collector doesn't take the results
nagarjuna sudi commented on JENKINS-23854 analysis collector doesn't take the results k i felt these two are different, can you please help to me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-23853) analysis collector doesn't generate the report
Ulli Hafner commented on JENKINS-23853 analysis collector doesn't generate the report You also need to activate the FindBugs and Checkstyle post build actions. Did you miss that? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-23854) analysis collector doesn't take the results
Ulli Hafner resolved JENKINS-23854 as Duplicate analysis collector doesn't take the results Why did you create 2 issues? Change By: Ulli Hafner (17/Jul/14 12:48 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Tom FENNELLY commented on JENKINS-23779 Layout in 1.572 is broken in IE9 Thanks George (Bloggs). I did a bit more testing. We can get around the browser compatibility mode setting via a tag in the document. I also notice (I'm not an IE expert by any means) that IE has a "Document Mode" that can be configured in the dev tools (F11). See http://goo.gl/TJMhSe If this is set to anything other than IE9 standards (as shown in http://goo.gl/TJMhSe) then the page seems to render incorrectly (irrespective of the browser compatibility mode). Please check this setting in your browser and let me know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23779) Layout in 1.572 is broken in IE9
Tom FENNELLY updated JENKINS-23779 Layout in 1.572 is broken in IE9 Change By: Tom FENNELLY (17/Jul/14 12:39 PM) Attachment: Screenshot 2014-07-17 13.35.01.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12998) Allows variable subistution for Job 'Restrict where this project can be run' label expression
Miroslav Nedyalkov commented on JENKINS-12998 Allows variable subistution for Job 'Restrict where this project can be run' label _expression_ Daniel, thanks for the information. I guess we should stick to one of the plugins for the time being This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22547) Git timeout setting does not work for checkout
Mark Waite commented on JENKINS-22547 Git timeout setting does not work for checkout Another work around which may work for some users is to use sparse checkout and only checkout the subtree which is actually used. If the checkout of the subtree you need can be completed in less than 10 minutes, then sparse checkout would be a solution. Add the "Additional Behaviours" - "Sparse Checkout paths", then list the directories needed. The plugin will copy the entire repository, but only checkout the directories specified by the sparse checkout. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported
Jesse Glick assigned JENKINS-22853 to Kohsuke Kawaguchi SEVERE: Trying to unexport an object that's already unexported Change By: Jesse Glick (17/Jul/14 12:02 PM) Assignee: Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-23854) analysis collector doesn't take the results
nagarjuna sudi created JENKINS-23854 analysis collector doesn't take the results Issue Type: Bug Assignee: Ulli Hafner Components: analysis-collector Created: 17/Jul/14 12:02 PM Description: Analysis collector doesn't collect the results generated by analysis core plugins, after the build success it just show an empty graph Project: Jenkins Priority: Major Reporter: nagarjuna sudi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-21959) Dashboard Plug In Links do not work together with Cloudbees Folder Plug In
Aurélien Pupier commented on JENKINS-21959 Dashboard Plug In Links do not work together with Cloudbees Folder Plug In To help further investigation: The faulty link come from dashboard-view-plugin\src\main\resources\hudson\plugins\view\dashboard\core\UnstableJobsPortlet\portlet.jelly l.56 It is using the Util method from dashboard-view-plugin\src\main\resources\hudson\plugins\view\dashboard\jobLink.jelly I suppose that the fix will be similar to what was done for https://issues.jenkins-ci.org/browse/JENKINS-19310 during this commit: https://github.com/jenkinsci/jenkins/commit/ea95434938b2111d8768528823990a78bdc58d3e This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-21959) Dashboard Plug In Links do not work together with Cloudbees Folder Plug In
Aurélien Pupier edited a comment on JENKINS-21959 Dashboard Plug In Links do not work together with Cloudbees Folder Plug In To help further investigation: The faulty link come from https://github.com/jenkinsci/dashboard-view-plugin/blob/master/src/main/resources/hudson/plugins/view/dashboard/core/UnstableJobsPortlet/portlet.jelly l.56 It is using the Util method from https://github.com/jenkinsci/dashboard-view-plugin/blob/master/src/main/resources/hudson/plugins/view/dashboard/jobLink.jelly I suppose that the fix will be similar to what was done for https://issues.jenkins-ci.org/browse/JENKINS-19310 during this commit: https://github.com/jenkinsci/jenkins/commit/ea95434938b2111d8768528823990a78bdc58d3e This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [analysis-collector] (JENKINS-23853) analysis collector doesn't generate the report
nagarjuna sudi created JENKINS-23853 analysis collector doesn't generate the report Issue Type: Bug Assignee: Ulli Hafner Components: analysis-collector Created: 17/Jul/14 11:37 AM Description: I am using 1.566 version. I installed findbugs,checkstyle plugins and analysis collector plugin in the jenkins and i specify these two as plugins in reporting section of maven POM.XML but the collector plugin doesn't generate the report with the combined results Project: Jenkins Priority: Major Reporter: nagarjuna sudi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-23588) JaCoCo Plugin creates unreadable coverage report
Akos Kozak commented on JENKINS-23588 JaCoCo Plugin creates unreadable coverage report I think the coloured column has somehow a dynamic size. We got the same problem! I just think, maybe to use Emma till this is not fixed, would be maybe a better choice. Please fix this ASAP! Thank you! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco] (JENKINS-19370) JaCoCo plugin should say on build result page why build failed, if threshold is broken
Akos Kozak commented on JENKINS-19370 JaCoCo plugin should say on build result page why build failed, if threshold is broken I think i case it fails because of the threshold, should the job fail not only the colour/status of the job should be changed. If the coverage drops down, the build should fail, and delvelopers should implement some more Tests, or do something. No email notification will be send if because of coverage the build "fails". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Daniele Vigano commented on JENKINS-20427 Build Parameter variable in branch name causes polling to detect false changes in GIT I can confirm this bug. With Jenkins 1.572, git client plugin 1.9.2 and git plugin 2.2.2 the polling module does not resolve our "$branch" variable, set in the parametrized build configuration: Started on Jul 17, 2014 10:50:00 AM Using strategy: Default [poll] Last Built Revision: Revision 2d1a169f855f69312b4b47819283063ea15c1448 (origin/master) > git ls-remote -h git://github.com/gem/oq-nrmllib.git $branch Done. Took 0.54 sec No changes If we disable the parametrized buildand just set 'master' as branch it works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23800) Xvfb won't activate
zregvart commented on JENKINS-23800 Xvfb won't activate I think that there is something wrong with your Jenkins installation: the ClassNotFoundException preceding the NoClassDefFoundError for com.sonyericsson.rebuild.RebuildValidator indicates that the configuration is referencing the rebuild plugin that is not installed or at least available to jenkins. Check file permissions on the plugins directory, and check the checksum of xvfb.jpi in the plugins directory, for version 1.0.12 it should be: $ shasum xvfb.jpi 73541d5bc014bd65e26374533d120e7b2f23bd78 xvfb.jpi If you're behind a corporate proxy/antivirus it could be that it corrupts jar files, so check for that. I've downloaded Jenkins version 1.572 and installed Xvfb plugin without problems, so what you're experiencing is local to you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23267) NullPointerException in XvfbBuildWrapper.setUp when configured without node label restrictions
zregvart closed JENKINS-23267 as Fixed NullPointerException in XvfbBuildWrapper.setUp when configured without node label restrictions closing resolved issue Change By: zregvart (17/Jul/14 11:05 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration] (JENKINS-23799) SCM Sync configuration plugin synchronizes tar.gz files ?!
Frédéric Camblor closed JENKINS-23799 as Duplicate SCM Sync configuration plugin synchronizes tar.gz files ?! I prefer to close it for the moment. But don't hesitate to re-open it if you see the issue is still present in 0.0.7.5 Change By: Frédéric Camblor (17/Jul/14 10:55 AM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Daniele Vigano commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name I can confirm this bug. With Jenkins 1.572, git client plugin 1.9.2 and git plugin 2.2.2 the polling module does not resolve our "$branch" variable, set in the parametrized build configuration: Started on Jul 17, 2014 10:50:00 AM Using strategy: Default [poll] Last Built Revision: Revision 2d1a169f855f69312b4b47819283063ea15c1448 (origin/master) > git ls-remote -h git://github.com/gem/oq-nrmllib.git $branch Done. Took 0.54 sec No changes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22009) Git Polling Keeps Detecting Changes When Variables in refspec
Daniele Vigano commented on JENKINS-22009 Git Polling Keeps Detecting Changes When Variables in refspec I can confirm this bug. With Jenkins 1.572, git client plugin 1.9.2 and git plugin 2.2.2 the polling module does not resolve our "$branch" variable, set in the parametrized build configuration: Started on Jul 17, 2014 10:50:00 AM Using strategy: Default [poll] Last Built Revision: Revision 2d1a169f855f69312b4b47819283063ea15c1448 (origin/master) > git ls-remote -h git://github.com/gem/oq-nrmllib.git $branch Done. Took 0.54 sec No changes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
