[JIRA] (JENKINS-54278) Pipeline builds fail when cleanWs() in post stage
Title: Message Title Michael Forstner commented on JENKINS-54278 Re: Pipeline builds fail when cleanWs() in post stage Upgraded all plugins in my latest LTS Jenkins instance (2.138.2) and now my issue disappeared, so most likely it was not caused by the cleanWs() plugin. 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-10273) Possibility to use environment variables or parameters
Title: Message Title Ashok Kumar commented on JENKINS-10273 Re: Possibility to use environment variables or parameters I Still can't able to get the environmental variable in the email (HTML)section of the jenkins job 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-10273) Possibility to use environment variables or parameters
Title: Message Title Ashok Kumar commented on JENKINS-10273 Re: Possibility to use environment variables or parameters Still $BUILD_NUMBER is not supported please tell me the changes to be made for this particular concern. 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-54331) Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13
Title: Message Title Torsten Kleiber created an issue Jenkins / JENKINS-54331 Bitbucket Minimum Successful Merge Check does not work from Bitbucket Branch Source version 2.2.13 Issue Type: Bug Assignee: Unassigned Attachments: 1_new_plugin_version_two_jenkins_builds.png, 2_new_plugin_only_last_build_update_is_shown_1.png, 3_new_plugin_only_last_build_update_is_shown.png, 4_new_plugin_only_last_build_update_is_shown.png, 5_old_plugin_version_two_jenkins_builds.png, 6_old_plugin_2_builds_of_branch_and_pr_are_shown.png, 7_old_plugin_2_builds_of_branch_and_pr_are_shown.png Components: bitbucket-branch-source-plugin Created: 2018-10-30 07:27 Environment: Jenkins 2.138.2, Bitbucket Branch Source Plugin 2.2.13 Priority: Major Reporter: Torsten Kleiber We use here Bitbucket Merge Checks. We have defined 2 required successful build for merge, one for the branch itself and one for the pull request. This ensure that the master remains clean after the merge. Till 2.2.12 both builds are shown in Bitbucket. From 2.2.13 on only the last branch or pull request build update is shown, so the merge check can never fulfilled anymore!
[JIRA] (JENKINS-54332) New Parameters option, specifying separate parameters for each separate job
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-54332 New Parameters option, specifying separate parameters for each separate job Issue Type: Improvement Assignee: Unassigned Attachments: image-2018-10-30-08-28-52-881.png Components: parameterized-trigger-plugin Created: 2018-10-30 07:40 Priority: Major Reporter: Flemming Steffensen TL;DR; Allow each Project started to receive individual parameters. I started out thinking this was a bug/omission in the existing "Parameters from properties file" option, but I now believe this should be a separate properties option: "Individual project parameters from properties file" It's close to the functionality of the "Parameters from properties file" option, but with a critical difference: Each project specified in the "Projects to build", receive individual parameters. A pictures explains it better: All other functionality from the "Parameters from properties file" are still useful, and should remain. Also note that it's not smart to add it as an option to the "Parameters from properties file" option, as it may still be needed to supply some common parameters to all projects.
[JIRA] (JENKINS-54333) Projects are triggered twice by "build with parameters"
Title: Message Title wang ying created an issue Jenkins / JENKINS-54333 Projects are triggered twice by "build with parameters" Issue Type: Bug Assignee: Unassigned Components: parameterized-trigger-plugin Created: 2018-10-30 07:47 Environment: Jenkins ver.2.149 and Jenkens ver.2.148 Parameterized Trigger plugin 2.35.2 Labels: plugin Priority: Major Reporter: wang ying Projects are triggered twice which are using "Parameterized Trigger plugin". Add Comment
[JIRA] (JENKINS-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias created an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2018-10-30 08:14
Environment:
Jenkins 2.121.1 Jenkins 2.138.2 Plugins installed: "git": "3.9.1", "git-client": "2.7.3", "git-server": "1.7", "github": "1.29.2", "github-api": "1.92", and many more
Priority:
Minor
Reporter:
Croydon Dias
On our jenkins master, we've configured two git tools to be used on our slaves on the {{http:///jenkins/webapp/configureTools/ }} page
Default - Linux git binary
/usr/bin/git
gitwin - Windows git binary
C:\Program Files\Git\bin\git
Every Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.
[JIRA] (JENKINS-52055) A problem occurred while processing the request. Please check after installing gitlab plugin
Title: Message Title ahamed hussain mahsoom updated JENKINS-52055 Jenkins / JENKINS-52055 A problem occurred while processing the request. Please check after installing gitlab plugin Change By: ahamed hussain mahsoom 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-52055) A problem occurred while processing the request. Please check after installing gitlab plugin
Title: Message Title ahamed hussain mahsoom updated JENKINS-52055 Jenkins / JENKINS-52055 A problem occurred while processing the request. Please check after installing gitlab plugin Change By: ahamed hussain mahsoom Status: Closed In 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-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master, we've configured two git tools to be used on our slaves on the \{{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master. For a Pipeline job with the Jenkinsfile stored in the jobs config.xml - a job scheduled on a windows node correctly picked up the \{{git tool}} configured For a Pipeline job with the Jenkinsfile stored in SCM - a job scheduled on a windows node does not correctly picked up the \{{git tool}} configured. Instead it default to the first configured tool, which happens to be a linux path and hence fails on windows.
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 opt
[JIRA] (JENKINS-54296) Docker cannot be used right after agent provisioning without sudo
Title: Message Title Dominik Bartholdi commented on JENKINS-54296 Re: Docker cannot be used right after agent provisioning without sudo I worked around this by setting up my own AMI where docker is already installed 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-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master, we've configured two git tools to be used on our slaves on the \{{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs config.xml - a job scheduled on a windows node correctly picked up the \ {{git tool}} configured {{pipeline { agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { parallel { stage('Windows') {steps { echo "Compiling code" sleep 10} } }}} For a Pipeline job with the Jenkinsfile stored in SCM - a job scheduled on a windows node does not correctly picked up the \ {{git tool}} configured. Instead it default to the first configured tool, which happens to be a linux path and hence fails on windows.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master, we've configured two git tools to be used on our slaves on the \{{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs config.xml - a job scheduled on a windows node correctly picked up the {{git tool}} configured{ { noformat} pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { parallel { stage('Windows') {steps { echo "Compiling code" sleep 10} } }}}}} {noformat } } For a Pipeline job with the Jenkinsfile stored in SCM - a job scheduled on a windows node does not correctly picked up the {{git tool}} configured. Instead it default to the first configured tool, which happens to be a linux path and hence fails on windows.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master, we've configured two git tools to be used on our slaves on the \{{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs ' config.xml - a job scheduled on a windows node correctly picked up the configured {{git tool}} configured {noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { parallel { stage('Windows') {steps { echo "Compiling code" sleep 10} } }}}}}{noformat} For a Pipeline job with the Jenkinsfile (same Jenkinsfile as listed above) stored in SCM - a job scheduled on a windows node does not correctly picked up the {{git tool}} configured. Instead it default to the first configured tool, which happens to be a linux path and hence fails on windows.
Add Comment
This message was sent by Atlassian Jira (
[JIRA] (JENKINS-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master, we've configured two git tools to be used on our slaves on the \{{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs' config.xml - a job scheduled on a windows node correctly picked up the configured {{git tool}} {noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { parallel { stage('Windows') {steps { echo "Compiling code" sleep 10} } }}}}}{noformat} For a Pipeline job with the Jenkinsfile (same Jenkinsfile as listed above) stored in SCM - a job scheduled on a windows node does not correctly picked up the {{git tool}} configured. Instead it default to the first configured tool, which happens to be a linux path and hence fails on windows. The [following blog post|http://flatland-thoughts.blogspot.com/2017/05/multiple-git-tools-in-jenkins-scripted.html] documents this issue and suggests using the {{checkout}} pipeline step to override the {{gitTool}}. I tried this and it didn't work either.
Add Comment
[JIRA] (JENKINS-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master, we've configured two git tools to be used on our slaves on the \{{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs' config.xml - a job scheduled on a windows node correctly picked up the configured {{git tool}} {noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { echo "Compiling code" sleep 10} }}}} } {noformat} For a Pipeline job with the Jenkinsfile (same Jenkinsfile as listed above) stored in SCM - a job scheduled on a windows node does not correctly picked up the {{git tool}} configured. Instead it default to the first configured tool, which happens to be a linux path and hence fails on windows. The [following blog post|http://flatland-thoughts.blogspot.com/2017/05/multiple-git-tools-in-jenkins-scripted.html] documents this issue and suggests using the {{checkout}} pipeline step to override the {{gitTool}}. I tried this and it didn't work either.
Add Comment
[JIRA] (JENKINS-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master, we've configured two git tools to be used on our slaves on the \{{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs' config.xml - a job scheduled on a windows node correctly picked up the configured {{git tool}} {noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { parallel { stage('Windows') {steps { echo "Compiling code" sleep 10} } }}}} } {noformat} For a Pipeline job with the Jenkinsfile (same Jenkinsfile as listed above) stored in SCM - a job scheduled on a windows node does not correctly picked up the {{git tool}} configured. Instead it default to the first configured tool, which happens to be a linux path and hence fails on windows. The [following blog post|http://flatland-thoughts.blogspot.com/2017/05/multiple-git-tools-in-jenkins-scripted.html] documents this issue and suggests using the {{checkout}} pipeline step to override the {{gitTool}}. I tried this and it didn't work either.
Add Comment
[JIRA] (JENKINS-54335) Upstream Downstream Column plugin displays wrong data
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-54335 Upstream Downstream Column plugin displays wrong data Issue Type: Improvement Assignee: Lucie Votypkova Attachments: image-2018-10-30-09-15-51-040.png Components: core Created: 2018-10-30 08:35 Environment: Upstream Downstream Column Plugin version 1.006 Folders Plugin 6.6 Jenkins version 2.149 Labels: plugin Priority: Major Reporter: Flemming Steffensen Raw HTML is now displayed, instead of rendered HTML: "model-link inside" href="" class="code-quote" style="color: #009100">"/job/Jenkins_Test/job/MultiCall/job/Test_Main/">Jenkins_Test » MultiCall » Test_Main Looking at the page source, it's a simple case of < used instead of < and < used instead of >. Example picture: Note, This Issue is assigned directly to the maintainer of the Upstream Downstream Column Plugin. As I were unable to find the proper component, I choose to set it as core, as I assume the first rely on the other. Please update as required.
[JIRA] (JENKINS-54041) EC2 Plugin no longer able to start build slaves
Title: Message Title
David Goate commented on JENKINS-54041
Re: EC2 Plugin no longer able to start build slaves
Further note on something I see in the logs which may be related/help debug the issue:
Oct 30, 2018 8:34:38 AM INFO hudson.plugins.ec2.EC2Cloud provisionSlaveTemplate{ami='ami-xxx', labels='cloud-slave'}. Attempting to provision slave needed by excess workload of 2 units
Oct 30, 2018 8:34:38 AM INFO hudson.plugins.ec2.EC2Cloud getNewOrExistingAvailableSlaveSlaveTemplate{ami='ami-xxx', labels='cloud-slave'}. Cannot provision - no capacity for instances: 0
Oct 30, 2018 8:34:38 AM WARNING hudson.plugins.ec2.EC2Cloud provisionCan't raise nodes for SlaveTemplate{ami='ami-xxx', labels='cloud-slave'}
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-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master, we've configured two git tools to be used on our slaves on the \{{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs' config.xml - a job scheduled on a windows node correctly picked up the configured {{git tool}} {noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { echo "Compiling code" sleep 10} }}}}{noformat} For a Pipeline job with the Jenkinsfile (same Jenkinsfile as listed above) stored in SCM - a job scheduled on a windows node does not correctly picked up the {{git tool}} configured. Instead it default to the first configured tool, which happens to be a linux path and hence fails on windows. The [following blog post|http://flatland-thoughts.blogspot.com/2017/05/multiple-git-tools-in-jenkins-scripted.html] documents this issue and suggests using the {{checkout}} pipeline step to override the {{gitTool}}. I tried this and it didn't work either. {noformat} pipeline { agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { checkout([ $class: 'GitSCM', branches: [[name: '*/master']], gitTool: 'gitwin', userRemoteConfigs: [[ credentialsId: null, url: 'http:// < internally-hosted-git-url>.git'] ] ]) echo "Compiling code" sleep 10} }}}}{noformat}< Still editing>
Add Com
[JIRA] (JENKINS-54336) consider adding pipeline-utility-steps-plugin to essentials
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-54336 consider adding pipeline-utility-steps-plugin to essentials Issue Type: New Feature Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-30 08:36 Priority: Minor Reporter: Dominik Bartholdi I find myself to use the pipeline-utility-steps-plugin[1] more and more, it has some very useful utilities like reading information from a maven pom or other configuration files. I think these simple steps are useful for many many users and are a good addition to the provided functionality in evergreen. [1] https://plugins.jenkins.io/pipeline-utility-steps Add Comment
[JIRA] (JENKINS-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master, we've configured two git tools to be used on our slaves on the \{{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs' config.xml - a job scheduled on a windows node correctly picked up the configured {{git tool}} {noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { echo "Compiling code" sleep 10} }}}}{noformat} For a Pipeline job with the Jenkinsfile (same Jenkinsfile as listed above) stored in SCM - a job scheduled on a windows node does not correctly picked up the {{git tool}} configured. Instead it default to the first configured tool, which happens to be a linux path and hence fails on windows. The [following blog post|http://flatland-thoughts.blogspot.com/2017/05/multiple-git-tools-in-jenkins-scripted.html] documents this issue and suggests using the {{checkout}} pipeline step to override the {{gitTool}}. I tried this and it didn't work either.{noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { checkout([ $class: 'GitSCM', branches: [[name: '*/master']], gitTool: 'gitwin', userRemoteConfigs: [ [ credentialsId: null, url: 'http://.git' ] ] ]) echo "Compiling code" sleep 10} }}}}{noformat}
Add Comment
[JIRA] (JENKINS-54335) Upstream Downstream Column plugin displays wrong data
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-54335
Upstream Downstream Column plugin displays wrong data
Change By:
Flemming Steffensen
Raw HTML is now displayed, instead of rendered HTML: {code:java}Jenkins_Test » MultiCall » Test_Main{code} Looking at the page source, it's a simple case of *<* used instead of *<* and *<* used instead of *>.* Example picture:!image-2018-10-30-09-15-51-040.png! Note, This Issue is assigned directly to the maintainer of the *Upstream Downstream Column Plugin*. As I were unable to find the proper component, I choose to set it as *core*, as I assume the first rely on the other. Please update as required.
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-40904) [pipeline-maven-plugin] Expose Maven "--debug" config parameter at the folder/global config level
Title: Message Title Cyrille Le Clerc closed an issue as Won't Do no activity. close as won't fix Jenkins / JENKINS-40904 [pipeline-maven-plugin] Expose Maven "--debug" config parameter at the folder/global config level Change By: Cyrille Le Clerc Status: Open Closed Resolution: Won't Do 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-42195) Use POJOS and JAXB instead of schemaless XML between the maven event spy and the withMaven plugin
Title: Message Title Cyrille Le Clerc closed an issue as Won't Fix no activity, close as won't fix for the moment Jenkins / JENKINS-42195 Use POJOS and JAXB instead of schemaless XML between the maven event spy and the withMaven plugin Change By: Cyrille Le Clerc Status: Open Closed Resolution: Won't Fix 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-42195) Use POJOS and JAXB instead of schemaless XML between the maven event spy and the withMaven plugin
Title: Message Title Cyrille Le Clerc reopened an issue Jenkins / JENKINS-42195 Use POJOS and JAXB instead of schemaless XML between the maven event spy and the withMaven plugin Change By: Cyrille Le Clerc Resolution: Won't Fix 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-42195) Use POJOS and JAXB instead of schemaless XML between the maven event spy and the withMaven plugin
Title: Message Title Cyrille Le Clerc closed an issue as Won't Do Jenkins / JENKINS-42195 Use POJOS and JAXB instead of schemaless XML between the maven event spy and the withMaven plugin Change By: Cyrille Le Clerc Status: Reopened Closed Resolution: Won't Do 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-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master, we've configured two git tools to be used on our slaves on the \{{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs' config.xml - a job scheduled on a windows node correctly picked up the configured {{git tool}} {noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { echo "Compiling code" sleep 10} }}}}{noformat} For a Pipeline job with the Jenkinsfile (same Jenkinsfile as listed above) stored in SCM - a job scheduled on a windows node does not correctly picked up the {{git tool}} configured. Instead it default to the first configured tool, which happens to be a linux path and hence fails on windows. The [following blog post|http://flatland-thoughts.blogspot.com/2017/05/multiple-git-tools-in-jenkins-scripted.html] documents this issue and suggests using the {{checkout}} pipeline step to override the {{gitTool}}. I tried this and it didn't work either.{noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { checkout([ $class: 'GitSCM', branches: [[name: '*/master']], gitTool: 'gitwin', userRemoteConfigs: [[ credentialsId: null, url: 'http://.git' ]] ]) echo "Compiling code" sleep 10} }}}}{noformat} Job log with error:{noformat}[Pipeline] nodeRunning on VMWASX in C:\workspace\msde-jenkinsfile-sample-windows[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutCloning the remote Git repositoryCloning repository http:// < internally-hosted-git-url>.git > /usr/bin/git init C:\workspace\msde-jenkinsfile-sample-windows # timeout=10ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Could not init C:\workspace\msde-jenkinsfile-sample-windows at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:787) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:579) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(Rem
[JIRA] (JENKINS-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master, we've configured two git tools to be used on our slaves on the \{{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs' config.xml - a job scheduled on a windows node correctly picked up the configured {{git tool}} {noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { echo "Compiling code" sleep 10} }}}}{noformat} For a Pipeline job with the Jenkinsfile (same Jenkinsfile as listed above) stored in SCM - a job scheduled on a windows node does not correctly picked pick up the {{git tool}} configured. Instead it default defaults to the first configured tool, which happens to be a linux path and hence fails on windows. The [following blog post|http://flatland-thoughts.blogspot.com/2017/05/multiple-git-tools-in-jenkins-scripted.html] documents this issue and suggests using the {{checkout}} pipeline step to override the {{gitTool}}. I tried this and it didn't work either.{noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { checkout([ $class: 'GitSCM', branches: [[name: '*/master']], gitTool: 'gitwin', userRemoteConfigs: [[ credentialsId: null, url: 'http://.git' ]] ]) echo "Compiling code" sleep 10} }}}}{noformat}Job log with error that highlights the slave trying to use the Default git tool rather than the overridden 'gitwin' tool configured in the Jenkinsfile{noformat}[Pipeline] nodeRunning on VMWASX in C:\workspace\msde-jenkinsfile-sample-windows[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutCloning the remote Git repositoryCloning repository http://.git > /usr/bin/git init C:\workspace\msde-jenkinsfile-sample-windows # timeout=10ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Could not init C:\workspace\msde-jenkinsfile-sample-windows at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:787) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:579) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHa
[JIRA] (JENKINS-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master, we've configured two git tools to be used on our slaves on the \{{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs' config.xml - a job scheduled on a windows node correctly picked up the configured {{git tool}} {noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { echo "Compiling code" sleep 10} }}}}{noformat} For a Pipeline job with the Jenkinsfile (same Jenkinsfile as listed above) stored in SCM - a job scheduled on a windows node does not correctly picked up the {{git tool}} configured. Instead it default to the first configured tool, which happens to be a linux path and hence fails on windows. The [following blog post|http://flatland-thoughts.blogspot.com/2017/05/multiple-git-tools-in-jenkins-scripted.html] documents this issue and suggests using the {{checkout}} pipeline step to override the {{gitTool}}. I tried this and it didn't work either.{noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { checkout([ $class: 'GitSCM', branches: [[name: '*/master']], gitTool: 'gitwin', userRemoteConfigs: [[ credentialsId: null, url: 'http://.git' ]] ]) echo "Compiling code" sleep 10} }}}}{noformat}Job log with error : that highlights the slave trying to use the Default git tool rather than the overridden 'gitwin' tool configured in the Jenkinsfile {noformat}[Pipeline] nodeRunning on VMWASX in C:\workspace\msde-jenkinsfile-sample-windows[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutCloning the remote Git repositoryCloning repository http://.git > /usr/bin/git init C:\workspace\msde-jenkinsfile-sample-windows # timeout=10ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Could not init C:\workspace\msde-jenkinsfile-sample-windows at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:787) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:579) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(Rem
[JIRA] (JENKINS-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master , runs on a linux host and we've configured two git tools to be used on our slaves on the \{{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs' config.xml - a job scheduled on a windows node correctly picked up the configured {{git tool}} {noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { echo "Compiling code" sleep 10} }}}}{noformat} For a Pipeline job with the Jenkinsfile (same Jenkinsfile as listed above) stored in SCM - a job scheduled on a windows node does not correctly pick up the {{git tool}} configured. Instead it defaults to the first configured tool, which happens to be a linux path and hence fails on windows. The [following blog post|http://flatland-thoughts.blogspot.com/2017/05/multiple-git-tools-in-jenkins-scripted.html] documents this issue and suggests using the {{checkout}} pipeline step to override the {{gitTool}}. I tried this and it didn't work either.{noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { checkout([ $class: 'GitSCM', branches: [[name: '*/master']], gitTool: 'gitwin', userRemoteConfigs: [[ credentialsId: null, url: 'http://.git' ]] ]) echo "Compiling code" sleep 10} }}}}{noformat}Job log with error that highlights the slave trying to use the Default git tool rather than the overridden 'gitwin' tool configured in the Jenkinsfile{noformat}[Pipeline] nodeRunning on VMWASX in C:\workspace\msde-jenkinsfile-sample-windows[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutCloning the remote Git repositoryCloning repository http://.git > /usr/bin/git init C:\workspace\msde-jenkinsfile-sample-windows # timeout=10ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Could not init C:\workspace\msde-jenkinsfile-sample-windows at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:787) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:579) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvoc
[JIRA] (JENKINS-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master runs on a linux host and we've configured two git tools to be used on our slaves on the \ {{http:///jenkins/webapp/configureTools/ }} page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs' config.xml - a job scheduled on a windows node correctly picked up the configured {{git tool}} {noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { echo "Compiling code" sleep 10} }}}}{noformat} For a Pipeline job with the Jenkinsfile (same Jenkinsfile as listed above) stored in SCM - a job scheduled on a windows node does not correctly pick up the {{git tool}} configured. Instead it defaults to the first configured tool, which happens to be a linux path and hence fails on windows. The [following blog post|http://flatland-thoughts.blogspot.com/2017/05/multiple-git-tools-in-jenkins-scripted.html] documents this issue and suggests using the {{checkout}} pipeline step to override the {{gitTool}}. I tried this and it didn't work either.{noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { checkout([ $class: 'GitSCM', branches: [[name: '*/master']], gitTool: 'gitwin', userRemoteConfigs: [[ credentialsId: null, url: 'http://.git' ]] ]) echo "Compiling code" sleep 10} }}}}{noformat}Job log with error that highlights the slave trying to use the Default git tool rather than the overridden 'gitwin' tool configured in the Jenkinsfile{noformat}[Pipeline] nodeRunning on VMWASX in C:\workspace\msde-jenkinsfile-sample-windows[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutCloning the remote Git repositoryCloning repository http://.git > /usr/bin/git init C:\workspace\msde-jenkinsfile-sample-windows # timeout=10ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Could not init C:\workspace\msde-jenkinsfile-sample-windows at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:787) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:579) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocat
[JIRA] (JENKINS-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title
Croydon Dias updated an issue
Jenkins / JENKINS-54334
git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Change By:
Croydon Dias
On our jenkins master runs on a linux host and we've configured two git tools to be used on our slaves on the { { noformat} http:///jenkins/webapp/configureTools/ {noformat } } page # Default - Linux git binary ## /usr/bin/git # gitwin - Windows git binary ## C:\Program Files\Git\bin\gitEvery Linux/Windows slaves in our infrastructure has git installed in the above location. On each slave configuration page, we don't override the 'Tools locations' and instead depend on inheriting the tools configured on the master.For a Pipeline job with the Jenkinsfile stored in the jobs' config.xml - a job scheduled on a windows node correctly picked up the configured {{git tool}} {noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { echo "Compiling code" sleep 10} }}}}{noformat} For a Pipeline job with the Jenkinsfile (same Jenkinsfile as listed above) stored in SCM - a job scheduled on a windows node does not correctly pick up the {{git tool}} configured. Instead it defaults to the first configured tool, which happens to be a linux path and hence fails on windows. The [following blog post|http://flatland-thoughts.blogspot.com/2017/05/multiple-git-tools-in-jenkins-scripted.html] documents this issue and suggests using the {{checkout}} pipeline step to override the {{gitTool}}. I tried this and it didn't work either.{noformat}pipeline {agent { label '(build) && win2k8' }tools { git "gitwin" }stages {stage('Compile') { stage('Windows') {steps { checkout([ $class: 'GitSCM', branches: [[name: '*/master']], gitTool: 'gitwin', userRemoteConfigs: [[ credentialsId: null, url: 'http://.git' ]] ]) echo "Compiling code" sleep 10} }}}}{noformat}Job log with error that highlights the slave trying to use the Default git tool rather than the overridden 'gitwin' tool configured in the Jenkinsfile{noformat}[Pipeline] nodeRunning on VMWASX in C:\workspace\msde-jenkinsfile-sample-windows[Pipeline] {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkoutCloning the remote Git repositoryCloning repository http://.git > /usr/bin/git init C:\workspace\msde-jenkinsfile-sample-windows # timeout=10ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Could not init C:\workspace\msde-jenkinsfile-sample-windows at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:787) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:579) at org.jenkinsci.plugins.gitclient.Remote
[JIRA] (JENKINS-54337) consider adding job-dsl to essentials
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-54337 consider adding job-dsl to essentials Issue Type: New Feature Assignee: R. Tyler Croy Components: evergreen Created: 2018-10-30 08:48 Priority: Minor Reporter: Dominik Bartholdi As evergreen already makes use of JCasC, I think the logical consequence would be to also add the job-dsl-plugin. I would even go further and think evergreen should provide an initial seed job out of the box - this job could then be adapted by evergreen users to setup there own stuff. Thinking about this: are there any concepts like evergreen setup extensions planned? Add Comment
[JIRA] (JENKINS-54041) EC2 Plugin no longer able to start build slaves
Title: Message Title David Goate commented on JENKINS-54041 Re: EC2 Plugin no longer able to start build slaves Is there any other enhanced log level/appender I could enable or settings I could export which might help with this. I found a way to get builds running (manually log into the EC2 console and start the slaves which are in the stopped state and then once they are running go into the jenkins nodes section and start the agent) When I manually start the agent, I do get a few warnings/errors, but ultimately it does attach and run and builds work. @@@ @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! >ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.lang.IllegalStateException: Already connected Agent successfully connected and online Oct 30, 2018 8:48:13 AM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1; see: https://jenkins.io/redirect/serialization-of-anonymous-classes/ 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
fisnik hajredini commented on JENKINS-54304
Re: Jobs in parallel dont display the variant they are running.
The following was generated using this groovy script:
Jenkins.instance.pluginManager.plugins.each{
plugin ->
println ("${plugin.getDisplayName()} (${plugin.getShortName()}): ${plugin.getVersion()}")
}
Durable Task Plugin (durable-task): 1.26 Pipeline: Nodes and Processes (workflow-durable-task-step): 2.25 Nexus Artifact Uploader (nexus-artifact-uploader): 2.10 GitHub Branch Source Plugin (github-branch-source): 2.4.1 Pipeline: SCM Step (workflow-scm-step): 2.7 Pipeline (workflow-aggregator): 2.6 Pipeline: API (workflow-api): 2.31 Pipeline: Declarative (pipeline-model-definition): 1.3.2 Pipeline: GitHub Groovy Libraries (pipeline-github-lib): 1.0 Ant Plugin (ant): 1.8 Apache HttpComponents Client 4.x API Plugin (apache-httpcomponents-client-4-api): 4.5.5-3.0 Workspace Cleanup Plugin (ws-cleanup): 0.36 Command Agent Launcher Plugin (command-launcher): 1.2 SSH Slaves plugin (ssh-slaves): 1.28.1 Windows Slaves Plugin (windows-slaves): 1.3.1 _javascript_ GUI Lib: Moment.js bundle plugin (momentjs): 1.1.1 Pipeline: Basic Steps (workflow-basic-steps): 2.12 Lockable Resources plugin (lockable-resources): 2.3 JDK Tool Plugin (jdk-tool): 1.1 Pipeline: REST API Plugin (pipeline-rest-api): 2.10 Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.12 Folders Plugin (cloudbees-folder): 6.6 JSch dependency plugin (jsch): 0.1.54.2 Build Timeout (build-timeout): 1.19 Job Configuration History Plugin (jobConfigHistory): 2.18.3 Credentials Binding Plugin (credentials-binding): 1.16 PAM Authentication plugin (pam-auth): 1.4 Token Macro Plugin (token-macro): 2.5 Matrix Authorization Strategy Plugin (matrix-auth): 2.3 Docker Commons Plugin (docker-commons): 1.13 Pipeline: Milestone Step (pipeline-milestone-step): 1.3.1 LDAP Plugin (ldap): 1.20 Green Balls (greenballs): 1.15 External Monitor Job Type Plugin (external-monitor-job): 1.7 Copy Artifact Plugin (copyartifact): 1.41 Resource Disposer Plugin (resource-disposer): 0.12 Pipeline: Build Step (pipeline-build-step): 2.7 _javascript_ GUI Lib: Handlebars bundle plugin (handlebars): 1.1.1 Pipeline: Supporting APIs (workflow-support): 2.21 Gradle Plugin (gradle): 1.29 Pipeline: Job (workflow-job): 2.26 Structs Plugin (structs): 1.17 Pipeline: Groovy (workflow-cps): 2.60 Matrix Project Plugin (matrix-project): 1.13 Simple Theme Plugin (simple-theme-plugin): 0.5.1 GitHub Authentication plugin (github-oauth): 0.29 Branch API Plugin (branch-api): 2.0.20 GitHub API Plugin (github-api): 1.92 Pipeline: Stage View Plugin (pipeline-stage-view): 2.10 OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.5 Pipeline: Stage Tags Metadata (pipeline-stage-tags-metadata): 1.3.2 bouncycastle API Plugin (bouncycastle-api): 2.17 Jackson 2 API Plugin (jackson2-api): 2.8.11.3 Email Extension Plugin (email-ext): 2.63 _javascript_ GUI Lib: ACE Editor bundle plugin (ace-editor): 1.1 Docker Pipeline (docker-workflow): 1.17 GitHub plugin (github): 1.29.3 Pipeline: Multibranch (workflow-multibranch): 2.20 JUnit Plugin (junit): 1.26.1 SSH Credentials Plugin (ssh-credentials): 1.14 Node and Label parameter plugin (nodelabelparameter): 1.7.2 Credentials Plugin (credentials): 2.1.18 Nexus Platform Plugin (nexus-jenkins-plugin): 3.3.20181025-134249.614c5f4 Authentication Tokens A
[JIRA] (JENKINS-52828) Add slave suffix command
Title: Message Title Oliver Pereira commented on JENKINS-52828 Re: Add slave suffix command What does this change do exactly and how do we use it? 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-54338) Затирается значение в поле ввода
Title: Message Title Nataly S created an issue Jenkins / JENKINS-54338 Затирается значение в поле ввода Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2018-10-30 09:14 Priority: Minor Reporter: Nataly S Добрый день! Баг заключается в следующем: * размещаю в шаге pipeline несколько полей ввода затем заполняю одно из них при переходе к другому полю значение первого затирается. Add Comment
[JIRA] (JENKINS-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-54334 git-plugin ignores 'gitTool' when multiple git tools are configured on the master 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-54334) git-plugin ignores 'gitTool' when multiple git tools are configured on the master
Title: Message Title Mark Waite commented on JENKINS-54334 Re: git-plugin ignores 'gitTool' when multiple git tools are configured on the master A possible work around may be to create a git tool that relies on the system provided path. For example, I have a git tool whose path is `git` (no directory components, just 'git`). Then the Windows machines can have their PATH set to include `C:\Program Files\Git\bin` in the PATH. 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-44141) Define a resource pool
Title: Message Title Benjamin Schuler commented on JENKINS-44141 Re: Define a resource pool Supporting Xaviers statement regarding the "farm" of testing resources! We are currently struggling with a similar situation where multiple resources are available for multiple jobs, each job would request for an available resource and lock it until it is finished, but we cannot specify which resource the job should pick. 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-54339) Jenkins Configuration Page Loading Forever
Title: Message Title Sam Tang created an issue Jenkins / JENKINS-54339 Jenkins Configuration Page Loading Forever Issue Type: Bug Assignee: Sam Tang Attachments: a2.png Components: _unsorted Created: 2018-10-30 09:56 Environment: Jenkins ver. 2.138.23 Windows service used Priority: Critical Reporter: Sam Tang Jenkins configuration page loading forever this happens to (Manage Jenkins -> Configure System / Configure Global Security). As enclosed, Chrome console shows error. I have tried to remove/disable ALL plugins and restart, but the problem is still here. What else could I do/try? Apart from reinstallation... Add Comment
[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly
Title: Message Title Niels Alebregtse commented on JENKINS-52593 Re: Support EKS authentication, or specifying a kubeconfig directly I just wanted to give a heads-up here that the kubernetes-client library has been updated to use the aws-iam-authenticator configuration from the kubeconfig file (see [here|https://github.com/fabric8io/kubernetes-client/pull/1224|https://github.com/fabric8io/kubernetes-client/pull/1224]).] ). So the easiest fix now would be to upgrade to a more recent version of the kubernetes-client (e.g. version 4.1.0). 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-54340) CWP throws error if pom.xml is used for plugins and casc for configuration
Title: Message Title Michael Werner created an issue Jenkins / JENKINS-54340 CWP throws error if pom.xml is used for plugins and casc for configuration Issue Type: Bug Assignee: Oleg Nenashev Components: custom-war-packager Created: 2018-10-30 10:13 Priority: Minor Reporter: Michael Werner % make clean build run rm -rf tmp java \ -jar ../../custom-war-packager-cli/target/custom-war-packager-cli-1.4-SNAPSHOT-jar-with-dependencies.jar \ -configPath packager-config.yml -version 256.0-test Picked up _JAVA_OPTIONS: -Dhttp.proxyHost=proxy.mms-dresden.de -Dhttp.proxyPort=8080 -Dhttps.proxyHost=proxy.mms-dresden.de -Dhttps.proxyPort=8080 Exception in thread "main" java.io.IOException: CasC section is declared, but CasC plugin is not declared in the plugins list at io.jenkins.tools.warpackager.lib.impl.Builder.verifyConfig(Builder.java:66) at io.jenkins.tools.warpackager.lib.impl.Builder.build(Builder.java:73) at io.jenkins.tools.warpackager.cli.Main.main(Main.java:56) make: *** [Makefile:15: tmp/output/target/jenkins-casc-demo-256.0-test.war] Error 1 I used the the effective pom from the jcasc plugin. my test code can be found here https://github.com/Xaseron/custom-war-packager/tree/bugreport/demo/casc
[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly
Title: Message Title Niels Alebregtse edited a comment on JENKINS-52593 Re: Support EKS authentication, or specifying a kubeconfig directly I just wanted to give a heads-up here that the kubernetes-client library has been updated to use the aws-iam-authenticator configuration from the kubeconfig file (see [here| [ https://github.com/fabric8io/kubernetes-client/pull/1224] |https://github.com/fabric8io/kubernetes-client/pull/1224] ).] ). So the easiest fix now would be to upgrade to a more recent version of the kubernetes-client (e.g. version 4.1.0). 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-52593) Support EKS authentication, or specifying a kubeconfig directly
Title: Message Title Niels Alebregtse edited a comment on JENKINS-52593 Re: Support EKS authentication, or specifying a kubeconfig directly I just wanted to give a heads-up here that the kubernetes-client library has been updated to use the aws-iam-authenticator configuration from the kubeconfig file (see [here|https://github.com/fabric8io/kubernetes-client/pull/1224]). ] ). So the easiest fix now would be to upgrade to a more recent version of the kubernetes-client (e.g. version 4.1.0). 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-53888) Batch step running on a node other than the master fails
Title: Message Title Florian Ramillien commented on JENKINS-53888 Re: Batch step running on a node other than the master fails About worklow-api (Pipeline API plugin) I was still in 2.30 when this problem occured. For now, I can plan to upgrade to last plugins version and re-enable watch mode next week. About "special conditions triggering it", in my case it's huge logs files (example in this report was working perfectly). See : https://issues.jenkins-ci.org/browse/JENKINS-54081?focusedCommentId=352021&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-352021 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-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
Title: Message Title
Marcus Philip commented on JENKINS-54305
Re: Oracle JDK 10 not available anymore - Oracle JDK 11 is not free
I am quite OK with this not getting fixed. The main problem is really the confusion ('java.sun.com' in Installer name, no Java 11 appearing, Java 10 install failing, ...), not that there is no download installer available OOTB. It's simple to install the tool in another way.
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-54241) Log parser not displaying full log
Title: Message Title Martin Stolle commented on JENKINS-54241 Re: Log parser not displaying full log External log storage for Pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54341) Ansible Tower Plugin 0.9.0 not compatible with Tower 3.2.5
Title: Message Title
Rainer Montag created an issue
Jenkins / JENKINS-54341
Ansible Tower Plugin 0.9.0 not compatible with Tower 3.2.5
Issue Type:
Bug
Assignee:
John Westcott
Components:
ansible-tower-plugin
Created:
2018-10-30 10:47
Priority:
Major
Reporter:
Rainer Montag
Jenkins: 2.121.3 Ansible-Tower-Plugin: 0.9.0 Ansible Tower: 3.2.5 When configuring a Ansible Tower 3.2.5 connectivity with plugin version 0.9.0 it does not work (anymore?) Plugin is issuing a POST "/api/v2/authtoken/" and retrieving a token: {"token":"2878104c539b9dd3526cd07280f596441d7b9e02","expires":"2018-10-30T09:56:23.351Z"} Then Plugin is sending a GET Request "/api/v2/jobs/", but is sending the Header "Authorization: Bearer 2878104c539b9dd3526cd07280f596441d7b9e02" which will result in a 401 error {"detail":"Authentication credentials were not provided."}. Problem is the "Bearer" value in the Header (introduced with OAuth support for Tower 3.3 ?). The correct request needs to send the Header as "Authorization: Token 2878104c539b9dd3526cd07280f596441d7b9e02", then the command is working (from curl). As a result, the plugin 0.9.0 is not working with Ansible Tower 3.2.5. I have currently no possibility to upgrade Ansible Tower to >= 3.3.
Ad
[JIRA] (JENKINS-53402) Connection to ALM Octane server failed
Title: Message Title Adnane SAGHIR updated an issue Jenkins / JENKINS-53402 Connection to ALM Octane server failed Change By: Adnane SAGHIR Attachment: nga.log 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-53402) Connection to ALM Octane server failed
Title: Message Title Adnane SAGHIR updated an issue Jenkins / JENKINS-53402 Connection to ALM Octane server failed Change By: Adnane SAGHIR Attachment: all.log 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-53402) Connection to ALM Octane server failed
Title: Message Title Adnane SAGHIR commented on JENKINS-53402 Re: Connection to ALM Octane server failed Hi, it seems everything is fine in terms of networking. I also installed all the necessary certificates of my organisation. But I still get the error. Please look at the attached logs Thanks & regards all.log nga.log 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-53402) Connection to ALM Octane server failed
Title: Message Title Adnane SAGHIR updated JENKINS-53402 Jenkins / JENKINS-53402 Connection to ALM Octane server failed Change By: Adnane SAGHIR Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-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
If its writing the env variables thats causing the problem, can we try doing something like this?
private void setupEnvironmentVariable(EnvVars vars, ExecWatch watch) throws IOException {
StringBuilder envVars = new StringBuilder();
for (Map.Entry entry : vars.entrySet()) {
//Check that key is bash compliant.
if (entry.getKey().matches("[a-zA-Z_][a-zA-Z0-9_]*")) {
envVars.append(String.format(
"export %s='%s'%s",
entry.getKey(),
entry.getValue().replace("'", "'\\''"),
NEWLINE
));
}
}
watch.getInput().write(envVars.toString()).getBytes(StandardCharsets.UTF_8);
}
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-50429) Shell command are really slower than before
Title: Message Title
Joseph Green edited a comment on JENKINS-50429
Re: Shell command are really slower than before
If its writing the env variables thats causing the problem, can we try doing something like this?{code:java}private void setupEnvironmentVariable(EnvVars vars, ExecWatch watch) throws IOException { StringBuilder envVars = new StringBuilder(); for (Map.Entry entry : vars.entrySet()) {//Check that key is bash compliant.if (entry.getKey().matches("[a-zA-Z_][a-zA-Z0-9_]*")) { envVars.append(String.format( "export %s='%s'%s", entry.getKey(), entry.getValue().replace("'", "'\\''"), NEWLINE ));} } watch.getInput().write(envVars.toString()).getBytes(StandardCharsets.UTF_8);}{code}
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-54041) EC2 Plugin no longer able to start build slaves
Title: Message Title
David Goate edited a comment on JENKINS-54041
Re: EC2 Plugin no longer able to start build slaves
On latest version (1.41) I still get the warning: {code:java}WARNING: Failed to load org.jenkinsci.plugins.github.pullrequest.extra.GitHubPRLabelUnblockQueueCondition$DescriptorImpljava.lang.NoClassDefFoundError: org/jenkinsci/plugins/blockqueuedjob/condition/BlockQueueCondition$BlockQueueConditionDescriptor{code} Reverting back to 1.39 now also gives: {code:java}Connecting to 10.1.1.90 on port 22, with timeout 1.Oct 29, 2018 11:19:39 AM WARNING org.jvnet.hudson.annotation_indexer.Index$2$1 fetchFailed to load org.jenkinsci.plugins.github.pullrequest.extra.GitHubPRLabelUnblockQueueCondition$DescriptorImpljava.lang.ClassNotFoundException: org.jenkinsci.plugins.blockqueuedjob.condition.BlockQueueCondition$BlockQueueConditionDescriptor at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1374) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1327) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1080) at java.lang.ClassLoader.loadClass(ClassLoader.java:357){code} Currently none of So my Jenkins builds will run previous "fix" for this (downgrading) no longer fixes the problem . Do you I think this is related after upgrading to this 1.41 some configuration files might have changed as the plugin or manager in Jenkins displayed a different issue red warning saying that it might not be possible to downgrade . Currently none of my Jenkins builds will run automatically.
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-50429) Shell command are really slower than before
Title: Message Title
Joseph Green edited a comment on JENKINS-50429
Re: Shell command are really slower than before
If its writing the env variables thats causing the problem, can we try doing something like this?{code:java}private void setupEnvironmentVariable(EnvVars vars, ExecWatch watch) throws IOException { StringBuilder envVars = new StringBuilder(); for (Map.Entry entry : vars.entrySet()) {//Check that key is bash compliant.if (entry.getKey().matches("[a-zA-Z_][a-zA-Z0-9_]*")) { envVars.append(String.format( "export %s='%s'%s", entry.getKey(), entry.getValue().replace("'", "'\\''"), NEWLINE ));} } watch.getInput().write(envVars.toString()) .getBytes(StandardCharsets.UTF_8) ;}{code}
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-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 Additionally, this post (also mentioned earlier in this thread) https://stackoverflow.com/questions/28617175/did-i-find-a-bug-in-java-io-pipedinputstream seems to suggest that `OutputStream.write()` can hang for up to a second and that calling `OutputStream.flush()` can help with this 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-53575) Configuration-as-Code compatibility
Title: Message Title Nicolas De Loof commented on JENKINS-53575 Re: Configuration-as-Code compatibility The issue is due to JCasC export feature design : as we only want to export things that differ from default values, we create a fresh new `GradleInstallation$DescriptorImpl` instance and compare properties. But gradle plugin did manage the transition from `Gradle.DescriptorImpl` to `ToolDescriptor` relying on an `@Inject` delegate, which I think is a nice, concise and clean way to handle this. When JCasC do create a new instance it doesn't inject dependencies and the delegate call results in a NPE. I'm not sure the best way to handle this. I like the @Inject-based delegate approach, compared to other implementations which do a systematic lookup to legacy Descriptor. On the other hand the root issue maybe is that those approach don't migrate data, they just pretend they implement the new API but tried to avoid having to manage data migration. Maybe a correct way to handle this is for `Gradle.DescriptorImpl` (and other) to populate `GradleInstallation$DescriptorImpl#installations` when some legacy data get loaded, and fully follow the intended `ToolDescriptor` design to host `installations` property. 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-54342) Jenkinsfile Runner productization
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-54342 Jenkinsfile Runner productization Change By: Oleg Nenashev Assignee: Nicolas De Loof Oleg Nenashev 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-54342) Jenkinsfile Runner productization
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54342 Jenkinsfile Runner productization Issue Type: Epic Assignee: Nicolas De Loof Components: jenkinsfile-runner Created: 2018-10-30 11:20 Priority: Minor Reporter: Oleg Nenashev Just a placeholder EPIC for Jenkinsfile Runner productization tasks Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54343) Create Jenkinsfile for Jenkinsfile Runner
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-54343 Create Jenkinsfile for Jenkinsfile Runner Issue Type: Task Assignee: Nicolas De Loof Components: jenkinsfile-runner Created: 2018-10-30 11:21 Priority: Minor Reporter: Oleg Nenashev 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-54343) Create Jenkinsfile for Jenkinsfile Runner
Title: Message Title Oleg Nenashev started work on JENKINS-54343 Change By: Oleg Nenashev 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-54343) Create Jenkinsfile for Jenkinsfile Runner
Title: Message Title Oleg Nenashev commented on JENKINS-54343 Re: Create Jenkinsfile for Jenkinsfile Runner https://github.com/jenkinsci/jenkinsfile-runner/pull/31 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-54343) Create Jenkinsfile for Jenkinsfile Runner
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-54343 Create Jenkinsfile for Jenkinsfile Runner Change By: Oleg Nenashev Assignee: Nicolas De Loof Oleg Nenashev 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-50429) Shell command are really slower than before
Title: Message Title
Joseph Green edited a comment on JENKINS-50429
Re: Shell command are really slower than before
If its writing the env variables thats causing the problem, can we try doing something like this?{code:java}private void setupEnvironmentVariable(EnvVars vars, ExecWatch watch) throws IOException { StringBuilder envVars = new StringBuilder(); for (Map.Entry entry : vars.entrySet()) {//Check that key is bash compliant.if (entry.getKey().matches("[a-zA-Z_][a-zA-Z0-9_]*")) { envVars.append(String.format( "export %s='%s'%s", entry.getKey(), entry.getValue().replace("'", "'\\''"), NEWLINE ));} } watch.getInput().write(envVars.toString());}{code} I've created a PR with an initial attempt at this. We need to address any failing tests as a result of this change. https://github.com/jenkinsci/kubernetes-plugin/pull/390
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-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-46715 Error steps may change to show up as errors in pipeline view Change By: Reinhold Füreder Attachment: image-2018-10-30-12-30-10-803.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-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title Reinhold Füreder updated an issue Jenkins / JENKINS-46715 Error steps may change to show up as errors in pipeline view Change By: Reinhold Füreder Attachment: image-2018-10-30-12-32-53-068.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-45635) Jenkins slave provisioned by Kubernetes plugin missing file in /home/jenkins
Title: Message Title seenimurugan shanmugam commented on JENKINS-45635 Re: Jenkins slave provisioned by Kubernetes plugin missing file in /home/jenkins Davis Tran Could you please share your work around? i want to add the private and public keys to /home/jenkins/.ssh folder. 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-46715) Error steps may change to show up as errors in pipeline view
Title: Message Title
Reinhold Füreder commented on JENKINS-46715
Re: Error steps may change to show up as errors in pipeline view
Thorsten Scherler First of all thanks a lot in advance for taking care of this mysterious and disturbing problem The classic UI shows the error as expected:
Of course the build itself is red (but this is also the case in BO)
The console log contains the error step output at the very end:
...
> Task :migrateDb FAILEDFAILURE: Build failed with an exception.* What went wrong:
Execution failed for task ':migrateDb'.
> Process 'command 'php'' finished with non-zero exit value 1* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.* Get more help at https://help.gradle.orgBUILD FAILED in 14s
2 actionable tasks: 1 executed, 1 up-to-date
[Pipeline] echo
[DEBUG] gradlew phpunit exit code: 1
[Pipeline] pwd
[Pipeline] error
[Pipeline] }
$ docker stop --time=1 2d13f6eb6583a72e93035a276888210f140b200ab6e7533144bf017ad1f13965
$ docker rm -f 2d13f6eb6583a72e93035a276888210f140b200ab6e7533144bf017ad1f13965
[Pipeline] // withDockerContainer
[Pipeline] }
[Pipeline] // withDockerRegistry
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] sh
[ACME-Pipeline-WS] Running shell script
+ docker stop d94a0bd920c35a4e98559980b9409c0ecc8d3db2d062ce7b6de07f350d1dcd0b
d94a0bd920c35a4e98559980b9409c0ecc8d3db2d062ce7b6de07f350d1dcd0b
+ docker rm -f d94a0bd920c35a4e98559980b9409c0ecc8d3db2d062ce7b6de07f350d1dcd0b
d94a0bd920c35a4e98559980b9409c0ecc8d3db2d062ce7b6de07f350d1dcd0b
[Pipeline] }
[Pipeline] // withDockerRegistry
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // ws
[Pipeline] }
[Pipeline] // node
[Pipeline] }
[Pipeline] // stage
[Pipeline] ansiColor
[Pipeline] {
[Pipeline] echo
Pipeline problem: PHPUnit DB integration test execution failed completely due to: "hudson.AbortException: PHPUnit DB integration test execution failed completely: Please check the previous step(s)" => Please check the "Console/Log Output" => Failure notification will be sent...
[Pipeline] }
[Pipeline] // ansiColor
[Pipeline] emailextrecipients
[Pipeline] emailextrecipients
[Pipeline] emailextrecipients
[Pipeline] emailextrecipients
[Pipeline] emailextrecipients
[Pipeline] emailextrecipients
[Pipeline] echo
email-ext-recipients:
failingTestSuspects:
failingBuildSuspects:
developers: a.n...@acme.com
culprits: a.n...@acme.com
requester:
upstreamCommitters:
[Pipeline] emailext
Single culprit: [A Name]
Sending email to: a.n...@acme.com jenkins.ci...@acme.com
[Pipeline] stage
[Pipeline] { (kpi)
[Pipeline] echo
Listing all KPIs...
[Pipeline] echo[Pipeline] node
Running on Jenkins in /var/lib/jenkins/workspace/ACME-Pipeline
[Pipeline] {
[Pipeline] ws
Running in /var/lib/jenkins/workspace/ACME-Pipeline-WS-kpi
[Pipeline] {
[Pipeline] echo
Build Pipeline KPIs:
- Build duration: 2 minutes, 49.844 seconds ... time duration since build start
- Time duration since build scheduling: 2 minutes, 49.857 seconds
- Pipeline net execution time duration: 2 minutes, 42.368 seconds ... in "acme.build"
- Cycle time: 2 minutes, 50.570 seconds ... time duration since (oldest included production code) SVN commit (170953)
[Pi
[JIRA] (JENKINS-44141) Define a resource pool
Title: Message Title Benjamin Heilbrunn commented on JENKINS-44141 Re: Define a resource pool +1 for a pool of resources from where I can draw instances that the are then locked until explicitly released by the build 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-44141) Define a resource pool
Title: Message Title Benjamin Heilbrunn edited a comment on JENKINS-44141 Re: Define a resource pool +1 for a pool of resources from where I can draw (random) resource instances that the are then locked until explicitly released by the build 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-54344) Add an AdministrativeMonitor to check/warn critical aspects of an Evergreen instance
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-54344 Add an AdministrativeMonitor to check/warn critical aspects of an Evergreen instance Issue Type: New Feature Assignee: R. Tyler Croy Components: evergreen, evergreen-plugin Created: 2018-10-30 11:59 Labels: evergreen Priority: Minor Reporter: Baptiste Mathus Problem statement If something goes very wrong on an Evergreen instance, it's currently hard to surface it to the user. E.g. no update manifest unable to connect to the backend ... Proposal Using an AdministrativeMonitor, we could setup a serie of tests to check things look fine, and if not surface it to the user. Idea from Adrien Lecharpentier I thought I'd file here to remember. Add Comment
[JIRA] (JENKINS-54344) Add an AdministrativeMonitor to check/warn critical aspects of an Evergreen instance
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-54344 Add an AdministrativeMonitor to check/warn critical aspects of an Evergreen instance Change By: Baptiste Mathus Assignee: R. Tyler Croy 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-50429) Shell command are really slower than before
Title: Message Title Carlos Sanchez commented on JENKINS-50429 Re: Shell command are really slower than before check above comments, writing one string or multiple ones takes the same amount of time 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-54345) Job-DSL RTC Build Definition
Title: Message Title Victor Martinez moved an issue Jenkins / JENKINS-54345 Job-DSL RTC Build Definition Change By: Victor Martinez Project: Jenkins Website Key: WEBSITE JENKINS - 526 54345 Workflow: WEBSITE: Software Development Workflow JNJira + In-Review Status: To Do Open Component/s: job-dsl-plugin Component/s: plugin-site 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
[JIRA] (JENKINS-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54304 Jobs in parallel dont display the variant they are running. Change By: Jesse Glick Component/s: workflow-job-plugin Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-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. This is as designed. The HTML rendering layer was rewritten. You can click on (hide) links to suppress irrelevant branches or other blocks. There is a TODO comment requesting that in the case of parallel, all but the first branch be hidden by default. Or, a similar kind of branch prefix could be displayed in JS/CSS without requiring the physical log to have that prefix, as it did before. 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-54241) Log parser not displaying full log
Title: Message Title Martin Stolle assigned an issue to jborghi Jenkins / JENKINS-54241 Log parser not displaying full log Change By: Martin Stolle Assignee: Manuel Recena Soto jborghi 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-54241) Log parser not displaying full log
Title: Message Title Martin Stolle commented on JENKINS-54241 Re: Log parser not displaying full log According to https://plugins.jenkins.io/log-parser John ist the maintainer, therefore I added him as assignee Please let me know if this plugin is still maintained or up for adoption 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-54241) Log parser not displaying full log
Title: Message Title Martin Stolle edited a comment on JENKINS-54241 Re: Log parser not displaying full log According to https://plugins.jenkins.io/log-parser John ist is the maintainer, therefore I added him as assigneePlease let me know if this plugin is still maintained or up for adoption 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-53888) Batch step running on a node other than the master fails
Title: Message Title Jesse Glick commented on JENKINS-53888 Re: Batch step running on a node other than the master fails Florian Ramillien in my case it's huge logs files Then you may rather have hit a symptom of JENKINS-54073, whereas other reporters (Bhushan Shah, Éric Louvard, mishal shah, but again excluding the false initial report by Yoav Miles) seem to have hit something very different. 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-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Jesse Glick commented on JENKINS-2111 Re: removing a job (including multibranch/org folder branches/repos) does not remove the workspace I still have a @script folder on my Jenkins master. Is that the responsibility of another component to delete? Yes, this is created by Pipeline builds under certain SCM configurations (“heavyweight checkouts”), and is not covered by the workspace infrastructure. Probably those should be cleaned up, too, but it would be a separate patch. 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-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title
Rolando-Mihai Vlad edited a comment on JENKINS-49033
Re: Issue with HPE Application Automation Tools plugin
Hello Edwin,Sorry for the delay. You might have some registry issues. Please register the LrWsNetClient.dll using the following commands:{color:#57d9a3}> cd \bin{color}{color:#57d9a3}> C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe LrWsNetClient.dll /regfile:LrWsNetClient.reg /codebase{color} Regards,Rolando
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-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title Rolando-Mihai Vlad commented on JENKINS-49033 Re: Issue with HPE Application Automation Tools plugin Hello Edwin, Sorry for the delay. You might have some registry issues. Please register the LrWsNetClient.dll using the following commands: > cd \bin > C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe LrWsNetClient.dll /regfile:LrWsNetClient.reg /codebase Regards, Rolando 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-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title
Rolando-Mihai Vlad edited a comment on JENKINS-49033
Re: Issue with HPE Application Automation Tools plugin
Hello Edwin,Sorry for the delay. You might have some registry issues. Please register the LrWsNetClient.dll using the following commands:{color:# 57d9a3 505f79 }> cd \bin{color}{color:# 57d9a3 505f79 }> C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe LrWsNetClient.dll /regfile:LrWsNetClient.reg /codebase{color} Regards,Rolando
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-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Nick Jones commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults I had rolled back to 2.58 to avoid the issue tracked here, but now see a 2.60 release fixing a security issue. I'd rather not upgrade and start getting these errors again but also am loath to ignore a security fix. Could someone give me some guidance as to whether the problem reported here is fixable? AFAIK the only actual impact of this bug is large stack traces in the logs – not actual functional problems – but I'd rather avoid excessive log noise if I can. 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-54262) Groovy Postbuild requires Overall/Administer permission
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54262 Groovy Postbuild requires Overall/Administer permission Change By: Jesse Glick Labels: permissions 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-54262) Groovy Postbuild requires Overall/Administer permission
Title: Message Title Jesse Glick commented on JENKINS-54262 Re: Groovy Postbuild requires Overall/Administer permission CC Wadeck Follonier + Daniel Beck 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-54314) LR 5.6 jenkins features break backwards compatibility
Title: Message Title Rolando-Mihai Vlad resolved as Fixed Jenkins / JENKINS-54314 LR 5.6 jenkins features break backwards compatibility Change By: Rolando-Mihai Vlad 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-54337) consider adding job-dsl to Evergreen
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54337 consider adding job-dsl to Evergreen Change By: Baptiste Mathus Summary: consider adding job-dsl to essentials Evergreen 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-54336) consider adding pipeline-utility-steps-plugin to Evergreen
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54336 consider adding pipeline-utility-steps-plugin to Evergreen Change By: Baptiste Mathus Summary: consider adding pipeline-utility-steps-plugin to essentials Evergreen 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-54336) consider adding pipeline-utility-steps-plugin to Evergreen
Title: Message Title Baptiste Mathus assigned an issue to Baptiste Mathus Jenkins / JENKINS-54336 consider adding pipeline-utility-steps-plugin to Evergreen Change By: Baptiste Mathus Assignee: R. Tyler Croy Baptiste Mathus 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-54317) change NAT timeout
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-54317 change NAT timeout Change By: Baptiste Mathus Assignee: R. Tyler Croy 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-54336) consider adding pipeline-utility-steps-plugin to Evergreen
Title: Message Title Baptiste Mathus started work on JENKINS-54336 Change By: Baptiste Mathus 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-54336) consider adding pipeline-utility-steps-plugin to Evergreen
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-54336 consider adding pipeline-utility-steps-plugin to Evergreen Change By: Baptiste Mathus Sprint: Evergreen - Milestone 2 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-54337) consider adding job-dsl to Evergreen
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-54337 consider adding job-dsl to Evergreen Change By: Baptiste Mathus Assignee: R. Tyler Croy 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-54288) Create GSoC project proposal documents
Title: Message Title Martin d'Anjou started work on JENKINS-54288 Change By: Martin d'Anjou 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-54337) consider adding job-dsl to Evergreen
Title: Message Title Baptiste Mathus commented on JENKINS-54337 Re: consider adding job-dsl to Evergreen I definitely agree with that one, and I was not later than yesterday thinking about using Job DSL to seed and version my instance. AFAIK, CasC does not provide handling for jobs (and was even using job-dsl for it too some time ago). IIRC, though, there are a few challenges with security using Job DSL. I need to understand them better before potentially acting here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
