Subscribe

2019-09-30 Thread Kaliyug Antagonist
-- 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.c

'Include' a shared library pipeline in other pipelines in the same shared library

2019-09-30 Thread Kaliyug Antagonist
I have several microservices which use the same pipeline from a shared library which is named *jenkins-shared-pipelines* . The Jenkinsfile for a microservice is as follows: @Library(['jenkins-shared-pipelines']) _ gradleProjectPrPipeli

Re: 'Include' a shared library pipeline in other pipelines in the same shared library

2019-09-30 Thread Kaliyug Antagonist
On Monday, September 30, 2019 at 9:35:30 AM UTC+2, Kaliyug Antagonist wrote: > > I have several microservices which use the same pipeline from a shared > library which is > named *jenkins-shared-pipelines* . The Jenkinsfile for a microser

Re: 'Include' a shared library pipeline in other pipelines in the same shared library

2019-09-30 Thread Kaliyug Antagonist
*Note:* - The workspace(where the clone stag checks out the code and later stages operate) will be used by awsPipeline etc. In other words, the variables and results from the gradleProjectBranchWrapper should be accessible to the awsPipeline etc. - There is a post block in the

Clean useless files and directories

2019-09-30 Thread Peter Flanagan
Hello, working on Jenkins 2.150 hosted on on AWS-EC2, jenkins_home dir is located on an EFS The space of some Jenkins instances increase dramatically due to folder not removed automatically by internal Jenkins storage management. Using multi-branch jobs I got 2 major issues: - some branches dir

Docker plugin running / failing on 'docker login' command

2019-09-30 Thread No-one
*Scenario:* We have Docker ephemeral build agents running on the Linux side via the Docker Jenkins plugin and the *docker *declarative pipeline syntax. We want to mimic that setup on the Windows side. *Setup:* - Docker engine installed in Windows server 2016 - Everything locally on that h