[JIRA] (JENKINS-49622) Support Stride
Title: Message Title aldaris updated an issue Jenkins / JENKINS-49622 Support Stride Removing the hipchat-plugin component given that this plugin proposal has not much to do with HipChat (The APIs are quite different), and Atlassian is already in the process of creating a stride specific plugin already. Change By: aldaris Component/s: hipchat-plugin Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-41976) Add support for Add-on generated HipChat v2 tokens
Title: Message Title aldaris edited a comment on JENKINS-41976 Re: Add support for Add-on generated HipChat v2 tokens I've been trying to read more about addons, but I always end up having the feeling that it requires having HTTP endpoints exposed by some means. I've summed up my questions here:https://answers.atlassian.com/questions/ 53748694 53746531 / how-do-hipchat-addons-work In general though: anything that will require an exposed endpoint (such as the capabilities descriptor), will most likely never make it into the plugin.You may be able to create a BYO integration and save the obtained OAuth2 access token as a v2 credential to achieve your goals. 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-32083) Allow hipchat card formatting for Jenkins integration messages
Title: Message Title aldaris commented on JENKINS-32083 Re: Allow hipchat card formatting for Jenkins integration messages Yes, cards only work with v2 API. 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-41976) Add support for Add-on generated HipChat v2 tokens
Title: Message Title aldaris commented on JENKINS-41976 Re: Add support for Add-on generated HipChat v2 tokens I've been trying to read more about addons, but I always end up having the feeling that it requires having HTTP endpoints exposed by some means. I've summed up my questions here: https://answers.atlassian.com/questions/53748694/how-do-hipchat-addons-work In general though: anything that will require an exposed endpoint (such as the capabilities descriptor), will most likely never make it into the plugin. You may be able to create a BYO integration and save the obtained OAuth2 access token as a v2 credential to achieve your goals. 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-41976) Add support for Add-on generated HipChat v2 tokens
Title: Message Title aldaris commented on JENKINS-41976 Re: Add support for Add-on generated HipChat v2 tokens Sounds similar to https://github.com/jenkinsci/hipchat-plugin/issues/80 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-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title aldaris resolved as Fixed Should work properly in the upcoming 2.1.1 version. Jenkins / JENKINS-41861 New message templates show "is not supported in this context" in Pipeline builds Change By: aldaris Status: Reopened Resolved Resolution: Fixed 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
[JIRA] (JENKINS-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title aldaris reopened an issue Reopening to track the development of real support for CHANGES and COMMIT_MESSAGE tokens. Jenkins / JENKINS-41861 New message templates show "is not supported in this context" in Pipeline builds Change By: aldaris Resolution: Fixed Status: Resolved Reopened 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
[JIRA] (JENKINS-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title aldaris commented on JENKINS-41861 Re: New message templates show "is not supported in this context" in Pipeline builds Ah, so it never really worked well then. CHANGES_OR_CAUSE just falled back to CAUSE because it was never able to calculate CHANGES. 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-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title aldaris commented on JENKINS-41861 Re: New message templates show "is not supported in this context" in Pipeline builds I'm a bit puzzled as to how could the CHANGES variable work in 2.0.0, looking at the code, I just don't see how it could have worked :/ I will have a second stab at trying to get CHANGES* and COMMIT_MESSAGE* working with pipeline jobs.. 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-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title aldaris resolved as Fixed Hopefully the issues raised here are now all addressed. If HIPCHAT_CHANGES_OR_CAUSE and COMMIT_MESSAGE is still acting up: pull requests welcome. Will wait for a week or so to see if any other issues get reported, and then I'll release 2.1.1. Jenkins / JENKINS-41861 New message templates show "is not supported in this context" in Pipeline builds Change By: aldaris Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title aldaris commented on JENKINS-41861 Re: New message templates show "is not supported in this context" in Pipeline builds Changeset information access with pipeline jobs is not too straightforward (not for me at least), so that is currently not supported with pipeline jobs. I now see that the CHANGES macro has some hacky reflection code to deal with this, so you may find $CHANGES to be a more suitable option for now. BUILD_DURATION should be supported with pipeline jobs as well, it is however buggy as you've found. The 0 ms issue should be resolved soon. Since you are saying that CHANGES_OR_CAUSE and COMMIT_MESSAGE has worked with pipeline builds before, I think there may be an easy solution to fix them, but it's unlikely that I'll investigate a lot more than that. 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-41843) Sandbox RejectedAccessException when running from Global Shared Pipeline Library
Title: Message Title
aldaris resolved as Cannot Reproduce
Works fine for me after following the instructions provided in the pipeline documentation:
in my global shared library's git repo I have the following file under src/com/mycompany/Hipchat.groovy:
package com.mycompany;
class Hipchat implements Serializable {
def notifyStarted(script, room) {
script.hipchatSend (color: 'YELLOW', room: room, notify: false,
message: "STARTED: Job '${script.env.JOB_NAME} [${script.env.BUILD_NUMBER}]' (${script.env.BUILD_URL})"
)
}
}
The pipeline job has been configured with this DSL:
@Library('utils')
import com.mycompany.Hipchat
node() {
stage('hipchat') {
new Hipchat().notifyStarted(this, 'Jenkins')
}
}
Jenkins / JENKINS-41843
Sandbox RejectedAccessException when running from Global Shared Pipeline Library
Change By:
aldaris
Status:
Open Resolved
Assignee:
aldaris
Resolution:
Cannot Reproduce
[JIRA] (JENKINS-41861) New message templates show "is not supported in this context" in Pipeline builds
Title: Message Title aldaris assigned an issue to aldaris Jenkins / JENKINS-41861 New message templates show "is not supported in this context" in Pipeline builds Change By: aldaris Assignee: aldaris 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-41843) Sandbox RejectedAccessException when running from Global Shared Pipeline Library
Title: Message Title aldaris commented on JENKINS-41843 Re: Sandbox RejectedAccessException when running from Global Shared Pipeline Library Just checking: did this work with 2.0.0? 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-41843) Sandbox RejectedAccessException when running from Global Shared Pipeline Library
Title: Message Title aldaris commented on JENKINS-41843 Re: Sandbox RejectedAccessException when running from Global Shared Pipeline Library Which version of the plugin did this happen with? 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-41843) Sandbox RejectedAccessException when running from Global Shared Pipeline Library
Title: Message Title
aldaris updated an issue
Jenkins / JENKINS-41843
Sandbox RejectedAccessException when running from Global Shared Pipeline Library
Change By:
aldaris
I have the following Global Shared Pipeline Library:{code :groovy }def notifyStarted(script, room) { script.hipchatSend (color: 'YELLOW', room: room, notify: false, message: "STARTED: Job '${script.env.JOB_NAME} [${script.env.BUILD_NUMBER}]' (${script.env.BUILD_URL})" )}{code}And the following Jenkinsfile:{code :groovy }@Library('utils')import com.mycompany.Hipchatnode() { stage('hipchat') {Hipchat.notifyStarted(this, 'MyRoom') }}{code}And I get the following error:{code:java}org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: unclassified method java.lang.Class notifyStarted java.lang.String at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:113) at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:149) at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:146) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:16) at WorkflowScript.run(WorkflowScript:15) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:74) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:163) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:328) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:80) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:240) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:228) at
[JIRA] (JENKINS-34934) Integrate token macro plugin
Title: Message Title aldaris resolved as Fixed This is now implemented and should be released with 2.1.0 version. Jenkins / JENKINS-34934 Integrate token macro plugin Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Fixed 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
[JIRA] (JENKINS-40461) ${DURATION} template contains "and counting" even at job conclusion, for pipeline builds
Title: Message Title
aldaris resolved as Fixed
Thanks for the report, this should be fixed in the upcoming 2.1.0 version.
Jenkins / JENKINS-40461
${DURATION} template contains "and counting" even at job conclusion, for pipeline builds
Change By:
aldaris
Status:
Open Resolved
Assignee:
aldaris
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You
[JIRA] (JENKINS-40321) Job notification settings not respected in multibranch pipeline
Title: Message Title aldaris resolved as Not A Defect Both the global notifications and the now deprecated (and soon to be removed) HipChatJobProperty rely on the job having the HipChat post build action being present in the job configuration. Pipeline jobs do not have post build actions, hence the only viable way of sending notifications from those is to use the hipchatSend DSL as part of the pipeline definition. Jenkins / JENKINS-40321 Job notification settings not respected in multibranch pipeline Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-32083) Allow hipchat card formatting for Jenkins integration messages
Title: Message Title aldaris resolved as Fixed Cards will be supported with the 2.1.0 release. Jenkins / JENKINS-32083 Allow hipchat card formatting for Jenkins integration messages Change By: aldaris Status: Open Resolved Resolution: Fixed 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
[JIRA] (JENKINS-27303) integrate credentials plugin
Title: Message Title aldaris resolved as Fixed This is now implemented. Will be part of 1.1.0 release. Jenkins / JENKINS-27303 integrate credentials plugin Change By: aldaris Status: Open Resolved Resolution: Fixed 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-27303) integrate credentials plugin
Title: Message Title aldaris stopped work on JENKINS-27303 Change By: aldaris Status: In Progress Open 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-27303) integrate credentials plugin
Title: Message Title aldaris started work on JENKINS-27303 Change By: aldaris Status: Open In Progress 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-33214) Hipchat plugin not working with authenticating proxy
Title: Message Title aldaris resolved as Fixed This should be fixed now. Can you test the changes in your environment? I don't really have a forward proxy available to test this myself.. Jenkins / JENKINS-33214 Hipchat plugin not working with authenticating proxy Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-34918) Jenkins avatar not showing in Hipchat on web
Title: Message Title aldaris resolved as Not A Defect Not sure how could this be a fault of the plugin. Frankly I never seen an avatar for Jenkins notifications... Jenkins / JENKINS-34918 Jenkins avatar not showing in Hipchat on web Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) --
[JIRA] (JENKINS-34934) Integrate token macro plugin
Title: Message Title aldaris commented on JENKINS-34934 Re: Integrate token macro plugin Excellent idea, thanks for letting me know that there is a plugin already for this. The supported template variables are slowly getting out of hand. 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-36031) hipchat-plugin ignores "No Proxy Host"
Title: Message Title aldaris resolved as Cannot Reproduce Works fine for me by carrying out the following test: Configure proxy: localhost:1234 Test that HipChat notifications fail Configure No Proxy Host setting to include: api.hipchat.com Test that HipChat notifications now work just fine I suppose this could happen if you have the proxy settings configured additionally on the JVM level or maybe at the OS level, which could override the No Proxy Host setting at Jenkins/HipChat plugin level. Jenkins / JENKINS-36031 hipchat-plugin ignores "No Proxy Host" Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Cannot Reproduce Add Comment
[JIRA] (JENKINS-37357) Allow messaging users
Title: Message Title aldaris commented on JENKINS-37357 Re: Allow messaging users Looks to be the same RFE as https://github.com/jenkinsci/hipchat-plugin/issues/74 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-38074) No notification if build is open in browser
Title: Message Title aldaris resolved as Cannot Reproduce Works fine for me. I think it is more likely that you are not getting notifications of successful builds if they occur straight after a failed or an unstable build. For such scenarios you would need to configure the Back To Normal notification instead. Jenkins / JENKINS-38074 No notification if build is open in browser Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-29057) Proxy Support
Title: Message Title aldaris commented on JENKINS-29057 Re: Proxy Support Daniel Wagner which version of he plugin are you using? 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-26845) Security: HipChat Plugin can leak global hipchat server host name and token
Title: Message Title aldaris commented on JENKINS-26845 Re: Security: HipChat Plugin can leak global hipchat server host name and token Kurt Madel I believe you are looking for JENKINS-27303. 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-35981) Unable to get past initial admin password screen on Tomcat 8
Title: Message Title aldaris commented on JENKINS-35981 Re: Unable to get past initial admin password screen on Tomcat 8 The workaround is to change the URL before entering the initial admin password, so that the from parameter has the value of "%2Fjenkins%2F". 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-35981) Unable to get past initial admin password screen on Tomcat 8
Title: Message Title
aldaris created an issue
Jenkins / JENKINS-35981
Unable to get past initial admin password screen on Tomcat 8
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2016/Jun/15 7:49 PM
Environment:
Oracle JDK 8 with Tomcat 8.5.x
Priority:
Major
Reporter:
aldaris
When installing Jenkins 2.8 onto Tomcat 8, it is really difficult to get past the initial admin password screen. Looking further into this, it appears that this is because the from parameter defaults to /jenkins and not /jenkins/, and the FORCE_SETUP_WIZARD_FILTER in SetupWizard will fail to realize that it should display the setupWizard. Potentially the if check should be enhanced to:
if ((req.getContextPath() + "/").equals(req.getRequestURI()) || req.getContextPath().equals(req.getRequestURI()) {
[JIRA] [hipchat-plugin] (JENKINS-32083) Allow hipchat card formatting for Jenkins integration messages
Title: Message Title aldaris commented on JENKINS-32083 Re: Allow hipchat card formatting for Jenkins integration messages This sounds really nice, will try to have a look at this, but probably it won't be implemented for the next release. 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] [hipchat-plugin] (JENKINS-27202) Workflow compatibility for HipChatNotifier
Title: Message Title aldaris resolved as Fixed #60 is now merged, will be part of the 1.0.0 release. Jenkins / JENKINS-27202 Workflow compatibility for HipChatNotifier Change By: aldaris Status: Open Resolved Resolution: Fixed 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] [core] (JENKINS-31510) Filter commons-fileupload DiskFileItem using ClassFilter.DEFAULT
Title: Message Title aldaris commented on JENKINS-31510 Re: Filter commons-fileupload DiskFileItem using ClassFilter.DEFAULT Of course, this issue was created based on the assumption that the only difference between 1.3.1 and 1.3.1-jenkins-1 is the missing readObject method on DiskFileItem. 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] [hipchat-plugin] (JENKINS-26974) Allow notification background color to be passed from Jenkins
Title: Message Title aldaris resolved as Fixed The recent improvements implemented for notification config means that now the color can be configured for each notification type. Will be released with 1.0.0 version. Jenkins / JENKINS-26974 Allow notification background color to be passed from Jenkins Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Fixed 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
[JIRA] [hipchat-plugin] (JENKINS-28314) Support non-notify messages
Title: Message Title aldaris commented on JENKINS-28314 Re: Support non-notify messages This is now possible with #16 fixed. Will be part of 1.0.0 version of the plugin. 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] [hipchat-plugin] (JENKINS-28314) Support non-notify messages
Title: Message Title aldaris resolved as Fixed Jenkins / JENKINS-28314 Support non-notify messages Change By: aldaris Status: Open Resolved Resolution: Fixed 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] [hipchat-plugin] (JENKINS-31250) Allow environment variables to be used in "Project Room"-field
Title: Message Title aldaris resolved as Duplicate Jenkins / JENKINS-31250 Allow environment variables to be used in "Project Room"-field Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Duplicate 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] [hipchat-plugin] (JENKINS-18127) Add an option to enable room notification
Title: Message Title aldaris resolved as Fixed Resolved with #16. Will be part of 1.0.0 Jenkins / JENKINS-18127 Add an option to enable room notification Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: Fixed 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] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title aldaris edited a comment on JENKINS-27520 Re: Notifications not sent starting 0.1.9 with HipChat API v2 v2integrationworksfineforme(cloudversionofHipChat).Theerrormessagesforv1andSendAsvalueshavebeenimprovedwith[# 47 46 |https://github.com/jenkinsci/hipchat-plugin/issues/ 47 46 ]. 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] [hipchat-plugin] (JENKINS-27202) Workflow compatibility for HipChatNotifier
Title: Message Title aldaris commented on JENKINS-27202 Re: Workflow compatibility for HipChatNotifier Looks like the HipChat plugin gets used by both workflow and build-flow plugin users (yay), at the moment build flow is winning on the installations front, so I will focus on better build-flow integration first. 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] [hipchat-plugin] (JENKINS-28314) Support non-notify messages
Title: Message Title aldaris commented on JENKINS-28314 Re: Support non-notify messages Conflicting request with #16. I think the solution will be to have a single checkbox that says notify or not notify and that will determine the notification mode for ALL notification types. 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] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title aldaris resolved as Cannot Reproduce v2 integration works fine for me (cloud version of HipChat). The error messages for v1 and Send As values have been improved with #47. Jenkins / JENKINS-27520 Notifications not sent starting 0.1.9 with HipChat API v2 Change By: aldaris Status: Open Resolved Resolution: CannotReproduce 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] [hipchat-plugin] (JENKINS-27303) integrate credentials plugin
Title: Message Title aldaris commented on JENKINS-27303 Re: integrate credentials plugin Whilst it would be nice to utilize the credentials plugin, probably it won't happen for 0.2.0. Upgrade will be a pain, and I'll need to learn a lot about how the credentials storage actually works. Pull requests are welcome for now. 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] [hipchat-plugin] (JENKINS-29057) Proxy Support
Title: Message Title aldaris resolved as Fixed This should be now resolved with 1d70878. Will be part of the 0.2.0 release. Jenkins / JENKINS-29057 Proxy Support Change By: aldaris Status: Open Resolved Resolution: Fixed 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] [hipchat-plugin] (JENKINS-26926) HipChat Notification does not work as promote action
Title: Message Title aldaris resolved as Cannot Reproduce I can't reproduce this issue with 0.2.0-SNAPSHOT, the promotion triggers the success message for me, and I do receive the notification. Jenkins / JENKINS-26926 HipChat Notification does not work as promote action Change By: aldaris Status: Open Resolved Assignee: aldaris Resolution: CannotReproduce 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
[JIRA] [hipchat-plugin] (JENKINS-27712) Provide Web Display Name variables for use in notification templates
Title: Message Title aldaris resolved as Fixed This is now done: https://github.com/jenkinsci/hipchat-plugin/commit/b797b20312c46ce19b2c4bd7a15ce280ce050571 Will be part of 0.2.0 release. Jenkins / JENKINS-27712 Provide Web Display Name variables for use in notification templates Change By: aldaris Status: Open Resolved Resolution: Fixed 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] [hipchat-plugin] (JENKINS-22723) Cannot pass hipchat room number as a parameter to a job
Title: Message Title aldaris assigned an issue to aldaris Jenkins / JENKINS-22723 Cannot pass hipchat room number as a parameter to a job Change By: aldaris Assignee: aldaris 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] [hipchat-plugin] (JENKINS-22723) Cannot pass hipchat room number as a parameter to a job
Title: Message Title aldaris resolved as Fixed This is now implemented with https://github.com/jenkinsci/hipchat-plugin/commit/cfc8282b3f52909c1f17ebe5b0e69f2ddce7340d . Will be part of the 0.2.0 release. Jenkins / JENKINS-22723 Cannot pass hipchat room number as a parameter to a job Change By: aldaris Status: Open Resolved Resolution: Fixed 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] [hipchat-plugin] (JENKINS-29057) Proxy Support
Title: Message Title aldaris assigned an issue to aldaris Jenkins / JENKINS-29057 Proxy Support Change By: aldaris Assignee: aldaris 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] [hipchat-plugin] (JENKINS-28314) Support non-notify messages
Title: Message Title aldaris assigned an issue to aldaris Jenkins / JENKINS-28314 Support non-notify messages Change By: aldaris Assignee: aldaris 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] [hipchat-plugin] (JENKINS-26974) Allow notification background color to be passed from Jenkins
Title: Message Title aldaris commented on JENKINS-26974 Re: Allow notification background color to be passed from Jenkins https://www.hipchat.com/docs/apiv2/method/send_room_notification The color selection isn't that wide, so maybe start events should be purple? 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] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title aldaris commented on JENKINS-27520 Re: Notifications not sent starting 0.1.9 with HipChat API v2 Haven't really heard of the group API to be frank, but the simplest test would be to check if your OAuth2 access token has the send_notification scope: https://www.hipchat.com/docs/apiv2/method/get_session To generate OAuth2 tokens for my notifications I just normally go to the room I've created and create a new token under the Tokens menu. 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] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title aldaris commented on JENKINS-27520 Re: Notifications not sent starting 0.1.9 with HipChat API v2 That is a good point. The v1 API requires a valid value for the Send As configuration field (should be less than 15 chars long), the v2 API does not use the Send As value, it will publish messages using the name of the OAuth2 access tokens. To test your OAuth2 access token, you could follow https://www.hipchat.com/docs/apiv2/auth#auth_test . You should make sure that the acquired OAuth2 access token has the send_notification scope. 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] [hipchat-plugin] (JENKINS-27712) Provide Web Display Name variables for use in notification templates
Title: Message Title aldaris commented on JENKINS-27712 Re: Provide Web Display Name variables for use in notification templates Your request makes perfect sense, the full job name has been implemented due to https://github.com/jenkinsci/hipchat-plugin/issues/12 . I assume this is not an issue in your environment. Will try to target this for the 0.2.0 release. 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] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title aldaris commented on JENKINS-27520 Re: Notifications not sent starting 0.1.9 with HipChat API v2 I'm not really sure what is going wrong in your setup, I'm pretty sure it works well for me. I'm wondering if you are using a self-hosted HipChat server or are you using the cloud version instead? In any case, when performing an upgrade, the configuration should not need any change, it should remain to work just fine (using the v1 API). Most of the documentation is embedded into the plugin as help texts, so that should help you get going, but here are the main details just in case: v2 mode is a global option, either you enable v2 support in your Jenkins and use v2 OAuth2 tokens everywhere, or you use v1 style API tokens. Each job has a new field for the Auth Token now to allow you to define tokens per build jobs, however if no value is specified for the job, it should fall back to the globally configured Auth Token. v1 API tokens can be obtained by following the v1 docs, v2 OAuth2 tokens can be obtained by following the v2 docs. To help investigate the root cause of this problem please provide some logs from Jenkins for failed notification attempts. 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] [hipchat-plugin] (JENKINS-27520) Notifications not sent starting 0.1.9 with HipChat API v2
Title: Message Title aldaris assigned an issue to aldaris Jenkins / JENKINS-27520 Notifications not sent starting 0.1.9 with HipChat API v2 Change By: aldaris Assignee: aldaris 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] [hipchat-plugin] (JENKINS-27202) Workflow compatibility for HipChatNotifier
aldaris commented on JENKINS-27202 Workflow compatibility for HipChatNotifier After having a quick look I guess this is about having some sort of an integration with the workflow-plugin. A plugin, which on its own Wiki page points to a different plugin as an alternative? I'm just not entirely sure it is worthwhile to introduce a dependency on workflow-plugin to implement this requirement. Could you point me to other plugins that integrate with these Steps by any chance? 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] [hipchat-plugin] (JENKINS-27304) wrong help test for Use v2 API
aldaris resolved JENKINS-27304 as Fixed wrong help test for Use v2 API Change By: aldaris (14/Mar/15 12:14 AM) Status: Open Resolved Resolution: Fixed 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] [hipchat-plugin] (JENKINS-23240) hipchat link in hipchat client is broken.
aldaris resolved JENKINS-23240 as Fixed hipchat link in hipchat client is broken. With 0.1.9-SNAPSHOT now the build server URL setting is gone, instead we are using Jenkins' instance URL from the global settings. Change By: aldaris (09/Mar/15 5:11 PM) Status: Open Resolved Assignee: aldaris Resolution: Fixed 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] [hipchat-plugin] (JENKINS-25714) No HipChat notification when build status change from Unstable to Back To Normal
aldaris resolved JENKINS-25714 as Fixed No HipChat notification when build status change from Unstable to Back To Normal This was because only FAILURE - SUCCESS was considered Back To Normal, with 0.1.9-SNAPSHOT UNSTABLE - SUCCESS will trigger Back To Normal notifications as well. Change By: aldaris (09/Mar/15 5:18 PM) Status: Open Resolved Assignee: aldaris Resolution: Fixed 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] [hipchat-plugin] (JENKINS-19184) hipchat does not update job configs when the settings change
aldaris resolved JENKINS-19184 as Fixed hipchat does not update job configs when the settings change This has been fixed in 0.1.9-SNAPSHOT already. Change By: aldaris (09/Mar/15 5:06 PM) Status: Open Resolved Assignee: aldaris Resolution: Fixed 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] [hipchat-plugin] (JENKINS-20423) Hipchat Notifications do not function behind a proxy.
aldaris resolved JENKINS-20423 as Fixed Hipchat Notifications do not function behind a proxy. Proxy support was added in 0.1.8 release. Change By: aldaris (09/Mar/15 5:08 PM) Status: Open Resolved Assignee: aldaris Resolution: Fixed 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] [hipchat-plugin] (JENKINS-26974) Allow notification background color to be passed from Jenkins
aldaris commented on JENKINS-26974 Allow notification background color to be passed from Jenkins I'm not entirely sure about this request, and generally I'm against overcomplicating the configuration. Currently the coloring looks something like this: STARTED - green ABORTED - gray SUCCESS - green FAILURE - red NOT_BUILT - gray UNSTABLE - yellow I'd say if this issue gets 10 votes, I'll have a look. 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] [hipchat-plugin] (JENKINS-25802) Notification for failure to success transition
aldaris resolved JENKINS-25802 as Cannot Reproduce Notification for failure to success transition Failure-Success transitions result in Back To Normal notifications in my environment. Change By: aldaris (09/Mar/15 5:24 PM) Status: Open Resolved Assignee: aldaris Resolution: CannotReproduce 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] [hipchat-plugin] (JENKINS-25908) Move proerties to PostBuildAction
aldaris resolved JENKINS-25908 as Fixed Move proerties to PostBuildAction This has now happened in 0.1.9-SNAPSHOT. Change By: aldaris (09/Mar/15 5:26 PM) Status: Open Resolved Assignee: aldaris Resolution: Fixed 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] [hipchat-plugin] (JENKINS-24852) Jenkins-HipChat plugin does not send message to internal hosted HipChat server
aldaris resolved JENKINS-24852 as Fixed Jenkins-HipChat plugin does not send message to internal hosted HipChat server I don't believe this is a problem any more. Change By: aldaris (09/Mar/15 5:13 PM) Status: Open Resolved Assignee: aldaris Resolution: Fixed 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] [hipchat-plugin] (JENKINS-26845) Security: HipChat Plugin can leak global hipchat server host name and token
aldaris resolved JENKINS-26845 as Fixed Security: HipChat Plugin can leak global hipchat server host name and token This is now resolved in 0.1.9-SNAPSHOT. With the addition of the v2 API support, now it is possible to define auth tokens on the job level or just simply inherit them from the global settings (without duplicating the setting in the project configuration). Change By: aldaris (09/Mar/15 5:27 PM) Status: Open Resolved Assignee: aldaris Resolution: Fixed 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.
