[JIRA] [jobconfighistory] (JENKINS-22639) Configuration for CloudSlaves & Ephemeral Nodes is persisted
Stefan Brausch resolved JENKINS-22639 as Fixed Configuration for CloudSlaves & Ephemeral Nodes is persisted Available in version 2.10. Thanks Ryan and Jesse Change By: Stefan Brausch (25/Sep/14 6:35 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory] (JENKINS-23795) error connecting jenkins to artifactory
sunil garje commented on JENKINS-23795 error connecting jenkins to artifactory I am facing the same issue checked Maven and JDK installation its correct but then also facing this issue please help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory] (JENKINS-22639) Configuration for CloudSlaves & Ephemeral Nodes is persisted
SCM/JIRA link daemon commented on JENKINS-22639 Configuration for CloudSlaves & Ephemeral Nodes is persisted Code changed in jenkins User: Stefan Brausch Path: src/main/java/hudson/plugins/jobConfigHistory/ComputerHistoryListener.java http://jenkins-ci.org/commit/jobConfigHistory-plugin/e9c4b003463a7aff44b71eee5560858bfb70520f Log: Merge pull request #27 from jenkinsci/ephemeral JENKINS-22639 Don't record changes to AbstractCloudSlaves or Ephemeral Nodes Compare: https://github.com/jenkinsci/jobConfigHistory-plugin/compare/ba17efff74b2...e9c4b003463a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-24860) Allow to disable build trigger
Martin Meyer created JENKINS-24860 Allow to disable build trigger Issue Type: Improvement Assignee: huybrechts Components: parameterized-trigger Created: 25/Sep/14 6:02 AM Description: Problem Currently, it is not possible to just disable a parameterized trigger, so the workaround is to either set the projects to build to disabled or to completely delete the trigger. Suggestion / Feature Request Could you add an entry to Trigger when build is to simply disable the trigger, e.g. Disabled (never triggered)? Project: Jenkins Priority: Trivial Reporter: Martin Meyer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-21051) Add new credential plugin displays help text in Japanese characters
Afriza Noor Arief started work on JENKINS-21051 Add new credential plugin displays help text in Japanese characters Change By: Afriza Noor Arief (25/Sep/14 3:40 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/d/optout.
[JIRA] [git] (JENKINS-24454) Windows GIT SCM Polling hung
sharon xia commented on JENKINS-24454 Windows GIT SCM Polling hung There seems to be a git process left unkilled when the job is aborted or killed. Leaving the job hung when next time it starts a new 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/d/optout.
[JIRA] [credentials] (JENKINS-21051) Add new credential plugin displays help text in Japanese characters
Afriza Noor Arief assigned JENKINS-21051 to Afriza Noor Arief Add new credential plugin displays help text in Japanese characters Change By: Afriza Noor Arief (25/Sep/14 3:16 AM) Assignee: stephenconnolly Afriza Noor Arief This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia updated JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported This issue is existing on a the latest nightly build and LTS version. It has a global impact to users as people will get artifacts download with no error but the actual size if wrong. Using "ab -n300 -c2 http://.your_artifact_link" is very easy to reproduce. Change By: sharon xia (25/Sep/14 1:53 AM) Labels: 1.554.X 1.556.X artifact-download stapler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
Ken Adams commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported Similar problem with version 1.565.1 here. We have Linux server which settle in China. And our colleagues from US and Europe report that they can hardly download an artifacts successfully since we upgrade to 1.565 from 1.515 And this even happens in our local office, with LAN I mean, so that's definitely NOT a network issue I think. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia updated JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported Change By: sharon xia (25/Sep/14 1:49 AM) Labels: 1.554.X artifact-download stapler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23868) Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported
sharon xia commented on JENKINS-23868 Use IE/Chrome/Firefox to download Jenkins artifacts has wrong size but no error reported Hi, Could you please revisit this issue? I saw it also on the latest nightly build of jenkins yesterday and still found this issue. I believe download across country is very easy to reproduce this issue. And a command "ab -n300 -c2 http://.EXE" could easily help you to verify whether this version is working properly or not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20035) see "exclusively" and "possible assigned jobs (by tags)" in node view
Dominique Brice started work on JENKINS-20035 see "exclusively" and "possible assigned jobs (by tags)" in node view Change By: Dominique Brice (25/Sep/14 1:22 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20035) see "exclusively" and "possible assigned jobs (by tags)" in node view
Dominique Brice commented on JENKINS-20035 see "exclusively" and "possible assigned jobs (by tags)" in node view Made new page more detailed, grouping jobs by labels. I think I'm pretty much done, just need to release new version of plugin with this new Node Action/page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20035) see "exclusively" and "possible assigned jobs (by tags)" in node view
Dominique Brice updated JENKINS-20035 see "exclusively" and "possible assigned jobs (by tags)" in node view Change By: Dominique Brice (25/Sep/14 1:20 AM) Attachment: NodeLinkedJobs_b.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20035) see "exclusively" and "possible assigned jobs (by tags)" in node view
Dominique Brice stopped work on JENKINS-20035 see "exclusively" and "possible assigned jobs (by tags)" in node view Change By: Dominique Brice (25/Sep/14 1:21 AM) Status: In Progress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-2717) svn polling without checkout or update
Greg Hansen commented on JENKINS-2717 svn polling without checkout or update I have a single parent project that gets a build number and queries Subversion for the head version, then passes these two values to 15 child processes (all of which work in parallel) that do their own checkouts, each at the same revision. I'd like to be able to trigger the parent project on an SCM change to the particular branch it's watching, without having to do the sync (which is about 7GB). Definitely NOT a duplicate. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
ikedam commented on JENKINS-24750 Cannot find user credentials when job is triggered with parameters I had a quick look at ssh-agents and credentials, but I don't think they depends on runtime authorization (that is, authorize-project). Do you mean your project works correct only if you uncheck "Configure Build Authorization"? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project] (JENKINS-24750) Cannot find user credentials when job is triggered with parameters
ikedam commented on JENKINS-24750 Cannot find user credentials when job is triggered with parameters Write versions of Jenkins and related plugins you use. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11889) Suspended slave do not start accepting tasks when policy changed
Daniel Beck updated JENKINS-11889 Suspended slave do not start accepting tasks when policy changed Change By: Daniel Beck (25/Sep/14 12:12 AM) Component/s: core Component/s: slave-status This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23016) Suspended slaves not online despite being past starting time
Daniel Beck updated JENKINS-23016 Suspended slaves not online despite being past starting time More of a core issue I think. Change By: Daniel Beck (25/Sep/14 12:11 AM) Assignee: Kohsuke Kawaguchi Component/s: core Component/s: ssh-slaves This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [credentials] (JENKINS-24859) LDAP cresentials with sAMAccountName including uppercase letter does not work with Global Security
Fory Horio created JENKINS-24859 LDAP cresentials with sAMAccountName including uppercase letter does not work with Global Security Issue Type: Bug Assignee: stephenconnolly Components: credentials Created: 25/Sep/14 12:07 AM Description: With LDAP auth, the sAMAccountName containing uppercase case letters does not work with Global Security. For example, user ID "testuser" can be specified in the Global Security as expected. However, user ID "TEstuser" does not work as expected with the Global Security specified as TEstuser. In the Jenkis home dir there is a dir for either users/testuser/config.xml and users/TEstuser/config.xml. It just doesn't work with the ID containing uppercase letters. Environment: Version 1.579 on Ubuntu 12.04.5 LTS Project: Jenkins Priority: Critical Reporter: Fory Horio This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-24331) [JIRA Plugin] Progress JIRA issue by workflow action does not work if field is required
Jonathan Langevin commented on JENKINS-24331 [JIRA Plugin] Progress JIRA issue by workflow action does not work if field is required Just a note, I worked around this issue by creating a workflow action that is only accessible by the Jenkins user account. By doing so, I can avoid custom screens or required fields that would normally affect a workflow action (transition) and otherwise breaks this feature. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2] (JENKINS-23935) Allow tags for all instances in an EC2 cloud configuration
Sam Xiao commented on JENKINS-23935 Allow tags for all instances in an EC2 cloud configuration +1 nice feature! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24763) Long running OldDataMonitor.doDiscard() results in thread starvation
recampbell commented on JENKINS-24763 Long running OldDataMonitor.doDiscard() results in thread starvation Latest pull request: https://github.com/jenkinsci/jenkins/pull/1402 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24836) Ability to fail a build when no executors are available
Ilya Ivanov commented on JENKINS-24836 Ability to fail a build when no executors are available Well, generally a vanilla Jenkins job may not work properly (and don't notify about it) due to the following reasons (I'm referring to bash here): 1) The script isn't catching all errors. Jenkins launches the scripts with "-xe" options by default. A more robust way is "-xeu -o pipefail". This is trivial to do. 2) Not all commands return correct exit code on failure. "Log parser" plugin often helps here. 3) The node isn't available at the time, as described in this issue. Right now I'm using https://wiki.jenkins-ci.org/display/JENKINS/Monitor+and+Restart+Offline+Slaves, but it's not enough. 4) Some step hangs, so the build is never completed and the next one is in queue forever. Fortunately, there's a "Build timeout" plugin for that. I think that's all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24825) Missing build history moving a job when BuildDir is set to a custom location
dogfood commented on JENKINS-24825 Missing build history moving a job when BuildDir is set to a custom location Integrated in jenkins_main_trunk #3706 [FIXED JENKINS-24825] define hudson.model.AbstractItem#movedTo (Revision 9b3f48853d481b848f91b4f6fb7d96e87e81b500) test case for JENKINS-24825 (Revision 8975b0e0b5b5c553301c7bc85fd81d080a658b96) Result = SUCCESS Nicolas De Loof : 9b3f48853d481b848f91b4f6fb7d96e87e81b500 Files : core/src/main/java/hudson/model/Items.java core/src/main/java/hudson/model/AbstractItem.java core/src/main/java/hudson/model/Job.java changelog.html Nicolas De Loof : 8975b0e0b5b5c553301c7bc85fd81d080a658b96 Files : test/src/test/java/hudson/model/ItemsTest.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/d/optout.
[JIRA] [ci-game] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTe
Philip Aston commented on JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Looking good. [ci-game] scored: 1.0 Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22514) Zip generated from "all files in zip" contains the wrong slashes
Daniel Beck assigned JENKINS-22514 to Daniel Beck Zip generated from "all files in zip" contains the wrong slashes Change By: Daniel Beck (24/Sep/14 10:09 PM) Assignee: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22514) Zip generated from "all files in zip" contains the wrong slashes
Daniel Beck
commented on JENKINS-22514
Zip generated from "all files in zip" contains the wrong slashes
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/util/io/ZipArchiver.java shows how it's supposed to be done.
String relativePath = _relativePath.replace('\\', '/');
Unfortunately this would introduce a bug on platforms where backslash is a legal file name character. Something like replace(File.separator, '/') should do it though.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted
swolk commented on JENKINS-24832 Failed maven builds using -T are showing up as Aborted Sorry about that. Yep, that is my result as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted
swolk updated JENKINS-24832 Failed maven builds using -T are showing up as Aborted Change By: swolk (24/Sep/14 10:06 PM) Attachment: screenshot-1.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted
Daniel Beck edited a comment on JENKINS-24832 Failed maven builds using -T are showing up as Aborted (Instructions failed to mention I actually need a goal...) I get one failed, one successful, and one aborted module, and the overall build status is aborted. Jenkins 1.580(ish), Maven plugin 2.6, building on the CentOS 6 Jenkins master node. So at least it's reproducible. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24832) Failed builds are showing up as Aborted
Daniel Beck commented on JENKINS-24832 Failed builds are showing up as Aborted The overall build is failed for me, and all three module builds are shown as skipped. Jenkins 1.580(-ish, a developer build) with Maven plugin 2.6. Builds run on the master node, which is a CentOS 6. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted
swolk updated JENKINS-24832 Failed maven builds using -T are showing up as Aborted Change By: swolk (24/Sep/14 10:04 PM) Summary: Failed maven builds using -T are showing up as Aborted This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24832) Failed builds are showing up as Aborted
swolk edited a comment on JENKINS-24832 Failed builds are showing up as Aborted OK, this is very easy to reproduce. Create a maven job for this example multi-module project https://github.com/idodevjobs/sample-multi-module-project. For root pom, use parent module. Add -T4 for Maven Goals and Options to enable multiple threads. Kick off the build and 'sample-multi-module-web Maven Webapp' module should fail because of missing dependency. Job status will show as Aborted instead of Failed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24832) Failed builds are showing up as Aborted
swolk commented on JENKINS-24832 Failed builds are showing up as Aborted OK, this is very easy to reproduce. Create a maven job for this example multi-module project https://github.com/idodevjobs/sample-multi-module-project. Root root pom use parent module. Add -T4 for Maven Goals and Options to enable multiple threads. Kick off the build and 'sample-multi-module-web Maven Webapp' module should fail because of missing dependency. Job status will show as Aborted instead of Failed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24833) Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Mark Waite edited a comment on JENKINS-24833 Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds It appears from the screen shot that you upgraded from a git 1.x release to git plugin 2.2.6. That may indicate that you need to make some minor change to the job definition, and save it. That minor change and save may switch the job configuration file from using the git plugin 1.x settings to using the latest settings. Sorry for this junk comment. I confused this bug report with a completely different bug report. I'll need to stare at this more before I say anything else foolish. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22514) Zip generated from "all files in zip" contains the wrong slashes
Daniel Beck commented on JENKINS-22514 Zip generated from "all files in zip" contains the wrong slashes Confirmation that it worked correctly up to and including 1.531 would be nice. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [powershell] (JENKINS-15890) [PATCH] Powershell improvements
Hector Magnanao edited a comment on JENKINS-15890 [PATCH] Powershell improvements Can some describe how to apply this patch to the powershell plugin error for executionpolicy problems ? I don't see these 2 files under my Jenkins home directory. And does this patch work for Powershell 3.0 ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [powershell] (JENKINS-15890) [PATCH] Powershell improvements
Hector Magnanao commented on JENKINS-15890 [PATCH] Powershell improvements Can some describe how to apply this patch to the powershell plugin error for executionpolicy problems ? I don't see these 2 files under my Jenkins home directory. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24857) Builds happening because of false-positive SCM changes
Rob Petti assigned JENKINS-24857 to Unassigned Builds happening because of false-positive SCM changes Change By: Rob Petti (24/Sep/14 9:34 PM) Assignee: Rob Petti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7793) Failed to launch slave to Windows 7 while all config steps done
Daniel Beck commented on JENKINS-7793 Failed to launch slave to Windows 7 while all config steps done wgracelee: It should work the same way. Try -noCertificateCheck to work around your admins being too cheap and/or lazy to get a properly recognized SSL cert. I cannot find your message to jenkinsci-users, make sure it actually got through. Another option would be asking in #jenkins on Freenode. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7793) Failed to launch slave to Windows 7 while all config steps done
wgracelee commented on JENKINS-7793 Failed to launch slave to Windows 7 while all config steps done This is the command to start the https master on Linux: nohup java -XX:+CMSClassUnloadingEnabled -jar "$WAR" --httpPort=-1 --ajp13Port=-1 --httpsPort=$port --httpsKeyStore=$HUDSON_HOME/keystore.jks --httpsKeyStorePassword= --prefix= This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7793) Failed to launch slave to Windows 7 while all config steps done
wgracelee commented on JENKINS-7793 Failed to launch slave to Windows 7 while all config steps done Daniel, Thanks for updating this ticket. The steps there are horrible. What we really like to do is to have Windows 7 connect to our Jenkins master running on https protocol. When the master is on http, we can just use 'java -jar slave.jar -jnlpUrl http://://computer/-jnlp/slave-agent.jnlp -secret ' on slave to connect to master. If we can run a command from the Windows 7 to connect to https master, that'll be great. I googled and asked the question in Jenkins users mailing list and couldn't find a good answer. If you or someone can help us on this, that'll be great. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24825) Missing build history moving a job when BuildDir is set to a custom location
SCM/JIRA link daemon commented on JENKINS-24825 Missing build history moving a job when BuildDir is set to a custom location Code changed in jenkins User: Nicolas De Loof Path: changelog.html core/src/main/java/hudson/model/AbstractItem.java core/src/main/java/hudson/model/Items.java core/src/main/java/hudson/model/Job.java test/src/test/java/hudson/model/ItemsTest.java http://jenkins-ci.org/commit/jenkins/d54bc061b125c580346e42b9af4e6bdb3c6646ef Log: Merge branch 'JENKINS-24825' Compare: https://github.com/jenkinsci/jenkins/compare/b2bb58895f2d...d54bc061b125 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24788) Cannot run program "/bin/java" on maven 3 projects
Stephane Odul updated JENKINS-24788 Cannot run program "/bin/java" on maven 3 projects Change By: Stephane Odul (24/Sep/14 9:20 PM) Environment: 1.580, Ubuntu 12.04 LTS 64 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24836) Ability to fail a build when no executors are available
Daniel Beck commented on JENKINS-24836 Ability to fail a build when no executors are available Please explain other conditions etc. so I get a more complete picture what this is about. It may be possible to implement fairly easily. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24836) Ability to fail a build when no executors are available
Ilya Ivanov commented on JENKINS-24836 Ability to fail a build when no executors are available There are other conditions, but they can be worked around with plugins. This one cannot. No, the plugins that you mentioned don't exactly solve the problem. The node status isn't relevant. Job status is. (To elaborate, for example, the node might itself be launched only periodically. Or have some issues with connectivity. Or resources. Or something else. In that case using a plugin that notifies about node availability will result in a number of alerts, which will render the notification system useless). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22514) Zip generated from "all files in zip" contains the wrong slashes
Oleg Nenashev assigned JENKINS-22514 to Unassigned Zip generated from "all files in zip" contains the wrong slashes Change By: Oleg Nenashev (24/Sep/14 9:03 PM) Assignee: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-24808) PluginFirstClassLoader not supported by gradle-jpi-plugin
SCM/JIRA link daemon commented on JENKINS-24808 PluginFirstClassLoader not supported by gradle-jpi-plugin Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md README.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiExtension.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiManifest.groovy http://jenkins-ci.org/commit/gradle-jpi-plugin/01161be5db061aa2a8fad177b0343241d4e49b30 Log: Merge pull request #15 from daspilker/JENKINS-24808 Added support for PluginFirstClassLoader Compare: https://github.com/jenkinsci/gradle-jpi-plugin/compare/930b9990cb7d...01161be5db06 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-24808) PluginFirstClassLoader not supported by gradle-jpi-plugin
Daniel Spilker resolved JENKINS-24808 as Fixed PluginFirstClassLoader not supported by gradle-jpi-plugin Change By: Daniel Spilker (24/Sep/14 9:01 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24836) Ability to fail a build when no executors are available
Daniel Beck commented on JENKINS-24836 Ability to fail a build when no executors are available Before a build is started by starting execution on an executor, there is no build, just a queue item. Those cannot have a result like builds, and nothing about them is recorded either. If you cancel one, no "failed build" or "canceled build" entry is created, and no build numbers are assigned either. Is node being/going offline just an example, or is this the one condition that's relevant? If the latter, plugins like https://wiki.jenkins-ci.org/display/JENKINS/Extreme+Notification+Plugin or http://jenkins-enterprise.cloudbees.com/docs/user-guide-bundle/nodes-plus.html would solve this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory] (JENKINS-24858) Update scm tag in pom.xml when doing a Release Staging
mhaefele created JENKINS-24858 Update scm tag in pom.xml when doing a Release Staging Issue Type: Improvement Assignee: yossis Components: artifactory Created: 24/Sep/14 8:40 PM Description: When using the maven release plugin, it updates the ... value to match the scm tag for that release. So for example: ... 4.2-SNAPSHOT scm:git:https://github.com/MY_TEAM/my_project.git HEAD ... is changed to ... 4.2 scm:git:https://github.com/MY_TEAM/my_project.git my_project_4.2 ... for the release and then to ... 4.3-SNAPSHOT scm:git:https://github.com/MY_TEAM/my_project.git HEAD ... for the next snapshot version. This is really handy for being able to instantly track a jar (with pom file) back to the source it was released from. Improvement: Add this behavior to the Jenkins Artifactory plugin. Project: Jenkins Priority: Minor Reporter: mhaefele This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24836) Ability to fail a build when no executors are available
Ilya Ivanov commented on JENKINS-24836 Ability to fail a build when no executors are available Not sure what do you mean by "there's no build to fail". It's right there, in queue, "job #12345", waiting for the next available executor. Anyway, I don't really see a difference. I'm asking for a way to be sure that either the job runs in time or I get a notification that it didn't. I guessed failing it would be the natural way. "Queue watcher" would do just as well, I suppose. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24857) Builds happening because of false-positive SCM changes
swolk created JENKINS-24857 Builds happening because of false-positive SCM changes Issue Type: Bug Assignee: Rob Petti Attachments: build.xml, changelog.xml, config.xml, polling.log, screenshot-1.jpg Components: perforce Created: 24/Sep/14 8:30 PM Description: We're seeing full builds happening because checkins were detected, but no changelogs are shown. When comparing to previous build, they have synced to same changelist which is the latest. Environment: Jenkins 1.565.2 Perforce 1.3.28-SNAPSHOT Project: Jenkins Priority: Critical Reporter: swolk This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24857) Builds happening because of false-positive SCM changes
swolk updated JENKINS-24857 Builds happening because of false-positive SCM changes Change By: swolk (24/Sep/14 8:31 PM) Attachment: screenshot-1.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24856) Perforce View Mask option gets reset when editing job configuration
Rob Petti commented on JENKINS-24856 Perforce View Mask option gets reset when editing job configuration If you can donate time to fix bugs or do pre-release testing, then that would be fantastic. It also might be worth checking out Perforce's official Jenkins plugin, https://wiki.jenkins-ci.org/display/JENKINS/P4+Plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ci-game] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTe
Richard Bergoin edited a comment on JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Maybe you can install and provide feedback using this snapshot : https://jenkins.ci.cloudbees.com/job/plugins/job/ci-game-plugin/23/org.jenkins-ci.plugins$ci-game/ EDIT : I just installed it : [ci-game] scored: 1.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24856) Perforce View Mask option gets reset when editing job configuration
Rob Petti assigned JENKINS-24856 to Unassigned Perforce View Mask option gets reset when editing job configuration Change By: Rob Petti (24/Sep/14 8:23 PM) Assignee: Rob Petti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-24298) Localizer is not generating Messages classes
SCM/JIRA link daemon commented on JENKINS-24298 Localizer is not generating Messages classes Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/LocalizerTask.groovy http://jenkins-ci.org/commit/gradle-jpi-plugin/8b84f4aefad5379b1ab3ba672bebd8c7a38a3ca3 Log: Merge pull request #11 from daspilker/JENKINS-24298 Fix for JENKINS-24298 Compare: https://github.com/jenkinsci/gradle-jpi-plugin/compare/59b81270befb...8b84f4aefad5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-24298) Localizer is not generating Messages classes
SCM/JIRA link daemon commented on JENKINS-24298 Localizer is not generating Messages classes Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/LocalizerTask.groovy http://jenkins-ci.org/commit/gradle-jpi-plugin/2c095364bf1e3efd1d0ca3b16aadcf90c8f7a635 Log: set task input files, fix for JENKINS-24298 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-24820) Environment is not fulfilled
Marcin Hawraniak
commented on JENKINS-24820
Environment is not fulfilled
I had the same. Make sure that build triggers in job configuration:
Build when a change is pushed to GitHub - is not checked (I had it enabled and it caused ${sha1} not to be set, which makes sense as this checkbox is for "Github plugin", not for "GitHub pull request builder plugin" and reacts for every push),
GitHub Pull Request Builder - is checked and reacts only for pull reqests and issue comments (webhook setup done automatically by Jenkins).
Verify also Webhook in your project settings:
payload url: http://jenkins.com/ghprbhook/
content: x-www-form-urlencoded
events: pull request, issue comment
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-24298) Localizer is not generating Messages classes
Daniel Spilker resolved JENKINS-24298 as Fixed Localizer is not generating Messages classes Change By: Daniel Spilker (24/Sep/14 8:20 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24856) Perforce View Mask option gets reset when editing job configuration
swolk updated JENKINS-24856 Perforce View Mask option gets reset when editing job configuration Change By: swolk (24/Sep/14 8:18 PM) Attachment: after_save.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-19942) gradle/groovy plugin cannot build test task
Daniel Spilker resolved JENKINS-19942 as Fixed gradle/groovy plugin cannot build test task Change By: Daniel Spilker (24/Sep/14 8:17 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer] (JENKINS-24845) jenkins mailer version 1.11 fails to send test mail
marlene cote resolved JENKINS-24845 as Fixed jenkins mailer version 1.11 fails to send test mail The darn McAfee virus scanner bit me. Sorry for the chaff. Change By: marlene cote (24/Sep/14 8:16 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce] (JENKINS-24856) Perforce View Mask option gets reset when editing job configuration
swolk commented on JENKINS-24856 Perforce View Mask option gets reset when editing job configuration The workaround is to leave 'Use View Mask' checked and all it's sub-options unchecked, but honestly, would be great to fix this behavior. Also, when is the next release on Perforce plugin? Hasn't been a release since January. BTW, I'm happy to make some donations on behalf of my company, thanks for the work you guys 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/d/optout.
[JIRA] [perforce] (JENKINS-24856) Perforce View Mask option gets reset when editing job configuration
swolk created JENKINS-24856 Perforce View Mask option gets reset when editing job configuration Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 24/Sep/14 8:13 PM Description: In the Perforce configuration for a job, when I uncheck 'Use View Mask' option and save, then edit configuration again, the 'Use View Mask option' AND 'Use mask when polling' options are checked which could lead to bad results if I saved without unchecking them again. Environment: Jenkins 1.565.2 Perforce 1.3.28-SNAPSHOT Project: Jenkins Priority: Critical Reporter: swolk This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle] (JENKINS-19417) Jenkins Gradle Plugin - 2nd invoke call to "Invoke Gradle Script" within a Jenkins job, makes first call lose Gradle version list/box
Daniel Spilker updated JENKINS-19417 Jenkins Gradle Plugin - 2nd invoke call to "Invoke Gradle Script" within a Jenkins job, makes first call lose Gradle version list/box This is an issue of the Gradle Plugin (the build step), not of the Gradle JPI Plugin (the plugin for Gradle to build Jenkins plugins). Change By: Daniel Spilker (24/Sep/14 8:10 PM) Component/s: gradle Component/s: gradle-jpi-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-19942) gradle/groovy plugin cannot build test task
Daniel Spilker commented on JENKINS-19942 gradle/groovy plugin cannot build test task The problem is that the Gradle JPI plugin sets up the build to use http://repo.jenkins-ci.org/releases/. But the Jenkins Maven Parent POM (org.jenkins-ci.main:pom) uses http://repo.jenkins-ci.org/public/ which contains more artifacts. So the Gradle build does not see many artifacts which are neither in Maven Central nor in the Jenkins releases repo. Pull request with a fix: https://github.com/jenkinsci/gradle-jpi-plugin/pull/13/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/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-19942) gradle/groovy plugin cannot build test task
Daniel Spilker assigned JENKINS-19942 to Daniel Spilker gradle/groovy plugin cannot build test task Change By: Daniel Spilker (24/Sep/14 8:00 PM) Assignee: abayer Daniel Spilker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-23603) instance-identity dependency is missing
Daniel Spilker resolved JENKINS-23603 as Fixed instance-identity dependency is missing Change By: Daniel Spilker (24/Sep/14 8:01 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle] (JENKINS-21653) Gradle build command not working as Gradle version is unavailable for selection in Configure
Daniel Spilker updated JENKINS-21653 Gradle build command not working as Gradle version is unavailable for selection in Configure This does not seem to be related to the Gradle JPI Plugin, which is a plugin for Gradle to build Jenkins plugins. Change By: Daniel Spilker (24/Sep/14 7:56 PM) Component/s: gradle-jpi-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-24808) PluginFirstClassLoader not supported by gradle-jpi-plugin
Daniel Spilker assigned JENKINS-24808 to Daniel Spilker PluginFirstClassLoader not supported by gradle-jpi-plugin Change By: Daniel Spilker (24/Sep/14 7:56 PM) Assignee: abayer Daniel Spilker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-24298) Localizer is not generating Messages classes
Daniel Spilker assigned JENKINS-24298 to Daniel Spilker Localizer is not generating Messages classes Change By: Daniel Spilker (24/Sep/14 7:57 PM) Assignee: abayer Daniel Spilker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-23603) instance-identity dependency is missing
Daniel Spilker assigned JENKINS-23603 to Daniel Spilker instance-identity dependency is missing Change By: Daniel Spilker (24/Sep/14 7:56 PM) Assignee: abayer Daniel Spilker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle] (JENKINS-16147) Java classes generation from XSD with xjc does not work using Gradle plugin
Daniel Spilker updated JENKINS-16147 Java classes generation from XSD with xjc does not work using Gradle plugin I think this is a problem of the Gradle Plugin (the build step), not the Gradle JPI Plugin (the plugin for building Jenkins plugins with Gradle). But please correct me if I'm wrong. Change By: Daniel Spilker (24/Sep/14 7:54 PM) Component/s: gradle Component/s: gradle-jpi-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ci-game] (JENKINS-24478) Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTe
Richard Bergoin commented on JENKINS-24478 Publisher hudson.plugins.cigame.GamePublisher aborted due to exception NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction Maybe you can install and provide feedback using this snapshot : https://jenkins.ci.cloudbees.com/job/plugins/job/ci-game-plugin/23/org.jenkins-ci.plugins$ci-game/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle] (JENKINS-15754) Jenkins fails to save configuration when using Invoke Gradle with net.sf.json.JSONException: null object
Daniel Spilker updated JENKINS-15754 Jenkins fails to save configuration when using Invoke Gradle with net.sf.json.JSONException: null object As far as I see this has nothing to do with the gradle-jpi-plugin. Change By: Daniel Spilker (24/Sep/14 7:51 PM) Component/s: gradle-jpi-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24855) Build Review not working with Swarm
Michael Rose created JENKINS-24855 Build Review not working with Swarm Issue Type: Bug Assignee: Unassigned Attachments: p4plugin-buildreview-syncissue-console.png, p4plugin-buildreview-syncissue-parameters.png Components: p4 Created: 24/Sep/14 7:46 PM Description: Given the following request: [24/Sep/2014:11:56:11 -0500] 10.1.58.229 TLSv1 DHE-RSA-AES256-SHA "GET /jenkins/job/test-new-p4plugin/review/build?status=shelved&review247&pass=http%3A%2F%2Fswarm-test.csdt.sjm.com%2Freviews%2F247%2Ftests%2Fpass%2FB40F09C6-006B-679A-05C6-511CE789B669%2F&fail=http%3A%2F%2Fswarm-test.csdt.sjm.com%2Freviews%2F247%2Ftests%2Ffail%2FB40F09C6-006B-679A-05C6-511CE789B669%2F HTTP/1.1" - Note: This is the request swarm makes when I shelve a changelist for review The associated Jenkins build fails to sync. From what I can tell, it does not look like the Build Review job respects the review parameter when building the job. Attached are screenshots for the console output and build parameters. Notice that: 1. The "review" parameter from the request does not appear in the build parameters screenshot. 2. The build attempted to sync to changelist 267 (the review changelist) and then tried to unshelve changelist 0. I would have expected it to sync to the latest revision and then unshelve changelist 267. Environment: Jenkins version 1.580 P4 plubin version 1.0.14 Project: Jenkins Priority: Major Reporter: Michael Rose This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4] (JENKINS-24855) Build Review not working with Swarm
Michael Rose updated JENKINS-24855 Build Review not working with Swarm Change By: Michael Rose (24/Sep/14 7:47 PM) Environment: Jenkins version 1.580P4 plubin plugin version 1.0.14 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-23603) instance-identity dependency is missing
SCM/JIRA link daemon commented on JENKINS-23603 instance-identity dependency is missing Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy http://jenkins-ci.org/commit/gradle-jpi-plugin/4e0673361e7ea8789759be81fd942f92b6a81fb6 Log: Merge pull request #9 from daspilker/JENKINS-23603 JENKINS-23603 do not exclude instance-identity Compare: https://github.com/jenkinsci/gradle-jpi-plugin/compare/f1e4592f8576...4e0673361e7e This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-23603) instance-identity dependency is missing
SCM/JIRA link daemon commented on JENKINS-23603 instance-identity dependency is missing Code changed in jenkins User: Daniel Spilker Path: CHANGELOG.md src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy http://jenkins-ci.org/commit/gradle-jpi-plugin/b305f1e1a0182c151aa44c0ab2327d9cb686d91f Log: fixed JENKINS-23603, do not exclude instance-identity This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24802) notifyCommit don't trigger a build if two svn repositories have same url start
Richard Bergoin commented on JENKINS-24802 notifyCommit don't trigger a build if two svn repositories have same url start Ok, fixed it this time with PR 99 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [exclusive-execution] (JENKINS-24854) Exclusive Execution Plugin stays in shutdown mode if build aborts
Frank Canova created JENKINS-24854 Exclusive Execution Plugin stays in shutdown mode if build aborts Issue Type: Bug Assignee: Marco Ambu Components: exclusive-execution Created: 24/Sep/14 7:34 PM Description: If job aborts, for example from a time out, then the plug in leaves Jenkins in the shutdown mode and other jobs in the queue are unable to start. Environment: Jenkins ver. 1.579 Exclusive Execution Plugin 0.7 Project: Jenkins Labels: shutdown Priority: Minor Reporter: Frank Canova This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [customtools-plugin] (JENKINS-24853) custom tools plugin doesn't work with matrix job
kyle rockman created JENKINS-24853 custom tools plugin doesn't work with matrix job Issue Type: Bug Assignee: Oleg Nenashev Components: customtools-plugin Created: 24/Sep/14 7:32 PM Description: [CustomTools] - Skipping installation of tools at the master job FATAL: null java.lang.NullPointerException at com.cloudbees.jenkins.plugins.customtools.CustomToolInstallWrapper.decorateLauncher(CustomToolInstallWrapper.java:154) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:581) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:491) at hudson.model.Run.execute(Run.java:1745) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:306) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) Environment: jenkins = 1.579 customtools-plugin = 0.4.1 Project: Jenkins Priority: Critical Reporter: kyle rockman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24836) Ability to fail a build when no executors are available
Daniel Beck commented on JENKINS-24836 Ability to fail a build when no executors are available There is no build to fail if there's no executor available to run on. Please explain in more detail what you are asking for. Wouldn't it be more useful to have a "queue watcher" and if certain items are queued longer than a certain timeout, send a notification? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24833) Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Loren Klingman commented on JENKINS-24833 Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds That's a strange thing to have happened. I just added the git merge pushing a day or two ago so the job details should have been up to date. I also installed some plugin updates at that time, but I stay pretty up to date on the plugins so I don't think I would have gone from 1.x to 2.2.6. When I originally configured this job and installed Jenkins in July or August, I did start with a sample job configuration file so if I have old settings, more than likely they came from that file rather than from something I had installed. I just resaved is there something I should be looking to change on the configuration page? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24846) UI Improvement: Update Center
Daniel Beck commented on JENKINS-24846 UI Improvement: Update Center Reordered so it makes sense: Jenkins should be polling for updates automatically by default (Check Now button should be redundant...Chrome doesn't have it, why should Jenkins?). It does, once a day. Currently to Update plugins or Jenkins Core: Click on Manage Jenkins Click on Manage Plugins Click on Advanced Tab Scroll down to bottom of page Click on Check Now Click on Return to Update Center Click on All link Click on Update Click on Restart Jenkins check box We cannot hammer the update centers whenever someone clicks on 'Manage Plugins', so this is the way it'll be if you cannot deal with minimally out of date data. Click on Manage Jenkins Click on Manage Plugins Click on Automatically Upgrade button Click on Restart Jenkins checkbox. Not true, step 2 is not necessary. Add a pancake icon to the top right corner (like Chrome) that is has the same visibility as the Manage Jenkins menu link that changes color (like Chrome does to green) to some color to indicate there is core or plugin updates available. Maybe https://github.com/daniel-beck/jenkins-visible-administrative-monitors-plugin can help. "Restart Jenkins when no jobs running" should be the convention (no need for checkboxseems redundant to me) Restarts are a big deal for many Jenkins installs, so I disagree completely. Under Manage Jenkins I should be able subscribe to the "Latest and Greatest" channel or the "LTS" channel. You can in Manage Jenkins » Manage Plugins » Advanced. Other than it probably shouldn't be necessary to click on 'Manage Jenkins' to see that updates are available, I see no useful suggestion in this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hipchat] (JENKINS-24852) Jenkins-HipChat plugin does not send message to internal hosted HipChat server
Kevin Cheng created JENKINS-24852 Jenkins-HipChat plugin does not send message to internal hosted HipChat server Issue Type: Bug Assignee: Unassigned Components: hipchat Created: 24/Sep/14 6:54 PM Description: We used to use hosted HC server with Jenkins-HC plugin v0.1.6. We recently installed and hosted our internal HC server which we have to upgrade the plugin version to 0.1.8 in order to specify the server URL. We tried to use both the server based token or room based token, and with / without the default room value filled in the global configuration, and the message still did not get send. I tried to use Curl with v1 API using the server token, at least I validated HC server side is getting the message with direct API call. Environment: Jenkins 1.565.2, HipChat plugin v 0.1.8 Project: Jenkins Priority: Major Reporter: Kevin Cheng This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-24851) downstreamParameterized step does not block on completion of downstream job
Jordan Spiker
created JENKINS-24851
downstreamParameterized step does not block on completion of downstream job
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin, parameterized-trigger
Created:
24/Sep/14 6:51 PM
Description:
When using the 'downstreamParameterized()' step, creating a 'blockingThresholds' map does not cause the downstream job to wait for completion.
steps {
downstreamParameterized {
trigger('vxworks-kernel-build', 'SUCCESS', false,
['unstable': 'UNSTABLE']) {
This creates the following relevant XML for the generated job:
UNSTABLE
1
YELLOW
The block should include
true
or else the upstream job will not wait for completion of the downstream job.
Project:
Jenkins
Priority:
Major
Reporter:
Jordan Spiker
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
Anatoly Bubenkov commented on JENKINS-24457 VERY poor performance on big json files. thanks! and sorry for annoying me This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult] (JENKINS-24457) VERY poor performance on big json files.
teilo reopened JENKINS-24457 VERY poor performance on big json files. Will. Attempt to reproduce Change By: teilo (24/Sep/14 6:28 PM) Resolution: Not A Defect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-24833) Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds
Mark Waite commented on JENKINS-24833 Git Plugin Publisher Publishes on Failed Build even though set to push only if build succeeds It appears from the screen shot that you upgraded from a git 1.x release to git plugin 2.2.6. That may indicate that you need to make some minor change to the job definition, and save it. That minor change and save may switch the job configuration file from using the git plugin 1.x settings to using the latest settings. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [support-core] (JENKINS-24850) Collect hot threads
recampbell created JENKINS-24850 Collect hot threads Issue Type: Improvement Assignee: Steven Christou Components: support-core Created: 24/Sep/14 6:19 PM Description: Collect thread dumps from the "hottest" threads, perhaps every n minutes. Background: https://weblogs.java.net/blog/brucechapman/archive/2008/03/hot_threads.html http://java.dzone.com/news/porting-hot-thread-detector-vi Example implementation: https://github.com/elasticsearch/elasticsearch/blob/1816951b6b0320e7a011436c7c7519ec2bfabc6e/src/main/java/org/elasticsearch/monitor/jvm/HotThreads.java Sample output: https://gist.github.com/mlamp/3852210 Project: Jenkins Priority: Minor Reporter: recampbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
SCM/JIRA link daemon commented on JENKINS-14276 Git SCM-polling doesn't work when using a parametrized branch-name Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/ea62814db213b41b0e8fe99dbca6898aa369da97 Log: [FIXED JENKINS-20427] [FIXED JENKINS-14276] expanded vars in branch spec for remote polling This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
SCM/JIRA link daemon commented on JENKINS-20427 Build Parameter variable in branch name causes polling to detect false changes in GIT Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/plugins/git/GitSCM.java http://jenkins-ci.org/commit/git-plugin/ea62814db213b41b0e8fe99dbca6898aa369da97 Log: [FIXED JENKINS-20427] [FIXED JENKINS-14276] expanded vars in branch spec for remote polling This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-24810) The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop
Daniel Beck resolved JENKINS-24810 as Not A Defect The "invoke build for each property file" ParameterFactory Generates More than One Set of Builds, Doesn't Stop Change By: Daniel Beck (24/Sep/14 5:29 PM) Status: Open Resolved Assignee: huybrechts Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20697) API wrong number of arguments on build specific endpoints
Daniel Beck commented on JENKINS-20697 API wrong number of arguments on build specific endpoints The affected build's build.xml would be helpful then. (Or maybe on an affected instance trying to bisect-search for the responsible element) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24818) Unable to Access Jenkins URL in slave machines
Daniel Beck resolved JENKINS-24818 as Not A Defect Unable to Access Jenkins URL in slave machines http://jenkins-ci.org/content/mailing-lists http://jenkins-ci.org/content/chat Change By: Daniel Beck (24/Sep/14 5:26 PM) Status: Reopened Resolved Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
