[JIRA] (JENKINS-49497) Proxy not set when doing lightweight checkout
Title: Message Title David Stein created an issue Jenkins / JENKINS-49497 Proxy not set when doing lightweight checkout Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2018-02-12 07:41 Environment: git-client-plugin 2.7.1, jenkins 2.89.3 Priority: Minor Reporter: David Stein I've setup a pipeline project that pulls pipeline script from SCM, and by default "Lightweight checkout" is checked. This causes an error saying that: hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/master:refs/remotes/origin/master --prune" returned status code 128: stdout: stderr: fatal: unable to access 'https://github.com/owner/repo.git/': Failed connect to github.com:443; Connection refused at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1715) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:351) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:196) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:172) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:107) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67) at
[JIRA] (JENKINS-49463) jenkins needs a DRY mode which disables schedulers
Title: Message Title Oleg Nenashev commented on JENKINS-49463 Re: jenkins needs a DRY mode which disables schedulers DRY issue is a bit wider, because somebody will need to disable all dependency/polling triggering in plugins (e.g. in Maven projects). It is a valiant goal, but also a pretty big chunk of work. Sorin Sbarnea do you plan to work on this task in short-term? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49496) Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard
Title: Message Title Jan Vansteenkiste updated an issue Jenkins / JENKINS-49496 Dutch translation of 'allow users to sign-up' is wrong and creates a security hazard Change By: Jan Vansteenkiste Summary: Dutch translation of 'allow users to sign-up' is wrong and creates a securit security hazard Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49496) Dutch translation of 'allow users to sign-up' is wrong and creates a securit hazard
Title: Message Title Jan Vansteenkiste created an issue Jenkins / JENKINS-49496 Dutch translation of 'allow users to sign-up' is wrong and creates a securit hazard Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-02-12 07:33 Labels: security Priority: Critical Reporter: Jan Vansteenkiste The dutch translation of 'Allow a user to sign up' translates back to 'allow a user to sign in'. The current translation is confusing and dangerous to jenkins administrators since it will open up your jenkins to allow random users to register themselves. Add Comment
[JIRA] (JENKINS-49469) Nodejs plugin should be able to access npmrc files configured inside folders
Title: Message Title Dominik Bartholdi assigned an issue to Nikolas Falco Jenkins / JENKINS-49469 Nodejs plugin should be able to access npmrc files configured inside folders Change By: Dominik Bartholdi Component/s: cloudbees-folder-plugin Component/s: config-file-provider-plugin Assignee: Dominik Bartholdi Nikolas Falco Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48945) wrong testreport, if testnames produce a hashcollision (because of temp. generated junit-files)
Title: Message Title Sascha Friederich assigned an issue to Gregory Boissinot Jenkins / JENKINS-48945 wrong testreport, if testnames produce a hashcollision (because of temp. generated junit-files) Change By: Sascha Friederich Assignee: Andrew Bayer Gregory Boissinot Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49234) TFS polling exception
Title: Message Title Alexey Larsky closed an issue as Fixed After blacklisted last and issued version of JIRA plugin all works. Jenkins / JENKINS-49234 TFS polling exception Change By: Alexey Larsky Status: Open Closed Assignee: redsolo Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-49234) TFS polling exception
Title: Message Title Alexey Larsky updated an issue Jenkins / JENKINS-49234 TFS polling exception Change By: Alexey Larsky Component/s: tfs-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34262) Support for OAuth credentials
Title: Message Title Weynham Zheng commented on JENKINS-34262 Re: Support for OAuth credentials Same here, after enabled two factors auth, tried app passwords, won't work either. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs
Title: Message Title bharath ganesh kumar balasubrmanian commented on JENKINS-26138 Re: Support workspaces for Pipeline jobs For all those who're particular to look the workspace of multi branch pipeline jenkins projects, please navigate to the build run and click “pipeline steps”, then click “allocate node: start” ( for multiple nodes, this shall be done as required) Tadaaa..!!! you've your workspace button in the left Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34403) docker build fails if Dockerfile pip-installs simplejson
Title: Message Title Jon Hermansen edited a comment on JENKINS-34403 Re: docker build fails if Dockerfile pip-installs simplejson I wrote a functional test for this fix. I'm hoping to see the above PR merged in as well. [https://github.com/jenkinsci/docker-custom-build-environment-plugin/pull/69]By the way, docker build supports a flag called --iidfile, which will write the built image ID to a separate file. [ https://docs.docker.com/engine/reference/commandline/build/#options ] Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34403) docker build fails if Dockerfile pip-installs simplejson
Title: Message Title Jon Hermansen commented on JENKINS-34403 Re: docker build fails if Dockerfile pip-installs simplejson I wrote a functional test for this fix. I'm hoping to see the above PR merged in as well. https://github.com/jenkinsci/docker-custom-build-environment-plugin/pull/69 By the way, docker build supports a flag called --iidfile, which will write the image ID to a separate file. https://docs.docker.com/engine/reference/commandline/build/#options Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45998) Build failed when docker can't remove docker image
Title: Message Title Jon Hermansen commented on JENKINS-45998 Re: Build failed when docker can't remove docker image I believe this is fixed: https://github.com/jenkinsci/docker-custom-build-environment-plugin/pull/63 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43244) slackSend does not work with jenkins pipelines
Title: Message Title daniel zhang edited a comment on JENKINS-43244 Re: slackSend does not work with jenkins pipelines Hi [~nickolasfox], It seems that slackSend need a fixed format. Just as below:slackSend channel: SLACK_CHANNEL, color: SLACK_Color, message: SLACK_MESSAFE, teamDomain: SLACK_TEAM_DOMAIN, token: SLACK_TOKEN I can receive the message from Jenkins now. Every channel need one token and I used other channel's token before. But it still report error message from Jenkins console output run slackstepsend, step null:false, desc : , falseSlack Send Pipeline step configured values from global config - baseUrl: true, teamDomain: false, token: false, channel: false, color: false And one more, I don't configure the Global Slack Notifier Settings. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48475) Build step returns null if propagate set to true
Title: Message Title vadim sluzky edited a comment on JENKINS-48475 Re: Build step returns null if propagate set to true There is still a problem with that implementation.If propagate is set to false, all the corresponding tests are displayed in GREENIs it possible to let the upstream job know about failures?Are there any problems with returning real non-null result if wait is true? What is the logic behind using 'propagate' field to whether returning result?I strongly believe it should be returned or not based on 'wait' parameter and this is a valid non-minor defects defect that does not have a workaround and needs to be fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48475) Build step returns null if propagate set to true
Title: Message Title vadim sluzky edited a comment on JENKINS-48475 Re: Build step returns null if propagate set to true There is still a problem with that implementation.If propagate is set to false, all the corresponding tests are displayed in GREENIs it possible to let the upstream job know about failures?Are there any problems with returning real non-null result if wait is true? What is the logic behind using 'propagate' field to whether returning result? I strongly believe it should be returned or not based on 'wait' parameter and this is a valid non-minor defects that does not have a workaround Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49495) False positive for LLVM/Clang
Title: Message Title Steffen Kötte created an issue Jenkins / JENKINS-49495 False positive for LLVM/Clang Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-02-12 02:01 Environment: Jenkins 2.46.2 Priority: Minor Reporter: Steffen Kötte 01 Copying the source file '2018-02-12 01' from the workspace to the build folder '25bd.tmp' on the Jenkins master failed. 02 Seems that the path is relative, however an absolute path is required when copying the sources. 03 Is the file '2018-02-12 01' contained more than once in your workspace? 04 Is the file '2018-02-12 01' a valid filename? 05 If you are building on a slave: please check if the file is accessible under '$JENKINS_HOME/[job-name]/2018-02-12 01' 06 If you are building on the master: please check if the file is accessible under '$JENKINS_HOME/[job-name]/workspace/2018-02-12 01' Follow up for https://wiki.jenkins.io/display/JENKINS/Warnings+Plugin?focusedCommentId=138446333=1515495766539#app-switcher The part of the log which is producing the issue is this:
[JIRA] (JENKINS-47022) DropDown is loosing focus on selection of an option
Title: Message Title Nicolae Pascu started work on JENKINS-47022 Change By: Nicolae Pascu Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48475) Build step returns null if propagate set to true
Title: Message Title vadim sluzky edited a comment on JENKINS-48475 Re: Build step returns null if propagate set to true There is still a problem with that implementation.If propagate is set to false, all the corresponding tests are displayed in GREENIs it possible to let the upstream job know about failures? Are there any problems with returning real non-null result if wait is true? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48475) Build step returns null if propagate set to true
Title: Message Title vadim sluzky commented on JENKINS-48475 Re: Build step returns null if propagate set to true There is still a problem with that implementation. If propagate is set to false, all the corresponding tests are displayed in GREEN Is it possible to let the upstream job know about failures? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49494) Add support for Jenkins Pipeline to the Eggplant plugin
Title: Message Title Lincoln Peters created an issue Jenkins / JENKINS-49494 Add support for Jenkins Pipeline to the Eggplant plugin Issue Type: Improvement Assignee: Unassigned Components: eggplant-plugin Created: 2018-02-12 00:04 Labels: pipeline Priority: Minor Reporter: Lincoln Peters Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49490) Failed to run AVD creation on MAC
Title: Message Title Christopher Orr closed an issue as Not A Defect The log says: > Warning: Failed to find package system-images;android-19;google_apis;x86_64 Indeed, running sdkmanager --list | grep android-19 shows that there is no x86_64 image for Android 19 with Google APIs. You would need to use x86. Jenkins / JENKINS-49490 Failed to run AVD creation on MAC Change By: Christopher Orr Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-49493) CF push failing with Jenkins
Title: Message Title Lokeswara Katuru created an issue Jenkins / JENKINS-49493 CF push failing with Jenkins Issue Type: Bug Assignee: olamy Attachments: JenkinsError.txt Components: cloudfoundry-plugin Created: 2018-02-11 23:47 Labels: plugin Priority: Critical Reporter: Lokeswara Katuru CF push is failing when using thru Jenkins with below error: Please refer attachment for complete error log. FYI:Jar file size : ~45 MB Verified internet speed and it is ~ 100MB/s STDERR: "warning [/var/vcap/data/cloud_controller_ng/tmp/uploads/000525]: 8039 extra bytes at beginning or within zipfile (attempting to process anyway) " at org.cloudfoundry.util.JobUtils.getError(JobUtils.java:103) at reactor.core.publisher.MonoThenMap$ThenMapMain.onNext(MonoThenMap.java:120) Add Comment
[JIRA] (JENKINS-48475) Build step returns null if propagate set to true
Title: Message Title vadim sluzky commented on JENKINS-48475 Re: Build step returns null if propagate set to true Got it. I set propagate to false and then analyzed result field. Thank you for quick help, Andrew! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48475) Build step returns null if propagate set to true
Title: Message Title Andrew Bayer commented on JENKINS-48475 Re: Build step returns null if propagate set to true Set `propagate` to false. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48475) Build step returns null if propagate set to true
Title: Message Title vadim sluzky commented on JENKINS-48475 Re: Build step returns null if propagate set to true I can not agree that this is a correct behavior. It's a blocker for the following use case I'm trying to implement: Run a set of tests represented by Jenkins Jobs For jobs that fail post name of the test and a link to a corresponding build For failing tests build step returns null and I can't get BUILD_URL May you suggest an alternative way to unblock me? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22489) Add the ability to specify where each script executes instead of all of the scripts when added to a matrix job.
Title: Message Title Daniel Heid closed an issue as Done Jenkins / JENKINS-22489 Add the ability to specify where each script executes instead of all of the scripts when added to a matrix job. Change By: Daniel Heid Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-22489) Add the ability to specify where each script executes instead of all of the scripts when added to a matrix job.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-22489 Re: Add the ability to specify where each script executes instead of all of the scripts when added to a matrix job. Code changed in jenkins User: Daniel Heid Path: README.md src/main/java/org/jenkinsci/plugins/postbuildscript/ConfigurableMatrixAggregator.java src/main/java/org/jenkinsci/plugins/postbuildscript/ExecuteOn.java src/main/java/org/jenkinsci/plugins/postbuildscript/MatrixPostBuildScript.java src/main/java/org/jenkinsci/plugins/postbuildscript/PostBuildScript.java src/main/java/org/jenkinsci/plugins/postbuildscript/Processor.java src/main/java/org/jenkinsci/plugins/postbuildscript/ProcessorFactory.java src/main/java/org/jenkinsci/plugins/postbuildscript/model/ExecuteOn.java src/main/java/org/jenkinsci/plugins/postbuildscript/model/PostBuildItem.java src/main/java/org/jenkinsci/plugins/postbuildscript/processor/Processor.java src/main/java/org/jenkinsci/plugins/postbuildscript/processor/ProcessorFactory.java src/main/java/org/jenkinsci/plugins/postbuildscript/processor/rules/ExecutionRule.java src/main/java/org/jenkinsci/plugins/postbuildscript/processor/rules/MatrixRule.java src/main/java/org/jenkinsci/plugins/postbuildscript/processor/rules/ResultRule.java src/main/java/org/jenkinsci/plugins/postbuildscript/processor/rules/RoleRule.java src/main/resources/lib/postbuildscript/form.jelly src/main/resources/lib/postbuildscript/form_de.properties src/main/resources/org/jenkinsci/plugins/postbuildscript/MatrixPostBuildScript/config.jelly src/main/resources/org/jenkinsci/plugins/postbuildscript/MatrixPostBuildScript/config_de.properties src/main/resources/org/jenkinsci/plugins/postbuildscript/Messages.properties src/main/resources/org/jenkinsci/plugins/postbuildscript/Messages_de.properties src/main/webapp/help/execute-on.html src/test/java/org/jenkinsci/plugins/postbuildscript/ConfigurableMatrixAggregatorTest.java src/test/java/org/jenkinsci/plugins/postbuildscript/ExecuteOnTest.java src/test/java/org/jenkinsci/plugins/postbuildscript/model/ExecuteOnTest.java src/test/java/org/jenkinsci/plugins/postbuildscript/processor/rules/MatrixRuleTest.java src/test/java/org/jenkinsci/plugins/postbuildscript/processor/rules/ResultRuleTest.java src/test/java/org/jenkinsci/plugins/postbuildscript/processor/rules/RoleRuleTest.java http://jenkins-ci.org/commit/postbuildscript-plugin/1f7ec730435a3a7d16412d480cbe3641b5909150 Log: JENKINS-22489 - Add the ability to specify where each script executes instead of all of the scripts when added to a matrix job. Add Comment
[JIRA] (JENKINS-22489) Add the ability to specify where each script executes instead of all of the scripts when added to a matrix job.
Title: Message Title Daniel Heid resolved as Done Jenkins / JENKINS-22489 Add the ability to specify where each script executes instead of all of the scripts when added to a matrix job. Change By: Daniel Heid Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49490) Failed to run AVD creation on MAC
Title: Message Title theexplorer commented on JENKINS-49490 Re: Failed to run AVD creation on MAC Christopher Orr Any suggestions ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34311) execute scripts on axes after all build steps are finished
Title: Message Title Daniel Heid updated an issue Jenkins / JENKINS-34311 execute scripts on axes after all build steps are finished Change By: Daniel Heid Summary: execute scripts on axes after all build steps are fnished finished Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49492) EC2 remote ssh ports system setting got lost after restart
Title: Message Title Alexander Vorobiev created an issue Jenkins / JENKINS-49492 EC2 remote ssh ports system setting got lost after restart Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2018-02-11 15:17 Environment: Jenkins 2.89.3 EC2 plugin 1.38 Priority: Major Reporter: Alexander Vorobiev 1. In 'Configure System' > Cloud > Amazon EC2 > AMIs: Change 'Remote ssh port' to 1. 2. Restart Jenkins The port in this setting appears as 22, while it is expected to stay 1. Add Comment
[JIRA] (JENKINS-46280) Postbuild fails when used with amazon-ecs plugin
Title: Message Title Daniel Heid commented on JENKINS-46280 Re: Postbuild fails when used with amazon-ecs plugin I don't think that this has something to do with the postbuildscript plugin and removed the component. Please provide your postbuildscript configuration. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46280) Postbuild fails when used with amazon-ecs plugin
Title: Message Title Daniel Heid updated an issue Jenkins / JENKINS-46280 Postbuild fails when used with amazon-ecs plugin Change By: Daniel Heid Component/s: postbuildscript-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48014) Allow sandboxing for Groovy scripts
Title: Message Title Daniel Heid closed an issue as Done Jenkins / JENKINS-48014 Allow sandboxing for Groovy scripts Change By: Daniel Heid Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48014) Allow sandboxing for Groovy scripts
Title: Message Title SCM/JIRA link daemon commented on JENKINS-48014 Re: Allow sandboxing for Groovy scripts Code changed in jenkins User: Daniel Heid Path: README.md pom.xml src/main/java/org/jenkinsci/plugins/postbuildscript/Processor.java src/main/java/org/jenkinsci/plugins/postbuildscript/model/Script.java src/main/java/org/jenkinsci/plugins/postbuildscript/model/ScriptFile.java src/main/java/org/jenkinsci/plugins/postbuildscript/service/GroovyScriptExecutor.java src/main/java/org/jenkinsci/plugins/postbuildscript/service/GroovyScriptExecutorFactory.java src/main/java/org/jenkinsci/plugins/postbuildscript/service/GroovyScriptPreparer.java src/main/resources/lib/postbuildscript/form.jelly src/main/resources/lib/postbuildscript/form_de.properties src/main/webapp/help/sandbox.html src/test/java/org/jenkinsci/plugins/postbuildscript/service/GroovyScriptExecutorFactoryTest.java src/test/java/org/jenkinsci/plugins/postbuildscript/service/GroovyScriptExecutorIT.java src/test/java/org/jenkinsci/plugins/postbuildscript/service/GroovyScriptPreparerTest.java http://jenkins-ci.org/commit/postbuildscript-plugin/4575c2423085242403aa3a9af991cb711470d898 Log: JENKINS-48014 Allow sandboxing for Groovy scripts Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48102) CMake plugin leaks file handle on CMakeCache.txt
Title: Message Title Martin Weber resolved as Fixed Jenkins / JENKINS-48102 CMake plugin leaks file handle on CMakeCache.txt Change By: Martin Weber Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49482) Hide empty 'Deployed Artifacts:'
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49482 Re: Hide empty 'Deployed Artifacts:' Code changed in jenkins User: Bing Shiao Path: jenkins-plugin/src/main/resources/org/jenkinsci/plugins/pipeline/maven/publishers/MavenLinkerPublisher/summary.jelly http://jenkins-ci.org/commit/pipeline-maven-plugin/f39c4e6338fb69776173d1358507cdc08ef92f7c Log: JENKINS-49482 Hide empty 'Deployed Artifacts:' (#124) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49038) Jenkins does not start due to a deadlock
Title: Message Title Arnaud TAMAILLON commented on JENKINS-49038 Re: Jenkins does not start due to a deadlock Fly Cricket, can you test https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fclaim-plugin/detail/PR-53/1/artifacts version please, to tell me if situation is better ? I'm still not managing to reproduce, but am under the impression that it is probably linked to the actual list of plugins and maybe threads used by the task reactor lib, as on my dev pc, the deadlock does not occur. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43038) Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins
Title: Message Title Tsvi Mostovicz commented on JENKINS-43038 Re: Intermittent error "Cannot contact node123: java.lang.InterruptedException " in jenkins I see this issue as well during testing which can take about 10-20 minutes of running a single shell script. I suppose it happens when the agent gets disconnected for a split second. Is there anyway to create a workaround protecting the shell script from this. At the moment I have to manually abort the running test. Thanks, Tsvi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47085) Responsive stage names in blue ocean pipeline view
Title: Message Title Tsvi Mostovicz commented on JENKINS-47085 Re: Responsive stage names in blue ocean pipeline view Hi James Dumay, I have the same issue as Sam Gleske. We create the stage name programmatically. Our pipeline runs through a matrix of a variety of flavors and environments for testing. The stage name is from a string "flavor/environment". Unfortunately, the flavor in a lot of cases takes the whole string, so we can't really see what environment the dot relates to. Please see the attached image. I would appreciate if the size of the column could be set dynamically. Thanks, Tsvi Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47085) Responsive stage names in blue ocean pipeline view
Title: Message Title Tsvi Mostovicz updated an issue Jenkins / JENKINS-47085 Responsive stage names in blue ocean pipeline view Change By: Tsvi Mostovicz Attachment: image-2018-02-11-14-04-32-495.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title
Sam Gleske edited a comment on JENKINS-49406
Re: Prototype the Evergreen snapshotting data safety system
Example from my Jenkins RPM package: * [preUninstall.sh script running dailycommit.sh to save a copy of configuration before package upgrade|https://github.com/samrocketman/jenkins-bootstrap-shared/blob/0aa6a14868bb05105bb558c9c4d9ba0bca8a9d04/packaging/preUninstall.sh.in].* [Example gitignore used for my JENKINS_HOME|https://github.com/samrocketman/jenkins-bootstrap-shared/blob/0aa6a14868bb05105bb558c9c4d9ba0bca8a9d04/packaging/share/gitignore.in].* [Contents of dailycommit.sh|https://github.com/samrocketman/jenkins-bootstrap-shared/blob/0aa6a14868bb05105bb558c9c4d9ba0bca8a9d04/packaging/share/dailycommit.sh.in].That repository supports packaging Jenkins and plugins into multiple formats.{noformat}./gradlew buildRpm./gradlew buildDeb./gradlew buildTar#or package all three with ./gradlew packages#docker requires buildTardocker build -t jenkins .{noformat} h1. Additional notes * One of the challenges I discussed with [~rtyler] was setting workspaces for jobs building on master outside of JENKINS_HOME. Otherwise, you encounter weird issues with Git repositories inside of other Git repositories when they're not submodules. In general, we know it's bad practice for people to build on the master but it still gets done.* The gitignore file I linked intentionally does not track secret.key or the secrets directory. The intention here is that secrets get backed up separately from the encrypted configuration. However, this may not matter to some organizations. * Eventually, I want to completely rewrite the service scripts I copied from jenkins-packaging. Mainly because I have a different style of bash writing and will propose my changes back.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title
Sam Gleske edited a comment on JENKINS-49406
Re: Prototype the Evergreen snapshotting data safety system
Example from my Jenkins RPM package:* [preUninstall.sh script running dailycommit.sh to save a copy of configuration before package upgrade|https://github.com/samrocketman/jenkins-bootstrap-shared/blob/0aa6a14868bb05105bb558c9c4d9ba0bca8a9d04/packaging/preUninstall.sh.in].* [Example gitignore used for my JENKINS_HOME|https://github.com/samrocketman/jenkins-bootstrap-shared/blob/0aa6a14868bb05105bb558c9c4d9ba0bca8a9d04/packaging/share/gitignore.in].* [Contents of dailycommit.sh|https://github.com/samrocketman/jenkins-bootstrap-shared/blob/0aa6a14868bb05105bb558c9c4d9ba0bca8a9d04/packaging/share/dailycommit.sh.in].That repository supports packaging Jenkins and plugins into multiple formats.{noformat}./gradlew buildRpm./gradlew buildDeb./gradlew buildTar#or package all three with ./gradlew packages#docker requires buildTardocker build -t jenkins .{noformat} h1. Additional notes* One of the challenges I discussed with [~rtyler] was setting workspaces for jobs building on master outside of JENKINS_HOME. Otherwise, you encounter weird issues with Git repositories inside of other Git repositories when they're not submodules. In general, we know it's bad practice for people to build on the master but it still gets done.* The gitignore file I linked intentionally does not track secret.key or the secrets directory. The intention here is that secrets get backed up separately from the encrypted configuration. However, this may not matter to some organizations.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title Sam Gleske commented on JENKINS-49406 Re: Prototype the Evergreen snapshotting data safety system Example from my Jenkins RPM package: preUninstall.sh script running dailycommit.sh to save a copy of configuration before package upgrade. Example gitignore used for my JENKINS_HOME. Contents of dailycommit.sh. That repository supports packaging Jenkins and plugins into multiple formats. ./gradlew buildRpm ./gradlew buildDeb ./gradlew buildTar #or package all three with ./gradlew packages #docker requires buildTar docker build -t jenkins . Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49485) jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
Title: Message Title
Sam Gleske resolved as Cannot Reproduce
I provisioned Jenkins 2.89.2 with github-oauth 0.28.1. Configured the global security to use my GitHub OAuth app. Configured scopes: read:org, user:email, repo I logged in just fine. You likely have your GitHub scopes incorrectly configured. That's the most common misconfiguration. See also:
https://developer.github.com/apps/building-oauth-apps/scopes-for-oauth-apps/
Jenkins / JENKINS-49485
jenkin crashes with {"message":"Bad credentials","documentation_url":"https://developer.github.com/v3"}
Change By:
Sam Gleske
Status:
Open Resolved
Resolution:
Cannot Reproduce
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
