[JIRA] (JENKINS-61613) Maven Project Configuration not used in withMaven(){}
Title: Message Title
Benjamin Brummer updated an issue
Jenkins / JENKINS-61613
Maven Project Configuration not used in withMaven(){}
Change By:
Benjamin Brummer
Settings for Global Maven Options or Local Maven Repository in Jenkins is not used in withMaven(){} !image-2020-03-22-10-49-58-738.png|thumbnail! Workaround : around for Global MAVEN Options !image-2020-03-22-10-50-40-438.png|thumbnail!
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205318.1584870659000.10705.1584870720275%40Atlassian.JIRA.
[JIRA] (JENKINS-61613) Maven Project Configuration not used in withMaven(){}
Title: Message Title
Benjamin Brummer updated an issue
Jenkins / JENKINS-61613
Maven Project Configuration not used in withMaven(){}
Change By:
Benjamin Brummer
Environment:
Jenkins 2.204.5Pipeline Maven Integration Plugin 3.8.2Master Ubuntu 18.04Agent: Ubuntu and Windows 10
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205318.1584870659000.10703.1584870720215%40Atlassian.JIRA.
[JIRA] (JENKINS-61613) Maven Project Configuration not used in withMaven(){}
Title: Message Title
Benjamin Brummer created an issue
Jenkins / JENKINS-61613
Maven Project Configuration not used in withMaven(){}
Issue Type:
Bug
Assignee:
Alvaro Lobato
Attachments:
image-2020-03-22-10-49-58-738.png, image-2020-03-22-10-50-40-438.png
Components:
pipeline-maven-plugin
Created:
2020-03-22 09:50
Priority:
Minor
Reporter:
Benjamin Brummer
Settings for Global Maven Options or Local Maven Repository in Jenkins is not used in withMaven(){} Workaround:
Add Comment
[JIRA] (JENKINS-61612) withMaven does not detect maven
Title: Message Title Benjamin Brummer updated an issue Jenkins / JENKINS-61612 withMaven does not detect maven Change By: Benjamin Brummer Environment: Jenkins 2.204.5Pipeline Maven Integration Plugin 3.8.2 Master Ubuntu 18.04Agent: Ubuntu und and Windows 10 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205317.158486867.10699.1584870480143%40Atlassian.JIRA.
[JIRA] (JENKINS-61612) withMaven does not detect maven
Title: Message Title
Benjamin Brummer updated an issue
Jenkins / JENKINS-61612
withMaven does not detect maven
Change By:
Benjamin Brummer
Environment:
Jenkins 2.204.5Pipeline Maven Integration Plugin 3.8.2Master Ubuntu 18.04Agent: Ubuntu und Windows 10
withMaven does not detect maven which was installed through tools {...} in a pipeline{code:bash}[withMaven] Options: [][withMaven] Available options: [withMaven] using JDK installation 8$ where mvn.cmd$ where mvn.bat[withMaven] Maven installation not specified in the 'withMaven()' step and not found on the build agent[Pipeline] {[Pipeline] isUnix[Pipeline] batC:\jenkins\workspace\capshe2_master>mvn -f impl/eu.pinteam.capshe/pom.xml -Dmaven.test.skip=true -Dfile.encoding=UTF-8 clean package -X Skipping download of https://repos.pinteam.eu/nexus/service/local/repositories/ci/content/pinteam/openjdk8u-x64-windows-hotspot/8u232b09/openjdk8u-x64-windows-hotspot-8u232b09.zip as C:\jenkins\tools\hudson.model.JDK\8 is up to date on WJENKSL01.Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)Maven home: C:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.6.3\apache-maven-3.6.3\bin\..Java version: 1.8.0_232, vendor: AdoptOpenJDK, runtime: C:\jenkins\tools\hudson.model.JDK\8\jdk8u232-b09\jreDefault locale: en_US, platform encoding: UTF-8OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"[DEBUG] Included C:\jenkins\workspace\capshe2_master@tmp\withMavenedd529ce\pipeline-maven-spy.jar[DEBUG] Populating class realm maven.ext[DEBUG] Included C:\jenkins\workspace\capshe2_master@tmp\withMavenedd529ce\pipeline-maven-spy.jar[INFO] [jenkins-event-spy] Generate C:\jenkins\workspace\capshe2_master@tmp\withMavenedd529ce\maven-spy-20200322-101222-3544782924526790386938.log.tmp ...[DEBUG] Created new class realm maven.api[DEBUG] Importing foreign packages into class realm maven.api[DEBUG] Imported: javax.annotation.* < maven.ext[DEBUG] Imported: javax.annotation.security.* < maven.ext[DEBUG] Imported: javax.enterprise.inject.* < maven.ext[DEBUG] Imported: javax.enterprise.util.* < maven.ext[DEBUG] Imported: javax.inject.* < maven.ext[DEBUG] Imported: org.apache.maven.* < maven.ext[DEBUG] Imported: org.apache.maven.artifact < maven.ext[DEBUG] Imported: org.apache.maven.classrealm < maven.ext[DEBUG] Imported: org.apache.maven.cli < maven.ext[DEBUG] Imported: org.apache.maven.configuration < maven.ext[DEBUG] Imported: org.apache.maven.exception < maven.ext[DEBUG] Imported: org.apache.maven.execution < maven.ext[DEBUG] Imported: org.apache.maven.execution.scope < maven.ext[DEBUG] Imported: org.apache.maven.lifecycle < maven.ext[DEBUG] Imported: org.apache.maven.model < maven.ext[DEBUG] Imported: org.apache.maven.monitor < maven.ext[DEBUG] Imported: org.apache.maven.plugin < maven.ext[DEBUG]
[JIRA] (JENKINS-50662) withMaven for declarative pipeline
Title: Message Title Benjamin Brummer updated an issue Jenkins / JENKINS-50662 withMaven for declarative pipeline Change By: Benjamin Brummer Environment: Jenkins 2.204.5Pipeline Maven Integration Plugin 3.8.2 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189746.1523267564000.10687.1584868800372%40Atlassian.JIRA.
[JIRA] (JENKINS-61612) withMaven does not detect maven
Title: Message Title
Benjamin Brummer created an issue
Jenkins / JENKINS-61612
withMaven does not detect maven
Issue Type:
Bug
Assignee:
Alvaro Lobato
Components:
pipeline-maven-plugin
Created:
2020-03-22 09:17
Priority:
Minor
Reporter:
Benjamin Brummer
withMaven does not detect maven which was installed through tools {...} in a pipeline
[withMaven] Options: []
[withMaven] Available options:
[withMaven] using JDK installation 8
$ where mvn.cmd
$ where mvn.bat
[withMaven] Maven installation not specified in the 'withMaven()' step and not found on the build agent
[Pipeline] {
[Pipeline] isUnix
[Pipeline] bat
C:\jenkins\workspace\capshe2_master>mvn -f impl/eu.pinteam.capshe/pom.xml -Dmaven.test.skip=true -Dfile.encoding=UTF-8 clean package -X
Skipping download of https://repos.pinteam.eu/nexus/service/local/repositories/ci/content/pinteam/openjdk8u-x64-windows-hotspot/8u232b09/openjdk8u-x64-windows-hotspot-8u232b09.zip as C:\jenkins\tools\hudson.model.JDK\8 is up to date on WJENKSL01.
Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.6.3\apache-maven-3.6.3\bin\..
Java version: 1.8.0_232, vendor: AdoptOpenJDK, runtime: C:\jenkins\tools\hudson.model.JDK\8\jdk8u232-b09\jre
Default locale: en_US, platform encoding: UTF-8
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
[DEBUG] Included C:\jenkins\workspace\capshe2_master@tmp\withMavenedd529ce\pipeline-maven-spy.jar
[DEBUG] Populating class realm maven.ext
[DEBUG] Included C:\jenkins\workspace\capshe2_master@tmp\withMavenedd529ce\pipeline-maven-spy.jar
[INFO] [jenkins-event-spy] Generate C:\jenkins\workspace\capshe2_master@tmp\withMavenedd529ce\maven-spy-20200322-101222-3544782924526790386938.log.tmp ...
[DEBUG] Created new class
[JIRA] (JENKINS-61448) Replay function shows unrelated shared libraries
Title: Message Title Benjamin Brummer created an issue Jenkins / JENKINS-61448 Replay function shows unrelated shared libraries Issue Type: Bug Assignee: Unassigned Attachments: image-2020-03-12-08-38-30-445.png Components: core, pipeline Created: 2020-03-12 07:41 Environment: Jenkins 2.204.5 Priority: Minor Reporter: Benjamin Brummer Unrelated pipeline libraries are shown on replay screen. We have a single repository with three pipeline libraries repo/vars/lib1.groovy repo/vars/lib2.groovy repo/vars/lib3.groovy If we use one of these pipeline libraries the other two libraries are shown on the replay screen, too.
[JIRA] (JENKINS-61324) Replay global pipelines
Title: Message Title Benjamin Brummer created an issue Jenkins / JENKINS-61324 Replay global pipelines Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2020-03-04 11:41 Priority: Minor Reporter: Benjamin Brummer Shared pipelines define globally can not be modified when using Replay function for a Job (Bitbucket Team/Project) Expected behaviour: Replay shows all used pipelines Actual Behavior: Only Jenkinsfile is shown Assumption: This may be wanted, as global pipelines are meant to be trusted and modifieng them could be a security issue. Add Comment
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title
Benjamin Brummer edited a comment on JENKINS-60204
Re: git plugin 4.0.0 can not shallow clone a submodule
So it looks like a layer 8 problem on my side combined with inconsistent submodule handling in our company. We always get this error when something is wrong with git (e.g. Agent is running out of disk space and therefore git fails){code:java}Error when executing always post condition:org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing. Suppressed: org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missingPerhaps you forgot to surround the code with a step that provides this, such as: node{code}So therefore the build failed cause because of a detached head status in the submodule , what can not work with shallow clone . When i readded the submodule it was tracking the master !git_status_submodule.png|thumbnail! The shallow clone was a miss-configuration on my side, which worked often but failed on branches with a detached head submodules submodule . As it is hard to make sure that submodules are tracking a branch, which they per default will not do it is safer to not use this feature on our jenkins. This is handled inconsistently on git client side, too , e.g GitKraken tracks the branch by default for a submodule, therefore the build startet to work after i re-added the submodule.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title
Benjamin Brummer edited a comment on JENKINS-60204
Re: git plugin 4.0.0 can not shallow clone a submodule
So it looks like a layer 8 problem on my side combined with inconsistent submodule handling in our company. We always get this error when something is wrong with git (e.g. Agent is running out of disk space and therefore git fails){code:java}Error when executing always post condition:org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing. Suppressed: org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missingPerhaps you forgot to surround the code with a step that provides this, such as: node{code}So therefore the build failed cause a detached head status in the submodule can not work with shallow. When i readded the submodule it was tracking the master !git_status_submodule.png|thumbnail! The shallow clone was a missconfiguration miss-configuration on my side, which worked often but failed on branches with detached head submodules. As it is hard to make sure that submodules are tracking a branch, which they per default will not do it is safer to not use this feature on our jenkins. This is handled inconsistently on git client side, e.g GitKraken tracks the branch by default for a submodule, therefore the build startet to work after i re-added the submodule.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title
Benjamin Brummer edited a comment on JENKINS-60204
Re: git plugin 4.0.0 can not shallow clone a submodule
So it looks like a layer 8 problem on my side combined with inconsistent submodule handling in our company. We always get this error when something is wrong with git (e.g. Agent is running out of disk space and therefore git fails){code:java}Error when executing always post condition:org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing. Suppressed: org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missingPerhaps you forgot to surround the code with a step that provides this, such as: node{code} So therefore the build failed cause a detached head status in the submodule can not work with shallow. When i readded the submodule it was tracking the master !git_status_submodule.png|thumbnail! The shallow clone was a missconfiguration on my side, which worked often but failed on branches with detached head submodules.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4042.1574203800251%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer updated an issue Jenkins / JENKINS-60204 git plugin 4.0.0 can not shallow clone a submodule Change By: Benjamin Brummer Attachment: git_status_submodule.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4039.1574203680300%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title
Benjamin Brummer edited a comment on JENKINS-60204
Re: git plugin 4.0.0 can not shallow clone a submodule
So it looks like a layer 8 problem on my side combined with inconsistent submodule handling in our company. We always get this error when something is wrong with git (e.g. Agent is running out of disk space and therefore git fails){code:java}Error when executing always post condition:org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing. Suppressed: org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missingPerhaps you forgot to surround the code with a step that provides this, such as: node{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4036.1574203500169%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title
Benjamin Brummer edited a comment on JENKINS-60204
Re: git plugin 4.0.0 can not shallow clone a submodule
So it looks like a layer 8 problem on my side combined with inconsistent submodule handling in our company. We always get this error when something is wrong with git (e . g. Agent is running out of disk space and therefore git fails) {code:java}Error when executing always post condition:org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing. Suppressed: org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missingPerhaps you forgot to surround the code with a step that provides this, such as: node{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4029.1574203380281%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title
Benjamin Brummer edited a comment on JENKINS-60204
Re: git plugin 4.0.0 can not shallow clone a submodule
So it looks like a layer 8 problem on my side combined with inconsistent submodule handling in our company. We always get this error when something is wrong with git.{code:java}Error when executing always post condition:org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing. Suppressed: org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missingPerhaps you forgot to surround the code with a step that provides this, such as: node{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4022.1574202300191%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule So it looks like a layer 8 problem on my side combined with inconsistent submodule handling in our company. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4019.1574202060153%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule The missing "–depth=1" in the first log is caused, by running first with shallow clone on the submodule which leaves a somehow broken submodule directory behind. The next build was than not a clean build i guess. [ comment |https://issues.jenkins-ci.org/browse/JENKINS-60204?focusedCommentId=380228=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-380228] None of the above errors happen when i downgrade to git plugin 3.12.1 with the exact same job configuration. When i switch between the original submodule and the readded submodule commit i can reproducible make the build fail/succeed.I will test on commandline and report back. But i assume somehow the submodules where added in a strange way. Although i can not tell what is wrong and why it worked until this update. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4013.1574201220793%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule The missing "–depth=1" in the first log is caused, by running first with shallow clone on the submodule which leaves a somehow broken submodule directory behind. The next build was than not a clean build i guess. [comment|https://issues.jenkins-ci.org/browse/JENKINS-60204?focusedCommentId=380228=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-380228] None of the above errors happen when i downgrade to git plugin 3.12.1 with the exact same job configuration. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4003.1574200740169%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule The missing "–depth=1" in the first log is caused, by running first with shallow clone on the submodule which leaves a somehow broken submodule directory behind. The next build was than not a clean build i guess. None of the above errors happen when i downgrade to git plugin 3.12.1 with the exact same job configuration. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.4000.1574200680185%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule I checked the submodule again updated it to a different commit already.Now i removed it, added it again => it looks like it is working now. No clue what is going on. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3991.1574198880148%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule I checked the submodule again updated it to a different commit already and now .Now i removed it, added it again => it looks like it is working now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3988.1574198700193%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule I checked the submodule again updated it to a different commit already and now i removed it, added it again => it looks like it is working now. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3985.1574198581476%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule I tried to reproduce it with a public repo without success, so a) only private repo.[^works.xml][^fail.xml] ^[^fail.log]^ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3975.1574196420150%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer updated an issue Jenkins / JENKINS-60204 git plugin 4.0.0 can not shallow clone a submodule Change By: Benjamin Brummer Attachment: fail.xml Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3969.1574196060888%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule I tried to reproduce it with a public repo without success, so a) only private repo. works.xml fail.xml Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3970.1574196060963%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer updated an issue Jenkins / JENKINS-60204 git plugin 4.0.0 can not shallow clone a submodule Change By: Benjamin Brummer Attachment: works.xml Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3966.1574196000212%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not shallow clone a submodule
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not shallow clone a submodule If shallow clone for the submodule is activated this error happens on my side. It has to be a clean build. Additionally: If i activate shallow clone and the build fails the submodule-folder has just a .git. If i deactivate shallow clone again it will still fail, until i wipe the workspace again. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3906.1574191980140%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules If shallow clone for the submodule is activated this error happens on my side. It has to be a clean build. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3894.1574190360170%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules If shallow clone for the submodule is activated this error happens on my side. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3886.1574188860258%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules Ok it looks like something which is configured on the multibranch configuration is causing this error. I removed now all advanced options apart from Advanced sub-modules behaviours from a copy of the original jobs and it works. I will have a look tomorrow, what is causing this error. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.2946.1574113620195%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules Looks like this is somehow project type related. The log above is from a multibranch pipeline. If i use a freestyle project the submodules are handled without a problem. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.2911.1574112000186%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer created an issue Jenkins / JENKINS-60204 git plugin 4.0.0 can not handle submodules Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-11-18 18:58 Environment: Jenkins 2.190.2 git-plugin 4.0.0 Priority: Major Reporter: Benjamin Brummer git-plugin 3.12 works without any problem. > git submodule update --remote impl/tool_protec # timeout=10 Error when executing always post condition: org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing Perhaps you forgot to surround the code with a step that provides this, such as: node at org.jenkinsci.plugins.workflow.steps.StepDescriptor.checkContextAvailability(StepDescriptor.java:266) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:263) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor849.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at
[JIRA] (JENKINS-55362) Support command profiles
Title: Message Title Benjamin Brummer commented on JENKINS-55362 Re: Support command profiles I just added a Windows 101903 ssh agent to our Jenkins 2.190.2 with ssh-slaves-plugin 1.31.0. There was no need of adding "Prefix Start Agent Command" and "Suffix Start Agent Command" to make it work. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196465.1546107377000.12251.1573552440277%40Atlassian.JIRA.
[JIRA] (JENKINS-55362) Support command profiles
Title: Message Title Benjamin Brummer edited a comment on JENKINS-55362 Re: Support command profiles I just added a Windows 101903 10 1903 ssh agent to our Jenkins 2.190.2 with ssh-slaves-plugin 1.31.0. There was no need of adding "Prefix Start Agent Command" and "Suffix Start Agent Command" to make it work. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196465.1546107377000.12253.1573552440308%40Atlassian.JIRA.
[JIRA] (JENKINS-57631) No credentials found for id
Title: Message Title Benjamin Brummer commented on JENKINS-57631 Re: No credentials found for id I can reproduce it now: If i configure "Access Control for Builds" under "Global Security", the credentials vanish in the job configuration. If i remove everything under "Access Control for Builds" they reappear. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199561.1558603884000.7688.1562797560121%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57631) No credentials found for id
Title: Message Title Benjamin Brummer edited a comment on JENKINS-57631 Re: No credentials found for id Update: Transfered jenkins again now everything is fine. After a migration from a centos to a ubuntu system we get the error "Cannot find any credentials with id..." for all projects. The jobs run fine, but it is not possible to switch credentials. I can add new one in the job configuration, but they are not select able afterwards.!image-2019-07-10-21-53-04-753.png! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199561.1558603884000.7663.1562790660242%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57631) No credentials found for id
Title: Message Title Benjamin Brummer updated an issue Jenkins / JENKINS-57631 No credentials found for id Change By: Benjamin Brummer Attachment: image-2019-07-10-21-53-04-753.png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199561.1558603884000.7650.1562788440227%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57631) No credentials found for id
Title: Message Title Benjamin Brummer commented on JENKINS-57631 Re: No credentials found for id After a migration from a centos to a ubuntu system we get the error "Cannot find any credentials with id..." for all projects. The jobs run fine, but it is not possible to switch credentials. I can add new one in the job configuration, but they are not select able afterwards. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199561.1558603884000.7652.1562788440256%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39636) Could not initialize class org.jfree.chart.JFreeChart
Title: Message Title Benjamin Brummer commented on JENKINS-39636 Re: Could not initialize class org.jfree.chart.JFreeChart I can confirm on Ubuntu using the openjdk-8-jdk solves this problem. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176200.1478758105000.18810.1559565961189%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer updated JENKINS-56579 Jenkins / JENKINS-56579 .mvn/extensions.xml not recognized Change By: Benjamin Brummer Status: Fixed but Unreleased 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198194.155264253.13855.1559058720320%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer updated JENKINS-56579 I can not reproduce the problem anymore. All maven versions work now as expected. Jenkins / JENKINS-56579 .mvn/extensions.xml not recognized Change By: Benjamin Brummer Status: Open Fixed but Unreleased Resolution: Cannot Reproduce 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198194.155264253.13852.1559058660475%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title
Benjamin Brummer updated an issue
Jenkins / JENKINS-56579
.mvn/extensions.xml not recognized
Change By:
Benjamin Brummer
We wanted to setup a tycho-pomless build on jenkins, with maven 3.6.0. Running the build without Jenkins works fine.The pom.xml is in a subfolder next to the .mvn/extensions.xmlThis job only works when the pom.xml is in the workspace root and maven 3.3.9 is used. Useing dir() in a pipeline when calling maven 3.3.9 is working to too . We could reproduce this issue with the tycho-example form here too [https://github.com/vogellacompany/tycho-example]h1. 3.3.9 + code in "sub"{code:java}[Vogella] $ cmd.exe /C "c:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.3.9\bin\mvn.cmd clean verify -V -B --file sub/pom.xml && exit %%ERRORLEVEL%%"Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)Maven home: c:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.3.9Java version: 1.8.0_202, vendor: Oracle CorporationJava home: c:\jenkins\tools\hudson.model.JDK\8\jreDefault locale: en_US, platform encoding: Cp1252OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"[INFO] Scanning for projects...[ERROR] [ERROR] Some problems were encountered while processing the POMs:[ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.logging.config\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ [ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.plugin1\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ [ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.rcp\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ [ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.p2.ui\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ [ERROR] Child module C:\jenkins\workspace\Vogella\sub\features\com.vogella.tycho.feature\pom.xml of C:\jenkins\workspace\Vogella\sub\features\pom.xml does not exist @ [ERROR] Child module C:\jenkins\workspace\Vogella\sub\tests\com.vogella.tycho.plugin1.tests\pom.xml of C:\jenkins\workspace\Vogella\sub\tests\pom.xml does not exist @ [ERROR] Child module C:\jenkins\workspace\Vogella\sub\tests\com.vogella.tycho.rcp.tests\pom.xml of C:\jenkins\workspace\Vogella\sub\tests\pom.xml does not exist @ @ [ERROR] The build could not read 3 projects -> [Help 1][ERROR] [ERROR] The project com.vogella.tycho:com.vogella.tycho.bundles:1.0.0-SNAPSHOT (C:\jenkins\workspace\Vogella\sub\bundles\pom.xml) has 4 errors[ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.logging.config\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist[ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.tycho.plugin1\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist[ERROR] Child module
[JIRA] (JENKINS-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer commented on JENKINS-56579 Re: .mvn/extensions.xml not recognized "I call maven via CMD, not the jenkins maven plugin" => Without jenkins involved at all? Without jenkins it works here with 3.6.0. Useing a Jenkins agent => No matter how we call mvn, it fails. 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-44322) email-ext sends wrong build status when called from declarative script
Title: Message Title
Benjamin Brummer edited a comment on JENKINS-44322
Re: email-ext sends wrong build status when called from declarative script
[~bkihm], here we have the same error since with Jenkins 2.164.1 and email ext 2.65 (2.64) {code:java}/* Set email content */def subjectContent = '$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS!'def bodyContent = '${SCRIPT, template="groovy-html.template"}'.stage('Test') { steps { bat 'exit 1' }}...fixed { emailext( body: bodyContent, recipientProviders: [ developers(), requestor() ], subject: subjectContent )}{code}Build on Jenkins fails and is red. Email says "Test - Build # 52 - SUCCESS!
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-44322) email-ext sends wrong build status when called from declarative script
Title: Message Title
Benjamin Brummer commented on JENKINS-44322
Re: email-ext sends wrong build status when called from declarative script
Benjamin Kihm, here we have the same error since with Jenkins 2.164.1 and email ext 2.65 (2.64)
/* Set email content */
def subjectContent = '$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS!'
def bodyContent = '${SCRIPT, template="groovy-html.template"}'
.
stage('Test') {
steps {
bat 'exit 1'
}
}
...
fixed {
emailext(
body: bodyContent,
recipientProviders: [
developers(),
requestor()
],
subject: subjectContent
)
}
Build on Jenkins fails and is red. Email says "Test - Build # 52 - SUCCESS!
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-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer edited a comment on JENKINS-56579 Re: .mvn/extensions.xml not recognized * Building on the jenkins linux master works with maven 3.6.0 with and without pom.xml in subdirectory. * Windows 10 Agent fails * Ubuntu agent is fineSo looks like a Windows problem. 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-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer edited a comment on JENKINS-56579 Re: .mvn/extensions.xml not recognized * Building on the jenkins linux master works with maven 3.6.0 with and without pom.xml in subdirectory. * Windows 10 Agent fails 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-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer commented on JENKINS-56579 Re: .mvn/extensions.xml not recognized Building on the jenkins linux master works with maven 3.6.0 with and without pom.xml in subdirectory. 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-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer updated an issue Jenkins / JENKINS-56579 .mvn/extensions.xml not recognized Change By: Benjamin Brummer Environment: jenkins 2.164.1 maven-invoker-plugin 2.4ubuntu 18.04.2 masterwindows 7 slaves 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-56579) .mvn/extensions.xml not recognized
Title: Message Title Benjamin Brummer created an issue Jenkins / JENKINS-56579 .mvn/extensions.xml not recognized Issue Type: Bug Assignee: Olivier Lamy Components: maven-invoker-plugin Created: 2019-03-15 09:35 Environment: jenkins 2.164.1 Priority: Minor Reporter: Benjamin Brummer We wanted to setup a tycho-pomless build on jenkins, with maven 3.6.0. Running the build without Jenkins works fine. The pom.xml is in a subfolder next to the .mvn/extensions.xml This job only works when the pom.xml is in the workspace root and maven 3.3.9 is used. Useing dir() in a pipeline when calling maven 3.3.9 is working to. We could reproduce this issue with the tycho-example form here too https://github.com/vogellacompany/tycho-example 3.3.9 + code in "sub" [Vogella] $ cmd.exe /C "c:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.3.9\bin\mvn.cmd clean verify -V -B --file sub/pom.xml && exit %%ERRORLEVEL%%" Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00) Maven home: c:\jenkins\tools\hudson.tasks.Maven_MavenInstallation\3.3.9 Java version: 1.8.0_202, vendor: Oracle Corporation Java home: c:\jenkins\tools\hudson.model.JDK\8\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" [INFO] Scanning for projects... [ERROR] [ERROR] Some problems were encountered while processing the POMs: [ERROR] Child module C:\jenkins\workspace\Vogella\sub\bundles\com.vogella.logging.config\pom.xml of C:\jenkins\workspace\Vogella\sub\bundles\pom.xml does not exist @ [ERROR] Child module
[JIRA] (JENKINS-55649) X-Bitbucket-Type header / server_url request parameter not found
Title: Message Title
Benjamin Brummer edited a comment on JENKINS-55649
Re: X-Bitbucket-Type header / server_url request parameter not found
When i let the plugin manage the hooks it configures the webhook on Bitbucket to be [ {code:java} https://jenkins.company.com/bitbucket-scmsource-hook/notify?server_url=https%3A%2F%2Fbitbucket.company.com .] {code} Similar to [~dpat65]'s comment. It works without any problem. Maybe this simply needs to be updated in the plugin wiki?
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-55649) X-Bitbucket-Type header / server_url request parameter not found
Title: Message Title Benjamin Brummer commented on JENKINS-55649 Re: X-Bitbucket-Type header / server_url request parameter not found When i let the plugin manage the hooks it configures the webhook on Bitbucket to be https://jenkins.company.com/bitbucket-scmsource-hook/notify?server_url=https%3A%2F%2Fbitbucket.company.com. Similar to Darin Patrick's comment. It works without any problem. Maybe this simply needs to be updated in the plugin wiki? 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-55905) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Benjamin Brummer edited a comment on JENKINS-55905 Re: Git Plugin 3.9.2 cannot clone remote repo [~markewaite] - can you clarify what you mean by "renamed" submodule? - It looks like our developer did not configure the submodules properly. The were just added but not initialized and committed. Everything works now. 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-55905) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Benjamin Brummer commented on JENKINS-55905 Re: Git Plugin 3.9.2 cannot clone remote repo Mark Waite can you clarify what you mean by "renamed" submodule? 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-55905) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title
Benjamin Brummer commented on JENKINS-55905
Re: Git Plugin 3.9.2 cannot clone remote repo
With submodules behavior we get an exception for the post{ always{}} too
Error when executing always post condition:
java.lang.IllegalArgumentException: Failed to prepare recordIssues step
at org.jenkinsci.plugins.workflow.cps.DSL.invokeDescribable(DSL.java:397)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179)
at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)
at sun.reflect.GeneratedMethodAccessor567.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:157)
at org.kohsuke.groovy.sandbox.GroovyInterceptor.onMethodCall(GroovyInterceptor.java:23)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:155)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:155)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:159)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:129)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.methodCall(SandboxInvoker.java:17)
at fujiPipeline.call(/var/lib/jenkins/jobs/FujiDesigner/branches/bbr/builds/8/libs/fuji/vars/fujiPipeline.groovy:244)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109)
at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82)
at sun.reflect.GeneratedMethodAccessor404.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55)
at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.item(CollectionLiteralBlock.java:45)
at sun.reflect.GeneratedMethodAccessor408.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.CollectionLiteralBlock$ContinuationImpl.dispatch(CollectionLiteralBlock.java:55)
at
[JIRA] (JENKINS-55905) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Benjamin Brummer commented on JENKINS-55905 Re: Git Plugin 3.9.2 cannot clone remote repo This is what is happening before it fails using credential 8e9cdbd8-1fb6-4a5a-a431-100b00c20d6c Fetching changes from the remote Git repository Pruning obsolete local branches Checking out Revision 391e617bb844859cf70dcab71dd4178cccfdfea5 (qwe) Commit message: "changed path again" > git rev-parse --is-inside-work-tree # timeout=10 > git config remote.origin.url https://bitbucket_url/scm/ASD/repo.git # timeout=10 Fetching upstream changes from https://bitbucket_url/scm/ASD/repo.git > git --version # timeout=10 using GIT_ASKPASS to set credentials > git fetch --no-tags --force --progress https://bitbucket_url/scm/ASD/repo.git +refs/heads/qwe:refs/remotes/origin/qwe --prune > git config core.sparsecheckout # timeout=10 > git checkout -f 391e617bb844859cf70dcab71dd4178cccfdfea5 > git rev-list --no-walk 391e617bb844859cf70dcab71dd4178cccfdfea5 # timeout=10 > git remote # timeout=10 > git submodule init # timeout=10 > git submodule sync # timeout=10 > git config --get remote.origin.url # timeout=10 > git submodule init # timeout=10 [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // ws [Pipeline] } [Pipeline] // node [Pipeline] End of Pipeline [Bitbucket] Notifying commit build result [Bitbucket] Build result notified 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
[JIRA] (JENKINS-55905) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Benjamin Brummer updated JENKINS-55905 Jenkins / JENKINS-55905 Git Plugin 3.9.2 cannot clone remote repo Change By: Benjamin Brummer Resolution: Cannot Reproduce Status: Fixed but Unreleased Reopened 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-55905) Git Plugin 3.9.2 cannot clone remote repo
Title: Message Title Benjamin Brummer commented on JENKINS-55905 Re: Git Plugin 3.9.2 cannot clone remote repo When using submodules on multipipeline job wit 3.9.2, 3.9.3 and 4.0.0-rc. Without submodule everything is ok. Tested on windows and linux Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from X.X.X.X/X.X.X.X:49253 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:955) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:146) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:132) at com.sun.proxy.$Proxy115.execute(Unknown Source) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:108) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1270) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) hudson.plugins.git.GitException: Command "git config --get submodule.name.url" returned status code 1: stdout: stderr: at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2010) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2006) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1638) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1650) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getSubmoduleUrl(CliGitAPIImpl.java:1250) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$7.execute(CliGitAPIImpl.java:1176) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at
[JIRA] (JENKINS-53677) Email-adresses is not fetched in correct format
Title: Message Title
Benjamin Brummer updated an issue
Jenkins / JENKINS-53677
Email-adresses is not fetched in correct format
Change By:
Benjamin Brummer
If you connect jenkins with Crowd (SSO) User profiles in Jenkins users get emails like "firstname lastname (firstname.lastn...@domain.com)" instead of just "firstname.lastn...@domain.com"--{{Adding recipients from project recipient list}} \ {{ Collecting change authors...}} \ {{ build: 3}} \ {{ adding author: Firstname Lastname (firstname.lastname)}}{{Not sending mail to user firstname.lastn...@domain.com with no permission to view JobXYU » feature/XY-53 #3Adding Firstname Lastname (firstname.lastn...@domain.com) with address Firstname Lastname (firstname.lastn...@domain.com)}}{{Analyzing: Firstname,Lastname,(firstname.lastn...@domain.com)}}{{Looking for: Firstname}} \ {{ starting at: 0}} \ {{ firstFoundIdx: 0}} \ {{ firstFoundIdx-substring: Firstname,Lastname,(firstname.lastn...@domain.com)}} \ {{ => found type: 0}}{{Looking for: Lastname}} \ {{ starting at: 9}} \ {{ firstFoundIdx: 9}} \ {{ firstFoundIdx-substring: Lastname,(firstname.lastn...@domain.com)}} \ {{ => found type: 0}}{{Analyzing: Firstname,Lastname,(firstname.lastn...@domain.com)}}{{Looking for: Firstname}} \ {{ starting at: 0}} \ {{ firstFoundIdx: 0}} \ {{ firstFoundIdx-substring: Firstname,Lastname,(firstname.lastn...@domain.com)}} \ {{ => found type: 0}}{{Looking for: Lastname}} \ {{ starting at: 9}} \ {{ firstFoundIdx: 9}} \ {{ firstFoundIdx-substring: Lastname,(firstname.lastn...@domain.com)}} \ {{ => found type: 0}}{{Analyzing: Firstname,Lastname,(firstname.lastn...@domain.com)}}{{Looking for: Firstname}} \ {{ starting at: 0}} \ {{ firstFoundIdx: 0}} \ {{ firstFoundIdx-substring: Firstname,Lastname,(firstname.lastn...@domain.com)}} \ {{ => found type: 0}}{{Looking for: Lastname}} \ {{ starting at: 9}} \ {{ firstFoundIdx: 9}} \ {{ firstFoundIdx-substring: Lastname,(firstname.lastn...@domain.com)}} \ {{ => found type: 0}}{{Adding recipients from trigger recipient list}}{{Successfully created MimeMessage}}{{Sending email to: Firstname firstname.lastn...@domain.com}}{{Successfully sent to the following addresses: firstname.lastn...@domain.com}}{{Error sending to the following INVALID addresses: Firstname}}--
[JIRA] (JENKINS-53677) Email-adresses is not fetched in correct format
Title: Message Title
Benjamin Brummer created an issue
Jenkins / JENKINS-53677
Email-adresses is not fetched in correct format
Issue Type:
Bug
Assignee:
Martin Spielmann
Components:
crowd2-plugin, email-ext-plugin
Created:
2018-09-20 11:30
Priority:
Minor
Reporter:
Benjamin Brummer
If you connect jenkins with Crowd (SSO) User profiles in Jenkins get emails like "firstname lastname (firstname.lastn...@domain.com)" instead of just "firstname.lastn...@domain.com" -- Adding recipients from project recipient list {{ Collecting change authors...}} {{ build: 3}} {{ adding author: Firstname Lastname (firstname.lastname)}} Not sending mail to user firstname.lastn...@domain.com with no permission to view JobXYU » feature/XY-53 #3Adding Firstname Lastname (firstname.lastn...@domain.com) with address Firstname Lastname (firstname.lastn...@domain.com) Analyzing: Firstname,Lastname,(firstname.lastn...@domain.com) Looking for: Firstname {{ starting at: 0}} {{ firstFoundIdx: 0}} {{ firstFoundIdx-substring: Firstname,Lastname,(firstname.lastn...@domain.com)}} {{ => found type: 0}} Looking for: Lastname {{ starting at: 9}} {{ firstFoundIdx: 9}} {{ firstFoundIdx-substring: Lastname,(firstname.lastn...@domain.com)}} {{ => found type: 0}} Analyzing: Firstname,Lastname,(firstname.lastn...@domain.com) Looking for: Firstname {{ starting at: 0}} {{ firstFoundIdx: 0}} {{ firstFoundIdx-substring: Firstname,Lastname,(firstname.lastn...@domain.com)}} {{ => found type: 0}} Looking for: Lastname {{ starting at: 9}} {{ firstFoundIdx: 9}} {{ firstFoundIdx-substring: Lastname,(firstname.lastn...@domain.com)}} {{ => found type: 0}} Analyzing: Firstname,Lastname,(firstname.lastn...@domain.com) Looking for: Firstname {{ starting at: 0}} {{ firstFoundIdx: 0}} {{ firstFoundIdx-substring: Firstname,Lastname,(firstname.lastn...@domain.com)}} {{ => found type: 0}} Looking for: Lastname {{ starting at: 9}} {{ firstFoundIdx: 9}} {{
