Re: CLI Created Jobs Do Not Run

[Hilco Wijbenga]

On 8 October 2015 at 15:09, Hilco Wijbenga  wrote:
> I am experiencing a strange issue. I am successfully creating new jobs using
> Jenkins CLI "create-job" + "enable-job" but these jobs are not triggered
> (they use "Build Periodically"). If I go in and change something through the
> UI (e.g., I change H/10 * * * * to H/10 * * * 1-7), then all of a sudden the
> build *does* get triggered. So it looks like something is not happening when
> calling "create-job" (or "enable-job"?) that *is* happening when creating a
> job through the UI. Any ideas?

It is in fact not even necessary to change anything in the
configuration. If I simply click "configure" and then "Save", the job
is triggered normally from then on.

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

CLI Created Jobs Do Not Run

[Hilco Wijbenga]

Hi all,

I am experiencing a strange issue. I am successfully creating new jobs 
using Jenkins CLI "create-job" + "enable-job" but these jobs are not 
triggered (they use "Build Periodically"). If I go in and change something 
through the UI (e.g., I change H/10 * * * * to H/10 * * * 1-7), then all of 
a sudden the build *does* get triggered. So it looks like something is not 
happening when calling "create-job" (or "enable-job"?) that *is* happening 
when creating a job through the UI. Any ideas?

1) After making a change in the UI, I do not see any (other) change in 
config.xml.
2) I noticed not all of the "last*Build" links exist for the jobs that had 
never run but creating them did not change anything. (Hey, I was grasping 
at straws.)

Cheers,
Hilco

Jenkins 1.631

-- 
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/6f836aa5-f3cc-4e6b-a074-40cf49ea920d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gerrit Trigger Password Troubles

[Justin Fehr]

I downgraded to 1.609 and am still seeing the issue. I am wondering if this 
is a bug that has been around for a while, my guess (although I can't 
confirm) is that it does not affect users who already have it set up. only 
users trying to change or set a password for the first time.

On Wednesday, October 7, 2015 at 4:10:03 PM UTC-5, Justin Fehr wrote:
>
> Hi all. Disclaimer, Im new to Jenkins. Anyways I am trying to set up 
> Jenkins with the Gerrit Trigger to run builds as patch sets are pushed to 
> our gerrit server.  I go through the settings and set up the connection and 
> test the connection. the connection is successful. Then I save my settings 
> which takes me back to the gerrit trigger page. When I open the settings I 
> just saved and test the connection it fails. When I re-enter the ssh 
> keyfile password and test again it works. From my testing I can conclude 
> that the problem is from saving it seems to be changing or corrupting the 
> password. Similarly I am seeing the same issue with the rest api http 
> password. I have tried this with 1.631 and 1.632 current core releases, as 
> well as 1.625 of the LTS version. My gerrit trigger version is 2.16.0 any 
> help would be greatly appreciated. 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/6b19fe64-5a2e-4ea2-8d08-12e81f7834ba%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

is 51,000 tests too much in a job?

[Kevin Goess]

Is 51,000 tests too much in a single job?

We're seeing painful slowdowns in the Jenkins UI and this question came up. 
 Our junit.xml file is about 17MB in size.  Are other people running that 
number of tests successfully?




-- 
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/9be581c9-263b-457a-ab06-6fabcdbd0b6d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Workflow manual input step: how do I use it the right way?

[Martin d'Anjou]

I think I am using the Workflow manual input step incorrectly. I must 
misunderstand the problem it solves.

My pipeline has several steps:
1) compiler phase 1 and test (1 hour)
3) manually decide whether to stop or continue to step 4
4) compiler phase 2 and more tests (2 to 4 hours)
5) manually decide whether to stop or continue to step 6
6) deploy to dev
7) manually decide whether to stop or continue to step 8
8) deploy to production

Only a few, out of thousands, make it to production. When I use the 
Workflow plugin with the manual input step, it leaves builds with balls 
blinking waiting for user input. Also, pausing eventually blocks all 
execution slots. With thousands of builds, this can't be right.

This cannot be how the manual input is intended to work. How do people do 
manual build steps that depend on upstream jobs?

Thanks,
Martin

-- 
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/d4e00c68-787e-451e-a1f7-dcf8b627d431%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Simple Plugin Theme Store

[Kayn Ty]

i approve that idea.
it could be great to have a link to that central place on the Simple Theme 
Plugin readme, https://github.com/mallowlabs/simple-theme-plugin and in the 
official jenkins website.

Le dimanche 6 septembre 2015 18:38:10 UTC+2, Lewis England a écrit :
>
> Hi everybody, 
>
> I'm a guy who loves customisation, and the Jenkins Simple Theme Plugin was 
> a wonderful thing for me. 
> I have been using it for a while and found out many wonderful things that 
> I can tweak and theme.
>
> However, it has come to my attention that there is no central theme 
> repository or theme catalogue for this plugin. 
> This is where I feel I can step in, but I'd like to get an idea on 
> interest.
>
> MY PLAN:
>  - Create a database and interface for completed / WIP Jenkins Themes 
> (names, descriptions, screenshots)
>  - Allow users to upload to it (ZIP file with CSS, JS and other theme 
> files)
>  - Allow links back to the original source, guessing GitHub, for community 
> contribution (and other classic GitHub uses)
>  - Ratings, comments, tags and all the other standard stuff.
>
> REASON:
> Jenkins is a highly versatile system and I'm sure that those who are 
> installing the Simple Theme plugin are the kind of people who are not a fan 
> of the default UI.
> Also, I personally am not too keen on searching around the internet for 
> theme ideas / source to get started with. 
>
> Please let me know who is interested in this idea / who would like to help 
> out.
>
>

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

Re: Preventing two jobs to run simultaneously on same node but allowing to run simultaneously on different nodes

[Catalyst Approva]

Thanks Victor!
Throttle concurrent build plugin did work. It seems i had incorrectly
configured it previously but its working now. Thanks again!

On Mon, Sep 28, 2015 at 3:50 PM, Victor Martinez <
victormartinezru...@gmail.com> wrote:

> Hi there,
>
>  I believe "Throttle concurrent builds" plugin should work, in fact, it's
> exactly what I don in roder to run different builds. Have you tried with
> the below setup?
>
>
> 
>
>   I'm based on:
> - Jenkins ver. 1.599
> - throttle-concurrents ver. 1.8.3
>
> I hope it helps
>
> Cheers
>
> On Monday, 28 September 2015 09:35:14 UTC+2, ozonec...@gmail.com wrote:
>>
>> Hi Jenkins Users,
>>
>> I am using *Jenkins 1.609*
>>
>> I have a requirement wherein
>>
>> *1) no two jobs can execute simultaneously on the same node but 2) they
>> can execute simultaneously when triggered on different nodes.*
>> No of executors configured on all slave nodes is 1.
>>
>> Default Jenkins behavior:
>> If job A and job B, both are triggered on same node then Job B goes in
>> executor starvation state because build is waiting for "too long" compared
>> to the time it takes to execute it. Once job B goes in this state, it gets
>> stuck and is not picked up for building.
>>
>> Have tried using "Exclusion plugin". It helps in achieving first point
>> but not the second one.
>> Also, have tried using Throttle concurrent builds plugin but still Job B
>> goes into executor starvation state.
>>
>> Is there any way wherein I can achieve both the points i.e. prevent
>> running the jobs simultaneously on same node but can run on different nodes
>> and without the second job going into executor starvation state as I cannot
>> change the sequence of the jobs??
>>
>> Thanks in advance!
>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/F-AeRRUYWXg/unsubscribe.
> To unsubscribe from this group and all its topics, 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/d1684b31-8673-48c8-9a86-233b9ed8b3e6%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/CANv-LvKENOYj2Rrhb5LfcwF76kQUiM%2B7qwXd_8J5WKTiF05Pew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to Deploy the jar file through jenkins after build process

[Maciej Jaros]

sumanth veera (2015-10-04 16:35):

Hi All,

 i am trying to Deploy the jar files to remote server from the 
artifacts created.after the build process can any one tell me how to 
do this .


Basically i need to deploy the jar to remote server.


If you have many servers (or plan to grow) it might be easier to setup 
certificate authentication through SSH. This allows easier 
parametrization and making easier to read scripts.


Basic steps are (assuming your Jenkins and remote server is Linux based):

1. Generate your local key (use a default options to generate
   password-less authentication):
   ssh-keygen -b 4096
2. Copy your key to remote server:
   ssh-copy-id username@remote_host
3. Test login:
   ssh username@remote_host

Note that from now on anyone having the certificate will be able to 
connect to your remote host. So some extra security measures might be 
required (e.g. enabling drive encryption).


So to copy a file you just execute shell script:
connectionString=username@remote_host
scp /some/local/file.jar $connectionString:/some/remote/file.jar

You can also run scripts:
scp /some/local/file.sh $connectionString:/some/remote/file.sh
ssh $connectionString /some/remote/file.sh

Or copy whole folder to remote:
scp -r /some/local/dir/ $connectionString:/some/remote/dir

Or you can copy remote folder to your jenkins:
scp -r $connectionString:/some/remote/dir /some/local/dir/

Regards,
Nux.

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