[JIRA] [s3-plugin] (JENKINS-26903) S3 plugin missing http jars
Morgan Nelson created JENKINS-26903 S3 plugin missing http jars Issue Type: Bug Assignee: Michael Watt Components: s3-plugin Created: 11/Feb/15 4:20 PM Description: updated Jenkins server but kept Jenkins $HOME from old server. Updated installed plugins including S3 plugin, S3 plugin started throwing errors: java.lang.NoClassDefFoundError: org/apache/http/conn/scheme/SchemeSocketFactory java.lang.NoClassDefFoundError: org/apache/http/protocol/HttpContext I had to drop the httpclient-4.4 and httpcore-4.4 jars from another plugin into the S3 plugin to make it work Environment: Jenkins 1.598, S3 plugin 0.7, oracle jdk 7. Ubuntu 14.04 fresh install. Project: Jenkins Labels: s3 Priority: Major Reporter: Morgan Nelson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-plugin] (JENKINS-26904) Add the ability to change interval between SCM polls
C. Alex Reober created JENKINS-26904 Add the ability to change interval between SCM polls Issue Type: Improvement Assignee: Frédéric Camblor Components: scm-sync-configuration-plugin Created: 11/Feb/15 4:25 PM Description: Request the ability to change how often the SCM sync config plugin runs and pushes configs to the repo. This would allow the Admin to determine what is an optimal backup plan for there enviromment. Environment: All Project: Jenkins Labels: enhancement plugin Priority: Minor Reporter: C. Alex Reober This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter-plugin] (JENKINS-26905) NodeLabelParameter plugin is missing VALUE for parameter in API
Danny Staple created JENKINS-26905 NodeLabelParameter plugin is missing VALUE for parameter in API Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter-plugin Created: 11/Feb/15 4:54 PM Description: When a build has completed with a nodelabel parameter, querying the builds API, in teh parameters list, the NodeLabel parameters have a NAME but no VALUE. Environment: Jenkins-1.580.1, Nodelabelparameter plugin 1.5.1 Project: Jenkins Priority: Major Reporter: Danny Staple This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26906) Re-introduce the ability to override the username/password at the specific job
Cletus DSouza created JENKINS-26906 Re-introduce the ability to override the username/password at the specific job Issue Type: Improvement Assignee: Cletus DSouza Components: integrity-plugin Created: 11/Feb/15 5:26 PM Description: I really don't think it is a good idea to store the user and password in the general configuration. This means that anyone who can create a job has access to all projects of the users stored in the general configuration. This information must be stored in each individual job. I have no problem with the server information being stored in the general configuration, but the user name and password is a real security problem for us. I can understand that where each project has its own Jenkins server and their own service account, this will be much easier. However, we have a central Jenkins server that is run by the Tools Group that has many varied jobs, some of which require admin access to Integrity. This means that anyone who can create jobs on this particular Jenkins server (including the majority of users who should not have admin access to Integrity) can get access to all Integrity projects, which is not allowed. Environment: Integrity Plugin Version 1.30 Project: Jenkins Priority: Major Reporter: Cletus DSouza This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-9690) Cache jmeter parsing results
Mischa Holz commented on JENKINS-9690 Cache jmeter parsing results This is still an issue and pretty much makes this plugin unusable for our purposes. I'd suggest to use some kind of database to store all HttpSamples and let it do all the aggregation after the inital parsing of the jtl file. It seems like no one is actually still working on this plugin though, which is kinda sad. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fxcop-runner-plugin] (JENKINS-26902) FxCop-Runner The Assembly Files textbox is preventing spaces in my path name from working.
Christopher Orr moved JENKINS-26902 FxCop-Runner The Assembly Files textbox is preventing spaces in my path name from working. Change By: Christopher Orr (11/Feb/15 3:37 PM) Project: Infrastructure Jenkins Key: INFRA JENKINS - 236 26902 Workflow: jira JNJira Component/s: fxcop-runner-plugin Component/s: etc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flaky-test-handler-plugin] (JENKINS-25446) ERROR: Publisher com.google.jenkins.flakyTestHandler.plugin.JUnitFlakyResultArchiver aborted due to exception
Qingzhou Luo commented on JENKINS-25446 ERROR: Publisher com.google.jenkins.flakyTestHandler.plugin.JUnitFlakyResultArchiver aborted due to exception Thanks Daniel! Right now I am having some injury on my right wrist, plus the school is quite busy, so I couldn't do much work these days. I will try to resolve that as soon as I get a chance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp-plugin] (JENKINS-26907) HockeyApp Configuration Lost after Jenkins Restart
Jedi Lewis updated JENKINS-26907 HockeyApp Configuration Lost after Jenkins Restart Change By: Jedi Lewis (11/Feb/15 5:38 PM) Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp-plugin] (JENKINS-26907) HockeyApp Configuration Lost after Jenkins Restart
Jedi Lewis created JENKINS-26907 HockeyApp Configuration Lost after Jenkins Restart Issue Type: Bug Assignee: Unassigned Components: hockeyapp-plugin Created: 11/Feb/15 5:37 PM Description: 1. Configure a Jenkins job to have the HockeyApp post-build action with template parameters for the API Token and App File fields. 2. Restart Jenkins 3. The configuration for HockeyApp in the job is gone. Reproduced on several Jenkins instances running Jenkins 1.598 (and older) and HockeyApp 1.2.0 The issue does not exist in HockeyApp 1.1.0 Project: Jenkins Priority: Blocker Reporter: Jedi Lewis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26887) git polling/web hooks need to occur in a separate polling workspace
Jeremiah Norris commented on JENKINS-26887 git polling/web hooks need to occur in a separate polling workspace Also it looks like polling won't even be attempted if a build is already running. It doesn't take concurrent builds in to consideration at all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26887) git polling/web hooks need to occur in a separate polling workspace
Jeremiah Norris commented on JENKINS-26887 git polling/web hooks need to occur in a separate polling workspace It will execute concurrent builds only if they are kicked off manually. If a build is already running and an new commit comes in to the repository and Jenkins gets notified via web hook Jenkins will just ignore it and continue running the current build instead of starting a concurrent build to build the new commit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xcode-plugin] (JENKINS-20916) Code Sign error: No matching provisioning profile found
Wojtek Siudzinski
commented on JENKINS-20916
Code Sign error: No matching provisioning profile found
Only thing I found to make it work is manually specifying provisioning profile as custom xcodebuild arguments:
1. Add Execute shell step before Xcode and place this:
echo "PROVISIONING_ID=`/usr/libexec/PlistBuddy -c 'Print UUID' /dev/stdin $(security cms -D -i ${WORKSPACE}/Resources/profile.mobileprovision)`" env.properties
(fix the path to provisioning file)
2. Add Inject environment variables step after Execute shell step and set Properties File Path to env.properties
3. In Xcode step, click Settings, then Advanced build settings... and fill Custom xcodebuild arguments with:
PROVISIONING_PROFILE=${PROVISIONING_ID}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26906) Re-introduce the ability to override the username/password at the specific job
Cletus DSouza commented on JENKINS-26906 Re-introduce the ability to override the username/password at the specific job This was created on behalf of Paul Adams This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26906) Re-introduce the ability to override the username/password at the specific job
Cletus DSouza updated JENKINS-26906 Re-introduce the ability to override the username/password at the specific job Still cannot release to jenkins-ci. Attaching the latest candidate version integrity-plugin.hpi 1.31 to this issue for user testing Change By: Cletus DSouza (11/Feb/15 5:29 PM) Attachment: integrity-plugin.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [simple-theme-plugin] (JENKINS-20058) Ability to change the favicon for Jenkins
Mark Chance
commented on JENKINS-20058
Ability to change the favicon for Jenkins
I have done this in the _javascript_:
function myFunction() {
head = document.getElementsByTagName('head');
title = head0.getElementsByTagName('title');
title0.innerHTML = title0.innerHTML.replace("Jenkins", "Nucleator");
links = head0.getElementsByTagName('link');
for (var i in links) {
link = linksi;
if (link.getAttribute('rel') == 'shortcut icon') {
link.setAttribute('href', '/userContent/favicon.ico');
break;
}
}
};
var body = document.getElementsByTagName('body');
if (window.addEventListener) {
window.addEventListener('load', myFunction, false);
}
else if (window.attachEvent) {
window.attachEvent('onload', myFunction );
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [simple-theme-plugin] (JENKINS-20058) Ability to change the favicon for Jenkins
Mark Chance
edited a comment on JENKINS-20058
Ability to change the favicon for Jenkins
I have done this in the _javascript_:
function myFunction() {
head = document.getElementsByTagName('head');
links = head0.getElementsByTagName('link');
for (var i in links) {
link = linksi;
if (link.getAttribute('rel') == 'shortcut icon') {
link.setAttribute('href', '/userContent/favicon.ico');
break;
}
}
};
var body = document.getElementsByTagName('body');
if (window.addEventListener) {
window.addEventListener('load', myFunction, false);
}
else if (window.attachEvent) {
window.attachEvent('onload', myFunction );
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26900) Hide flyweight master executor when ≥1 heavyweight executors running as subtasks
Yuriy Kryshchuk commented on JENKINS-26900 Hide flyweight master executor when ≥1 heavyweight executors running as subtasks From the other side, if we have the flow idle on user input we still need to see 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] [simple-theme-plugin] (JENKINS-20058) Ability to change the favicon for Jenkins
Mark Chance
edited a comment on JENKINS-20058
Ability to change the favicon for Jenkins
I have done this in the _javascript_:
function myFunction() {
head = document.getElementsByTagName('head');
links = head[0].getElementsByTagName('link');
for (var i in links) {
link = links[i];
if (link.getAttribute('rel') == 'shortcut icon') {
link.setAttribute('href', '/userContent/favicon.ico');
break;
}
}
};
var body = document.getElementsByTagName('body');
if (window.addEventListener) {
window.addEventListener('load', myFunction, false);
}
else if (window.attachEvent) {
window.attachEvent('onload', myFunction );
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-19007) copy artifacts via permalink for promoted builds shows wrong link
Tim Wood commented on JENKINS-19007 copy artifacts via permalink for promoted builds shows wrong link @ikedam Issue https://issues.jenkins-ci.org/browse/JENKINS-15086 contains a suggestion from @nathang which seems to work. It indirects from MyPromotingJob into the sub-job that contains the promoted artifact. I did some head-scratching to figure out the permalink, which was simpler than all my guesses. Permalink: PromotionLabel Artifact: myArtifact.tar.gz (no extraneous path elements needed.) However, I may have found a problem with that code: where it would seem to pick up the latest promotion, I think I found a case where it takes an old one. Thanks for the followup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [simple-theme-plugin] (JENKINS-26378) Simple Theme Plugin causes Jenkins to hang on Configure screen in LOADING state
Mark Chance
commented on JENKINS-26378
Simple Theme Plugin causes Jenkins to hang on Configure screen in LOADING state
I had a similar problem - with the plugin installed and my skinning _javascript_, the "Loading..." never went away. I think it has to do with event handlers, etc. Try this in your _javascript_:
function myFunction() {
// the stuff you want to do.
}
var body = document.getElementsByTagName('body');
if (window.addEventListener) {
window.addEventListener('load', myFunction, false);
}
else if (window.attachEvent) {
window.attachEvent('onload', myFunction );
}
Then it works fine. I didn't run into the other issues.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Grigoriy Milman resolved JENKINS-26770 as Fixed Apply doesnt work in version 1.29 of the plugin I have tested it. It works! Thanks for fast responses! Change By: Grigoriy Milman (11/Feb/15 7:02 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26908) Jenkins Windows should use C:\ProgramData\Jenkins as a working directory
Michael Cramer created JENKINS-26908 Jenkins Windows should use C:\ProgramData\Jenkins as a working directory Issue Type: Improvement Assignee: Unassigned Components: core Created: 11/Feb/15 7:07 PM Description: Jenkins installs itself to C:\Program Files (x86)\Jenkins. It then assumes that all working data should exist underneath this path. Due to the way User Account Control and other Windows Security mechanisms work, the appropriate location for any Jenkins working data should be separated out to C:\ProgramData\Jenkins. This includes the jobs, tools, plugins, etc. subfolders. The Jenkins Binary itself is okay (and preferable) to work out of the Program Files directory. But anything that Jenkins requires the ability to change should be moved out of this folder. Note: Separating these paths will break Jenkins' self-update mechanism. Alternatively, you can simply make Jenkins default install to C:\Jenkins on all Windows platforms. In this manner, UAC will not take effect. However, the aforementioned C:\ProgramData and C:\Program Files (x86) separation is the preferred Windows design. Environment: Jenkins 1.598, Windows Server 2012R2 Project: Jenkins Priority: Major Reporter: Michael Cramer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Cletus DSouza commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin Can you grab the latest hpi from JENKINS-26906 and test against that please? I added the ability to override the username/password at the job at the request of another user. Please make sure there is nothing in the latest fixes that comes as a surprise to you This latest snapshot will become the new release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth-plugin] (JENKINS-26909) Project-based security inheritance doesn't work
Igor Koyfman created JENKINS-26909 Project-based security inheritance doesnt work Issue Type: Bug Assignee: Jesse Glick Components: matrix-auth-plugin, security Created: 11/Feb/15 7:30 PM Description: Somewhat similar to JENKINS-10601, I can't get the job to properly inherit global permissions. I want authenticated users to not be able to build any jobs except for those that start the pipeline. So in my global permissions authenticated users don't have the build permission, and then I add it for some certain jobs. That does not work - every authenticated user can still build every job. I don't consider "Block inheritance of global authorization matrix" checkbox an appropriate fix for this issue. Project: Jenkins Priority: Major Reporter: Igor Koyfman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-26868) Add repack after cloning option to the 'reference' support in git clone
Nathan Neulinger commented on JENKINS-26868 Add repack after cloning option to the reference support in git clone Cool. That's a nice additional option in git. Sounds like it does equivalent to running a git repack -a afterwards, but probably a lot more efficient. Unfortunately, it'll be a while before 2.3 is available on many of the build agent systems, where 'git repack -a' works now. I'm just looking for something that would remove the dependency on the referenced repo after the cloning - to use it purely as a cache and not for live use. (Would be even nicer if the git plugin had some way of caching the repo on the master, but that's a major functionality change.) Seems like a checkbox to repack would be easy/simple way to accomplish 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] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Clifford Sanders commented on JENKINS-26493 Use new EC2 API endpoint hostnames Because we have to start our Jenkins slaves in eu-central-1 I made the changes here. I also had to upgrade the AWS SDK because the requests to eu-central need a Signature Version 4 (see Problem accessing eu-central-1 with API) There seem to be some problems with newer versions of the AWS SDK so I'll have to investigate this before doing a pull request. https://github.com/jenkinsci/ec2-plugin/pull/131 https://issues.jenkins-ci.org/browse/JENKINS-26854?focusedCommentId=221457page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-221457 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26899) Multiple domain authentication when not part of the same forest
Dan D commented on JENKINS-26899 Multiple domain authentication when not part of the same forest I'll try again regarding no spaces - but I'm sure I took out any whitespace (in the logs when i first started troubleshooting, I did see a whitespace initially when jenkins joined the single username to the attempted domain). It does seem to attempt to tack on both domains, but it seems it only asks one of the servers on the list. (I added two domain controllers for each domain separated by a comma as well) If the UNIX implementation is being called under the hood, a) can that implementation be configured to bind using 2 diff credentials and b) would i be able to hand edit the config file to configure it since GUI wouldn't 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] [vault-scm-plugin] (JENKINS-26487) NPE during SCM polling
Ken Overly
commented on JENKINS-26487
NPE during SCM polling
I have additional info to report. I was able to get the VaultSCM plugin running in a debugger to track down exactly where the NPE occurs.
It occurs at line 357 in method getVaultPath() in file VaultSCM.java. The Computer object is NULL and I'm trying to identify why.
VaultSCM.java
private String getVaultPath(Launcher launcher, TaskListener listener) throws InterruptedException, IOException {
final String defaultPath = "C:\\Program Files\\SourceGear\\Vault Client\\vault.exe";
final String defaultPathX86 = "C:\\Program Files (x86)\\SourceGear\\Vault Client\\vault.exe";
VaultSCMInstallation installation = getVault();
String pathToVault;
if (installation == null) {
// Check the first default location for vault...
if (checkVaultPath(defaultPath, launcher, listener)) {
pathToVault = defaultPath;
} else if (checkVaultPath(defaultPathX86, launcher, listener)) {
pathToVault = defaultPathX86;
} else {
listener.fatalError("Failed find vault client");
return null;
}
} else {
NPE-- installation = installation.forNode(Computer.currentComputer().getNode(), listener);
pathToVault = installation.getVaultLocation();
if (!checkVaultPath(pathToVault, launcher, listener)) {
listener.fatalError(pathToVault + " doesn't exist");
return null;
}
}
return pathToVault;
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
SCM/JIRA link daemon commented on JENKINS-25203 support embedded content in json Code changed in jenkins User: James Nord Path: pom.xml src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONParser.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberTestResultArchiver.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/DefaultTestResultParserImpl.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/EmbeddedItem.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioResult.java src/main/java/org/jenkinsci/plugins/cucumber/jsontestsupport/ScenarioToHTML.java src/test/java/org/jenkinsci/plugins/cucumber/jsontestsupport/CucumberJSONParserTest.java http://jenkins-ci.org/commit/cucumber-testresult-plugin/168125ae8bf99e7f7fd19e9166f9bb7f79234afc Log: ISSUE JENKINS-25203 Add support for embedded items in the json result. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-5856) Unable to Release a Git Project
Jan Klass commented on JENKINS-5856 Unable to Release a Git Project What is the reason behind that decision? Why does it not check out the branch? This is especially confusing as you already were branch-specific when specifying the branch specifier. When you specify the job shall build master, why does it not check out master? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-26901) Not possible to run freestyle job with non-set baseDirectory
Robert Kleinschmager created JENKINS-26901 Not possible to run freestyle job with non-set baseDirectory Issue Type: Bug Assignee: Robert Kleinschmager Components: weblogic-deployer-plugin Created: 11/Feb/15 3:24 PM Description: instead of using the workspace by default, the non-null (and not existing) directory will be mourned I will provide a patch via github Environment: release 2.12, freestyle project Project: Jenkins Priority: Minor Reporter: Robert Kleinschmager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26899) Multiple domain authentication when not part of the same forest
Daniel Beck commented on JENKINS-26899 Multiple domain authentication when not part of the same forest Make sure to only use a comma, don't add spaces before/after it. Could also be the usual problem that configuring anything on Windows invokes the Unix (LDAP) implementation, but doesn't show the options specific to 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] [active-directory-plugin] (JENKINS-26899) Multiple domain authentication when not part of the same forest
Dan D commented on JENKINS-26899 Multiple domain authentication when not part of the same forest Appreciate it. I believe the documentation makes the assumption that the domains must be in the same forest (due to some other related bugs in the tracker) but the docs do not explicitly state that, so I question the validity of that statement. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Cletus DSouza updated JENKINS-26770 Apply doesnt work in version 1.29 of the plugin This version will become the next integrity-plugin.hpi 1.31. Please use this to test as I cannot release to jenkins-ci at the moment. Change By: Cletus DSouza (11/Feb/15 2:53 PM) Attachment: integrity-plugin.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fxcop-runner-plugin] (JENKINS-26902) FxCop-Runner The Assembly Files textbox is preventing spaces in my path name from working.
Christopher Orr assigned JENKINS-26902 to Unassigned FxCop-Runner The Assembly Files textbox is preventing spaces in my path name from working. Change By: Christopher Orr (11/Feb/15 3:37 PM) Assignee: R.TylerCroy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26899) Multiple domain authentication when not part of the same forest
Dan D commented on JENKINS-26899 Multiple domain authentication when not part of the same forest Made sure there were no whitespaces in either the domain or the domain controller field. Same problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [flaky-test-handler-plugin] (JENKINS-26894) Can't run Deflake rebuild against multi-module project
Qingzhou Luo commented on JENKINS-26894 Cant run Deflake rebuild against multi-module project Thanks. I will try to add support for multi modules when I have 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] [extended-choice-parameter-plugin] (JENKINS-25187) Extended choice parameter multi level select list not populating
Len Isac closed JENKINS-25187 as Fixed Extended choice parameter multi level select list not populating Not sure what happened, but the issue is resolved.. Change By: Len Isac (11/Feb/15 3:45 PM) Status: Open Closed 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] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Grigoriy Milman commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin Just tested. Hpi for JENKINS-26906 works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26910) Null Pointer Exception if host/port/user is changed in global configuration page
Cletus DSouza created JENKINS-26910 Null Pointer Exception if host/port/user is changed in global configuration page Issue Type: Bug Assignee: Cletus DSouza Components: integrity-plugin Created: 11/Feb/15 7:58 PM Description: java.lang.NullPointerException at hudson.scm.IntegrityCheckpointAction.getProjectSettings(IntegrityCheckpointAction.java:218) at hudson.scm.IntegrityCheckpointAction.perform(IntegrityCheckpointAction.java:254) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1046) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:670) at hudson.model.Run.execute(Run.java:1743) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Environment: Jenkins 1.598 integrity-plugin v1.30 Project: Jenkins Priority: Major Reporter: Cletus DSouza This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-23052) Shallow clones should only pass '--tags' if opted-in
David Humeniuk commented on JENKINS-23052 Shallow clones should only pass --tags if opted-in Yeah, basically we have no way of doing a shallow clone and the fetch operation will often timeout after 30 minutes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26906) Re-introduce the ability to override the username/password at the specific job
Cletus DSouza resolved JENKINS-26906 as Fixed Re-introduce the ability to override the username/password at the specific job Resolved with 1.31 Change By: Cletus DSouza (11/Feb/15 9:16 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] [job-dsl-plugin] (JENKINS-26853) Add support for Custom Tools Plugin
Nick B commented on JENKINS-26853 Add support for Custom Tools Plugin 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] [job-dsl-plugin] (JENKINS-26853) Add support for Custom Tools Plugin
Daniel Spilker resolved JENKINS-26853 as Fixed Add support for Custom Tools Plugin Will be released in 1.30. Change By: Daniel Spilker (11/Feb/15 8:36 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] [weblogic-deployer-plugin] (JENKINS-26901) Not possible to run freestyle job with non-set baseDirectory
SCM/JIRA link daemon commented on JENKINS-26901 Not possible to run freestyle job with non-set baseDirectory Code changed in jenkins User: RaphC Path: src/main/java/org/jenkinsci/plugins/deploy/weblogic/FreeStyleJobArtifactSelectorImpl.java http://jenkins-ci.org/commit/weblogic-deployer-plugin/bac9f2dbd174c6e37894757522e78037bc6a Log: Merge pull request #2 from barclay-reg/master FIXED JENKINS-26901 Compare: https://github.com/jenkinsci/weblogic-deployer-plugin/compare/d83af6f65499...bac9f2dbd174 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-26901) Not possible to run freestyle job with non-set baseDirectory
SCM/JIRA link daemon resolved JENKINS-26901 as Fixed Not possible to run freestyle job with non-set baseDirectory Change By: SCM/JIRA link daemon (11/Feb/15 9:30 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] [weblogic-deployer-plugin] (JENKINS-26901) Not possible to run freestyle job with non-set baseDirectory
SCM/JIRA link daemon commented on JENKINS-26901 Not possible to run freestyle job with non-set baseDirectory Code changed in jenkins User: Robert Kleinschmager Path: src/main/java/org/jenkinsci/plugins/deploy/weblogic/FreeStyleJobArtifactSelectorImpl.java http://jenkins-ci.org/commit/weblogic-deployer-plugin/b91e9d63ddfef122919efa6a04ff9b5314069534 Log: FIXED JENKINS-26901 rearranged baseDirectory checks to allow non-null baseDirectory to lead to search in workspace directory This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26908) Jenkins Windows should use C:\ProgramData\Jenkins as a working directory
Michael Cramer commented on JENKINS-26908 Jenkins Windows should use C:\ProgramData\Jenkins as a working directory Perhaps only the service wrapper needs to be in Program Files, while the remaining Jenkins files go into C:\ProgramData? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26890) custom workspace not properly resolving global environment variable
Dan Franklin resolved JENKINS-26890 as Not A Defect custom workspace not properly resolving global environment variable Argh. I did get the environment variable name wrong when I tried to use it. I tried it now and it's working. Sorry! Change By: Dan Franklin (11/Feb/15 8:42 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26910) Null Pointer Exception if host/port/user is changed in global configuration page
Cletus DSouza resolved JENKINS-26910 as Fixed Null Pointer Exception if host/port/user is changed in global configuration page Resolved with 1.31 Change By: Cletus DSouza (11/Feb/15 9:16 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] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Grigoriy Milman commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin By the way, on our production Jenkins server we will use the official plugin 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/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-25523) Multiple SCMs Plugin doesn't work with Mercurial plugin 1.51
Oliver Kuster commented on JENKINS-25523 Multiple SCMs Plugin doesnt work with Mercurial plugin 1.51 A similar thing happened to me. Moving a project from CVS to Mercurial. Jenkins ver. 1.579 Mercurial Plugin 1.51 FATAL: hudson.scm.CvsRevisionState cannot be cast to hudson.plugins.mercurial.MercurialTagAction java.lang.ClassCastException: hudson.scm.CvsRevisionState cannot be cast to hudson.plugins.mercurial.MercurialTagAction at hudson.plugins.mercurial.MercurialSCM.determineChanges(MercurialSCM.java:603) at hudson.plugins.mercurial.MercurialSCM.checkout(MercurialSCM.java:552) at hudson.scm.SCM.checkout(SCM.java:488) at hudson.model.AbstractProject.checkout(AbstractProject.java:1253) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:622) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:528) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Disabling Changelog in the advanced options is a valid workaround... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26906) Re-introduce the ability to override the username/password at the specific job
SCM/JIRA link daemon commented on JENKINS-26906 Re-introduce the ability to override the username/password at the specific job Code changed in jenkins User: Cletus D'Souza Path: pom.xml src/main/java/hudson/scm/IntegrityCheckinAction.java src/main/java/hudson/scm/IntegrityCheckpointAction.java src/main/java/hudson/scm/IntegrityConfigurable.java src/main/java/hudson/scm/IntegrityItemAction.java src/main/java/hudson/scm/IntegritySCM.java src/main/resources/hudson/scm/IntegritySCM/global.jelly http://jenkins-ci.org/commit/integrity-plugin/b72bd21fd4c8b085ae0a43c6bd6a5922a1d23155 Log: Completed fixes for the following: FIXED JENKINS-26906 Re-introduce the ability to override the username/password at the specific job FIXED JENKINS-26910 Null Pointer Exception if host/port/user is changed in global configuration page This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Cletus DSouza commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin Just found an issue with the new credential management. If you change a particular hostname/port/user global config page then that changes the ID and can potentially cause a NPE if you don't go back and change it under each job. I will implement a unique ID that will guard against such NPE from a rename/change. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26910) Null Pointer Exception if host/port/user is changed in global configuration page
SCM/JIRA link daemon commented on JENKINS-26910 Null Pointer Exception if host/port/user is changed in global configuration page Code changed in jenkins User: Cletus D'Souza Path: pom.xml src/main/java/hudson/scm/IntegrityCheckinAction.java src/main/java/hudson/scm/IntegrityCheckpointAction.java src/main/java/hudson/scm/IntegrityConfigurable.java src/main/java/hudson/scm/IntegrityItemAction.java src/main/java/hudson/scm/IntegritySCM.java src/main/resources/hudson/scm/IntegritySCM/global.jelly http://jenkins-ci.org/commit/integrity-plugin/b72bd21fd4c8b085ae0a43c6bd6a5922a1d23155 Log: Completed fixes for the following: FIXED JENKINS-26906 Re-introduce the ability to override the username/password at the specific job FIXED JENKINS-26910 Null Pointer Exception if host/port/user is changed in global configuration page This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim-plugin] (JENKINS-23513) Claim plugin doesn't allow you to claim unstable builds.
Brian Smith commented on JENKINS-23513 Claim plugin doesnt allow you to claim unstable builds. Looking into it a bit more it would seem that it is just the Matrix build jobs that you can't Claim (either failed or unstable)? Other unstable jobs that I checked recently have the Claim option available. I don't recall if my initial JIRA was entered after I was looking at a Matrix job 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] [warnings-plugin] (JENKINS-11225) Add aggregation and subview for multi-configuration projects
Roland Schulz commented on JENKINS-11225 Add aggregation and subview for multi-configuration projects I meant those 3 options as alternatives (of which the easiest to do would suffice) not as 3 independent things. Thus I only created one issue: 26913. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26797) Zombie instance created by the EC2 plugins
Michael Lieberman commented on JENKINS-26797 Zombie instance created by the EC2 plugins I also noticed that these instances do count towards the instance cap though they don't show up as slaves in Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26911) Can't access /userContent when not logged in
Mark Chance created JENKINS-26911 Cant access /userContent when not logged in Issue Type: Bug Assignee: Unassigned Components: core Created: 11/Feb/15 11:45 PM Description: I have Matrix authentication turned on, with no access for anonymous. I am using the Simple Theme Plugin to skin the UI. This all is fine, except that when not logged in, Jenkins returns a 403 error on my css and js files in /userContent resulting in the default Jenkins appearance. This page https://wiki.jenkins-ci.org/display/JENKINS/User+Content states: "Note that these files are not subject to any access controls." And, I can't figure out how to add my files to the whitelist. Environment: Jenkins 1.598 Project: Jenkins Priority: Minor Reporter: Mark Chance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp-plugin] (JENKINS-26907) HockeyApp Configuration Lost after Jenkins Restart
Jedi Lewis commented on JENKINS-26907 HockeyApp Configuration Lost after Jenkins Restart The problem appears to be the way the plugin is saving the schemaVersion parameter. When you save the job, it saves the schemaVersion is an XML element, Jenkins will lose the configuration: hockeyapp.HockeyappRecorder schemaVersion2/schemaVersion Here is the fixed version. When it's saved as an attribute of hockeyapp.HockeyappRecorder, it will retain the HockeyApp configuration across Jenkins restarts, but saving the job again will reset the attribute to be an Element instead and thus break the plugin. hockeyapp.HockeyappRecorder schemaVersion="2" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26912) 'build' workflow command ignores parameters, triggering default-only builds
James VL created JENKINS-26912 build workflow command ignores parameters, triggering default-only builds Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 11/Feb/15 11:55 PM Description: Summary It appears "Build a Job" in the Workflow DSL is not properly passing parameters to the jobs it builds. Sample Code build job: 'My Test Job', version: 'master' Where 'My Test Job' is normal Jenkins job. Expect to See Jenkins execute the job named 'My Test Job', setting its expected parameter named 'version' to the value 'master'. Actually See 'My Test Job' is run, but with whatever the default value is for 'version', not the value 'master'. Further notes: I tried various other formats of passing parameters to the build command (name, unnamed, key value list in a string...), but none worked. The snippet generator was not very helpful in trying to guess what to send. The Snippet Generator says of parameters: "parameters may be bound to a list of ParameterValues." and generates sample code: build 'My Test Job' I would welcome clarification in the snippet builder on how to use it with jobs that take parameters. It does not demonstrate or describe that the job name must be passed as the 'job' parameter. Environment: Jenkins 1.598 on Linux w/ Workflow 1.2 Project: Jenkins Priority: Major Reporter: James VL This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26914) Can't use prefixed ABIs
jsotuyod created JENKINS-26914 Cant use prefixed ABIs Issue Type: Bug Assignee: Christopher Orr Components: android-emulator-plugin Created: 12/Feb/15 12:17 AM Description: Android Wear and Lollipop has started prefixing the ABIs. For instance, this is the output of `android list target` for Google Services version of Lollipop: id: 25 or "Google Inc.:Google APIs:21" Name: Google APIs Type: Add-On Vendor: Google Inc. Revision: 1 Description: Android + Google APIs Based on Android 5.0.1 (API level 21) Libraries: com.android.future.usb.accessory (usb.jar) API for USB Accessories com.google.android.media.effects (effects.jar) Collection of video effects com.google.android.maps (maps.jar) API for Google Maps Skins: HVGA, QVGA, WQVGA400, WQVGA432, WSVGA, WVGA800 (default), WVGA854, WXGA720, WXGA800, WXGA800-7in Tag/ABIs : google_apis/armeabi-v7a, google_apis/x86, google_apis/x86_64 As seen, the ABIs are prefixed. If no prefix is included during configuration, AVD creation fails due to an invalid --tag. If properly set, the form complains of an unrecognized ABI (minor issue), but then fails to create the AVD due to naming issues, for example: android create avd -f -a -s WVGA800 -n hudson_en-US_320_WVGA_Google_Inc._Google_APIs_21_google-apis/x86-64 -t "Google Inc.:Google APIs:21" --abi google_apis/x86_64 android Failed to run AVD creation command Error: AVD name 'hudson_en-US_320_WVGA_Google_Inc._Google_APIs_21_google-apis/x86-64' contains invalid characters. Allowed characters are: a-z A-Z 0-9 . _ - Either way, it's not possible to use the latest target APIs with the current version of the plugin. Project: Jenkins Priority: Minor Reporter: jsotuyod This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-23700) Maven projects should default to search the target folder
Raphael CHAUMIER commented on JENKINS-23700 Maven projects should default to search the target folder Hi Can you tell if it's a freestyle jenkins job type or a maven one. 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] [warnings-plugin] (JENKINS-26913) Add more information about warnings for multi-configuration projects
Roland Schulz created JENKINS-26913 Add more information about warnings for multi-configuration projects Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-plugin Created: 11/Feb/15 11:59 PM Description: Currently it isn't possible to see which configurations of a multi-configuration project cause which compiler warnings. At the root level only a list of all warnings are shown. And one needs to look at the individual configuration to see which warning is produced by which configuration. This information could be presented multiple ways including: show the configuration name as extra information (for "Folder", "Files" and "Warnings" tabs it could be its own column. For details it should be added to the header) add a new tab "Configuration". It works like "Details" but the warnings are grouped by configurations have the whole table with the tabs shown once per configuration Project: Jenkins Priority: Minor Reporter: Roland Schulz This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26914) Can't use prefixed ABIs
jsotuyod
updated JENKINS-26914
Cant use prefixed ABIs
Change By:
jsotuyod
(12/Feb/15 12:20 AM)
Description:
AndroidWearandLollipophasstartedprefixingtheABIs.Forinstance,thisistheoutputof`androidlisttarget`forGoogleServicesversionofLollipop:
{quote}
id:25orGoogleInc.:GoogleAPIs:21Name:GoogleAPIsType:Add-OnVendor:GoogleInc.Revision:1Description:Android+GoogleAPIsBasedonAndroid5.0.1(APIlevel21)Libraries:*com.android.future.usb.accessory(usb.jar)APIforUSBAccessories*com.google.android.media.effects(effects.jar)Collectionofvideoeffects*com.google.android.maps(maps.jar)APIforGoogleMapsSkins:HVGA,QVGA,WQVGA400,WQVGA432,WSVGA,WVGA800(default),WVGA854,WXGA720,WXGA800,WXGA800-7inTag/ABIs:google_apis/armeabi-v7a,google_apis/x86,google_apis/x86_64
{quote}
Asseen,theABIsareprefixed.Ifnoprefixisincludedduringconfiguration,AVDcreationfailsduetoaninvalid--tag.Ifproperlyset,theformcomplainsofanunrecognizedABI(minorissue),butthenfailstocreatetheAVDduetonamingissues,forexample:
{quote}
androidcreateavd-f-a-sWVGA800-nhudson_en-US_320_WVGA_Google_Inc._Google_APIs_21_google-apis/x86-64-tGoogleInc.:GoogleAPIs:21--abigoogle_apis/x86_64[android]FailedtorunAVDcreationcommand Error:AVDnamehudson_en-US_320_WVGA_Google_Inc._Google_APIs_21_google-apis/x86-64containsinvalidcharacters. Allowedcharactersare:a-zA-Z0-9._-
{quote}
Eitherway,itsnotpossibletousethelatesttargetAPIswiththecurrentversionoftheplugin.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop 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-15627) Using MacOS slave in 1.487 - Can't connect to window server - not enough permissions
lata kopalle commented on JENKINS-15627 Using MacOS slave in 1.487 - Cant connect to window server - not enough permissions thanks for the workaround Andrey, it just saved our day. Our Jenkins version: 1.533, Master on windows. Issue seen with on Mac OS X 10.9 slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multi-slave-config-plugin] (JENKINS-22904) No string replacement when mass-creating SSHLauncher slaves
Perrin Morrow commented on JENKINS-22904 No string replacement when mass-creating SSHLauncher slaves It also does not replace $NAME in the SSH host field. So unless I've missed something, it's not currently possible to create multiple SSH-launcher slaves with unique host names. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26893) Unable to run emulator-arm to start emulator
Wesley Archbell edited a comment on JENKINS-26893 Unable to run emulator-arm to start emulator nope. not permissions issue. emulator-arm executable does not exist (only emulator64-arm) Wesleys-MacBook-Pro:tools wesley$ ls -la /Users/wesley/apps/android/sdk/tools total 19416 drwxr-xr-x 26 wesley staff 884 31 Dec 13:05 . drwxrwxr-x@ 14 wesley staff 476 31 Dec 13:05 .. rw-rr- 1 wesley staff 763411 31 Dec 13:05 NOTICE.txt -rwxr-xr-x 1 wesley staff 3498 31 Dec 13:05 android drwxr-xr-x 5 wesley staff 170 31 Dec 13:05 ant drwxr-xr-x 3 wesley staff 102 31 Dec 13:05 apps -rwxr-xr-x 1 wesley staff 3286 31 Dec 13:05 ddms -rwxr-xr-x 1 wesley staff 1940 31 Dec 13:05 draw9patch -rwxr-xr-x 1 wesley staff46444 31 Dec 13:05 emulator -rwxr-xr-x 1 wesley staff 3015608 31 Dec 13:05 emulator64-arm -rwxr-xr-x 1 wesley staff 2906988 31 Dec 13:05 emulator64-mips -rwxr-xr-x 1 wesley staff 3113608 31 Dec 13:05 emulator64-x86 -rwxr-xr-x 1 wesley staff 3464 31 Dec 13:05 hierarchyviewer -rwxr-xr-x 1 wesley staff 1845 31 Dec 13:05 jobb drwxr-xr-x 82 wesley staff 2788 31 Dec 13:05 lib -rwxr-xr-x 1 wesley staff 2046 31 Dec 13:05 lint -rwxr-xr-x 1 wesley staff13892 31 Dec 13:05 mksdcard -rwxr-xr-x 1 wesley staff 1293 31 Dec 13:05 monitor -rwxr-xr-x 1 wesley staff 3176 31 Dec 13:05 monkeyrunner drwxr-xr-x 12 wesley staff 408 31 Dec 13:05 proguard -rwxr-xr-x 1 wesley staff 2259 31 Dec 13:05 screenshot2 rw-rr- 1 wesley staff16545 31 Dec 13:05 source.properties drwxr-xr-x 11 wesley staff 374 31 Dec 13:05 support drwxr-xr-x 6 wesley staff 204 31 Dec 13:05 templates -rwxr-xr-x 1 wesley staff 3219 31 Dec 13:05 traceview -rwxr-xr-x 1 wesley staff 3054 31 Dec 13:05 uiautomatorviewer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26893) Unable to run emulator-arm to start emulator
Wesley Archbell commented on JENKINS-26893 Unable to run emulator-arm to start emulator nope. not permissions issue. not an emulator-arm executable (only emulator64-arm) Wesleys-MacBook-Pro:tools wesley$ ls -la /Users/wesley/apps/android/sdk/tools total 19416 drwxr-xr-x 26 wesley staff 884 31 Dec 13:05 . drwxrwxr-x@ 14 wesley staff 476 31 Dec 13:05 .. rw-rr- 1 wesley staff 763411 31 Dec 13:05 NOTICE.txt -rwxr-xr-x 1 wesley staff 3498 31 Dec 13:05 android drwxr-xr-x 5 wesley staff 170 31 Dec 13:05 ant drwxr-xr-x 3 wesley staff 102 31 Dec 13:05 apps -rwxr-xr-x 1 wesley staff 3286 31 Dec 13:05 ddms -rwxr-xr-x 1 wesley staff 1940 31 Dec 13:05 draw9patch -rwxr-xr-x 1 wesley staff46444 31 Dec 13:05 emulator -rwxr-xr-x 1 wesley staff 3015608 31 Dec 13:05 emulator64-arm -rwxr-xr-x 1 wesley staff 2906988 31 Dec 13:05 emulator64-mips -rwxr-xr-x 1 wesley staff 3113608 31 Dec 13:05 emulator64-x86 -rwxr-xr-x 1 wesley staff 3464 31 Dec 13:05 hierarchyviewer -rwxr-xr-x 1 wesley staff 1845 31 Dec 13:05 jobb drwxr-xr-x 82 wesley staff 2788 31 Dec 13:05 lib -rwxr-xr-x 1 wesley staff 2046 31 Dec 13:05 lint -rwxr-xr-x 1 wesley staff13892 31 Dec 13:05 mksdcard -rwxr-xr-x 1 wesley staff 1293 31 Dec 13:05 monitor -rwxr-xr-x 1 wesley staff 3176 31 Dec 13:05 monkeyrunner drwxr-xr-x 12 wesley staff 408 31 Dec 13:05 proguard -rwxr-xr-x 1 wesley staff 2259 31 Dec 13:05 screenshot2 rw-rr- 1 wesley staff16545 31 Dec 13:05 source.properties drwxr-xr-x 11 wesley staff 374 31 Dec 13:05 support drwxr-xr-x 6 wesley staff 204 31 Dec 13:05 templates -rwxr-xr-x 1 wesley staff 3219 31 Dec 13:05 traceview -rwxr-xr-x 1 wesley staff 3054 31 Dec 13:05 uiautomatorviewer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26915) Create saltstack-plugin component
Christian McHugh created JENKINS-26915 Create saltstack-plugin component Issue Type: Task Assignee: Unassigned Components: core Created: 12/Feb/15 3:10 AM Description: Please create a saltstack-plugin component in jira to track the jenkins plugin of the same name. Project: Jenkins Priority: Trivial Reporter: Christian McHugh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26893) Unable to run emulator-arm to start emulator
Wesley Archbell edited a comment on JENKINS-26893 Unable to run emulator-arm to start emulator sorry yes its for OS X 10.10, not permissions issue. emulator-arm executable does not exist (only emulator64-arm) Wesleys-MacBook-Pro:tools wesley$ ls -la /Users/wesley/apps/android/sdk/tools total 19416 drwxr-xr-x 26 wesley staff 884 31 Dec 13:05 . drwxrwxr-x@ 14 wesley staff 476 31 Dec 13:05 .. rw-rr- 1 wesley staff 763411 31 Dec 13:05 NOTICE.txt -rwxr-xr-x 1 wesley staff 3498 31 Dec 13:05 android drwxr-xr-x 5 wesley staff 170 31 Dec 13:05 ant drwxr-xr-x 3 wesley staff 102 31 Dec 13:05 apps -rwxr-xr-x 1 wesley staff 3286 31 Dec 13:05 ddms -rwxr-xr-x 1 wesley staff 1940 31 Dec 13:05 draw9patch -rwxr-xr-x 1 wesley staff46444 31 Dec 13:05 emulator -rwxr-xr-x 1 wesley staff 3015608 31 Dec 13:05 emulator64-arm -rwxr-xr-x 1 wesley staff 2906988 31 Dec 13:05 emulator64-mips -rwxr-xr-x 1 wesley staff 3113608 31 Dec 13:05 emulator64-x86 -rwxr-xr-x 1 wesley staff 3464 31 Dec 13:05 hierarchyviewer -rwxr-xr-x 1 wesley staff 1845 31 Dec 13:05 jobb drwxr-xr-x 82 wesley staff 2788 31 Dec 13:05 lib -rwxr-xr-x 1 wesley staff 2046 31 Dec 13:05 lint -rwxr-xr-x 1 wesley staff13892 31 Dec 13:05 mksdcard -rwxr-xr-x 1 wesley staff 1293 31 Dec 13:05 monitor -rwxr-xr-x 1 wesley staff 3176 31 Dec 13:05 monkeyrunner drwxr-xr-x 12 wesley staff 408 31 Dec 13:05 proguard -rwxr-xr-x 1 wesley staff 2259 31 Dec 13:05 screenshot2 rw-rr- 1 wesley staff16545 31 Dec 13:05 source.properties drwxr-xr-x 11 wesley staff 374 31 Dec 13:05 support drwxr-xr-x 6 wesley staff 204 31 Dec 13:05 templates -rwxr-xr-x 1 wesley staff 3219 31 Dec 13:05 traceview -rwxr-xr-x 1 wesley staff 3054 31 Dec 13:05 uiautomatorviewer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator-plugin] (JENKINS-26893) Unable to run emulator-arm to start emulator
Wesley Archbell updated JENKINS-26893 Unable to run emulator-arm to start emulator Change By: Wesley Archbell (12/Feb/15 12:56 AM) Environment: OSX:10. 2.2 10 ,Jenkinsver.1.598,AndroidEmulatorPlugin2.12,AndroidPlatformTools21 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink-plugin] (JENKINS-26000) Invalid processing of suite-files in testng
A B updated JENKINS-26000 Invalid processing of suite-files in testng The file ok63.xml is the XML RPC exchange between the plugin and testlink for build 63 where the second test is present Change By: A B (11/Feb/15 9:31 AM) Attachment: ok63.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Waldek M commented on JENKINS-24946 JUnit Tests Results fail to archive in V1.582 You may want to upgrade core version. I was on 1.586 and upgrade finally solved it for me, as advised by Daniel Beck above. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [show-build-parameters] (JENKINS-26896) Show build parameters on build start
Sean Flanigan created JENKINS-26896 Show build parameters on build start Issue Type: Improvement Assignee: Peter Hayes Components: show-build-parameters Created: 11/Feb/15 10:04 AM Description: It would be nice if the build parameters were shown as soon as the build started, not only on completion. Environment: RHEL 7, Jenkins ver. 1.580.3 LTS rpm, openjdk 1.7.0_51, SSH slaves Project: Jenkins Labels: performance user-experience Priority: Minor Reporter: Sean Flanigan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Kent Granström commented on JENKINS-24946 JUnit Tests Results fail to archive in V1.582 Silly me RTFM before writing... Thanx Waldek M This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26895) Exception if Dashboard View plugin is not installed
Paolo Borelli created JENKINS-26895 Exception if Dashboard View plugin is not installed Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 11/Feb/15 8:12 AM Description: I have this excpetion in the logs. I am assuming it comes from the copyartifact plugin from the backtrace Feb 11, 2015 8:13:20 AM WARNING hudson.ExtensionFinder$GuiceFinder$SezpozModule configure Failed to load hudson.plugins.release.dashboard.RecentReleasesPortlet$DescriptorImpl java.lang.LinkageError: Failed to resolve class hudson.plugins.release.dashboard.RecentReleasesPortlet$DescriptorImpl at hudson.ExtensionFinder$GuiceFinder$SezpozModule.resolve(ExtensionFinder.java:491) at hudson.ExtensionFinder$GuiceFinder$SezpozModule.configure(ExtensionFinder.java:524) at com.google.inject.AbstractModule.configure(AbstractModule.java:62) at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:253) at com.google.inject.spi.Elements.getElements(Elements.java:108) at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:135) at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:104) at com.google.inject.Guice.createInjector(Guice.java:96) at com.google.inject.Guice.createInjector(Guice.java:73) at hudson.ExtensionFinder$GuiceFinder.init(ExtensionFinder.java:279) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at java.lang.Class.newInstance(Class.java:379) at net.java.sezpoz.IndexItem.instance(IndexItem.java:181) at hudson.ExtensionFinder$Sezpoz._find(ExtensionFinder.java:642) at hudson.ExtensionFinder$Sezpoz.find(ExtensionFinder.java:617) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:371) at hudson.ExtensionList.load(ExtensionList.java:300) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253) at hudson.ExtensionList.iterator(ExtensionList.java:143) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:364) at hudson.ExtensionList.load(ExtensionList.java:300) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253) at hudson.ExtensionList.iterator(ExtensionList.java:143) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1191) at hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:99) at hudson.plugins.copyartifact.CopyArtifactPlugin.postInitialize(CopyArtifactPlugin.java:35) at hudson.PluginManager$2$1$2.run(PluginManager.java:386) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Environment: jenkins 1.598 copyartifact plugin 1.34 Project: Jenkins Priority: Minor Reporter: Paolo Borelli This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators.
[JIRA] [flaky-test-handler-plugin] (JENKINS-26894) Can't run Deflake rebuild against multi-module project
Daniel Beck updated JENKINS-26894 Cant run Deflake rebuild against multi-module project Assigning to plugin maintainer (will need to change default assignee later) Change By: Daniel Beck (11/Feb/15 9:00 AM) Assignee: DanielBeck QingzhouLuo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-11149) JNLP slave fails to connect if Anonymous has not permission READ
Ciaran Liedeman commented on JENKINS-11149 JNLP slave fails to connect if Anonymous has not permission READ This issue can be closed In the latest version of jenkins (1.598) and I'm sure its been there for a while. You only have to enable slave connect permission for anonymous which will allow JNLP Slaves to connect without affecting the login screen. Ciaran This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26770) 'Apply' doesn't work in version 1.29 of the plugin
Daniel Beck commented on JENKINS-26770 Apply doesnt work in version 1.29 of the plugin FYI see https://wiki.jenkins-ci.org/display/JENKINS/contributing#contributing-CommitMessages on how to write commit messages to get the bot to close the related issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink-plugin] (JENKINS-26000) Invalid processing of suite-files in testng
A B commented on JENKINS-26000 Invalid processing of suite-files in testng A added two more files: ko62.xml and ok63.xml containing the XML RPC messages exchanged between the plugin and testlink. The main difference is at the end: ko62.xml: the plugin sends back only one test case result ok63.xml: the plugin sends back two test case results the builds 62 and 63 use the same set of test cases, but for 62 they are structured into suites, and in 63 they are in the same suite. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-22267) Upgrade to advanced mode is somehow not persisted to disk
Asmund Ostvold commented on JENKINS-22267 Upgrade to advanced mode is somehow not persisted to disk What type of information can I provide to help resolve this issue? Jenkins ver. 1.580.2 Priority Sorter Plugin 2.9 inheritance-plugin 1.5.3 I am willing to turn on logging if I am told how to. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Kent Granström reopened JENKINS-24946 JUnit Tests Results fail to archive in V1.582 Encountered this problem on 1.583 when installing v1.3 of jUnit. Tried v1.4, same result. Manually resinstalled v1.2 works. The problem is still in there somewhere ... Archiving artifacts Recording test results ERROR: Publisher hudson.tasks.junit.JUnitResultArchiver aborted due to exception java.lang.NoClassDefFoundError: hudson/tasks/junit/JUnitParser$ParseResultCallable at hudson.tasks.junit.JUnitParser.parseResult(JUnitParser.java:90) at hudson.tasks.junit.JUnitResultArchiver.parse(JUnitResultArchiver.java:120) at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:137) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1770) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Change By: Kent Granström (11/Feb/15 9:51 AM) Resolution: CannotReproduce 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] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
cepnyci commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection We configured the slaves to connect via JNLP. No more experiencing this 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/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-22267) Upgrade to advanced mode is somehow not persisted to disk
Magnus Sandberg commented on JENKINS-22267 Upgrade to advanced mode is somehow not persisted to disk This it not something I have ever been able to reproduce so I'm a bit in the dark here. Do you get any errors in the "normal" jenkins logs? Do you have a very large installation with many jobs? How long does the conversion take until Jenkins tells you it is done? Do you have your old data left or is it destroyed by the conversion? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink-plugin] (JENKINS-26000) Invalid processing of suite-files in testng
A B updated JENKINS-26000 Invalid processing of suite-files in testng XML RPC exchange for build 62 where the second test is not run Change By: A B (11/Feb/15 9:29 AM) Attachment: ko62.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26890) custom workspace not properly resolving global environment variable
Daniel Beck commented on JENKINS-26890 custom workspace not properly resolving global environment variable Where is that variable defined? Note that your report is mentioning two different variables. FWIW I don't know whether custom workspace has any variable resolution, it may simply not support this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink-plugin] (JENKINS-26000) Invalid processing of suite-files in testng
A B edited a comment on JENKINS-26000 Invalid processing of suite-files in testng The file ko62.xml is the XML RPC exchange between the plugin and testlink for build 62 where the second test is not run This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mantis-plugin] (JENKINS-26831) Mantis password written in plain text in build.xml
sogabe started work on JENKINS-26831 Mantis password written in plain text in build.xml Change By: sogabe (11/Feb/15 10:56 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-24946) JUnit Tests Results fail to archive in V1.582
Kent Granström resolved JENKINS-24946 as Cannot Reproduce JUnit Tests Results fail to archive in V1.582 Reverting issue to its previous state since it is explained in the comments why it doesn't work with 1.583. The release-notes for the plugin however should perhaps state the incompatibility even though it is compatible with later versions of Jenkins. Change By: Kent Granström (11/Feb/15 10:56 AM) Status: Reopened Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-26113) REST api needed to get individual warnings values, not combined ones
Morne Joubert
commented on JENKINS-26113
REST api needed to get individual warnings values, not combined ones
I added the following in AggregatedWarningsProjectAction.java
@Exported
public ListWarningsResultAction getWarningsResultAction() {
ListWarningsResultAction projectActions;
// projectActions = this.getProject().getActions(WarningsResultAction.class);
// can't use project, its actions list is allways empty
// try getting the actions of the last build
projectActions = this.getLastFinishedBuild().getActions(WarningsResultAction.class);
return projectActions;
}
Inside WarningsResultAction.java i then added the exported and visibility fields
@Exported(visibility = 2)
@Override
public String getUrlName() {
return WarningsDescriptor.getResultUrl(parserName);
}
/**
Returns the parser group this result belongs to.
*
@return the parser group
*/
@Exported(visibility = 2)
public String getParser() {
return parserName;
}
@Exported(visibility = 2)
@Override
public String getDisplayName() {
return ParserRegistry.getParser(parserName).getLinkName().toString();
}
the ../warnings/api/xml REST api then gives me:
aggregatedWarningsProjectAction
displayNameCompiler Warnings/displayName
lastFinishedBuild
number344/number
url
http://localhost:8080/job/code_coverage/job/Build_L1PHY_el1c_task_test_MAT_gcc/344/
/url
/lastFinishedBuild
warningsResultAction
displayNameGNU C Compiler Warnings/displayName
parserGNU C Compiler 4 (gcc)/parser
urlNamewarnings18Result/urlName
/warningsResultAction
warningsResultAction
displayNamePC-Lint Warnings/displayName
parserPC-Lint/parser
urlNamewarnings0Result/urlName
/warningsResultAction
/aggregatedWarningsProjectAction
So i now get the urlName and parser name i can use.
This is for a project, so to get the actual values for a particular build i can then do the calls to the particular parser urls.
if i do ../warnings/api/xml?depth=2 then i get the full value tree (for the last build)
warningsResultAction
namewarnings/name
result
newSuccessfulHighScorefalse/newSuccessfulHighScore
newZeroWarningsHighScorefalse/newZeroWarningsHighScore
numberOfFixedWarnings0/numberOfFixedWarnings
numberOfHighPriorityWarnings0/numberOfHighPriorityWarnings
numberOfLowPriorityWarnings0/numberOfLowPriorityWarnings
numberOfNewWarnings0/numberOfNewWarnings
numberOfNormalPriorityWarnings2/numberOfNormalPriorityWarnings
numberOfWarnings2/numberOfWarnings
pluginResultSUCCESS/pluginResult
referenceBuild
number343/number
url
http://localhost:8080/job/code_coverage/job/Build_L1PHY_el1c_task_test_MAT_gcc/343/
/url
/referenceBuild
successfulHighScore0/successfulHighScore
successfulSinceBuild0/successfulSinceBuild
successfulSinceDate0/successfulSinceDate
warning/
warning/
warningsDelta0/warningsDelta
zeroWarningsHighScore1200233384/zeroWarningsHighScore
zeroWarningsSinceBuild0/zeroWarningsSinceBuild
zeroWarningsSinceDate0/zeroWarningsSinceDate
/result
successfultrue/successful
displayNameGNU C Compiler Warnings/displayName
parserGNU C Compiler 4 (gcc)/parser
urlNamewarnings18Result/urlName
/warningsResultAction
if i call .../buildNumber/warningsResult/api/xml
then i get the collated values for a particular build.
where do i need to add code to get the list of warnings actions in the /warningsResult/ call ?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-26113) REST api needed to get individual warnings values, not combined ones
Morne Joubert
edited a comment on JENKINS-26113
REST api needed to get individual warnings values, not combined ones
I added the following in AggregatedWarningsProjectAction.java
@Exported
public ListWarningsResultAction getWarningsResultAction() {
ListWarningsResultAction projectActions;
// projectActions = this.getProject().getActions(WarningsResultAction.class);
// can't use project, its actions list is allways empty
// try getting the actions of the last build
projectActions = this.getLastFinishedBuild().getActions(WarningsResultAction.class);
return projectActions;
}
Inside WarningsResultAction.java i then added the exported and visibility fields
@Exported(visibility = 2)
@Override
public String getUrlName() {
return WarningsDescriptor.getResultUrl(parserName);
}
/**
* Returns the parser group this result belongs to.
*
* @return the parser group
*/
@Exported(visibility = 2)
public String getParser() {
return parserName;
}
@Exported(visibility = 2)
@Override
public String getDisplayName() {
return ParserRegistry.getParser(parserName).getLinkName().toString();
}
the ../warnings/api/xml REST api then gives me:
aggregatedWarningsProjectAction
displayNameCompiler Warnings/displayName
lastFinishedBuild
number344/number
url
http://localhost:8080/job/code_coverage/job/Build_L1PHY_el1c_task_test_MAT_gcc/344/
/url
/lastFinishedBuild
warningsResultAction
displayNameGNU C Compiler Warnings/displayName
parserGNU C Compiler 4 (gcc)/parser
urlNamewarnings18Result/urlName
/warningsResultAction
warningsResultAction
displayNamePC-Lint Warnings/displayName
parserPC-Lint/parser
urlNamewarnings0Result/urlName
/warningsResultAction
/aggregatedWarningsProjectAction
So i now get the urlName and parser name i can use.
This is for a project, so to get the actual values for a particular build i can then do the calls to the particular parser urls.
if i do ../warnings/api/xml?depth=2 then i get the full value tree (for the last build)
warningsResultAction
namewarnings/name
result
newSuccessfulHighScorefalse/newSuccessfulHighScore
newZeroWarningsHighScorefalse/newZeroWarningsHighScore
numberOfFixedWarnings0/numberOfFixedWarnings
numberOfHighPriorityWarnings0/numberOfHighPriorityWarnings
numberOfLowPriorityWarnings0/numberOfLowPriorityWarnings
numberOfNewWarnings0/numberOfNewWarnings
numberOfNormalPriorityWarnings2/numberOfNormalPriorityWarnings
numberOfWarnings2/numberOfWarnings
pluginResultSUCCESS/pluginResult
referenceBuild
number343/number
url
http://localhost:8080/job/code_coverage/job/Build_L1PHY_el1c_task_test_MAT_gcc/343/
/url
/referenceBuild
successfulHighScore0/successfulHighScore
successfulSinceBuild0/successfulSinceBuild
successfulSinceDate0/successfulSinceDate
warning/
warning/
warningsDelta0/warningsDelta
zeroWarningsHighScore1200233384/zeroWarningsHighScore
zeroWarningsSinceBuild0/zeroWarningsSinceBuild
zeroWarningsSinceDate0/zeroWarningsSinceDate
/result
successfultrue/successful
displayNameGNU C Compiler Warnings/displayName
parserGNU C Compiler 4 (gcc)/parser
urlNamewarnings18Result/urlName
/warningsResultAction
if i call .../buildNumber/warningsResult/api/xml
then i get the collated values for a particular build.
where do i need to add code to get the list of warnings actions in the /warningsResult/ call ?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-26113) REST api needed to get individual warnings values, not combined ones
Morne Joubert
edited a comment on JENKINS-26113
REST api needed to get individual warnings values, not combined ones
I added the following in AggregatedWarningsProjectAction.java
@Exported
public ListWarningsResultAction getWarningsResultAction() {
ListWarningsResultAction projectActions;
// projectActions = this.getProject().getActions(WarningsResultAction.class);
// can't use project, its actions list is allways empty
// try getting the actions of the last build
projectActions = this.getLastFinishedBuild().getActions(WarningsResultAction.class);
return projectActions;
}
Inside WarningsResultAction.java i then added the exported and visibility fields
@Exported(visibility = 2)
@Override
public String getUrlName() {
return WarningsDescriptor.getResultUrl(parserName);
}
/**
Returns the parser group this result belongs to.
*
@return the parser group
*/
@Exported(visibility = 2)
public String getParser() {
return parserName;
}
@Exported(visibility = 2)
@Override
public String getDisplayName() {
return ParserRegistry.getParser(parserName).getLinkName().toString();
}
the ../warnings/api/xml REST api then gives me:
aggregatedWarningsProjectAction
displayNameCompiler Warnings/displayName
lastFinishedBuild
number344/number
url
http://localhost:8080/job/code_coverage/job/Build_L1PHY_el1c_task_test_MAT_gcc/344/
/url
/lastFinishedBuild
warningsResultAction
displayNameGNU C Compiler Warnings/displayName
parserGNU C Compiler 4 (gcc)/parser
urlNamewarnings18Result/urlName
/warningsResultAction
warningsResultAction
displayNamePC-Lint Warnings/displayName
parserPC-Lint/parser
urlNamewarnings0Result/urlName
/warningsResultAction
/aggregatedWarningsProjectAction
So i now get the urlName and parser name i can use.
This is for a project, so to get the actual values for a particular build i can then do the calls to the particular parser urls.
if i do ../warnings/api/xml?depth=2 then i get the full value tree (for the last build)
warningsResultAction
namewarnings/name
result
newSuccessfulHighScorefalse/newSuccessfulHighScore
newZeroWarningsHighScorefalse/newZeroWarningsHighScore
numberOfFixedWarnings0/numberOfFixedWarnings
numberOfHighPriorityWarnings0/numberOfHighPriorityWarnings
numberOfLowPriorityWarnings0/numberOfLowPriorityWarnings
numberOfNewWarnings0/numberOfNewWarnings
numberOfNormalPriorityWarnings2/numberOfNormalPriorityWarnings
numberOfWarnings2/numberOfWarnings
pluginResultSUCCESS/pluginResult
referenceBuild
number343/number
url
http://localhost:8080/job/code_coverage/job/Build_L1PHY_el1c_task_test_MAT_gcc/343/
/url
/referenceBuild
successfulHighScore0/successfulHighScore
successfulSinceBuild0/successfulSinceBuild
successfulSinceDate0/successfulSinceDate
warning/
warning/
warningsDelta0/warningsDelta
zeroWarningsHighScore1200233384/zeroWarningsHighScore
zeroWarningsSinceBuild0/zeroWarningsSinceBuild
zeroWarningsSinceDate0/zeroWarningsSinceDate
/result
successfultrue/successful
displayNameGNU C Compiler Warnings/displayName
parserGNU C Compiler 4 (gcc)/parser
urlNamewarnings18Result/urlName
/warningsResultAction
if i call .../buildNumber/warningsResult/api/xml
then i get the collated values for a particular build.
where do i need to add code to get the list of warnings actions in the /warningsResult/ call ?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [prioritysorter-plugin] (JENKINS-22267) Upgrade to advanced mode is somehow not persisted to disk
Asmund Ostvold commented on JENKINS-22267 Upgrade to advanced mode is somehow not persisted to disk Magnus: Do you get any errors in the "normal" jenkins logs? Magnus: Do you have a very large installation with many jobs? Not that I was able to detect. I grep did show: grep -i -A 3 prioritys jenkins.log Feb 08, 2015 7:39:30 AM jenkins.advancedqueue.PrioritySorterPlugin init INFO: Configuring the Priority Sorter ... Feb 08, 2015 7:39:31 AM org.jenkinsci.main.modules.sshd.SSHD start INFO: Started SSHD at port 58781 Feb 10, 2015 8:42:50 PM jenkins.advancedqueue.PrioritySorterPlugin init INFO: Configuring the Priority Sorter ... Feb 10, 2015 8:42:51 PM org.jenkinsci.main.modules.sshd.SSHD start INFO: Started SSHD at port 45932 Magnus: How long does the conversion take until Jenkins tells you it is done? 1-2 min I believe. Magnus: Do you have your old data left or is it destroyed by the conversion? grep -i -A 5 prioritys *xml jenkins.advancedqueue.PriorityConfiguration.xml:jenkins.advancedqueue.PriorityConfiguration plugin="PrioritySorter@2.9" jenkins.advancedqueue.PriorityConfiguration.xml- jobGroups class="linked-list" jenkins.advancedqueue.PriorityConfiguration.xml-jenkins.advancedqueue.JobGroup jenkins.advancedqueue.PriorityConfiguration.xml- id0/id jenkins.advancedqueue.PriorityConfiguration.xml- priority20/priority jenkins.advancedqueue.PriorityConfiguration.xml- descriptionunit/description jenkins.advancedqueue.PriorityConfiguration.xml: usePriorityStrategiesfalse/usePriorityStrategies jenkins.advancedqueue.PriorityConfiguration.xml: priorityStrategies/ jenkins.advancedqueue.PriorityConfiguration.xml-/jenkins.advancedqueue.JobGroup jenkins.advancedqueue.PriorityConfiguration.xml- /jobGroups jenkins.advancedqueue.PriorityConfiguration.xml-/jenkins.advancedqueue.PriorityConfiguration jenkins.advancedqueue.PrioritySorterConfiguration.xml:jenkins.advancedqueue.PrioritySorterConfiguration plugin="PrioritySorter@2.9" jenkins.advancedqueue.PrioritySorterConfiguration.xml- legacyModefalse/legacyMode jenkins.advancedqueue.PrioritySorterConfiguration.xml- legacyMaxPriority2147483647/legacyMaxPriority jenkins.advancedqueue.PrioritySorterConfiguration.xml- legacyMinPriority-2147483648/legacyMinPriority jenkins.advancedqueue.PrioritySorterConfiguration.xml- allowPriorityOnJobstrue/allowPriorityOnJobs jenkins.advancedqueue.PrioritySorterConfiguration.xml- onlyAdminsMayEditPriorityConfigurationtrue/onlyAdminsMayEditPriorityConfiguration jenkins.advancedqueue.PrioritySorterConfiguration.xml:/jenkins.advancedqueue.PrioritySorterConfiguration This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-26684) Maven build step fail to launch mvn process when special chars are present in build variables
SCM/JIRA link daemon commented on JENKINS-26684 Maven build step fail to launch mvn process when special chars are present in build variables Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/tasks/Maven.java http://jenkins-ci.org/commit/jenkins/58a41bcb182290de681da01ba277b5e0d6211707 Log: FIXED JENKINS-26684 Escape special chars in maven build step arguments This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-11225) Add aggregation and subview for multi-configuration projects
Ulli Hafner commented on JENKINS-11225 Add aggregation and subview for multi-configuration projects Ok, I understand. There is nothing missing in the graphs or in the overview, the details on the root need to be enhanced. If you don't mind: could you please file individual issues for these feature request. I'm almost sure that this requires some time so tracking them individually would be easier. Please also consider setting the priorities so we can better see where to start first. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
Michael Pailloncy reopened JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Hi all, Exactly the same problem : reload the config from disk cause current running builds to disappear after reload but the build directory is present on the disk. Environment: Jenkins 1.593 on RHEL 6.0 Change By: Michael Pailloncy (11/Feb/15 10:45 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mantis-plugin] (JENKINS-26831) Mantis password written in plain text in build.xml
SCM/JIRA link daemon commented on JENKINS-26831 Mantis password written in plain text in build.xml Code changed in jenkins User: Seiji Sogabe Path: src/main/java/hudson/plugins/mantis/MantisSite.java src/main/java/hudson/plugins/mantis/soap/mantis110/MantisSessionImpl.java src/main/java/hudson/plugins/mantis/soap/mantis120/MantisSessionImpl.java src/main/resources/hudson/plugins/mantis/MantisProjectProperty/global.jelly src/test/java/hudson/plugins/mantis/MantisProjectPropertyConfigSubmitTest.java src/test/java/hudson/plugins/mantis/MantisSiteTest.java http://jenkins-ci.org/commit/mantis-plugin/5cbc6c75d2da51d77b688c416b32a7f54fd88029 Log: FIXED JENKINS-26831 save secret password This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mantis-plugin] (JENKINS-26831) Mantis password written in plain text in build.xml
SCM/JIRA link daemon resolved JENKINS-26831 as Fixed Mantis password written in plain text in build.xml Change By: SCM/JIRA link daemon (11/Feb/15 10:57 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26897) Specify true/false values for boolean parameter
elygre created JENKINS-26897 Specify true/false values for boolean parameter Issue Type: Improvement Assignee: Unassigned Components: core Created: 11/Feb/15 11:03 AM Description: We need to parameterize our builds so that the user can specify whether to refresh-dependencies or not, which in gradle-parlor translates to the optional "--refresh-dependencies" parameters. It would be really nice if you could specify true/false values for a boolean parameter. We would then create a parameter with true-value set to "--refresh-dependencies" and false-value set to "", and then just use $gradleRefreshDependencies when invoking the gradle script. Our current workaround is to create a text parameter with the description "Please add --refresh-dependencies" to refresh dependencies. This is simple enough, of course, but the use case is ideal for boolean parameters. Project: Jenkins Labels: parameter parameters parameterized Priority: Minor Reporter: elygre This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
