[JIRA] (JENKINS-17388) ssh-slaves 0.23: NoSuchMethodException: com.trilead.ssh2.Session.setWindowSize(int)
sogabe resolved JENKINS-17388 as Fixed ssh-slaves 0.23: NoSuchMethodException: com.trilead.ssh2.Session.setWindowSize(int) already fixed. see https://github.com/jenkinsci/ssh-slaves-plugin/commit/9e6f0300cfdbb7da9072363a87a1856bc9ad361b Change By: sogabe (29/Mar/13 6:55 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/groups/opt_out.
[JIRA] (JENKINS-17334) GHPRB fails to use Github server api URL for Github Enterprise
Zachary Benz commented on JENKINS-17334 GHPRB fails to use Github server api URL for Github Enterprise Oops, scratch that. The actual problem is line 66 of GhprbRepo.java: gitHub = GitHub.connect(trigger.getDescriptor().getUsername(), null, trigger.getDescriptor().getPassword()); Unlike the accessToken based login on line 61, which uses the serverAPIUrl, the else block that handles login without an accessToken ignores the serverAPIUrl setting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17334) GHPRB fails to use Github server api URL for Github Enterprise
Zachary Benz commented on JENKINS-17334 GHPRB fails to use Github server api URL for Github Enterprise It appears that the problem is line 78 of GhprbRepo.java, which is: repo = gh.getRepository(reponame); This is inside the checkState() method This makes a call to the class org.kohsuke.github.GitHub from github-api-1.35.jar. Unfortunately, internally this is hard wired to point to github.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9250) Clone workspace does not work well with multiple scm plugin
Christian Beikov commented on JENKINS-9250 Clone workspace does not work well with multiple scm plugin Same problem here, hope this will be fixed soon! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Nickolay Martinov commented on JENKINS-17265 Builds disappearing from history I confirm that script is perfect reproducer: Checking Infrastructure_update_sys... Checking Infrastructure_update_valgrind... Checking NOM_6_build... Job NOM_6_build missing builds: 887 618 Checking NOM_6_kit... Job NOM_6_kit missing builds: 204 Checking NOM_6_kit_smoke... Job NOM_6_kit_smoke missing builds: 139 Checking NOM_6_test_f... Checking NOM_6_test_f_m... Job NOM_6_test_f_m missing builds: 88 Checking NOM_6_test_l... Checking NOM_6_test_l_m... Job NOM_6_test_l_m missing builds: 204 Checking NOM_6_test_sdk... Job NOM_6_test_sdk missing builds: 85 Checking NOM_6_test_sdk_m... Checking NOM_V600_build... Checking NOM_V600_kit... Checking NOM_V600_kit_smoke... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16419) Jenkins Exception java.lang.StringIndexOutOfBoundsException: String index out of range: -114
liangxing wu
commented on JENKINS-16419
Jenkins Exception java.lang.StringIndexOutOfBoundsException: String index out of range: -114
May be cause by a coding problem, do not use non-english characters in you git user config.
Or you can modify the source code like this in ChangeLog.java:
commands.add("--format=\"zzREPOzz%H%n%an <%ae>%aD" + "%n%cn <%ce>%cD%n%s%n%n%byyREPOyy\"");
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Jose Sa
edited a comment on JENKINS-17265
Builds disappearing from history
Both "/api/json?tree=builds[number]" and "/rssAll" job urls seem to be returning only latest builds (not all as expected), like I wrote above this could be a symptom for this case.
Luckily "/buildHistory/all" does still provide all visible builds, so I was able to create created a bash script to help automatically to check for this kind of problems and provide a text report.
# Assuming some host specific variables
jenkins_url=https://localhost:8080
jobs_dir=/work/jenkins/jobs
# This should work for any unix environment using bash
for job_dir in ${jobs_dir}/*; do
job=$(basename ${job_dir})
echo "Checking $job..." >&2
job_url=${jenkins_url}/job/${job}
wget -q --no-check-certificate -O all ${job_url}/buildHistory/all
gawk -F'#' '/ #/{print $2}' all > online_builds
find ${jobs_dir}/${job}/builds/* -type l ! -name "last*" -prune | sed "s,${jobs_dir}/${job}/builds/,,g" > local_builds
missing=$(gawk '
BEGIN {first_file = ""}
{
if (first_file == "") first_file = FILENAME
if (first_file == FILENAME) {build_list[$1]=1} else {delete build_list[$1]}
}
END {for (build in build_list) print build}
' local_builds online_builds)
[ ! -z "${missing}" ] && echo Job $job missing builds: $missing
done | tee missing_builds.txt
I found out that after 3 days online, 85 (out of 1406) jobs are showing missing builds varying from a few to all.
I have FreeStyle and MultiJob types and they both show this problem.
We are using mixed ClearCase and SVN (both showing same problems)
Server is Solaris 10 Sparc, having slaves on HP-UX, Windows (XP, 2k3, 7), RHEL (5, 6), Solaris.
Running Jenkins from war file, currently with 1.505 (but noticing this problem since 1.485)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17388) ssh-slaves 0.23: NoSuchMethodException: com.trilead.ssh2.Session.setWindowSize(int)
Kenny Ayers commented on JENKINS-17388 ssh-slaves 0.23: NoSuchMethodException: com.trilead.ssh2.Session.setWindowSize(int) Same issue here. Jenkins ver. 1.489. Jenkins SSH Slaves plugin 0.23 ERROR: Failed to expand buffer size java.lang.NoSuchMethodException: com.trilead.ssh2.Session.setWindowSize(int) at java.lang.Class.getMethod(Class.java:1622) at hudson.plugins.sshslaves.SSHLauncher.expandChannelBufferSize(SSHLauncher.java:711) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:661) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:472) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:200) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:679) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17403) Git pre build merge should support a fast forward only merge
Mike Power commented on JENKINS-17403 Git pre build merge should support a fast forward only merge Work around (which works pretty good) Setup the jenkins user with this command: git config --global --add merge.ff only This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13154) Heavy thread congestion with FingerPrint.save
Eric Denman commented on JENKINS-13154 Heavy thread congestion with FingerPrint.save @jglick looks like my threaddump is blocked deep underneath Fingerprint.load so it may not be the same issue. Should I re-open this ticket or file a new one? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13564) Mailer fails to send an email whe thre's a project with broken commits
dogfood commented on JENKINS-13564 Mailer fails to send an email whe thre's a project with broken commits Integrated in jenkins_main_trunk #2421 JENKINS-13564 make the method self-correcting (Revision c3a19670d5400d805a7096a5b69df0ec14c532cd) Result = SUCCESS kohsuke : c3a19670d5400d805a7096a5b69df0ec14c532cd Files : core/src/main/java/hudson/model/Computer.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13154) Heavy thread congestion with FingerPrint.save
Eric Denman updated JENKINS-13154 Heavy thread congestion with FingerPrint.save FWIW, I just installed 1.510-SNAPSHOT (e837438c0138faf401bcb433450c8dfdc7ebbe6f) and our builds are still taking 5+ minutes on the "Waiting for Jenkins to finish collecting data" step and the whole jenkins app frequently stops responding to any requests. We have 228M of data in the "fingerprints" dir. I tried getting a thread dump by using the /threadDump when it was in the "not responding" state but that didn't work so I used jstack -F. Attaching that dump. Change By: Eric Denman (29/Mar/13 12:18 AM) Attachment: threadDump This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15677) S3 plugin should retry few times if upload to S3 fails
David Glasser commented on JENKINS-15677 S3 plugin should retry few times if upload to S3 fails You can increase the buffer size by passing something like -Dcom.amazonaws.sdk.s3.defaultStreamBufferSize=15728640 to the jenkins java command-line. (This raises the buffer to 15MB from 128KB, which means that errors in the first 15MB are recoverable.) It would be nice, though, if it this were fully avoidable, but I guess since Jenkins supports uploads from other servers (not just local files) you can't just pass a File object to AmazonS3Client.putObject, and so there needs to be some buffering to make the InputStream repeatable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17403) Git pre build merge should support a fast forward only merge
Mike Power created JENKINS-17403 Git pre build merge should support a fast forward only merge Issue Type: New Feature Assignee: Nicolas De Loof Components: git Created: 28/Mar/13 11:38 PM Description: We have the use case where one git remote always contains what is released and only what is released. So all development is done in a development remote. At the point of release we want to merge the development remote into this release remote and then run a maven release build. Those on the development remote are expected to merge from the release into the development remote. Hence when using jenkins to do the work of merging from the development remote to the release remote the pre build merge should be a fast forward only merge. That way we know all the work to test and certify the code has been completed. Should a non fast forward merge take place from development to remote it represents an integration case that should under go testing on the development remote. Right now almost all of this can be done with the git plugin. However when doing prebuild merge the plugin won't fail if it is a fast forward merge. Thus it will go head and merge and push an integration case. I would like to see the pre build merge support the option for fast forward merges only. Project: Jenkins Priority: Major Reporter: Mike Power This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13564) Mailer fails to send an email whe thre's a project with broken commits
SCM/JIRA link daemon commented on JENKINS-13564 Mailer fails to send an email whe thre's a project with broken commits Code changed in jenkins User: Kohsuke Kawaguchi Path: core/src/main/java/hudson/model/Computer.java http://jenkins-ci.org/commit/jenkins/c3a19670d5400d805a7096a5b69df0ec14c532cd Log: JENKINS-13564 make the method self-correcting If for some reason the numExecutors field gets out of sync with executors.size() (for example this can happen if an executor swallowed an interrupt signal without properly processing it), then a further attempt to call setNumExecutors results in a no-op. Given that these things can get out of sync, a smarter thing to do is to always compare where we are (the "executors" variable) and where we'd like to be (numExecutors), and make corrective actions. This particularly affects a zombie computer. The sequence to kill a Computer first involves waiting for all the executors to quit. If setNumExecutors(0) becomes no-op, a zombine computer never gets killed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17262) Remotely triggered build with parameters failing with extended choice parameters
vimil resolved JENKINS-17262 as Fixed Remotely triggered build with parameters failing with extended choice parameters Change By: vimil (28/Mar/13 10:34 PM) Status: In Progress Resolved Assignee: vimil 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/groups/opt_out.
[JIRA] (JENKINS-17262) Remotely triggered build with parameters failing with extended choice parameters
vimil started work on JENKINS-17262 Remotely triggered build with parameters failing with extended choice parameters Change By: vimil (28/Mar/13 10:34 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/groups/opt_out.
[JIRA] (JENKINS-13275) Jenkins stops handling HTTP/AJP requests after some time
evernat commented on JENKINS-13275 Jenkins stops handling HTTP/AJP requests after some time Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available
Mike Caspar commented on JENKINS-17343 Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available OK.. I made some progress and wanted to help others who are having trouble. It appears that by upgrading to Java 1.7 (jre7) instead of 1.6 does the trick. I found out that just changing JAVA_HOME is not enough to be able to do the switch. If you go to Manage Jenkins, then system info (sysinfo).. check the java.runtime.version. You will see that it seems to ignores whatever is in JAVA_HOME. I discovered that the reason for this is that a Copy of the JRE at the time of initial installation was copied to JENKINS_HOME/jre. To fix this, I did the following... net stop jenkins rename JENKINS_HOME\jre to JENKINS_HOME\jre-backup (in my case, I actually copied the entire folder elsewhere to be sure I had a copy (just in case). Copy the folder c:\Program Files\Java\jre7 to JENKINS_HOME/jre7. After copying JRE7 to JENKINS_HOME, rename it to jre (of course, you might be able to do without the rename step). Start up Jenkins with net start Jenkins Login and go to sysinfo.. you should see the newer java.runtime.version. I put this together from a few of the notes above and wanted to share it with other WinXP users that might not easily find this resolution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17262) Remotely triggered build with parameters failing with extended choice parameters
SCM/JIRA link daemon commented on JENKINS-17262 Remotely triggered build with parameters failing with extended choice parameters Code changed in jenkins User: vimil Path: src/main/java/com/cwctravel/hudson/plugins/extended_choice_parameter/ExtendedChoiceParameterDefinition.java http://jenkins-ci.org/commit/extended-choice-parameter-plugin/dee8e972bd0460255942a612cdbc76aba4069803 Log: JENKINS-17262 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available
Mike Caspar commented on JENKINS-17343 Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available Hi there. I upgraded from 1.506 to 1.508 and started having this problem. It was easily solved by downgrading to 1.506. This may allow you to keep working while looking for resolution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13995) Would like the ability to disable hover-over context menus.
dogfood commented on JENKINS-13995 Would like the ability to disable hover-over context menus. Integrated in jenkins_main_trunk #2420 Result = UNSTABLE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Jose Sa
commented on JENKINS-17265
Builds disappearing from history
Both "/api/json?tree=builds[number]" and "/rssAll" job urls seem to be returning only latest builds (not all as expected), like I wrote above this could be a symptom for this case.
Luckily "/buildHistory/all" does still provide all visible builds, so I was able to create created a bash script to help automatically to check for this kind of problems and provide a text report.
# Assuming some host specific variables
jenkins_url=https://localhost:8080
jobs_dir=/work/jenkins/jobs
# This should work for any unix environment using bash
for job_dir in ${jobs_dir}/*; do
job=$(basename ${job_dir})
echo "Checking $job..." >&2
job_url=${jenkins_url}/job/${job}
wget -q --no-check-certificate -O all ${job_url}/buildHistory/all
gawk -F'#' '/ #/{print $2}' all > online_builds
find ${jobs_dir}/${job}/builds/* * -type l ! -name "last*" -prune | sed "s,${jobs_dir}/${job}/builds/,,g" > local_builds
missing=$(gawk '
BEGIN {first_file = ""}
{
if (first_file == "") first_file = FILENAME
if (first_file == FILENAME) {build_list[$1]=1} else {delete build_list[$1]}
}
END {for (build in build_list) print build}
' local_builds online_builds)
[ ! -z "${missing}" ] && echo Job $job missing builds: $missing
done | tee missing_builds.txt
I found out that after 3 days online, 85 (out of 1406) jobs are showing missing builds varying from a few to all.
I have FreeStyle and MultiJob types and they both show this problem.
We are using mixed ClearCase and SVN (both showing same problems)
Server is Solaris 10 Sparc, having slaves on HP-UX, Windows (XP, 2k3, 7), RHEL (5, 6), Solaris.
Running Jenkins from war file, currently with 1.505 (but noticing this problem since 1.485)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17402) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact
John Dyer
created JENKINS-17402
Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
copyartifact
Created:
28/Mar/13 8:54 PM
Description:
I seem to be unable to select a project to copy an artifact from via the job config. Any time I try to and press save I get the following error msg:
Exception: java.lang.RuntimeException: Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact from {"projectName":"Moho","":"0","selector":{"stapler-class":"hudson.plugins.copyartifact.StatusBuildSelector","stableOnly":false},"filter":"*//mysql.provisioning.sql-*.tar.gz","target":"target/artifacts/","parameters":"","flatten":true,"optional":false,"stapler-class":"hudson.plugins.copyartifact.CopyArtifact","kind":"hudson.plugins.copyartifact.CopyArtifact"}
Stacktrace:
Full logs: https://gist.github.com/johntdyer/4ecd0135fad5586c637f
This is version 1.26
Environment:
Jenkins 1.508
Project:
Jenkins
Priority:
Major
Reporter:
John Dyer
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Frank Merrow commented on JENKINS-17265 Builds disappearing from history Just chiming in with "me too" on 1.502 . . . it is new installation and no matter what I do it only seems to show jobs from "today". (Have not been around at midnight to look . . . but in morning onward I only see jobs that ran today). FWIW: If I look in the jobs directory, the correct number of history directories are there . . . but web view just doesn't show them. (???) Windows7, no slaves, nothing odd about the installation that isn't in 10 others I have that are working on Jenkins from 1.488 onward. Also, I have a second 1.502 installation that was brought on-line around the same time . . . everything shows there. I cannot say the plugin mix on the two systems is identical, but it is very similar. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
Dan Checkoway commented on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled @Jesse Glick, I did.https://issues.jenkins-ci.org/browse/JENKINS-17110 Just noted it here since I'm pretty sure the bug was introduced with JENKINS-16844's fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14670) Node Label Parameter Plugin - Choose whether to queue builds for offline nodes or not.
domi resolved JENKINS-14670 as Duplicate Node Label Parameter Plugin - Choose whether to queue builds for offline nodes or not. this is implemented with 'JENKINS-17305' Change By: domi (28/Mar/13 7:49 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/groups/opt_out.
[JIRA] (JENKINS-14407) Allow multi-value default for Scheduled runs
SCM/JIRA link daemon resolved JENKINS-14407 as Fixed Allow multi-value default for Scheduled runs Change By: SCM/JIRA link daemon (28/Mar/13 7:48 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/groups/opt_out.
[JIRA] (JENKINS-17305) All nodes for label - don't wait for offline nodes
SCM/JIRA link daemon resolved JENKINS-17305 as Fixed All nodes for label - don't wait for offline nodes Change By: SCM/JIRA link daemon (28/Mar/13 7:48 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/groups/opt_out.
[JIRA] (JENKINS-14407) Allow multi-value default for Scheduled runs
SCM/JIRA link daemon commented on JENKINS-14407 Allow multi-value default for Scheduled runs Code changed in jenkins User: imod Path: pom.xml src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/NodeParameterDefinition.java src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/NodeParameterValue.java src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/NodeUtil.java src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/wrapper/TriggerNextBuildWrapper.java src/main/resources/org/jvnet/jenkins/plugins/nodelabelparameter/Messages.properties src/main/resources/org/jvnet/jenkins/plugins/nodelabelparameter/NodeParameterDefinition/config.jelly src/main/resources/org/jvnet/jenkins/plugins/nodelabelparameter/NodeParameterDefinition/config.properties src/main/resources/org/jvnet/jenkins/plugins/nodelabelparameter/NodeParameterDefinition/index.jelly src/main/resources/org/jvnet/jenkins/plugins/nodelabelparameter/parameterizedtrigger/AllNodesForLabelBuildParameterFactory/config_de.properties src/main/webapp/lib/nodelabel.js http://jenkins-ci.org/commit/nodelabelparameter-plugin/e6bdc216cf4e2a3c756ceb170503b2ff09013159 Log: [FIXED JENKINS-14407] Allow multi-value default for Scheduled runs Compare: https://github.com/jenkinsci/nodelabelparameter-plugin/compare/8c046cc97b09...e6bdc216cf4e This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17305) All nodes for label - don't wait for offline nodes
SCM/JIRA link daemon commented on JENKINS-17305 All nodes for label - don't wait for offline nodes Code changed in jenkins User: imod Path: src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/parameterizedtrigger/AllNodesForLabelBuildParameterFactory.java src/main/resources/org/jvnet/jenkins/plugins/nodelabelparameter/parameterizedtrigger/AllNodesForLabelBuildParameterFactory/config.jelly http://jenkins-ci.org/commit/nodelabelparameter-plugin/7b44cfbeedf6b0341a0f3c1a0bdff19382b39e37 Log: [FIXED JENKINS-17305] add option to ignore offline nodes in parameter factory This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13995) Would like the ability to disable hover-over context menus.
Bernd bep commented on JENKINS-13995 Would like the ability to disable hover-over context menus. IMHO, the context menu should not open automatically in the crumb bar. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16844) Triggering a build from the context menu produces a warning when security is enabled
Jesse Glick commented on JENKINS-16844 Triggering a build from the context menu produces a warning when security is enabled @dcheckoway: any related bugs should be filed separately. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Batch script runs on server but not via Jenkins
We have a Jenkins job that bring together test results and populates a text file with the current build we are testing. The text file is on a shared folder on the same machine that hosts our Jenkins environment. We have another Jenkins job that uses this file and has a build step with the following batch command: cd C:\TestResults IF EXIST Build.txt ( set /p Build=http://jenkins.361315.n4.nabble.com/Batch-script-runs-on-server-but-not-via-Jenkins-tp4660923.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17401) Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window
Stuart Montgomery created JENKINS-17401 Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: gui Created: 28/Mar/13 6:45 PM Description: In Jenkins 1.508, when attempting to rename a project, clicking 'Apply' at the bottom of the 'Configure Project' page results in an empty "Error" pop-over box on the page. No error message is displayed. However, when I press 'Save' instead of Apply, it takes me to a separate confirmation page asking "Am I sure I want to rename the project? Yes/No". So I am guessing that this confirmation step prevents 'Apply' from working. Project: Jenkins Priority: Minor Reporter: Stuart Montgomery This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17401) Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window
Stuart Montgomery updated JENKINS-17401 Renaming a job and clicking 'Apply' shows an empty 'Error' pop-over window Change By: Stuart Montgomery (28/Mar/13 6:46 PM) Description: In Jenkins 1.508, when attempting to rename a project, clicking 'Apply' at the bottom of the 'Configure Project' page results in an empty "Error" pop-over box on the page. No error message is displayed.However, when I press 'Save' instead of Apply, it takes me to a separate confirmation page asking "Am I sure I want to rename the project? Yes/No". So I am guessing that this confirmation step prevents 'Apply' from working. I would expect to see a pop-over window asking me to confirm the change on the same page when I click 'Apply', instead of presenting an empty error pop-over, which can be confusing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13995) Would like the ability to disable hover-over context menus.
Jesse Glick commented on JENKINS-13995 Would like the ability to disable hover-over context menus. Better. Still pops up context menu automatically in crumb bar; is this intentional and should be the issue be marked 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/groups/opt_out.
[JIRA] (JENKINS-17400) Context menu icons not properly cached
Jesse Glick created JENKINS-17400 Context menu icons not properly cached Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Mar/13 6:14 PM Description: Context menu icons (e.g. notepad.png) are not loaded as /static, so each context menu display causes several requests resulting in a 304. Project: Jenkins Labels: images performance context-menu Priority: Minor Reporter: 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/groups/opt_out.
[JIRA] (JENKINS-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available
Jesse Glick commented on JENKINS-17343 Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available @mafujosh: right, using Java 7 is one workaround, since on Java 7 we use NIO.2 APIs which offer symlink functions when available. It is only on Java 5/6 that we try to use JNA to access platform-specific symlink calls. The fix is not to search for other symlink-like things on XP, but to ignore errors calling this API, as we do for other native methods. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16264) Posting config.xml to master node advertised to work
Damon G commented on JENKINS-16264 Posting config.xml to master node advertised to work I have to take that comment back. It doesn't work. I thought it was working because my attempt above used cashed credentials I had open in another browser tab. I don't have CSRF enabled. I'll take it to the forums though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13995) Would like the ability to disable hover-over context menus.
SCM/JIRA link daemon commented on JENKINS-13995 Would like the ability to disable hover-over context menus. Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/resources/lib/layout/breadcrumbs.css core/src/main/resources/lib/layout/breadcrumbs.js core/src/main/resources/lib/layout/menu_down_arrow.png http://jenkins-ci.org/commit/jenkins/b41aa9e0a6489ec8f45aaf1c9f7cd3ad81419adf Log: JENKINS-13995 Disabled the automatic pop-up of context menu. Instead, it shows a small 'v' icon to the right that needs to be clicked to open a context menu. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15642) ArrayIndexOutOfBounds exception with Maven build when triggered by SCM change
Haijing Wei commented on JENKINS-15642 ArrayIndexOutOfBounds exception with Maven build when triggered by SCM change a quick and dirty workaround, there is a modules folder in ur job folder, remove it, and restart server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15642) ArrayIndexOutOfBounds exception with Maven build when triggered by SCM change
Haijing Wei commented on JENKINS-15642 ArrayIndexOutOfBounds exception with Maven build when triggered by SCM change question is how could this happen? lo=17,hi=3, why is lo > hi? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17323) Log lines print without newlines
Jason Swager assigned JENKINS-17323 to Jason Swager Log lines print without newlines Change By: Jason Swager (28/Mar/13 3:59 PM) Assignee: Jason Swager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16590) Wrong Load Statistics Graph
Jason Swager commented on JENKINS-16590 Wrong Load Statistics Graph Is this problem still happening with Jenkins 1.508? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15504) NPE on running a job
Jason Swager assigned JENKINS-15504 to Jason Swager NPE on running a job Change By: Jason Swager (28/Mar/13 3:59 PM) Assignee: Jason Swager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16960) Status Code: 500/ NullPointerException when running command in slave script console
Jason Swager commented on JENKINS-16960 Status Code: 500/ NullPointerException when running command in slave script console What command did you enter into the Script Console? I tried a couple simple ones and there were no errors - got expected response. Also, what sort of slave are you running the commands on? And was the slave connected at the time you ran the command? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available
Joshua Masek commented on JENKINS-17343 Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available Ok, I updated to latest version of Java, and that fixed this issue. Sorry I didn't think to try that before. I don't think I had updated it in awhile. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16960) Status Code: 500/ NullPointerException when running command in slave script console
Jason Swager assigned JENKINS-16960 to Jason Swager Status Code: 500/ NullPointerException when running command in slave script console Change By: Jason Swager (28/Mar/13 3:51 PM) Assignee: Jason Swager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17399) CVS Tagging plugin currently does not work with CVS Plugin 2.0 or later.
Lloyd Meinholz created JENKINS-17399 CVS Tagging plugin currently does not work with CVS Plugin 2.0 or later. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cvs-tag Created: 28/Mar/13 3:14 PM Description: CVS Tagging plugin currently does not work with CVS Plugin 2.0 or later. SEVERE: Executor threw an exception java.lang.NoSuchMethodError: hudson.scm.CVSSCM$DescriptorImpl.getCvsExeOrDefault()Ljava/lang/String; at hudson.plugins.cvs_tag.CvsTagPlugin.perform(CvsTagPlugin.java:89) at hudson.plugins.cvs_tag.CvsTagPublisher.perform(CvsTagPublisher.java:117) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:798) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:770) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1620) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Project: Jenkins Priority: Major Reporter: Lloyd Meinholz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17397) NPE in MatrixBuild -> parent project fails when children did not yet finish
Krzysztof Malinowski created JENKINS-17397 NPE in MatrixBuild -> parent project fails when children did not yet finish Issue Type: Bug Assignee: Unassigned Components: core Created: 28/Mar/13 3:00 PM Description: It happened that matrix parent project fails due to exception while one of the configuration was still building (and other two configurations succeeded). Configuration 0 was still building when the issue occurred. 15:25:26 Triggering 1,RedHatEnterpriseServer 15:25:26 Triggering 2,RedHatEnterpriseServer 15:25:26 Triggering 0,RedHatEnterpriseServer 15:44:12 1,RedHatEnterpriseServer completed with result SUCCESS 15:45:12 2,RedHatEnterpriseServer completed with result SUCCESS 15:45:12 0,RedHatEnterpriseServer completed with result FAILURE 15:45:12 FATAL: null 15:45:12 java.lang.NullPointerException 15:45:12 at hudson.matrix.MatrixBuild$MatrixBuildExecution.doRun(MatrixBuild.java:371) 15:45:12 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) 15:45:12 at hudson.model.Run.execute(Run.java:1575) 15:45:12 at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) 15:45:12 at hudson.model.ResourceController.execute(ResourceController.java:88) 15:45:12 at hudson.model.Executor.run(Executor.java:237) 15:45:12 at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66) Environment: Jenkins 1.508 on RHEL5 x86_64 Project: Jenkins Priority: Critical Reporter: Krzysztof Malinowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13662) Maven job Pre Step properties are not getting right
Eugene Gligalov commented on JENKINS-13662 Maven job Pre Step properties are not getting right Hi The problem is a bit different, I have tried to use that parameters in Jenkins API scripts, it does require to recreate pre or post build step with the same settings. Regards Eugene This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17396) When a technical issue arise in the plugin itself the baseline should be untouched
jenkinsuserfrance jenkinsuserfrance created JENKINS-17396 When a technical issue arise in the plugin itself the baseline should be untouched Issue Type: Bug Assignee: Praqma Support Components: clearcase-ucm Created: 28/Mar/13 1:39 PM Description: Sometimes the rebase\update fails within the plugin thus the build itself has not even started. Right now, it still means that the baseline is rejected. Project: Jenkins Priority: Major Reporter: jenkinsuserfrance jenkinsuserfrance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14575) SCM checkout retry count not working
Adam PAPAI edited a comment on JENKINS-14575 SCM checkout retry count not working I'm just fixing this. I got the bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-5408) Quoting Issue with JDK Installer with Windows Slave
Christoph Linder commented on JENKINS-5408 Quoting Issue with JDK Installer with Windows Slave Pretty please? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17372) Error looking up function 'CreateSymbolicLinkW' (our case 8908)
Lars Kruse commented on JENKINS-17372 Error looking up function 'CreateSymbolicLinkW' (our case 8908) This bug is not related to the PRQA plugin, but to the fact that "Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available" https://issues.jenkins-ci.org/browse/JENKINS-17343 Praqma support has been in contact with Klaus who verified that Jenkins was indeed upgraded too along with the upgrade of the PRQA plugin. Rolling Jenkins back to a version < 1.505 solved the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13314) Remote API does not include downstream/upstream build info
jfigler commented on JENKINS-13314 Remote API does not include downstream/upstream build info Agreed. It would be great to be able to ask an upstream build which downstream builds it was responsible for triggering via that API. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8276) Add View Job Filters to the List View Section
Michel Rasschaert reopened JENKINS-8276 Add View Job Filters to the List View Section Using Jenkins LTS 1.480.3, there is no way to add View Job filters to the List view section. Change By: Michel Rasschaert (28/Mar/13 12:04 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Ivan Veselkov edited a comment on JENKINS-17265 Builds disappearing from history We have a matrix job with two configurations (os = hpux or linux ). There is a keep-forever build which appears in parent history but it is absent in histories of configurations. From parent build one can still access both configurations. The copy plugin almost always cannot copy artifacts from this build: "Unable to find a build for artifact copy from" but at least once it succeeded for os=hpux. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Ivan Veselkov edited a comment on JENKINS-17265 Builds disappearing from history We have a matrix job with two configurations (os = hpux or linux ). There is a keep-forever build which appears in parent history but it is absent in histories of configurations. From parent build one can still access both configurations. The copy plugin cannot copy artifacts from this build: "Unable to find a build for artifact copy from". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Ivan Veselkov commented on JENKINS-17265 Builds disappearing from history We have a matrix job with two configurations (os = hpux or linux ). There is a keep-forever build which appears in parent history but it is absent in histories of configurations. From parent build one can still access both configurations. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14575) SCM checkout retry count not working
Adam PAPAI started work on JENKINS-14575 SCM checkout retry count not working Change By: Adam PAPAI (28/Mar/13 9:22 AM) 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/groups/opt_out.
[JIRA] (JENKINS-15808) CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Andrew Erickson commented on JENKINS-15808 CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration Yes, I will try to test this soon (if not tomorrow, definitely this week). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14575) SCM checkout retry count not working
Adam PAPAI commented on JENKINS-14575 SCM checkout retry count not working I've just fixing this. I got the bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-14575) SCM checkout retry count not working
Adam PAPAI assigned JENKINS-14575 to Adam PAPAI SCM checkout retry count not working Change By: Adam PAPAI (28/Mar/13 9:07 AM) Assignee: Adam PAPAI This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available
Christian Gmeiner edited a comment on JENKINS-17343 Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available same here with Windows Server 2003 SP2: Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/G:/hudson/war/WEB-INF/lib/jenkins-core-1.508.jar!/hudson/model/Job/permalinks.jelly:32:48: Error looking up function 'CreateSymbolicLinkW': The specified procedure could not be found. Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/G:/hudson/war/WEB-INF/lib/jenkins-core-1.508.jar!/hudson/model/Job/permalinks.jelly:32:48: Error looking up function 'CreateSymbolicLinkW': The specified procedure could not be found. at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(Reque
[JIRA] (JENKINS-17343) Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available
Christian Gmeiner commented on JENKINS-17343 Jenkins is no more WinXP compliant : CreateSymbolicLinkW is not available same here: Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/G:/hudson/war/WEB-INF/lib/jenkins-core-1.508.jar!/hudson/model/Job/permalinks.jelly:32:48: Error looking up function 'CreateSymbolicLinkW': The specified procedure could not be found. Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/G:/hudson/war/WEB-INF/lib/jenkins-core-1.508.jar!/hudson/model/Job/permalinks.jelly:32:48: Error looking up function 'CreateSymbolicLinkW': The specified procedure could not be found. at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:666) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.koh
[JIRA] (JENKINS-17265) Builds disappearing from history
Nickolay Martinov commented on JENKINS-17265 Builds disappearing from history Jose has made interesting note. I recall that sometimes we can see build listed in UI but Copy Artifacts Plugin seems to fail to find the build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Nickolay Martinov commented on JENKINS-17265 Builds disappearing from history Using SVN, standard plugin. Using only matrix and freestyle jobs. Previously both were disappearing like crazy. Recently matrix jobs seems to become more stable. Freestyle jobs still have problems. Perhaps makes to note that jobs are not standalone: both matrix and freestyle jobs trigger each other (build other builds) heavily. Installed plugins (env injector is disabled): Jenkins Mailer Plugin 1.4 External Monitor Job Type Plugin 1.1 LDAP Plugin 1.2 pam-auth 1.0 Javadoc Plugin 1.1 Token Macro Plugin This plug-in adds reusable macro expansion capability for other plug-ins to use. 1.6 Maven 2 Project Plugin 1.505 Jenkins Subversion Plug-in 1.45 Ant Plugin 1.2 Jenkins CVS Plug-in Integrates Jenkins with CVS version control system using a modified version of the Netbeans cvsclient. 2.8 Dump Info BuildWrapper Plugin The Dump Info BuildWrapper Plugin allows jobs to automatically dump some important Hudson-specific information into the job log. 1.1 Hudson platformlabeler plugin Assigns labels on nodes automatically based on the computer operating system. 1.1 Tracking SVN Plugin 1.1 Priority Sorter This plugin allows for the build queue to be sorted based on pre-assigned priorities for each job. 1.3 Jenkins Translation Assistance plugin 1.10 Static Analysis Utilities This plug-in provides utilities for the static code analysis plug-ins. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 1.49 Task Scanner Plugin This plug-in scans for open tasks in a specified set of files in the project modules and visualizes the results. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 4.35 Disk Usage Plugin This plugin counts disk usage. 0.18 SSH Slaves plugin 0.22 FindBugs Plug-in This plug-in collects the FindBugs analysis results of the project modules and visualizes the found warnings. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 4.48 Checkstyle Plug-in This plug-in collects the Checkstyle analysis results of the project modules and visualizes the found warnings. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 3.35 Git Client Plugin 1.0.3 Git Plugin This plugin integrates GIT with Jenkins. 1.2.0 View Job Filters Create smart views with exactly the jobs you want. Your smart views can automatically include or exclude jobs by using things like the SCM path or type, the job type, build statuses or trends or triggers, relevance to the logged-in user, email recipients, Maven configuration, job parameterization, and user permissions. Mix and match filters to narrow down to exactly what you want. 1.22 Warnings Plug-in This plug-in collects the compiler warnings of the project modules and visualizes the results. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 4.23 PMD Plug-in This plug-in collects the PMD analysis results of the project modules and visualizes the found warnings. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 3.34 Copy Artifact Plugin Adds a build step to copy artifacts from another project. 1.25 Downstream build view This plug-in allows you to view the full status all the downstream builds so that we can graphically see that everything for this build has been completed successfully. 1.8 Hudson Blame Subversion Plug-in 1.200 Groovy Postbuild Groovy postbuild task. 1.8 groovyaxis This plugin is a sample to explain how to write a Jenkins plugin. 0.3 Duplicate Code Scanner Plug-in This plug-in collects the duplicate code analysis results of the project modules and visualizes the found warnings. Supported duplicate code analysis tools: • PMD's Copy Paste Detector (CPD) • Simian If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 2.34 Static Analysis Collector Plug-in This plug-in is an add-on for the plug-ins Checkstyle, Dry, FindBugs, PMD, Tasks, and Warnings: the plug-in collects the different analysis results and shows the results in a combined trend graph. Additionally, the plug-in provides health reporting and build stability based on these combined results. If you like this open sourc
