Jenkins Jira plugin - looking for pipeline example

[Vitaly Karasik]

I'm able to use JiraIssueFieldUpdater ("Issue custom field updater") from 
the Jira plugin in the legacy (freestyle) job. But I couldn't find any 
example of using this function into Jenkins pipeline, I'll be glad to see 
some code snippets.
Vitaly

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a20e32c4-6279-43f2-b030-af09c50db266%40googlegroups.com.

Re: NPE in JIRA Plugin after update to 3.0.7

[Baptiste Mathus]

If you confirmed the issue, and would like to raise chances to see it fixe,
please file a JIRA in the tracker with clear reproduction steps (ideally,
providing the fix PR with it).

Thanks!

Le mer. 15 mai 2019 à 22:17, Junio Souz  a
écrit :

> I've observed that in 3.0.7 release notes there's this improvement
> JENKINS-19195 . I
> can't say for sure, but after update to this version all my builds that
> closes releases stopped work with NPE, no more stacktrace.
>
> After it's downgrade, the problem had been solved.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/6d7067cc-a2cb-4564-bdea-0c38d659dab4%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS6w2bxM%2BY%2Bgw%3DREnC4TPHd%3DfE5_ykhd79Hhgbw2d2mY3w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

JIRA Plugin 3.0.7 NPE

[Junio Souz]

After update the plugin to this version release a version start to break 
with NPE, no more stacktrace.

Then I downgraded the plugin and it back to work.

I suspect JENKINS-19195 caused this.

Can anyone confirm that and otherwise fix it? Tks.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/90d9e3c8-f34e-4f5e-9f68-2ccad4fd1ea8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

NPE in JIRA Plugin after update to 3.0.7

[Junio Souz]

I've observed that in 3.0.7 release notes there's this improvement 
JENKINS-19195 . I can't 
say for sure, but after update to this version all my builds that closes 
releases stopped work with NPE, no more stacktrace. 

After it's downgrade, the problem had been solved.


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6d7067cc-a2cb-4564-bdea-0c38d659dab4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Windows personal certificate and Jira plugin

[Victor Martinez]

I'd suggest to add a logger to gather as much details as possible using the 
UI:
- https://wiki.jenkins.io/display/JENKINS/Logging

IIRC, long time ago I had some issues with the Jira plugin something 
related with the restapi and login, but the only way I was able to debug 
what caused the issue was by adding loggers, even for the apache http 
library. I don't remember exactly how I fixed :(

Cheers

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/e0dc950b-b4e9-42a9-afab-bae1aeea2b4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Windows personal certificate and Jira plugin

[t3knoid]

Bumping this up. Anyone have any ideas? 

On Saturday, March 16, 2019 at 10:58:25 AM UTC-4, t3knoid wrote:
>
> I am trying to use the Jira plugin with a a Jira server that uses a 
> personal certificate before you can even access the site. Once browser is 
> authenticated, the user can login using their username/password as usual. I 
> am running Jenkins in a Windows box. I've installed the personal 
> certificate in the Jenkins server in the local machine store. I also tried 
> installing it as a the user account that the Jenkins service is running as. 
> Here's part of the exception stack.
>
> org.apache.http.ParseException:
>   at 
> org.apache.http.message.BasicLineParser.parseProtocolVersion(BasicLineParser.java:148)
>   at 
> org.apache.http.message.BasicLineParser.parseStatusLine(BasicLineParser.java:366)
>   at 
> org.apache.http.impl.nio.codecs.DefaultHttpResponseParser.createMessage(DefaultHttpResponseParser.java:112)
>   at 
> org.apache.http.impl.nio.codecs.DefaultHttpResponseParser.createMessage(DefaultHttpResponseParser.java:50)
>   at 
> org.apache.http.impl.nio.codecs.AbstractMessageParser.parseHeadLine(AbstractMessageParser.java:156)
>   at 
> org.apache.http.impl.nio.codecs.AbstractMessageParser.parse(AbstractMessageParser.java:207)
> Caused: org.apache.http.ProtocolException: 
>
>   at 
> org.apache.http.impl.nio.codecs.AbstractMessageParser.parse(AbstractMessageParser.java:209)
>   at 
> org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:245)
>   at 
> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81)
>   at 
> org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39)
>   at 
> org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:121)
>   at 
> org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162)
>   at 
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337)
>   at 
> org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315)
>   at 
> org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276)
>   at 
> org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/250691af-36da-4176-9f08-29d610ce4524%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Windows personal certificate and Jira plugin

[t3knoid]

I am trying to use the Jira plugin with a a Jira server that uses a 
personal certificate before you can even access the site. Once browser is 
authenticated, the user can login using their username/password as usual. I 
am running Jenkins in a Windows box. I've installed the personal 
certificate in the Jenkins server in the local machine store. I also tried 
installing it as a the user account that the Jenkins service is running as. 
Here's part of the exception stack.

org.apache.http.ParseException:
at 
org.apache.http.message.BasicLineParser.parseProtocolVersion(BasicLineParser.java:148)
at 
org.apache.http.message.BasicLineParser.parseStatusLine(BasicLineParser.java:366)
at 
org.apache.http.impl.nio.codecs.DefaultHttpResponseParser.createMessage(DefaultHttpResponseParser.java:112)
at 
org.apache.http.impl.nio.codecs.DefaultHttpResponseParser.createMessage(DefaultHttpResponseParser.java:50)
at 
org.apache.http.impl.nio.codecs.AbstractMessageParser.parseHeadLine(AbstractMessageParser.java:156)
at 
org.apache.http.impl.nio.codecs.AbstractMessageParser.parse(AbstractMessageParser.java:207)
Caused: org.apache.http.ProtocolException: 

at 
org.apache.http.impl.nio.codecs.AbstractMessageParser.parse(AbstractMessageParser.java:209)
at 
org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:245)
at 
org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81)
at 
org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39)
at 
org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:121)
at 
org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162)
at 
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337)
at 
org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315)
at 
org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276)
at 
org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/93584361-afc8-4a5e-b273-68f34226d696%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: threadExecutorNumber must be at least 1 error with JIRA plugin v3.04 and Jenkins v2.138.2

['David Brown' via Jenkins Users]

Apologies, plugin version should read JIRA plugin v3.0.4

On Friday, 2 November 2018 16:30:49 UTC, David Brown wrote:
>
> Hello. I'm facing an issue with the JIRA plugin. Associated cases are 
> correctly getting updated but the JIRA Issue links in build Changelog are 
> not rendering correctly as hyplerlinks. As a first step in trying to debug 
> this I have tried "Validate Settings" in the JIRA section of Manage Jenkins 
> > Configure System but this fails with an error message 
> "threadExecutorNumber must be at least 1". It seems there is a new 
> parameter "Thread Executor Size" (defaults to 10, I have tried a few other 
> values but these make no difference to my error message) but I can see no 
> option to specify the Thread Executor Number. Can anyone help please? 
> Regards, David 
>
>
>  
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/69f7916d-66b6-42b8-9d54-ea91b7abff38%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

threadExecutorNumber must be at least 1 error with JIRA plugin v3.04 and Jenkins v2.138.2

['David Brown' via Jenkins Users]

Hello. I'm facing an issue with the JIRA plugin. Associated cases are 
correctly getting updated but the JIRA Issue links in build Changelog are 
not rendering correctly as hyplerlinks. As a first step in trying to debug 
this I have tried "Validate Settings" in the JIRA section of Manage Jenkins 
> Configure System but this fails with an error message 
"threadExecutorNumber must be at least 1". It seems there is a new 
parameter "Thread Executor Size" (defaults to 10, I have tried a few other 
values but these make no difference to my error message) but I can see no 
option to specify the Thread Executor Number. Can anyone help please? 
Regards, David 
   

 

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/26d39012-0fde-4420-bcca-fce48fcae730%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jira plugin 2.5.1 fails to validate settings

[t3knoid]

I am posting this just in case someone else runs into the issue. The latest 
Jira Plugin fails to validate it's settings. Version 2.5.0 works fine 

The following exception stack trace is thrown when trying to validate Jira 
settings:

java.lang.IllegalAccessError: 
org/apache/http/impl/client/cache/BasicHttpCache
at 
org.apache.http.impl.client.cache.CachingHttpAsyncClient.(CachingHttpAsyncClient.java:173)
at 
com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.(ApacheAsyncHttpClient.java:239)
at 
com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.(ApacheAsyncHttpClient.java:123)
at 
com.atlassian.httpclient.apache.httpcomponents.DefaultHttpClientFactory.doCreate(DefaultHttpClientFactory.java:68)
at 
com.atlassian.httpclient.apache.httpcomponents.DefaultHttpClientFactory.create(DefaultHttpClientFactory.java:35)
at 
com.atlassian.jira.rest.client.internal.async.AsynchronousHttpClientFactory.createClient(AsynchronousHttpClientFactory.java:63)
at 
com.atlassian.jira.rest.client.internal.async.AsynchronousJiraRestClientFactory.create(AsynchronousJiraRestClientFactory.java:35)
at 
com.atlassian.jira.rest.client.internal.async.AsynchronousJiraRestClientFactory.createWithBasicHttpAuthentication(AsynchronousJiraRestClientFactory.java:42)
at hudson.plugins.jira.JiraSite.createSession(JiraSite.java:303)
at hudson.plugins.jira.JiraSite$DescriptorImpl.doValidate(JiraSite.java:805)
at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)
Caused: javax.servlet.ServletException
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:765)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)
at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:248)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154)
at 
org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
at 
com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:232)
at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:209)
at 
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:88)
at 
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:113)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
at javax.servlet.FilterChain$doFilter.call(Unknown Source)
at 
com.ceilfors.jenkins.plugins.jiratrigger.ExceptionLoggingFilter.doFilter(ExceptionLoggingFilter.groovy:29)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
at 
org.tuckey.web.filters.urlrewrite.RuleChain.handleRewrite(RuleChain.java:176)
at org.tuckey.web.filters.urlrewrite.RuleChain.doRules(RuleChain.java:145)
at 
org.tuckey.web.filters.urlrewrite.UrlRewriter.processRequest(UrlRewriter.java:92)
at 
com.marvelution.jenkins.plugins.jira.filter.UrlRewriteFilter.doFilter(UrlRewriteFilter.java:51)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
at 
com.marvelution.jenkins.plugins.jira.filter.OAuthFilter.doFilter(OAuthFilter.java:88)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:99)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at 
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:8

Jira Plugin - Adding only a comment

[Josh W]

Hello,

I'm trying to add a comment using the Jenkins Jira Plugin.  I see this 
functionality should have been added awhile back on the plugin page, but I 
cannot seem to figure out how to do this.

per https://wiki.jenkins.io/display/JENKINS/JIRA+Plugin 
Version 1.39 (Oct 6, 2013)
   
   - Ability only to comment issue without processing of workflow (pull #38 
   <https://github.com/jenkinsci/jira-plugin/pull/38>)


The Issue Updater plugin and jira-ext plugin both can do this, but I was 
hoping to utilize the jenkins jira plugin as much as possible.  If anyone 
has any experience with this feature, I'd love to hear how it can be done.
The Marvelution Jira Add-on for jenkins will accomplish exactly this, but 
it's polling jenkins for changes to jobs and this would cause too much 
overhead for us so I'd prefer to use the jira plugin to do push 
notifications for completed jobs.

Thanks in advance!
Josh

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/88a2f1c2-3736-4b48-8ba8-1246cd1be4a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Getting the Jira URL value from Jira plugin

[t3knoid]

I am using the Jira and Jira-ext plugins to integrate with a Jira server. I 
want to write a script where I have to enumerate the Jira URL (I dont want 
to hard code it in my script). Where can I get that value?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3d4aa1f3-5d63-4809-9518-9cfea743bce6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

JIRA plugin: add issue labels

[Alex Vasilkov]

Hi,

I'm using JIRA Plugin
<https://wiki.jenkins.io/display/JENKINS/JIRA+Plugin> v2.4.2
and trying to add a lebel with build number to each related JIRA issue.

Changelog for version 2.2 says that it now has "Support adding labels to
updated issues".
I also checked source code and can see that adding labels is supported by
JiraIssueUpdater
<https://github.com/jenkinsci/jira-plugin/blob/master/src/main/java/hudson/plugins/jira/JiraIssueUpdater.java>
.

But I can't see how I can sepcify these labels. Specifically I want to be
able to set new label based on environment parameter. Could you please
point me on how I can achive it?

Regards,
Alex Vasilkov

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CACLi4PzRwxw%3D-76SVAdkYnvmcX%3DF-tfOOucoNeKvRYSsyUfGVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins-jira-plugin: Failed to authenticate with JIRA

[James Green]

The Wiki page says:

"Starting from this plugin version 2.0, it is using JIRA REST API to
communicate instead of JIRA RPC SOAP which has been deprecated and removed
since JIRA v.7.0"

So that's the SOAP interface dropped since version 2. Inside JIRA I think
it's had a REST interface since around version 4. There's no suggestion
that the plugin should not work against the REST interface in JIRA-6.

My copy of IntelliJ is working against our JIRA-6 instance via the Tasks
component without trouble - which I strongly suspect is also using the REST
interface.

James


On 25 July 2017 at 13:48, Alex Johnson  wrote:

> Hello James,
>
> Glancing at the plugin wiki page
> <https://wiki.jenkins.io/display/JENKINS/JIRA+Plugin> it seems you are
> correct - you need Jira v7.0 to use the latest version of the plugin.
>
> Installing version 1.41 (latest pre-2.0) could resolve this problem
> http://updates.jenkins-ci.org/download/plugins/jira/
> <http://updates.jenkins-ci.org/download/plugins/jira/1.41/jira.hpi>, but
> I'd suggest upgrading Jira to 7.0 if possible to use the latest version of
> the plugin.
>
> br,
> -Alex
>
> On Monday, July 24, 2017 at 4:02:42 AM UTC-4, James Green wrote:
>>
>> Got the latest LTS version of Jenkins with current jenkins-jira-plugin
>> and a JIRA 6.4 installation.
>>
>> I can log in to JIRA without issue and in the configuration I can see
>> that the Remote API is indeed switched on.
>>
>> When I do a wget from our Jenkins box against JIRA I get told I'm not
>> authenticated - perfect.
>>
>> When I configure the JIRA plugin within Jenkins using my credentials I
>> hit "Validate" and get told Failed to authenticate.
>>
>> Checked the Jenkins logs and I find a stack trace. An HTTP response has
>> been received - HTML output with markup that I've failed to authenticate.
>> The stack trace itself says it expected a JSON response!
>>
>> I'm sure this must be pretty fundamental. Does it somehow require a more
>> recent version of JIRA or something that I've not spotted?
>>
>> Thanks,
>>
>> James
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/d4e39397-8d99-4065-a686-a1659ebb3992%40googlegroups.
> com
> <https://groups.google.com/d/msgid/jenkinsci-users/d4e39397-8d99-4065-a686-a1659ebb3992%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMH6%2BawjwbNcbZisv0XYxGHZXq7MKsJP5UVGiT%2B0OfSqN_zuwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins-jira-plugin: Failed to authenticate with JIRA

[Alex Johnson]

Hello James,

Glancing at the plugin wiki page 
<https://wiki.jenkins.io/display/JENKINS/JIRA+Plugin> it seems you are 
correct - you need Jira v7.0 to use the latest version of the plugin.

Installing version 1.41 (latest pre-2.0) could resolve this problem 
http://updates.jenkins-ci.org/download/plugins/jira/ 
<http://updates.jenkins-ci.org/download/plugins/jira/1.41/jira.hpi>, but 
I'd suggest upgrading Jira to 7.0 if possible to use the latest version of 
the plugin.

br,
-Alex

On Monday, July 24, 2017 at 4:02:42 AM UTC-4, James Green wrote:
>
> Got the latest LTS version of Jenkins with current jenkins-jira-plugin and 
> a JIRA 6.4 installation.
>
> I can log in to JIRA without issue and in the configuration I can see that 
> the Remote API is indeed switched on.
>
> When I do a wget from our Jenkins box against JIRA I get told I'm not 
> authenticated - perfect.
>
> When I configure the JIRA plugin within Jenkins using my credentials I hit 
> "Validate" and get told Failed to authenticate.
>
> Checked the Jenkins logs and I find a stack trace. An HTTP response has 
> been received - HTML output with markup that I've failed to authenticate. 
> The stack trace itself says it expected a JSON response!
>
> I'm sure this must be pretty fundamental. Does it somehow require a more 
> recent version of JIRA or something that I've not spotted?
>
> Thanks,
>
> James
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/d4e39397-8d99-4065-a686-a1659ebb3992%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

jenkins-jira-plugin: Failed to authenticate with JIRA

[James Green]

Got the latest LTS version of Jenkins with current jenkins-jira-plugin and
a JIRA 6.4 installation.

I can log in to JIRA without issue and in the configuration I can see that
the Remote API is indeed switched on.

When I do a wget from our Jenkins box against JIRA I get told I'm not
authenticated - perfect.

When I configure the JIRA plugin within Jenkins using my credentials I hit
"Validate" and get told Failed to authenticate.

Checked the Jenkins logs and I find a stack trace. An HTTP response has
been received - HTML output with markup that I've failed to authenticate.
The stack trace itself says it expected a JSON response!

I'm sure this must be pretty fundamental. Does it somehow require a more
recent version of JIRA or something that I've not spotted?

Thanks,

James

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMH6%2BazeDiy6dvMRw4J6f965eSvm1gqcBgB-O288k8Uip1bKag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: JIRA-Plugin comments huge loads of issues since Update

[d . guthmann]

Hello,

 

> Since the Update to Jenkins 2 the PostBuild-Action comments a huge amount of JIRA-Issues when a build is finished, which had "Changes in Dependencies".

 

Basically I don't understand what causes the "Changes in Dependencies" in Jenkins. I've inspected some of those builds, for which "Changes in Dependencies" is displayed, but that build wasn't triggered by a svn:external-Commit...

Any hints...?

 

Best Regards

 

Dieter




-- 
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-c7d60490-6ca7-4cf1-847a-fc4e0a8ded0e-1498228552125%403capp-gmx-bs56.
For more options, visit https://groups.google.com/d/optout.

JIRA-Plugin comments huge loads of issues since Update

[Dieter Guthmann]

Hello there,

 

we've got problems with the JIRA-Plugin for Jenkins since we've updated our Jenkins-Master from 1.609.3 to 2.46.3 (both LTS).

We've updated also the JIRA-Plugin-Version to 2.3.1.

 

For many of our Jobs the Post-Build-Action "JIRA: Update relevant issues" is enabled (in our previous used JIRA-Plugin-Version nothing has to be configured there, now an "issue selector" can be choosen here - I've used the "Default selector").

Since the Update to Jenkins 2 the PostBuild-Action comments a huge amount of JIRA-Issues when a build is finished, which had "Changes in Dependencies". When a build is finished which was started due to a repository change in the 'main repository' no problem occours (Issues are commented properly, if an Issue-Key was mentioned in the SVN-Commit-Message).

 

I've attached a build-console-Output below.

 

We use Subversion as Code Repository - for libraries are also "subversion externals" in use (= Dependencies). For all Repositories a SVN Post-Commit-Hook is enabled which triggers Jenkins.

And we use subversion externals also as a replacement for "symbolic links" with the following notation:

svn:externals = ../other/directory/in/the/same/repository/file.txt file.txt

 

From which sources does the JIRA-Plugin extracts those issues? There are more issues commented, than svn:externals are existent - and many of the externals most recent commit messages doesn't contain a JIRA-Issue-Key at all...

 

Thanks in Advance.

 

Rgds

Dieter Guthmann

 

- Build Console Output 

[WARNINGS] Parsing warnings in console log with parser GNU C Compiler 4 (gcc)
[WARNINGS] Computing warning deltas based on reference build #3311
[WARNINGS] Plug-in Result: Success - no threshold has been exceeded
Archiving artifacts
Recording fingerprints
[JIRA] Updating issue JIRA-2940
[JIRA] Updating issue JIRA-2976
[JIRA] Updating issue JIRA-2646
[JIRA] Updating issue JIRA-2772
[JIRA] Updating issue JIRA-2791
[JIRA] Updating issue JIRA-2755
[JIRA] Updating issue JIRA-2771
[JIRA] Updating issue JIRA-2120
[JIRA] Updating issue JIRA-2236
[JIRA] Updating issue JIRA-2689
[JIRA] Updating issue JIRA-1141
[JIRA] Updating issue JIRA-2215
[JIRA] Updating issue JIRA-2337
[JIRA] Updating issue JIRA-2562
[JIRA] Updating issue JIRA-2523
[JIRA] Updating issue JIRA-1680
[JIRA] Updating issue JIRA-1270
[JIRA] Updating issue JIRA-2386
[JIRA] Updating issue JIRA-2379
[JIRA] Updating issue JIRA-2040
[JIRA] Updating issue JIRA-2052
[JIRA] Updating issue JIRA-2030
[JIRA] Updating issue JIRA-2347
[JIRA] Updating issue JIRA-2346
[JIRA] Updating issue JIRA-1724
[JIRA] Updating issue JIRA-1595
[JIRA] Updating issue JIRA-1883
[JIRA] Updating issue JIRA-1754
[JIRA] Updating issue JIRA-1871
[JIRA] Updating issue JIRA-1858
[JIRA] Updating issue JIRA-939
[JIRA] Updating issue JIRA-1793
[JIRA] Updating issue JIRA-1770
[JIRA] Updating issue JIRA-281
[JIRA] Updating issue JIRA-1642
[JIRA] Updating issue JIRA-1473
[JIRA] Updating issue JIRA-1537
[JIRA] Updating issue JIRA-1307
[JIRA] Updating issue JIRA-1263
[JIRA] Updating issue JIRA-1048
[JIRA] Updating issue JIRA-1470
[JIRA] Updating issue JIRA-1436
[JIRA] Updating issue JIRA-1237
[JIRA] Updating issue JIRA-1303
[JIRA] Updating issue JIRA-1328
[JIRA] Updating issue JIRA-1306
[JIRA] Updating issue JIRA-1309
[JIRA] Updating issue JIRA-1281
[JIRA] Updating issue JIRA-1261
[JIRA] Updating issue JIRA-1262
[JIRA] Updating issue STMM-38
[JIRA] Updating issue JIRA-633
[JIRA] Updating issue JIRA-838
[JIRA] Updating issue JIRA-1179
[JIRA] Updating issue JIRA-1177
[JIRA] Updating issue JIRA-1098
[JIRA] Updating issue JIRA-933
[JIRA] Updating issue JIRA-1065
[JIRA] Updating issue JIRA-965
[JIRA] Updating issue JIRA-59
[JIRA] Updating issue JIRA-1056
[JIRA] Updating issue JIRA-849
[JIRA] Updating issue JIRA-923
[JIRA] Updating issue JIRA-1265
[JIRA] Updating issue JIRA-3296
[JIRA] Updating issue JIRA-3272
[JIRA] Updating issue JIRA-3297
[JIRA] Updating issue JIRA-3312
[JIRA] Updating issue JIRA-3322
[JIRA] Updating issue JIRA-2750
[JIRA] Updating issue JIRA-3300
[JIRA] Updating issue JIRA-3317
Recording plot data



-- 
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-7bfde448-19a6-4550-9db5-f9fd09028a28-1497451689348%403capp-gmx-bs75.
For more options, visit https://groups.google.com/d/optout.

Re: Required core for jira plugin

[Slide]

It is the minimum version required.

On Wed, Mar 22, 2017, 10:42 Gustavo Czobel  wrote:

> Hi,
> I see in the Jira Plugin wiki
> https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin that the Required
> Core is 1.642.3
>
> This means the *minimum *core version required or the *required *core?
>
> Can I use this plugin with core 1.658 ? (This is the latest core before
> 2.0)
>
> Thanks in advance
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/42788223-918b-4349-a771-25ea8926a7ee%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/42788223-918b-4349-a771-25ea8926a7ee%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVdX%2BajGwJSosUrm2ZiE46pXX%3DJBRDy64AGNo-u_%3DUGMmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Required core for jira plugin

[Gustavo Czobel]

Hi,
I see in the Jira Plugin wiki 
https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin that the Required 
Core is 1.642.3

This means the *minimum *core version required or the *required *core?

Can I use this plugin with core 1.658 ? (This is the latest core before 2.0)

Thanks in advance


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/42788223-918b-4349-a771-25ea8926a7ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Problem with Jira plugin 2.3

[vf]

Thank you, slide.
I didnt change anything, or at least tried to avoid any other changes, in 
fact I saw the incompatibility warnings and upgraded therefore only jira 
plugin, it brought upgrades of other plugins automatically (scm api2, 
branch api, folder etc). And as I said, I tested the upgrade on a fresh 
Jenkins 2.44 installation, with no plugins installed by the wizard, only 
jira 2.3 thereafter, and the same error occured.
Since my test with issues.jenkins-ci.org works just fine, it seems to me 
that our Jira server might be the culprit, although 2.2.1 and older worked 
with our jira without issues. 
I also suspect that the underlying apache httpcomponents might cause some 
version specific imcompatibilities (our jira server is v6, 
issues.jenkins-ci.org is v7+), tried to debug down to jira-plugin, but did 
not yet tracked it down (still trying).


Am Freitag, 10. Februar 2017 18:40:00 UTC+1 schrieb slide:
>
> Root of the problem looks to be:
>
> JSONException: A JSONObject text must begin with '{' at character 19 of 
>  
>   
>Wrong host!
>   
>   
>Please use a valid host.
>   
>  
>
> Nothing in your setup changed other than the plugin version? Did you check 
> the change log of the plugin to see if there were any notes on config 
> updates you might need to do? It looks like your server is responding with 
> the data above, which is causing the exception.
>
> On Fri, Feb 10, 2017, 08:01 vf > wrote:
>
>> More information:
>> Our Jira version: v6.3.1#6329-sha1:7df76f1
>> issues.jenkins-ci.org: v7.1.7#71011-sha1:2526d7c
>>
>>
>> Am Freitag, 10. Februar 2017 13:00:52 UTC+1 schrieb vf:
>>>
>>> Hi,
>>>
>>> I upgraded Jira plugin from 2.2.1 to 2.3, and could not make it working 
>>> (see stack trace below). 
>>> System:
>>>   Jenkins 2.44 on RHEL, OpenJDK 1.8.0_121
>>> Jira plugin configuration: (unchanged fo 3+ years)
>>>  url https://my.company.com/jira/
>>>  username + password
>>>  other fields are all default.
>>>
>>> I tested on a fresh installation: Jenkins 2.44, with only jira plugin 
>>> 2.3 installed.
>>>
>>> I can reproduce the stacktrace by validating my configuration on the 
>>> configure screen.
>>>
>>> But, when I test https://issues.jenkins-ci,org/ with my account, it 
>>> works without any problem.
>>>
>>> So I am very much stuck here, Can anyone give me a hint?
>>>
>>> thanks
>>> vf
>>>
>>>
>>> WARNUNG: Failed to login to JIRA at https://my.company.com/jira/
>>> RestClientException{statusCode=Optional.absent(), errorCollections=[]}
>>> at 
>>> com.atlassian.jira.rest.client.internal.async.DelegatingPromise.claim(DelegatingPromise.java:47)
>>> at 
>>> hudson.plugins.jira.JiraRestService.getMyPermissions(JiraRestService.java:407)
>>> at hudson.plugins.jira.JiraSession.getMyPermissions(JiraSession.java:462)
>>> at 
>>> hudson.plugins.jira.JiraSite$DescriptorImpl.doValidate(JiraSite.java:763)
>>> 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:483)
>>> at 
>>> org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
>>> at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
>>> at 
>>> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
>>> at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
>>> at 
>>> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
>>> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
>>> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>>> at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
>>> at 
>>> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
>>> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
>>> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
>>> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
>>> at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
>>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>>> at org.mortbay.jetty.servlet.Servl

Re: Problem with Jira plugin 2.3

[Slide]

Root of the problem looks to be:

JSONException: A JSONObject text must begin with '{' at character 19 of
 
  
   Wrong host!
  
  
   Please use a valid host.
  
 

Nothing in your setup changed other than the plugin version? Did you check
the change log of the plugin to see if there were any notes on config
updates you might need to do? It looks like your server is responding with
the data above, which is causing the exception.

On Fri, Feb 10, 2017, 08:01 vf  wrote:

> More information:
> Our Jira version: v6.3.1#6329-sha1:7df76f1
> issues.jenkins-ci.org: v7.1.7#71011-sha1:2526d7c
>
>
> Am Freitag, 10. Februar 2017 13:00:52 UTC+1 schrieb vf:
>
> Hi,
>
> I upgraded Jira plugin from 2.2.1 to 2.3, and could not make it working
> (see stack trace below).
> System:
>   Jenkins 2.44 on RHEL, OpenJDK 1.8.0_121
> Jira plugin configuration: (unchanged fo 3+ years)
>  url https://my.company.com/jira/
>  username + password
>  other fields are all default.
>
> I tested on a fresh installation: Jenkins 2.44, with only jira plugin 2.3
> installed.
>
> I can reproduce the stacktrace by validating my configuration on the
> configure screen.
>
> But, when I test https://issues.jenkins-ci,org/ with my account, it works
> without any problem.
>
> So I am very much stuck here, Can anyone give me a hint?
>
> thanks
> vf
>
>
> WARNUNG: Failed to login to JIRA at https://my.company.com/jira/
> RestClientException{statusCode=Optional.absent(), errorCollections=[]}
> at
> com.atlassian.jira.rest.client.internal.async.DelegatingPromise.claim(DelegatingPromise.java:47)
> at
> hudson.plugins.jira.JiraRestService.getMyPermissions(JiraRestService.java:407)
> at hudson.plugins.jira.JiraSession.getMyPermissions(JiraSession.java:462)
> at
> hudson.plugins.jira.JiraSite$DescriptorImpl.doValidate(JiraSite.java:763)
> 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:483)
> at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
> at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
> at
> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
> at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
> at
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
> at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
> at
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
> at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1074)
> at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
> at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
> at
> hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
> at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at
> org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at
> hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at
> org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at org.mortbay.jetty.ser

Re: Problem with Jira plugin 2.3

[vf]

More information:
Our Jira version: v6.3.1#6329-sha1:7df76f1
issues.jenkins-ci.org: v7.1.7#71011-sha1:2526d7c

Am Freitag, 10. Februar 2017 13:00:52 UTC+1 schrieb vf:
>
> Hi,
>
> I upgraded Jira plugin from 2.2.1 to 2.3, and could not make it working 
> (see stack trace below). 
> System:
>   Jenkins 2.44 on RHEL, OpenJDK 1.8.0_121
> Jira plugin configuration: (unchanged fo 3+ years)
>  url https://my.company.com/jira/
>  username + password
>  other fields are all default.
>
> I tested on a fresh installation: Jenkins 2.44, with only jira plugin 2.3 
> installed.
>
> I can reproduce the stacktrace by validating my configuration on the 
> configure screen.
>
> But, when I test https://issues.jenkins-ci,org/ with my account, it works 
> without any problem.
>
> So I am very much stuck here, Can anyone give me a hint?
>
> thanks
> vf
>
>
> WARNUNG: Failed to login to JIRA at https://my.company.com/jira/
> RestClientException{statusCode=Optional.absent(), errorCollections=[]}
> at 
> com.atlassian.jira.rest.client.internal.async.DelegatingPromise.claim(DelegatingPromise.java:47)
> at 
> hudson.plugins.jira.JiraRestService.getMyPermissions(JiraRestService.java:407)
> at hudson.plugins.jira.JiraSession.getMyPermissions(JiraSession.java:462)
> at 
> hudson.plugins.jira.JiraSite$DescriptorImpl.doValidate(JiraSite.java:763)
> 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:483)
> at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
> at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
> at 
> org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
> at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
> at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
> at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
> at 
> org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
> at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
> at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1074)
> at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
> at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at 
> hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
> at 
> hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
> at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at 
> org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at 
> hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at 
> org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
> at 
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185)
> at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)
> at 
> org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:146)
> at 
> org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> at 

Problem with Jira plugin 2.3

[vf]

Hi,

I upgraded Jira plugin from 2.2.1 to 2.3, and could not make it working 
(see stack trace below). 
System:
  Jenkins 2.44 on RHEL, OpenJDK 1.8.0_121
Jira plugin configuration: (unchanged fo 3+ years)
 url https://my.company.com/jira/
 username + password
 other fields are all default.

I tested on a fresh installation: Jenkins 2.44, with only jira plugin 2.3 
installed.

I can reproduce the stacktrace by validating my configuration on the 
configure screen.

But, when I test https://issues.jenkins-ci,org/ with my account, it works 
without any problem.

So I am very much stuck here, Can anyone give me a hint?

thanks
vf


WARNUNG: Failed to login to JIRA at https://my.company.com/jira/
RestClientException{statusCode=Optional.absent(), errorCollections=[]}
at 
com.atlassian.jira.rest.client.internal.async.DelegatingPromise.claim(DelegatingPromise.java:47)
at 
hudson.plugins.jira.JiraRestService.getMyPermissions(JiraRestService.java:407)
at hudson.plugins.jira.JiraSession.getMyPermissions(JiraSession.java:462)
at hudson.plugins.jira.JiraSite$DescriptorImpl.doValidate(JiraSite.java:763)
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:483)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:491)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1074)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at 
hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
at 
org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
at 
hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
at 
org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at 
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1065)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
at 
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:185)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:689)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:391)
at 
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:146)
at 
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:285)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:457)
at 
org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:765)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:628)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:209)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:357)
at 
org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:329)
at 
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:475)
Caused by: RestClientException

JIRA Plugin + "Update Jira Issues For All Build Results" doesn't get triggered when the bug number is on in the title

[Stathis]

My developer do not always include the bug number in the title. They often 
do so in the message itself which doesn't seem to be triggering an update 
to the bug when 'Update Jira Issues For All Build Results" setting is on.
Do you have any thoughts?
Thanks in advance for your help!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/043130a1-6365-4ea0-a678-92f8f33f1c4c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jira plugin failed to find Ticket

[Eliran Shlomo]

Hi, i'm trying to integrate jenkins with jira but it's keep saying that he 
couldn't find JIRA project

Nov 04, 2015 2:11:58 PM FINE hudson.plugins.jira.JiraChangeLogAnnotator

Using issue pattern: ([a-zA-Z][a-zA-Z0-9_]+-[1-9][0-9]*)([^.]|\.[^0-9]|\.$|$)

Nov 04, 2015 2:11:58 PM INFO hudson.plugins.jira.JiraChangeLogAnnotator annotate

No known JIRA project corresponding to id: 'WP-4795'











please advise
Regards,
Eliran

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/78168f4d-b320-4389-852e-7825db2956a0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Aw: JIRA-Plugin: Problem with SVN-Externals

[d . guthmann]

Additional Information:

We use currently Jenkins vers. 1.509.4 with the "Jenkins JIRA plugin" V. 1.39

 



-- 
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/trinity-48f03dac-d594-4dfb-b4e9-65d5daefca65-1443596231777%403capp-gmx-bs37.
For more options, visit https://groups.google.com/d/optout.

JIRA-Plugin: Problem with SVN-Externals

[Dieter Guthmann]

Hi,
 
we use Jenkins-CI with a SVN post commit hook script as build trigger.
Our SVN repositories uses heavily "SVN externals" for 'importing' independent 
modules into other repositories. So a build can be triggered by a commit onto 
the original project-repository or by a commit at one of the 'imported' 
repositories.
That configuration does works almost perfectly in Jenkins - builds are 
triggered in both cases.
 
We've now activated den JIRA-Plugin to connect our JIRA-Instance (v6.4.11). The 
comment-function basically works and looks really helpful - in svn repositories 
which no SVN-externals are used, the JIRA-comment-function works great.
In projects WITH externals the plugin often creates numerous comments per 
commit. Thats ok, when a commit affects more than one 
jenkins-job/svn-project-repository if e.g. some work in a 'imported' module was 
done:
SUCCESS: integrated in PROJECT A

- files
SUCCESS: integrated in PROJECT B

- files
 
But sometimes ONE JIRA-Issue is commented by the JIRA-Plugin for multiple 
builds out of the same Jenkins-job. e.g.
SUCCESS: integrated in PROJECT A #2366
SUCCESS: integrated in PROJECT A #2367
 
The commit-comment of Build 2367 doesn't contain any JIRA Issue-ID 
(commit-comment was empty also) or sometimes it contained a different JIRA 
Issue-ID (can't see a pattern at this time).
That problem does not occur on every build. It seems that these problems only 
affects jobs with subversion-repositories, which has 'svn-externals' referenced.
 
Thanks in Advance.
 
Rgds.
Dieter

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/trinity-380d5e80-8f6d-436e-9474-f5f558d7d34c-1443592787800%403capp-gmx-bs31.
For more options, visit https://groups.google.com/d/optout.

jira plugin

[g.fer.ordas]

Hi

I would like to know about a jura plugin which will simple raise a new 
issue upon completion of a job.

I got the following installed:

https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin

I have defined in my job :
Post build Action ->Create Jira Issue

But for some reason it does not seem to do anything at all. 

Maybe any other plugin o top in relation with some Jira ticket automation? 
(just to create the issue)

If that is the right Plugin and the correct task,. Any tips how to maybe 
debug or configure that properly?

thanks!!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/52538f81-d9d0-4da0-9b72-10d1dc5535d6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

JIRA Plugin not adding comment on downstream builds

[Matt Ouellette]

I have been trying to use the JIRA Plugin 
<https://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin> to integrate 
Jenkins and JIRA.  From what I've read, the JIRA plugin should be able to 
use fingerprint information to update the JIRA ticket when a downstream 
build runs that uses that artifact.

ex: a fix is made to projectA and the build updates the relevant JIRA 
ticket.  After projectA is built, projectB (which depends on projectA) 
builds, and that should also update the JIRA ticket.

However, I am only getting an update on the JIRA ticket from the build of 
projectA and not from the both (the projectB build is the one I really care 
about).  I double checked the fingerprint of the artifact in Jenkins and it 
does recognize the relationship between the two builds, and I made sure 
both jobs were configured with the "Update relevant JIRA issues" post build 
action.  I'm not sure if I have mis-understood the description of the 
plugin and this isn't possible, or if I just simply have something 
mis-configured.  After searching around online, I couldn't find any similar 
issues with the plugin, so I'm coming here to see if anyone uses that 
plugin in this way, and if so if there is any special configuration that 
needs to be done to get it to work that I may have missed.


-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/68c5ff88-6a82-47af-8581-6490a2f61e19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Can Jenkins-Jira plugin move Jira issues from Resolved to Needs Verification?

[dudemous]

We are using the git plugin and the Jenkins-Jira plugin in our job 
configurations.
Our git commit messages all have a Jira ID, so in a continuous build we see 
a list of git changes and the Jira IDs associated with them.
We use the Jenkins-Jira plugin to update issues for each build, which is 
working fine.

I've been asked to have each build move the Jira issues from Resolved to 
Needs Verification.
I've tried using the "Move issues matching JQL to the specified version" 
but that doesn't seem to work...we don't use "Jira Release" fields so I'm 
not really sure if this will do what I want.

Is this something the plugin can do and I'm just missing how to set it up, 
or should I write a script to do this via the Jira REST api?
I'm not sure how to get the changelog info from the Git SCM plugin at build 
time...I can get it from Jenkins REST api after the build has finished, so 
I could make a downstream job that does all the api commands, but I'd 
rather do this all in the same job.

I was initially asked to write a plugin to do this but I'm not a Java 
developer so I dismissed that idea.  I have looked at the Java code for the 
plugin and I've done some groovy scripts with the cli so I might be able to 
figure something out...I'd rather use an existing plugin though.

Any help or suggestions would be appreciated.

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

Re: Jira plugin disabled but still updated JIRA issues ?!

[Marek Marzec]

W dniu wtorek, 20 sierpnia 2013 15:43:42 UTC+2 użytkownik Marek Marzec 
napisał:
>
> 1) It was FULL restart.
>
>
> 2) listting of plugins dir:
>
>
> drwxr-xr-x  4 jenkins nogroup 4096 Aug 16 22:23   *jira*
> -rw-r--r-- 1 jenkins nogroup  2045030 Mar 20 21:45 ji*ra.bak*
> -rw-r--r-- 1 jenkins nogroup  2064637 Aug 16 22:23 *jira.jpi*
> -rw-r--r-- 1 jenkins nogroup0 Aug 19 09:10 *
> jira.jpi.disabled*
>
>
> so seems that plugin is disabled (*jira.jpi.disabled*
> ) & active (*jira.jpi*) at once or ?
>
>
> Can  I safetly  delete jira.jpi file ?
>

Replying myself:

RTFM: 

https://wiki.jenkins-ci.org/display/JENKINS/Removing+and+disabling+plugins

>
>>  
>>
>>

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

Re: Jira plugin disabled but still updated JIRA issues ?!

[Marek Marzec]

1) It was FULL restart.


2) listting of plugins dir:


drwxr-xr-x  4 jenkins nogroup 4096 Aug 16 22:23   *jira*
-rw-r--r-- 1 jenkins nogroup  2045030 Mar 20 21:45 ji*ra.bak*
-rw-r--r-- 1 jenkins nogroup  2064637 Aug 16 22:23 *jira.jpi*
-rw-r--r-- 1 jenkins nogroup0 Aug 19 09:10 *
jira.jpi.disabled*


so seems that plugin is disabled (*jira.jpi.disabled*
) & active (*jira.jpi*) at once or ?


Can  I safetly  delete jira.jpi file ?




W dniu wtorek, 20 sierpnia 2013 14:40:37 UTC+2 użytkownik 
matthew...@diamond.ac.uk napisał:
>
>  Do you restart Jenkins, or just "reload configuration from disk"? I 
> think you need to do a full restart.
>
>  
>   
> *From:* jenkins...@googlegroups.com  [mailto:
> jenkins...@googlegroups.com ] *On Behalf Of *Marek Marzec
> *Sent:* 20 August 2013 12:32
> *To:* jenkins...@googlegroups.com 
> *Subject:* Re: Jira plugin disabled but still updated JIRA issues ?!
>  
>  
>  
>
>
> W dniu wtorek, 20 sierpnia 2013 13:19:28 UTC+2 użytkownik Ullrich Hafner 
> napisał:
>  
> Did you restart Jenkins?
>  
>
> Forgot to add -> sure, I'd restarted jenkins
>  
>  
>   
>  
>  
>
> Jenkins 1.519.
>
> In plugin I manager i switched off (untick checkbox) : Jenkins JIRA 
> plugin<http://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin>vers 1.37 - 
> still JIRA issues are being commented.
>
>
> Any ideas how to disable this plugin?
>
> How this jenkins "enable plugin" function works?
>
> Didn't want to unistall plugin completely as all of ours 400 builds use 
> this and I was not sure how build will react ... remove configuration from 
> builds or just skip this (ad unreadable data ) as Jenkins do this...
>
>
>
> Thx for help and all hints
>  
>  
>  
> 
>  
>
> --  
>
> This e-mail and any attachments may contain confidential, copyright and or 
> privileged material, and are for the use of the intended addressee only. If 
> you are not the intended addressee or an authorised recipient of the 
> addressee please notify us of receipt by returning the e-mail and do not 
> use, copy, retain, distribute or disclose the information in or attached to 
> the e-mail.
> Any opinions expressed within this e-mail are those of the individual and 
> not necessarily of Diamond Light Source Ltd. 
> Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
> attachments are free from viruses and we cannot accept liability for any 
> damage which you may sustain as a result of software viruses which may be 
> transmitted in or with the message.
> Diamond Light Source Limited (company no. 4375679). Registered in England 
> and Wales with its registered office at Diamond House, Harwell Science and 
> Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom
>  
>
>

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

RE: Jira plugin disabled but still updated JIRA issues ?!

[Matthew.Webber]

Do you restart Jenkins, or just "reload configuration from disk"? I think you 
need to do a full restart.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Marek Marzec
Sent: 20 August 2013 12:32
To: jenkinsci-users@googlegroups.com
Subject: Re: Jira plugin disabled but still updated JIRA issues ?!



W dniu wtorek, 20 sierpnia 2013 13:19:28 UTC+2 użytkownik Ullrich Hafner 
napisał:
Did you restart Jenkins?

Forgot to add -> sure, I'd restarted jenkins




Jenkins 1.519.

In plugin I manager i switched off (untick checkbox) : Jenkins JIRA 
plugin<http://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin> vers 1.37 - 
still JIRA issues are being commented.


Any ideas how to disable this plugin?

How this jenkins "enable plugin" function works?

Didn't want to unistall plugin completely as all of ours 400 builds use this 
and I was not sure how build will react ... remove configuration from builds or 
just skip this (ad unreadable data ) as Jenkins do this...



Thx for help and all hints




-- 

This e-mail and any attachments may contain confidential, copyright and or 
privileged material, and are for the use of the intended addressee only. If you 
are not the intended addressee or an authorised recipient of the addressee 
please notify us of receipt by returning the e-mail and do not use, copy, 
retain, distribute or disclose the information in or attached to the e-mail.

Any opinions expressed within this e-mail are those of the individual and not 
necessarily of Diamond Light Source Ltd. 

Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments 
are free from viruses and we cannot accept liability for any damage which you 
may sustain as a result of software viruses which may be transmitted in or with 
the message.

Diamond Light Source Limited (company no. 4375679). Registered in England and 
Wales with its registered office at Diamond House, Harwell Science and 
Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

 







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

Re: Jira plugin disabled but still updated JIRA issues ?!

[Marek Marzec]

W dniu wtorek, 20 sierpnia 2013 13:19:28 UTC+2 użytkownik Ullrich Hafner 
napisał:
>
> Did you restart Jenkins?
>

Forgot to add -> sure, I'd restarted jenkins
 

>
>
>
> Jenkins 1.519.
>
> In plugin I manager i switched off (untick checkbox) : Jenkins JIRA 
> plugin<http://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin>vers 1.37 - 
> still JIRA issues are being commented.
>
>
> Any ideas how to disable this plugin?
>
> How this jenkins "enable plugin" function works?
>
> Didn't want to unistall plugin completely as all of ours 400 builds use 
> this and I was not sure how build will react ... remove configuration from 
> builds or just skip this (ad unreadable data ) as Jenkins do this...
>
>
>
> Thx for help and all hints
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-use...@googlegroups.com .
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

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

Re: Jira plugin disabled but still updated JIRA issues ?!

[Ulli Hafner]

Did you restart Jenkins?

Ulli

Am 20.08.2013 um 13:01 schrieb Marek Marzec :

> Hello,
> 
> 
> Jenkins 1.519.
> 
> In plugin I manager i switched off (untick checkbox) : Jenkins JIRA plugin 
> vers 1.37 - still JIRA issues are being commented.
> 
> 
> Any ideas how to disable this plugin?
> 
> How this jenkins "enable plugin" function works?
> 
> Didn't want to unistall plugin completely as all of ours 400 builds use this 
> and I was not sure how build will react ... remove configuration from builds 
> or just skip this (ad unreadable data ) as Jenkins do this...
> 
> 
> 
> Thx for help and all hints
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.



signature.asc
Description: Message signed with OpenPGP using GPGMail

Jira plugin disabled but still updated JIRA issues ?!

[Marek Marzec]

Hello,


Jenkins 1.519.

In plugin I manager i switched off (untick checkbox) : Jenkins JIRA 
plugin<http://wiki.jenkins-ci.org/display/JENKINS/JIRA+Plugin>vers 1.37 - still 
JIRA issues are being commented.


Any ideas how to disable this plugin?

How this jenkins "enable plugin" function works?

Didn't want to unistall plugin completely as all of ours 400 builds use 
this and I was not sure how build will react ... remove configuration from 
builds or just skip this (ad unreadable data ) as Jenkins do this...



Thx for help and all hints

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

Jira plugin : released version

[valipost]

Hello.
I'm trying to configure Jenkins to work with Perforce and Jira. The Perforce
part is working, I'm having issues with the Jira plugin.
I will be using Perforce to keep the version information, in a counter (a
Perforce variable). I can get them in jenkins environment variables if
needed.
The question is simple, how can I use these values so that Jira version
equals the Perforce one.
(there is a field for that, the wiki isn't clear).
Thanks.



--
View this message in context: 
http://jenkins-ci.361315.n4.nabble.com/Jira-plugin-released-version-tp4676382.html
Sent from the Jenkins users mailing list archive at Nabble.com.

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