[JIRA] [pretested-integration-plugin] (JENKINS-25831) Branch not found (our case 12373)
Bue Petersen commented on JENKINS-25831 Branch not found (our case 12373) I'm told there might be a dependency on git 1.8 or newer. Related to using squash commit and maybe adding new files in the commits. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-25831) Branch not found (our case 12373)
Bue Petersen commented on JENKINS-25831 Branch not found (our case 12373) No wait a moment, it seems like we are testing with git 1.7.9.5 on the build slaves. I will ask a developer to briefly look at the problem, but else I will recommend to wait for the release that comes out in the following week. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Ralf Mühle commented on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL Having similar issue with Jenkins 1.591 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-25818) Next day after a Jenkins reboot the report is empty
centic resolved JENKINS-25818 as Duplicate Next day after a Jenkins reboot the report is empty Already discussed in JENKINS-23708, hopefully a fixed version will be available shortly. Change By: centic (29/Nov/14 10:39 AM) Status: Open Resolved Assignee: OgnjenBubalo centic Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-25832) Launch multiple slaves in parallel for jobs with same node label
arazauci
created JENKINS-25832
Launch multiple slaves in parallel for jobs with same node label
Issue Type:
New Feature
Assignee:
Francis Upton
Components:
ec2-plugin
Created:
29/Nov/14 10:52 AM
Description:
I use build flow plugin to kick off 200+ jobs. Each of these jobs has the same label. During this scenario, 200+ jobs are queued up. The ec2 plugin seems to process one job at time and this is a painfully slow process.
It seems that the AWS JAVA SDK allows for launching multiple ec2 instances. Can the ec2 plugin detect the number of jobs with the same label in the queue, and then launch that many ec2 instances in parallel?
http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/ec2/model/RunInstancesRequest.html#RunInstancesRequest%28java.lang.String,%20java.lang.Integer,%20java.lang.Integer%29
private EC2AbstractSlave provisionOndemand(TaskListener listener) throws AmazonClientException, IOException {
PrintStream logger = listener.getLogger();
AmazonEC2 ec2 = getParent().connect();
try {
String msg = "Launching " + ami + " for template " + description;
logger.println(msg);
LOGGER.info(msg);
KeyPair keyPair = getKeyPair(ec2);
RunInstancesRequest riRequest = new RunInstancesRequest(ami, 1, 1);
Project:
Jenkins
Priority:
Critical
Reporter:
arazauci
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [embeddable-build-status-plugin] (JENKINS-25306) Build status badge for specific build of a job
Christian Galsterer resolved JENKINS-25306 as Fixed Build status badge for specific build of a job Available with version 1.6 Change By: Christian Galsterer (29/Nov/14 11:00 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [embeddable-build-status-plugin] (JENKINS-25306) Build status badge for specific build of a job
Christian Galsterer closed JENKINS-25306 as Fixed Build status badge for specific build of a job Change By: Christian Galsterer (29/Nov/14 11:00 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-10628) SCM build trigger not working correctly with variables in SVN URL
Daniel Beck commented on JENKINS-10628 SCM build trigger not working correctly with variables in SVN URL The credential problem is JENKINS-23007. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
kutzi reopened JENKINS-25676 Disconnect from XMPP after a few minutes Change By: kutzi (29/Nov/14 12:25 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
kutzi commented on JENKINS-25676 Disconnect from XMPP after a few minutes Jordan, Florian, great work in finding out the root cause! I've fixed this in a slighty different way than in the PR and uploaded a build with the fix to: https://dl.dropboxusercontent.com/u/25863594/jabber.hpi Jordan, would be great if you could test it, before I do a release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-9233) Builds hang on jabber notification when XMPP server is not responding
kutzi commented on JENKINS-9233 Builds hang on jabber notification when XMPP server is not responding Not sure, but probably yes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25505) jabber-plugin 1.28 cannot resolve host with javax.naming.NameNotFoundException: DNS name not found
kutzi resolved JENKINS-25505 as Fixed jabber-plugin 1.28 cannot resolve host with javax.naming.NameNotFoundException: DNS name not found Fixed in upcoming release 1.31 Change By: kutzi (29/Nov/14 1:03 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] [cvs-plugin] (JENKINS-25722) CVS update not working (CVS plugin 2.4,2.7) and cvsclient-71-jenkins-11 artifact
Michael Clarke commented on JENKINS-25722 CVS update not working (CVS plugin 2.4,2.7) and cvsclient-71-jenkins-11 artifact To give us a chance of diagnosing and fixing this, please explain what it is you're expecting to happen, what it is that is actually happening, and try this out using the latest version of the CVS 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] [git-plugin] (JENKINS-20427) Build Parameter variable in branch name causes polling to detect false changes in GIT
Mark Waite commented on JENKINS-20427 Build Parameter variable in branch name causes polling to detect false changes in GIT Fix included in git plugin 2.3.1, released 29 Nov 2014 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-14276) Git SCM-polling doesn't work when using a parametrized branch-name
Mark Waite closed JENKINS-14276 as Fixed Git SCM-polling doesnt work when using a parametrized branch-name Fix included in git plugin 2.3.1, released 29 Nov 2014 Change By: Mark Waite (29/Nov/14 1:15 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-23675) The git plugin is not working correctly when the repository url has job parameter and any repository credentials
Mark Waite commented on JENKINS-23675 The git plugin is not working correctly when the repository url has job parameter and any repository credentials Fix included in git plugin 2.3.1, released 29 Nov 2014 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-24133) GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL
Mark Waite closed JENKINS-24133 as Fixed GIT_BRANCH set to detached when sha1 parameter set in notifyCommit URL Fix included in git plugin 2.3.1, released 29 Nov 2014 Change By: Mark Waite (29/Nov/14 1:16 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jabber-plugin] (JENKINS-25676) Disconnect from XMPP after a few minutes
Jordan Spiker commented on JENKINS-25676 Disconnect from XMPP after a few minutes Thank you so much for the help with this one. I'll be able to test on Monday when I'm back in the office. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop 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-25822) No more connections to slaves - no log - troncated command
Oleg Nenashev
commented on JENKINS-25822
No more connections to slaves - no log - troncated command
@clement:
Could you provide versions of SSH Client, SSH Credentials and Credentials plugins?
Have you updated any of them?
// a full list of plugins and a dump of ${JENKINS_URL}/systemInfo may be useful 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] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
mohamed badran commented on JENKINS-25340 lost trend history after skipping build I'm not sure what happened but suddenly i lost seeing my trend results graph after updating to Jenkins to v1.5.91 Here is the log message i get in the system logs hudson.model.FreeStyleProject@33544533project_name did not contain project_name #720 to begin with This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
mohamed badran edited a comment on JENKINS-25340 lost trend history after skipping build I'm not sure what happened but suddenly i lost seeing my trend results graph after updating Jenkins to v1.5.91 Here is the log message i get in the system logs hudson.model.FreeStyleProject@33544533project_name did not contain project_name #720 to begin with This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext-plugin] (JENKINS-25719) bad html content after upgrading to Email Extension Plugin v2.39
Alex Earl resolved JENKINS-25719 as Fixed bad html content after upgrading to Email Extension Plugin v2.39 Will be fixed in 2.40 which should come out in a few weeks. Change By: Alex Earl (29/Nov/14 10:10 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Daniel Beck commented on JENKINS-25340 lost trend history after skipping build mohamed badran: If the graph doesn't show up at all, that's a completely unrelated issue. Ask on the jenkinsci-users mailing list for advice (maybe it's a known issue); or file a bug after reading the advice and instructions on https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue The log entry is very likely unrelated and tracked as JENKINS-25788 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-build-step-plugin] (JENKINS-25692) Incompatibility with docker-plugin?
vjuranek commented on JENKINS-25692 Incompatibility with docker-plugin? IMHO docker-java PR #102 won't help as the problem with ClientBuilder is caused by different version of jersey-client (2.11 in docker-java, 2.5.1 in jDocker). As both plugins use very similar docker library (forked from same project), we can expect similar issue in the future even if this one is fixed. Both plugins needs to use non-conflicting dependencies or Jenkins core has to implement proper class loader isolation of the plugins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-21518) Error while using SSH credentials to fetch git repository.
Mark Waite resolved JENKINS-21518 as Cannot Reproduce Error while using SSH credentials to fetch git repository. Since I can't duplicate it and the comments on the bug have been quiet for over a month, I'm closing this bug as "Cannot Reproduce". Change By: Mark Waite (29/Nov/14 11:56 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-21518) Error while using SSH credentials to fetch git repository.
Mark Waite closed JENKINS-21518 as Cannot Reproduce Error while using SSH credentials to fetch git repository. Change By: Mark Waite (29/Nov/14 11:56 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
