[JIRA] (JENKINS-53710) Update site signature validation fails on Java 11
Title: Message Title Sam Van Oort updated JENKINS-53710 Jenkins / JENKINS-53710 Update site signature validation fails on Java 11 Change By: Sam Van Oort Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53729) Regression HyperlinkNote serialization: serialVersionUID
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-53729 Regression HyperlinkNote serialization: serialVersionUID Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-09-22 04:24 Labels: regression Priority: Minor Reporter: Oleg Nenashev Placeholder for https://github.com/jenkinsci/jenkins/pull/3613 from Devin Nusbaum Add Comment
[JIRA] (JENKINS-53728) No such method if git-client 3.0.0 beta is used with declarative pipeline
Title: Message Title Mark Waite commented on JENKINS-53728 Re: No such method if git-client 3.0.0 beta is used with declarative pipeline Sorry for the mistake on this one. The most recent beta release of the git plugin is "behind" the most recent release of the git client plugin. The most recent git plugin release contains a dependency on JGit 4.x while the most recent beta release of the git client plugin delivers JGit 5.x. The immediate workaround is to base your plugin builds on the incremental versions of git client plugin and git plugin until the next beta release of both. The incremental for git client plugin is git-client-3.0.0-beta6-rc1776.912790760394 The incremental for git plugin is git/4.0.0-rc2892.70634f157021/git-4.0.0-rc2892.70634f157021.hpi 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-53728) No such method if git-client 3.0.0 beta is used with declarative pipeline
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-53728 No such method if git-client 3.0.0 beta is used with declarative pipeline Issue Type: Improvement Assignee: Mark Waite Components: git-client-plugin Created: 2018-09-22 03:55 Environment: git-client 3.0.0 beta 5 git 4.0.0 beta 3 Priority: Minor Reporter: Ulli Hafner I integrated warnings plugin 5.0.0 beta with Git-Client plugin 3.0.0 beta. I get the following exception: java.lang.NoSuchMethodError: org.eclipse.jgit.lib.Repository.getRef(Ljava/lang/String;)Lorg/eclipse/jgit/lib/Ref; at jenkins.plugins.git.GitSCMFileSystem.lambda$new$0(GitSCMFileSystem.java:114) at jenkins.plugins.git.GitSCMFileSystem.lambda$invoke$e8567d7e$1(GitSCMFileSystem.java:181) at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.withRepository(AbstractGitAPIImpl.java:28) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.withRepository(CliGitAPIImpl.java:75) at jenkins.plugins.git.GitSCMFileSystem.invoke(GitSCMFileSystem.java:181) at jenkins.plugins.git.GitSCMFileSystem.(GitSCMFileSystem.java:114) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:339) 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:108) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:67) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:303) at
[JIRA] (JENKINS-52023) If we update Groovy to 2.4.12 for Java 10, Pipeline builds leaks Metaspace memory
Title: Message Title Sam Van Oort resolved as Cannot Reproduce It seems I can no longer reproduce the leaks – at least with current Java core versions – despite extensive testing. Something in the current round of hacking seems to have resolved this. Jenkins / JENKINS-52023 If we update Groovy to 2.4.12 for Java 10, Pipeline builds leaks Metaspace memory Change By: Sam Van Oort Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53727) Resolve branch build problem
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-53727 Resolve branch build problem Issue Type: Bug Assignee: Pham Vu Tuan Components: simple-pull-request-job-plugin Created: 2018-09-22 03:05 Priority: Minor Reporter: Pham Vu Tuan Currently there are build problems with the building branches for the plugin, that might be mismatch in the pipeline plugin version. [Pipeline] End of Pipeline java.lang.NoSuchMethodError: No such DSL method 'buildPlugin' found among steps [archive, bat, build, catchError, checkout, deleteDir, dir, dockerFingerprintFrom, dockerFingerprintRun, echo, error, fileExists, getContext, git, gitPush, input, isUnix, load, mail, milestone, node, parallel, powershell, properties, pwd, readFile, readTrusted, resolveScm, retry, sh, sleep, stage, stash, step, timeout, tool, unarchive, unstash, waitUntil, withContext, withCredentials, withDockerContainer, withDockerRegistry, withDockerServer, withEnv, wrap, writeFile, ws] or symbols [agent, all, always, apiToken, architecture, archiveArtifacts, artifactManager, batchFile, booleanParam, buildButton, buildDiscarder, caseInsensitive, caseSensitive, certificate, choice, choiceParam, clock, cloud, command, credentials, cron, crumb, defaultView, demand, disableConcurrentBuilds, dockerCert, downloadSettings, downstream, dumb, envVars, file, fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, fromScm, fromSource, git, gitPush, headRegexFilter, headWildcardFilter, hyperlink, hyperlinkToModels, installSource, jdk, jdkInstaller, jgit, jgitapache, jnlp, jobName, junit, lastDuration, lastFailure, lastGrantedAuthorities, lastStable, lastSuccess, legacy, list, local, location, logRotator, loggedInUsersCanDoAnything, masterBuild, maven, maven3Mojos, mavenErrors, mavenMojos, mavenWarnings, myView,
[JIRA] (JENKINS-52664) support for either .yaml or .yml
Title: Message Title Pham Vu Tuan started work on JENKINS-52664 Change By: Pham Vu Tuan 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-48708) Username Password for OAuth based authentication
Title: Message Title
Wayne Warren commented on JENKINS-48708
Re: Username Password for OAuth based authentication
A simple workaround for this problem: ``` curl https://api.github.com/authorizations --user $USERNAME --data '{"scopes":["user:email","read:org"],"note":"jenkins swarm clients"}' ``` You will be prompted to enter your password. The response will look something like: ``` { ... "token": "" ... } ``` You would then take the 'token' value from here for use as the `-password` field in the swarm client command line. That's all there is to it! The token doesn't expire as far as I can tell; you can manually revoke it from the github web ui at https://github.com/settings/tokens. The `note` field in the abovementioned curl call ends up being the name of the token (attempting to obtain a new token with the same name will fail. Come to think of it you don't need to use the above curl command since you can just generate a token at the same tokens url; it just needs `user:email` and `read:org` 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-53726) Rename of the plugin
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-53726 Rename of the plugin Issue Type: Improvement Assignee: Pham Vu Tuan Components: simple-pull-request-job-plugin Created: 2018-09-22 00:45 Priority: Minor Reporter: Pham Vu Tuan 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-52519) Release 1.0-rc-1 version
Title: Message Title Pham Vu Tuan assigned an issue to Pham Vu Tuan Jenkins / JENKINS-52519 Release 1.0-rc-1 version Change By: Pham Vu Tuan Assignee: Abhishek Gautam Pham Vu Tuan 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-52664) support for either .yaml or .yml
Title: Message Title Pham Vu Tuan assigned an issue to Pham Vu Tuan Jenkins / JENKINS-52664 support for either .yaml or .yml Change By: Pham Vu Tuan Assignee: Abhishek Gautam Pham Vu Tuan 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-53717) Keep extension point inside the plugin
Title: Message Title Pham Vu Tuan updated an issue Jenkins / JENKINS-53717 Keep extension point inside the plugin Change By: Pham Vu Tuan Summary: Keep extension point inside the plugn 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-53717) Keep extension point inside the plugn
Title: Message Title Pham Vu Tuan assigned an issue to Pham Vu Tuan Jenkins / JENKINS-53717 Keep extension point inside the plugn Change By: Pham Vu Tuan Assignee: Abhishek Gautam Pham Vu Tuan 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-53684) Provide links for all tabs in details page
Title: Message Title Ulli Hafner commented on JENKINS-53684 Re: Provide links for all tabs in details page I'm not sure if I understand correctly. Pipelines and Freestyle projects in 5.x have the same UI. Which UI do you prefer exactly? 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-51813) Write tests for the plugin
Title: Message Title Pham Vu Tuan updated JENKINS-51813 Jenkins / JENKINS-51813 Write tests for the plugin Change By: Pham Vu Tuan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51813) Write tests for the plugin
Title: Message Title Pham Vu Tuan updated JENKINS-51813 Jenkins / JENKINS-51813 Write tests for the plugin Change By: Pham Vu Tuan Status: In Review Resolved Resolution: Done 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-53684) Provide links for all tabs in details page
Title: Message Title Flash Sheridan commented on JENKINS-53684 Re: Provide links for all tabs in details page Thanks very much; I had to upgrade to 5.0ß today for a new Pipeline project, so that will suffice for us. (The backward compatibility for a non-Pipeline build seemed fine, by the way—the only difference I’ve noticed so far was the Deprecated label. I do prefer the old non-Pipeline appearance though; it’s more information-rich, with things like New and Fixed numbers prominently displayed.) 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-53710) Update site signature validation fails on Java 11
Title: Message Title Daniel Beck updated JENKINS-53710 Jenkins / JENKINS-53710 Update site signature validation fails on Java 11 Change By: Daniel Beck 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-53710) Update site signature validation fails on Java 11
Title: Message Title Daniel Beck updated JENKINS-53710 Jenkins / JENKINS-53710 Update site signature validation fails on Java 11 Change By: Daniel Beck Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53710) Update site signature validation fails on Java 11
Title: Message Title Daniel Beck started work on JENKINS-53710 Change By: Daniel Beck 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-53725) git-plugin cannot operate on a git-worktree
Title: Message Title
T L updated an issue
Jenkins / JENKINS-53725
git-plugin cannot operate on a git-worktree
Change By:
T L
Core issue: JGit doesn't support git-worktree yet.Trigger: git-plugin tries to retrieve the commit message via JGit in order to print it to the log, fails the build on errorPossible short-term solution: make printing the commit message optionalPossible short-term solution: make errors while printing the commit message not fail the build Possible long-term solution: fix JGit to support git-worktree Possible long-term solution: stop using JGit Stack trace:{noformat} > git checkout -f 22ae7e760b087f56426e764b5762ec58506dba04org.eclipse.jgit.errors.MissingObjectException: Missing unknown 22ae7e760b087f56426e764b5762ec58506dba04 at org.eclipse.jgit.internal.storage.file.WindowCursor.open(WindowCursor.java:158) at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:227) at org.eclipse.jgit.revwalk.RevWalk.parseAny(RevWalk.java:859) at org.eclipse.jgit.revwalk.RevWalk.parseCommit(RevWalk.java:772) at hudson.plugins.git.util.RevCommitRepositoryCallback.invoke(RevCommitRepositoryCallback.java:25) at hudson.plugins.git.util.RevCommitRepositoryCallback.invoke(RevCommitRepositoryCallback.java:13) at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.withRepository(AbstractGitAPIImpl.java:29) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.withRepository(CliGitAPIImpl.java:72) at hudson.plugins.git.GitSCM.printCommitMessageToLog(GitSCM.java:1271) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1244) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1806) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429){noformat}This previously worked. Likely up to git-plugin 3.3.0.
Add Comment
[JIRA] (JENKINS-53725) git-plugin cannot operate on a git-worktree
Title: Message Title
T L updated an issue
Jenkins / JENKINS-53725
git-plugin cannot operate on a git-worktree
Change By:
T L
Labels:
regression
Core issue: JGit doesn't support git-worktree yet.Trigger: git-plugin tries to retrieve the commit message via JGit in order to print it to the log, fails the build on errorPossible solution: make printing the commit message optionalPossible solution: make errors while printing the commit message not fail the buildStack trace:{noformat} > git checkout -f 22ae7e760b087f56426e764b5762ec58506dba04org.eclipse.jgit.errors.MissingObjectException: Missing unknown 22ae7e760b087f56426e764b5762ec58506dba04 at org.eclipse.jgit.internal.storage.file.WindowCursor.open(WindowCursor.java:158) at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:227) at org.eclipse.jgit.revwalk.RevWalk.parseAny(RevWalk.java:859) at org.eclipse.jgit.revwalk.RevWalk.parseCommit(RevWalk.java:772) at hudson.plugins.git.util.RevCommitRepositoryCallback.invoke(RevCommitRepositoryCallback.java:25) at hudson.plugins.git.util.RevCommitRepositoryCallback.invoke(RevCommitRepositoryCallback.java:13) at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.withRepository(AbstractGitAPIImpl.java:29) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.withRepository(CliGitAPIImpl.java:72) at hudson.plugins.git.GitSCM.printCommitMessageToLog(GitSCM.java:1271) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1244) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1806) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429){noformat} This previously worked. Likely up to git-plugin 3.3.0.
[JIRA] (JENKINS-53725) git-plugin cannot operate on a git-worktree
Title: Message Title T L created an issue Jenkins / JENKINS-53725 git-plugin cannot operate on a git-worktree Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2018-09-22 00:21 Priority: Minor Reporter: T L Core issue: JGit doesn't support git-worktree yet. Trigger: git-plugin tries to retrieve the commit message via JGit in order to print it to the log, fails the build on error Possible solution: make printing the commit message optional Possible solution: make errors while printing the commit message not fail the build Stack trace: > git checkout -f 22ae7e760b087f56426e764b5762ec58506dba04org.eclipse.jgit.errors.MissingObjectException: Missing unknown 22ae7e760b087f56426e764b5762ec58506dba04 at org.eclipse.jgit.internal.storage.file.WindowCursor.open(WindowCursor.java:158) at org.eclipse.jgit.lib.ObjectReader.open(ObjectReader.java:227) at org.eclipse.jgit.revwalk.RevWalk.parseAny(RevWalk.java:859) at org.eclipse.jgit.revwalk.RevWalk.parseCommit(RevWalk.java:772) at hudson.plugins.git.util.RevCommitRepositoryCallback.invoke(RevCommitRepositoryCallback.java:25) at hudson.plugins.git.util.RevCommitRepositoryCallback.invoke(RevCommitRepositoryCallback.java:13) at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.withRepository(AbstractGitAPIImpl.java:29) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.withRepository(CliGitAPIImpl.java:72) at hudson.plugins.git.GitSCM.printCommitMessageToLog(GitSCM.java:1271) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1244) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at
[JIRA] (JENKINS-2111) removing a job (including multibranch/org folder branches/repos) does not remove the workspace
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-2111 removing a job (including multibranch/org folder branches/repos) does not remove the workspace Change By: Jesse Glick Assignee: rsandell Jesse Glick 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 started work on JENKINS-2111 Change By: Jesse Glick 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-53684) Provide links for all tabs in details page
Title: Message Title Ulli Hafner commented on JENKINS-53684 Re: Provide links for all tabs in details page Added support for URL switching in upcoming 5.0 release, see #2547d29. So once the Git blame functionality is integrated into the 5.0 release (still under development) it should be available. 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-51897) Delete work space when PR closed.
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-51897 Delete work space when PR closed. Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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-53724) EnvVars.masterEnvVars is widely used as a public collection without synchronization
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-53724 EnvVars.masterEnvVars is widely used as a public collection without synchronization Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-09-21 23:39 Priority: Critical Reporter: Oleg Nenashev Originally discovered while fixing Illegal Reflective Access in EnvInject (CC Jeff Pearce). There are many usages of the field: https://github.com/search?q=org%3Ajenkinsci+%22masterEnvVars%22=Code . In many cases the collection is modified, but there is no synchronization in the code. So there is a risk of Concurrent modification exceptions I propose reworking the code, e.g. by introducing CopyOnWriteEnvVars or so which follows the same interface Add Comment
[JIRA] (JENKINS-52016) Build parameters & env variables not working to Publish Over SSH
Title: Message Title Alex Earl commented on JENKINS-52016 Re: Build parameters & env variables not working to Publish Over SSH I even tried using variables in the source files text box and that worked fine too. 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-52016) Build parameters & env variables not working to Publish Over SSH
Title: Message Title Alex Earl commented on JENKINS-52016 Re: Build parameters & env variables not working to Publish Over SSH I can't reproduce this. I setup an environment variable in the global config for Jenkins and also setup a parameter for the build. I used both in the remote directory and it worked just fine, the variables were expanded and the correct stuff was done. Is there a specific field that is having issues? 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-53723) [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync
Title: Message Title
Stuart Rowe created an issue
Jenkins / JENKINS-53723
[P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync
Issue Type:
New Feature
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-09-21 23:14
Priority:
Major
Reporter:
Stuart Rowe
The pin property is difficult to work with because it affects polling. Add an additional String property such as buildChange or change to the Populate class that can be set via a @DataBoundSetter. Update CheckoutTask#getBuildChange to also consider this value (if set) to determine the build change. This will at least allow pipelines to easily sync to specific changelists / labels / counters that come from job parameters. Example (assuming String parameter 'Changelist' exists):
checkout(
perforce(
credential: 'credential',
populate: syncOnly(
change: params.Changelist,
force: false,
have: true,
modtime: false,
parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'],
pin: '',
quiet: false,
revert: false
),
workspace: streamSpec(
charset: 'none',
format: 'jenkins-${NODE_NAME}-${JOB_NAME}',
pinHost: true,
streamName: '//depot/path'
)
)
)
[JIRA] (JENKINS-53722) JdbcSQLException Unique index or primary key violation
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-53722 JdbcSQLException Unique index or primary key violation Issue Type: Bug Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2018-09-21 22:56 Priority: Minor Reporter: Cyrille Le Clerc In some edge cases ERROR: [withMaven] WARNING Exception executing Maven reporter 'Pipeline Graph Publisher' / org.jenkinsci.plugins.pipeline.maven.publishers.PipelineGraphPublisher. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org org.jenkinsci.plugins.pipeline.maven.util.RuntimeSqlException: org.h2.jdbc.JdbcSQLException: Unique index or primary key violation: "IDX_JENKINS_JOB ON PUBLIC.JENKINS_JOB(JENKINS_MASTER_ID, FULL_NAME) VALUES (1, 'maven-jar-with-flatten-pom/master', 147)"; SQL statement: INSERT INTO JENKINS_JOB(FULL_NAME, JENKINS_MASTER_ID) VALUES (?, ?) [23505-196] at org.h2.message.DbException.getJdbcSQLException(DbException.java:345) at org.h2.message.DbException.get(DbException.java:179) at org.h2.message.DbException.get(DbException.java:155) at org.h2.index.BaseIndex.getDuplicateKeyException(BaseIndex.java:103) at org.h2.mvstore.db.MVSecondaryIndex.checkUnique(MVSecondaryIndex.java:231) at org.h2.mvstore.db.MVSecondaryIndex.add(MVSecondaryIndex.java:190) at org.h2.mvstore.db.MVTable.addRow(MVTable.java:705) at org.h2.command.dml.Insert.insertRows(Insert.java:156) at org.h2.command.dml.Insert.update(Insert.java:114) at org.h2.command.CommandContainer.update(CommandContainer.java:101) at org.h2.command.Command.executeUpdate(Command.java:260) at org.h2.server.TcpServerThread.process(TcpServerThread.java:354) at org.h2.server.TcpServerThread.run(TcpServerThread.java:158) at java.lang.Thread.run(Thread.java:748) at
[JIRA] (JENKINS-53721) Add support for setting envVars.Platform
Title: Message Title Jeff Pearce created an issue Jenkins / JENKINS-53721 Add support for setting envVars.Platform Issue Type: Improvement Assignee: Jeff Pearce Components: core Created: 2018-09-21 22:53 Priority: Minor Reporter: Jeff Pearce In order to remove the setAccessible warning in the envinject plugin, we need to add a setter to allow it to set the Platform in the environment variables (currently that's done via reflection) Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-47163) Use same workspace or node in multiple stages in pipeline
Title: Message Title Victor Bjelkholm assigned an issue to Victor Bjelkholm Jenkins / JENKINS-47163 Use same workspace or node in multiple stages in pipeline Change By: Victor Bjelkholm Assignee: Andrew Bayer Victor Bjelkholm 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-51811) KubernetesSlave should override getWorkspaceFor(TopLevelItem)
Title: Message Title Jesse Glick commented on JENKINS-51811 Re: KubernetesSlave should override getWorkspaceFor(TopLevelItem) For comparison the dockerNode step just sets the workspace to be a fixed subdirectory. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52464) Issues using RunResultRecorder in pipelines
Title: Message Title Chris Rock reopened an issue I've updated to 5.5 and I'm still running into the WorkflowJob to Project conversion error. The first part of this bug is fixed and I can now generate the pipeline step for the run result recorder but that step still doesn't work. I tested both putting the runResultRecorder step immediately after the runFromAlmBuilder step and putting the recorder step into a declarative post action. None of the other information has changed. One thing I may not have mentioned but I'm not sure it makes a difference is that we are using Declarative Pipelines. The error again for reference: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.Project at com.microfocus.application.automation.tools.results.RunResultRecorder.perform(RunResultRecorder.java:1406) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:78) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:65) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:49) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Jenkins / JENKINS-52464 Issues using RunResultRecorder in pipelines Change By: Chris Rock Resolution: Fixed Status: Closed Reopened
[JIRA] (JENKINS-45419) 'Use Repository' setting does not find other remote urls if multiple repos are added to job
Title: Message Title Boguslaw Klimas resolved as Fixed release 0.9.5 Jenkins / JENKINS-45419 'Use Repository' setting does not find other remote urls if multiple repos are added to job Change By: Boguslaw Klimas Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45419) 'Use Repository' setting does not find other remote urls if multiple repos are added to job
Title: Message Title Boguslaw Klimas commented on JENKINS-45419 Re: 'Use Repository' setting does not find other remote urls if multiple repos are added to job I released plugin version 0.9.5 and I've updated the wiki page. Please look on section https://wiki.jenkins.io/display/JENKINS/Git+Parameter+Plugin#GitParameterPlugin-Userepository 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-50510) use repository settings dublicates branch listing
Title: Message Title Boguslaw Klimas resolved as Fixed release 0.9.5 Jenkins / JENKINS-50510 use repository settings dublicates branch listing Change By: Boguslaw Klimas Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50510) use repository settings dublicates branch listing
Title: Message Title Boguslaw Klimas commented on JENKINS-50510 Re: use repository settings dublicates branch listing I released plugin version 0.9.5 and I've updated the wiki page. Please look on section https://wiki.jenkins.io/display/JENKINS/Git+Parameter+Plugin#GitParameterPlugin-Userepository 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-51041) git-parameter-plugin: Tags are duplicated in pipeline
Title: Message Title Boguslaw Klimas resolved as Fixed Release 0.9.5 Jenkins / JENKINS-51041 git-parameter-plugin: Tags are duplicated in pipeline Change By: Boguslaw Klimas Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51041) git-parameter-plugin: Tags are duplicated in pipeline
Title: Message Title Boguslaw Klimas commented on JENKINS-51041 Re: git-parameter-plugin: Tags are duplicated in pipeline I released plugin version 0.9.5 and I've updated the wiki page. Please look on section https://wiki.jenkins.io/display/JENKINS/Git+Parameter+Plugin#GitParameterPlugin-Userepository 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-53710) Update site signature validation fails on Java 11
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-53710 Update site signature validation fails on Java 11 Change By: Daniel Beck SHA- 256 512 signature check and potentially others fail on Java 11. 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-53720) JDK11 Build Flow: FindBugs fails with RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE on some classes
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-53720 JDK11 Build Flow: FindBugs fails with RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE on some classes Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-09-21 21:10 Priority: Minor Reporter: Oleg Nenashev It seems FindBugs does not 100% support Java 11 code generation. RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE is displayed randomly for the code which is okay in JDK8. [INFO] --- findbugs-maven-plugin:3.0.5:check (findbugs) @ cli --- [INFO] BugInstance size is 3 [INFO] Error size is 0 [INFO] Total bugs: 3 [INFO] Nullcheck of channel at line 112 of value previously dereferenced in hudson.cli.SSHCLI.sshConnection(String, String, List, PrivateKeyProvider, boolean) [hudson.cli.SSHCLI, hudson.cli.SSHCLI] At SSHCLI.java:[line 112]Redundant null check at SSHCLI.java:[line 127] RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE [INFO] Nullcheck of client at line 99 of value previously dereferenced in hudson.cli.SSHCLI.sshConnection(String, String, List, PrivateKeyProvider, boolean) [hudson.cli.SSHCLI, hudson.cli.SSHCLI] At SSHCLI.java:[line 99]Redundant null check at SSHCLI.java:[line 131] RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE [INFO] Nullcheck of session at line 109 of value previously dereferenced in hudson.cli.SSHCLI.sshConnection(String, String, List, PrivateKeyProvider, boolean) [hudson.cli.SSHCLI, hudson.cli.SSHCLI] At SSHCLI.java:[line 109]Redundant null check at SSHCLI.java:[line 128] RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE [INFO]
[JIRA] (JENKINS-50458) JNLP agent died while reconnecting to master with java.lang.ClassNotFoundException: jenkins.slaves.restarter.JnlpSlaveRestarterInstaller
Title: Message Title Ashton Treadway updated JENKINS-50458 Per Oleg Nenashev, closing as resolved with no response from submitter. Jenkins / JENKINS-50458 JNLP agent died while reconnecting to master with java.lang.ClassNotFoundException: jenkins.slaves.restarter.JnlpSlaveRestarterInstaller Change By: Ashton Treadway Status: Open Fixed but Unreleased 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-50575) Dash changed to underscore in custom prefix
Title: Message Title karan magdani updated an issue Jenkins / JENKINS-50575 Dash changed to underscore in custom prefix Change By: karan magdani When entering a custom prefix for InfluxDB that includes a dash the plugin is incorrectly substituting the dash for an underscore. This isn't necessary and is confusing if you're using the prefix to query the data. The AbstractPointGenerator is incorrectly passing the custom prefix to the measurementName() method. This isn't necessary, it's not being used in the measurement name but rather in the Prefix tag. Tag values can have underscore. !image-2018-04-04-09-11-05-147.png |width=702,height=448 ! 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-42413) java.lang.ClassNotFoundException leads to LinkerError on remote agent with jdk9
Title: Message Title Ashton Treadway updated JENKINS-42413 Jenkins / JENKINS-42413 java.lang.ClassNotFoundException leads to LinkerError on remote agent with jdk9 Change By: Ashton Treadway Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42413) java.lang.ClassNotFoundException leads to LinkerError on remote agent with jdk9
Title: Message Title Ashton Treadway updated JENKINS-42413 Jenkins / JENKINS-42413 java.lang.ClassNotFoundException leads to LinkerError on remote agent with jdk9 Change By: Ashton Treadway Status: Open Fixed but Unreleased Resolution: Duplicate 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-50575) Dash changed to underscore in custom prefix
Title: Message Title
karan magdani edited a comment on JENKINS-50575
Re: Dash changed to underscore in custom prefix
Why are we replacing the '-' to '_' ?I want to use custom prefix and keep the '-' {{"Tag values can have underscore."}}I think what Mandy meant was that if we want ' _ __ ' we can use underscore. Why does the code need to convert '-' to '_'
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-50575) Dash changed to underscore in custom prefix
Title: Message Title
karan magdani edited a comment on JENKINS-50575
Re: Dash changed to underscore in custom prefix
Why are we replacing the '-' to '_' ?I want to use custom prefix and keep the '-' {{"Tag values can have underscore."}}I think what Mandy meant was that if we want '__' we can use underscore. Why does the code need to convert '-' to ' _ __ '
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-50575) Dash changed to underscore in custom prefix
Title: Message Title
karan magdani edited a comment on JENKINS-50575
Re: Dash changed to underscore in custom prefix
Why are we replacing the '-' to '_' ?I want to use custom prefix and keep the '-' {{"Tag values can have underscore."}}I think what Mandy meant was that if we want '_' we can use underscore. Why does the code need to convert '-' to '_'
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-53718) Add instructions for remoting kafka global configuration
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-53718 Add instructions for remoting kafka global configuration Issue Type: Improvement Assignee: Pham Vu Tuan Components: remoting-kafka-plugin Created: 2018-09-21 19:31 Priority: Minor Reporter: Pham Vu Tuan 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-41272) Pipeline "currentBuild" should expose build causes
Title: Message Title Jesse Glick commented on JENKINS-41272 Re: Pipeline "currentBuild" should expose build causes Filed a sketch. 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-41272) Pipeline "currentBuild" should expose build causes
Title: Message Title Jesse Glick started work on JENKINS-41272 Change By: Jesse Glick 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-41272) Pipeline "currentBuild" should expose build causes
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-41272 Pipeline "currentBuild" should expose build causes Change By: Jesse Glick Assignee: Sam Van Oort Jesse Glick 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-49348) BlueOcean misses a button to re-run a build
Title: Message Title Brian Saville commented on JENKINS-49348 Re: BlueOcean misses a button to re-run a build James Dumay, this would be extremely helpful for us as well. We heavily use pipeline jobs, and modify them often through the Job DSL plugin. Since the re-run button currently does a replay, it will use the old pipeline script instead of the latest one. The rebuild plugin does some nice things as well such as maintain the same build parameters and causes. Causes are especially important to us because it can trigger different behavior based on what caused the build in the first place. IMHO, I think we should either have two buttons available in blue ocean - one for replay and one for rebuild, or, since the replay doesn't actually let you change the pipeline script yet through blue ocean (AFAIK) and the rebuild plugin truly redo the current build exactly as it was the first time, I vote that if the rebuild plugin is present, make the re-run button trigger a rebuild instead of a replay. I would prefer the latter since it prevents confusion, but would be a potentially breaking change for other users. 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-48420) Provide lightweight checkout capability for Subversion
Title: Message Title Philip Steiner commented on JENKINS-48420 Re: Provide lightweight checkout capability for Subversion Ivan Fernandez Calvo - I don't think there are any externals. The files all reside in the same subdirectory of the repository, and as far as I know, there are no external references (I am not an SVN expert). I have worked around the error for now by deselecting "Lightweight checkout" on all jobs that use these pipeline files. Forgive this question, I am just an end-user on this Jenkins master, with no admin access - where would I ask the sysadmin to set the property you suggested? Is that in a configuration file for the Jenkins master? 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-53717) Keep extension point inside the plugn
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-53717 Keep extension point inside the plugn Issue Type: Improvement Assignee: Abhishek Gautam Components: simple-pull-request-job-plugin Created: 2018-09-21 19:25 Priority: Minor Reporter: Pham Vu Tuan 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-53713) Pipeline as YAML Incubator Plugin 1.0-rc
Title: Message Title Pham Vu Tuan started work on JENKINS-53713 Change By: Pham Vu Tuan 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-53716) Core Build Flow: ysoserial tests cannot compile on JDK11, Corba was removed
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-53716 Core Build Flow: ysoserial tests cannot compile on JDK11, Corba was removed Change By: Oleg Nenashev Assignee: 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-53716) Core Build Flow: ysoserial tests cannot compile on JDK11, Corba was removed
Title: Message Title Oleg Nenashev started work on JENKINS-53716 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-53716) Core Build Flow: ysoserial tests cannot compile on JDK11, Corba was removed
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-53716 Core Build Flow: ysoserial tests cannot compile on JDK11, Corba was removed Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-09-21 19:23 Priority: Minor Reporter: Oleg Nenashev Subj, some tests depend on Corba, and they do not compile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53633) Remove pinned certificates
Title: Message Title Baptiste Mathus updated JENKINS-53633 Jenkins / JENKINS-53633 Remove pinned certificates Change By: Baptiste Mathus Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53595) Upgrade to jest 23+
Title: Message Title Baptiste Mathus updated JENKINS-53595 Jenkins / JENKINS-53595 Upgrade to jest 23+ Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53691) "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+
Title: Message Title Rick Liu commented on JENKINS-53691 Re: "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+ Thank you very much for such a prompt fix! Attached my job config.xml when using v0.17 plugin and v2.8.1 plugin. The solution works! 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-53691) "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-53691 "Execute script on Matrix" not working after upgraing from 0.18.1 to 1.0.0+ Change By: Rick Liu Attachment: config-0.17.xml Attachment: config-2.8.1.xml 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-53709) Parallel blocks in node blocks cause executors to be persisted outside of the node block
Title: Message Title Devin Nusbaum updated JENKINS-53709 Jenkins / JENKINS-53709 Parallel blocks in node blocks cause executors to be persisted outside of the node block Change By: Devin Nusbaum Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50575) Dash changed to underscore in custom prefix
Title: Message Title karan magdani commented on JENKINS-50575 Re: Dash changed to underscore in custom prefix Why are we replacing the '-' to '_' ? I want to use custom prefix and keep the '-' 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-53595) Upgrade to jest 23+
Title: Message Title Baptiste Mathus started work on JENKINS-53595 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-52941) Simple Pull Request Builder plugin needs to be updated to the new JCasC release candidate
Title: Message Title Martin d'Anjou updated JENKINS-52941 Jenkins / JENKINS-52941 Simple Pull Request Builder plugin needs to be updated to the new JCasC release candidate Change By: Martin d'Anjou Status: Fixed but Unreleased Resolved Resolution: Fixed Duplicate 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-52941) Simple Pull Request Builder plugin needs to be updated to the new JCasC release candidate
Title: Message Title Martin d'Anjou updated JENKINS-52941 Jenkins / JENKINS-52941 Simple Pull Request Builder plugin needs to be updated to the new JCasC release candidate Change By: Martin d'Anjou Status: Open Fixed but Unreleased 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-52519) Release 1.0-rc-1 version
Title: Message Title Martin d'Anjou updated an issue Jenkins / JENKINS-52519 Release 1.0-rc-1 version Change By: Martin d'Anjou Summary: Release 1.0 -rc-1 version 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-53715) Upgrade to configuration as code 1.0
Title: Message Title Martin d'Anjou created an issue Jenkins / JENKINS-53715 Upgrade to configuration as code 1.0 Issue Type: Story Assignee: Pham Vu Tuan Components: simple-pull-request-job-plugin Created: 2018-09-21 18:27 Priority: Minor Reporter: Martin d'Anjou Upgrade the pom.xml to use the 1.0 configuration as code plugin release. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53714) Pipeline as YAML Incubator Plugin Long Term Plan
Title: Message Title Pham Vu Tuan created an issue Jenkins / JENKINS-53714 Pipeline as YAML Incubator Plugin Long Term Plan Issue Type: Epic Assignee: Abhishek Gautam Components: simple-pull-request-job-plugin Created: 2018-09-21 18:26 Priority: Minor Reporter: Pham Vu Tuan 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-53713) Pipeline as YAML Incubator Plugin 1.0-rc
Title: Message Title Martin d'Anjou created an issue Jenkins / JENKINS-53713 Pipeline as YAML Incubator Plugin 1.0-rc Issue Type: Epic Assignee: Pham Vu Tuan Components: simple-pull-request-job-plugin Created: 2018-09-21 18:23 Priority: Minor Reporter: Martin d'Anjou Capture the list of issues that need to be resolved before the 1.0-rc release. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-52081) create an Epic for phase 3
Title: Message Title Oleg Nenashev closed an issue as Fixed Jenkins / JENKINS-52081 create an Epic for phase 3 Change By: Oleg Nenashev Status: In Progress Closed 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-52452) GSoC Phase 3 - Simple Pull Request Job plugin
Title: Message Title Oleg Nenashev closed an issue as Fixed Done Jenkins / JENKINS-52452 GSoC Phase 3 - Simple Pull Request Job plugin Change By: Oleg Nenashev Status: Open Closed 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-46636) `dir` does not change working directory for contained steps
Title: Message Title
Michael Slattery edited a comment on JENKINS-46636
Re: `dir` does not change working directory for contained steps
I was able to fix the issue by applying the following patch to [https://github.com/jenkinsci/docker-workflow-plugin], building the .hpi w/mvn, and placing it into my Jenkins server.{code:java}diff --git a/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java b/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.javaindex 862b454.. c2d6f5f efcb6b2 100644--- a/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java+++ b/src/main/java/org/jenkinsci/plugins/docker/workflow/WithContainerStep.java@@ -255 +255 ,2 @@ public class WithContainerStep extends AbstractStepImpl {- launcher.getListener().getLogger().println("Docker version is older than 17.12, working directory will be " + ws + " not " + path);+ String safePath = path.replace("'", "'\"'\"'");+ starter.cmds().addAll(0, Arrays.asList("sh", "-c", "cd '" + path safePath + "'; \"$@\"", "--")); {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-52663) Change the plugin name and the yaml file name for future compatibility
Title: Message Title Oleg Nenashev closed an issue as Fixed Jenkins / JENKINS-52663 Change the plugin name and the yaml file name for future compatibility Change By: Oleg Nenashev Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52663) Change the plugin name and the yaml file name for future compatibility
Title: Message Title Oleg Nenashev updated JENKINS-52663 Jenkins / JENKINS-52663 Change the plugin name and the yaml file name for future compatibility Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51153) GSoC: Community Bonding tasks for Simple Pull Request Job plugin
Title: Message Title Oleg Nenashev closed an issue as Fixed Jenkins / JENKINS-51153 GSoC: Community Bonding tasks for Simple Pull Request Job plugin Change By: Oleg Nenashev Status: Open Closed 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-52588) Create blog post for 1.0 SPRP release
Title: Message Title Oleg Nenashev closed an issue as Fixed The blogpost was published Jenkins / JENKINS-52588 Create blog post for 1.0 SPRP release Change By: Oleg Nenashev Status: In Progress Closed 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-51371) GSoC Phase 1 - Simple Pull request Job Project
Title: Message Title Oleg Nenashev closed an issue as Fixed Jenkins / JENKINS-51371 GSoC Phase 1 - Simple Pull request Job Project Change By: Oleg Nenashev Status: Open Closed 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-53711) Pipeline customWorkspace not obeyed in docker agent when reuseNode is true
Title: Message Title Ray Kivisto created an issue Jenkins / JENKINS-53711 Pipeline customWorkspace not obeyed in docker agent when reuseNode is true Issue Type: Bug Assignee: Andrew Bayer Attachments: Jenkinsfile.fail, Jenkinsfile.pass, log.fail, log.pass Components: pipeline-model-definition-plugin Created: 2018-09-21 17:57 Environment: Jenkins LTS 2.138.1 (fresh install) Plugins: I chose the "recommended Plugins" when I spun up this fresh instance, which gave me "Pipeline: Model API" 1.3.2 Mac OS X Java "1.8.0_151" Docker for Mac 18.06.1-ce Priority: Minor Reporter: Ray Kivisto When you use the 'customWorkspace' declarative Pipeline option in a docker agent, it is working correctly. (see attached Jenkinsfile.pass log.pass ) The problem I'm encountering is if you also add the 'reuseNode true' option for that docker agent, then the 'customWorkspace' option is no longer obeyed. (see Jenkinsfile.fail log.fail ) What happens is the stage runs in the same workspace as the previous stage (/Users/rkivisto/.jenkins/workspace/pipeline) which was not even run on the same agent (the first stage was run on the Master, the second stage is running in a container) You can see the error from the "sh 'pwd'" in the second stage, I would have expected both of these to be in '/Users/rkivisto/.jenkins/test', since the first stage was not run in the same agent as the second stage: diff log.pass log.fail ... < /Users/rkivisto/.jenkins/test — > /Users/rkivisto/.jenkins/workspace/pipeline
[JIRA] (JENKINS-53712) Jenkins context initialization should not complete until Jenkins is "ready to work"
Title: Message Title Jake Gage created an issue Jenkins / JENKINS-53712 Jenkins context initialization should not complete until Jenkins is "ready to work" Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-09-21 17:57 Priority: Minor Reporter: Jake Gage Recent changes to Jenkins seem to have made startup times longer, and have acerbated this issue, breaking several automations. However— this issue hopes to address a deeper problem with the startup sequence. The Jenkins initialization reports as completing, then other processes begin to make Jenkins "ready to work...". It's completely okay that these processes will take a while and that the Jenkins application is in-place before it's able to respond to Web service events, say. The problem comes when automations attempt to restart Jenkins, and presume that Jenkins has been restarted when the service reports as restarting. At a deep level, the Jenkins context reports initialization as complete before functionality is available. For the GUI user, we present a nice interface that clearly tells the user to wait. However, for anything relying on Jenkins, there is no cue differentiating Jenkins being "up" and "waiting to come up." Automations can wait for the service to start, but service wrapping report Jenkins as being started— in some cases many minutes before Jenkins is prepared to respond to any events. This issue proposes that this is a bug, and that the init() process should wait for dependent processes, and not return as complete until Jenkins is considered fit-for-use.
[JIRA] (JENKINS-52917) Update project page on jenkins.io for submission
Title: Message Title Oleg Nenashev updated JENKINS-52917 Jenkins / JENKINS-52917 Update project page on jenkins.io for submission Change By: Oleg Nenashev Status: Open Fixed but Unreleased 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-52917) Update project page on jenkins.io for submission
Title: Message Title Oleg Nenashev updated JENKINS-52917 Jenkins / JENKINS-52917 Update project page on jenkins.io for submission Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46636) `dir` does not change working directory for contained steps
Title: Message Title Michael Slattery updated an issue Jenkins / JENKINS-46636 `dir` does not change working directory for contained steps Change By: Michael Slattery Component/s: docker-workflow-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-53710) Update site signature validation fails on Java 11
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-53710 Update site signature validation fails on Java 11 Issue Type: Bug Assignee: Daniel Beck Components: core Created: 2018-09-21 17:40 Priority: Major Reporter: Daniel Beck SHA-256 signature check and potentially others fail on Java 11. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-31592) ACE Editor textarea should be resizable
Title: Message Title Senthil Nathan Sampath Kumar assigned an issue to Unassigned Jenkins / JENKINS-31592 ACE Editor textarea should be resizable Change By: Senthil Nathan Sampath Kumar Assignee: Senthil Nathan Sampath Kumar 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-31592) ACE Editor textarea should be resizable
Title: Message Title Senthil Nathan Sampath Kumar assigned an issue to Senthil Nathan Sampath Kumar Jenkins / JENKINS-31592 ACE Editor textarea should be resizable Change By: Senthil Nathan Sampath Kumar Assignee: Senthil Nathan Sampath Kumar 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-28822) Can't distinguish between durable task abort and failure in workflow plugin
Title: Message Title Devin Nusbaum commented on JENKINS-28822 Re: Can't distinguish between durable task abort and failure in workflow plugin I am working on this in https://github.com/jenkinsci/workflow-durable-task-step-plugin/pull/75. My main concern is whether fixing it now will break all of the workarounds the people are currently using, so I want to do a few tests with some of the workarounds posted here to get an idea of the impact. 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-26138) Support workspaces for Pipeline jobs
Title: Message Title Jesse Glick updated JENKINS-26138 Jenkins / JENKINS-26138 Support workspaces for Pipeline jobs Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs
Title: Message Title Jesse Glick commented on JENKINS-26138 Re: Support workspaces for Pipeline jobs Filed PR with a basic display for classic UI. 2015-09-11 comments, as well as some miscellaneous fixes such as adding a wipe out workspace link, need to be refiled as separate issues, but I think this captures the most common and obvious request. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52099) jenkins-cli requires Overall/Read permission on anonymous user
Title: Message Title
Eric Blackburn edited a comment on JENKINS-52099
Re: jenkins-cli requires Overall/Read permission on anonymous user
I had a similar issue with an error message stating "ERROR: anonymous is missing the Overall/Read permission" when trying to create a slave or perform any cli cmds. Turns out I needed to update to use a different authentication process that the CLI offers. For example, change the command {code:java}java -jar /usr/local/bin/jenkins-cli.jar -logger FINE -s http://localhost:8080 -noKeyAuth connect-node containers-medium --username exampleuser --password examplepass{code}to use the auth parameter{code:java}-auth username:password{code}So that your command ends up being{code:java}java -jar /usr/local/bin/jenkins-cli.jar -logger FINE -s http://localhost:8080 -auth exampleuser:examplepass connect-node containers-medium{code}I don't think the -noKeyAuth parameter is needed, but I could be wrong about that.
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-52099) jenkins-cli requires Overall/Read permission on anonymous user
Title: Message Title Eric Blackburn commented on JENKINS-52099 Re: jenkins-cli requires Overall/Read permission on anonymous user I had a similar issue with an error message stating "ERROR: anonymous is missing the Overall/Read permission" when trying to create a slave or perform any cli cmds. Turns out I needed to update to use a different authentication process that the CLI offers. For example, change the command java -jar /usr/local/bin/jenkins-cli.jar -logger FINE -s http://localhost:8080 -noKeyAuth connect-node containers-medium --username exampleuser --password examplepass to use the auth parameter -auth username:password So that your command ends up being java -jar /usr/local/bin/jenkins-cli.jar -logger FINE -s http://localhost:8080 -auth exampleuser:examplepass connect-node containers-medium I don't think the -noKeyAuth parameter is needed, but I could be wrong about that. 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
[JIRA] (JENKINS-53709) Parallel blocks in node blocks cause executors to be persisted outside of the node block
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-53709
Parallel blocks in node blocks cause executors to be persisted outside of the node block
Change By:
Devin Nusbaum
When a {{parallel}} step is nested in a {{node}} step, the executor associated with the node appears to outlive both the {{parallel}} and {{node}} steps. This leads to the executor being rehydrated when a pipeline is restarted, even if the pipeline is outside of the node block. Reproduction test case:{code}@Test public void shouldNotLeakExecutorsViaContextVars() {story.then(r -> {DumbSlave s = r.createOnlineSlave();WorkflowJob p = r.jenkins.createProject(WorkflowJob.class, "demo");p.setDefinition(new CpsFlowDefinition("node('" + s.getNodeName() + "') {\n" +" parallel one: {\n" +"echo '" + s.getNodeName() + "'\n" +" }\n" +"}\n" +"semaphore 'wait'\n", false));WorkflowRun b = p.scheduleBuild2(0).waitForStart();SemaphoreStep.waitForStart("wait/1", b);r.jenkins.removeNode(s);});story.then(r -> {WorkflowRun b = r.jenkins.getItemByFullName("demo", WorkflowJob.class).getBuildByNumber(1);SemaphoreStep.waitForStart("wait/1", b);SemaphoreStep.success("wait/1", null);while (b.isBuilding()) {r.assertLogNotContains("Jenkins doesn’t have label", b);Thread.sleep(100);}r.assertBuildStatusSuccess(b);});}{code}This test currently fails because the pipeline waits for the 'Test' agent to become available after restarting even though we are not in a node block. From a quick investigation, I think this may have been introduced by JENKINS-26034 ([commit|https://github.com/jenkinsci/workflow-cps-plugin/commit/c8c668f2b60a19c33add92e2b14345f23f58aabc]), because if I remove [ResultHandler.stepExecution|https://github.com/jenkinsci/workflow-cps-plugin/blob/54d2f4fe8069fde53789bfe21229ce8e545300bb/src/main/java/org/jenkinsci/plugins/workflow/cps/steps/ParallelStep.java#L70], the test case passes successfully. I'm not sure if we shouldn't be persisting the execution there, or if we need to clear it out after the step completes, or if the persistence is fine and the root problem is somewhere else.
[JIRA] (JENKINS-53709) Parallel blocks in node blocks cause executors to be persisted outside of the node block
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-53709
Parallel blocks in node blocks cause executors to be persisted outside of the node block
Change By:
Devin Nusbaum
When a {{parallel}} step is nested in a {{node}} step, the executor associated with the node appears to outlive both the {{parallel}} and {{node}} steps. This leads to the executor being rehydrated when a pipeline is restarted, even if the pipeline is outside of the node block. Reproduction test case:{code}@Test public void shouldNotLeakExecutorsViaContextVars() {story.then(r -> {DumbSlave s = r.createOnlineSlave();WorkflowJob p = r.jenkins.createProject(WorkflowJob.class, "demo");p.setDefinition(new CpsFlowDefinition("node('" + s.getNodeName() + "') {\n" +" parallel one: {\n" +"echo '" + s.getNodeName() + "'\n" +" }\n" +"}\n" +"semaphore 'wait'\n", false));WorkflowRun b = p.scheduleBuild2(0).waitForStart();SemaphoreStep.waitForStart("wait/1", b);r. disconnectSlave jenkins.removeNode (s);});story.then(r -> {WorkflowRun b = r.jenkins.getItemByFullName("demo", WorkflowJob.class).getBuildByNumber(1);SemaphoreStep.waitForStart("wait/1", b);SemaphoreStep.success("wait/1", null);while (b.isBuilding()) {r.assertLogNotContains(" is offline Jenkins doesn’t have label ", b);Thread.sleep(100);}r.assertBuildStatusSuccess(b);});}{code}This test currently fails because the pipeline waits for the 'Test' agent to become available after restarting even though we are not in a node block.From a quick investigation, I think this may have been introduced by JENKINS-26034 ([commit|https://github.com/jenkinsci/workflow-cps-plugin/commit/c8c668f2b60a19c33add92e2b14345f23f58aabc]), because if I remove [ResultHandler.stepExecution|https://github.com/jenkinsci/workflow-cps-plugin/blob/54d2f4fe8069fde53789bfe21229ce8e545300bb/src/main/java/org/jenkinsci/plugins/workflow/cps/steps/ParallelStep.java#L70], the test case passes successfully. I'm not sure if we shouldn't be persisting the execution there, or if we need to clear it out after the step completes, or if the persistence is fine and the root problem is somewhere else.
[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-26138 Support workspaces for Pipeline jobs Change By: Jesse Glick Component/s: workflow-support-plugin Component/s: workflow-durable-task-step-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-26138) Support workspaces for Pipeline jobs
Title: Message Title Jesse Glick started work on JENKINS-26138 Change By: Jesse Glick 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.
