[JIRA] [build-user-vars] (JENKINS-21955) Set BUILD_USER to "SCMTrigger" if a build is run because of a source code change
Clifford Sanders started work on JENKINS-21955 Set BUILD_USER to "SCMTrigger" if a build is run because of a source code change Change By: Clifford Sanders (26/Feb/14 8:26 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-user-vars] (JENKINS-21955) Set BUILD_USER to "SCMTrigger" if a build is run because of a source code change
Clifford Sanders created JENKINS-21955 Set BUILD_USER to "SCMTrigger" if a build is run because of a source code change Issue Type: New Feature Assignee: Clifford Sanders Components: build-user-vars Created: 26/Feb/14 8:26 AM Description: If a build is run because of a change in the source code (SCMTrigger) all variables are empty. We have a deployment pipeline that builds a war file and deploys it on to a development environment. In order to know who is responsible for the current status on this development environment we want to write the username into a file that is contained in the war file. This works when the build is run manually but not if it is run from the SCMTrigger. Project: Jenkins Priority: Minor Reporter: Clifford Sanders This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Jose Sa commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials After some additional testing it seems that subversion plugin is relying on host svn client configuration looking into $HOME/.subversion for the credentials instead of of using the ones configured in Jenkins. When I used a Windows slave that didn't had a svn client installed or removed .subversion on linux slaves or master the problem to check on all urls is shown in scm polling log. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [rundeck] (JENKINS-21802) Rundeck plugin crashes jenkins on startup
firass Gz resolved JENKINS-21802 as Cannot Reproduce Rundeck plugin crashes jenkins on startup I tested the issue on centos 6.4 and did not reproduce it. jenkins worked just fine It seems there was a problem with centos 6.5 installation Thanks Change By: firass Gz (26/Feb/14 8:54 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [rake] (JENKINS-21956) Enable rake plugin to create rvm gemset on the fly if it does not already exist
Brian Fletcher created JENKINS-21956 Enable rake plugin to create rvm gemset on the fly if it does not already exist Issue Type: Improvement Assignee: david_calavera Components: rake Created: 26/Feb/14 8:55 AM Description: Background: The rake version dropdown list refers to all of the rvm environments which had existed on the system the last time the plugin was loaded or the last time the jenkins configuration page was saved. Problem: When creating new builds using the jenkins API, I want to also create isolated gemsets for the builds. The plugin does not know about all of the existing gemsets during the build (the gemset may have been created on an earlier step of the build using the rvm Build environment setting) The plugin does not create non-existing gemsets during the build Suggested Improvement: It would be nice for the dropdown list to be a combo box which allows free form text input. Then during a build, if the gemset entered is not known about yet, the rake plugin would 1. attempt to read the environment for the specified gemset 2. If number one fails, make an attempt at creating that gemset using rvm 3. If that fails, fail the build Project: Jenkins Priority: Major Reporter: Brian Fletcher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [rundeck] (JENKINS-21802) Rundeck plugin crashes jenkins on startup
firass Gz closed JENKINS-21802 as Cannot Reproduce Rundeck plugin crashes jenkins on startup Change By: firass Gz (26/Feb/14 8:54 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[no subject]
桃花潭水深千尺，不及汪伦送我情。－（唐）李白
真实快速通过学历职称资格证毕业证办理。主要受理真民办大学毕业证学历，真初、中、高级职称，各类职业资格证等。我处所办理的真实大学本科毕业证书、职称证书等均是真实有效！官网可查！为您的就业铺大道，为您的成功筑桥梁。咨询加游老师Q{}Q:920021576
64.老大、老二乘坐飞机，老二晕机，不停呕吐。一袋吐满，老大只好去取袋子，等他回来时，发觉全机人都在不停呕吐。老大问其原因老二说“我看到这只袋子也吐满了，只好又喝进去了半袋，结果他们就全吐了。”
--
You received this message because you are subscribed to the Google Groups
"Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-21717) openstack-nova: can no longer connect to cloud after update: "A> cannot be used as a key; "
foudil foudil commented on JENKINS-21717 openstack-nova: can no longer connect to cloud after update: "A> cannot be used as a key; " For my installation, this was related to jdk jdk 1.7.0_51, see https://issues.apache.org/jira/browse/JCLOUDS-427. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21871) Websphere deploy plugin
samir cherbani reopened JENKINS-21871 Websphere deploy plugin Change By: samir cherbani (26/Feb/14 9:16 AM) Resolution: Won't Fix Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21871) Websphere deploy plugin
samir cherbani commented on JENKINS-21871 Websphere deploy plugin Hello Greg, i can telnet from the Jenkins server to the WAS server over the HTTPS ports [root@srv28 ~]# telnet X.X.X.X 9045 Trying X.X.X.X... Connected to X.X.X.X. Escape character is '^]'. but i still have the same issue. Regards. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-21957) NPE when showing promotion status of a build with a run but deleted promotion step
Martin Kutter created JENKINS-21957 NPE when showing promotion status of a build with a run but deleted promotion step Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: stacktrace.txt Components: promoted-builds Created: 26/Feb/14 9:15 AM Description: When displaying the promotion status of a job with a once run, but now deleted promotion step, a NPE is written to the log, and a click on "Re-Execute promotion" yields a 404 Steps to reproduce 1. Configure a freestyle job "test-deleted-promotion", with a promotion step "Test1" with manual approval. There's no build steps required in both the job and the promotion step. 2. Run the Job once, then run the promotion step once. 3. Go to the job's configure page and delete the promotion step. 4. Navigate to job/test-deleted-promotion/1/promotion Jenkins writes the attached stacktrace to the log 5. Click on "Re-Execute promotion". Jenkins responds with 404 not found Environment: Jenkins-1.532.2 LTS Promoted Builds Plugin 2.15 Project: Jenkins Priority: Minor Reporter: Martin Kutter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-13140) Disconnected slaves come back online within a few minutes
mwebber commented on JENKINS-13140 Disconnected slaves come back online within a few minutes Can the 'Availability' option in the slave config be used to not reconnect automatically? Err ... how? Did you look at options for 'Availability' and come up with an idea, or did you just see an option called 'Availability and idly speculate as to what it might do? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-13140) Disconnected slaves come back online within a few minutes
mwebber edited a comment on JENKINS-13140 Disconnected slaves come back online within a few minutes Can the 'Availability' option in the slave config be used to not reconnect automatically? Err ... how? Did you look at options for 'Availability' and come up with an idea, or did you just see an option called 'Availability' and idly speculate as to what it might do? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-21946) Build Publisher Pluging when using https the jenkins loging does not work
tapiomtr updated JENKINS-21946 Build Publisher Pluging when using https the jenkins loging does not work Change By: tapiomtr (26/Feb/14 9:36 AM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-publisher] (JENKINS-18851) HudsonInstance.password stored in plaintext
tapiomtr commented on JENKINS-18851 HudsonInstance.password stored in plaintext The standard jenkins "credentials storage" shall be used. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21649) High CPU Usage on master while slaves working (multijob)
Patrik Schalin commented on JENKINS-21649 High CPU Usage on master while slaves working (multijob) Seem to be a fix here: https://github.com/jenkinsci/tikal-multijob-plugin/pull/49 Is that good? Any ETA on this fix, 1.13? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Flavio Donzé commented on JENKINS-20196 Failed to connect to URL (status = 404) The new exception I posted above (fatal: Authentication failed for 'https://usern...@bitbucket.org/scodi/tools.git/) seems to be a different problem than the original issue. I noticed that my password contains a "!", which is changed into "%21", this leads to the "Authentication failed" exception. Using the "configured credentials" works fine, alone or with the multiple SCM plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21643) Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment)
kal commented on JENKINS-21643 Jenkins Plugin for WebSphere Deployer Not deploying to Websphere AS 7 ( Remote deployment) thanks Greg. I will be testing it soon and get back to you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-user-vars] (JENKINS-21955) Set BUILD_USER to "SCMTrigger" if a build is run because of a source code change
Clifford Sanders commented on JENKINS-21955 Set BUILD_USER to "SCMTrigger" if a build is run because of a source code change I have forked the code: https://github.com/clifford-github/build-user-vars-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21509) Create new item: NumberFormatException: for InputString ""
Philip Helger commented on JENKINS-21509 Create new item: NumberFormatException: for InputString "" Still happening in 1.552 - please have a look at this - I can't create new projects and this is a real disturbance!! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-21387) If "Provide version number" flag selected and only Marketing or Technical version is specified parameter does not expose other, non-specified version via environment var
Francisco Cardoso
commented on JENKINS-21387
If "Provide version number" flag selected and only Marketing or Technical version is specified parameter does not expose other, non-specified version via environment variables
My suggestion to fix this: pull the try{}catch with the plist reading out of the if. This way, the default values will always be read from the plist.
Bar.java
try {
output.reset();
returnCode = launcher.launch().envs(envs).cmds("/usr/libexec/PlistBuddy", "-c", "Print :CFBundleVersion", app.absolutize().child("Info.plist").getRemote()).stdout(output).pwd(projectRoot).join();
if (returnCode == 0) {
version = output.toString().trim();
}
output.reset();
returnCode = launcher.launch().envs(envs).cmds("/usr/libexec/PlistBuddy", "-c", "Print :CFBundleShortVersionString", app.absolutize().child("Info.plist").getRemote()).stdout(output).pwd(projectRoot).join();
if (returnCode == 0) {
shortVersion = output.toString().trim();
}
}
catch(Exception ex) {
listener.getLogger().println("Failed to get version from Info.plist: " + ex.toString());
return false;
}
if (provideApplicationVersion) {
if (! StringUtils.isEmpty(cfBundleVersionValue)) {
version = cfBundleVersionValue;
}
else if (! StringUtils.isEmpty(cfBundleShortVersionStringValue)) {
shortVersion = cfBundleShortVersionStringValue;
}
else {
listener.getLogger().println("You have to provide a value for either the marketing or technical version. Found neither.");
return false;
}
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-21387) If "Provide version number" flag selected and only Marketing or Technical version is specified parameter does not expose other, non-specified version via environment var
Francisco Cardoso
edited a comment on JENKINS-21387
If "Provide version number" flag selected and only Marketing or Technical version is specified parameter does not expose other, non-specified version via environment variables
My suggestion to fix this: pull the try{}catch with the plist reading out of the if. This way, the default values will always be read from the plist.
Bar.java
try {
output.reset();
returnCode = launcher.launch().envs(envs).cmds("/usr/libexec/PlistBuddy", "-c", "Print :CFBundleVersion", app.absolutize().child("Info.plist").getRemote()).stdout(output).pwd(projectRoot).join();
if (returnCode == 0) {
version = output.toString().trim();
}
output.reset();
returnCode = launcher.launch().envs(envs).cmds("/usr/libexec/PlistBuddy", "-c", "Print :CFBundleShortVersionString", app.absolutize().child("Info.plist").getRemote()).stdout(output).pwd(projectRoot).join();
if (returnCode == 0) {
shortVersion = output.toString().trim();
}
}
catch(Exception ex) {
listener.getLogger().println("Failed to get version from Info.plist: " + ex.toString());
return false;
}
if (provideApplicationVersion) {
if (! StringUtils.isEmpty(cfBundleVersionValue)) {
version = cfBundleVersionValue;
}
else if (! StringUtils.isEmpty(cfBundleShortVersionStringValue)) {
shortVersion = cfBundleShortVersionStringValue;
}
else {
listener.getLogger().println("You have to provide a value for either the marketing or technical version. Found neither.");
return false;
}
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-21387) If "Provide version number" flag selected and only Marketing or Technical version is specified parameter does not expose other, non-specified version via environment var
Francisco Cardoso
edited a comment on JENKINS-21387
If "Provide version number" flag selected and only Marketing or Technical version is specified parameter does not expose other, non-specified version via environment variables
My suggestion to fix this: pull the try{}catch with the plist reading out of the if. This way, the default values will always be read from the plist.
XCodeBuilder.java
...
try {
output.reset();
returnCode = launcher.launch().envs(envs).cmds("/usr/libexec/PlistBuddy", "-c", "Print :CFBundleVersion", app.absolutize().child("Info.plist").getRemote()).stdout(output).pwd(projectRoot).join();
if (returnCode == 0) {
version = output.toString().trim();
}
output.reset();
returnCode = launcher.launch().envs(envs).cmds("/usr/libexec/PlistBuddy", "-c", "Print :CFBundleShortVersionString", app.absolutize().child("Info.plist").getRemote()).stdout(output).pwd(projectRoot).join();
if (returnCode == 0) {
shortVersion = output.toString().trim();
}
}
catch(Exception ex) {
listener.getLogger().println("Failed to get version from Info.plist: " + ex.toString());
return false;
}
if (provideApplicationVersion) {
if (! StringUtils.isEmpty(cfBundleVersionValue)) {
version = cfBundleVersionValue;
}
else if (! StringUtils.isEmpty(cfBundleShortVersionStringValue)) {
shortVersion = cfBundleShortVersionStringValue;
}
else {
listener.getLogger().println("You have to provide a value for either the marketing or technical version. Found neither.");
return false;
}
}
...
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-user-vars] (JENKINS-21955) Set BUILD_USER to "SCMTrigger" if a build is run because of a source code change
Clifford Sanders commented on JENKINS-21955 Set BUILD_USER to "SCMTrigger" if a build is run because of a source code change I have create a pull request: https://github.com/jenkinsci/build-user-vars-plugin/pull/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/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-20957) Add support for RunParameter to parameterized-trigger
ikedam updated JENKINS-20957 Add support for RunParameter to parameterized-trigger Change By: ikedam (26/Feb/14 10:48 AM) Issue Type: Bug New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-20256) users can see all the Build Pipeline Views althought they have no priviledge on any project associated with these Views.
yohan bernard resolved JENKINS-20256 as Fixed users can see all the Build Pipeline Views althought they have no priviledge on any project associated with these Views. Resolved on gitHub Change By: yohan bernard (26/Feb/14 10:49 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-9766) Triggering a parameterized build from the dashboard does not return to the dashboard
ikedam updated JENKINS-9766 Triggering a parameterized build from the dashboard does not return to the dashboard This is a issue with "parameterized project", which is a project with parameters, not a project with parameterized-trigger plugin. If no fixes will be done in dashboard-view, please close with won't fix. Change By: ikedam (26/Feb/14 10:57 AM) Component/s: dashboard-view Component/s: parameterized-trigger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-11257) Stopping a parent job doesn't stop the triggered child jobs
ikedam updated JENKINS-11257 Stopping a parent job doesn't stop the triggered child jobs This is not a bug, nor critical. Change By: ikedam (26/Feb/14 10:59 AM) Issue Type: Bug Improvement Priority: Critical 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/groups/opt_out.
[JIRA] [core] (JENKINS-21958) ArtifactManager introduces regression with publishing symbolic links.
eliedebrauwer created JENKINS-21958 ArtifactManager introduces regression with publishing symbolic links. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 26/Feb/14 12:20 PM Description: I have observed a regression issue with the introduction of the new ArtifactManager (https://github.com/jenkinsci/jenkins/commit/e1eea67bb2fa1a356492e91313d84a523f441b34 - https://issues.jenkins-ci.org/browse/JENKINS-17236 ). I have pinpointed the issue and saw it was introduced in jenkins 1.532 (as in it works perfectly in 1.531, but fails in 1.532 and above, including the 1.532.2 LTS version). My particular use case is that the result of our build creates a symlink which points to the final artifact (the final artifact as stored on disk has a timestamp/build number in its name). However with the introduction of the new ArtifactManager the artifacts which are identified using symlinks no longer get published. Steps to reproduce: Create a new job Add a shell build step rm -rf folder mkdir folder echo "bla" > folder/artifact ln -sf ./artifact folder/link Add a 'Archive the Artifacts' post-build action and in the Files to archive text box enter folder/link Expected behavior (as implemented/verified) on jenkins 1.524 - 1.531: The build succeeds The 'Last Successful Artifacts' mentions: link 4B Actual behavior (as implemented/verified) on jenkins 1.532 - 1.552, including LTS: The build succeeds The 'Last Successful Artifacts' mentions nothing. (for reference the build output: Started by user anonymous Building on master in workspace /home/jenkins/jenkins/jobs/brossel_edb/workspace [workspace] $ /bin/sh -xe /tmp/hudson1352860404870483249.sh + rm -rf folder + mkdir folder + echo bla + ln -sf ./artifact folder/link Archiving artifacts Finished: SUCCESS ) An additional sidenote is that the ArtifactDeployer plugin (version 0.28) is doing its job properly, another indication that the way symlinks are resolved/dealt with has likely changed due the introduction of the new ArtifactManager. Environment: jenkins@:~/jenkins$ java -version java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.5) (6b24-1.11.5-1) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) jenkins@:~/jenkins$ uname -a Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux Project: Jenkins Priority: Major Reporter: eliedebrauwer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-21162) CopyArtifact plugin 1.28 no longer creates COPYARTIFACT_BUILD_NUMBER_* variables in the same way
John O'Brien commented on JENKINS-21162 CopyArtifact plugin 1.28 no longer creates COPYARTIFACT_BUILD_NUMBER_* variables in the same way This may be similar, but when a build job has a dash in it. For example, when copying artifacts from job rel-02-09 the environment variable created is COPYARTIFACT_BUILD_NUMBER_REL_ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21958) ArtifactManager introduces regression with publishing symbolic links.
Jesse Glick assigned JENKINS-21958 to Jesse Glick ArtifactManager introduces regression with publishing symbolic links. Change By: Jesse Glick (26/Feb/14 1:06 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21958) ArtifactManager introduces regression with publishing symbolic links.
Jesse Glick started work on JENKINS-21958 ArtifactManager introduces regression with publishing symbolic links. Change By: Jesse Glick (26/Feb/14 1:06 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21958) ArtifactManager introduces regression with publishing symbolic links.
Jesse Glick updated JENKINS-21958 ArtifactManager introduces regression with publishing symbolic links. Change By: Jesse Glick (26/Feb/14 1:06 PM) Labels: regression This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21871) Websphere deploy plugin
Greg Peters commented on JENKINS-21871 Websphere deploy plugin This issue may be related to automatically building an EAR from a WAR file and not necessarily from a connectivity issue. Have you tried changing your settings to EE5 or EE6 in the plugin settings? The plugin will use this setting to automatically create an application.xml based on the EE setting specified. If this setting change doesn't make a difference, validate the EAR file is truly generated on the file system and that it's not a read/write permissions issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-21959) Dashboard Plug In Links do not work together with Cloudbees Folder Plug In
Rudolf Honegger created JENKINS-21959 Dashboard Plug In Links do not work together with Cloudbees Folder Plug In Issue Type: Bug Affects Versions: current Assignee: Peter Hayes Components: dashboard-view Created: 26/Feb/14 1:18 PM Description: On the dashboard view (Jobs Grid) the link to the jobs do not work together with the CloudBees Folder Plug In. When I select a link I always get HTTP ERROR 404 with a wrong link. It seems that this view can not solve nested folders. Environment: Jenkins version 1.551 CloudBees Folder Plug In Project: Jenkins Priority: Major Reporter: Rudolf Honegger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21960) Numeric Value '1' isn't passing down as a parameter in a multijob project
manish pillai created JENKINS-21960 Numeric Value '1' isn't passing down as a parameter in a multijob project Issue Type: Bug Assignee: Unassigned Attachments: ChildJobs_MissingParameterValue.png, ParentJob_WithParameterValue.png Components: jenkins-multijob-plugin Created: 26/Feb/14 1:27 PM Description: While triggering a multijob project with one of the parameter value as '1', is its being noted that the child jobs have the parameter as 'blank' . '1' is not being passed down as a parameter value. I have tried using other alpha numeric values , and all of the values were being successfully passed down. Environment: Windows Server 2008 R2 Enterprise Edition Project: Jenkins Priority: Major Reporter: manish pillai This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21960) Numeric Value '1' isn't passing down as a parameter in a multijob project
manish pillai started work on JENKINS-21960 Numeric Value '1' isn't passing down as a parameter in a multijob project Change By: manish pillai (26/Feb/14 1:28 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [groovy-postbuild] (JENKINS-21480) Groovy postbuild add ability to use external groovy script
Martin d'Anjou commented on JENKINS-21480 Groovy postbuild add ability to use external groovy script I am able to do just that by doing the following. Enter these lines in lieu of the script in the "Groovy script" box: // Delegate to an external script // The filename must match the class name import JenkinsPostBuild def postBuild = new JenkinsPostBuild(manager) postBuild.run() Create a file called JenkinsPostBuild.groovy and elaborate your script in there. The file name must match the class name. There is another example on this page https://wiki.jenkins-ci.org/display/JENKINS/Groovy+Postbuild+Plugin (open the Comments section and look for "Example8") Then in the "Additional groovy classpath" box enter the path to that file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-21961) job-dsl copyArtifacts won't accept a non numerical value for build number
Rob Langley
created JENKINS-21961
job-dsl copyArtifacts won't accept a non numerical value for build number
Issue Type:
Bug
Affects Versions:
current
Assignee:
Justin Ryan
Components:
job-dsl-plugin
Created:
26/Feb/14 1:33 PM
Description:
I've hit the same issue as this user: https://groups.google.com/forum/?fromgroups#!topic/job-dsl-plugin/N-UzUF61p58
Basically the following doesn't work.
steps{
copyArtifacts("name","target"){
buildNumber("\$MY_PARAMETER")
}
}
However the copy artifacts plugin is more than happy to accept parameters rather than a build number.
Environment:
Job-dsl plugin version 1.20
Project:
Jenkins
Priority:
Major
Reporter:
Rob Langley
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes
Brian Biggs commented on JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes Same issue here using Multiple SCM plugin. Git 2.0.2. Git Client 1.6.3. Multiple SCM 0.3 Started on Feb 25, 2014 4:52:31 PM Polling SCM changes on master Using strategy: Default [poll] Last Built Revision: Revision 18e02f062d1dbe081bc9c0b8bac3f5e7b8e85af6 (origin/master) using GIT_SSH to set credentials Using strategy: Default [poll] Last Built Revision: Revision 18e02f062d1dbe081bc9c0b8bac3f5e7b8e85af6 (origin/master) using GIT_SSH to set credentials Done. Took 0.89 sec Changes found However the actual revisions are: Revision: 18e02f062d1dbe081bc9c0b8bac3f5e7b8e85af6 Revision: 8f3e5979c556c117905f46dc1811964d70a21998 It looks like somehow the revision of one repo is used for both repos and maybe that kicks off the build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [backup] (JENKINS-21076) Workspace zip from windows host wrong
ritzmann commented on JENKINS-21076 Workspace zip from windows host wrong Rather major issue for us and only started occurring when we upgraded from 1.509.x to 1.532 along with the plugins last week. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
WH commented on JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Similar problem here (Jenkins LTS 1.532.2 and Subversion Plugin 2.2): Project1 has svn:externals property "^/project2/trunk/directory directory". Checking out svn+ssh://server/repo/project1/trunk@3895 at revision 3895 A xxx.xxx ... U. Fetching 'svn+ssh://server/repo/project2/trunk/directory' at -1 into 'C:\slavedir\workspace\jobdir\f99eb302\directory' A directory\yyy.yyy ... Udirectory At revision 3895 At revision 3895 hudson.util.IOException2: revision check failed on svn+ssh://server/repo/project2/trunk/directory at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:189) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:132) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:738) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:899) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1665) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No credential to try. Authentication failed at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthentication(DefaultSVNAuthenticationManager.java:185) at org.tmatesoft.svn.core.internal.io.svn.SVNSSHConnector.open(SVNSSHConnector.java:77) at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.open(SVNConnection.java:77) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1252) at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:168) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118) at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:148) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160) at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1238) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967) at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872) at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:177) ... 11 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
WH updated JENKINS-21785 Check for changes in folders linked via svn:externals fails due to missing credentials Change By: WH (26/Feb/14 2:19 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21954) Jenkins can not enter Job's api page with latest version 1.552
Egil Haugli commented on JENKINS-21954 Jenkins can not enter Job's api page with latest version 1.552 I get the same error, trying to use json api: java.io.IOException: Failed to write timestamp at org.kohsuke.stapler.export.Property.writeTo(Property.java:120) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182) at org.kohsuke.stapler.export.Property.writeValue(Property.java:232) at org.kohsuke.stapler.export.Property.writeValue(Property.java:169) at org.kohsuke.stapler.export.Property.writeValue(Property.java:137) at org.kohsuke.stapler.export.Property.writeTo(Property.java:114) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182) at org.kohsuke.stapler.export.Property.writeValue(Property.java:232) at org.kohsuke.stapler.export.Property.writeValue(Property.java:137) at org.kohsuke.stapler.export.Property.writeTo(Property.java:114) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182) at org.kohsuke.stapler.export.Model.writeTo(Model.java:154) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doJson(Api.java:195) at sun.reflect.GeneratedMethodAccessor350.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServle
[JIRA] [mercurial] (JENKINS-15806) Exit code of `hg pull` not checked
SCM/JIRA link daemon resolved JENKINS-15806 as Fixed Exit code of `hg pull` not checked Change By: SCM/JIRA link daemon (26/Feb/14 2:36 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-15806) Exit code of `hg pull` not checked
SCM/JIRA link daemon commented on JENKINS-15806 Exit code of `hg pull` not checked Code changed in jenkins User: Ben Rogers Path: src/main/java/hudson/plugins/mercurial/MercurialSCM.java src/test/java/hudson/plugins/mercurial/SCMTestBase.java http://jenkins-ci.org/commit/mercurial-plugin/0854a77f154cbadf71835731ea6f5f90593f42f8 Log: [FIXED JENKINS-15806] - Fail build on failed pull This is an update to pull request #31 and #40 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-15806) Exit code of `hg pull` not checked
SCM/JIRA link daemon commented on JENKINS-15806 Exit code of `hg pull` not checked Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/mercurial/MercurialSCM.java src/test/java/hudson/plugins/mercurial/SCMTestBase.java http://jenkins-ci.org/commit/mercurial-plugin/0b005bd18419f81ecb2d98827054273d9d70fbdc Log: Merge pull request #56 from ben--/master [FIXED JENKINS-15806] - Fail build on failed pull Compare: https://github.com/jenkinsci/mercurial-plugin/compare/c064ebaab7fd...0b005bd18419 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [concurrent-build] (JENKINS-13972) Concurrent matrix builds abort
Shay Weiss commented on JENKINS-13972 Concurrent matrix builds abort Hi all, I've been investigating aborts issues in Jenkins and I've found at least one bug with regards to this. Here is my report on the subject: https://docs.google.com/presentation/d/1ybtB-Bhkb4c3dhb5ZMArr4prtEZ-pjLqH9Vk7yhdZTg/ There is also another issue I'm dealing with and in the process of investigating. Core developers - I'll be happy to make a contribution to the sources if you can give me pointers on how to modify my proposed fix so it will be 'commit worthy' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-20690) Subversion changes using Assembla
twolfart commented on JENKINS-20690 Subversion changes using Assembla I had the same effect, and could remove it with the same solution. 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/groups/opt_out.
[JIRA] [core] (JENKINS-21958) ArtifactManager introduces regression with publishing symbolic links.
Jesse Glick updated JENKINS-21958 ArtifactManager introduces regression with publishing symbolic links. Change By: Jesse Glick (26/Feb/14 3:06 PM) Labels: lts-candidate regression This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21958) ArtifactManager introduces regression with publishing symbolic links.
Jesse Glick commented on JENKINS-21958 ArtifactManager introduces regression with publishing symbolic links. The problem arises in the particular case that the directory containing the symlink was not otherwise archived. (Which would be odd in the case you cite, since there is not much purpose in archiving link without also archiving artifact, since the link would be dead, but there could be other cases where a directory containing just symlinks is being archived for some reason along with other directories with the target files.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-tracker] (JENKINS-21962) User which is log-outed by session expiration can download files.
Alena Luchkovskaya updated JENKINS-21962 User which is log-outed by session expiration can download files. Change By: Alena Luchkovskaya (26/Feb/14 3:08 PM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-tracker] (JENKINS-21962) User which is log-outed by session expiration can download files.
Alena Luchkovskaya created JENKINS-21962 User which is log-outed by session expiration can download files. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-tracker Created: 26/Feb/14 3:07 PM Description: Login to Jenkins Navigate to build of your project Find e.g. .war file for download Leave opened page till your session will be expired Click on download .war link(do not refresh the page) Enter your credentials and Press "Login" button (do not refresh the page) Expected: user is logged in. Actual war file is downloaded by every click on "Login" button Environment: Browser Chrome OS: Windows7 Project: Jenkins Labels: jenkins Priority: Major Reporter: Alena Luchkovskaya This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-tracker] (JENKINS-21962) User which is log-outed by session expiration can download files.
Alena Luchkovskaya updated JENKINS-21962 User which is log-outed by session expiration can download files. Change By: Alena Luchkovskaya (26/Feb/14 3:07 PM) Description: # Login to Jenkins# Navigate to build of your project# Find e.g. .war file for download# Leave opened page till your session will be expired# Click on download .war link(do not refresh the page)# Enter your credentials and Press "Login" button (do not refresh the page) *Expected:*- user is logged in.*Actual*- war file is downloaded by every click on "Login" button ;- user is not logged in. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21958) ArtifactManager introduces regression with publishing symbolic links.
Elie De Brauwer commented on JENKINS-21958 ArtifactManager introduces regression with publishing symbolic links. Thanks for the swift investigation. As far as I can tell from my tests, the pre-1.532 did actually a deep copy of the contents of the symlink, hence instead of archiving the symlink it archived the contents of the link under the name of the link. (In my particular case I would have a folder having build-1.bin build-2.bin build-3.bin build-4.bin latest.bin (which points to build-4.bin) ) When I would point jenkins to 'latest.bin' (since the counter in my scenario is not know/set by jenkins) it would actually create a file called 'latest.bin' with the contents of build-4.bin, aka a deep-copy. (I'm not saying that this behavior is 100% sane/correct/understandable, since obviously this may result in unwanted duplication of data when not done carefully, but in my case it did what it was supposed to do, and for that account the artefactdeployer plugin was doing exactly the same thing). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21958) ArtifactManager introduces regression with publishing symbolic links.
Jesse Glick commented on JENKINS-21958 ArtifactManager introduces regression with publishing symbolic links. pre-1.532 did actually a deep copy of the contents of the symlink If true, I would consider that a bug in the older version. The principle of least surprise means that if your workspace has a mixture of regular files and symlinks, and you ask to archive some or all of them, the resulting artifact directory contains the exact same things. If you wished to archive a particular regular file that might change from build to build, then you must have a build step which copies it to some fixed location. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
QC Plugin for Jenkins
Hi, I am using Jenkins v1.545. Have also installed the qc plugin 1.2.1. But i am not able to add a new build for HP Quality Center in a job. I am getting the option, when i am clicking on add new build button on the job configuration page. But when i click on HP quality center build, no build is added. Nothing happens on the page. Have been facing this issue for quite some time. Could some body please let me know the way out, or anybody share there thoughs if they have faced any such issue earlier. Pankaj -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/QC-Plugin-for-Jenkins-tp4692284.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-13523) Missing option "Add timestamps to the Console Output" (Build Environment)
Richard Cross edited a comment on JENKINS-13523 Missing option "Add timestamps to the Console Output" (Build Environment) Actually, I would argue this is non-trivial. True, the start times of the individual jobs called by Build Flow DSL are recorded elsewhere, but an awful lot can happen either side of the DSL, for example a source checkout, or a bunch of post-build activities. Not having any timestamps in the console output of this kind of job is a major annoyance. Please can you raise the priority? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-13523) Missing option "Add timestamps to the Console Output" (Build Environment)
Richard Cross commented on JENKINS-13523 Missing option "Add timestamps to the Console Output" (Build Environment) Actually, I would argue this is non-trivial. True, the start times of the individual jobs called by Build Flow DSL are recorded elsewhere, but an awful lot can happen either side of the DSL, for example a source checkout, or a bunch of post-build activites. Not having any timestamps in the console output of this kind of job is a major annoyance. Please can you raise the priority? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-13523) Missing option "Add timestamps to the Console Output" (Build Environment)
Ben Golding commented on JENKINS-13523 Missing option "Add timestamps to the Console Output" (Build Environment) Richard: changed priority to '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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-21961) job-dsl copyArtifacts won't accept a non numerical value for build number
Rob Langley commented on JENKINS-21961 job-dsl copyArtifacts won't accept a non numerical value for build number PR submitted https://github.com/jenkinsci/job-dsl-plugin/pull/161 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-13523) Missing option "Add timestamps to the Console Output" (Build Environment)
Ben Golding updated JENKINS-13523 Missing option "Add timestamps to the Console Output" (Build Environment) Change By: Ben Golding (26/Feb/14 3:49 PM) Priority: Trivial 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/groups/opt_out.
[JIRA] [jenkins-tracker] (JENKINS-21962) User which is log-outed by session expiration can download files.
Alena Luchkovskaya updated JENKINS-21962 User which is log-outed by session expiration can download files. Change By: Alena Luchkovskaya (26/Feb/14 4:11 PM) Priority: Minor 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/groups/opt_out.
[JIRA] [core] (JENKINS-21958) ArtifactManager introduces regression with publishing symbolic links.
SCM/JIRA link daemon resolved JENKINS-21958 as Fixed ArtifactManager introduces regression with publishing symbolic links. Change By: SCM/JIRA link daemon (26/Feb/14 4:37 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21958) ArtifactManager introduces regression with publishing symbolic links.
SCM/JIRA link daemon commented on JENKINS-21958 ArtifactManager introduces regression with publishing symbolic links. Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/FilePath.java test/src/test/java/hudson/tasks/ArtifactArchiverTest.java http://jenkins-ci.org/commit/jenkins/7c568178f3810ab590d33ba23f1cf7fea418edac Log: [FIXED JENKINS-21958] FilePath.copyRecursiveTo given a scanner including a symlink but not any regular file in the same directory would neglect to create the parent directory on the destination and thus not copy the link. (Util.createSymlink is partly to blame for not throwing a descriptive IOException when it fails to create a link, but this is its historical behavior needed for compatibility. copyRecursiveTo also continues to suppress error text from this method because there is nowhere for it to go. Perhaps need a new variant of createSymlink that is guaranteed to either have created the link or throw an exception.) Compare: https://github.com/jenkinsci/jenkins/compare/ddbba3405434...7c568178f381 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [credentials] (JENKINS-21963) SVN checkout using mutual authentication
David Tabacu created JENKINS-21963 SVN checkout using mutual authentication Issue Type: Bug Affects Versions: current Assignee: stephenconnolly Components: credentials, credentials-binding, subversion Created: 26/Feb/14 4:40 PM Description: Hello, I've added a PKCS12 to the credentials store and I'm trying to use it to checkout a SVN repository, but I'm getting the following error: "java.lang.IllegalArgumentException: password can't be null" The P12 password exists and is not empty, and in credentials store it displays my CN. Log: Feb 26, 2014 6:20:02 PM INFO hudson.scm.SubversionSCM$ModuleLocation$DescriptorImpl doCheckCredentialsId Failed to access subversion repository https:// org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99) at hudson.scm.SubversionSCM$DescriptorImpl.checkRepositoryPath(SubversionSCM.java:2315) at hudson.scm.SubversionSCM$ModuleLocation$DescriptorImpl.doCheckCredentialsId(SubversionSCM.java:2944) at sun.reflect.GeneratedMethodAccessor224.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:611) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTrans
[JIRA] [cppcheck] (JENKINS-21346) Not working with cppcheck 1.63
rggjan resolved JENKINS-21346 as Fixed Not working with cppcheck 1.63 Yes, this seems to be fixed already... maybe cppcheck 1.63.1 contained some fixes. Thanks anyway. Change By: rggjan (26/Feb/14 4:45 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.
James Griffin created JENKINS-21964 Build definition and workspace name should accept parameters and/or environment variables. Issue Type: Improvement Assignee: Deluan Quintão Components: rtc, teamconcert Created: 26/Feb/14 4:47 PM Description: We are looking to use the same build project for multiple streams in rtc (parallel supported versioning). Currently if you try to add a parameter or variable to the build definition name or repository workspace name, the team concert plugin will not parse the variable and error out, not finding the correct definition/workspace. for example parameter choice list : stream = ver2.5, ver3.2, ver6.0 build definition = jenkins.$stream adding this functionality would allow us to greatly expand our use of jenkins for production builds as well as testing processes for individual developer workspaces. Currently we are considering this a blocker for set up of developer testing. the only know method around this is to set up a template project using another plugin. Project: Jenkins Priority: Major Reporter: James Griffin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [s3] (JENKINS-21965) publishing to s3 bucket always failed authentication (us-east-1)
Ryan Vanderwerf
created JENKINS-21965
publishing to s3 bucket always failed authentication (us-east-1)
Issue Type:
Bug
Affects Versions:
current
Assignee:
Michael Watt
Components:
s3
Created:
26/Feb/14 5:02 PM
Description:
I get an error publishing to an s3 bucket. I've triple checked my access key and secret key and they all have full access (I use the same keys for s3fs setups). When I try to publish I get this error:
Publish artifacts to S3 Bucket Using S3 profile: rf-s3
Publish artifacts to S3 Bucket bucket=/jenkins/xxx/xxx-13, file=xxx.war region = US_EAST_1
ERROR: Failed to upload files
java.io.IOException: put Destination [bucketName=, objectName=jenkins/rdc/rdc-13/rdc.war]: AmazonS3Exception: Status Code: 403, AWS Service: Amazon S3, AWS Request ID: BA4394BEC07x, AWS Error Code: SignatureDoesNotMatch, AWS Error Message: The request signature we calculated does not match the signature you provided. Check your key and signing method., S3 Extended Request ID: xxx
I set up publish on my build as bucketname: "/jenkins/xxx/${JOB_NAME}-${BUILD_NUMBER}"
Does this work for everyone else?
Environment:
Ubuntu native installer 1.551
Project:
Jenkins
Priority:
Major
Reporter:
Ryan Vanderwerf
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-13140) Disconnected slaves come back online within a few minutes
Daniel Beck commented on JENKINS-13140 Disconnected slaves come back online within a few minutes mwebber: Instead of only disconnecting, configure the slave to also have an in demand connection delay of 100. Works like a charm. It'd be better if slave processes weren't started while they're marked offline, then you could just configure all your slaves with in demand delay 0/idle delay 100 and have effectively regular 'always on' slaves that don't automatically reconnect. Maybe this can be improved in core. Since the user reporting this issue originally mentioned that the goal was accomplished through "mark offline", it'd help if anyone interested in this could provide a use case. Starting new builds can be prevented after 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/groups/opt_out.
[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes
Brian Biggs commented on JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes Update from my post: I went back to the job directory and deleted everything but the job configuration. Everything is working fine now. It may be that my original configuration only had one repo and when I added the second repo and issue arose. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21855) Add markup formatter preview for parameter descriptions
SCM/JIRA link daemon commented on JENKINS-21855 Add markup formatter preview for parameter descriptions Code changed in jenkins User: Oliver Gondža Path: core/src/main/resources/hudson/model/BooleanParameterDefinition/config.jelly core/src/main/resources/hudson/model/ChoiceParameterDefinition/config.jelly core/src/main/resources/hudson/model/FileParameterDefinition/config.jelly core/src/main/resources/hudson/model/PasswordParameterDefinition/config.jelly core/src/main/resources/hudson/model/RunParameterDefinition/config.jelly core/src/main/resources/hudson/model/StringParameterDefinition/config.jelly core/src/main/resources/hudson/model/TextParameterDefinition/config.jelly http://jenkins-ci.org/commit/jenkins/d9b16017e4872e8e128a29ee9aab432f1cd26536 Log: Merge pull request #1133 from daniel-beck/JENKINS-21855 [FIXED JENKINS-21855] Add preview for parameter descriptions Compare: https://github.com/jenkinsci/jenkins/compare/7c568178f381...d9b16017e487 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21855) Add markup formatter preview for parameter descriptions
SCM/JIRA link daemon commented on JENKINS-21855 Add markup formatter preview for parameter descriptions Code changed in jenkins User: Daniel Beck Path: core/src/main/resources/hudson/model/BooleanParameterDefinition/config.jelly core/src/main/resources/hudson/model/ChoiceParameterDefinition/config.jelly core/src/main/resources/hudson/model/FileParameterDefinition/config.jelly core/src/main/resources/hudson/model/PasswordParameterDefinition/config.jelly core/src/main/resources/hudson/model/RunParameterDefinition/config.jelly core/src/main/resources/hudson/model/StringParameterDefinition/config.jelly core/src/main/resources/hudson/model/TextParameterDefinition/config.jelly http://jenkins-ci.org/commit/jenkins/672954baf4570b93f66b7c1bc997f878322918ba Log: [FIXED JENKINS-21855] Add preview for parameter descriptions This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21855) Add markup formatter preview for parameter descriptions
SCM/JIRA link daemon resolved JENKINS-21855 as Fixed Add markup formatter preview for parameter descriptions Change By: SCM/JIRA link daemon (26/Feb/14 5:39 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-13140) Disconnected slaves come back online within a few minutes
Daniel Beck commented on JENKINS-13140 Disconnected slaves come back online within a few minutes Something approaching a fix should be a trivial change in RetentionStrategy: If the node is disconnected, and isn't launching, and can be launched, launch it if not marked offline by the user. Would that work? Never reconnecting could be annoying with disconnects due to error, so I doubt that's an option. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cucumber-testresult] (JENKINS-21835) Cucumber Test Result Plugin does not correctly parse Scenario Outline results
Leidiane Vieira commented on JENKINS-21835 Cucumber Test Result Plugin does not correctly parse Scenario Outline results Guys, someone could solved this issue? Thanks in advance... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21966) SVN_REVISION not set for Jenkins version 1.447
babak eshraghi created JENKINS-21966 SVN_REVISION not set for Jenkins version 1.447 Issue Type: Bug Assignee: Unassigned Components: subversion Created: 26/Feb/14 6:10 PM Description: Hi, I'm using Jenkins version 1.447. and also subversion . I'm trying to set SVN_REVISION in Jenkins for building my project. but SVN_REVISION is not setting, I'm wondering which Jenkins version you have fixed this bug. Project: Jenkins Priority: Major Reporter: babak eshraghi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21958) ArtifactManager introduces regression with publishing symbolic links.
dogfood commented on JENKINS-21958 ArtifactManager introduces regression with publishing symbolic links. Integrated in jenkins_main_trunk #3197 [FIXED JENKINS-21958] FilePath.copyRecursiveTo given a scanner including a symlink but not any regular file in the same directory would neglect to create the parent directory on the destination and thus not copy the link. (Revision 7c568178f3810ab590d33ba23f1cf7fea418edac) Result = UNSTABLE Jesse Glick : 7c568178f3810ab590d33ba23f1cf7fea418edac Files : core/src/main/java/hudson/FilePath.java test/src/test/java/hudson/tasks/ArtifactArchiverTest.java changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scriptler] (JENKINS-18862) Add an ability to specify external GIT repository for scripts
Dominik Bartholdi commented on JENKINS-18862 Add an ability to specify external GIT repository for scripts can't you just push to the scriptler repo? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21159) buildTimeTrend only shows last day of builds
Dominik Bartholdi commented on JENKINS-21159 buildTimeTrend only shows last day of builds @Jesse, I'm not sure what you want me to do - just fill another issue with the same content? (maybe its just my english which stops me from understanding, sorry) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21954) Jenkins can not enter Job's api page with latest version 1.552
Darrell Hamilton commented on JENKINS-21954 Jenkins can not enter Job's api page with latest version 1.552 based on: ??... at hudson.plugins.git.GitChangeSet.getTimestamp(GitChangeSet.java:194) ...?? It would appears this is an issue with the Git plugin and not 1.552 of Jenkins. I upgraded Jenkins at the same time as the Git plugin and we're only seeing this error on projects using Git. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21954) Jenkins can not enter Job's api page with latest version 1.552
Darrell Hamilton edited a comment on JENKINS-21954 Jenkins can not enter Job's api page with latest version 1.552 based on: ... at hudson.plugins.git.GitChangeSet.getTimestamp(GitChangeSet.java:194) ... It would appears this is an issue with the Git plugin and not 1.552 of Jenkins. I upgraded Jenkins at the same time as the Git plugin and we're only seeing this error on projects using Git. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-11949) Parameterized Trigger Plugin does not pass parameters when Tomcat and JENKINS_HOME are not on the same drive
evernat resolved JENKINS-11949 as Incomplete Parameterized Trigger Plugin does not pass parameters when Tomcat and JENKINS_HOME are not on the same drive No response from the reporter, so resolving the issue as incomplete. Change By: evernat (26/Feb/14 6:57 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21954) Jenkins can not enter Job's api page with latest version 1.552
Darrell Hamilton commented on JENKINS-21954 Jenkins can not enter Job's api page with latest version 1.552 Confirmed, rolling the Git plugin back from 2.0.3 to 2.0.1 resolves 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/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-12140) Parameterized Trigger Plugin for multi-configuration project
evernat resolved JENKINS-12140 as Incomplete Parameterized Trigger Plugin for multi-configuration project No response from the reporter, so resolving the issue as incomplete. Change By: evernat (26/Feb/14 6:58 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-20264) Testflight plugin hangs job forever if Testflightapp.com is having performance issues
Steven Shipton commented on JENKINS-20264 Testflight plugin hangs job forever if Testflightapp.com is having performance issues A consequence of this issue is that a manual abort of the build will not release the lock the JVM has on the file. So aborting and trying again causes an error when trying to delete the file (e.g. with git checkout/clean) or overwrite. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21954) Jenkins can not enter Job's api page with latest version 1.552
Darrell Hamilton updated JENKINS-21954 Jenkins can not enter Job's api page with latest version 1.552 Change By: Darrell Hamilton (26/Feb/14 7:01 PM) Labels: git plugin Environment: Jenkins 1.552 , Git Plugin 2.0.3 Component/s: git This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21159) buildTimeTrend only shows last day of builds
Jesse Glick commented on JENKINS-21159 buildTimeTrend only shows last day of builds @domi well not the same content as this one because this one is fixed! But an issue blocking JENKINS-20892 requesting that >20 builds be handled by using a lazy iterator from the build widget. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Devsh sharma commented on JENKINS-21312 Vsphere plugin keeps reseting the slave when slave is configured for on demand start if you can suggest me a way to increase the Jenkins Job Queue polling time , it can be a temporary solution for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Devsh sharma edited a comment on JENKINS-21312 Vsphere plugin keeps reseting the slave when slave is configured for on demand start if you can suggest me a way to increase the Jenkins Job Queue polling time , it can be a temporary solution for me. and my problem is revert operation that is performed by this plugin , my VMs are in stopped state and the snapshot i am reverting to, is also a cold snapshot. so every 2 mins machine is reverted to cold snapshot and started by 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/groups/opt_out.
[JIRA] [core] (JENKINS-21954) Jenkins can not enter Job's api page with latest version 1.552
Mark Waite resolved JENKINS-21954 as Duplicate Jenkins can not enter Job's api page with latest version 1.552 Duplicate of JENKINS-21906 Change By: Mark Waite (26/Feb/14 7:41 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Jason Swager commented on JENKINS-21312 Vsphere plugin keeps reseting the slave when slave is configured for on demand start Sorry - I don't know of a way to change the polling time of Jenkins for cloud slaves. So far, I haven't been able to replicate your problem, even when I setup a slave that took 5 minutes to fully connect to Jenkins. I'm still trying to figure out what the problem really is. There is already code in the plugin to prevent multiple simultaneous power-ons for the same VM, but that doesn't seem to be working in your case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21855) Add markup formatter preview for parameter descriptions
dogfood commented on JENKINS-21855 Add markup formatter preview for parameter descriptions Integrated in jenkins_main_trunk #3198 [FIXED JENKINS-21855] Add preview for parameter descriptions (Revision 672954baf4570b93f66b7c1bc997f878322918ba) Result = UNSTABLE daniel-beck : 672954baf4570b93f66b7c1bc997f878322918ba Files : core/src/main/resources/hudson/model/TextParameterDefinition/config.jelly core/src/main/resources/hudson/model/ChoiceParameterDefinition/config.jelly core/src/main/resources/hudson/model/StringParameterDefinition/config.jelly core/src/main/resources/hudson/model/RunParameterDefinition/config.jelly core/src/main/resources/hudson/model/PasswordParameterDefinition/config.jelly core/src/main/resources/hudson/model/BooleanParameterDefinition/config.jelly core/src/main/resources/hudson/model/FileParameterDefinition/config.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-17450) "warning" and "performance" not counted
Michal Turek edited a comment on JENKINS-17450 "warning" and "performance" not counted Tested the latest version of the plugin, but it adds "Warning" and "Performance" issues to totals and also displays them on the graph. The described behavior may be caused by unwanted advanced configuration on configuration page. Can you confirm that? But the graph doesn't consider "No Category" and whole plugin doesn't work with "portability" severity. --errorlist Print a list of all possible error messages in XML format. ./cppcheck --xml --xml-version=2 --errorlist | grep severity | sed 's/.*severity="//' | sed 's/" msg=.*//' | sort -u error information performance portability style warning This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21780) DirectoryBrowserSupport.buildChildPaths does quadratic number of calls to check whether entries are directories
SCM/JIRA link daemon commented on JENKINS-21780 DirectoryBrowserSupport.buildChildPaths does quadratic number of calls to check whether entries are directories Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/DirectoryBrowserSupport.java http://jenkins-ci.org/commit/jenkins/ab54f136ca66dc0a29886c5dc94851adeb166356 Log: [FIXED JENKINS-21780] DirectoryBrowserSupport.FileComparator should cache isDirectory calls. (cherry picked from commit d577c0850d10348c92d763309b163223be26f68b) Conflicts: changelog.html core/src/main/java/hudson/model/DirectoryBrowserSupport.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-20534) Pegged CPU by writeSymlink calls
SCM/JIRA link daemon commented on JENKINS-20534 Pegged CPU by writeSymlink calls Code changed in jenkins User: Vincent Latombe Path: core/src/main/java/jenkins/model/PeepholePermalink.java http://jenkins-ci.org/commit/jenkins/f768fb7aed02bf4e944eff10cb2ba3007d98e560 Log: JENKINS-20534 Avoid usage of temporary file to write symlink. Creating a symlink is an atomic operation, and additionally usage of tmp file + rename performs very badly on NTFS file system because of the way the rename is tracked in the $MFT. In case symbolic links are not supported, we still fallback to a regular file. (cherry picked from commit c0742b8bff9fe407e568da7ed860f30d9ea8aedc) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-17606) Copy Artifact's fingerprinting creates second hudson.tasks.Fingerprinter_-FingerprintAction section with just the artifacts copied
SCM/JIRA link daemon commented on JENKINS-17606 Copy Artifact's fingerprinting creates second hudson.tasks.Fingerprinter_-FingerprintAction section with just the artifacts copied Code changed in jenkins User: Stefan Wolf Path: core/src/main/java/hudson/tasks/Fingerprinter.java test/src/test/java/hudson/tasks/FingerprinterTest.java http://jenkins-ci.org/commit/jenkins/1c847ccb5cdd92d36cc9344482247d6d86cff7df Log: [FIXED JENKINS-17606] Reuse existing fingerprint action if present. Prevents multiple FingerprintActions. (cherry picked from commit be7a97ee32b57dcb27b8fd6c908ebbe451220902) Conflicts: changelog.html core/src/main/java/hudson/tasks/Fingerprinter.java test/src/test/java/hudson/tasks/FingerprinterTest.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21023) WorkspaceCleanupThread does not handle folders
SCM/JIRA link daemon commented on JENKINS-21023 WorkspaceCleanupThread does not handle folders Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/WorkspaceCleanupThread.java test/src/test/java/hudson/model/WorkspaceCleanupThreadTest.java http://jenkins-ci.org/commit/jenkins/6b474c279dcc473c063a84f29d37b0123a4bc192 Log: [FIXED JENKINS-21023] Rewrote WorkspaceCleanupThread to determine where workspaces for known items should be, rather than looking for directories that look like they might be workspaces. One key advantage is that this correctly handles the new default workspace location on the master. Another is that this allows folders to be correctly skipped, and jobs in folders to be correctly deleted. A subtler advantage would be handling of configured nondefault workspace locations, and compatibility with WorkspaceLocator. (Orphaned workspaces from deleted jobs are not removed, but these were not removed before either.) (cherry picked from commit cd526e99e63ae362f2d1ce1a04c3c68a38032a5c) Conflicts: changelog.html Compare: https://github.com/jenkinsci/jenkins/compare/93500aeaa5e8...6b474c279dcc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21312) Vsphere plugin keeps reseting the slave when slave is configured for on demand start
Devsh sharma commented on JENKINS-21312 Vsphere plugin keeps reseting the slave when slave is configured for on demand start The issue is with revert operation , does code skips the revert operation if a previous slavr start operation is in progress ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-17606) Copy Artifact's fingerprinting creates second hudson.tasks.Fingerprinter_-FingerprintAction section with just the artifacts copied
Oliver Gondža reopened JENKINS-17606 Copy Artifact's fingerprinting creates second hudson.tasks.Fingerprinter_-FingerprintAction section with just the artifacts copied Change By: Oliver Gondža (26/Feb/14 8:02 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
