Re: Need CPS/Groovy understanding - problem with setters/getters

[Michael Lasevich]

Well, apparently it is a known issue for about a year, with little activity 
:-(

https://issues.jenkins-ci.org/browse/JENKINS-31484

-M

On Wednesday, September 28, 2016 at 6:00:40 PM UTC-7, Michael Lasevich 
wrote:
>
> Can anyone who understands Groovy/CPS look at this and see if this is even 
> resolvable/fixable?
>
> Ok, so after much hair loss and much unpredictable behavior - I have 
> discovered an ugly bug (feature?) that Groovy getters/setters that work 
> fine under regular Groovy, fail miserably under Pipelines/Jenkins. I 
> suspect this is due to CPS, although I have not yet confirmed that, and 
> wrapping it in @NonCPS tag seems to have not affected the problem
>
> Consider this simple Groovy demo bean with a custom getter(same thing 
> happens with setters, btw, I just wanted to keep example simple):
>
> class Bean implements Serializable{
>
>  def name = "unset"
>
>
>   String getName(){
>
>if (this.name == "unset"){
>
>  this.name = "is not set"
>
>}
>
>return this.name
>
>  }
>
> }
>
> and following pipeline code is using it:
>
> import Bean
>
> b = new Bean()
>
> echo("Bean name: "+ b.name)
>
>
> The code here works fine under plain Groovy (replace "echo" with 
> "println") - but under pipelines it blows up. Looking under the hood it 
> appears that the 'return this.name' literally throws CPS for a loop, it 
> is being replaced with "return this.getName()" which causes infinite 
> recursion.
>
> Knowing this, the workaround seems to be to change the internal field name 
> to not match the getter/setter pattern - but that causes much ugliness (you 
> are forced to now have both getter/setter for common usage and your 
> getter/setter and your field name do not match)
>
> My suspicion is that this is a bug in CPS, but not clearly understanding 
> the purpose/benefits of CPS - I am unclear if this is even fixable. Best I 
> can figure is that CPS injects a lot of headaches in exchange for ability 
> to serialize your workflow at any point in time - a benefit which I am not 
> sure I care much about, considering bulk of the builds happens in 
> sub-processes outside of CPS control... My point is that I clearly do not 
> understand enough of what is going on or why it is happening under 
> Pipelines but not under Groovy in general.  Can someone who understands 
> this  better see if this is a bug or something inherent to Groovy/CPS setup?
>
> Thanks,
>
> -M
>
>
>

-- 
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/9aef94fb-ef8f-41bb-81d4-44febb57dfad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maintaining a unique Build Number across multiple build servers

[Michael Lasevich]

There are many approaches to this problem, and I am not sure what your 
setup or requirements are, but here is some information that may be helpful.

* It is important to understand that any jenkins build has two ids - the 
actual immutable build_id - which is always consecutive for a job and 
specific to that job alone, and the build display name which is what you 
see in the UI. You can set the build display name to anything you want from 
within your job. By default it is # (pound symbol) followed by build_id.

* You are usually better off having one build server with many slaves than 
parallel build servers that are independent of each other. This way as long 
as you are building the same job, it does not matter what slave you are 
building on, your build ids will be consecutive and unique.

* If you do need multiple jobs on same master (even if builds are performed 
on any slave), you can write some code that will issue numbers from same 
pool. You can back that pool by anything, the simplest thing being writing 
a file to disk on master. I have implemented this many times via writing my 
own plugin, but these days it is far easier to do this via a pipelines 
shared library (if you are using pipelines, and you should). The simplest 
thing to do is to have a function that takes some id, and for that id it 
issues you next number by incrementing a synchronized counter somewhere. Of 
course this will still keep you on a single Jenkins master...

* If you want to do this across multiple masters as you indicated (and I 
would strongly urge you to reconsider) - you can use the above with some 
sort of a shared storage resource that either supports atomic changes or 
locking - for example you can use a shared MySQL DB. You just have a table 
you lock and increment a counter in while locked (there are many other 
approaches too)

* If you do not care for keeping a shared counter somewhere and do not mind 
longer build ids, a cheap and easy way to go is to assign each jenkins 
server an id number, then use a build name consisting of timestamp followed 
by server id, followed by whatever you want to guarantee it is unique 
within a single server. Your build ids will be long, but will always be in 
a sequential order - even if not consecutive.

* All that said, I would also reconsider overall value of consecutive build 
numbers - in the end you probably only care about what branch it was done 
from and which commit it was done from. If you use a SCM that provides you 
with a sequential commit id (SVN is awesome for this) - just use the commit 
id as your build indicator. If you are using git or any other 
non-sequential commit SCM - you can just include the hash of the SCM on 
build and to get sequence, you can cheat a little by also counting commits 
in the log. Last bit is not exactly great as git allows you to rewrite your 
commit history, but if you can lock it down, it is reasonably functional 
indicator.

Good luck,

-M

On Monday, September 19, 2016 at 12:54:15 PM UTC-7, Robert Kruck wrote:
>
>  Is it possible to preserve the integrity of build numbers (NO DUPLICATES 
> and build numbers in order) while building in multiple Jenkins build 
> servers?
>
> If this capability exists in Jenkins, what Jenkins plugins are required, 
> and what versions of Jenkins itself, and of the required Jenkins plugins, 
> are needed?
>

-- 
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/84b32adc-04d5-417f-b0a6-01469c13ed5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Need CPS/Groovy understanding - problem with setters/getters

[Michael Lasevich]

Can anyone who understands Groovy/CPS look at this and see if this is even 
resolvable/fixable?

Ok, so after much hair loss and much unpredictable behavior - I have 
discovered an ugly bug (feature?) that Groovy getters/setters that work 
fine under regular Groovy, fail miserably under Pipelines/Jenkins. I 
suspect this is due to CPS, although I have not yet confirmed that, and 
wrapping it in @NonCPS tag seems to have not affected the problem

Consider this simple Groovy demo bean with a custom getter(same thing 
happens with setters, btw, I just wanted to keep example simple):

class Bean implements Serializable{

 def name = "unset"


  String getName(){

   if (this.name == "unset"){

 this.name = "is not set"

   }

   return this.name

 }

}

and following pipeline code is using it:

import Bean

b = new Bean()

echo("Bean name: "+ b.name)


The code here works fine under plain Groovy (replace "echo" with "println") 
- but under pipelines it blows up. Looking under the hood it appears that 
the 'return this.name' literally throws CPS for a loop, it is being 
replaced with "return this.getName()" which causes infinite recursion.

Knowing this, the workaround seems to be to change the internal field name 
to not match the getter/setter pattern - but that causes much ugliness (you 
are forced to now have both getter/setter for common usage and your 
getter/setter and your field name do not match)

My suspicion is that this is a bug in CPS, but not clearly understanding 
the purpose/benefits of CPS - I am unclear if this is even fixable. Best I 
can figure is that CPS injects a lot of headaches in exchange for ability 
to serialize your workflow at any point in time - a benefit which I am not 
sure I care much about, considering bulk of the builds happens in 
sub-processes outside of CPS control... My point is that I clearly do not 
understand enough of what is going on or why it is happening under 
Pipelines but not under Groovy in general.  Can someone who understands 
this  better see if this is a bug or something inherent to Groovy/CPS setup?

Thanks,

-M


-- 
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/f977f049-8b7e-440d-ab4f-3bf2f621abf1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue Ocean Problems: Cannot read property 'jenkinsConfig' of undefined

[Indra Gunawan (ingunawa)]

Have you restarted Jenkins yet before trying new plugin?

From: 
> on 
behalf of jwa >
Reply-To: 
"jenkinsci-users@googlegroups.com" 
>
Date: Wednesday, September 28, 2016 at 9:21 AM
To: Jenkins Users 
>
Subject: Blue Ocean Problems: Cannot read property 'jenkinsConfig' of undefined

Hi All,

Has anyone seen this problem with the Blue Ocean UI? When I click "Try Blue 
Ocean UI..." the progress bar stalls at ~90%.

When I open the console in Chrome it has the following logged out:

Cannot read property 'jenkinsConfig' of undefined blueocean.js:82243

I've only just installed the BlueOcean plugins, and I've never had it running.

Any suggestions would be greatly appreciated.

jwa.

--
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/de626d28-3a0c-43d6-be83-8fa897f0ba28%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/D411A9A1.5DC7D%25ingunawa%40cisco.com.
For more options, visit https://groups.google.com/d/optout.

Re: LDAP with Jenkins 2.0 (Jenkins 2.7.4 version to be specific)

[Indra Gunawan (ingunawa)]

Yes LDAP plugin is working fine with Jenkins 2.7.4 LTS.  My case is I upgraded 
from 1.625.3 to 2.7.4.  I kept LDAP plugin the same @ version 1.11

From: 
> on 
behalf of Raghu Pallikonda >
Reply-To: 
"jenkinsci-users@googlegroups.com" 
>
Date: Wednesday, September 28, 2016 at 3:55 PM
To: Jenkins Users 
>
Subject: LDAP with Jenkins 2.0 (Jenkins 2.7.4 version to be specific)

Does anyone have the LDAP plugin 
https://wiki.jenkins-ci.org/display/JENKINS/LDAP+Plugin working successfully 
with Jenkins 2.0 ?  I installed and configured the LDAP plugin with Jenkins 
2.7.4 and it doesn't work as expected (got server certificate change is 
restricted during renegotiation).

I downloaded the plugin source code, but got compile errors when tried to build 
with Jenkins 2.7.4 version. The class hudson.tasks.MailAddressResolver is not 
found.



--
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/c8036a59-84ad-4062-8042-23db74702fad%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/D411A8B0.5DC76%25ingunawa%40cisco.com.
For more options, visit https://groups.google.com/d/optout.

LDAP with Jenkins 2.0 (Jenkins 2.7.4 version to be specific)

[Raghu Pallikonda]

Does anyone have the LDAP 
plugin https://wiki.jenkins-ci.org/display/JENKINS/LDAP+Plugin working 
successfully with Jenkins 2.0 ?  I installed and configured the LDAP plugin 
with Jenkins 2.7.4 and it doesn't work as expected (got *server certificate 
change is restricted during renegotiation)*. 

I downloaded the plugin source code, but got compile errors when tried to 
build with Jenkins 2.7.4 version. The class 
hudson.tasks.MailAddressResolver is not found. 


-- 
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/c8036a59-84ad-4062-8042-23db74702fad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

(ez-template) Can job using a template add build steps

[John Mathews]

I used EZ-Template to create a template that has common configurations for 
my jobs. I'm trying to create a job that uses the template, with additional 
builds steps. Is this possible? Every time I save the job, the build step 
is removed.

-- 
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/b73a939d-459e-40bf-b38c-5519ae8ceb01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Scheduled maintenance for JIRA, Wiki, Accounts, DNS, etc 2016-09-29 22:00-23:00 UTC

[R. Tyler Croy]

Consider this notice that we will be performing scheduled maintenance during a
60 minute window tomorrow September 29th (UTC).

I will be taking various services which are deployed via Docker containers
temporarily offline as we upgrade the underlying Docker daemons. We will be
iterating through machines which host containers one by one, so a total outage
should not be experienced.

The ticket this is related to is:


The services this will affect are:

 * JIRA (https://issues.jenkins-ci.org)
 * Confluence (https://wiki.jenkins-ci.org)
 * Accounts management (https://accounts.jenkins.io)
 * jenkins-admin ircbot
 * robobutler ircbot
 * DNS services
 * demo.jenkins-ci.org
 * Docker-capable build agents attached to https://ci.jenkins.io


I will send an all-clear when the maintenance has completed.


Cheers
- R. Tyler Croy

--
 Code: 
  Chatter: 

  % gpg --keyserver keys.gnupg.net --recv-key 1426C7DC3F51E16F
--

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


signature.asc
Description: Digital signature

reg old builds

[Zue Sani]

Hi ,

Can I know how can we save old builds in Jenkins.

we are building dacpac and deploying but when we want to deploy the old
builds I couldn't find the old build. is there any way I can store the old
builds and set them to deployment.

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

Re: Jenkins Docker Slave unable to connect to Jenkins Master

[Harikrishnan Gopalakrishnan]

Hi,

I am also facing similar issue. Where you able to resolve this issue. Could 
you please let me know how this was fixed?


On Tuesday, March 22, 2016 at 10:26:58 AM UTC-4, jsand...@gmail.com wrote:
>
> HI,
>
> Issue:  Jenkin Slave running in a Docker Container unable to connect to 
> the Jenkins Master.
>
> I have Jenkins Master in Docker Container on AWS EC2 Instance.  I have 
> installed AWS ECS (Container Plugin).   Jenkins Slaves are running in the 
> Docker container.   
>
> Here is the log:
>
> Jenkins Master Log:
>
>
> Mar 21, 2016 11:18:41 PM WARNING jenkins.slaves.JnlpSlaveHandshake error
>
> TCP slave agent connection handler #10 with /10.231.5.122:56870 is 
> aborted: JNLP2-connect: rejected connection for node: my-slave-13
>
> Mar 21, 2016 11:18:41 PM INFO 
> hudson.TcpSlaveAgentListener$ConnectionHandler run
>
> Accepted connection #11 from /10.231.5.122:56871
>
> Mar 21, 2016 11:18:41 PM WARNING jenkins.slaves.JnlpSlaveHandshake error
>
> TCP slave agent connection handler #11 with /10.231.5.122:56871 is 
> aborted: Unauthorized access
>
> Mar 21, 2016 11:18:41 PM INFO 
> hudson.TcpSlaveAgentListener$ConnectionHandler run
>
> Accepted connection #12 from /10.231.5.122:56872
>
> Mar 21, 2016 11:18:41 PM WARNING 
> hudson.TcpSlaveAgentListener$ConnectionHandler run
>
> Connection #12 failed
>
> java.io.EOFException
>
> at 
> java.io.DataInputStream.readUnsignedShort(DataInputStream.java:340)
>
> at 
> java.io.DataInputStream.readUTF(DataInputStream.java:589)
>
> at 
> java.io.DataInputStream.readUTF(DataInputStream.java:564)
>
> at 
> hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:150)
>
>  
>
> Jenkins Slave Log:
>
>
> On the slave, I am getting the following error
>
> ar 21, 2016 11:18:41 PM hudson.remoting.jnlp.Main createEngine
>
> INFO: Setting up slave: my-slave-13
>
> Mar 21, 2016 11:18:41 PM hudson.remoting.jnlp.Main$CuiListener 
>
> INFO: Jenkins agent is running in headless mode.
>
> Mar 21, 2016 11:18:41 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Locating server among [http://10.231.1.123:8080/jenkins/]
>
> Mar 21, 2016 11:18:41 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Handshaking
>
> Mar 21, 2016 11:18:41 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Connecting to 10.231.1.123:5
>
> Mar 21, 2016 11:18:41 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Trying protocol: JNLP2-connect
>
> Mar 21, 2016 11:18:41 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Server didn't understand the protocol: JNLP2-connect: rejected 
> connection for node: my-slave-13
>
> Mar 21, 2016 11:18:41 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Connecting to 10.231.1.123:5
>
> Mar 21, 2016 11:18:41 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Trying protocol: JNLP-connect
>
> Mar 21, 2016 11:18:41 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Server didn't understand the protocol: Unauthorized access
>
> Mar 21, 2016 11:18:41 PM hudson.remoting.jnlp.Main$CuiListener status
>
> INFO: Connecting to 10.231.1.123:5
>
> Mar 21, 2016 11:18:41 PM hudson.remoting.jnlp.Main$CuiListener error
>
> SEVERE: The server rejected the connection: None of the protocols were 
> accepted
>
> java.lang.Exception: The server rejected the connection: None of the 
> protocols were accepted
>
> at hudson.remoting.Engine.onConnectionRejected(Engine.java:297)
>
> at hudson.remoting.Engine.run(Engine.java:268)
>

-- 
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/f977173a-22d7-41fd-b54f-3bbdad1165a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Merge Git Core Repo and Site Repo folder while Jenkins deployment

[Mark Waite]

I'm sorry, but I don't have a script handy to do that.  You might
investigate the "ant" build tool and its "copy" task.

Mark Waite

On Tue, Sep 27, 2016 at 5:08 AM kamlesh nattamai ramesh babu <
nrkaml...@gmail.com> wrote:

> Thanks very much *Mark Waite, *I was looking for the similar kind of
> solution.
>
> You are right , My expectation is to *combine* 2 folders of "WP-CONTENT"
> from the different repositories(CORE & SITE) while JENKINS deployment. We
> make the changes only on the *site wise "WP-CONTENT". *But finally when
> we do the* JENKINS deployment* I would need to COMBINE the WP-CONTENT
> folders from the CORE along with the site repository which belongs to a
> particular site and contains the recent changes.
>
> It would be helpful for me if you have the script handy for the same
> experiment ..
>
> Thanks again for your worthy suggestions..
>
> Thanks,
> Kamlesh
>
> On Tuesday, 27 September 2016 05:54:04 UTC+5:30, Mark Waite wrote:
>>
>>
>> On Mon, Sep 26, 2016 at 9:50 AM kamlesh nattamai ramesh babu <
>> nrka...@gmail.com> wrote:
>>
>>> Hi Folks,
>>>
>>> I need your advice badly.. We are Maintaining  2 GIT repo for handling
>>> code.
>>>
>>> 1. *Core repo*: This repo contains the core files which is commonly
>>> used for all the projects as a core base files.
>>> 2. *Site repo*: This repo contains the site wise file which will merge
>>> with core while GIT deployment.
>>>
>>>
>> I assume in my comments below that the verb "merge" in the above comment
>> means "combine the files from both git repositories into a single
>> directory.  I assume in my comments below that the verb "merge" does not
>> mean "perform the 'git merge' command across two git repositories".
>>
>> If those assumptions are wrong, then my comments should be ignored.
>>
>>
>>> Both CORE and SITE will get merged with each other while doing the GIT
>>> deployment.  We maintain the CORE plugins in the *core repo* and site
>>> wise plugins in *site repo. *So both the repo will contain the same
>>> folder name called "WP-CONTENT" which contain core plugins in core repo and
>>> site plugins in site repo. Both the folder will get merged while deploying
>>> the code thru GIT. I want to make this process automate thru *JENKIN
>>> deployment* but it is not happening.
>>>
>>>
>> The Jenkins git plugin can't combine the contents of two different
>> repositories into the same root workspace folder.  Thus, you can't use the
>> Jenkins git plugin to have a single job workspace root folder which
>> contains both CORE and SITE repositories at its root.
>>
>> You can (with the pipeline plugin, or with the multiple SCM's plugin)
>> checkout multiple repositories into subdirectories of the workspace root
>> folder.  You could then run a build step which combines the contents of the
>> "WP-CONTENT" directory from each of those subdirectories into a single
>> subdirectory of your choosing inside the workspace.
>>
>> I'm not sure what you mean when you say "Both the folder will get merged
>> while deploying the code thru GIT".
>>
>> Thanks,
>> Mark Waite
>>
>>
> I would like you guys share your esteemed knowledge to make this sort out..
>>>
>>> Thanks,
>>> Kamlesh
>>>
>>> --
>>> 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/46e509ed-2734-41e1-9d31-76c17f43bffb%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/eded920d-8067-49d7-8595-30197bf1c1e7%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/CAO49JtEBfsJ355pvz%3D9-wmPkpfHtnHn0BNcFDF%3D4tUekj5OmUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

scriptler - dependencies with grab/grape?

[Guy Matz]

Hello!  Does anyone know if it's possible to grab dependencies within a
scriptler script?  Any advice out there?

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

Blue Ocean Problems: Cannot read property 'jenkinsConfig' of undefined

[jwa]

Hi All,

Has anyone seen this problem with the Blue Ocean UI? When I click "Try Blue 
Ocean UI..." the progress bar stalls at ~90%.

When I open the console in Chrome it has the following logged out: 

Cannot read property 'jenkinsConfig' of undefined blueocean.js:82243

I've only just installed the BlueOcean plugins, and I've never had it 
running.

Any suggestions would be greatly appreciated.

jwa.

-- 
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/de626d28-3a0c-43d6-be83-8fa897f0ba28%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Maintaining a unique Build Number across multiple build servers

[Robert Kruck]

On Monday, September 19, 2016 at 2:54:15 PM UTC-5, Robert Kruck wrote:
>
>  Is it possible to preserve the integrity of build numbers (NO DUPLICATES 
> and build numbers in order) while building in multiple Jenkins build 
> servers?
>
> If this capability exists in Jenkins, what Jenkins plugins are required, 
> and what versions of Jenkins itself, and of the required Jenkins plugins, 
> are needed?
>

Would the simplest solution to maintain build number integrity across 
multiple Jenkins servers be to:
a) Create a versioned ini file (in our case, a StarTeam file in a *.ini 
format), containing the latest 5-digit build number.
b) The above StarTeam file would be visible to all our build scripts, no 
matter what Jenkins server they were located in.
c) When a build script is under way, it would do an EXCLUSIVE checkout of 
the StarTeam build number ini file. (Perhaps a wait time could be added to 
this checkout step, in case the above file was checked-out & locked at the 
time by another build script).
d) The build script increments the build number in the build number ini 
file using WriteINI, and uses this incremented build number for its build.
e) Finally, the build script checks in the StarTeam build number ini file, 
so it is unlocked / correctly updated / and visible to other build scripts 
in other Jenkins servers.

1) Obtaining the build number via a versioned *.ini file would seem to have 
no problems for an interactive, non-Jenkins build.

2) Would obtaining the build number via a versioned *.ini file, rather than 
a build number generated by Jenkins, be practical in a build done through 
Jenkins?

3) Is the above "versioned build number *.ini file" concept reasonable, or 
would use of Jenkins plugin(s) & Windows Environment variables be the best 
way to reliably increment, then communicate, build numbers across multiple 
Jenkins servers?

-- 
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/26118b34-d8e1-4e5b-b3f4-1eb5eb669159%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

How to Stop Weblogic Node from jenkins

[R Jeevitha]

Hi,
Can anyone please tell me the steps to stop weblogic node from jenkins.
Manually we follow the below process,the same thing I want to achieve in 
jenkins.
-Login Weblogic console
-Go To Environment->Clusters->Select Node->click Force ShutDown.

Thanks,
Jeevitha.R

-- 
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/9f86b646-78a4-4612-9af5-3cdfa628b05b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: WARN: sonar-runner.bat script is deprecated. Please use sonar-scanner.bat instead.

[Capfo]

Hello,

Do you found the solution ?


thanks,



Le jeudi 18 août 2016 17:42:03 UTC+2, Philippe Couas a écrit :
>
> Hi
>
> I have tried to add login to sonar user without succes 
> -Dsonar.login=postgre login -Dsonar.password=postgres password
> I have tried too to add SonarQube admin user with same parameters without 
> succes
>
> Regards
>
> Le jeudi 18 août 2016 17:28:21 UTC+2, Philippe Couas a écrit :
>>
>>
>>
>> Le jeudi 18 août 2016 17:26:08 UTC+2, Philippe Couas a écrit :
>>>
>>> Hi,
>>>
>>> I launch sonar scaner from Jenkins 2.7.2 and i have following message 
>>> "WARN: sonar-runner.bat script is deprecated. Please use 
>>> sonar-scanner.bat instead.'
>>>
>>
>> When i add -X option, i have following error message
>>
>> Caused by: Not authorized. Please check the properties sonar.login and 
>> sonar.password.
>> Build step 'Lancer une analyse avec SonarQube Scanner' marked build as 
>> failure
>> Injection des variables d'environnement SonarQube en utilisant la 
>> configuration: sonarqube
>>
>>  
>>
>>>
>>> Regards
>>>
>>

-- 
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/bb445c12-4e34-4e91-a9a7-72230ab2840f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.