[JIRA] (JENKINS-60546) job-dsl triggers all jobs in organizationFolder on second seed job run

2019-12-19 Thread alius.mi...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Taras Bondarchuk created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60546  
 
 
  job-dsl triggers all jobs in organizationFolder on second seed job run   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Spilker  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2019-12-19 17:07  
 
 
Environment: 
 Jenkins ver. 2.204.1  job-dsl-plugin 1.76  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Taras Bondarchuk  
 

  
 
 
 
 

 
 On second run of seed job JobDSL recreates organizationFolders and triggers build for all jobs in it, with build cause 'Branch indexing'. SkipInitialBuildOnFirstBranchIndexing is configured in build strategies, and first run of seed job is indeed skipping builds, but second run seems to ignore that. Are there any ways to prevent this? My understanding is that for MultiBranchPipeline it's done by 'id' parameter, but what about all mutlibranch pipelines created by organizationFolder? Possible hack to diminish impact is to add when clause to all pipelines to skip stages on Branch Indexing, but that's way less then optimal: 

 

when {
 not {
   triggeredBy 'BranchIndexingCause'
 }
} 

    

[JIRA] (JENKINS-47026) User not completely set in docker containers

2018-02-14 Thread alius.mi...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Taras Bondarchuk commented on  JENKINS-47026  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User not completely set in docker containers   
 

  
 
 
 
 

 
 Since I'm building agent from Dockerfile anyway, I've fixed this by:   

 

agent {
   dockerfile {
  additionalBuildArgs '--build-arg USER_ID=$(id -u) --build-arg GROUP_ID=$(id -g)'
   }
}
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[JIRA] (JENKINS-47026) User not completely set in docker containers

2018-02-14 Thread alius.mi...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Taras Bondarchuk edited a comment on  JENKINS-47026  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User not completely set in docker containers   
 

  
 
 
 
 

 
 Since I'm building agent from Dockerfile anyway, I've fixed this by: {code:java}agent {   dockerfile {  additionalBuildArgs '--build-arg USER_ID=$(id -u) --build-arg GROUP_ID=$(id -g)'   }}{code} and in Dockerfile: {code:java}ARG USER_ID=1000ARG GROUP_ID=1000RUN groupadd -g $GROUP_ID user && \useradd -u $USER_ID -s /bin/sh -g user user{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.