[JIRA] (JENKINS-54288) Create GSoC project proposal documents
Title: Message Title Lloyd Chang updated JENKINS-54288 Jenkins / JENKINS-54288 Create GSoC project proposal documents Change By: Lloyd Chang 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-54235) Parameterized scheduler not triggering daily builds
Title: Message Title Deepak Puligundla closed an issue as Not A Defect Jenkins / JENKINS-54235 Parameterized scheduler not triggering daily builds Change By: Deepak Puligundla Status: Open Closed Resolution: Not A Defect 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-54381) Allow to specify a different team when creating a pipeline
Title: Message Title Armandas Jarusauskas created an issue Jenkins / JENKINS-54381 Allow to specify a different team when creating a pipeline Issue Type: Improvement Assignee: Unassigned Attachments: new_interface.png, old_interface.png Components: blueocean-plugin Created: 2018-11-01 04:23 Environment: Jenkins 2.138.2 Blue Ocean 1.9.0 Priority: Minor Reporter: Armandas Jarusauskas In the old interface, one is able to specify the "owner" of the repositories (i.e. the team). However, in the Blue Ocean interface, the owner is assumed to be the user whose credentials are used. It would be great if the new interface allowed to enter the team name in free form text. Background: In BitBucket, a user is not considered a part of the team unless they have admin rights (see this [bug report|https://bitbucket.org/site/master/issues/10981/team-members-cant-see-teams-on-teams),] which is why other teams are not detected in Blue Ocean. However, since the old interface has the ability to specify the owner, I think it would make sense to add this feature to the Blue Ocean interface as well.
[JIRA] (JENKINS-54380) Private repository authentication
Title: Message Title Marcos Vallim assigned an issue to Philipp Garbe Jenkins / JENKINS-54380 Private repository authentication Change By: Marcos Vallim Assignee: Marcos Vallim Philipp Garbe 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-54380) Private repository authentication
Title: Message Title Marcos Vallim commented on JENKINS-54380 Re: Private repository authentication I created a pull request for this: https://github.com/jenkinsci/amazon-ecs-plugin/pull/18 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-54380) Private repository authentication
Title: Message Title Marcos Vallim updated JENKINS-54380 Jenkins / JENKINS-54380 Private repository authentication Change By: Marcos Vallim 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-54380) Private repository authentication
Title: Message Title Marcos Vallim updated JENKINS-54380 Jenkins / JENKINS-54380 Private repository authentication Change By: Marcos Vallim Status: In Review 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-54380) Private repository authentication
Title: Message Title Marcos Vallim updated JENKINS-54380 Jenkins / JENKINS-54380 Private repository authentication Change By: Marcos Vallim 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-54380) Private repository authentication
Title: Message Title Marcos Vallim started work on JENKINS-54380 Change By: Marcos Vallim 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-54379) Jenkins gradle java.lang.interrupted exception for Jbehave Automated test
Title: Message Title
Tejo K updated an issue
Jenkins / JENKINS-54379
Jenkins gradle java.lang.interrupted exception for Jbehave Automated test
Change By:
Tejo K
My automated JBehave test cases run fine in IntelliJ but when run as a job in Jenkins, it throws the following error. This error is not consistent with any specific test case/scenario. The job remains idle and the job fails after specific inactivity time set by me. No info on Jenkins log is seen except below. {code:java} java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:502) at java.lang.UNIXProcess.waitFor(UNIXProcess.java:396) at hudson.Proc$LocalProc.join(Proc.java:324) at hudson.Launcher$ProcStarter.join(Launcher.java:474) at hudson.plugins.gradle.Gradle.performTask(Gradle.java:333) at hudson.plugins.gradle.Gradle.perform(Gradle.java:225) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1727) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) {code} I've tried with increasing the timeout value in Storiesrunner.java to 10, but still sees the issue. {code:java} configuredEmbedder() .embedderControls() .useStoryTimeouts("10") {code} Jenkins version installed in Linux(Centos Java 1.8): Jenkins ver. 2.105 Gradle plugin: 1.9. Gradle version 4.9performTask(Gradle.java:333) has {code:java} launcher.launch().cmds(args).envs(env).stdout(gca) .pwd(rootLauncher).join(); {code}
Add Comment
[JIRA] (JENKINS-54380) Private repository authentication
Title: Message Title Marcos Vallim created an issue Jenkins / JENKINS-54380 Private repository authentication Issue Type: New Feature Assignee: Marcos Vallim Components: amazon-ecs-plugin Created: 2018-11-01 02:14 Priority: Minor Reporter: Marcos Vallim Private Registry Authentication for Tasks Private registry authentication for tasks using AWS Secrets Manager enables you to store your credentials securely and then reference them in your container definition. This allows your tasks to use images from private repositories. This feature is supported by tasks using both the Fargate or EC2 launch types. Add Comment
[JIRA] (JENKINS-54379) Jenkins gradle java.lang.interrupted exception for Jbehave Automated test
Title: Message Title Tejo K updated an issue Jenkins / JENKINS-54379 Jenkins gradle java.lang.interrupted exception for Jbehave Automated test Change By: Tejo K Priority: Minor Trivial 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-54379) Jenkins gradle java.lang.interrupted exception for Jbehave Automated test
Title: Message Title
Tejo K updated an issue
Jenkins / JENKINS-54379
Jenkins gradle java.lang.interrupted exception for Jbehave Automated test
Change By:
Tejo K
My automated JBehave test cases run fine in IntelliJ but when run as a job in Jenkins, it throws the following error. This error is not consistent with any specific test case/scenario. The job remains idle and the job fails after specific inactivity time set by me . No info on Jenkins log is seen except below. java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:502) at java.lang.UNIXProcess.waitFor(UNIXProcess.java:396) at hudson.Proc$LocalProc.join(Proc.java:324) at hudson.Launcher$ProcStarter.join(Launcher.java:474) at hudson.plugins.gradle.Gradle.performTask(Gradle.java:333) at hudson.plugins.gradle.Gradle.perform(Gradle.java:225) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1727) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) I've tried with increasing the timeout value in Storiesrunner.java to 10, but still sees the issue.configuredEmbedder() .embedderControls() .useStoryTimeouts("10") Jenkins version installed in Linux(Centos Java 1.8): Jenkins ver. 2.105 Gradle plugin: 1.9. Gradle version 4.9 performTask(Gradle.java:333) haslauncher.launch().cmds(args).envs(env).stdout(gca) .pwd(rootLauncher).join();
Add Comment
[JIRA] (JENKINS-54379) Jenkins gradle java.lang.interrupted exception for Jbehave Automated test
Title: Message Title
Tejo K created an issue
Jenkins / JENKINS-54379
Jenkins gradle java.lang.interrupted exception for Jbehave Automated test
Issue Type:
Bug
Assignee:
Stefan Wolf
Components:
gradle-plugin
Created:
2018-11-01 02:04
Priority:
Minor
Reporter:
Tejo K
My automated JBehave test cases run fine in IntelliJ but when run as a job in Jenkins, it throws the following error. This error is not consistent with any specific test case/scenario. The job remains idle and the job fails after specific inactivity. java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:502) at java.lang.UNIXProcess.waitFor(UNIXProcess.java:396) at hudson.Proc$LocalProc.join(Proc.java:324) at hudson.Launcher$ProcStarter.join(Launcher.java:474) at hudson.plugins.gradle.Gradle.performTask(Gradle.java:333) at hudson.plugins.gradle.Gradle.perform(Gradle.java:225) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1727) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) I've tried with increasing the timeout value in Storiesrunner.java to 10, but still sees the issue. configuredEmbedder() .embedderControls() .useStoryTimeouts("10") Jenkins version installed in Linux(Centos Java 1.8): Jenkins ver. 2.105 Gradle plugin: 1.9. Gradle version 4.9 performTask(Gradle.java:333) has launcher.launch().cmds(args).envs(env).stdout(gca) .pwd(rootLauncher).join();
[JIRA] (JENKINS-20155) Select All in /pluginManager/ should not select plugins with a compatWarning
Title: Message Title Philipp Nowak commented on JENKINS-20155 Re: Select All in /pluginManager/ should not select plugins with a compatWarning Proposed PR for this issue: https://github.com/jenkinsci/jenkins/pull/3715 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-46257) Improve Run Parameters folders support for auto-completion
Title: Message Title Philipp Nowak commented on JENKINS-46257 Re: Improve Run Parameters folders support for auto-completion There's an open PR for this here: https://github.com/jenkinsci/jenkins/pull/3083 Just leaving this here for others searching for `newbie-friendly` and expecting PRs to be linked in the issue. (I had pretty much the same changes done already) 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-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Nikolas Falco commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix For me it's ok 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-53707) Allow commit message and author of head commit
Title: Message Title Joseph Petersen resolved as Fixed Jenkins / JENKINS-53707 Allow commit message and author of head commit Change By: Joseph Petersen Status: Open Resolved Resolution: Fixed Released As: 2.2.14 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-54367) Cannot Rollback/Downgrade jenkins to a previous version after upgrading to a higher version
Title: Message Title Daniel Beck commented on JENKINS-54367 Re: Cannot Rollback/Downgrade jenkins to a previous version after upgrading to a higher version Don't know. In general it should be expected that major updates perform irreversible data migration. 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-49640) Don't mark builds as failed in Bitbucket when they were not built in Jenkins
Title: Message Title Joseph Petersen resolved as Fixed Jenkins / JENKINS-49640 Don't mark builds as failed in Bitbucket when they were not built in Jenkins Change By: Joseph Petersen Status: Open Resolved Resolution: Fixed Released As: 2.2.14 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-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Jon Starbird commented on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
Just the change of the brackets didn't make a difference. I used it just like I posted above but with the ${gitprops.GitVersion_FullSemVer} change. Here is the Jenkins log output for the entire Create Package stage, as you can see the app id and deployable id are set correctly.
[Pipeline] { (Create Buildmaster package)
[Pipeline] wrap
14:29:59 [BuildMaster] Sending POST to http://ca-builder3:8181/api/releases
14:29:59 [BuildMaster] With application/x-www-form-urlencoded content:
14:29:59 [BuildMaster] key=xxx=44=active
14:29:59 [BuildMaster] Inject environment variable BUILDMASTER_APPLICATION_ID=44
14:29:59 [BuildMaster] Inject environment variable BUILDMASTER_RELEASE_NUMBER=1.1.0
14:29:59 [BuildMaster] Inject environment variable BUILDMASTER_DEPLOYABLE_ID=1058
[Pipeline] {
[Pipeline] script
[Pipeline] {
[Pipeline] buildMasterCreatePackage
14:29:59 [BuildMaster] Sending GET to http://ca-builder3:8181/api/json/Applications_GetApplication?API_Key=xxx_Id=44
14:29:59 [BuildMaster] Create BuildMaster package
14:29:59 [BuildMaster] Sending PUT to http://ca-builder3:8181/api/releases/packages/create
14:29:59 [BuildMaster] With application/x-www-form-urlencoded content:
14:29:59 [BuildMaster] key=xxx=44=1.1.0
14:29:59 [BuildMaster] Wait for any active deployments to complete
14:29:59 [BuildMaster] Sending POST to http://ca-builder3:8181/api/releases/packages/deployments
14:29:59 [BuildMaster] With application/x-www-form-urlencoded content:
14:29:59 [BuildMaster] key=xxx=44=1.1.0=pending
14:29:59 [BuildMaster] Sending POST to http://ca-builder3:8181/api/releases/packages/deployments
14:29:59 [BuildMaster] With application/x-www-form-urlencoded content:
14:29:59 [BuildMaster] key=xxx=44=1.1.0=executing
14:29:59 [BuildMaster] Deploy package to next stage
14:29:59 [BuildMaster] Sending PUT to http://ca-builder3:8181/api/releases/packages/deploy
14:29:59 [BuildMaster] With application/x-www-form-urlencoded content:
14:29:59 [BuildMaster] key=xxx=44=1.1.0=181031006
14:30:00 [BuildMaster] Wait till deployment completed
14:30:00 [BuildMaster] Sending POST to http://ca-builder3:8181/api/releases/packages/deployments
14:30:00 [BuildMaster] With application/x-www-form-urlencoded content:
14:30:00 [BuildMaster] key=xxx=44=1.1.0=181031006=17131
14:30:07 [BuildMaster] Sending POST to http://ca-builder3:8181/api/releases/packages/deployments
14:30:07 [BuildMaster] With application/x-www-form-urlencoded content:
14:30:07 [BuildMaster] key=xxx=44=1.1.0=181031006=17131
[JIRA] (JENKINS-54171) Git parameter branch selector becomes slow after a period of time
Title: Message Title Boguslaw Klimas commented on JENKINS-54171 Re: Git parameter branch selector becomes slow after a period of time If is not a problem for you, you can try prepare job using some open source repositories (hosting on github) and attach config.xml. That would be very helpful in reproduce this issue in my local environment. In MultiJob project you use MultiSCM definition and you have a few/many git repository? 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-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title Jon Starbird commented on JENKINS-54286 Re: Unable to use variable tokens as build property values in Create Package in Declarative Script The appid and deployableid are being set at the top of the script in the environment section of the full script. These to values work though, it's getting to the app in BuildMaster. I will try the brackets around the git props and the API logging. I also should have been more clear, the Jenkins job does fail. I only meant I don't get errors about the script itself. It does execute the call to BuildMaster which fails with BuildMaster failing on the passed variables not being set and then the Jenkins job will fail at that stage. 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-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Andrew Sumner commented on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
$gitprops.GitVersion_FullSemVer probably needs to be ${$gitprops.GitVersion_FullSemVer} Can you turn on API logging in buildmaster section of Jenkins configuration page and reply back with the log output? How are you setting ${env.BuildMaster_appId}" and "${env.BuildMaster_deployableId}" I'm also concerned that the Jenkins job is succeeding when buildmaster is failing. That definitely should not happen. I'll try to replicate that tonight.
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-54378) Pipeline templates in parallel blocks are interpreted as being "nested"
Title: Message Title
Fernando Nasser created an issue
Jenkins / JENKINS-54378
Pipeline templates in parallel blocks are interpreted as being "nested"
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-10-31 21:10
Priority:
Major
Reporter:
Fernando Nasser
I understood that having nested pipeline {} blocks was not possible. However I found out now that one cannot run pipeline {} blocks in parallel. The reason I considered this as a Bug is that these pipeline {} blocks are not "nested" (at least visibly) which is what the documentation says it is not allowed. So this should be allowed accordingly to the documentation. I marked it as Major as it takes away possibly the major use case of "pipeline templates". A common sequence of stages that achieves some X result is made into a "pipeline template" for avoiding repeating code (DNRY) and so it can be used with different parameters many times. But having to do this many times SEQUENTIALLY is most of the times impractical as it would make the pipeline execution be too long. The only workaround would be to repeat the sequence of stages in each parallel block so not using the "pipeline template". Example: I get a java.lang.IllegalStateException: Only one pipeline { ... } block can be executed in a single run. when trying to invoke it on one of the parallel blocks: (the ettPipeline is a declarative "pipeline template"; only one of it runs perfectly to completion) try { stage('Parallel Builds') { parallel ( Build1: { node { ettPipeline ( task: "${ETT_TASK}", pkg: "${ETT_PACKAGE}", scm_url: "${SCM_URL}", clentry: "${NOTE}", email: "${EMAIL}" ) }}, Build2: { node { ettPipeline ( task: "${ETT_TASK2}",
[JIRA] (JENKINS-54171) Git parameter branch selector becomes slow after a period of time
Title: Message Title
Andrei Brajnicov edited a comment on JENKINS-54171
Re: Git parameter branch selector becomes slow after a period of time
Thank you [~klimas7] for such fast response.You pipeline was loading pretty fast for me, but unfortunately I still have issues with my deployment.Probably because my deployment job is not a pipeline, but it is a MultiJob Project. Here is a sample of my *config.xml :* {code:java} A 720703d4-a0dd-46e7-b6f1-5597c53c1be2 PT_BRANCH * origin[0-9]{0,}/(.*) NONE master NONE A.git true 5 B c1dd1635-57b5-4055-be95-5e761fd2cef9 PT_BRANCH * origin[0-9]{0,}/(.*) NONE master NONE B.git true 5 C bfb3e395-b5e4-483f-bd6b-e2292a393cf2 PT_BRANCH * origin[0-9]{0,}/(.*) NONE master NONE C.git true 5{code}^ actual config is a bit longer, as I told you I have ~ 26 repositories. !jenkins.png! I In case if it will be helpful, I can record a video with detailed example .
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-54171) Git parameter branch selector becomes slow after a period of time
Title: Message Title
Andrei Brajnicov commented on JENKINS-54171
Re: Git parameter branch selector becomes slow after a period of time
Thank you Boguslaw Klimas for such fast response. You pipeline was loading pretty fast for me, but unfortunately I still have issues with my deployment. Probably because my deployment job is not a pipeline, but it is a MultiJob Project. Here is a sample of my config.xml : **
"git-parameter@0.9.6">
A
720703d4-a0dd-46e7-b6f1-5597c53c1be2
PT_BRANCH
*
origin[0-9]{0,}/(.*)
NONE
master
NONE
A.git
true
5
"git-parameter@0.9.6">
B
c1dd1635-57b5-4055-be95-5e761fd2cef9
PT_BRANCH
*
origin[0-9]{0,}/(.*)
NONE
master
NONE
B.git
true
5
"git-parameter@0.9.6">
C
bfb3e395-b5e4-483f-bd6b-e2292a393cf2
PT_BRANCH
*
origin[0-9]{0,}/(.*)
NONE
master
NONE
C.git
true
5
^ actual config is a bit longer, as I told you I have ~ 26 repositories. I case if it will be helpful, I can record a video with detailed example
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-54171) Git parameter branch selector becomes slow after a period of time
Title: Message Title
Andrei Brajnicov edited a comment on JENKINS-54171
Re: Git parameter branch selector becomes slow after a period of time
Thank you [~klimas7] for such fast response.You pipeline was loading pretty fast for me, but unfortunately I still have issues with my deployment.Probably because my deployment job is not a pipeline, but it is a MultiJob Project. Here is a sample of my *config.xml :* ** {code:java} A 720703d4-a0dd-46e7-b6f1-5597c53c1be2 PT_BRANCH * origin[0-9]{0,}/(.*) NONE master NONE A.git true 5 B c1dd1635-57b5-4055-be95-5e761fd2cef9 PT_BRANCH * origin[0-9]{0,}/(.*) NONE master NONE B.git true 5 C bfb3e395-b5e4-483f-bd6b-e2292a393cf2 PT_BRANCH * origin[0-9]{0,}/(.*) NONE master NONE C.git true 5{code}^ actual config is a bit longer, as I told you I have ~ 26 repositories. !jenkins.png! I case if it will be helpful, I can record a video with detailed example
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-54171) Git parameter branch selector becomes slow after a period of time
Title: Message Title Andrei Brajnicov updated an issue Jenkins / JENKINS-54171 Git parameter branch selector becomes slow after a period of time Change By: Andrei Brajnicov Attachment: jenkins.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53670) Nested declarative pipelines
Title: Message Title
Fernando Nasser commented on JENKINS-53670
Re: Nested declarative pipelines
Hi Andrew, I understood that having nested pipeline {} blocks was not possible. However I found out now that one cannot run pipeline {} blocks in parallel. So I also get a java.lang.IllegalStateException: Only one pipeline { ... } block can be executed in a single run. when trying to invoke it on one of the parallel blocks: (the ettPipeline is a declarative "pipeline template"; only one of it runs perfectly to completion) try { stage('Parallel Builds') { parallel ( Build1: { node { ettPipeline ( task: "${ETT_TASK}", pkg: "${ETT_PACKAGE}", scm_url: "${SCM_URL}", clentry: "${NOTE}", email: "${EMAIL}" ) }}, Build2: { node { ettPipeline ( task: "${ETT_TASK2}", pkg: "${ETT_PACKAGE2}", scm_url: "${SCM_URL2}", clentry: "${NOTE2}", email: "${EMAIL}" ) }}, ) } } catch(e) { currentBuild.result = "FAILED" throw e }
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-54372) NoStaplerConstructorException on jenkins.plugins.git.MergeWithGitSCMExtension
Title: Message Title Mark Waite commented on JENKINS-54372 Re: NoStaplerConstructorException on jenkins.plugins.git.MergeWithGitSCMExtension May be related to workflow cps plugin 2.59 or 2.60. Unclear if the correct fix is to add DataBoundConstructor's into classes in the git plugin or to make some change in the workflow cps plugin. Sam Van Oort or Jesse Glick can you provide more guidance? 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-54372) NoStaplerConstructorException on jenkins.plugins.git.MergeWithGitSCMExtension
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-54372 NoStaplerConstructorException on jenkins.plugins.git.MergeWithGitSCMExtension Change By: Mark Waite Assignee: Mark Waite 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-50096) Integrate http://prismjs.com/ to visualize source code
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-50096 Integrate http://prismjs.com/ to visualize source code Change By: Ulli Hafner https://github.com/jenkinsci/warnings-plugin/pull/146 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-54328) When using blueocean-pipeline editor with when conditions in JenkinsFile we get errors about "Empty closure" and "Expected When Condition"
Title: Message Title Ali Aly updated an issue Jenkins / JENKINS-54328 When using blueocean-pipeline editor with when conditions in JenkinsFile we get errors about "Empty closure" and "Expected When Condition" Change By: Ali Aly Priority: Critical Major 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-54171) Git parameter branch selector becomes slow after a period of time
Title: Message Title
Boguslaw Klimas edited a comment on JENKINS-54171
Re: Git parameter branch selector becomes slow after a period of time
Hi,Thanks for test. I understood your job configuration looks similar that?{code:java}pipeline {agent anyparameters {gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_01', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_02', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_03', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_04', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_05', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_06', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_07', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_08', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_09', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_10', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_11', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_12', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_13', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_14', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_15', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_16', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_17', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_18', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_19', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_20', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_21', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_22', type: 'PT_BRANCH',
[JIRA] (JENKINS-54340) CWP throws error if pom.xml is used for plugins and casc for configuration
Title: Message Title Oleg Nenashev commented on JENKINS-54340 Re: CWP throws error if pom.xml is used for plugins and casc for configuration Thanks Michael Werner!I will try to address it and to incorporate a test case. 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-54377) Document CWP usage in Docker
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54377 Document CWP usage in Docker Issue Type: Task Assignee: Oleg Nenashev Components: custom-war-packager Created: 2018-10-31 20:02 Priority: Minor Reporter: Oleg Nenashev We have recently added an official Custom WAR Packager build: https://hub.docker.com/r/jenkins/custom-war-packager/ It needs to be documented. Usage example: https://github.com/jenkinsci/jenkinsfile-runner/tree/master/demo/cwp Add Comment This message
[JIRA] (JENKINS-54328) When using blueocean-pipeline editor with when conditions in JenkinsFile we get errors about "Empty closure" and "Expected When Condition"
Title: Message Title Ali Aly updated an issue Jenkins / JENKINS-54328 When using blueocean-pipeline editor with when conditions in JenkinsFile we get errors about "Empty closure" and "Expected When Condition" Change By: Ali Aly Priority: Minor Critical 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-54323) Create a Pipeline step to set the current build's display name, description, etc.
Title: Message Title Devin Nusbaum stopped work on JENKINS-54323 Change By: Devin Nusbaum Status: In Progress Open 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-54374) Jenkins never start on raspberry pi
Title: Message Title Damien LEFEVRE commented on JENKINS-54374 Re: Jenkins never start on raspberry pi # java -version openjdk version "1.8.0_191" OpenJDK Runtime Environment (build 1.8.0_191-b12) OpenJDK Zero VM (build 25.191-b12, interpreted mode) How would I get more detailed traces than the ones I get? 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-54035) can't exclude everything under a given dir
Title: Message Title Brian J Murrell commented on JENKINS-54035 Re: can't exclude everything under a given dir Here's the project and branch/PR that I am reproducing these results in, complete with a Jenkinsfile to build it. It's probably more in-depth and complicated than you need, but you can strip back the parts you don't need easily enough. Alternatively, I can provide you a Jenkins console log of a run of the above Jenkinsfile if that's useful and easier. 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-53963) No login methods supported exception using Poll mailbox trigger plugin
Title: Message Title
Sesha Bezawada commented on JENKINS-53963
Re: No login methods supported exception using Poll mailbox trigger plugin
Mine was resolved after setting the property properties.put("mail.smtp.ssl.enable", "true");
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-53963) No login methods supported exception using Poll mailbox trigger plugin
Title: Message Title Sesha Bezawada updated an issue Jenkins / JENKINS-53963 No login methods supported exception using Poll mailbox trigger plugin Change By: Sesha Bezawada Attachment: jenkinsemail.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52551) Make mapping of PMD levels for the Jenkins PMD plugins configurable
Title: Message Title Ulli Hafner commented on JENKINS-52551 Re: Make mapping of PMD levels for the Jenkins PMD plugins configurable The migration of the PMD parser into the warnings parser is now complete, I think we can integrate such a change into the warnings plugin 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-52560) Mark everything below hudson.plugins as deprecated and mark steps as deprecated
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-52560 Mark everything below hudson.plugins as deprecated and mark steps as deprecated Change By: Ulli Hafner Status: In Progress 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-53737) Warnings plugin - Elektrobit and GHS parser issue
Title: Message Title Ulli Hafner commented on JENKINS-53737 Re: Warnings plugin - Elektrobit and GHS parser issue Please add the lines of the console log that contain the corresponding warning. 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-53786) Flake8 found 0 issues, which should find some issues
Title: Message Title Ulli Hafner resolved as Not A Defect Jenkins / JENKINS-53786 Flake8 found 0 issues, which should find some issues Change By: Ulli Hafner Status: Open Resolved Resolution: Not A Defect 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-54376) needs documentation
Title: Message Title Fritz Platzke created an issue Jenkins / JENKINS-54376 needs documentation Issue Type: Bug Assignee: Tomas Salazar Components: nvm-wrapper-plugin Created: 2018-10-31 19:21 Priority: Minor Reporter: Fritz Platzke There are no instructions on how to use this plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54171) Git parameter branch selector becomes slow after a period of time
Title: Message Title
Boguslaw Klimas commented on JENKINS-54171
Re: Git parameter branch selector becomes slow after a period of time
Hi, Thanks for test. I understood your job configuration looks similar that?
pipeline {
agent any
parameters {
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_01', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_02', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_03', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_04', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_05', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_06', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_07', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_08', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_09', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_10', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_11', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_12', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_13', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_14', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_15', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_16', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_17', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_18', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_19', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name: 'BRANCH_20', type: 'PT_BRANCH', useRepository: '.*git-parameter-plugin.git'
gitParameter branchFilter: 'origin.*/(.*)', defaultValue: 'master', name:
[JIRA] (JENKINS-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Change By: Oleg Nenashev There is no official release flow for Jenkisnfile Runner. We need some though in some cases a rebuild from tag is required (e . g. Custom WAR Packager). 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-54375) Setup a release flow for Jenkinsfile Runner
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54375 Setup a release flow for Jenkinsfile Runner Issue Type: Task Assignee: Oleg Nenashev Components: jenkinsfile-runner Created: 2018-10-31 18:59 Priority: Minor Reporter: Oleg Nenashev There is no official release flow for Jenkisnfile Runner. We need some. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54000) Support for Taglist Maven Plugin
Title: Message Title Ulli Hafner resolved as Fixed Jenkins / JENKINS-54000 Support for Taglist Maven Plugin Change By: Ulli Hafner Status: Open Resolved Resolution: Fixed Released As: 1.0.0-beta1 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-54035) can't exclude everything under a given dir
Title: Message Title Ulli Hafner commented on JENKINS-54035 Re: can't exclude everything under a given dir I am not using the gcc compilers on my own. I need to setup a test project that compiles some c files first. Do you have an example project? Or a link to a good OSS project that I can build locally in Jenkins? 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-54374) Jenkins never start on raspberry pi
Title: Message Title Oleg Nenashev commented on JENKINS-54374 Re: Jenkins never start on raspberry pi any chance to get a stacktrace for the time the startup hangs? Full JVM version would also help 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-54367) Cannot Rollback/Downgrade jenkins to a previous version after upgrading to a higher version
Title: Message Title Oleg Nenashev commented on JENKINS-54367 Re: Cannot Rollback/Downgrade jenkins to a previous version after upgrading to a higher version As designed. Rollback can be performed only via backups. Daniel Beck do you know whether we have any kind of public documentation about the downgrade flow? 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-54373) Quality Gate failure doesn't fail the step.
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-54373 Quality Gate failure doesn't fail the step. Change By: Ulli Hafner Issue Type: Bug New Feature 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-54374) Jenkins never start on raspberry pi
Title: Message Title Damien LEFEVRE created an issue Jenkins / JENKINS-54374 Jenkins never start on raspberry pi Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2018-10-31 18:50 Environment: Raspberry pi 3+ CentOS Java JDK 1.8 Jenkins 2.138.2 Priority: Minor Reporter: Damien LEFEVRE After installing Jenkins, I start the service with systemctl start jenkins. systemctl takes a long time to return and systmctl status jenkins returns the service is running. I am not able to access jenkins from the web browser. Firewall port is open When jenkins is running 1 CPU is at 100% permanently. jenkins log doesn't report anything after: INFO: Beginning extraction from war file I've tried with JRE version 1.7 and 1.8, and get the same behavior. I also stopped jenkins service, downloaded the jenkins.war and executed it manually. Here are the traces I get. # java -jar jenkins.war Running from: /root/jenkins.war webroot: $user.home/.jenkins Oct 31, 2018 6:18:58 PM org.eclipse.jetty.util.log.Log initialized INFO: Logging initialized @139124ms to org.eclipse.jetty.util.log.JavaUtilLog Oct 31, 2018 6:19:00 PM winstone.Logger logInternal INFO: Beginning extraction from war file
[JIRA] (JENKINS-40484) Unable to use withMaven() step inside docker container for old versions of Docker
Title: Message Title Tim Downey commented on JENKINS-40484 Re: Unable to use withMaven() step inside docker container for old versions of Docker Thanks for the writeup Joshua Noble – That's pretty much exactly what Josh Trow and I have done to deal with the 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-54286) Unable to use variable tokens as build property values in Create Package in Declarative Script
Title: Message Title
Jon Starbird commented on JENKINS-54286
Re: Unable to use variable tokens as build property values in Create Package in Declarative Script
Not working for me, maybe the format isn't right. I tried it with double quotes around the variables as well as the original method of triple single quotes and neither worked. Build_Number and Job_Name are both environment variables but the gitprops.gitversion_fullsemver is from importing the gitversion properties into the job earlier. I do use it elsewhere just fine even here for the ReleaseNumber. Here is what I have currently:
buildMasterWithApplicationRelease(applicationId: "${env.BuildMaster_appId}", deployableId: "${env.BuildMaster_deployableId}") {
script {
BUILDMASTER_PACKAGE_NUMBER = buildMasterCreatePackage applicationId: BUILDMASTER_APPLICATION_ID, deployToFirstStage: true, packageNumber: BUILDMASTER_PACKAGE_NUMBER, releaseNumber: "${gitprops.GitVersion_MajorMinorPatch}",
setBuildVariables: [
preserveVariables: false,
variables: "JenkinsBuildNumber=$BUILD_NUMBER\nBuildVersion=$gitprops.GitVersion_FullSemVer\nJenkinsProject=$JOB_NAME"],
waitTillBuildCompleted: [printLogOnFailure: false]
}
}
When it runs I get no errors on the Jenkins but on the BuildMaster it fails and doesn't show any values for the passed variables.
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-54373) Quality Gate failure doesn't fail the step.
Title: Message Title Ulli Hafner commented on JENKINS-54373 Re: Quality Gate failure doesn't fail the step. This seems to be the same as for unit tests failures. 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-50550) Docker build log not sent to console output
Title: Message Title Calla Feucht commented on JENKINS-50550 Re: Docker build log not sent to console output I also see this issue on Jenkins ver. 2.137. 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-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Jesse Glick commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. An experimental build if you care to try it out. (And if you are handy with CSS, please, offer improvements.) 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-54171) Git parameter branch selector becomes slow after a period of time
Title: Message Title Andrei Brajnicov commented on JENKINS-54171 Re: Git parameter branch selector becomes slow after a period of time Hi Boguslaw Klimas I would like to inform you that I just tried to test updated version of the plugin, which was generated using this build Unfortunately the menu with branch selector was loading still slow. I was unable to notice some speed improvements. But in the cloned job, It took only 15 seconds to load all branches for my 26 projects. 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-54192) Add missing help description for sorting and number of columns configuration options
Title: Message Title Tommy Tynjä closed an issue as Fixed Jenkins / JENKINS-54192 Add missing help description for sorting and number of columns configuration options Change By: Tommy Tynjä 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-44628) Support input steps for multibranch pipelines
Title: Message Title Tommy Tynjä closed an issue as Fixed Jenkins / JENKINS-44628 Support input steps for multibranch pipelines Change By: Tommy Tynjä 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-54193) Ability to limit number of pipelines shown in Jenkins pipeline based views
Title: Message Title Tommy Tynjä closed an issue as Fixed Jenkins / JENKINS-54193 Ability to limit number of pipelines shown in Jenkins pipeline based views Change By: Tommy Tynjä 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-54192) Add missing help description for sorting and number of columns configuration options
Title: Message Title Tommy Tynjä updated JENKINS-54192 Released in Delivery Pipeline plugin 1.3.0. Jenkins / JENKINS-54192 Add missing help description for sorting and number of columns configuration options Change By: Tommy Tynjä Status: Fixed but Unreleased Resolved 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-54193) Ability to limit number of pipelines shown in Jenkins pipeline based views
Title: Message Title Tommy Tynjä updated JENKINS-54193 Released in Delivery Pipeline plugin 1.3.0. Jenkins / JENKINS-54193 Ability to limit number of pipelines shown in Jenkins pipeline based views Change By: Tommy Tynjä Status: Fixed but Unreleased Resolved 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-42322) Docker rm/stop/... commands killed by the timeout, failing builds
Title: Message Title Sam Van Oort commented on JENKINS-42322 Re: Docker rm/stop/... commands killed by the timeout, failing builds Gustavo Chaves Which version of Docker itself are you using, and do you see the timeout error, or just the error "Failed to rm container" ? 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-54191) Persist task finished time
Title: Message Title Tommy Tynjä resolved as Fixed Released in Delivery Pipeline plugin 1.3.0 Jenkins / JENKINS-54191 Persist task finished time Change By: Tommy Tynjä Status: Open 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-53449) Pipeline input step not working when component name is not matching job name
Title: Message Title Tommy Tynjä closed an issue as Fixed Jenkins / JENKINS-53449 Pipeline input step not working when component name is not matching job name Change By: Tommy Tynjä 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-54191) Persist task finished time
Title: Message Title Tommy Tynjä closed an issue as Fixed Jenkins / JENKINS-54191 Persist task finished time Change By: Tommy Tynjä 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-54354) Jenkins Window slave can not fetch from bitbucket
Title: Message Title Xavier Fustero reopened an issue Jenkins / JENKINS-54354 Jenkins Window slave can not fetch from bitbucket Change By: Xavier Fustero Resolution: Not A Defect Status: Closed 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-44628) Support input steps for multibranch pipelines
Title: Message Title Tommy Tynjä updated JENKINS-44628 Released in Delivery Pipeline plugin 1.3.0 Jenkins / JENKINS-44628 Support input steps for multibranch pipelines Change By: Tommy Tynjä Status: Fixed but Unreleased Resolved 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-53449) Pipeline input step not working when component name is not matching job name
Title: Message Title Tommy Tynjä updated JENKINS-53449 Released in Delivery Pipeline plugin 1.3.0 Jenkins / JENKINS-53449 Pipeline input step not working when component name is not matching job name Change By: Tommy Tynjä Status: Fixed but Unreleased Resolved 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-54373) Quality Gate failure doesn't fail the step.
Title: Message Title Gennady Feldman created an issue Jenkins / JENKINS-54373 Quality Gate failure doesn't fail the step. Issue Type: Bug Assignee: Ulli Hafner Attachments: warnings-log1.PNG, warnings-step1.PNG Components: warnings-ng-plugin Created: 2018-10-31 16:18 Priority: Major Reporter: Gennady Feldman Running with warnings-ng-plugin 1.0.0beta1 and using quality gate settings to trigger a build failure I am not seeing any visual indicators as to why the pipeline failed in Blue ocean. However I see everything show up as "green" and no clue as to why build failed unless I exit out of Blue Ocean UI. I'll attach some images to show what I mean. Add Comment
[JIRA] (JENKINS-54354) Jenkins Window slave can not fetch from bitbucket
Title: Message Title Xavier Fustero edited a comment on JENKINS-54354 Re: Jenkins Window slave can not fetch from bitbucket I have checked the swarm process and it runs under SYSTEM user in windows. This user refers toC:\Windows\System32\config\systemprofile\I have created the .ssh directory under above dir and copied the private key. I go to Jenkins job and remove Git from *Source Code Management* and add creating "Execute Windows Batch command" in in Build section. I put the following command there:git clone ssh://g...@git.clarivate.io/ls-editorial/ls-jpharm-gui-qa-tests-acceptance.gitThis worked and cloned the repo under my worksapce D:\workspaces\SYS-TEST successfullyHowever, when using the Source Code Management I get the error from the description. Mark, I reopen it to see if you can take a look again and explain why it works one way but not the other way.Thanks 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-54354) Jenkins Window slave can not fetch from bitbucket
Title: Message Title Xavier Fustero commented on JENKINS-54354 Re: Jenkins Window slave can not fetch from bitbucket I have checked the swarm process and it runs under SYSTEM user in windows. This user refers to C:\Windows\System32\config\systemprofile\ I have created the .ssh directory under above dir and copied the private key. I go to Jenkins job and remove Git from Source Code Management and add creating "Execute Windows Batch command" in in Build section. I put the following command there: git clone ssh://g...@git.clarivate.io/ls-editorial/ls-jpharm-gui-qa-tests-acceptance.git This worked and cloned the repo under my worksapce D:\workspaces\SYS-TEST successfully However, when using the Source Code Management I get the error from the description. 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-54372) NoStaplerConstructorException on jenkins.plugins.git.MergeWithGitSCMExtension
Title: Message Title Martin _ created an issue Jenkins / JENKINS-54372 NoStaplerConstructorException on jenkins.plugins.git.MergeWithGitSCMExtension Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-10-31 16:06 Environment: Jenkins 2.138.2 Pipeline 2.6 Git 3.8.0/3.9.1 (both tested) Git client plugin 2.7.3 Labels: regression pipeline Priority: Minor Reporter: Martin _ After updating Jenkins plugins to latest today, Jenkins master is periodically logging a warning when running pipelines involving git checkout: Oct 31, 2018 3:40:40 PM org.jenkinsci.plugins.workflow.cps.DSL invokeStep WARNING: Error storing the arguments for step: checkout org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class jenkins.plugins.git.MergeWithGitSCMExtension at org.kohsuke.stapler.ClassDescriptor.loadConstructorParamNames (ClassDescriptor.java:265) at org.jenkinsci.plugins.structs.describable.DescribableModel. (DescribableModel.java:144) at org.jenkinsci.plugins.structs.describable.DescribableModel.of (DescribableModel.java:114) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeObjectAndRecordMutation (ArgumentsActionImpl.java:294) at org.jenkinsci.plugins.workflow.cps.actions.ArgumentsActionImpl.sanitizeListAndRecordMutation (ArgumentsActionImpl.java:242) at
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title
Joseph Green commented on JENKINS-50429
Re: Shell command are really slower than before
I've tested combining all the env vars into a single command and that makes no difference. My test command was this:
def label = "slow-${UUID.randomUUID().toString()}"
podTemplate(label: label) {
node(label){
stage('20 calls outside container'){
for (i = 0; i <20; i++) {
sh "date"
}
}
stage('20 calls inside container'){
container("jnlp"){
for (i = 0; i <20; i++) {
sh "date"
}
}
}
}
}
Results were pretty consistently: Outside container: ~12 seconds Inside container: ~1min 10 seconds Individual sh calls for the `date` command were: Outside container: ~400ms Inside container: ~3 seconds Commenting out all the env variable setting only reduced the individual container time to 1s... This seems to tally with the stack overflow post reporting the piped input stream bug. (https://github.com/karianna/jdk8_tl/blob/master/jdk/src/share/classes/java/io/PipedInputStream.java#L274) ?? I tried combining the env variables into a single set before sending them, which reduced the time spent inside the container to 30 seconds. There's a PR for that here... https://github.com/jenkinsci/kubernetes-plugin/pull/393
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-54371) Monitoring plugin not pushing slave metrics to InfluxDB
Title: Message Title Puneeth Nanjundaswamy created an issue Jenkins / JENKINS-54371 Monitoring plugin not pushing slave metrics to InfluxDB Issue Type: Bug Assignee: evernat Components: monitoring-plugin Created: 2018-10-31 15:28 Priority: Blocker Reporter: Puneeth Nanjundaswamy The javamelody monitoring plugin doesn't seem to send metrics of slaves to InfluxDB. I can only see metrics from the master. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-50741) NPE on git.exe rev-list
Title: Message Title Timothy Kim commented on JENKINS-50741 Re: NPE on git.exe rev-list I got the same error. Commit message: "TP-40149 Set version number" > git rev-list --no-walk 6cb09529ee81434a2afa17fb2efa3063fec7505f # timeout=10 ERROR: Processing failed due to a bug in the code. Please report this to the issue tracker ( https://jenkins.io/redirect/report-an-issue ). java.lang.RuntimeException: java.lang.NullPointerException at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.buildEnvVars(MavenExtractorEnvironment.java:143) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:881) at hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:57) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:168) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:634) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1806) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: java.lang.NullPointerException at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.createPublisherContext(MavenExtractorEnvironment.java:220) at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.buildEnvVars(MavenExtractorEnvironment.java:129) ... 9 more project=hudson.maven.MavenModuleSet@6e26dab9[EBS/HotDeploy/smsmi-960/Build/Base/BuildBaseLangJar] project.getModules()=[hudson.maven.MavenModule@5f8cdd1b[EBS/HotDeploy/smsmi-960/Build/Base/BuildBaseLangJar/com.tecsys:tecsys-base-lang][EBS/HotDeploy/smsmi-960/Build/Base/BuildBaseLangJar/com.tecsys:tecsys-base-lang][relativePath:tecsys-base-lang]] project.getRootModule()=hudson.maven.MavenModule@5f8cdd1b[EBS/HotDeploy/smsmi-960/Build/Base/BuildBaseLangJar/com.tecsys:tecsys-base-lang][EBS/HotDeploy/smsmi-960/Build/Base/BuildBaseLangJar/com.tecsys:tecsys-base-lang][relativePath:tecsys-base-lang] FATAL: java.lang.NullPointerException java.lang.NullPointerException at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.createPublisherContext(MavenExtractorEnvironment.java:220) at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.buildEnvVars(MavenExtractorEnvironment.java:129) Caused: java.lang.RuntimeException at org.jfrog.hudson.maven3.extractor.MavenExtractorEnvironment.buildEnvVars(MavenExtractorEnvironment.java:143) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:881) at hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:57) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:168) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:634) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1806) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) [Office365connector] No webhooks to notify Finished: FAILURE
[JIRA] (JENKINS-54299) Jenkins failed to start after updating pluins and restart
Title: Message Title Devin Nusbaum closed an issue as Not A Defect Sam Tang I am glad to hear that the issue is fixed for you. I think it is very likely that the outdated Jenkins version was the problem. My guess is that when you manually updated dependencies you ended up with a plugin whose version was not compatible with 2.32.3. Normally in this case, you should get errors about "Failed to load plugin" in your Jenkins startup logs that indicate the version mismatch, so if you did not see those messages maybe your problem was something else, although I do not have any other ideas of what could have happened. Jenkins / JENKINS-54299 Jenkins failed to start after updating pluins and restart Change By: Devin Nusbaum Status: Open Closed Resolution: Not A Defect 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
[JIRA] (JENKINS-54313) null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186)
Title: Message Title James Nord edited a comment on JENKINS-54313 Re: null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186) a secret is required to have the annotation for its display name if it is labelled as a Jenkins credential. It shouldn't blow up but it should also not be tollerant to this. If this prevents handling of the specific credential but all others are ok then this is ok - but it should throw a more meaningful error message in this case 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-54313) null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186)
Title: Message Title James Nord commented on JENKINS-54313 Re: null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186) a secret is required to have the annotation for its display name if it is labelled as a Jenkins credential. 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-54370) false positive SCM triggers
Title: Message Title Andrei Brajnicov updated an issue Jenkins / JENKINS-54370 false positive SCM triggers Change By: Andrei Brajnicov Summary: False false positive SCM triggers 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-54370) False SCM triggers
Title: Message Title Andrei Brajnicov created an issue Jenkins / JENKINS-54370 False SCM triggers Issue Type: Bug Assignee: Unassigned Attachments: poll.png, started_by_an-SCM-CHange.png Components: core Created: 2018-10-31 14:25 Environment: Ubuntu: 18.04.1 Jenkins: 2.138.2 All plugins updated to latest version Priority: Major Reporter: Andrei Brajnicov Hello Jenkins Team. I have a MultiJob Project with about 30 GIT Repositories added to it. This job is parameterized using Git Parameter Plug-In and Poll SCM is DISABLED for this project. This job is launched manually. But sometimes during build this job is triggered somehow by SCM. As a result another build of the same job is queued. I can't understand how it happens, taking in consideration that Poll SCM is disabled for this project: I suppose that this is bug. I would be happy if this issue will be solved. Please let me know if you need some additional info.
[JIRA] (JENKINS-54369) Env-inject writing \u0000 in injectedEnvVars.txt from windows slave
Title: Message Title
Robson Hermes updated an issue
Jenkins / JENKINS-54369
Env-inject writing \u in injectedEnvVars.txt from windows slave
Change By:
Robson Hermes
I am having a problem with the envInject, cause it seems to be writing NUL (Unicode char) from the env of a Windows slave. 1 - Basically I am creating a new job which runs in a Windows slave. This job executes a powershell code that writes variables to a file env.properties (attachment 01.png). I am doing that cause these values are used later in other job steps.2 - The file is written without any problems in the windows slave (attachment 02.png)3 - When I try to run the job the next time, I have the error: {code:java}java.lang.IllegalArgumentException: Invalid environment variable name: "CURRENT_ARCHIVE" at java.lang.ProcessEnvironment.validateName(Unknown Source) at java.lang.ProcessEnvironment.put(Unknown Source) at java.lang.ProcessEnvironment.put(Unknown Source) at hudson.Proc$LocalProc.environment(Proc.java:234) at hudson.Proc$LocalProc.(Proc.java:219){code} 4 - As you can see, apparently the name of the variable is fine. However, if I open the injectedEnvVars.txt in our Linux master, between each char, envinject added a u char, which causes the method ProcessEnvironment.validateName to throw an exception. (see attachments 03 and 04) All other variables are fine. Just the ones I wrote are messed up. Result is that I can run the job only first time. Any subsequent attempt fails, that's why I classified as major. Sorry if this interpretation is incorrect.
Add Comment
[JIRA] (JENKINS-47823) withMaven fails to inject Maven settings files with docker-pipeline 1.14
Title: Message Title Joshua Noble commented on JENKINS-47823 Re: withMaven fails to inject Maven settings files with docker-pipeline 1.14 Josh Trow I know it's been a year, but I came up with a workaround for not having to update every mvn call here: https://issues.jenkins-ci.org/browse/JENKINS-40484?focusedCommentId=352635=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-352635 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-40484) Unable to use withMaven() step inside docker container for old versions of Docker
Title: Message Title Joshua Noble commented on JENKINS-40484 Re: Unable to use withMaven() step inside docker container for old versions of Docker I spent a good amount of time looking into this and came up with an acceptable workaround that works for my team. We have hundreds of branches across hundreds of repos, so updating all of the Java/Maven related Jenkinsfiles (on every branch) to use $MVN_CMD instead of "mvn" was not going to happen anytime soon. We also had several pending plugin updates, many of which required the latest version of the pipeline-maven plugin. In our case, we have a private internal Docker image that we use for all maven builds. It's forked off the official Docker Hub Maven image and includes a few additional tools and packages that we need. What I ended up doing was creating a bash script that simply wraps the "mvn" command and checks for existence of $MVN_CMD. If $MVN_CMD exists, it calls that and passes along the same parameters. If $MVN_CMD doesn't exist, it simply calls the real maven binary located at /usr/bin/mvn. This bash script lives at /usr/local/bin/mvn, which exists in our $PATH before the real maven binary, which is /usr/bin/mvn. Simply create a bash script like below, and ensure it has execute permissions: (chmod +x mvn.sh) #!/bin/bash if [[ -v MVN_CMD ]]; then $MVN_CMD "$@" else /usr/bin/mvn "$@" fi Then inside of your Dockerfile, add the following instruction: COPY mvn.sh /usr/local/bin/mvn This has been tested with the maven:3.5.3-jdk-8 Docker image. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-54369) Env-inject writing \u0000 in injectedEnvVars.txt from windows slave
Title: Message Title Robson Hermes updated an issue Jenkins / JENKINS-54369 Env-inject writing \u in injectedEnvVars.txt from windows slave Change By: Robson Hermes Attachment: 03.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54369) Env-inject writing \u0000 in injectedEnvVars.txt from windows slave
Title: Message Title Robson Hermes updated an issue Jenkins / JENKINS-54369 Env-inject writing \u in injectedEnvVars.txt from windows slave Change By: Robson Hermes Attachment: 03.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54369) Env-inject writing \u0000 in injectedEnvVars.txt from windows slave
Title: Message Title Robson Hermes updated an issue Jenkins / JENKINS-54369 Env-inject writing \u in injectedEnvVars.txt from windows slave Change By: Robson Hermes Attachment: 02.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54369) Env-inject writing \u0000 in injectedEnvVars.txt from windows slave
Title: Message Title Robson Hermes updated an issue Jenkins / JENKINS-54369 Env-inject writing \u in injectedEnvVars.txt from windows slave Change By: Robson Hermes Attachment: 02.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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54369) Env-inject writing \u0000 in injectedEnvVars.txt from windows slave
Title: Message Title Robson Hermes created an issue Jenkins / JENKINS-54369 Env-inject writing \u in injectedEnvVars.txt from windows slave Issue Type: Bug Assignee: Unassigned Attachments: 01.png, 02.png, 03.png, 04.png Components: envinject-plugin Created: 2018-10-31 14:11 Environment: jenkins master: Debian 8 Jenkins ver. 2.110 envinject 2.1.3 jenkins slave: Windows Server 2016 Labels: plugin environment Priority: Major Reporter: Robson Hermes I am having a problem with the envInject, cause it seems to be writing NUL (Unicode char) from the env of a Windows slave. 1 - Basically I am creating a new job which runs in a Windows slave. This job executes a powershell code that writes variables to a file env.properties (attachment 01.png). I am doing that cause these values are used later in other job steps. 2 - The file is written without any problems in the windows slave (attachment 02.png) 3 - When I try to run the job the next time, I have the error: java.lang.IllegalArgumentException: Invalid environment variable name: "CURRENT_ARCHIVE" at java.lang.ProcessEnvironment.validateName(Unknown Source) at java.lang.ProcessEnvironment.put(Unknown Source) at
[JIRA] (JENKINS-53237) Maven Surefire Report XSD requires a fix
Title: Message Title Tibor Digana commented on JENKINS-53237 Re: Maven Surefire Report XSD requires a fix Nikolas Falco If there are no objections I will introduce XML version in the XSD schema and we will proceed with plugin version 3.0.0-M1. We will have multiple versions of this XML in web deployment and the old versions of plugin would be validated against the old schema. I will open a pull request where you can have a look if you like and this way you will have the result under your control. Is this fair? 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-51757) After chaging the home directory of Jenkins, htmlpublisher plugin is archiving to the old directory and not the new path /home/jenkins
Title: Message Title Jakub Pawlinski commented on JENKINS-51757 Re: After chaging the home directory of Jenkins, htmlpublisher plugin is archiving to the old directory and not the new path /home/jenkins Ok, after longer investigation it is not related - just error output is messing up this error actually means that source location is empty. 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-54333) Projects are triggered twice by "build with parameters"
Title: Message Title Martin Mössner commented on JENKINS-54333 Re: Projects are triggered twice by "build with parameters" Same behaviour with our jenkins installation. We've rolled back to 2.147. Thanks for fixing. 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-54368) Jenkins Tests Recovery operations support
Title: Message Title Anda Sorina Laakso created an issue Jenkins / JENKINS-54368 Jenkins Tests Recovery operations support Issue Type: New Feature Assignee: Anda Sorina Laakso Attachments: Jenkins Tests Recovery operations support.docx Components: hp-application-automation-tools-plugin Created: 2018-10-31 12:16 Labels: UFT Priority: Major Reporter: Anda Sorina Laakso User would like the option present also in ALM to manage what to do in case a test / test set failed the execution. For example: Retry running the test Retry running the entire test set Retry running the test / test set after a cleanup process is performed
[JIRA] (JENKINS-54362) java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixBuild
Title: Message Title Jack Newcombe commented on JENKINS-54362 Re: java.lang.RuntimeException: Failed to serialize hudson.model.Actionable#actions for class hudson.matrix.MatrixBuild Yes, I have build-name-setter 1.6.7 I also find that build name setter only works when setting at the start of the build, but not the end (causes a similar IOException) 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.
