[JIRA] (JENKINS-54515) master triggers own branches
Title: Message Title Cyrille Le Clerc closed an issue as Fixed Jenkins / JENKINS-54515 master triggers own branches Change By: Cyrille Le Clerc Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title Thorsten Langer commented on JENKINS-54515 Re: master triggers own branches We can confirm, that the triggering from master to branches does not occur anymore. We tested this using the standard DB, because changing the DB to the MySQL version mentioned above was a bit tricky in our setup. In the log-file we cannot see any of these skip-messages you expected. Please note, that the branches (jobs) are still listed as downstream jobs of master job in the maven tab in the classic website. Thank you very much! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title dan tran edited a comment on JENKINS-54515 Re: master triggers own branches on the second thought, i am going to create a delegate job to invoke my sub jobs directly. So we good ( a --> b --> delegate --> c,e,f etc )but, it would be great to have this fixed fix :) https://issues.jenkins-ci.org/browse/JENKINS-53382 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title dan tran edited a comment on JENKINS-54515 Re: master triggers own branches on the second thought, i am going to create a delegate job to trigger invoke my sub builds jobs directly . So we good ( a --> b --> delegate --> c,e,f etc )but, it would be great to this fixed :) https://issues.jenkins-ci.org/browse/JENKINS-53382 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title dan tran commented on JENKINS-54515 Re: master triggers own branches on the second thought, i am going to create a delegate job to trigger my sub builds. So we good ( a --> b --> delegate --> c,e,f etc ) but, it would be great to this fixed https://issues.jenkins-ci.org/browse/JENKINS-53382 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title dan tran commented on JENKINS-54515 Re: master triggers own branches We have one large repo with 400+ maven modules including both production and integration test sources. Main repo build (~60min) does build integration test modules abut not running them. We also have many wrapper repos clone the main repo at build time and run * subset of integration tests at each repo ( ie main build trigger a number of parallel integration test builds * Platform sanity builds ( windows, etc) Merge them into a single pipeline are big, complex, and long. is there a way to disable maven pipeline event listener after we clone the main repo at the test pipelines? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title Cyrille Le Clerc updated JENKINS-54515 Fixed in 3.6.4 Jenkins / JENKINS-54515 master triggers own branches Change By: Cyrille Le Clerc Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title Cyrille Le Clerc commented on JENKINS-54515 Re: master triggers own branches dan tran we brainstormed with Arnaud Héritier and we felt that a reasonable default behaviour would be to not trigger pipelines that work on the same pom.xml. The implementation we chose, as we don't capture for the moment the pom.xml details (1), is to not trigger pipeline that generate the artifact that would be the reason of the trigger. This solution is fixing all the problems of multi-module Maven projects with multiple git branches but is unfortunately excluding your scenario. How frequent in your organisation is this scenario of chaining pipeline using same pom.xml? How many Maven apps do you build? How many Maven pipelines do you have? How many of such chain of pipelines do you have? Did you consider merging these chained pipelines in a single pipeline job? Did you face problems trying this? (1) SCM details + path in the SCM repo + introducing a POM entity in our data model between the builds and the dependency Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title dan tran edited a comment on JENKINS-54515 Re: master triggers own branches Unfortunately, my downstream pipelines do generate the same artifact ( just not deploy to maven repo). am I toasted?Use case: one main pipeline ( mvn deploy) triggers a number of pipeline using same source to run integrations in parallel ( mvn install) . See # JENKINS-53382 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title dan tran edited a comment on JENKINS-54515 Re: master triggers own branches Unfortunately, my downstream does pipelines do generate the same artifact ( just not deploy to maven repo). am I toasted?Use case: one main pipeline ( mvn deploy) triggers a number of pipeline using same source to run integrations in parallel ( mvn install) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title dan tran commented on JENKINS-54515 Re: master triggers own branches Unfortunately, my downstream does generate the same artifact ( just not deploy to maven repo). am I toasted? Use case: one main pipeline ( mvn deploy) triggers a number of pipeline using same source to run integrations in parallel ( mvn install) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title Cyrille Le Clerc commented on JENKINS-54515 Re: master triggers own branches Shipped in v3.6.4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title Cyrille Le Clerc commented on JENKINS-54515 Re: master triggers own branches Thanks Thorsten Langer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title Thorsten Langer commented on JENKINS-54515 Re: master triggers own branches Hello! Thank you for your efforts so far. It might take a few more days for us to test, but I will answer you here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-54515
Re: master triggers own branches
* Please test beta version 3.6.4-beta-1* To verify, please enable logs {{org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener}} at the FINE level and see message such as {noformat}[withMaven] downstreamPipelineTriggerRunListener - Skip triggering my-multi-jar-project » PR-1 for MavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-SNAPSHOT(version: 0.0.1-20181202.224248-35, snapshot:true) } because it generates artifact with same groupId:artifactId MavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-20181202.224107-34(version: 0.0.1-SNAPSHOT, snapshot:true) }{noformat}* Please ensure that you use a MySQL database instead of the embedded H2 database as documented in " [Using a MySQL Database|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-UsingaMySQLDatabase(since3.6.0)] " To download 3.6.4-beta-1: https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.4-beta-1
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-54515) master triggers own branches
Title: Message Title
Cyrille Le Clerc edited a comment on JENKINS-54515
Re: master triggers own branches
* Please test beta version 3.6.4-beta-1* To verify, please enable logs {{org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener}} at the FINE level and see message such as{noformat}[withMaven] downstreamPipelineTriggerRunListener - Skip triggering my-multi-jar-project » PR-1 forMavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-SNAPSHOT(version: 0.0.1-20181202.224248-35, snapshot:true) }because it generates artifact with same groupId:artifactIdMavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-20181202.224107-34(version: 0.0.1-SNAPSHOT, snapshot:true) }{noformat}* Please ensure that you use a MySQL database instead of the embedded H2 database as documented in [Using a MySQL Database|https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-UsingaMySQLDatabase(since3.6.0)]To download 3.6.4-beta-1: https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.4-beta-1
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-54515) master triggers own branches
Title: Message Title
Cyrille Le Clerc commented on JENKINS-54515
Re: master triggers own branches
Please test beta version 3.6.4-beta-1
To verify, please enable logs org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener at the FINE level and see message such as
[withMaven] downstreamPipelineTriggerRunListener - Skip triggering my-multi-jar-project » PR-1 for MavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-SNAPSHOT(version: 0.0.1-20181202.224248-35, snapshot:true) } because it generates artifact with same groupId:artifactId MavenArtifact{com.example.multi-jar:shared-core:jar:0.0.1-20181202.224107-34(version: 0.0.1-SNAPSHOT, snapshot:true) }
Please ensure that you use a MySQL database instead of the embedded H2 database as documented in Using a MySQL Database
To download 3.6.4-beta-1: https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.4-beta-1
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-54515) master triggers own branches
Title: Message Title Cyrille Le Clerc updated JENKINS-54515 Jenkins / JENKINS-54515 master triggers own branches Change By: Cyrille Le Clerc Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title Cyrille Le Clerc started work on JENKINS-54515 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title
Thorsten Langer commented on JENKINS-54515
Re: master triggers own branches
I can confirm this.
identical repos in 'master' and any branch.
identical pom.xml files in master and usually all branches. (at least in regard to all poms' own project/group|artifactId|version in top level and modules).
identical Jenkinsfile (see below)
but: different (git) branches. The distinction per {{when { buildingTag() } }} works quite fine
#!/usr/bin/env groovy
pipeline {
agent any
tools {
maven 'apache-maven-3.3.9'
jdk 'jdk1.8.0-latest'
}
options {
gitLabConnection('weblab.local')
gitlabBuilds(builds: ['Java-Build-And-Install'])
buildDiscarder logRotator(artifactDaysToKeepStr: '30',
artifactNumToKeepStr: '30',
daysToKeepStr: '30',
numToKeepStr: '30')
}
triggers {
gitlab(triggerOnPush: true,
triggerOnMergeRequest: true,
branchFilterType: 'All')
}
environment {
MAVEN_PROFILES = "-P continuousintegrationProfile -P slaSnapshotsProfile"
}
stages {
stage('Java-Build-And-Install') {
steps {
gitlabCommitStatus(name: 'Java-Build-And-Install') {
withMaven(
mavenLocalRepo: 'local-repo') {
sh "mvn clean install ${MAVEN_PROFILES}"
}
}
}
}
stage('Java-Deploy') {
when { anyOf {
branch "master"
buildingTag()
}}
steps {
gitlabBuilds(builds: ['Java-Deploy']) {
gitlabCommitStatus(name: 'Java-Deploy') {
withMaven(
mavenLocalRepo: 'local-repo') {
sh "mvn deploy -DskipTests=true ${MAVEN_PROFILES}"
}
}
}
}
}
}
post {
cleanup {
cleanWs()
}
}
}
Out current workaround is the following pre-install-stage: It gives the accidently-to-be-triggered artifacts in the branches branch-specific names, so they won't be triggered by builds in master.
stage('Java-Rename-Version') {
when { not { anyOf {
branch "master"
buildingTag()
}}}
steps {
gitlabBuilds(builds: ['Java-Rename-Version']) {
gitlabCommitStatus(name: 'Java-Rename-Version') {
withMaven(
[JIRA] (JENKINS-54515) master triggers own branches
Title: Message Title Cyrille Le Clerc commented on JENKINS-54515 Re: master triggers own branches Thorsten Langer can you please confirm that the pipeline that is triggered in an undesired manner is using the same pom.xml hosted on the same git repository and that the different branches have the same maven artifact version identifier? I want to find a generic way to understand that 2 pipelines relate to the same pom.xml. I would like to avoid finding the relationship going through the discovery of a parent multi branch pipeline. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title Thorsten Langer commented on JENKINS-54515 Re: master triggers own branches Is there something I can do to support you understand or reproduce this issue? (I'm still not sure, if it's a bug or a feature request). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-54515 master triggers own branches Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title Thorsten Langer commented on JENKINS-54515 Re: master triggers own branches Hi! We are currently on 3.5.9, and tested 3.5.15. Both with the same effect. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title Cyrille Le Clerc commented on JENKINS-54515 Re: master triggers own branches which version of the pipeline-maven-plugin are you using? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54515) master triggers own branches
Title: Message Title Thorsten Langer created an issue Jenkins / JENKINS-54515 master triggers own branches Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-11-07 14:59 Labels: jenkins pipeline maven trigger Priority: Critical Reporter: Thorsten Langer the setup: a multi-module, Jenkinsfile-based, maven project. builds are triggered via notifications from gitlab, manually or by SNAPSHOT builds of dependencies (per checkbox). only the master (and tags) gets deployed to an artifactory. every build uses a temp local maven repository - which is swiped afterwards. so we don't change the version in branches, as their artefacts never leave their sandbox (workplace directory). I experience, that the master-build/job triggers (on success) the build of the branches. This makes some kind of sense, as formally the modules depends on the artifact build in the master, but on the other hand, it does not make sense, because the triggered branches-builds/jobs will build these triggering artifacts on their own. I'm looking for some solution to suppress the triggering of builds by other jobs, that build the very same artifacts (at least according to their maven coordinates), the triggered build will build on their own. The current workaroud is to change the version in the branches (random or branchname-based), but this seems to me
