[JIRA] [maven-metadata-plugin] (JENKINS-22288) Disable username / password default values

2014-03-21 Thread elias.va...@gmail.com (JIRA)














































Olli Varis
 updated  JENKINS-22288


Disable username / password default values 
















Change By:


Olli Varis
(21/Mar/14 7:52 AM)




Attachment:


repo.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] [maven-metadata-plugin] (JENKINS-22288) Disable username / password default values

2014-03-21 Thread elias.va...@gmail.com (JIRA)














































Olli Varis
 updated  JENKINS-22288


Disable username / password default values 
















Change By:


Olli Varis
(21/Mar/14 7:52 AM)




Description:


Hi, whenever I go to job edit screen, username and password fields are autofilled with my current jenkins username (and password?) to repository username & pwd fields. For example our internal Nexus repository does not require authentication and after saving the job with these default values, plugin is unable to get artifact information from the repository.Just came to my mind when writing this, is
 this
 perhaps browser (Chrome in my case) feature, filling the username & pwd fields?



























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-metadata-plugin] (JENKINS-22288) Disable username / password default values

2014-03-21 Thread elias.va...@gmail.com (JIRA)














































Olli Varis
 created  JENKINS-22288


Disable username / password default values 















Issue Type:


Bug



Affects Versions:


current



Assignee:


Gesh Markov



Components:


maven-metadata-plugin



Created:


21/Mar/14 7:50 AM



Description:


Hi, whenever I go to job edit screen, username and password fields are autofilled with my current jenkins username (and password?) to repository username & pwd fields. For example our internal Nexus repository does not require authentication and after saving the job with these default values, plugin is unable to get artifact information from the repository.

Just came to my mind when writing this, is perhaps browser (Chrome in my case) feature, filling the username & pwd fields?




Project:


Jenkins



Priority:


Minor



Reporter:


Olli Varis

























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-21045) maven 2/3 projects cannot store emailaddress

2013-12-19 Thread elias.va...@gmail.com (JIRA)














































Olli Varis
 commented on  JENKINS-21045


maven 2/3 projects cannot store emailaddress















I'm sorry but how can you update Maven Integration plugin to 2.1 when it's bundled with Jenkins? We are using latest (LTS) Jenkins 1.532.1?



























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] [mailer] (JENKINS-20954) Cannot save email recipients

2013-12-17 Thread elias.va...@gmail.com (JIRA)














































Olli Varis
 commented on  JENKINS-20954


Cannot save email recipients















Sorry to report that the problem still exists, after upgrading plugin from 1.5 to 1.7. Jenkins version is 1.532.1, Job is Maven2/3 project. Works fine with 1.5 Mailer plugin.



























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







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


[JIRA] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use

2013-05-30 Thread elias.va...@gmail.com (JIRA)












































  
Olli Varis
 edited a comment on  JENKINS-18138


Value is not stored as parameter for later use
















Thanks for swift reply! Exactly where can I see this info?

EDIT: found it thanks a lot!



























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] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use

2013-05-30 Thread elias.va...@gmail.com (JIRA)














































Olli Varis
 commented on  JENKINS-18138


Value is not stored as parameter for later use















Thanks for swift reply! Exactly where can I see this info? 



























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] [maven-metadata-plugin] (JENKINS-18138) Value is not stored as parameter for later use

2013-05-29 Thread elias.va...@gmail.com (JIRA)














































Olli Varis
 created  JENKINS-18138


Value is not stored as parameter for later use















Issue Type:


Bug



Affects Versions:


current



Assignee:


Gesh Markov



Components:


maven-metadata-plugin



Created:


30/May/13 6:49 AM



Description:


I've been testing this plugin and it really doesn't work with current Jenkins release. After choosing version and trying to use that parameter later on, parameter is not recognized using ${param-name} format. I've tried to use this plugin with Artifact resolver plugin.




Environment:


Jenkins 1.515




Project:


Jenkins



Priority:


Blocker



Reporter:


Olli Varis

























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] [maven-metadata-plugin] (JENKINS-18063) Authentication support for repository

2013-05-29 Thread elias.va...@gmail.com (JIRA)














































Olli Varis
 updated  JENKINS-18063


Authentication support for repository
















Change By:


Olli Varis
(30/May/13 6:44 AM)




Priority:


Major
Minor



























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







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


[JIRA] [maven-metadata-plugin] (JENKINS-18063) Authentication support for repository

2013-05-29 Thread elias.va...@gmail.com (JIRA)














































Olli Varis
 commented on  JENKINS-18063


Authentication support for repository















Got around with this issue using URL format: http://username:password@... in "Repository Base URL".



























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] [maven-metadata-plugin] (JENKINS-18063) Authentication support for repository

2013-05-23 Thread elias.va...@gmail.com (JIRA)














































Olli Varis
 updated  JENKINS-18063


Authentication support for repository
















Change By:


Olli Varis
(23/May/13 12:43 PM)




Description:


Provide a way for maven repo authentication OR use preconfigured Jenkins maven repos.
Here's log entry: java.io.IOException: Server returned HTTP response code: 401 for URL 





Component/s:


maven-metadata-plugin





Component/s:


metadata-plugin



























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







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


[JIRA] [metadata-plugin] (JENKINS-18063) Authentication support for repository

2013-05-23 Thread elias.va...@gmail.com (JIRA)














































Olli Varis
 created  JENKINS-18063


Authentication support for repository















Issue Type:


Bug



Affects Versions:


current



Assignee:


rsandell



Components:


metadata-plugin



Created:


23/May/13 12:34 PM



Description:


Provide a way for maven repo authentication OR use preconfigured Jenkins maven repos.




Project:


Jenkins



Priority:


Major



Reporter:


Olli Varis

























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.