Re: Help w/ maven release and git

[Jeff]

Bumpanyone using GIT w/ maven-release-plugin in Jenkins?


On Wed, Jan 23, 2013 at 9:41 PM, Jeff  wrote:

> Two questions (from a Git n00b) dealing with Git + Maven in Jenkins:
>
> 1) When I do a release, I either want a new branch based on the maven
> release version or a "release" branch sync'd w/ the latest "master" code
> and tagged with the latest release version so we can pull it if we ever
> need to do a hot fix based on release code.  I haven't found the thing that
> helps me do this using the Maven Release Plugin and Git.  Can anyone point
> me in the right direction?
>
> 2) I've configured Jenkins w/ the SSH keys for our Git "service" account
> to our internal gitolite repository.  I can successfully pull and it seems
> that during the maven release process, the "commit" works when updating the
> POM, but it seems pushing the new branch fails with:
>
> MyGitProject: Unable to commit files
> Provider message:
> The git-push command failed.
> Command output:
> ssh: svcSCM: no address associated with name
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
>
>
> The user has the same rights as my personal user and I can do branching
> and pushing operations manually with either account on the Jenkins box.
>  I've tried leaving the SCM username/password blank when scheduling a maven
> release and I've also tried just setting the user name to match the Git
> service account user with similar failed results.
>
> I'm sure I'm missing something fundamentally simple, but I'm not seeing it.
>
> Any and all help is much appreciated.
>
> --
> Jeff Vincent
> predato...@gmail.com
> See my LinkedIn profile at:
> http://www.linkedin.com/in/rjeffreyvincent
> I ♥ DropBox  !!
>



-- 
Jeff Vincent
predato...@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
I ♥ DropBox  !!

Re: best linux production env for jenkins?

[Les Mikesell]

On Fri, Jan 25, 2013 at 4:19 PM, teilo  wrote:
>
>>
>> For RH or CentOS, I think the yum install is even easier if you want
>> to use the embedded winstone.
>> http://pkg.jenkins-ci.org/redhat/
>> You can configure your options in the /etc/sysconfig/jenkins file so
>> subsequent updates won't overwrite them.   JENKINS_HOME will be
>> /var/lib/jenkins (following packaging guidelines) so mount whatever
>> you want there before then install.
>>
>>
>
> Its easier for the first install, but after that it is not as good.

I'd argue the opposite on that.

> Packages are guaranteed to be broken more than the war alone (as there is an
> extra layer it is one more thiing that can change/break - as shown by the
> recent deb change)

And I'd argue that those extra layers should be correct and tested by
the time they are released.  Or you should wait until someone else
tries them and skip the broken releases.

> The war arguments are not likely to change but will be added to (if needed)
> but the config exposed by these scripts is not the same.
>
> For example what happens if you say want to run SSL - you then add custom
> ARGs to the line.

Not sure how the deb works, but the rpm package puts the things you
would customize in /etc/sysconfig/jenkins.

> Later the init scripts add a user friendly option for SSL (defaults to -1).
> so now the init script can fail as the HTTPS_PORT var is not -1 (as it
> doesn't exist in your config) - or worse it is 8443 by default so it uses
> the default as well as your different port.

Rpms normally either install files as .rpmnew if they would conflict
with local changes or save the local file as .rpmsave if they need to
replace it.


> That is a contrived example - but that has happend recently on the deb when
> a parameter was removed.
>
> upgrades/downgrades are a simple change of a symlink with the jenkins war.
> by all means grab the init scripts from the src repo - but in the long run
> the ease is lost.
>
> my 2p from experience.

If you want stability you probably want the 'LTS' version:
https://wiki.jenkins-ci.org/display/JENKINS/LTS+Release+Line

I just don't update very often because what I have works fine.

-- 
   Les Mikesell
 lesmikes...@gmail.com

Re: copy artifacts question

[Jason Swager]

Not really.  Promotions are a great way to mark when downstream jobs or
tests have completed for a specific build.  And each promotion is a
separate permalink.  Copy artifacts can work off permalinks.  Innovative
use of two custom plugins.

On Friday, January 25, 2013, Chris Withers wrote:

> Interesting, but does feel like a bit of a hack...
>
> Chris
>
> On 25/01/2013 15:25, Jason Swager wrote:
>
>> Yes. Using the Promotions plugin, setup a promotion that automatically
>> triggers when all the downstream jobs have passed. The Promotions plugin
>> will expose that build as a permalink.
>>
>> Use the Copy Artifacts plugin to pull artifacts from the permalink
>> associated with the promotion.
>> Jason Swager
>>
>> On Thursday, January 24, 2013 11:33:44 PM UTC-8, Chris Withers wrote:
>>
>> Hi All,
>>
>> Is there any way I can get the copy artifacts plugin to copy from the
>> last build for which all downstream jobs passed?
>>
>> cheers,
>>
>> Chris
>>
>> --
>> Simplistix - Content Management, Batch Processing & Python Consulting
>> - http://www.simplistix.co.uk
>>
>>
>> __**__**
>> __
>> This email has been scanned by the Symantec Email Security.cloud service.
>> For more information please visit http://www.symanteccloud.com
>> __**__**
>> __
>>
>
> --
> Simplistix - Content Management, Batch Processing & Python Consulting
> - http://www.simplistix.co.uk
>

Re: best linux production env for jenkins?

[teilo]

On Friday, 25 January 2013 21:56:41 UTC, LesMikesell wrote:
>
> On Fri, Jan 25, 2013 at 3:43 PM, teilo > 
> wrote: 
> > 
> > To be pretty honest - I would suggest you skip the packaged versions and 
> use 
> > your own init scripts and the war with the inbuilt winstone container. 
> > 
> > As for which distro - if you take the above advice it depends on you. 
> > Pretty much anything recent will have a good enough kernel and the reset 
> is 
> > just java. 
> > 
> > I use CentOS, but I prefer to admin debian - but work is RH/CentOS.  If 
> you 
> > are thinking of support then make sure that whatever you choose is 
> covered 
> > by your support vendor. Whichever you choose you can always choose not 
> to 
> > install the defaults but install just what you want (but having things 
> > installed should not be an issue - just don;t start the services and 
> install 
> > root on cheaper HDD and then have your JENKINS_HOME on the SSD 
> > 
>
> For RH or CentOS, I think the yum install is even easier if you want 
> to use the embedded winstone. 
> http://pkg.jenkins-ci.org/redhat/ 
> You can configure your options in the /etc/sysconfig/jenkins file so 
> subsequent updates won't overwrite them.   JENKINS_HOME will be 
> /var/lib/jenkins (following packaging guidelines) so mount whatever 
> you want there before then install. 
>
>
>
Its easier for the first install, but after that it is not as good.

Packages are guaranteed to be broken more than the war alone (as there is 
an extra layer it is one more thiing that can change/break - as shown by 
the recent deb change)

The war arguments are not likely to change but will be added to (if needed) 
but the config exposed by these scripts is not the same.

For example what happens if you say want to run SSL - you then add custom 
ARGs to the line.
Later the init scripts add a user friendly option for SSL (defaults to -1).
so now the init script can fail as the HTTPS_PORT var is not -1 (as it 
doesn't exist in your config) - or worse it is 8443 by default so it uses 
the default as well as your different port.

That is a contrived example - but that has happend recently on the deb when 
a parameter was removed.

upgrades/downgrades are a simple change of a symlink with the jenkins war.
by all means grab the init scripts from the src repo - but in the long run 
the ease is lost.

my 2p from experience.

Re: best linux production env for jenkins?

[Les Mikesell]

On Fri, Jan 25, 2013 at 3:43 PM, teilo  wrote:
>
> To be pretty honest - I would suggest you skip the packaged versions and use
> your own init scripts and the war with the inbuilt winstone container.
>
> As for which distro - if you take the above advice it depends on you.
> Pretty much anything recent will have a good enough kernel and the reset is
> just java.
>
> I use CentOS, but I prefer to admin debian - but work is RH/CentOS.  If you
> are thinking of support then make sure that whatever you choose is covered
> by your support vendor. Whichever you choose you can always choose not to
> install the defaults but install just what you want (but having things
> installed should not be an issue - just don;t start the services and install
> root on cheaper HDD and then have your JENKINS_HOME on the SSD
>

For RH or CentOS, I think the yum install is even easier if you want
to use the embedded winstone.
http://pkg.jenkins-ci.org/redhat/
You can configure your options in the /etc/sysconfig/jenkins file so
subsequent updates won't overwrite them.   JENKINS_HOME will be
/var/lib/jenkins (following packaging guidelines) so mount whatever
you want there before then install.

-- 
  Les Mikesell
 lesmikes...@gmail.com

Re: best linux production env for jenkins?

[teilo]

Hi Russ,

To be pretty honest - I would suggest you skip the packaged versions and 
use your own init scripts and the war with the inbuilt winstone container.

As for which distro - if you take the above advice it depends on you. 
 Pretty much anything recent will have a good enough kernel and the reset 
is just java.

I use CentOS, but I prefer to admin debian - but work is RH/CentOS.  If you 
are thinking of support then make sure that whatever you choose is covered 
by your support vendor. Whichever you choose you can always choose not to 
install the defaults but install just what you want (but having things 
installed should not be an issue - just don;t start the services and 
install root on cheaper HDD and then have your JENKINS_HOME on the SSD
Don'f forget to replace those SSDs early before they wear out :-)

/James

On Friday, 25 January 2013 20:18:12 UTC, Russ Tremain wrote:
>
> Hi, 
>
> Does anyone have suggestions for the best linux production 
> environment for jenkins? 
>
> I want to run a trimmed down server optimized for web performance. 
>
> In the past, I've always run jenkins under tomcat, but am open to 
> other suggestions. 
>
> Looking for specific version info for distros & tomcat. 
>
> Will run on vmware infrastructure with outrageous (SSD-based) i/o 
> performance. 
>
> tia, 
> -Russ 
>

RE: parameterizing which downstream jobs to build

[Merrow, Frank]

Build.CMD <- your normal build command
SET SAVEEC=%ERRORLEVEL%
Python startdownstreamjobusingpythonjenkins.py
EXIT %SAVEEC%

-Original Message-
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Chris Withers
Sent: Friday, January 25, 2013 11:05 AM
To: jenkinsci-users@googlegroups.com
Cc: Merrow, Frank
Subject: Re: parameterizing which downstream jobs to build

On 25/01/2013 16:27, Merrow, Frank wrote:
>> I'd like to have a job do something and then kick off some downstream 
>> jobs, but I'd like to make some choices in the job to decide *which* 
>> downstream jobs to kick off.
>>
>> How can I do that?
>
> I see other solutions have been offered, but if you needs are complex enough 
> . . . google "python Jenkins".
>
> It would allow you to write a Python Script to make that decision as part of 
> the job run.

How so? Can you point me to a short example as I can't think of a way to change 
the triggered downstream jobs from a build step on post-build action...

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
 - http://www.simplistix.co.uk

RE: best linux production env for jenkins?

[Mandeville, Rob]

I'm running a fairly large environment, 200+ nodes and hundreds of jobs a 
night.  We use the onboard WinStone running on Java 7 over Linux.  The VM 
arguments we use are
-Xmx4096m -Xms1024m -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode 
-XX:+CMSClassUnloadingEnabled

--Rob

-Original Message-
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Russ Tremain
Sent: Friday, January 25, 2013 3:18 PM
To: jenkinsci-users@googlegroups.com
Subject: best linux production env for jenkins?

Hi,

Does anyone have suggestions for the best linux production environment for 
jenkins?

I want to run a trimmed down server optimized for web performance.

In the past, I've always run jenkins under tomcat, but am open to other 
suggestions.

Looking for specific version info for distros & tomcat.

Will run on vmware infrastructure with outrageous (SSD-based) i/o performance.

tia,
-Russ

The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

Re: copy artifacts question

[Chris Withers]

Interesting, but does feel like a bit of a hack...

Chris

On 25/01/2013 15:25, Jason Swager wrote:

Yes. Using the Promotions plugin, setup a promotion that automatically
triggers when all the downstream jobs have passed. The Promotions plugin
will expose that build as a permalink.

Use the Copy Artifacts plugin to pull artifacts from the permalink
associated with the promotion.
Jason Swager

On Thursday, January 24, 2013 11:33:44 PM UTC-8, Chris Withers wrote:

Hi All,

Is there any way I can get the copy artifacts plugin to copy from the
last build for which all downstream jobs passed?

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk


__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__


--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

Re: parameterizing which downstream jobs to build

[Chris Withers]

On 25/01/2013 16:27, Merrow, Frank wrote:

I'd like to have a job do something and then kick off some downstream
jobs, but I'd like to make some choices in the job to decide *which*
downstream jobs to kick off.

How can I do that?


I see other solutions have been offered, but if you needs are complex enough . . . google 
"python Jenkins".

It would allow you to write a Python Script to make that decision as part of 
the job run.


How so? Can you point me to a short example as I can't think of a way to 
change the triggered downstream jobs from a build step on post-build 
action...


cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

best linux production env for jenkins?

[Russ Tremain]

Hi,

Does anyone have suggestions for the best linux production 
environment for jenkins?


I want to run a trimmed down server optimized for web performance.

In the past, I've always run jenkins under tomcat, but am open to 
other suggestions.


Looking for specific version info for distros & tomcat.

Will run on vmware infrastructure with outrageous (SSD-based) i/o performance.

tia,
-Russ

Re: sloccount plugin exception

[Kamal Ahmed]

P.S

This is on CentOs 6.3 ( Slave ) 


using sloccount-2.26-umask.1.x86_64.rpm

Jenkins sloccount plugin 1.8

Jenkins version 1.499, running on ubuntu 12.04 ( Master ) 





>
> From: Kamal Ahmed 
>To: "jenkinsci-users@googlegroups.com"  
>Sent: Friday, January 25, 2013 12:24 PM
>Subject: sloccount plugin exception
> 
>
>Hi Group,
>
>
>I am getting an exception:
>
>
>12:16:34 ERROR: Publisher hudson.plugins.sloccount.SloccountPublisher aborted 
>due to exception 12:16:34 java.lang.NullPointerException 12:16:34 at 
>hudson.plugins.sloccount.model.SloccountParser.parseLine(SloccountParser.java:92)
> 12:16:34 at 
>hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:59) 
>12:16:34 at 
>hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:50) 
>12:16:34 at 
>hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:40) 
>12:16:34 at 
>hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:17) 
>12:16:34 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2309) 
>12:16:34 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 12:16:34 
>at hudson.remoting.UserRequest.perform(UserRequest.java:48) 12:16:34 at 
>hudson.remoting.Request$2.run(Request.java:326) 12:16:34 at 
>hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 12:16:34 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 
12:16:34 at java.util.concurrent.FutureTask.run(FutureTask.java:166) 12:16:34 
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) 
12:16:34 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) 
12:16:34 at java.lang.Thread.run(Thread.java:679)
>
>Any ideas ? 
>
>
>

Re: Plugins update gone wrong

[Peter Miklosko]

Problem came from Github OAuth 
Plugin
. 

   1. I shutdown Jenkins
   2. Made copy of config.xml and saed it as config.xml.old
   3. Edited config.xml
  - changed useSecurity to false
  - removed all permissions entries for users
  - changed authorizationStrategy as 
  - changed  securityRealm as 
   4. Started Jenkins
   5. Downgraded plugin to 0.12
   6. Shutdown Jenkins
   7. Copied config.xml.old to config.xml
   8. Started Jennkins 

Hope this will help others

sloccount plugin exception

[Kamal Ahmed]

Hi Group,

I am getting an exception:

12:16:34 ERROR: Publisher hudson.plugins.sloccount.SloccountPublisher aborted 
due to exception 12:16:34 java.lang.NullPointerException 12:16:34 at 
hudson.plugins.sloccount.model.SloccountParser.parseLine(SloccountParser.java:92)
 12:16:34 at 
hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:59) 
12:16:34 at 
hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:50) 
12:16:34 at 
hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:40) 
12:16:34 at 
hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:17) 
12:16:34 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2309) 
12:16:34 at hudson.remoting.UserRequest.perform(UserRequest.java:118) 12:16:34 
at hudson.remoting.UserRequest.perform(UserRequest.java:48) 12:16:34 at 
hudson.remoting.Request$2.run(Request.java:326) 12:16:34 at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 12:16:34 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) 
12:16:34 at java.util.concurrent.FutureTask.run(FutureTask.java:166) 12:16:34 
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) 
12:16:34 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) 
12:16:34 at java.lang.Thread.run(Thread.java:679)

Any ideas ? 

Plugins update gone wrong

[Peter Miklosko]

Today I just run update on 3 plugins: SVN plugin and 2 GitHub plugins

After restart we landed with 500. Bellow is full error. Can anyone please 
advice how to solve this issue?

Exception: Unexpected character ('<' (code 60)): expected a valid value 
(number, String, array, object, 'true', 'false' or 'null') at [Source: 
java.io.StringReader@5e5e32a1; line: 1, column: 2]
Stacktrace:

org.codehaus.jackson.JsonParseException: Unexpected character ('<' (code 60)): 
expected a valid value (number, String, array, object, 'true', 'false' or 
'null')
 at [Source: java.io.StringReader@5e5e32a1; line: 1, column: 2]
at org.codehaus.jackson.JsonParser._constructError(JsonParser.java:1433)
at 
org.codehaus.jackson.impl.JsonParserMinimalBase._reportError(JsonParserMinimalBase.java:521)
at 
org.codehaus.jackson.impl.JsonParserMinimalBase._reportUnexpectedChar(JsonParserMinimalBase.java:442)
at 
org.codehaus.jackson.impl.ReaderBasedParser._handleUnexpectedValue(ReaderBasedParser.java:1198)
at 
org.codehaus.jackson.impl.ReaderBasedParser.nextToken(ReaderBasedParser.java:485)
at 
org.codehaus.jackson.map.ObjectMapper._initForReading(ObjectMapper.java:2770)
at 
org.codehaus.jackson.map.ObjectMapper._readMapAndClose(ObjectMapper.java:2718)
at 
org.codehaus.jackson.map.ObjectMapper.readValue(ObjectMapper.java:1863)
at org.kohsuke.github.Requester.parse(Requester.java:300)
at org.kohsuke.github.Requester._to(Requester.java:173)
at org.kohsuke.github.Requester.to(Requester.java:139)
at org.kohsuke.github.GitHub.getMyself(GitHub.java:200)
at org.kohsuke.github.GitHub.(GitHub.java:102)
at org.kohsuke.github.GitHub.connectUsingOAuth(GitHub.java:149)
at 
org.jenkinsci.plugins.GithubAuthenticationToken.(GithubAuthenticationToken.java:68)
at 
org.jenkinsci.plugins.GithubSecurityRealm.doFinishLogin(GithubSecurityRealm.java:313)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487)
at org.kohsuke.stapler.Stapler.service(Stapler.java:164)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at 
hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at 
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.rememberme.R

RE: parameterizing which downstream jobs to build

[Merrow, Frank]

> I'd like to have a job do something and then kick off some downstream 
> jobs, but I'd like to make some choices in the job to decide *which* 
> downstream jobs to kick off.
> 
> How can I do that?

I see other solutions have been offered, but if you needs are complex enough . 
. . google "python Jenkins".

It would allow you to write a Python Script to make that decision as part of 
the job run.

Depends on what you need and how complex your decisions are.

Frank

RE: copy artifacts question

[Merrow, Frank]

That I am aware of . . . not directly.

If your downstream jobs "fan out" then I don't have a solution for you.

However, if they are a sequence, pass the artifacts from job to job down the 
stream . . . then pull them from the last job.

Frank

-Original Message-
From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Chris Withers
Sent: Thursday, January 24, 2013 11:34 PM
To: jenkinsci-users@googlegroups.com
Subject: copy artifacts question

Hi All,

Is there any way I can get the copy artifacts plugin to copy from the last 
build for which all downstream jobs passed?

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
 - http://www.simplistix.co.uk

Re: copy artifacts question

[Jason Swager]

Yes.  Using the Promotions plugin, setup a promotion that automatically 
triggers when all the downstream jobs have passed.  The Promotions plugin 
will expose that build as a permalink.

Use the Copy Artifacts plugin to pull artifacts from the permalink 
associated with the promotion.
Jason Swager

On Thursday, January 24, 2013 11:33:44 PM UTC-8, Chris Withers wrote:
>
> Hi All, 
>
> Is there any way I can get the copy artifacts plugin to copy from the 
> last build for which all downstream jobs passed? 
>
> cheers, 
>
> Chris 
>
> -- 
> Simplistix - Content Management, Batch Processing & Python Consulting 
>  - http://www.simplistix.co.uk 
>

Re: Jenkins fails to send email

[Chris Jones]

Nope, it was a fresh install. (Both times, really.)

Chris

On 1/24/2013 5:04 PM, Slide wrote:
> Were you upgrading from a previous install when you started seeing the
> issue?
>
>
> On Thu, Jan 24, 2013 at 4:58 PM, Chris Jones  > wrote:
>
> I moved all the files to another location.
>
> Chris
>
>
> On 1/24/2013 4:57 PM, Slide wrote:
>> Did you also clean out your JENKINS_HOME directory, or was it
>> left over from the previous install?
>>
>>
>> On Thu, Jan 24, 2013 at 4:53 PM, Chris Jones
>> mailto:christian.jo...@sri.com>> wrote:
>>
>> Yes, to confound the issue, I did a reinstall and I'm not
>> seeing that particular problem anymore. (Still occasional
>> trouble with the "Loading" overlay not going away, though.) I
>> don't think there were any substantial differences in my
>> install process this time around.
>>
>> Chris
>>
>>
>> On 1/24/2013 12:17 PM, Slide wrote:
>>> So, somehow, for some reason this is returning null, does
>>> anyone know why this would return null and only for some
>>> people? Not everyone is running into this issue.
>>>
>>>
>>
>>
>>
>>
>> -- 
>> Website: http://earl-of-code.com
>
>
>
>
> -- 
> Website: http://earl-of-code.com

Re: parameterizing which downstream jobs to build

[cjo]

Not sure as the maintainer seems to be AWOL for the last 9-10 months, will 
ping the developer list to see if I can get someone to review the many Pull 
requests.

On Friday, January 25, 2013 11:44:34 AM UTC, Chris Withers wrote:
>
> On 25/01/2013 11:33, cjo wrote: 
> > Are you picking from a fixed set of projects? 
> > 
> > If you are you could try the pull request I created to use the 
> > run-condition plugin on the parameterized trigger plugin which would 
> > allow the decision on if a particular projects is triggered to be 
> > calculated from various options. Including files present, Env matching a 
> > string, etc. 
> > 
> > https://github.com/jenkinsci/parameterized-trigger-plugin/pull/17 
> > https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin 
>
> That does indeed sounds like what I want, when will it make it into a 
> release? 
>
> cheers, 
>
> Chris 
>
> -- 
> Simplistix - Content Management, Batch Processing & Python Consulting 
>  - http://www.simplistix.co.uk 
>

Re: parameterizing which downstream jobs to build

[Chris Withers]

On 25/01/2013 11:33, cjo wrote:

Are you picking from a fixed set of projects?

If you are you could try the pull request I created to use the
run-condition plugin on the parameterized trigger plugin which would
allow the decision on if a particular projects is triggered to be
calculated from various options. Including files present, Env matching a
string, etc.

https://github.com/jenkinsci/parameterized-trigger-plugin/pull/17
https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin


That does indeed sounds like what I want, when will it make it into a 
release?


cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

Re: parameterizing which downstream jobs to build

[cjo]

Are you picking from a fixed set of projects?

If you are you could try the pull request I created to use the 
run-condition plugin on the parameterized trigger plugin which would allow 
the decision on if a particular projects is triggered to be calculated from 
various options. Including files present, Env matching a string, etc. 

https://github.com/jenkinsci/parameterized-trigger-plugin/pull/17
https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin

On Friday, January 25, 2013 11:08:58 AM UTC, Chris Withers wrote:
>
> On 25/01/2013 10:30, CHAVANNE Robert wrote: 
> > It depends on what you call choice. You can use parametrized build. 
> > The parameter would be the name of the job to trigger. 
>
> OK. 
>
> > I don't know if you can choose the job to trigger automatically. 
>
> I was hoping to use logic within the job to pick the name of the 
> downstream job to trigger. Is that possible? 
>
> cheers, 
>
> Chris 
>
> -- 
> Simplistix - Content Management, Batch Processing & Python Consulting 
>  - http://www.simplistix.co.uk 
>

Re: Artifacts and Builds

[Chris Withers]

Hi Paulo,

It's tricky when you start, I remember finding this all a bit confusing too!

On 25/01/2013 11:16, Paulo Matos wrote:

* Builds are the files created during a job.


My understanding is that a build is a specific, numbered run of a job.


So if a job triggers the
creation of 2 files and 3 directories, that's the build and it exists in
the workspace.


Well, the build is a number. Each build uses a workspace, and the job 
may create files in that workspace. Jenkins keeps a copy of the 
workspace for each build, unless you configure it not to...



Artifacts are files/directories that are stored by
jenkins outside the workspace and can be copied between jobs.


Indeed, although they're still tied to a build. An artifact might be 
"'mydist.tgz' from build number 10 of the 'make_things' job".



Now, if this is correct, how does it work when we say: 'keep a maximum
amount of 5 builds'?


That means "keep up to 5 copies of the workspace, one for each build".


Does jenkins take a snapshot of workspace before a
job is run


I think it's after...


and knows what was created during the job execution and makes
that the build?


I believe it's just a copy of the workspace as it was, so no knowledge 
is used...



* If I have a job and create a tarball in a script to use as artifact,
the tarball is created in workspace and then the artifact [tarball] is
copied automatically by jenkins somewhere else.


If you configure the saving of artifacts as a post action.


However the tarball
stays in workspace occupying precious space.  How can I instruct jenkins
that all that is made into an artifact should be removed from workspace?


I think this might be what you're after:

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


* When I run a downstream job and copy artifacts from upstream into
workspace/artifacts, is there a way to remove all the artifacts from
previous build or this needs to be done manually through a script?


You can also configure how long to keep artifacts in old builds...

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

Re: Smart emails

[Slide]

Take a look at the email-ext [1] plugin and see if it fits your needs. I
can do quite a bit.

slide

1 - https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin


On Fri, Jan 25, 2013 at 4:19 AM, Paulo Matos  wrote:

> Hello,
>
> I need smarter email notifications. Mainly I need to know, when jenkins
> starts a job triggered by a git poll, what changed in the repository
> (source code diff between previous build and current build). This should be
> sent at the beginning of a job after the git poll. Can I do this?
>
> Another thing I need is to be able to run a script after a build, and then
> use the output of that script in a notification email. Is it possible to
> achieve this in jenkins?
>
> Thanks,
>
> --
> Paulo Matos
>



-- 
Website: http://earl-of-code.com

Smart emails

[Paulo Matos]

Hello,

I need smarter email notifications. Mainly I need to know, when jenkins 
starts a job triggered by a git poll, what changed in the repository 
(source code diff between previous build and current build). This should 
be sent at the beginning of a job after the git poll. Can I do this?


Another thing I need is to be able to run a script after a build, and 
then use the output of that script in a notification email. Is it 
possible to achieve this in jenkins?


Thanks,

--
Paulo Matos

Artifacts and Builds

[Paulo Matos]

Hi,

I am slightly confused by the difference between artifacts and builds.

Correct me if I am wrong and please add whatever I might have missed.

* Builds are the files created during a job. So if a job triggers the 
creation of 2 files and 3 directories, that's the build and it exists in 
the workspace. Artifacts are files/directories that are stored by 
jenkins outside the workspace and can be copied between jobs.


Now, if this is correct, how does it work when we say: 'keep a maximum 
amount of 5 builds'? Does jenkins take a snapshot of workspace before a 
job is run and knows what was created during the job execution and makes 
that the build?


* If I have a job and create a tarball in a script to use as artifact, 
the tarball is created in workspace and then the artifact [tarball] is 
copied automatically by jenkins somewhere else. However the tarball 
stays in workspace occupying precious space. How can I instruct jenkins 
that all that is made into an artifact should be removed from workspace?


* When I run a downstream job and copy artifacts from upstream into 
workspace/artifacts, is there a way to remove all the artifacts from 
previous build or this needs to be done manually through a script?


I am sorry for all these seemingly trivial questions but a hard thing 
to understand about jenkins is what jenkins can automate and what you 
need to have a script to do it yourself.


--
Paulo Matos

Re: parameterizing which downstream jobs to build

[Chris Withers]

On 25/01/2013 10:30, CHAVANNE Robert wrote:

It depends on what you call choice. You can use parametrized build.
The parameter would be the name of the job to trigger.


OK.


I don't know if you can choose the job to trigger automatically.


I was hoping to use logic within the job to pick the name of the 
downstream job to trigger. Is that possible?


cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

Re: parameterizing which downstream jobs to build

[CHAVANNE Robert]

Chris Withers  simplistix.co.uk> writes:

> 
> Hi All,
> 
> I'd like to have a job do something and then kick off some downstream 
> jobs, but I'd like to make some choices in the job to decide *which* 
> downstream jobs to kick off.
> 
> How can I do that?
> 
> Chris
> 

Hi Chris,

It depends on what you call choice. You can use parametrized build.
The parameter would be the name of the job to trigger.
I don't know if you can choose the job to trigger automatically.

Robert

Re: copy artifacts - pick from two upstream jobs

[Chris Withers]

Hi Fred,

Did you have any joy with this?

I've using 1.25 but can't see anything that would let me specify the 
triggering project in the "Project name" box. I'd imagine it would be 
some kind of place holder variable such as $COPYARTIFACT_UPSTREAM_JOB or 
some such?


cheers,

Chris

 Original Message 
Subject: Re: copy artifacts - pick from two upstream jobs
Date: Fri, 24 Feb 2012 18:54:10 +
From: Chris Withers 
To: jenkinsci-users@googlegroups.com
CC: Fred G 

Hi Fred,

On 21/02/2012 15:23, Fred G wrote:

You can use the "Upstream build that triggered this job"-functionality
of the Copy-Artifacts-Plugin.
Unfortunately you still need to specify the name of the triggering job.
I will try to fix this in an upcoming version.


That would be great :-)


Until then you need to specify two "Copy artifacts from another project"
build steps (one for each triggering project) and mark them as optional.


This works just fine!

thanks,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

viewing build results extremely slow on 1.480.2

[Chris Withers]

Hi All,

I've noticed this a lot since upgrading to 1.480.2, but it's been an 
intermittent problem for a while now..


Going to:

http://:8080/job///

...can take over a minute to render.

How can I figure out why this is taking so long?

cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

copy artifacts question

[Chris Withers]

Hi All,

Is there any way I can get the copy artifacts plugin to copy from the 
last build for which all downstream jobs passed?


cheers,

Chris

--
Simplistix - Content Management, Batch Processing & Python Consulting
- http://www.simplistix.co.uk

Re: Todo notes on a jekinsjob - any add-ins?

[Johannes Wienke]

Hi,

On 25.01.2013 08:56 schrieb Kenneth Nielsen:
> I am in the process of setting up Jenkins on our system.
> And want to stick a note on the different jobs, can that be done in a smart 
> way?
> I want the note to be for each job, but not necessarily stored and 
> published as it would be if i put it in a jobs description.

Maybe you could simply use the job description field for that?

Cheers,
Johannes




signature.asc
Description: OpenPGP digital signature