date:20140927

[JIRA] [copyartifact] (JENKINS-24887) Workflow support of Copyartifact

2014-09-27 Thread de...@ikedam.jp (JIRA)















































ikedam
 created  JENKINS-24887


Workflow support of Copyartifact















Issue Type:


Improvement



Assignee:


Unassigned


Components:


copyartifact



Created:


27/Sep/14 6:01 AM



Description:


With supporting SimpleBuildStep introduced in Jenkins 1.577...

(copied from https://github.com/jenkinsci/copyartifact-plugin/pull/43)
Atm, it works using the base 'step' step (i.e. you need to specify the $class) e.g.

node('master') {
  // Do stuff
  step($class: 'hudson.plugins.copyartifact.CopyArtifact', projectName: 'project1', filter: 'hellothere.txt')
  // More stuff
}


Once the workflow apis are published  we can build a dedicated step for this, it would look something like the following:


node('master') {
  // Do stuff
  copy(projectName: 'project1', filter: 'hellothere.txt')
  // More stuff
}





Project:


Jenkins



Priority:


Major



Reporter:


ikedam

























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] [copyartifact] (JENKINS-24888) Complete runtime permission check of Copyartifact

2014-09-27 Thread de...@ikedam.jp (JIRA)















































ikedam
 created  JENKINS-24888


Complete runtime permission check of Copyartifact















Issue Type:


Improvement



Assignee:


Unassigned


Components:


copyartifact



Created:


27/Sep/14 6:07 AM



Description:


Copyartifact performs permission checks only when projects to copy from are specified with variables: See https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin#CopyArtifactPlugin-Permissionstocopyartifact

This is misleading, users are often confused and that results in many JIRA issues.

As the latest Jenkins provides a more flexible authorization model (QueueItemAuthenticator), it's time for copyartifact to check permissions even for projects specified without variables.




Project:


Jenkins



Priority:


Major



Reporter:


ikedam

























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] [copyartifact] (JENKINS-24889) Copyartifact should output more verbose messages

2014-09-27 Thread de...@ikedam.jp (JIRA)















































ikedam
 created  JENKINS-24889


Copyartifact should output more verbose messages















Issue Type:


Improvement



Assignee:


Unassigned


Components:


copyartifact



Created:


27/Sep/14 6:09 AM



Description:


Add an option to have outputs like "build XXX is skipped for unstable".

There are often JIRA issues "the build wasn't properly selected", but there's no way to diagnose that.




Project:


Jenkins



Priority:


Major



Reporter:


ikedam

























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] [copyartifact] (JENKINS-24890) BuildFilter-based configuration for Copyartifact

2014-09-27 Thread de...@ikedam.jp (JIRA)















































ikedam
 created  JENKINS-24890


BuildFilter-based configuration for Copyartifact















Issue Type:


New Feature



Assignee:


Unassigned


Components:


copyartifact



Created:


27/Sep/14 6:11 AM



Description:


Copyartifact provides BuildSelector and BuildFilter as mechanisms to select a build to copy from.
But it mainly uses only BuildSelector.

BuildFilter-based configuration would allow more flexible build specifications such as: the last completed build that is unstable or more AND a downstream of build XXX AND its parameter FOO is BAR or BAZ.




Project:


Jenkins



Priority:


Major



Reporter:


ikedam

























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] [copyartifact] (JENKINS-24891) Remove FilePathCopyMethod from copyartifact

2014-09-27 Thread de...@ikedam.jp (JIRA)















































ikedam
 created  JENKINS-24891


Remove FilePathCopyMethod from copyartifact















Issue Type:


New Feature



Assignee:


Unassigned


Components:


copyartifact



Created:


27/Sep/14 6:13 AM



Description:


Copyartifact provides an extension point Copier which is to implement file copying operations.

But it doesn't provide an interface to switch them,
and it's only confusing to developers.

Especially, FilePathCopyMethod, an old implementation for Copier is no longer used, and not tested at all.
We should remove that. 




Project:


Jenkins



Priority:


Minor



Reporter:


ikedam

























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] [copyartifact] (JENKINS-24892) Copyartifact 2.0

2014-09-27 Thread de...@ikedam.jp (JIRA)















































ikedam
 created  JENKINS-24892


Copyartifact 2.0















Issue Type:


New Feature



Assignee:


ikedam



Components:


copyartifact



Created:


27/Sep/14 6:14 AM



Description:


I plan to start to develop Copyartifact 2.0 with major changes which may no longer preserve compatibility from 1.X.




Project:


Jenkins



Priority:


Major



Reporter:


ikedam

























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-24879) Git Plugin env variable resolution not working in Git Publisher

2014-09-27 Thread tobias.scha...@gmx.de (JIRA)















































tobias schaber
 commented on  JENKINS-24879


Git Plugin env variable resolution not working in Git Publisher















Hi Mark,

First: Sorry for not finding the duplicate entry. Thank you for your Response, it works. Great. You helped me over!

Kind regards,
Tobias



























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-24879) Git Plugin env variable resolution not working in Git Publisher

2014-09-27 Thread tobias.scha...@gmx.de (JIRA)
















































tobias schaber
 resolved  JENKINS-24879 as Duplicate


Git Plugin env variable resolution not working in Git Publisher
















Change By:


tobias schaber
(27/Sep/14 8:25 AM)




Status:


Open
Resolved





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] [mailer] (JENKINS-24885) SMTP authentication not working from jenkins version 1.576

2014-09-27 Thread dan...@beckweb.net (JIRA)
















































Daniel Beck
 resolved  JENKINS-24885 as Duplicate


SMTP authentication not working from jenkins version 1.576
















Duplicates JENKINS-24214, which should be fixed in Mailer Plugin 1.11.





Change By:


Daniel Beck
(27/Sep/14 9:32 AM)




Status:


Open
Resolved





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] [core] (JENKINS-24842) Add progress to artifact archiver

2014-09-27 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-24842


Add progress to artifact archiver















That is not going to be feasible any time soon, as the default artifact archiver reuses FilePath.copyRecursiveTo, and that doesn't support writing informational messages.



























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-4428) Security leak - password parameters are visible

2014-09-27 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 updated  JENKINS-4428


Security leak - password parameters are visible
















This issue is about the MavenProbeAction in Maven Project Plugin, so assigning that as component.





Change By:


Daniel Beck
(27/Sep/14 9:38 AM)




Component/s:


maven





Component/s:


security





Component/s:


core





Component/s:


mask-passwords



























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] [crowd2] (JENKINS-24884) Unable to use SSO with Jenkins + Crowd

2014-09-27 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 commented on  JENKINS-24884


Unable to use SSO with Jenkins + Crowd















Hi, could you check closed issues? There was some issues before but they are all were closed by requestor after setting right proxy and other settings.
Plus add in jenkins configuration logger for crowd and jenkins/hudson.security, acegi classes to collect debug info. And open in chrome debug console and check in network connection requested/accepted "cookies" tab.



























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-22708) JobDSL Plugin can produce never ending jobs (resource leak)

2014-09-27 Thread m...@daniel-spilker.com (JIRA)

Daniel Spilker
commented on JENKINS-22708

JobDSL Plugin can produce never ending jobs (resource leak)

The problem is that properties collects all properties of the job object, so all getter methods get called. Unfortunately, also getXml() is called which generates the config XML for the job. And there starts the recursion because to generated the XML, all configure block will be evaluated. And the configure block will try to generated the XML which calls the configure block and so on.

As a workaround I tried to make the "Process Job DSLs" step abortable by checking the thread's interrupted flag and throwing a InterruptedException. But that didn't work because the exception is caught somewhere and never aborts the build step.

Another solution would be to rename getXml() and getNode() to createXml() and createNode(). That would change the API, but will break the recursion since properties no longer causes the XML to be generated.

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.

1 2 >

1 - 100 of 153 matches

Mail list logo