date:20150328

[JIRA] [core] (JENKINS-19) full text search

2015-03-28 Thread m...@hanabi.se (JIRA)















































Marcus Jacobsson
 commented on  JENKINS-19


full text search















There is a plugin to improves the searh function in Jenkins 
https://wiki.jenkins-ci.org/display/JENKINS/Lucene-Search

It only indexes data bound to the build unless you write your own extensions.



























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-27454) Create component for aws-lambda

2015-03-28 Thread michael.wille...@gmail.com (JIRA)















































Michael Willemse
 updated  JENKINS-27454


Create component for aws-lambda
















Change By:


Michael Willemse
(28/Mar/15 7:53 AM)




Summary:


Create component for aws-lambda
-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] [core] (JENKINS-27644) Ability to show server-driven Jenkins project notifications in the UI

2015-03-28 Thread ch...@orr.me.uk (JIRA)

Christopher Orr
commented on JENKINS-27644

Ability to show server-driven Jenkins project notifications in the UI

Great. Thanks for the feedback!

It should be possible to make messages time-limited ("display until end of 2015-03-31")
Seems unnecessary, just change the message returned from jenkins-ci.org in time.
Maybe, but it would be a nice-to-have. I know how reliable the Jenkins community is at remembering to do things on time...

Messages should be shown at the top on the Manage Jenkins page.
I disagree. Should be shown on all pages for admins.
Sure, that definitely sounds reasonable. I hadn't seen your plugin before; it makes sense.

This should probably done mostly client-side (note like an admin monitor) to make it work on networks where Jenkins is not allowed to connect to the internet.

I'm not sure I fully understand what you mean. I was thinking that Jenkins would periodically fetch the messages.json (or whatever) file, like it does with update-center.json. Jenkins would determine which notifications must be shown (if any) and would then render them to the page, for admin users. i.e. Most stuff happens server-side, though with some client-side JS to make notifications look nice / be dismissable.

If you don't ever allow Jenkins online, we can't really download timely notifications (like security advisories) from the server. Or do you mean that these messages should reach Jenkins via the browser-proxy method? Or something else?

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] [flexible-publish-plugin] (JENKINS-27171) Conditions are evaluated for each actions

2015-03-28 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 commented on  JENKINS-27171


Conditions are evaluated for each actions















If you still didn't get, then you can execute flexible-publish from flexible-publish for grouping actions without evaluations

if (HeaveCondition 1){
  flexible-publish {
   (execution always) {
publisher 1
publisher 2
   }
  }
}

As i see current change broke all already configured setups.



























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] [flexible-publish-plugin] (JENKINS-27171) Conditions are evaluated for each actions

2015-03-28 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 commented on  JENKINS-27171


Conditions are evaluated for each actions















So now, if i have setup that do 'git push release' 'push released artifacts' for Condition build=SUCCESS i will have release artifacts upload even if git push failed?!



























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] [flexible-publish-plugin] (JENKINS-27171) Conditions are evaluated for each actions

2015-03-28 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-27171


Conditions are evaluated for each actions















Kanstantsin Shautsou IIUC you can just use one condition per step.



























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] [flexible-publish-plugin] (JENKINS-27171) Conditions are evaluated for each actions

2015-03-28 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-27171


Conditions are evaluated for each actions















ikedam Consider declaring configuration incompatibility so users know their jobs may behave differently.

https://wiki.jenkins-ci.org/display/JENKINS/Marking+a+new+plugin+version+as+incompatible+with+older+versions

Examples:
https://github.com/jenkinsci/ldap-plugin/blob/master/pom.xml#L121
https://github.com/jenkinsci/build-flow-plugin/blob/master/pom.xml#L106



























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] [flexible-publish-plugin] (JENKINS-27171) Conditions are evaluated for each actions

2015-03-28 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 commented on  JENKINS-27171


Conditions are evaluated for each actions















I know that i can use, i don't appreciate breaking current setups when any behaviour can be achieved in current functionality. All was needed is a help file with description. Also such destroying change can have readResolve() for splitting current configuration. But my opinion is now -1 for such style changes.



























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-4409) Hudson test case leaks temp folders

2015-03-28 Thread ogon...@gmail.com (JIRA)















































Oliver Gondža
 commented on  JENKINS-4409


Hudson test case leaks temp folders















Backported against 1.596.3 without [FIXED JENKINS-4409] Integrated a newer version of localizer that is a) not required and b) not soaked yet.



























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] [build-pipeline-plugin] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline

2015-03-28 Thread ogon...@gmail.com (JIRA)















































Oliver Gondža
 commented on  JENKINS-20499


unable to retry job execution for failed job in build-pipeline















Removing lts-candidate label as PR 1248 is a part of 1.596 baseline.



























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-27658) Add Disable feature for Build Step

2015-03-28 Thread pskumar...@gmail.com (JIRA)















































Suresh Kumar
 created  JENKINS-27658


Add Disable feature for Build Step















Issue Type:


Improvement



Assignee:


Unassigned


Components:


core



Created:


28/Mar/15 2:26 PM



Description:


In a job if we have a multiple build steps some times there will be a need to disable one of the step and when necessary again need facility to enable the build step. 
Instead of deleting the build step if there is a disable/enable button helps to keep the step information in the job itself. 




Project:


Jenkins



Labels:


plugin




Priority:


Major



Reporter:


Suresh Kumar

























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.

55 matches

Mail list logo