[JIRA] [core] (JENKINS-7291) Flyweight jobs and zero executors

2013-04-15 Thread christophe.dema...@inria.fr (JIRA)














































Christophe Demarey
 commented on  JENKINS-7291


Flyweight jobs and zero executors















Does it mean that a workspace will be created on the master?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-16626) Remote access API does not deal with a jenkins server only available through https

2013-02-04 Thread christophe.dema...@inria.fr (JIRA)














































Christophe Demarey
 created  JENKINS-16626


Remote access API does not deal with a jenkins server only available through https















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


04/Feb/13 4:40 PM



Description:


I have a Jenkins only available through https.
I set the Jenkins location URL using https://, but the api gives wrong urls, all beginning with http, whatever the flavor is (XML, json or python).

example: https://ci.inria.fr/rmod/api/json




Environment:


Jenkins 1.500




Project:


Jenkins



Priority:


Major



Reporter:


Christophe Demarey

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.




[JIRA] (JENKINS-15421) Add support for Matrix projects

2012-10-05 Thread christophe.dema...@inria.fr (JIRA)














































Christophe Demarey
 created  JENKINS-15421


Add support for Matrix projects















Issue Type:


Improvement



Affects Versions:


current



Assignee:


jieryn



Components:


job-import



Created:


05/Oct/12 2:00 PM



Description:


Job import plugin does not deal with matrix based projects.
A pull request providing this feature is available : https://github.com/jenkinsci/job-import-plugin/pull/2

Regards,
Christophe.




Fix Versions:


current



Project:


Jenkins



Labels:


plugin




Priority:


Major



Reporter:


Christophe Demarey

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira






[JIRA] (JENKINS-4608) Email notification disabled with the m2-extra-steps plugin

2012-02-13 Thread christophe.dema...@inria.fr (JIRA)

[ 
https://issues.jenkins-ci.org/browse/JENKINS-4608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158947#comment-158947
 ] 

Christophe Demarey commented on JENKINS-4608:
-

This issue is now fixed.
I tested it and it works fine.
Thanks!

 Email notification disabled with the m2-extra-steps plugin
 --

 Key: JENKINS-4608
 URL: https://issues.jenkins-ci.org/browse/JENKINS-4608
 Project: Jenkins
  Issue Type: Bug
  Components: m2-extra-steps
Affects Versions: current
 Environment: Platform: All, OS: Linux
Reporter: cdemarey2
Assignee: abayer

 Hello,
 I just discover this useful plugin (m2-extra-steps). I tried this plugin and 
 of
 course, for the first attempt, my second build step (executing a script after
 maven) failed! It's quite normal as I need to validate my script on the hudson
 executor.
 The build is labeled as a failed build = Good.
 But my job is configured to send an email if the build failed. Here no email 
 was
 sent. I cannot see the trace Sending e-mails to: ... on the build log.
 Is the email notification handle by the M2 extra steps plugin or is it a 
 bug?
 Regards,
 Christophe.

--
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