Re: how to define multibranch pipeline with jenkinsfile from another repository (or hardcoded)?

[Tom Brus]

Thanks for the quick reply Daniel!

I am in the process of setting up an extra *jenkins library* repo and using 
the *Pipeline Multibranch Defaults* plugin as you indicated.
This way I do not need any stubs in Repo-A which is my preference.
It looks good until now, although it feels like a workaround in various 
ways.

I am a bit confused why these pipeline plugins lack some abviously useful 
features that seem pretty simple to implement:

   - Why does the *Pipeline Multibranch* plugin not have the two options 
   that the *Pipeline *plugin has?
  - *Pipeline Script* (for script in the job)
  - *Pipeline Script from SCM* (for script from some SCM)
   - Why is there a separate *Pipeline Multibranch Defaults *plugin to only 
   add that one extra option
   - Why can I only define a jenkins library in *the root* of a SCM-repo? 
   (now I need to maintain an extra repo)
   - Why can I not include a declarative pipeline in another declarative 
   pipeline? (seems simple, but there seem to be technical issues...)

Anyway, thanks again for the pointers and workaround, they are happily 
accepted!

Greetings,
Tom Brus


Op donderdag 4 juli 2019 15:39:00 UTC+2 schreef Daniel Butler:
>
> You could use the Pipeline Multibranch Defaults plugin which does the 
> hardcoded in the job approach
>
> https://github.com/jenkinsci/pipeline-multibranch-defaults-plugin/blob/master/README.md
>
> If a stub file in Repo-A is acceptable you could also use a shared library 
> to store the actual jenkinsfile as a script and the stub just contains
> doRepoBuild() or similar which is the way jenkins plugin builds share 
> build scripting. The blog post 
> https://jenkins.io/blog/2017/10/02/pipeline-templates-with-shared-libraries/ 
> runs through a more elaborate example with a bunch of parameters to a 
> similar end.
>
> There are a few users which have done the parallel repo approach but I'm 
> not myself sure of the details.
>
> Regards,
> Daniel
>
> On Thu, Jul 4, 2019 at 1:51 PM Tom Brus > 
> wrote:
>
>> Hi,
>>
>> I have a repos I want to build all branches for (repos-A).
>> I do not want to put any jenkinsfiles (or any other build related stuff) 
>> into this repos.
>> My jenkinsfile lives in a separate repos (repos-B).
>>
>> So I need the branches from repos-A and I need the jenkinsfile to build 
>> with from repos-B.
>>
>> How can I set this up?
>>
>> - the *Pipeline Multibranch Plugin* only seems to allow "*by Jenkinsfile*" 
>> for *mode*
>> - the *Multi-Branch Project Plugin* is deprecated so I like to stay away 
>> from it
>> - I could live with a hardcaded jenkinsfile in the job itself
>>
>> Any help welcome!
>> Tom Brus
>>
>> -- 
>> 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 jenkins...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/a86e14e1-f39c-4616-92b0-957cdc3374c1%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-users/a86e14e1-f39c-4616-92b0-957cdc3374c1%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> 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/39f2d867-40b5-4d51-99c0-2d61fc929ea9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

how to define multibranch pipeline with jenkinsfile from another repository (or hardcoded)?

[Tom Brus]

Hi,

I have a repos I want to build all branches for (repos-A).
I do not want to put any jenkinsfiles (or any other build related stuff) 
into this repos.
My jenkinsfile lives in a separate repos (repos-B).

So I need the branches from repos-A and I need the jenkinsfile to build 
with from repos-B.

How can I set this up?

- the *Pipeline Multibranch Plugin* only seems to allow "*by Jenkinsfile*" 
for *mode*
- the *Multi-Branch Project Plugin* is deprecated so I like to stay away 
from it
- I could live with a hardcaded jenkinsfile in the job itself

Any help welcome!
Tom Brus

-- 
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/a86e14e1-f39c-4616-92b0-957cdc3374c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

build history pagination downside

[Tom Brus]

Hi,

Just installed 1.633 and I discovered the new *Build History* layout.
I must say, I did not carefully read through all the jira's about this (
JENKINS-26445 , ...), 
so I might have missed something...

There are many good things about this improvement but what I do not like is 
that all my builds that are "kept forever" seem to end up at the top of the 
list. For some jobs we have a lot of "kept forever" builds and that pushes 
down the latest builds, which are far more relevant to me most of the time.

Is there any way I can tweak this behaviour?

Regards,
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/eea876fb-a028-4db4-85cb-0f346cd872a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

scheduled jobs not starting

[Tom Brus]

Hi,

I recently updated to Jenkins 1.616 and now I see some of my nightly 
scheduled jobs not starting.

I see this behaviour in several jobs. One has the following crontab:

0 1 * * 1-6


another has this crontab:

0 1 * * 0


This Sunday-one did not run last weekend, the weekly one above ran some 
nights but not all.

I see no interesting traces in the jenkins log files.

Is this something others have encountered as well?


I scanned the jenkins sources and saw some recent changes in the 
*CronTab.java* source marked as @since 1.615. I did not check the sanity 
of these changes, just noticed that there were recent changes.

Hope I am not the only one... ;-)

-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/75e796f8-d3f5-4625-bf0e-f0818b88536b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

possible trouble with hue-light plugin

[Tom Brus]

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

URGENT: trouble in jenkins downloads

[Tom Brus]

Hi All,

I had my jenkins install (apt-get) on ubuntu failing with:

Failed to fetch 
http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb  404  Not 
Found


Then I discovered that the *Latest and greatest 
(1.519)http://mirrors.jenkins-ci.org/war/latest/jenkins.war
* on http://jenkins-ci.org/ is a dead link.
Strangely enough I end up at 
http://fallback.jenkins-ci.org/war/1.518/jenkins.war, which has a different 
number (518 not 519).

On http://pkg.jenkins-ci.org/debian/ the latest link 
(jenkins_1.518_all.debhttp://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb
 to 
http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb) is dead as 
well.

I guess something went wrong somewhere... :-(

-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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: URGENT: trouble in jenkins downloads

[Tom Brus]

no paradise without trouble, I guess ;-)

Op dinsdag 18 juni 2013 15:29:26 UTC+2 schreef Kevin Fleming het volgende:

 Yes, it's rather disconcerting that a continuous integration tool suffers 
 from release process failures, when such processes are eminently 
 automatable :-)

 - Original Message -
 From: jenkins...@googlegroups.com javascript:
 To: jenkins...@googlegroups.com javascript:
 At: Jun 18 2013 08:08:01

 Hi All,

 I had my jenkins install (apt-get) on ubuntu failing with:

 Failed to fetch 
 http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb  404  Not 
 Found


 Then I discovered that the *Latest and greatest 
 (1.519)http://mirrors.jenkins-ci.org/war/latest/jenkins.war
 * on http://jenkins-ci.org/ is a dead link.
 Strangely enough I end up at 
 http://fallback.jenkins-ci.org/war/1.518/jenkins.war, which has a 
 different number (518 not 519).

 On http://pkg.jenkins-ci.org/debian/ the latest link (
 jenkins_1.518_all.debhttp://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb
  to 
 http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb) is dead as 
 well.

 I guess something went wrong somewhere... :-(

 -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-use...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/groups/opt_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.
For more options, visit https://groups.google.com/groups/opt_out.

Re: URGENT: trouble in jenkins downloads

[Tom Brus]

seems to be solved now, at least ubuntu can install again...

Op dinsdag 18 juni 2013 14:07:30 UTC+2 schreef Tom Brus het volgende:

 Hi All,

 I had my jenkins install (apt-get) on ubuntu failing with:

 Failed to fetch 
 http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb  404  Not 
 Found


 Then I discovered that the *Latest and greatest 
 (1.519)http://mirrors.jenkins-ci.org/war/latest/jenkins.war
 * on http://jenkins-ci.org/ is a dead link.
 Strangely enough I end up at 
 http://fallback.jenkins-ci.org/war/1.518/jenkins.war, which has a 
 different number (518 not 519).

 On http://pkg.jenkins-ci.org/debian/ the latest link (
 jenkins_1.518_all.debhttp://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb
  to 
 http://pkg.jenkins-ci.org/debian/binary/jenkins_1.518_all.deb) is dead as 
 well.

 I guess something went wrong somewhere... :-(

 -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.
For more options, visit https://groups.google.com/groups/opt_out.

config.xml missing after install

[Tom Brus]

Hi,

I install jenkins on ubuntu (in a script) and I would like to tweak the 
config.xml file (to add security stuff).
The problem is that right after install the config.xml file is missing. 
Jenkins is running properly though.
If I browse to my new jenkins and do something (e.g. set security) the 
config.xml file is generated.
But I do not want any manual interaction at this stage.

Is there a way to force jenkins to write that file so I can tweak it?

Thanks,
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.
For more options, visit https://groups.google.com/groups/opt_out.