We use the jobDSL to manage the 10 different jobs for the 100+ Git
repositories we have. We are trying to reduce the number of jobs per
repository by using a pipeline library in combination with a Jenkinsfile in
each repository.

The original jobs:
- Build develop with deploy to Nexus
- Build feature branch with / without deploy to Nexus
- Update dependencies, test and commit.
- Start release
- Finish release
- OWASP build on master
- OWASP build on develop
- Sonar build on master
- Sonar build on develop
- Sonar build on featurebranch / PR

With new Maven Pipeline library:
- Start release
- Finish release
- Multibranch job based on Jenkinsfile
-- Runs:
* mvn process-test-classes
* mvn post-integration-test
* mvn verify -DskipTests
* Parallel OWASP and Sonar
* mvn deploy -DskipTests

If you want some more information, please let me know.

With regards,

Nick Stolwijk

~~~ Try to leave this world a little better than you found it and, when
your turn comes to die, you can die happy in feeling that at any rate you
have not wasted your time but have done your best ~~~

Lord Baden-Powell


On Wed, Apr 15, 2020 at 3:12 PM marouane zhani <marouane1993zh...@gmail.com>
wrote:

> Hi Marcin,
>
> I have the same needs actually, do you have a working solution for that ?
> I have tried a bit the Inheritance plugin (
> https://plugins.jenkins.io/project-inheritance/) but I am still having
> some problems with it.
>
> Looking forward to your reply.
> Kind regards,
> Marouane
>
> Le dimanche 18 novembre 2012 04:56:52 UTC+1, Marcin Biegan a écrit :
>>
>> It does not suite my needs, it just allows to organize multiple jobs
>> which are supposed to all be triggered by the same event, am I
>> correct?
>>
>> My jobs are pretty similar to each other - ex. build jobs have the
>> same configuration except svn url, downstream jobs list and maybe some
>> details (like email notification triggers), all other properties are
>> equal. But they are triggered at different times as they relate to
>> different projects. What I'm looking for is more like configuration
>> inheritance, where I'd need to change job configuration property once,
>> in only one place (in the 'base' job) instead of per each job (plus
>> possibility to override at job level).
>> Maybe there is possibility to use configuration slicing plugin without
>> admin permissions? That would partially work
>>
>> Thanks
>> Marcin
>>
>> On Nov 15, 5:48 pm, Marek Gimza <marekgi...@gmail.com> wrote:
>> > Marcin,
>> >
>> > Do you know about the "MultiJob" plugin?
>> >
>> > https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin
>> >
>> > Regards,
>> > Mgimza
>> >
>> > On Wed, Nov 14, 2012 at 7:39 PM, Marcin Biegan 
>> > <marcin.bie...@gmail.com>wrote:
>>
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > > Hi,
>> >
>> > > I wanted to ask how do you handle configuring multiple jobs. We have
>> > > about 10 maven projects to build in at least 2 versions (trunk/
>> > > branch), which makes 20 jobs, some more for additional tests,
>> > > releases, maybe deployment, verification, etc. Manually adding
>> > > permissions and adjusting configuration of jobs is cumbersome. Is
>> > > there a working plugin which would allow to set some 'parent' job
>> > > which would define default configuration? (Template Project Plugin is
>> > > not enough, because it 'works' only at job creation). I know also
>> > > about Configuration Slicing Plugin, but this will not work in my case
>> > > as it requires admin permissions.
>> >
>> > > Thanks
>> > > Marcin Biegan
>>
> --
> 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/0341ccd4-052b-4890-a49a-6510e50e79e6%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/0341ccd4-052b-4890-a49a-6510e50e79e6%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAA9S6i4p471waoUqrb8GC%3DMPeV5Z1yR4K%3D1xMuyWWWqyfZKaBg%40mail.gmail.com.

Reply via email to