[JIRA] (JENKINS-36875) Empty screen when creating new jobs
Title: Message Title Frédéric DROUET commented on JENKINS-36875 Re: Empty screen when creating new jobs Everything is working with the SNAPSHOT version. Thanks guys! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-34648) Cannot create new items after upgrade to 2.1
Title: Message Title Frédéric DROUET edited a comment on JENKINS-34648 Re: Cannot create new items after upgrade to 2.1 Mine was just upgraded from an 1. x 642.4 version Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-34648) Cannot create new items after upgrade to 2.1
Title: Message Title Frédéric DROUET commented on JENKINS-34648 Re: Cannot create new items after upgrade to 2.1 Mine was just upgraded from an 1.x version Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ssh-slaves-plugin] (JENKINS-26379) Jenkins - ssh connection exception
Title: Message Title Frdric DROUET commented on JENKINS-26379 Re: Jenkins - ssh connection exception The man on my Ubuntu 14.04 server says : MACsSpecifies the available MAC (message authentication code) algorithms. The MAC algorithm is used in protocol version 2 for data integrity protection. Multiple algorithms must be comma-separated. The algorithms that contain “-etm” calculate the MAC after encryption (encrypt-then-mac). These are considered safer and their use recommended. The default is: hmac-md5-...@openssh.com,hmac-sha1-...@openssh.com, umac-64-...@openssh.com,umac-128-...@openssh.com, hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com, hmac-ripemd160-...@openssh.com,hmac-sha1-96-...@openssh.com, hmac-md5-96-...@openssh.com, hmac-md5,hmac-sha1,umac...@openssh.com,umac-...@openssh.com, hmac-sha2-256,hmac-sha2-512,hmac-ripemd160, hmac-sha1-96,hmac-md5-96 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ssh-slaves-plugin] (JENKINS-26379) Jenkins - ssh connection exception
Title: Message Title Frdric DROUET commented on JENKINS-26379 Re: Jenkins - ssh connection exception I have found a workaround which allow my jenkins server (akka master) (Ubuntu 12.04 + jdk-oracle-7u67-x64) to start a Jenkins slave agent on the new server (Ubuntu 14.04) by commenting the MACs ... configuration line on the new server /etc/ssh/sshd_config file. After reloading SSH server, no more problem for jenkins master to establish a ssh connexion. For information, the MACs parameter of my new server was : MACs hmac-sha2-512-...@openssh.com,hmac-sha2-256-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-512,hmac-sha2-256,hmac-ripemd160 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ssh-slaves-plugin] (JENKINS-26379) Jenkins - ssh connection exception
Title: Message Title Frdric DROUET commented on JENKINS-26379 Re: Jenkins - ssh connection exception Mohit Sharma : any news about your problem ? did you succeed to solve it ? I have the same problem and even after double checked everything I can't fix my problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-13078) Multijob Plugin looses a hierarchical view at the multijob project page when it has upstream project(s)
[ https://issues.jenkins-ci.org/browse/JENKINS-13078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163742#comment-163742 ] Frédéric DROUET commented on JENKINS-13078: --- the component jenkins-multijob-plugin now exists in jira Multijob Plugin looses a hierarchical view at the multijob project page when it has upstream project(s) --- Key: JENKINS-13078 URL: https://issues.jenkins-ci.org/browse/JENKINS-13078 Project: Jenkins Issue Type: Bug Components: core Reporter: Tetiana Tvardovska When multijob project is linked to another upstream project, [Multijob Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin] stops showing an hierarchical view of used jobs. But, when the up link is removed, the hierarchical view of used jobs appears again. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14074) [jenkins-multijob-plugin] keep the default value for parameter of type Choice
Frédéric DROUET created JENKINS-14074: - Summary: [jenkins-multijob-plugin] keep the default value for parameter of type Choice Key: JENKINS-14074 URL: https://issues.jenkins-ci.org/browse/JENKINS-14074 Project: Jenkins Issue Type: Bug Components: jenkins-multijob-plugin Affects Versions: current Reporter: Frédéric DROUET Priority: Critical I have a main job (jobA) of type Multijob which launch an other job (jobB) which has parameters. jobB has 1 of its parameters which is a Choice parameter *with a default value*. If I don't specify the value of this parameter in jobA to use the default value, it doesn't work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14074) [jenkins-multijob-plugin] doesn't keep the default value for parameter of type Choice
[ https://issues.jenkins-ci.org/browse/JENKINS-14074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frédéric DROUET updated JENKINS-14074: -- Summary: [jenkins-multijob-plugin] doesn't keep the default value for parameter of type Choice (was: [jenkins-multijob-plugin] keep the default value for parameter of type Choice) [jenkins-multijob-plugin] doesn't keep the default value for parameter of type Choice - Key: JENKINS-14074 URL: https://issues.jenkins-ci.org/browse/JENKINS-14074 Project: Jenkins Issue Type: Bug Components: jenkins-multijob-plugin Affects Versions: current Reporter: Frédéric DROUET Priority: Critical I have a main job (jobA) of type Multijob which launch an other job (jobB) which has parameters. jobB has 1 of its parameters which is a Choice parameter *with a default value*. If I don't specify the value of this parameter in jobA to use the default value, it doesn't work. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
