Re: trigger local jenkins with github
> Hi stefan, > I am also trying to trigger a build job on my local jenkins server from Github webhook. So could you please tell how to make jenkins to publically accesible. Thanks, Sameer Chandekar -- 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/4b335691-0416-441f-b4f9-d79fedfe0f88%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
possible trouble with hue-light plugin
Hi All, We had an issue here that I would like to mention. I did not have time to sort out the exact details, so I will just have some vague info and suspicion. Maybe it rings a bell for someone to act on it. - The first thing we noticed was that our main build was not producing any deliverables anymore, even on green builds. - Investigation showed that all the post build actions had vanished... - I checked the actual config.xml file on the disk: it contained the post build actions as expected, no problem - huh, so jenkins did not read the config correctly? - restart jenkins still no post build actions in the web interface - I dug out that same config from backups over the past few days - I noticed it had exploded from 11k to 324k a few days back - a quick diff showed that the hue-light plugin had dumped a shedload of xml in my config file - huh, more then 300k of config xml to just turn on a light?!? - one of my colleagues had been playing around with some hue lights for some weeks but that seemed to work correctly - and the xml config explosion was only a few days back - I checked the config history from the backup, the hue plugin section in the config was first a modest 9 lines and then suddenly exploded to a whopping 5000 lines - a massive "" entry was added to the config of the hue plugin. - as far as we know there was no manual action at the time of the confg.xml explosion - what else could re-write the config.xml file? The result was that jenkins got lost in the massive xml (or there was an xml error in there, I did not check all 5000 lines!) and jenkins was missing all of our post actions. We needed to get the system in good order again quickly, so I restored a config.xml from a recent backup and restarted jenkins. The post actions have returned and life is good again (without the hue light feedback of course :-(). Any bells ringing for anyone? We will probably try the hue plugin once again, carefully... I will keep this list posted with further experiences. Cheers, Tom -- 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/8c4e5e42-27da-498b-8902-48ab4ee9d018%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[workflow-plugin]: How to read parameters from one step to another
Resending with Subject changed and mrore details on the request. I have below input step: input id: '4a894d73cf15795f912d3ce0f2f54c51', message: 'DEPLOY Parameters', ok: 'Proceed', parameters: [[$class: 'StringParameterDefinition', defaultValue: 'SC', description: '', name: 'projName'], [$class: 'TextParameterDefinition', defaultValue: '1234', description: '', name: 'projID']] How do I read values of the parameters projName and projID in my next steps in work-flow? Regards, Rupali On Thursday, November 20, 2014 7:35:09 PM UTC+5:30, Rupali wrote: > > Hi, > > I am trying beta version of new work-flow plugin. > https://github.com/jenkinsci/workflow-plugin > > I tried some basic steps to run multiple steps one after other in a > workflow using Groovy CPS DSL which are working fine. > But I am unable to read job parameters in in the workflow or parameters > selected as part of one step into another step of same workflow. > Can you advise how to do that? > > Regards, > Rupali > -- 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/6c24c0e1-1147-4058-987c-4436fa716296%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Cannot use mvn -pl ! in Jenkins
Hi Andrew I have the same Problem with Jenkins 1.565.3. Did you or anyone from the Jenkins guys find a workaround for this? Regards, Jacques Am Dienstag, 30. September 2014 03:38:11 UTC+2 schrieb Andrew Yan: > > Hi all, > > I'm pretty new to Jenkins and I'm trying to skip modules by maven reactor > within Jenkins. > > In my Jenkins job, the Build Goals and options looks like this: > > *clean install -U -X -pl !module-to-be-skipped* > > > It gives me error like below: > > [ERROR] Could not find the selected project in the reactor: > !module-to-be-skipped -> [Help 1] > org.apache.maven.MavenExecutionException: Could not find the selected project > in the reactor: !module-to-be-skipped > at > org.apache.maven.DefaultMaven.trimSelectedProjects(DefaultMaven.java:877) > at > org.apache.maven.DefaultMaven.createProjectDependencyGraph(DefaultMaven.java:811) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:261) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) > at > org.jvnet.hudson.maven3.launcher.Maven31Launcher.main(Maven31Launcher.java:132) > 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:606) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:330) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:238) > at jenkins.maven3.agent.Maven31Main.launch(Maven31Main.java:181) > 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:606) > at hudson.maven.Maven3Builder.call(Maven3Builder.java:134) > at hudson.maven.Maven3Builder.call(Maven3Builder.java:69) > at hudson.remoting.UserRequest.perform(UserRequest.java:118) > at hudson.remoting.UserRequest.perform(UserRequest.java:48) > at hudson.remoting.Request$2.run(Request.java:328) > at > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:745) > > > The exact same options work fine on command line. Please help! > > Thanks! > > - Andrew > -- 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/e94cc56b-4c36-4f67-872c-8bafbbc2aa61%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [workflow-plugin] Passing parameters to triggered jobs
Thank you James!
Eventually yes we'd like to merge them all into one job, but since for now
the plugin is missing support for some build steps that we're using, I
guess this is the only way to get it done.
Τη Δευτέρα, 24 Νοεμβρίου 2014 12:19:15 μ.μ. UTC+1, ο χρήστης James Nord
έγραψε:
>
> Hi,
>
> the syntax is something like
>
> ArrayList yourparamaters=new ArrayList();
> yourparamaters.add(new hudson.model.StringParameterValue('PARAM','123'));
>
> build job: 'yourJobNameToBuild', parameters: yourparamaters
>
>
> you can also shorthand this if you don;t need to re-use the same parameters
>
> build job: 'yourJobNameToBuild', parameters: [new hudson.model.
> StringParameterValue('PARAM1','123'), new hudson.model.
> StringParameterValue('PARAM2','345')]
>
>
> However - I would caution against using the workflow to trigger other jobs
> if you can - It's ideal is to self contain the workflow and steps in a
> single place so you don't have configuration sprawl (the workflow and all
> the configuration of it is defined in one single place).
>
> /James
>
>
> On Monday, 24 November 2014 08:10:08 UTC, excessgr wrote:
>>
>> I'm a bit confused as to how to pass parameters to triggered jobs.
>> The snippet generator says I can pass a list of ParameterValues, but I'm
>> really unfamiliar with the internals of jenkins so I'm not sure how I can
>> pass this list.
>>
>> I assume this is what the list should look like:
>> ArrayList parameters=new ArrayList();
>> parameters.add(new hudson.model.StringParameterValue('PARAM','123'));
>>
>>
>> However I'm checking the constructor of the build step and there is no
>> such parameter to pass through.
>> How do I use the setter before the build is executed?
>>
>> 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/7a46830a-f067-4e6a-9fa8-2f9fce467607%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: workflow plugin start parameterized job
Hi Eric
the syntax is something like
ArrayList yourparamaters=new ArrayList();
yourparamaters.add(new hudson.model.StringParameterValue('PARAM','123'));
build job: 'yourJobNameToBuild', parameters: yourparamaters
you can also shorthand this if you don't need to re-use the same parameters
build job: 'yourJobNameToBuild', parameters: [new hudson.model.
StringParameterValue('PARAM1','123'), new hudson.model.StringParameterValue(
'PARAM2','345')]
The next thing you need is the list of parameters the workflow was invoked
with -
(I am guessing from scanning the source - so may not be 100% correct)
The parameters are all exposed to the to the workflow as variables
so parameter "BOB" with value "TrueGent" can be accessed as BOB
e.g.
echo "the value of BOB is " + BOB
if you don't actually know what parameters you want (ie you want all of
them) then I think you need to retreive them programatically (I don't
beleive they are injected as a list of paramatervalues - or a map by
default - so you may require a custom step implementation - however I'm
sure someone will pipe up with a quick and easy way to do it.
/James
However - I would caution against using the workflow to trigger other jobs
if you can - It's ideal is to self contain the workflow and steps in a
single place so you don't have configuration sprawl (the workflow and all
the configuration of it is defined in one single place).
/James
On Thursday, 20 November 2014 18:01:07 UTC, Eric Engel wrote:
>
> Resending with correct subject
>
> -Ursprüngliche Nachricht-
> Von: jenkins...@googlegroups.com [mailto:
> jenkins...@googlegroups.com ] Im Auftrag von Eric Engel
> Gesendet: Donnerstag, 20. November 2014 16:33
> An: jenkins...@googlegroups.com
> Betreff: AW: Last Success shows unexpected time
>
> Hello Jenkins Users,
>
> we want to try the new jenkins workflow-plugin. Is there any documentation
> besides the information from github
> https://github.com/jenkinsci/workflow-plugin ?
> Especially a simple question: How to start a parameterized job? Ideally
> with all parameters from the parent job.
>
> Regards,
> Eric
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-use...@googlegroups.com .
> For more options, visit https://groups.google.com/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/8574c186-9c3d-426e-808d-febe7348dc43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [workflow-plugin] Passing parameters to triggered jobs
Hi,
the syntax is something like
ArrayList yourparamaters=new ArrayList();
yourparamaters.add(new hudson.model.StringParameterValue('PARAM','123'));
build job: 'yourJobNameToBuild', parameters: yourparamaters
you can also shorthand this if you don;t need to re-use the same parameters
build job: 'yourJobNameToBuild', parameters: [new hudson.model.
StringParameterValue('PARAM1','123'), new hudson.model.StringParameterValue(
'PARAM2','345')]
However - I would caution against using the workflow to trigger other jobs
if you can - It's ideal is to self contain the workflow and steps in a
single place so you don't have configuration sprawl (the workflow and all
the configuration of it is defined in one single place).
/James
On Monday, 24 November 2014 08:10:08 UTC, excessgr wrote:
>
> I'm a bit confused as to how to pass parameters to triggered jobs.
> The snippet generator says I can pass a list of ParameterValues, but I'm
> really unfamiliar with the internals of jenkins so I'm not sure how I can
> pass this list.
>
> I assume this is what the list should look like:
> ArrayList parameters=new ArrayList();
> parameters.add(new hudson.model.StringParameterValue('PARAM','123'));
>
>
> However I'm checking the constructor of the build step and there is no
> such parameter to pass through.
> How do I use the setter before the build is executed?
>
> 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/097cb936-d309-4c4e-9877-a2969a506ca8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Designing pre-tested commit strategy with jenkins and git repo
HI, I'm not entirely sure what Team City does - and how tied into your git infrastructure you are - but Gerrit[1] along with the gerrit trigger plugin can provide a pre-tested commit if you can change your git server (or put something infront of it and make all users push to gerrit). There is also the pretested integration plugin[2] and also a commercial solution provided by cloudbees[3]. /James [1] https://code.google.com/p/gerrit/ [2] https://wiki.jenkins-ci.org/display/JENKINS/Pretested+Integration+Plugin [3] https://www.cloudbees.com/products/jenkins-enterprise/plugins/validated-merge-plugin On Sunday, 23 November 2014 12:28:59 UTC, Ashish Sharma wrote: > > Hi, > > I am trying to design a pre-tested commit strategy with Jenkins and git , > > As such I want to replicate the TeamCity functionality using Jenkins and > other open source modules, is any such plugin available with Jenkins for > such said functionality? > > Moreover I found one plugin ( > https://wiki.jenkins-ci.org/display/JENKINS/Designing+pre-tested+commit) > but it provides a totally different strategy as provided by TeamCity. > > Please help. > > Thanks in advance > Ashish > -- 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/a98d664d-b7dc-4a1d-8df4-08d7d28075af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[workflow-plugin] Passing parameters to triggered jobs
I'm a bit confused as to how to pass parameters to triggered jobs.
The snippet generator says I can pass a list of ParameterValues, but I'm
really unfamiliar with the internals of jenkins so I'm not sure how I can
pass this list.
I assume this is what the list should look like:
ArrayList parameters=new ArrayList();
parameters.add(new hudson.model.StringParameterValue('PARAM','123'));
However I'm checking the constructor of the build step and there is no such
parameter to pass through.
How do I use the setter before the build is executed?
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/873da203-e57d-4e0c-a2f8-7c83bffe3ff2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
