Re: Blue Ocean Alpha Plugin - HTTP error of HTTPS

[Michael Neale]

Oh good catch. 

I am still curious why it would redirect to http - in *theory* the header 
is available so it can know the forwarded protocol...

but good to hear this is resolved. 

On Thursday, July 28, 2016 at 10:16:25 AM UTC+10, Dominic Scheirlinck wrote:
>
> Hi Michael,
>
> The relevant part is the proxy_redirect directive (I had mine at 'off').
>
> Jenkins generates a redirect, and nginx (if acting as a reverse proxy) has 
> to rewrite the location to the correct one (Jenkins, running behind the 
> reverse proxy, is relatively correct in redirecting to HTTP I believe). 
> Something like this directive should fix the problem:
>   proxy_redirect http:// https://;
>
> This is mentioned by the wiki:
>   
> https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+behind+an+NGinX+reverse+proxy
>  
> I guess the only real strange thing is that I managed to go this long 
> without something else breaking it!
>
>
> Dom
>
>
> On Thursday, 28 July 2016 12:03:23 UTC+12, Michael Neale wrote:
>>
>> Are you able to share the relevant parts of your nginx config? 
>>
>> I that redirect seems to be the problem (it should not redirect to non 
>> https, that seems a bug). I assume you are using example.com instead of 
>> your actual url just by way of example? 
>>
>> On Thursday, July 28, 2016 at 9:59:53 AM UTC+10, Dominic Scheirlinck 
>> wrote:
>>>
>>> Here's what's going on according to my testing:
>>>
>>> - /blue/js-extensions/ is the only affected resource
>>> - The page attempts to load https://example.com/blue/js-extensions 
>>>  (NB: no trailing slash)
>>> - This results in a 302, redirecting to Location: 
>>> http://example.com/blue/js-extensions/ (NB: trailing slash, but no 
>>> HTTPS)
>>> - If I'm visiting this location directly, HSTS will send me (307) to 
>>> https://example.com/blue/js-extensions/ (finally, the working URL), but 
>>> HSTS doesn't seem to be applied to 

Re: scm.gitTool in Jenkinsfile

[nicolas de loof]

Any reason you don't set git in default path ? Would be so simpler ;)
Le 27 juil. 2016 10:56 PM, "Nigel Magnay"  a écrit :

> No, as it's not on the path so would not be found.
>
> Oddly, if I do
> scm.gitTool = 'win git'
> echo scm.gitTool
>
> it responds with 'null' - so something is odd in the field setter :-/
>
>
> On Wed, Jul 27, 2016 at 9:53 PM, Mark Waite 
> wrote:
>
>> Have you tried configuring your git executable to be "git" rather than
>> "/usr/bin/git"?  That's what I've used in multi-platform environments and
>> it has worked well for me.
>>
>> Mark Waite
>>
>> On Wed, Jul 27, 2016 at 1:57 PM Nigel Magnay 
>> wrote:
>>
>>> In a bitbucket-sourced multibranch repository, I need to ensure the git
>>> checkout doesn't occur with /usr/bin/git, but with a tool that stands a
>>> chance of executing on Windows.
>>>
>>> I had rather hoped it would simply be the case of doing
>>>
>>> scm.gitTool = 'win git';
>>>
>>> before my
>>> checkout scm
>>>
>>> But it still seems to insist on using the wrong binary (even though
>>> there appears to be a setter, as I had to approve it in the script console).
>>>
>>> What have I 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/CAPYP83SpLOHmoJBupi6Q0QV6TDjKOf9EYtbXrtj3NZ0L9f1PTg%40mail.gmail.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/CAO49JtG8AdnRuA8LX3xSgkpD7p9jepaec%2BjxmaLg7TRZLaBi8A%40mail.gmail.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/CAPYP83Qxg3RtukcGLL8Ouf43x3VpJmaUS0nr0zsZhFkM1Yr7Yg%40mail.gmail.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/CANMVJz%3DZceaH3FQZ4B6oXuUaHVtLXTqTjaQjC1ra83Zbgx561A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Getting build cause

[Shade Alabsa]

I've been trying to write a Jenkinsfile to do different tasks based on 
whether it's a PR or a merge in Jenkins 2. I've found the snippet below 
which will tell me if the build was triggered by a user or via Github. The 
problem is that if the build was started via a PR or a merge the reason is 
the same. Is there a better way to get this? Thanks!

 def causes = currentBuild.rawBuild.getCauses()

for ( cause in causes) {
echo "Cause: " + cause.getShortDescription()
}

-- 
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/84409776-adab-42b8-915e-93631557210b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline Jenkinsfile job script not seeing Credentials

[Francis Lalonde]

It just doesn't run. 

I've seen this behavior with the maven settings file, if you specify 
something that could not be found, the code within the block is just 
skipped. 

I've made sure to use the ugly ID in my script, but I didn't put it in my 
example for clarity.

That no credentials appear in the generator combobox looks like it's more 
than just a bad ID. I'm not entirely clear how credentials propagate to 
child jobs / folders, maybe I need to do something at the multibranch 
pipeline level to propagate credentials to generated child jobs?

On Wednesday, July 27, 2016 at 7:08:51 PM UTC-4, Michael Neale wrote:
>
> Should the credentialsId be the horrible ugly ID in advanced in 
> credentials? 
>
> is there no error, but it just doesn't run? 
>
> On Thursday, July 28, 2016 at 7:34:51 AM UTC+10, Francis Lalonde wrote:
>>
>> Hi -
>>
>> I am writing a Jenkinsfile script to automate the creation of pipelines 
>> using the multibranch plugin. The Jenkinsfile appears at the root of a 
>> github repo. Branch Indexing is working fine and the first stages (Maven 
>> commands) go trough without a hitch.
>>
>> But then I am trying to deploy using ansible, for which I need ssh. I 
>> have defined a global-scoped "secret-file" credentials, which regular jobs 
>> can see and use. But my script-generated jobs do not get access to the 
>> credentials.
>>
>> In the following sample code, the echo command never runs : 
>>
>> node() {
>> withCredentials([[$class: 'FileBinding', credentialsId: 
>> 'secret-file', variable: 'SECRET_FILE']]) {
>> echo "${SECRET_FILE}"
>> }
>> }
>>
>> Moreover, using the "withCredentials" Pipeline Syntax Snippet Generator 
>> at the branch job level, the combobox does not list any available 
>> credentials. But doing the same thing a level above (in the multibranch 
>> job), the combobox shows all global-scoped credentials, including the 
>> "secret-file" which I am looking to use in my script.
>>
>> I don't know if this is an intentional limitation, either by design or 
>> for security, that can be configured or worked around or if it is a plain 
>> bug that I should file an issue for. I tried both freshly installed Windows 
>> Jenkins 2.15 and an older 1.651.3 Linux Jenkins with updated plugins and 
>> got the same behvaior.
>>
>> If anybody has a clue, this would make my week!
>>
>> Francis
>>
>>
>>

-- 
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/66c1edb5-6358-43d6-b36a-05f62aab77d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: BlueOcean JavaScript Error

[John D. Ament]

One more thing.  Hitting this 
endpoint: 
/blue/rest/search/?q=type:pipeline;excludedFromFlattening:jenkins.branch.MultiBranchProject

has this stacktrace in it:

java.io.IOException: Failed to write status
at org.kohsuke.stapler.export.Property.safeGetValue(Property.java:151)
at org.kohsuke.stapler.export.Property.writeTo(Property.java:126)
at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
at org.kohsuke.stapler.export.Property.writeValue(Property.java:279)
at org.kohsuke.stapler.export.Property.writeValue(Property.java:222)
at org.kohsuke.stapler.export.Property.writeValue(Property.java:168)
at org.kohsuke.stapler.export.Property.writeTo(Property.java:139)
at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
at org.kohsuke.stapler.export.Property.writeValue(Property.java:279)
at org.kohsuke.stapler.export.Property.writeValue(Property.java:222)
at org.kohsuke.stapler.export.Property.writeValue(Property.java:168)
at org.kohsuke.stapler.export.Property.writeTo(Property.java:139)
at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
at org.kohsuke.stapler.export.Property.writeValue(Property.java:279)
at org.kohsuke.stapler.export.Property.writeValue(Property.java:168)
at org.kohsuke.stapler.export.Property.writeTo(Property.java:139)
at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
at org.kohsuke.stapler.export.Property.writeTo(Property.java:135)
at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223)
at org.kohsuke.stapler.export.Property.writeValue(Property.java:279)
at org.kohsuke.stapler.export.Property.writeValue(Property.java:222)
at org.kohsuke.stapler.export.Property.writeValue(Property.java:168)
at org.kohsuke.stapler.export.Property.writeTo(Property.java:139)
at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223)
at org.kohsuke.stapler.export.Property.writeValue(Property.java:279)
at org.kohsuke.stapler.export.Property.writeValue(Property.java:168)
at org.kohsuke.stapler.export.Property.writeTo(Property.java:139)
at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:227)
at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:223)
at org.kohsuke.stapler.export.Model.writeTo(Model.java:198)
at org.kohsuke.stapler.ResponseImpl.writeOne(ResponseImpl.java:285)
at 
org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:273)
at hudson.model.Api.doJson(Api.java:211)
at 
io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:55)
at 
org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124)
at 
org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69)
at org.kohsuke.stapler.Function.renderResponse(Function.java:119)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:102)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:124)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:380)
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:790)
at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812)
at 
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135)
at 
org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132)
at 
com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47)
at 

BlueOcean JavaScript Error

[John D. Ament]

Was recommended to try the blue ocean plugin for jenkins.  After setting it 
up, in my existing jenkins instance.  I get the screen "No pipelines found" 
even though I have pipelines, and found the following javascript error:

jenkins-js-extension.js:15863 SyntaxError: Unexpected token 
 in JSON at position 10362880(anonymous function) @ 
jenkins-js-extension.js:15863
jenkins-js-extension.js:15863 SyntaxError: Unexpected token (…)(anonymous 
function) @ jenkins-js-extension.js:15863

-- 
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/b35fc4d2-183e-45d1-bca9-e916506f024c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean Alpha Plugin - HTTP error of HTTPS

[Dominic Scheirlinck]

Hi Michael,

The relevant part is the proxy_redirect directive (I had mine at 'off').

Jenkins generates a redirect, and nginx (if acting as a reverse proxy) has 
to rewrite the location to the correct one (Jenkins, running behind the 
reverse proxy, is relatively correct in redirecting to HTTP I believe). 
Something like this directive should fix the problem:
  proxy_redirect http:// https://;

This is mentioned by the wiki:
  
https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+behind+an+NGinX+reverse+proxy
 
I guess the only real strange thing is that I managed to go this long 
without something else breaking it!


Dom


On Thursday, 28 July 2016 12:03:23 UTC+12, Michael Neale wrote:
>
> Are you able to share the relevant parts of your nginx config? 
>
> I that redirect seems to be the problem (it should not redirect to non 
> https, that seems a bug). I assume you are using example.com instead of 
> your actual url just by way of example? 
>
> On Thursday, July 28, 2016 at 9:59:53 AM UTC+10, Dominic Scheirlinck wrote:
>>
>> Here's what's going on according to my testing:
>>
>> - /blue/js-extensions/ is the only affected resource
>> - The page attempts to load https://example.com/blue/js-extensions  (NB: 
>> no trailing slash)
>> - This results in a 302, redirecting to Location: 
>> http://example.com/blue/js-extensions/ (NB: trailing slash, but no HTTPS)
>> - If I'm visiting this location directly, HSTS will send me (307) to 
>> https://example.com/blue/js-extensions/ (finally, the working URL), but 
>> HSTS doesn't seem to be applied to 

Re: Blue Ocean Alpha Plugin - HTTP error of HTTPS

[Michael Neale]

Are you able to share the relevant parts of your nginx config? 

I that redirect seems to be the problem (it should not redirect to non 
https, that seems a bug). I assume you are using example.com instead of 
your actual url just by way of example? 

On Thursday, July 28, 2016 at 9:59:53 AM UTC+10, Dominic Scheirlinck wrote:
>
> Here's what's going on according to my testing:
>
> - /blue/js-extensions/ is the only affected resource
> - The page attempts to load https://example.com/blue/js-extensions  (NB: 
> no trailing slash)
> - This results in a 302, redirecting to Location: 
> http://example.com/blue/js-extensions/ (NB: trailing slash, but no HTTPS)
> - If I'm visiting this location directly, HSTS will send me (307) to 
> https://example.com/blue/js-extensions/ (finally, the working URL), but 
> HSTS doesn't seem to be applied to 

Re: Blue Ocean Alpha Plugin - HTTP error of HTTPS

[Dominic Scheirlinck]

Here's what's going on according to my testing:

- /blue/js-extensions/ is the only affected resource
- The page attempts to load https://example.com/blue/js-extensions  (NB: no 
trailing slash)
- This results in a 302, redirecting to 
Location: http://example.com/blue/js-extensions/ (NB: trailing slash, but 
no HTTPS)
- If I'm visiting this location directly, HSTS will send me (307) to 
https://example.com/blue/js-extensions/ (finally, the working URL), but 
HSTS doesn't seem to be applied to 

Re: Jenkins CLI, trouble installing plugin from local hpi

[James Richard]

Manually uploading the files to the server works fine, I can 
upgrade/downgrade and install any specific version without trouble. There 
is only an issue when I use the Jenkins CLI

-- 
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/b26b41b5-f304-444c-a366-85abcba36e6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Programmatically check if Jenkins service is up and running

[Liora Milbaum]

My chef cookbook deploys Jenkins and few plugins. A restart is required 
after the plugins are installed.
It takes few seconds to the service coming back. Till than, no additional 
configuration can be executed on that Jenkins service.
The easiest way is to sleep for lets say 60 seconds and than continue as 
usual.
But, there must be another way to deal with it. Something like looping till 
a heartbeat is received.

Any idea how it can be implemented?

Thanks,
Liora

 

-- 
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/d80728b1-09a0-40d1-ad7a-3dbfcad74577%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Multibranch Pipeline Jenkinsfile job script not seeing Credentials

[Michael Neale]

Should the credentialsId be the horrible ugly ID in advanced in 
credentials? 

is there no error, but it just doesn't run? 

On Thursday, July 28, 2016 at 7:34:51 AM UTC+10, Francis Lalonde wrote:
>
> Hi -
>
> I am writing a Jenkinsfile script to automate the creation of pipelines 
> using the multibranch plugin. The Jenkinsfile appears at the root of a 
> github repo. Branch Indexing is working fine and the first stages (Maven 
> commands) go trough without a hitch.
>
> But then I am trying to deploy using ansible, for which I need ssh. I have 
> defined a global-scoped "secret-file" credentials, which regular jobs can 
> see and use. But my script-generated jobs do not get access to the 
> credentials.
>
> In the following sample code, the echo command never runs : 
>
> node() {
> withCredentials([[$class: 'FileBinding', credentialsId: 'secret-file', 
> variable: 'SECRET_FILE']]) {
> echo "${SECRET_FILE}"
> }
> }
>
> Moreover, using the "withCredentials" Pipeline Syntax Snippet Generator at 
> the branch job level, the combobox does not list any available credentials. 
> But doing the same thing a level above (in the multibranch job), the 
> combobox shows all global-scoped credentials, including the "secret-file" 
> which I am looking to use in my script.
>
> I don't know if this is an intentional limitation, either by design or for 
> security, that can be configured or worked around or if it is a plain bug 
> that I should file an issue for. I tried both freshly installed Windows 
> Jenkins 2.15 and an older 1.651.3 Linux Jenkins with updated plugins and 
> got the same behvaior.
>
> If anybody has a clue, this would make my week!
>
> Francis
>
>
>

-- 
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/8a247d3a-7e7a-42d2-927c-95c78d3caabf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean Alpha Plugin - HTTP error of HTTPS

[Michael Neale]

It's hard to say, it could be a quirk of proxy settings. The resources 
don't specify any absolute paths that I can tell. 

if you use chrome, can you see what resources are trying to load that way, 
and what is triggering them? inspecting the JS will help a bit. 

note that 'X-Forwarded-Proto'  should be present in the request, which 
Jenkins willi honour. I think it is the same issue as you point out in that 
link. 

Reverse proxies can be tricky - any more information you can provide about 
your setup will help. nginx has been in use by many and it doesn't have 
this issue (it does set that header). 



On Thursday, July 28, 2016 at 4:40:24 AM UTC+10, Dan QAmbox wrote:
>
> This is the issue it seems, but have no idea where to look to set the src 
> locally in the files to src=//. 
>
> On Wednesday, July 27, 2016 at 10:33:39 AM UTC-4, Dan QAmbox wrote:
>>
>> Wonder is this may be related: 
>> https://issues.jenkins-ci.org/browse/JENKINS-14223
>>
>> On Wednesday, July 27, 2016 at 9:49:43 AM UTC-4, Dan QAmbox wrote:
>>>
>>> I restarted the server after updating the url in the configs to use 
>>> https. Still getting the same error. Is still thinks that the url is http. 
>>> Is there another place I need to set the https in the configs?
>>>
>>> Sincerely
>>>
>>> On Wednesday, July 27, 2016 at 2:13:28 AM UTC-4, James Dumay wrote:

 Does bouncing your Jenkins server help? Strangely we use https on 
 blueocean.io right now and we are not seeing any issues.

 On Wednesday, July 27, 2016 at 6:24:55 AM UTC+10, Dan QAmbox wrote:
>
> I went in and updated that to be HTTPS. I saved it but still getting 
> the same error in the console when trying to go to the blue ocean url. 
>
> Any other ideas? 
>
> Thanks for the help.
>
> Sincerely,
>
> On Tuesday, July 26, 2016 at 2:25:29 PM UTC-4, Daniel Beck wrote:
>>
>> What URL is configured in Manage Jenkins » Configure Jenkins » 
>> Jenkins Location? Should be HTTPS if you access Jenkins that way. 
>>
>> > On 26.07.2016, at 17:37, Dan QAmbox  wrote: 
>> > 
>> > Hi there. 
>> > 
>> > I just installed the alpha version of the Blue Ocean plugin. I see 
>> the blue "Try Blue Ocean" button at the top of the page. However, when I 
>> try to get to the page I get an error in the console: 
>> > 
>> > Mixed Content: The page at 'https://a.b.com/blue/' was loaded over 
>> HTTPS, but requested an insecure XMLHttpRequest endpoint '
>> http://a.b.com/blue/js-extensions/'. This request has been blocked; 
>> the content must be served over HTTPS. 
>> > 
>> > Is this something I can fix locally or can someone patch it? I know 
>> its a alpha,but was hoping to at least get it to load up so I can test 
>> it 
>> out. 
>> > 
>> > 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-use...@googlegroups.com. 
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/e0dcb993-e775-4997-9090-0afb1b237829%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/9febaa44-917d-4af0-aa96-705c7dd992ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Error while running maven install

[neha tayal]

I am trying to run the scm plugin. After running maven install  it gives 
are below error 

Here is the error log
WARNING] The POM for org.jenkins-ci.tools:maven-hpi-plugin:jar:1.117 is 
missing, no dependency information available
[WARNING] Failed to build parent project for 
org.jenkins-ci.plugins:scm-anywhere:hpi:1.0-SNAPSHOT
[INFO] 

[INFO] 

[INFO] Building SCM Anywhere Plugin 1.0-SNAPSHOT
[INFO] 

[INFO] 
[INFO] --- maven-hpi-plugin:1.100:validate (default-validate) @ 
scm-anywhere ---
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:display-info (display-info) @ 
scm-anywhere ---
[INFO] Maven Version: 3.3.9
[INFO] JDK Version: 1.8.0_91 normalized as: 1.8.0-91
[INFO] OS Info: Arch: amd64 Family: dos Name: windows 7 Version: 6.1
[INFO] 
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (display-info) @ 
scm-anywhere ---
[WARNING] Rule 3: org.apache.maven.plugins.enforcer.BannedDependencies 
failed with message:
Found Banned Dependency: org.sonatype.sisu:sisu-guice:jar:noaop:2.1.7
Use 'mvn dependency:tree' to locate the source of the banned dependencies.
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 7.062 s
[INFO] Finished at: 2016-07-28T00:16:02+02:00
[INFO] Final Memory: 23M/521M
[INFO] 

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-enforcer-plugin:1.3.1:enforce (display-info) 
on project scm-anywhere: Some Enforcer rules have failed. Look above for 
specific messages explaining why the rule failed. -> [Help 1]
[ERROR] 

 Here is the pom.xml file

http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;>
4.0.0

org.jenkins-ci.plugins
plugin
2.9


org.jenkins-ci.plugins
scm-anywhere
1.0-SNAPSHOT
hpi



1.625.3

7


2.1



UTF-8
1.8
true


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



MIT License
http://opensource.org/licenses/MIT




nhgupta
zone.n...@gmail.com
zone.n...@gmail.com






org.apache.maven.plugins
maven-checkstyle-plugin

config/sun_checks.xml










maven-enforcer-plugin


display-info





org.eclipse.jgit:org.eclipse.jgit.java7








org.apache.maven.plugins
maven-site-plugin
3.5


org.apache.maven.plugins
maven-compiler-plugin
3.5.1



org.jenkins-ci.tools
maven-hpi-plugin
1.100





maven-release-plugin
2.5


org.jenkins-ci.tools
maven-hpi-plugin
1.100
true


org.apache.maven.plugins
maven-site-plugin
3.3







repo.jenkins-ci.org
http://repo.jenkins-ci.org/public/

true


false





repo.jenkins-ci.org
http://repo.jenkins-ci.org/public/

true


false








org.jenkins-ci.plugins
token-macro
1.5.1


org.jenkins-ci.plugins
credentials
2.1.3


com.github.stephenc.findbugs
findbugs-annotations
1.3.9-1


org.jenkins-ci.plugins
ssh-credentials
1.10



org.jenkins-ci.plugins
git
2.3.5
test







-- 
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/d7680c67-fa0d-4ffb-85a3-0f38943be3cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Multibranch Pipeline Jenkinsfile job script not seeing Credentials

[Francis Lalonde]

Hi -

I am writing a Jenkinsfile script to automate the creation of pipelines 
using the multibranch plugin. The Jenkinsfile appears at the root of a 
github repo. Branch Indexing is working fine and the first stages (Maven 
commands) go trough without a hitch.

But then I am trying to deploy using ansible, for which I need ssh. I have 
defined a global-scoped "secret-file" credentials, which regular jobs can 
see and use. But my script-generated jobs do not get access to the 
credentials.

In the following sample code, the echo command never runs : 

node() {
withCredentials([[$class: 'FileBinding', credentialsId: 'secret-file', 
variable: 'SECRET_FILE']]) {
echo "${SECRET_FILE}"
}
}

Moreover, using the "withCredentials" Pipeline Syntax Snippet Generator at 
the branch job level, the combobox does not list any available credentials. 
But doing the same thing a level above (in the multibranch job), the 
combobox shows all global-scoped credentials, including the "secret-file" 
which I am looking to use in my script.

I don't know if this is an intentional limitation, either by design or for 
security, that can be configured or worked around or if it is a plain bug 
that I should file an issue for. I tried both freshly installed Windows 
Jenkins 2.15 and an older 1.651.3 Linux Jenkins with updated plugins and 
got the same behvaior.

If anybody has a clue, this would make my week!

Francis


-- 
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/f7234a21-3017-408c-a4a8-8ef1d731205f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jenkins CLI, trouble installing plugin from local hpi

[James Richard]

Using Jenkins 1.642.4, I installed an older version of my plugin from a 
local hpi using the Jenkins CLI and did a safe restart.  When I try to 
install a newer version from a local hpi using the Jenkins 
CLI, http://localhost:8080/pluginManager/installed still shows the older 
version is installed even after a safe restart.

-- 
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/de5c8056-67cb-4a6b-87bd-6a980f4b3ed6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Java 8 build are failing... please help..

[Mark Waite]

http://stackoverflow.com/questions/23442621/ant-class-not-found-javac1-8 seems
to hint that the Ant version you're using may not be compatible with Java 8.

Mark Waite

On Wed, Jul 27, 2016 at 2:42 PM Prasu S  wrote:

> We are planning to migrate to Jboss 6. . I installed JDK 1.8 on our test
> server . It now has both JDK 1.7 and JDK1.8 so that Jenkins jobs can use
> either JDK1.7 or JDK 1.8 . When I compile our code with JDK 1.8, I'm
> receiving this error:  C:/Jenkins/XYZ/workspace/build.xml :116 :Class not
> found:javac1.8. Please help. 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/72a576a7-0704-4495-a8a3-5f340d513bfc%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/CAO49JtGHgsftq0DZi%3DOigZ94bRTT9jzgNjj-9-Vy3Ud1_09uZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: scm.gitTool in Jenkinsfile

[Nigel Magnay]

No, as it's not on the path so would not be found.

Oddly, if I do
scm.gitTool = 'win git'
echo scm.gitTool

it responds with 'null' - so something is odd in the field setter :-/


On Wed, Jul 27, 2016 at 9:53 PM, Mark Waite 
wrote:

> Have you tried configuring your git executable to be "git" rather than
> "/usr/bin/git"?  That's what I've used in multi-platform environments and
> it has worked well for me.
>
> Mark Waite
>
> On Wed, Jul 27, 2016 at 1:57 PM Nigel Magnay 
> wrote:
>
>> In a bitbucket-sourced multibranch repository, I need to ensure the git
>> checkout doesn't occur with /usr/bin/git, but with a tool that stands a
>> chance of executing on Windows.
>>
>> I had rather hoped it would simply be the case of doing
>>
>> scm.gitTool = 'win git';
>>
>> before my
>> checkout scm
>>
>> But it still seems to insist on using the wrong binary (even though there
>> appears to be a setter, as I had to approve it in the script console).
>>
>> What have I 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/CAPYP83SpLOHmoJBupi6Q0QV6TDjKOf9EYtbXrtj3NZ0L9f1PTg%40mail.gmail.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/CAO49JtG8AdnRuA8LX3xSgkpD7p9jepaec%2BjxmaLg7TRZLaBi8A%40mail.gmail.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/CAPYP83Qxg3RtukcGLL8Ouf43x3VpJmaUS0nr0zsZhFkM1Yr7Yg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: scm.gitTool in Jenkinsfile

[Mark Waite]

Have you tried configuring your git executable to be "git" rather than
"/usr/bin/git"?  That's what I've used in multi-platform environments and
it has worked well for me.

Mark Waite

On Wed, Jul 27, 2016 at 1:57 PM Nigel Magnay  wrote:

> In a bitbucket-sourced multibranch repository, I need to ensure the git
> checkout doesn't occur with /usr/bin/git, but with a tool that stands a
> chance of executing on Windows.
>
> I had rather hoped it would simply be the case of doing
>
> scm.gitTool = 'win git';
>
> before my
> checkout scm
>
> But it still seems to insist on using the wrong binary (even though there
> appears to be a setter, as I had to approve it in the script console).
>
> What have I 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/CAPYP83SpLOHmoJBupi6Q0QV6TDjKOf9EYtbXrtj3NZ0L9f1PTg%40mail.gmail.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/CAO49JtG8AdnRuA8LX3xSgkpD7p9jepaec%2BjxmaLg7TRZLaBi8A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Java 8 build are failing... please help..

[Prasu S]

We are planning to migrate to Jboss 6. . I installed JDK 1.8 on our test 
server . It now has both JDK 1.7 and JDK1.8 so that Jenkins jobs can use 
either JDK1.7 or JDK 1.8 . When I compile our code with JDK 1.8, I'm 
receiving this error:  C:/Jenkins/XYZ/workspace/build.xml :116 :Class not 
found:javac1.8. Please help. 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/72a576a7-0704-4495-a8a3-5f340d513bfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Scaling - executors vs slaves

[Baptiste Mathus]

Good practices to scale, IMO:
* don't build on the master
* Yes. Add agents/slaves, see below.
* Never put more than one executor per agent (slave term now deprecated).
Engineering time is far more expensive than having N agents, preventing
builds to step over each other's toes.
** We initially used static agents, running in a corporate ESX. And now
it's mostly running using a docker swarm cluster, for about 60 hours a day
and ~1000 active jobs.
* IMO directly go to two or three agents and not just one. This way you'll
maybe avoid (your users) designing builds to depend on a specific machine.
** Corollary: never use node names as labels.

My 2 cents

-- Baptiste

Le 27 juil. 2016 8:42 PM, "Bruce Epstein"  a écrit :

> Hi -
>
> I'm an experienced Jenkins user (writing Ant scripts, using plugins, etc.)
> but not an IT/administrator, and my IT dept is not that familiar with
> Jenkins scaling.
>
> If anyone can point me to a comprehensive discussion of the best way to
> scale, please provide a url.
>
> Current architecture:
>
> Only one master with just a single executor.
> All jobs are run on the master
> Running jenkins 1.652
> The load is not the heavily. We probably never have more than 2 or 3 users
> needing Jenkins at the same time, and usually it is just one.  95% of the
> time, we don't have a scale issue, so I don't want to over-engineer the
> solution.
> We have three or four development teams, and sometimes queue conflicts
> arise. We want to scale up a bit for future growth.
>
> Current problems:
> 1. Some jobs (with three or four sub-jobs) monopolize the queue for 30+
> minutes, preventing other jobs from running. One in particular is a library
> built in response to an svn change, which then triggers four other apps to
> rebuild. These are separate Jenkins jobs and yet they hog the queue
> preventing other users from running any jobs, even "in between" each app
> being rebuilt.
>
> 2. Some multiconfiguration jobs (that build, say, 30 war files), can take
> about 90 minutes to run (3 minutes per iteration). We'd like to cut that
> down, but at least they allow other jobs to run (i.e. don't monopolize the
> queue). These wars can be built in parallel (no need to run in series,
> which is the default for multiconfiguration jobs, I assume).
>
> Things I've tried:
> 1. No matter how I've tried to configure the queue-hogging job, I can't
> get it to "play nicely". Once it starts, it runs all the way through (say,
> 4 subjobs, each taking about 8 minutes). So, configuring the master to use,
> say, 2 or 3 executors seems to be one way to allow other jobs to run
> without being shut out.
>
> 2. Increasing the number of executors "works" for some use cases, but it
> also seems to cause jobs to run in parallel that I need to run in sequence.
> I'm unclear on how to prevent multiple executors from being used when I
> want one job to wait for another. Is this just how executors work? How do I
> ensure the extra executors are assigned to other jobs and not just used in
> parallel for the queue-hogging job?
>
> Possible solutions:
> 1. Add slaves?  (see below)
> 2. Use multiple executors with BuildFlow or similar plugins to prevent
> jobs being triggered to run in parallel? Even BuildFlow seems to require at
> least two executors, or it hangs up trying to launch the first subjob in
> the flow.
>
> Proposed solution:
>
> 1. Stick with only one master. Creating multiple masters seems unnecessary
> at our size.
> 2. Don't build jobs on the master...leave that to the slaves. (This seems
> to be the best practice?)
> 3. Create two slaves eventually (one is enough for now while we are still
> performing builds on master too)
> 4. Configure one slave to use only one executor. Configure the second
> slave to use multiple executors.
> 5. Configure certain jobs to run on the appropriate slave (single-executor
> or multi-executor) depending on the job's needs.
>
> 6. Should I be looking at CloudBees or plugins like EC2, Heavy Job, or
> One-Shot Executor?
>
>
> I need someone who has "been there, done that" to give me a reality check
> or alert me to any blindspots before I ask IT to acquire more hardware and
> configure it. I want to have some confidence this will solve the problem
> without being overkill.
>
>
> Any insights appreciated.
>
>
> In gratitude, I'm happy to answer any Flex questions. :-)
>
>
> Thanks,
>
> Bruce
>
>
> --
> 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/3a038f29-5221-4830-80ae-ca5a70c7ccc7%40googlegroups.com
> 
> .
> For more options, visit 

RE: Scaling - executors vs slaves

[John Mellor]

The system load associated with any given build varies extremely widely, so I 
do not think that it is possible to provide guidelines for how many executors 
to configure.  Some jobs just do a lot of disk i/o, while other use all 
possible processor threads to build (e.g: make –j steps).  It may be possible 
to build some scheduling heuristics that would put the appropriate jobs on the 
various slave machines, but it would be insanely complicated and error-prone.

I stopped worrying about it, and just set the number of executors on each 
machine to one.  Nothing runs on the master, as it is busy enough with its 
normal task load.  If that is not efficient, so what?  Hardware is cheap in 
comparison – especially VMs and containerized slaves.  Use something like 
Kubernetes if you want to manage the total Jenkins load on the cluster and spin 
up more slaves as required.

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Bruce Epstein
Sent: July-27-16 14:43
To: Jenkins Users
Subject: Scaling - executors vs slaves

Hi -

I'm an experienced Jenkins user (writing Ant scripts, using plugins, etc.) but 
not an IT/administrator, and my IT dept is not that familiar with Jenkins 
scaling.

If anyone can point me to a comprehensive discussion of the best way to scale, 
please provide a url.

Current architecture:

Only one master with just a single executor.
All jobs are run on the master
Running jenkins 1.652
The load is not the heavily. We probably never have more than 2 or 3 users 
needing Jenkins at the same time, and usually it is just one.  95% of the time, 
we don't have a scale issue, so I don't want to over-engineer the solution.
We have three or four development teams, and sometimes queue conflicts arise. 
We want to scale up a bit for future growth.

Current problems:
1. Some jobs (with three or four sub-jobs) monopolize the queue for 30+ 
minutes, preventing other jobs from running. One in particular is a library 
built in response to an svn change, which then triggers four other apps to 
rebuild. These are separate Jenkins jobs and yet they hog the queue preventing 
other users from running any jobs, even "in between" each app being rebuilt.

2. Some multiconfiguration jobs (that build, say, 30 war files), can take about 
90 minutes to run (3 minutes per iteration). We'd like to cut that down, but at 
least they allow other jobs to run (i.e. don't monopolize the queue). These 
wars can be built in parallel (no need to run in series, which is the default 
for multiconfiguration jobs, I assume).

Things I've tried:
1. No matter how I've tried to configure the queue-hogging job, I can't get it 
to "play nicely". Once it starts, it runs all the way through (say, 4 subjobs, 
each taking about 8 minutes). So, configuring the master to use, say, 2 or 3 
executors seems to be one way to allow other jobs to run without being shut out.

2. Increasing the number of executors "works" for some use cases, but it also 
seems to cause jobs to run in parallel that I need to run in sequence. I'm 
unclear on how to prevent multiple executors from being used when I want one 
job to wait for another. Is this just how executors work? How do I ensure the 
extra executors are assigned to other jobs and not just used in parallel for 
the queue-hogging job?

Possible solutions:
1. Add slaves?  (see below)
2. Use multiple executors with BuildFlow or similar plugins to prevent jobs 
being triggered to run in parallel? Even BuildFlow seems to require at least 
two executors, or it hangs up trying to launch the first subjob in the flow.

Proposed solution:

1. Stick with only one master. Creating multiple masters seems unnecessary at 
our size.
2. Don't build jobs on the master...leave that to the slaves. (This seems to be 
the best practice?)
3. Create two slaves eventually (one is enough for now while we are still 
performing builds on master too)
4. Configure one slave to use only one executor. Configure the second slave to 
use multiple executors.
5. Configure certain jobs to run on the appropriate slave (single-executor or 
multi-executor) depending on the job's needs.

6. Should I be looking at CloudBees or plugins like EC2, Heavy Job, or One-Shot 
Executor?



I need someone who has "been there, done that" to give me a reality check or 
alert me to any blindspots before I ask IT to acquire more hardware and 
configure it. I want to have some confidence this will solve the problem 
without being overkill.



Any insights appreciated.



In gratitude, I'm happy to answer any Flex questions. :-)



Thanks,

Bruce

--
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 

Re: Scaling - executors vs slaves

[Stephen Connolly]

You really want a few build agents.

FTR you are not even close to scaling limits... I'm giving a talk on how to
scale Jenkins at this years Jenkins World... I don't want to spoil the fun
of that talk so I'm not giving out details, but if you cannot get to
Jenkins World it will be available on-line... And hopefully it will be a
good talk with interesting things for everyone no matter how big or small
their Jenkins is.

On Wednesday 27 July 2016, Bruce Epstein  wrote:

> Hi -
>
> I'm an experienced Jenkins user (writing Ant scripts, using plugins, etc.)
> but not an IT/administrator, and my IT dept is not that familiar with
> Jenkins scaling.
>
> If anyone can point me to a comprehensive discussion of the best way to
> scale, please provide a url.
>
> Current architecture:
>
> Only one master with just a single executor.
> All jobs are run on the master
> Running jenkins 1.652
> The load is not the heavily. We probably never have more than 2 or 3 users
> needing Jenkins at the same time, and usually it is just one.  95% of the
> time, we don't have a scale issue, so I don't want to over-engineer the
> solution.
> We have three or four development teams, and sometimes queue conflicts
> arise. We want to scale up a bit for future growth.
>
> Current problems:
> 1. Some jobs (with three or four sub-jobs) monopolize the queue for 30+
> minutes, preventing other jobs from running. One in particular is a library
> built in response to an svn change, which then triggers four other apps to
> rebuild. These are separate Jenkins jobs and yet they hog the queue
> preventing other users from running any jobs, even "in between" each app
> being rebuilt.
>
> 2. Some multiconfiguration jobs (that build, say, 30 war files), can take
> about 90 minutes to run (3 minutes per iteration). We'd like to cut that
> down, but at least they allow other jobs to run (i.e. don't monopolize the
> queue). These wars can be built in parallel (no need to run in series,
> which is the default for multiconfiguration jobs, I assume).
>
> Things I've tried:
> 1. No matter how I've tried to configure the queue-hogging job, I can't
> get it to "play nicely". Once it starts, it runs all the way through (say,
> 4 subjobs, each taking about 8 minutes). So, configuring the master to use,
> say, 2 or 3 executors seems to be one way to allow other jobs to run
> without being shut out.
>
> 2. Increasing the number of executors "works" for some use cases, but it
> also seems to cause jobs to run in parallel that I need to run in sequence.
> I'm unclear on how to prevent multiple executors from being used when I
> want one job to wait for another. Is this just how executors work? How do I
> ensure the extra executors are assigned to other jobs and not just used in
> parallel for the queue-hogging job?
>
> Possible solutions:
> 1. Add slaves?  (see below)
> 2. Use multiple executors with BuildFlow or similar plugins to prevent
> jobs being triggered to run in parallel? Even BuildFlow seems to require at
> least two executors, or it hangs up trying to launch the first subjob in
> the flow.
>
> Proposed solution:
>
> 1. Stick with only one master. Creating multiple masters seems unnecessary
> at our size.
> 2. Don't build jobs on the master...leave that to the slaves. (This seems
> to be the best practice?)
> 3. Create two slaves eventually (one is enough for now while we are still
> performing builds on master too)
> 4. Configure one slave to use only one executor. Configure the second
> slave to use multiple executors.
> 5. Configure certain jobs to run on the appropriate slave (single-executor
> or multi-executor) depending on the job's needs.
>
> 6. Should I be looking at CloudBees or plugins like EC2, Heavy Job, or
> One-Shot Executor?
>
>
> I need someone who has "been there, done that" to give me a reality check
> or alert me to any blindspots before I ask IT to acquire more hardware and
> configure it. I want to have some confidence this will solve the problem
> without being overkill.
>
>
> Any insights appreciated.
>
>
> In gratitude, I'm happy to answer any Flex questions. :-)
>
>
> Thanks,
>
> Bruce
>
>
> --
> 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/3a038f29-5221-4830-80ae-ca5a70c7ccc7%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Sent from my phone

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from 

scm.gitTool in Jenkinsfile

[Nigel Magnay]

In a bitbucket-sourced multibranch repository, I need to ensure the git
checkout doesn't occur with /usr/bin/git, but with a tool that stands a
chance of executing on Windows.

I had rather hoped it would simply be the case of doing

scm.gitTool = 'win git';

before my
checkout scm

But it still seems to insist on using the wrong binary (even though there
appears to be a setter, as I had to approve it in the script console).

What have I 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/CAPYP83SpLOHmoJBupi6Q0QV6TDjKOf9EYtbXrtj3NZ0L9f1PTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

RE: Scaling - executors vs slaves

[Jackson, Randy]

Bruce,

If you need to expand the number of executors on your master and prevent the 
jobs  you need to run in sequence from running in parallel, I would look into 
using the Parameterized Trigger Plugin.  You can create a control job to fire 
off the jobs you want to run one after the other by adding a trigger build step 
for each of the jobs and selecting the “Block until the triggered projects 
finish their builds” option.  Now the control job will hog one of the executors 
while each of the triggered jobs is running, so you will need 2 executors to 
run your sequence of jobs.  We have 10 executors open even though we don’t run 
many jobs and don’t run into any problems.

Hope that helps.

Randy Jackson
Software Build Engineer
Indiana Farm Bureau Insurance



From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Bruce Epstein
Sent: Wednesday, July 27, 2016 2:43 PM
To: Jenkins Users
Subject: Scaling - executors vs slaves

Hi -

I'm an experienced Jenkins user (writing Ant scripts, using plugins, etc.) but 
not an IT/administrator, and my IT dept is not that familiar with Jenkins 
scaling.

If anyone can point me to a comprehensive discussion of the best way to scale, 
please provide a url.

Current architecture:

Only one master with just a single executor.
All jobs are run on the master
Running jenkins 1.652
The load is not the heavily. We probably never have more than 2 or 3 users 
needing Jenkins at the same time, and usually it is just one.  95% of the time, 
we don't have a scale issue, so I don't want to over-engineer the solution.
We have three or four development teams, and sometimes queue conflicts arise. 
We want to scale up a bit for future growth.

Current problems:
1. Some jobs (with three or four sub-jobs) monopolize the queue for 30+ 
minutes, preventing other jobs from running. One in particular is a library 
built in response to an svn change, which then triggers four other apps to 
rebuild. These are separate Jenkins jobs and yet they hog the queue preventing 
other users from running any jobs, even "in between" each app being rebuilt.

2. Some multiconfiguration jobs (that build, say, 30 war files), can take about 
90 minutes to run (3 minutes per iteration). We'd like to cut that down, but at 
least they allow other jobs to run (i.e. don't monopolize the queue). These 
wars can be built in parallel (no need to run in series, which is the default 
for multiconfiguration jobs, I assume).

Things I've tried:
1. No matter how I've tried to configure the queue-hogging job, I can't get it 
to "play nicely". Once it starts, it runs all the way through (say, 4 subjobs, 
each taking about 8 minutes). So, configuring the master to use, say, 2 or 3 
executors seems to be one way to allow other jobs to run without being shut out.

2. Increasing the number of executors "works" for some use cases, but it also 
seems to cause jobs to run in parallel that I need to run in sequence. I'm 
unclear on how to prevent multiple executors from being used when I want one 
job to wait for another. Is this just how executors work? How do I ensure the 
extra executors are assigned to other jobs and not just used in parallel for 
the queue-hogging job?

Possible solutions:
1. Add slaves?  (see below)
2. Use multiple executors with BuildFlow or similar plugins to prevent jobs 
being triggered to run in parallel? Even BuildFlow seems to require at least 
two executors, or it hangs up trying to launch the first subjob in the flow.

Proposed solution:

1. Stick with only one master. Creating multiple masters seems unnecessary at 
our size.
2. Don't build jobs on the master...leave that to the slaves. (This seems to be 
the best practice?)
3. Create two slaves eventually (one is enough for now while we are still 
performing builds on master too)
4. Configure one slave to use only one executor. Configure the second slave to 
use multiple executors.
5. Configure certain jobs to run on the appropriate slave (single-executor or 
multi-executor) depending on the job's needs.

6. Should I be looking at CloudBees or plugins like EC2, Heavy Job, or One-Shot 
Executor?



I need someone who has "been there, done that" to give me a reality check or 
alert me to any blindspots before I ask IT to acquire more hardware and 
configure it. I want to have some confidence this will solve the problem 
without being overkill.



Any insights appreciated.



In gratitude, I'm happy to answer any Flex questions. :-)



Thanks,

Bruce

--
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 

Scaling - executors vs slaves

[Bruce Epstein]

Hi - 

I'm an experienced Jenkins user (writing Ant scripts, using plugins, etc.) 
but not an IT/administrator, and my IT dept is not that familiar with 
Jenkins scaling.

If anyone can point me to a comprehensive discussion of the best way to 
scale, please provide a url.

Current architecture:

Only one master with just a single executor.
All jobs are run on the master
Running jenkins 1.652
The load is not the heavily. We probably never have more than 2 or 3 users 
needing Jenkins at the same time, and usually it is just one.  95% of the 
time, we don't have a scale issue, so I don't want to over-engineer the 
solution.
We have three or four development teams, and sometimes queue conflicts 
arise. We want to scale up a bit for future growth.

Current problems:
1. Some jobs (with three or four sub-jobs) monopolize the queue for 30+ 
minutes, preventing other jobs from running. One in particular is a library 
built in response to an svn change, which then triggers four other apps to 
rebuild. These are separate Jenkins jobs and yet they hog the queue 
preventing other users from running any jobs, even "in between" each app 
being rebuilt.

2. Some multiconfiguration jobs (that build, say, 30 war files), can take 
about 90 minutes to run (3 minutes per iteration). We'd like to cut that 
down, but at least they allow other jobs to run (i.e. don't monopolize the 
queue). These wars can be built in parallel (no need to run in series, 
which is the default for multiconfiguration jobs, I assume).

Things I've tried:
1. No matter how I've tried to configure the queue-hogging job, I can't get 
it to "play nicely". Once it starts, it runs all the way through (say, 4 
subjobs, each taking about 8 minutes). So, configuring the master to use, 
say, 2 or 3 executors seems to be one way to allow other jobs to run 
without being shut out.

2. Increasing the number of executors "works" for some use cases, but it 
also seems to cause jobs to run in parallel that I need to run in sequence. 
I'm unclear on how to prevent multiple executors from being used when I 
want one job to wait for another. Is this just how executors work? How do I 
ensure the extra executors are assigned to other jobs and not just used in 
parallel for the queue-hogging job?

Possible solutions:
1. Add slaves?  (see below)
2. Use multiple executors with BuildFlow or similar plugins to prevent jobs 
being triggered to run in parallel? Even BuildFlow seems to require at 
least two executors, or it hangs up trying to launch the first subjob in 
the flow.

Proposed solution:

1. Stick with only one master. Creating multiple masters seems unnecessary 
at our size.
2. Don't build jobs on the master...leave that to the slaves. (This seems 
to be the best practice?)
3. Create two slaves eventually (one is enough for now while we are still 
performing builds on master too)
4. Configure one slave to use only one executor. Configure the second slave 
to use multiple executors.
5. Configure certain jobs to run on the appropriate slave (single-executor 
or multi-executor) depending on the job's needs.

6. Should I be looking at CloudBees or plugins like EC2, Heavy Job, or 
One-Shot Executor?


I need someone who has "been there, done that" to give me a reality check 
or alert me to any blindspots before I ask IT to acquire more hardware and 
configure it. I want to have some confidence this will solve the problem 
without being overkill.


Any insights appreciated. 


In gratitude, I'm happy to answer any Flex questions. :-)


Thanks,

Bruce


-- 
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/3a038f29-5221-4830-80ae-ca5a70c7ccc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean Alpha Plugin - HTTP error of HTTPS

[Dan QAmbox]

Sorry forgot 
link: 
http://stackoverflow.com/questions/18251128/why-am-i-suddenly-getting-a-blocked-loading-mixed-active-content-issue-in-fire

On Wednesday, July 27, 2016 at 2:40:24 PM UTC-4, Dan QAmbox wrote:
>
> This is the issue it seems, but have no idea where to look to set the src 
> locally in the files to src=//. 
>
> On Wednesday, July 27, 2016 at 10:33:39 AM UTC-4, Dan QAmbox wrote:
>>
>> Wonder is this may be related: 
>> https://issues.jenkins-ci.org/browse/JENKINS-14223
>>
>> On Wednesday, July 27, 2016 at 9:49:43 AM UTC-4, Dan QAmbox wrote:
>>>
>>> I restarted the server after updating the url in the configs to use 
>>> https. Still getting the same error. Is still thinks that the url is http. 
>>> Is there another place I need to set the https in the configs?
>>>
>>> Sincerely
>>>
>>> On Wednesday, July 27, 2016 at 2:13:28 AM UTC-4, James Dumay wrote:

 Does bouncing your Jenkins server help? Strangely we use https on 
 blueocean.io right now and we are not seeing any issues.

 On Wednesday, July 27, 2016 at 6:24:55 AM UTC+10, Dan QAmbox wrote:
>
> I went in and updated that to be HTTPS. I saved it but still getting 
> the same error in the console when trying to go to the blue ocean url. 
>
> Any other ideas? 
>
> Thanks for the help.
>
> Sincerely,
>
> On Tuesday, July 26, 2016 at 2:25:29 PM UTC-4, Daniel Beck wrote:
>>
>> What URL is configured in Manage Jenkins » Configure Jenkins » 
>> Jenkins Location? Should be HTTPS if you access Jenkins that way. 
>>
>> > On 26.07.2016, at 17:37, Dan QAmbox  wrote: 
>> > 
>> > Hi there. 
>> > 
>> > I just installed the alpha version of the Blue Ocean plugin. I see 
>> the blue "Try Blue Ocean" button at the top of the page. However, when I 
>> try to get to the page I get an error in the console: 
>> > 
>> > Mixed Content: The page at 'https://a.b.com/blue/' was loaded over 
>> HTTPS, but requested an insecure XMLHttpRequest endpoint '
>> http://a.b.com/blue/js-extensions/'. This request has been blocked; 
>> the content must be served over HTTPS. 
>> > 
>> > Is this something I can fix locally or can someone patch it? I know 
>> its a alpha,but was hoping to at least get it to load up so I can test 
>> it 
>> out. 
>> > 
>> > 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-use...@googlegroups.com. 
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/e0dcb993-e775-4997-9090-0afb1b237829%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/dbf7a05c-811b-4f47-909f-03dd8d61edfd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean Alpha Plugin - HTTP error of HTTPS

[Dan QAmbox]

This is the issue it seems, but have no idea where to look to set the src 
locally in the files to src=//. 

On Wednesday, July 27, 2016 at 10:33:39 AM UTC-4, Dan QAmbox wrote:
>
> Wonder is this may be related: 
> https://issues.jenkins-ci.org/browse/JENKINS-14223
>
> On Wednesday, July 27, 2016 at 9:49:43 AM UTC-4, Dan QAmbox wrote:
>>
>> I restarted the server after updating the url in the configs to use 
>> https. Still getting the same error. Is still thinks that the url is http. 
>> Is there another place I need to set the https in the configs?
>>
>> Sincerely
>>
>> On Wednesday, July 27, 2016 at 2:13:28 AM UTC-4, James Dumay wrote:
>>>
>>> Does bouncing your Jenkins server help? Strangely we use https on 
>>> blueocean.io right now and we are not seeing any issues.
>>>
>>> On Wednesday, July 27, 2016 at 6:24:55 AM UTC+10, Dan QAmbox wrote:

 I went in and updated that to be HTTPS. I saved it but still getting 
 the same error in the console when trying to go to the blue ocean url. 

 Any other ideas? 

 Thanks for the help.

 Sincerely,

 On Tuesday, July 26, 2016 at 2:25:29 PM UTC-4, Daniel Beck wrote:
>
> What URL is configured in Manage Jenkins » Configure Jenkins » Jenkins 
> Location? Should be HTTPS if you access Jenkins that way. 
>
> > On 26.07.2016, at 17:37, Dan QAmbox  wrote: 
> > 
> > Hi there. 
> > 
> > I just installed the alpha version of the Blue Ocean plugin. I see 
> the blue "Try Blue Ocean" button at the top of the page. However, when I 
> try to get to the page I get an error in the console: 
> > 
> > Mixed Content: The page at 'https://a.b.com/blue/' was loaded over 
> HTTPS, but requested an insecure XMLHttpRequest endpoint '
> http://a.b.com/blue/js-extensions/'. This request has been blocked; 
> the content must be served over HTTPS. 
> > 
> > Is this something I can fix locally or can someone patch it? I know 
> its a alpha,but was hoping to at least get it to load up so I can test it 
> out. 
> > 
> > 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-use...@googlegroups.com. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/e0dcb993-e775-4997-9090-0afb1b237829%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/5a598ff7-6657-423c-aa59-714cd6d0bd80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: accounts.jenkins.io problems not able to reset password or sign up

[Narahari 'n' Savitha]

Thank You Sir.  I was able to reset the password now.

Appreciate your help.

Regards,
-Narahari

On Tuesday, July 26, 2016 at 9:41:36 PM UTC-4, Narahari 'n' Savitha wrote:
>
> Hello:
> I tried to reset the password on the accounts.jenkins.io site and here is 
> what I see.
>
> *HTTP ERROR 500*
>
> Problem accessing /doPasswordReset. Reason:
>
> Server Error
>
>
> *Caused by:*
>
> javax.servlet.ServletException: javax.naming.NamingException: [LDAP: error 
> code 28 - entry update failed]; remaining name 
> 'cn=savithari,ou=people,dc=jenkins-ci,dc=org'
>
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
>
> 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:790)
>
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:837)
>
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)
>
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>
> at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>
> at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174)
>
> at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
>
>
> Even if I try to signup I get the same
>
>
> *HTTP ERROR 500*
>
> Problem accessing /doSignup. Reason:
>
> Server Error
>
>
> *Caused by:*
>
> javax.servlet.ServletException: javax.naming.NamingException: [LDAP: error 
> code 80 - Other]; remaining name 
> 'cn=narahari,ou=people,dc=jenkins-ci,dc=org'
>
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
>
> 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:790)
>
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:837)
>
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)
>
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>
> at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
>
> at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
>
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174)
>
> at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
>
> at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
>
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106)
>
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
>
> at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
>
> at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
>
> at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
>
> at org.eclipse.jetty.server.Server.handle(Server.java:524)
>
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319)
>
>
> Can I get some help please ?
>
>
> -Narahari
>

-- 
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/e33fcbff-786d-46f5-967f-3d6c38f72cef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to set request header size for jetty

[Mohammed Zahriya]

HI Andreas,

were you able to resolve this issue? We have Jenkins installed on Linux 
using the RPM and need to increase the header size to get our SSO 
operational. What configuration file and parameter did you update to 
resolve the issue?

Error Currently encountered:

org.eclipse.jetty.util.log.JavaUtilLog warn

WARNING: Header is too large >8192


On Wednesday, November 11, 2015 at 6:41:12 AM UTC-8, Andreas Müller wrote:

> Hi,
>
> the Jetty as bundled with jenkins cannot deal with headers larger than 
> 8kB, but Jetty
> can be configured to deal with larger headers, there is a 
> setRequestHeaderSize() method
> to the org.eclipse.jetty.server.HttpConfiguration class for this purpose. 
> But what is the
> accepted method to configure this for the Jetty in jenkins.war?
>
> Best regards
>
> Andreas Müller
>
>
>

-- 
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/6920b963-3f24-4b20-b640-f3cff888f12e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Log Parser and Reporting tool

[Bubunia Patra]

Hi all,
I was looking for a jenkins plugin that can parse the jenkins console 
logs after all the tests are run and put a report something as follows:

TestName : Status(Fail/Pass) : Error Message: LogPath (html link for 
testcaselog) format so that I can access the log by clicking on the html 
link for detailed analysis.

I have found some log management tools like graylogs/parser console/log 
parser etc which does different things . But I am confused which one to 
use. Can someone throw some light on it which one will serve my purpose?

Regards
Pradeep


-- 
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/44a1ce95-3e72-4364-9cd6-621e854b3534%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Share same jenkins home directory across multiple jenkins master in AWS environment

[vivek . dhrhel]

Hi Guys, 

I am trying to share same home directory across multiple jenkins master in 
AWS environment using ELB ( Load balancer ) & EFS ( NFS server ) to keep 
the jenkins home in sync & share the load across multiple masters . 

Sometime i get an error like you have shared a home directory across 
multiple instances . I understand that it doesn't support that but is there 
any way to make this possible ?

Jobs get created inside the home folder but only shows up on the instance 
we created the job using UI even the home is synced & contains that job on 
both instances . 

Is there any way to fix this issue ? If not then what could be the best way 
to use jenkins in autoscaling environment with same home directory since i 
don't want different jobs on the masters ? 
If this is not the right place to post this issue, please guide me . 


-- 
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/2b0b5eeb-da3a-46f5-a75d-0fc08bd5a227%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: accounts.jenkins.io problems not able to reset password or sign up

[R. Tyler Croy]

(replies inline)

On Tue, 26 Jul 2016, Narahari 'n' Savitha wrote:

> Hello:
> I tried to reset the password on the accounts.jenkins.io site and here is 
> what I see.


Please try again an issue behind the scenes was preventing the LDAP operations
from completing.


> 
> *HTTP ERROR 500*
> 
> Problem accessing /doPasswordReset. Reason:
> 
> Server Error
> 
> 
> *Caused by:*
> 
> javax.servlet.ServletException: javax.naming.NamingException: [LDAP: error 
> code 28 - entry update failed]; remaining name 
> 'cn=savithari,ou=people,dc=jenkins-ci,dc=org'
> 
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
> 
> 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:790)
> 
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:837)
> 
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)
> 
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> 
> at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
> 
> at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> 
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174)
> 
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
> 
> 
> Even if I try to signup I get the same
> 
> 
> *HTTP ERROR 500*
> 
> Problem accessing /doSignup. Reason:
> 
> Server Error
> 
> 
> *Caused by:*
> 
> javax.servlet.ServletException: javax.naming.NamingException: [LDAP: error 
> code 80 - Other]; remaining name 
> 'cn=narahari,ou=people,dc=jenkins-ci,dc=org'
> 
> at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
> 
> 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:790)
> 
> at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:837)
> 
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:583)
> 
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
> 
> at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
> 
> at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:226)
> 
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1174)
> 
> at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:511)
> 
> at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:185)
> 
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1106)
> 
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
> 
> at 
> org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:213)
> 
> at 
> org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:119)
> 
> at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:134)
> 
> at org.eclipse.jetty.server.Server.handle(Server.java:524)
> 
> at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:319)
> 
> 
> Can I get some help please ?
> 
> 
> -Narahari
> 
> -- 
> 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/a81fff6d-8353-443d-99e8-8b472529775c%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.


- R. Tyler Croy

--
 Code: 
  Chatter: 

  % gpg --keyserver keys.gnupg.net --recv-key 3F51E16F
--

-- 
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/20160727144242.GX22427%40blackberry.coupleofllamas.com.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: Blue Ocean Alpha Plugin - HTTP error of HTTPS

[Dan QAmbox]

Wonder is this may be 
related: https://issues.jenkins-ci.org/browse/JENKINS-14223

On Wednesday, July 27, 2016 at 9:49:43 AM UTC-4, Dan QAmbox wrote:
>
> I restarted the server after updating the url in the configs to use https. 
> Still getting the same error. Is still thinks that the url is http. Is 
> there another place I need to set the https in the configs?
>
> Sincerely
>
> On Wednesday, July 27, 2016 at 2:13:28 AM UTC-4, James Dumay wrote:
>>
>> Does bouncing your Jenkins server help? Strangely we use https on 
>> blueocean.io right now and we are not seeing any issues.
>>
>> On Wednesday, July 27, 2016 at 6:24:55 AM UTC+10, Dan QAmbox wrote:
>>>
>>> I went in and updated that to be HTTPS. I saved it but still getting the 
>>> same error in the console when trying to go to the blue ocean url. 
>>>
>>> Any other ideas? 
>>>
>>> Thanks for the help.
>>>
>>> Sincerely,
>>>
>>> On Tuesday, July 26, 2016 at 2:25:29 PM UTC-4, Daniel Beck wrote:

 What URL is configured in Manage Jenkins » Configure Jenkins » Jenkins 
 Location? Should be HTTPS if you access Jenkins that way. 

 > On 26.07.2016, at 17:37, Dan QAmbox  wrote: 
 > 
 > Hi there. 
 > 
 > I just installed the alpha version of the Blue Ocean plugin. I see 
 the blue "Try Blue Ocean" button at the top of the page. However, when I 
 try to get to the page I get an error in the console: 
 > 
 > Mixed Content: The page at 'https://a.b.com/blue/' was loaded over 
 HTTPS, but requested an insecure XMLHttpRequest endpoint '
 http://a.b.com/blue/js-extensions/'. This request has been blocked; 
 the content must be served over HTTPS. 
 > 
 > Is this something I can fix locally or can someone patch it? I know 
 its a alpha,but was hoping to at least get it to load up so I can test it 
 out. 
 > 
 > 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-use...@googlegroups.com. 
 > To view this discussion on the web visit 
 https://groups.google.com/d/msgid/jenkinsci-users/e0dcb993-e775-4997-9090-0afb1b237829%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/84c71612-5f77-48e7-b475-4482c60a1d09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Urgent Req : for Core Java Developer's with Web Services Mclean VA Fulltime

[lucky samudrala]

HI  Professional

This is  Manish from Agile Enterprise solutions

This is in reference to the following position.



* Please find below job description if you feel comfortable please
revert with updated resume, Rate and contact details ASAP *



*Title : **Core Java Developer*

*Start  date : Fulltime *

*Client : **Hexaware / Freddie Mac*

*Location : Mclean VA*



*US Citizen / Green Card / H1 transfer is also fine*



Required:

*Strong in HTML, CSS, Hibernate, Web services*



Thanks for your time and Consideration..





Thanks & Regards



*Manish Samudrala*

Ph: 972-427-1825

Agile Enterprise Solutions Inc || "Ensuring Client's Success"||

Email: manish_samudr...@aesinc.us.com  || www.aesinc.us.com

*Note*: If you have received this mail in error or prefer not to receive
such emails in the future, please reply with "REMOVE" in the subject line
and the email id(s) to be removed. All removal requests will be honored
ASAP. We sincerely apologize for any inconvenience caused

-- 
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/CAEi14v2UXixBMivJSpBjykXt4rotHFinmOze4fpVqQw72epheQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean Alpha Plugin - HTTP error of HTTPS

[Dan QAmbox]

I restarted the server after updating the url in the configs to use https. 
Still getting the same error. Is still thinks that the url is http. Is 
there another place I need to set the https in the configs?

Sincerely

On Wednesday, July 27, 2016 at 2:13:28 AM UTC-4, James Dumay wrote:
>
> Does bouncing your Jenkins server help? Strangely we use https on 
> blueocean.io right now and we are not seeing any issues.
>
> On Wednesday, July 27, 2016 at 6:24:55 AM UTC+10, Dan QAmbox wrote:
>>
>> I went in and updated that to be HTTPS. I saved it but still getting the 
>> same error in the console when trying to go to the blue ocean url. 
>>
>> Any other ideas? 
>>
>> Thanks for the help.
>>
>> Sincerely,
>>
>> On Tuesday, July 26, 2016 at 2:25:29 PM UTC-4, Daniel Beck wrote:
>>>
>>> What URL is configured in Manage Jenkins » Configure Jenkins » Jenkins 
>>> Location? Should be HTTPS if you access Jenkins that way. 
>>>
>>> > On 26.07.2016, at 17:37, Dan QAmbox  wrote: 
>>> > 
>>> > Hi there. 
>>> > 
>>> > I just installed the alpha version of the Blue Ocean plugin. I see the 
>>> blue "Try Blue Ocean" button at the top of the page. However, when I try to 
>>> get to the page I get an error in the console: 
>>> > 
>>> > Mixed Content: The page at 'https://a.b.com/blue/' was loaded over 
>>> HTTPS, but requested an insecure XMLHttpRequest endpoint '
>>> http://a.b.com/blue/js-extensions/'. This request has been blocked; the 
>>> content must be served over HTTPS. 
>>> > 
>>> > Is this something I can fix locally or can someone patch it? I know 
>>> its a alpha,but was hoping to at least get it to load up so I can test it 
>>> out. 
>>> > 
>>> > 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-use...@googlegroups.com. 
>>> > To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/jenkinsci-users/e0dcb993-e775-4997-9090-0afb1b237829%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/5481c148-e72c-4870-888e-1c05d6faa0bc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Pipeline: parallel and produced artifacts

[Manuel Vacelet]

Hi there,

I'm using Jenkins 2.7.1 with Pipeline 2.2.
My Jenkinsfile uses parallel to execute 2 type of tests but I don't have an 
aggregation of test results. I only get one of them:

stage "Test"
parallel 'rest-c6-php53-httpd22-mysql51': {
node('docker') {
checkout scm
sh "docker run --rm -v "+pwd()+":/usr/share/tuleap -v 
"+pwd()+":/output enalean/tuleap-test-rest:c6-php53-httpd22-mysql51"
step([$class: 'JUnitResultArchiver', testResults: 
'rest_tests.xml'])
}
}, 'rest-c6-php56-httpd24-mysql56': {
node('docker') {
checkout scm
sh "docker run --rm -v "+pwd()+":/usr/share/tuleap -v 
"+pwd()+":/output enalean/tuleap-test-rest:c6-php56-httpd24-mysql56"
step([$class: 'JUnitResultArchiver', testResults: 'rest_tests.xml'])
}
}

In the test result I only get 254 tests, whereas it's actually 512 tests 
that are executed (254 in each node).

Is that expected ?

Note: if I rename on of the junit files (rest_test.xml) I can see the 512 
tests.

-- 
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/b5663092-833a-4bbd-9432-695b4832f70f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Deployment

[Raghu Goud]

Hi , 
Iam new to jenkins ,i have checkout code form svn and generate build ear . 
please help me to deploy ear file from one server to another remote server. 
Let me know the steps...

-- 
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/3f757844-f9ed-4389-90eb-23623f4cbfd1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean Alpha Plugin - HTTP error of HTTPS

[James Dumay]

Does bouncing your Jenkins server help? Strangely we use https on 
blueocean.io right now and we are not seeing any issues.

On Wednesday, July 27, 2016 at 6:24:55 AM UTC+10, Dan QAmbox wrote:
>
> I went in and updated that to be HTTPS. I saved it but still getting the 
> same error in the console when trying to go to the blue ocean url. 
>
> Any other ideas? 
>
> Thanks for the help.
>
> Sincerely,
>
> On Tuesday, July 26, 2016 at 2:25:29 PM UTC-4, Daniel Beck wrote:
>>
>> What URL is configured in Manage Jenkins » Configure Jenkins » Jenkins 
>> Location? Should be HTTPS if you access Jenkins that way. 
>>
>> > On 26.07.2016, at 17:37, Dan QAmbox  wrote: 
>> > 
>> > Hi there. 
>> > 
>> > I just installed the alpha version of the Blue Ocean plugin. I see the 
>> blue "Try Blue Ocean" button at the top of the page. However, when I try to 
>> get to the page I get an error in the console: 
>> > 
>> > Mixed Content: The page at 'https://a.b.com/blue/' was loaded over 
>> HTTPS, but requested an insecure XMLHttpRequest endpoint '
>> http://a.b.com/blue/js-extensions/'. This request has been blocked; the 
>> content must be served over HTTPS. 
>> > 
>> > Is this something I can fix locally or can someone patch it? I know its 
>> a alpha,but was hoping to at least get it to load up so I can test it out. 
>> > 
>> > 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-use...@googlegroups.com. 
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/e0dcb993-e775-4997-9090-0afb1b237829%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/ee4ac002-e6aa-4d20-a0b9-0be8355582cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean Alpha Plugin - HTTP error of HTTPS

[Michael Neale]

This is odd, others use https and haven't seen this... the blue ocean url 
has https in it? 

On Wednesday, July 27, 2016 at 6:24:55 AM UTC+10, Dan QAmbox wrote:
>
> I went in and updated that to be HTTPS. I saved it but still getting the 
> same error in the console when trying to go to the blue ocean url. 
>
> Any other ideas? 
>
> Thanks for the help.
>
> Sincerely,
>
> On Tuesday, July 26, 2016 at 2:25:29 PM UTC-4, Daniel Beck wrote:
>>
>> What URL is configured in Manage Jenkins » Configure Jenkins » Jenkins 
>> Location? Should be HTTPS if you access Jenkins that way. 
>>
>> > On 26.07.2016, at 17:37, Dan QAmbox  wrote: 
>> > 
>> > Hi there. 
>> > 
>> > I just installed the alpha version of the Blue Ocean plugin. I see the 
>> blue "Try Blue Ocean" button at the top of the page. However, when I try to 
>> get to the page I get an error in the console: 
>> > 
>> > Mixed Content: The page at 'https://a.b.com/blue/' was loaded over 
>> HTTPS, but requested an insecure XMLHttpRequest endpoint '
>> http://a.b.com/blue/js-extensions/'. This request has been blocked; the 
>> content must be served over HTTPS. 
>> > 
>> > Is this something I can fix locally or can someone patch it? I know its 
>> a alpha,but was hoping to at least get it to load up so I can test it out. 
>> > 
>> > 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-use...@googlegroups.com. 
>> > To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/e0dcb993-e775-4997-9090-0afb1b237829%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/bd4b487c-5c5a-4dad-9dc2-d874869394c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.