[JIRA] (JENKINS-55068) Multibranch scanning deletes jobs if bitbucket server goes away during scan
Title: Message Title
Patrick Ruckstuhl commented on JENKINS-55068
Re: Multibranch scanning deletes jobs if bitbucket server goes away during scan
I think I found the issue in the code, in BitbucketServerAPIClient.java
@Override
public boolean checkPathExists(@NonNull String branchOrHash, @NonNull String path) throws IOException {
String url = ""
.fromTemplate(API_BROWSE_PATH)
.set("owner", getUserCentricOwner())
.set("repo", repositoryName)
.set("path", path.split(Operator.PATH.getSeparator()))
.set("at", branchOrHash)
.expand();
int status = getRequestStatus(url);
return HttpStatus.SC_OK == status;
}
This looks wrong as it will always just return that the path does not exist even if it's a "real" error instead of the info that the path does not exist.
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-51282) Azure VM plugin log is too chatty
Title: Message Title Jie Shen started work on JENKINS-51282 Change By: Jie Shen 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-51282) Azure VM plugin log is too chatty
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-51282 Azure VM plugin log is too chatty Change By: Jie Shen Assignee: Chenyang Liu Jie Shen 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-51282) Azure VM plugin log is too chatty
Title: Message Title Jie Shen commented on JENKINS-51282 Re: Azure VM plugin log is too chatty Need discussion whether we should change some periodic tasks' log level to do not log these start/end log. There are still considerable count of them. 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-55028) Jenkins considers build as success even if tower plugin fails
Title: Message Title Lukas Tischler commented on JENKINS-55028 Re: Jenkins considers build as success even if tower plugin fails Hi! Have you tried to add throwExceptionWhenFail: true to the ansibleTower step? Actually it should be true when nothing is specified. 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-51282) Azure VM plugin log is too chatty
Title: Message Title Jie Shen commented on JENKINS-51282 Re: Azure VM plugin log is too chatty This issue is caused by periodic work of this plugin. And PR 107 should have mitigated this issue by increasing the recurrence period time from 1 min to 5 min. 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-55068) Multibranch scanning deletes jobs if bitbucket server goes away during scan
Title: Message Title Patrick Ruckstuhl created an issue Jenkins / JENKINS-55068 Multibranch scanning deletes jobs if bitbucket server goes away during scan Issue Type: Bug Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-12-07 07:08 Priority: Critical Reporter: Patrick Ruckstuhl There is an issue with the bitbucket multibranch scanning if bitbucket goes away during the scan as this is not detected as an error case and instead the branches/jobs are considered as no longer existing and are therefore deleted (and new jobs triggered on the next scan when bitbucket server is back). It seems that the multibranch scanning works in two "phases". First phase is to find all the branches, if bitbucket is already offline during that time, everything is fine as it will just fail the scanning and not update any jobs. The problem is if bitucket is online during that time. So it finds out all the branches. Now in the second phase, each branch is checked for the Jenkinsfile. Now if during that phase bitbucket is offline, it's not resulting in an error, it's instead resulting in a "Jenkinsfile" not found which will then delete that job. Add Comment
[JIRA] (JENKINS-54936) 0.30 version not yet released for Github Authentication Plugin
Title: Message Title Sam Gleske updated JENKINS-54936 Jenkins / JENKINS-54936 0.30 version not yet released for Github Authentication Plugin Change By: Sam Gleske Status: Open Fixed but Unreleased Resolution: Fixed Released As: github-oauth-0.31 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54936) 0.30 version not yet released for Github Authentication Plugin
Title: Message Title Sam Gleske commented on JENKINS-54936 Re: 0.30 version not yet released for Github Authentication Plugin Hi 0.30 was a security release and did not include the changes which were unreleased in master at the time that you opened this issue. However, 0.31 was released a few minutes ago which contains a few fixes plus the user cache changes which were formerly unreleased. 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-54936) 0.30 version not yet released for Github Authentication Plugin
Title: Message Title Sam Gleske updated JENKINS-54936 Jenkins / JENKINS-54936 0.30 version not yet released for Github Authentication Plugin Change By: Sam Gleske 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-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Sam Gleske updated an issue Jenkins / JENKINS-54031 GitHub OAuth plugin fails with Jenkins 2.146 Change By: Sam Gleske Released As: github-oauth- 0.31 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Sam Gleske updated JENKINS-54031 Jenkins / JENKINS-54031 GitHub OAuth plugin fails with Jenkins 2.146 Change By: Sam Gleske Status: Fixed but Unreleased Resolved Released As: 0.31 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Sam Gleske commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 A few minutes ago I released 0.31 which includes https://github.com/jenkinsci/github-oauth-plugin/pull/103. This should be resolved. Please re-open if not. 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-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Sam Gleske updated JENKINS-54031 Jenkins / JENKINS-54031 GitHub OAuth plugin fails with Jenkins 2.146 Change By: Sam Gleske 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-55067) ClassNotFoundException: org.jvnet.hudson.maven3.listeners.MavenProjectInfo is occurring again in 3.2
Title: Message Title Mohammad Rajibul Alam Joarder updated an issue Jenkins / JENKINS-55067 ClassNotFoundException: org.jvnet.hudson.maven3.listeners.MavenProjectInfo is occurring again in 3.2 Change By: Mohammad Rajibul Alam Joarder Attachment: 2018-12-07_151857.jpg 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-55067) ClassNotFoundException: org.jvnet.hudson.maven3.listeners.MavenProjectInfo is occurring again in 3.2
Title: Message Title Mohammad Rajibul Alam Joarder created an issue Jenkins / JENKINS-55067 ClassNotFoundException: org.jvnet.hudson.maven3.listeners.MavenProjectInfo is occurring again in 3.2 Issue Type: Bug Assignee: Unassigned Components: maven-plugin Created: 2018-12-07 06:23 Priority: Major Reporter: Mohammad Rajibul Alam Joarder I updated my Jenkins with Maven Integration Plugin 3.2 and it starts giving following error randomly ClassNotFoundException: org.jvnet.hudson.maven3.listeners.MavenProjectInfo Once I downgrade to 3.1.2 its again start working all my job perfectly Jenkins version 2.154 Add Comment
[JIRA] (JENKINS-54973) Not able to generate build With Xcode 10
Title: Message Title Kazuhide Takahashi commented on JENKINS-54973 Re: Not able to generate build With Xcode 10 If you are doing the code signature of the Xcode project automatically, you have to register Apple Developer Account to the node and account you are using for building with Jenkins. If this problem happens only in Xcode 10 and not in Xcode 9 etc, I think it is due to another cause, so please let me know at that time. Anyhow, it is difficult to give further advice to the there are no detailed situations to reproduce or the projects for reproduction. 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-55066) Docker plugin erroneously terminates containers shortly after they start
Title: Message Title
Owen Mehegan updated an issue
Jenkins / JENKINS-55066
Docker plugin erroneously terminates containers shortly after they start
Change By:
Owen Mehegan
We are seeing an issue where Pipeline jobs using Docker agents (with the Docker plugin, as opposed to Docker containers on regular agents using Pipeline's Docker support) intermittently fail right at the start, during the initial git checkout, with a "FATAL: java.io.IOException: Unexpected termination of the channel" exception. Having enabled debug logging for the Docker plugin, it appears that the plugin is erroneously killing the container because it thinks it is no longer needed.Job log:{noformat}[First few lines redacted, this is the Jenkinsfile checkout]Checking out Revision 0b45f687992585a470e5faf003309b215e3f74f1 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 0b45f687992585a470e5faf003309b215e3f74f1FATAL: java.io.IOException: Unexpected termination of the channeljava.io.EOFExceptionat java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2679)at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3154)at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)at java.io.ObjectInputStream.(ObjectInputStream.java:358)at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)at hudson.remoting.Command.readFrom(Command.java:140)at hudson.remoting.Command.readFrom(Command.java:126)at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)Caused: java.io.IOException: Unexpected termination of the channelat hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to docker-2ae12755b75761at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)at hudson.remoting.Request.call(Request.java:202)at hudson.remoting.Channel.call(Channel.java:954)at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)at com.sun.proxy.$Proxy118.withRepository(Unknown Source)at org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:235)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)
[JIRA] (JENKINS-55066) Docker plugin erroneously terminates containers shortly after they start
Title: Message Title
Owen Mehegan updated an issue
Jenkins / JENKINS-55066
Docker plugin erroneously terminates containers shortly after they start
Change By:
Owen Mehegan
We are seeing an issue where Pipeline jobs using Docker agents (with the Docker plugin, as opposed to Docker containers on regular agents using Pipeline's Docker support) intermittently fail right at the start, during the initial git checkout, with a "FATAL: java.io.IOException: Unexpected termination of the channel" exception. Having enabled debug logging for the Docker plugin, it appears that the plugin is erroneously killing the container because it thinks it is no longer needed.Job log:{noformat}[First few lines redacted, this is the Jenkinsfile checkout]Checking out Revision 0b45f687992585a470e5faf003309b215e3f74f1 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 0b45f687992585a470e5faf003309b215e3f74f1FATAL: java.io.IOException: Unexpected termination of the channeljava.io.EOFExceptionat java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2679)at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3154)at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862)at java.io.ObjectInputStream.(ObjectInputStream.java:358)at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49)at hudson.remoting.Command.readFrom(Command.java:140)at hudson.remoting.Command.readFrom(Command.java:126)at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36)at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)Caused: java.io.IOException: Unexpected termination of the channelat hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to docker-2ae12755b75761at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)at hudson.remoting.Request.call(Request.java:202)at hudson.remoting.Channel.call(Channel.java:954)at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)at com.sun.proxy.$Proxy118.withRepository(Unknown Source)at org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:235)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)
[JIRA] (JENKINS-55066) Docker plugin erroneously terminates containers shortly after they start
Title: Message Title Owen Mehegan created an issue Jenkins / JENKINS-55066 Docker plugin erroneously terminates containers shortly after they start Issue Type: Bug Assignee: Nicolas De Loof Components: docker-plugin Created: 2018-12-07 05:04 Priority: Major Reporter: Owen Mehegan We are seeing an issue where Pipeline jobs using Docker agents (with the Docker plugin, as opposed to Docker containers on regular agents using Pipeline's Docker support) intermittently fail right at the start, during the initial git checkout, with a "FATAL: java.io.IOException: Unexpected termination of the channel" exception. Having enabled debug logging for the Docker plugin, it appears that the plugin is erroneously killing the container because it thinks it is no longer needed. Job log: [First few lines redacted, this is the Jenkinsfile checkout] Checking out Revision 0b45f687992585a470e5faf003309b215e3f74f1 (refs/remotes/origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 0b45f687992585a470e5faf003309b215e3f74f1 FATAL: java.io.IOException: Unexpected termination of the channel java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2679) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3154) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862) at java.io.ObjectInputStream.(ObjectInputStream.java:358) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at
[JIRA] (JENKINS-45455) Restarting stages
Title: Message Title Jay Spang commented on JENKINS-45455 Re: Restarting stages Jan Hoppe Andrew Bayer please update this thread if you created a ticket to disable stage restart. We desperately need this. This feature does not work at all with my pipelines (it does not run on the same node as the original run), so it's generating false positives and wreaking havoc with my customers. I'm considering implementing some custom CSS to hide the silly thing before it causes us any more grief! 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-47077) "Periodically if not otherwise run" interval does not trigger index scan
Title: Message Title Derek Sudduth commented on JENKINS-47077 Re: "Periodically if not otherwise run" interval does not trigger index scan Stephen Connolly, I noticed this was marked as resolved. There are no comments regarding the fix or release. Do you know when we can expect to pick up the new plugin version? And what that version will be? Thanks in advance! Derek 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-54031) GitHub OAuth plugin fails with Jenkins 2.146
Title: Message Title Daniel Lo Nigro commented on JENKINS-54031 Re: GitHub OAuth plugin fails with Jenkins 2.146 Are there any workarounds that don't cause security 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-55065) Support a fallback/backup auth mechanism
Title: Message Title Owen Mehegan created an issue Jenkins / JENKINS-55065 Support a fallback/backup auth mechanism Issue Type: New Feature Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2018-12-07 03:31 Priority: Minor Reporter: Owen Mehegan When Jenkins is configured with SAML authentication, general access to Jenkins from a stand-alone Windows client that is not "logged in" locally is impossible. Because there is no local login session for Jenkins/SAML to use, Jenkins just shows an error. It would be ideal if, when Jenkins was configured this way, it could optionally fall back to another auth mechanism, such as the local Jenkins user DB. The specific use case we're thinking of is when Jenkins build status or dashboards are displayed on a TV for general viewing, using a stand-alone PC. These systems often are not joined to a corporate LDAP server for security reasons. Add Comment
[JIRA] (JENKINS-34313) Exceptions by parallel SCM checkout
Title: Message Title Aaron Dietz commented on JENKINS-34313 Re: Exceptions by parallel SCM checkout @Shannon Kerr Have you also tried the lock method from my approach above? Acquire a singleton lock "execution end" (or a nicer name ) at the end of the execution and release it instandly. This way no execution can end in parallel. Next escalation step is to add a minimal delay before you release the lock. Definitely not pretty, but fixes it for me 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-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Mike Bolesta commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step I'm also seeing this issue when the triggered build is inside a parallel stage. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55064) Pipeline stages display garbage when skipped
Title: Message Title
Abhijit Sarkar created an issue
Jenkins / JENKINS-55064
Pipeline stages display garbage when skipped
Issue Type:
Bug
Assignee:
Matthew DeTullio
Attachments:
pipeline.png
Components:
multi-branch-project-plugin (not Pipeline), pipeline-stage-view-plugin
Created:
2018-12-07 01:48
Environment:
CentOS 7.5, Jenkins ver. 2.153
Priority:
Major
Reporter:
Abhijit Sarkar
Given a stage
stage("Deploy") {
when {
allOf {
_expression_ { "$DEPLOYABLE_BRANCH".toBoolean() }
_expression_ { sh(script: "$GRADLE_CMD -q tasks --all | grep -q -w deploy", returnStatus: true) == 0 }
}
}
steps {
sh "$GRADLE_CMD deploy"
}
}
When the stage is skipped, pipeline views shows garbage text instead of time (see attachment). Instead, it should indicate that the stage is skipped.
[JIRA] (JENKINS-55063) Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Title: Message Title
Christopher Tindall updated an issue
Jenkins / JENKINS-55063
Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Change By:
Christopher Tindall
Not entirely clear to me how to use recordIssues when using a Custom Parser based on my reading of the Warnings documentation here: [ https://github.com/jenkinsci/warnings-plugin/blob/master/doc/Documentation.md ] Presumably I'm simply misunderstanding how to use the Custom Parser in a pipeline, and nothing is actually broken. However, I'm reasonably sure that there are likely others like me who are failing or who would fail, to understand the right way to do this.Jenkinsfile:{code:java}stage('Static Analysis') {steps {sh 'luacheck -d --no-max-line-length --no-global --formatter TAP ./bsmtpd/modules/*.lua > ./static_analysis_junit.xml || true'recordIssues tools: [[pattern: 'static_analysis_junit.xml', tool: [$class: 'luacheck']]]}}{code} Jenkins -> configuration -> Groovy Based Warnings Parsers: <– (This location should possibly be made more explicit in documentation.)!image-2018-12-06-17-05-08-306.png! I've run the Jenkinsfile with a whole mess of different possible configuration for the recordIssues line, and been unable to find anything that works. Most return simply:!image-2018-12-06-17-08-01-006.png!Cheers
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55063) Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Title: Message Title
Christopher Tindall created an issue
Jenkins / JENKINS-55063
Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.
Issue Type:
Improvement
Assignee:
Ulli Hafner
Attachments:
image-2018-12-06-17-05-08-306.png, image-2018-12-06-17-08-01-006.png
Components:
warnings-ng-plugin
Created:
2018-12-07 01:13
Priority:
Minor
Reporter:
Christopher Tindall
Not entirely clear to me how to use recordIssues when using a Custom Parser based on my reading of the Warnings documentation here: [https://github.com/jenkinsci/warnings-plugin/blob/master/doc/Documentation.md ] Presumably I'm simply misunderstanding how to use the Custom Parser in a pipeline, and nothing is actually broken. However, I'm reasonably sure that there are likely others like me who are failing or who would fail, to understand the right way to do this. Jenkinsfile:
stage('Static Analysis') {
steps {
sh 'luacheck -d --no-max-line-length --no-global --formatter TAP ./bsmtpd/modules/*.lua > ./static_analysis_junit.xml || true'
recordIssues tools: [[pattern: 'static_analysis_junit.xml', tool: [$class: 'luacheck']]]
}
}
Jenkins -> configuration -> Groovy Based Warnings Parsers: <– (This location should possibly be made more explicit in documentation.) I've run the Jenkinsfile with a whole mess of different possible configuration for the recordIssues line, and been unable to find
[JIRA] (JENKINS-55059) pluginmanager shows Update information obtained: N/A ago
Title: Message Title Josh Soref commented on JENKINS-55059 Re: pluginmanager shows Update information obtained: N/A ago I assume it just hasn't had time to check. My complaint is purely about the display, it should special case N/A and give a distinct string. 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-50558) Valgrind plugin results error
Title: Message Title Achal Shah commented on JENKINS-50558 Re: Valgrind plugin results error Any update on this issue? 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-27548) Sporadic IOException: Failed to persist config
Title: Message Title Ulli Hafner commented on JENKINS-27548 Re: Sporadic IOException: Failed to persist config In the new beta of the warnings-ng plugin a warning is now logged if your system has a non empty sax parser property. Can you please check the log output on your system if there is such a warning? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55053) Jenkins init script does not stop jenkins if JENKINS_HOME not found
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-55053 Jenkins init script does not stop jenkins if JENKINS_HOME not found Change By: Daniel Beck Component/s: packaging Component/s: core 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-55059) pluginmanager shows Update information obtained: N/A ago
Title: Message Title Daniel Beck commented on JENKINS-55059 Re: pluginmanager shows Update information obtained: N/A ago Anything in the Jenkins system log? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-4995) Support windows AMI's in EC2 plugin
Title: Message Title
Ian Ellis edited a comment on JENKINS-4995
Re: Support windows AMI's in EC2 plugin
Managed to get my windows jenkins agent online :){code:java}PS C:\Users\Administrator> Disable- WSManCredSSPcmdlet Disable- WSManCredSSP at command pipeline position 1Supply values for the following parameters: - Role : Server Client PS C:\Users\Administrator> Disable- WSManCredSSPcmdlet Disable- WSManCredSSP at command pipeline position 1Supply values for the following parameters: - Role : Client Server {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-4995) Support windows AMI's in EC2 plugin
Title: Message Title Ian Ellis commented on JENKINS-4995 Re: Support windows AMI's in EC2 plugin Managed to get my windows jenkins agent online PS C:\Users\Administrator> Disable-WSManCredSSPcmdlet Disable-WSManCredSSP at command pipeline position 1 Supply values for the following parameters: Role: Server PS C:\Users\Administrator> Disable-WSManCredSSPcmdlet Disable-WSManCredSSP at command pipeline position 1 Supply values for the following parameters: Role: Client 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-54700) Findbugs SAXParser not found
Title: Message Title Ulli Hafner commented on JENKINS-54700 Re: Findbugs SAXParser not found I added Xerces again (now 2.11.0). Actually I still do not know who actually is changing the sax parser property, so this is only a workaround for a problem somewhere else (other plugin, configuration?). A warning is now logged if your system has a non empty sax parser property (see commit#c1b80e6. Can you please check the log output on your system? 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-55062) Restarting (and likely loading) screen is missing assets if prefixed infront of proxy
Title: Message Title Gavin Mogan updated an issue Jenkins / JENKINS-55062 Restarting (and likely loading) screen is missing assets if prefixed infront of proxy Change By: Gavin Mogan When restarting a jenkins server (/restart), the static assets (such as css/js) are not prefixed, so if jenkins is sitting infront of behind a proxy server, the assets are not coming from the right place.This appears to work fine in standalone mode (java -jar war), but I'm not sure why. Looks like the jelly files reference resURL, but resURL is undefined for the restarting template. 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-55062) Restarting (and likely loading) screen is missing assets if prefixed infront of proxy
Title: Message Title Gavin Mogan commented on JENKINS-55062 Re: Restarting (and likely loading) screen is missing assets if prefixed infront of proxy ... yes, if a proxy server is in front of it or it is behind a proxy server Silly gavin 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-55062) Restarting (and likely loading) screen is missing assets if prefixed infront of proxy
Title: Message Title Daniel Beck commented on JENKINS-55062 Re: Restarting (and likely loading) screen is missing assets if prefixed infront of proxy if jenkins is sitting infront of a proxy server Behind a proxy server? 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-4995) Support windows AMI's in EC2 plugin
Title: Message Title Ian Ellis commented on JENKINS-4995 Re: Support windows AMI's in EC2 plugin Getting the "java.lang.IllegalStateException: Unsupported authentication scheme: CredSSP" error message as well. Haven't used the EC2 agent for windows agents for last month or so, but it was working perfectly before that. Can RDP and WinRM in to the Windows agent that it spun up from my develop machine and our linux jenkins master. The agent just doesn't come on line, and we get the infinitely repeated "Waiting for WinRM to come up. Sleeping 10s." message. Can't find any corresponding logs on the Windows machine (don't you love :ms. I think the last time we used the ec2 agent plugin we were using 1.39, so I'm guessing 1.40 or 1.41 have broken it? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Ulli Hafner commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" Yes, this is the only reason. FindBugs uses XMLReaderFactory to obtain a parser. Normally this is the JDK parser. However, someone (plugin, system configuration, container, etc.?) seems to override one of the SAX settings (system property or Service Locator) and defines Xerces as default. 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-55062) Restarting (and likely loading) screen is missing assets if prefixed infront of proxy
Title: Message Title Gavin Mogan started work on JENKINS-55062 Change By: Gavin Mogan 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-55062) Restarting (and likely loading) screen is missing assets if prefixed infront of proxy
Title: Message Title Gavin Mogan commented on JENKINS-55062 Re: Restarting (and likely loading) screen is missing assets if prefixed infront of proxy https://github.com/jenkinsci/jenkins/pull/3793 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-49337) GeneralNonBlockingStepExecution (was: InterruptedException from step tail call)
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-49337 GeneralNonBlockingStepExecution (was: InterruptedException from step tail call) Change By: Cyrille Le Clerc Attachment: pipeline-maven-3.6.5-SNAPSHOT-JENKINS-49337.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-49337) GeneralNonBlockingStepExecution (was: InterruptedException from step tail call)
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-49337 GeneralNonBlockingStepExecution (was: InterruptedException from step tail call) Change By: Cyrille Le Clerc Attachment: workflow-step-api-2.17-rc491.f7bec8d9dc29.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-49337) GeneralNonBlockingStepExecution (was: InterruptedException from step tail call)
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-49337 GeneralNonBlockingStepExecution (was: InterruptedException from step tail call) Change By: Cyrille Le Clerc Assignee: Cyrille Le Clerc 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-49337) GeneralNonBlockingStepExecution (was: InterruptedException from step tail call)
Title: Message Title Cyrille Le Clerc commented on JENKINS-49337 Re: GeneralNonBlockingStepExecution (was: InterruptedException from step tail call) Vincent Massol could you test the fix installing the versions attached here: pipeline-maven-3.6.5-SNAPSHOT-JENKINS-49337.hpi workflow-step-api-2.17-rc491.f7bec8d9dc29.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-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Cyrille Le Clerc commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" > I released findbugs-5.0.0-beta3 now, that contains the findbugs library with Xerces 2.11.0. Thanks Ulli Hafner! > Note: It would still be quite helpful to find the actual plugin (or tool?) that sets the sax property globally! I added some logging to the warnings plugin now to see if the sax property has been altered. I am not aware of such problem. Is it the reason why you import Xerces in the findbugs 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-34313) Exceptions by parallel SCM checkout
Title: Message Title Shannon Kerr commented on JENKINS-34313 Re: Exceptions by parallel SCM checkout This is killing us today. So man occurrences. More than 50% of our builds. The recommended "sleep time" work-around did not appear to help when implemented on some branch build testing. We are move it to trunk because it has gotten so bad today, but I'm not hopeful. 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-54545) Promisify the plugin deletion
Title: Message Title Baptiste Mathus updated JENKINS-54545 Jenkins / JENKINS-54545 Promisify the plugin deletion 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-51404) processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method"
Title: Message Title Ulli Hafner commented on JENKINS-51404 Re: processMavenSpyLogs can fail with "java.lang.IllegalAccessError: tried to access method" I released findbugs-5.0.0-beta3 now, that contains the findbugs library with Xerces 2.11.0. Note: It would still be quite helpful to find the actual plugin (or tool?) that sets the sax property globally! I added some logging to the warnings plugin now to see if the sax property has been altered. 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-55062) Restarting (and likely loading) screen is missing assets if prefixed infront of proxy
Title: Message Title Gavin Mogan created an issue Jenkins / JENKINS-55062 Restarting (and likely loading) screen is missing assets if prefixed infront of proxy Issue Type: Bug Assignee: Gavin Mogan Components: core Created: 2018-12-06 21:55 Priority: Minor Reporter: Gavin Mogan When restarting a jenkins server (/restart), the static assets (such as css/js) are not prefixed, so if jenkins is sitting infront of a proxy server, the assets are not coming from the right place. This appears to work fine in standalone mode (java -jar war), but I'm not sure why. Looks like the jelly files reference resURL, but resURL is undefined for the restarting template. Add Comment
[JIRA] (JENKINS-53589) Evergreen client deletes should also remove the associated exploded plugin directories
Title: Message Title Mandie Smith resolved as Fixed Jenkins / JENKINS-53589 Evergreen client deletes should also remove the associated exploded plugin directories Change By: Mandie Smith Status: In Progress 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-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title Eduard Karlin commented on JENKINS-54632 Re: dsl job doesn't create a build step for Performance Center using Jenkins API It happens on old server with older version of plugin. On a new server I can't even create a build step with the latest version of plugin. I can obviously create manually those Jenkins jobs, but it will be difficult to manage any changes without dsl scripts. 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-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title Eduard Karlin updated an issue Jenkins / JENKINS-54632 dsl job doesn't create a build step for Performance Center using Jenkins API Change By: Eduard Karlin Attachment: image-2018-12-06-16-47-20-776.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51992) Provide a way to clean up console log before handing it to parser
Title: Message Title Ulli Hafner resolved as Won't Fix I think that the plugin can't do anything here. If you change the log output manually it would make sense to pipe the log to a separate file before you annotate the log. Or use the same invisible markers to identify the time stamps. Jenkins / JENKINS-51992 Provide a way to clean up console log before handing it to parser Change By: Ulli Hafner Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title Eduard Karlin commented on JENKINS-54632 Re: dsl job doesn't create a build step for Performance Center using Jenkins API Daniel Gront Dsl/Groovy scripts contains new parameters, but they aren't being passed to the build steps.. 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-54402) Pipeline Syntax page is missing the dropdown for supported parsers
Title: Message Title Ulli Hafner updated JENKINS-54402 Seems that Jenkins architecture does not really support such large (100) element lists with different sub UI pages. I re-organized the layout a little bit, hopefully this helps now. Jenkins / JENKINS-54402 Pipeline Syntax page is missing the dropdown for supported parsers Change By: Ulli Hafner 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-54750) Multiple charts of same type not shown on job summary page
Title: Message Title Ulli Hafner commented on JENKINS-54750 Re: Multiple charts of same type not shown on job summary page I can't reproduce this issue on my machine. Can you please attach the created HTML page? Maybe that helps to find the bug. 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-54904) "(hide)" and "(show)" links in console broken in Firefox
Title: Message Title Devin Nusbaum updated JENKINS-54904 This should be fixed in version 2.30 of the Pipeline Job Plugin, which was just released. Jenkins / JENKINS-54904 "(hide)" and "(show)" links in console broken in Firefox Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-job 2.30 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-55061) Use GeneralNonBlockingStepExecution in RealtimeJUnitStep.Callback
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-55061 Use GeneralNonBlockingStepExecution in RealtimeJUnitStep.Callback Issue Type: Task Assignee: Unassigned Components: junit-realtime-test-reporter-plugin Created: 2018-12-06 21:07 Priority: Minor Reporter: Jesse Glick Use the new API in JENKINS-49337 to solve issues with this step blocking the CPS VM thread in its callback. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-49337) GeneralNonBlockingStepExecution (was: InterruptedException from step tail call)
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-49337 GeneralNonBlockingStepExecution (was: InterruptedException from step tail call) Change By: Jesse Glick Component/s: workflow-step-api-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-49337) InterruptedException from
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-49337 InterruptedException from Change By: Jesse Glick Summary: InterruptedException - Exception processing the logs from 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-49337) GeneralNonBlockingStepExecution (was: InterruptedException from step tail call)
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-49337 GeneralNonBlockingStepExecution (was: InterruptedException from step tail call) Change By: Jesse Glick Summary: GeneralNonBlockingStepExecution (was: InterruptedException fromstep tail call) Component/s: core 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-55060) Use GeneralNonBlockingStepExecution in DockerNodeStepExecution
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-55060 Use GeneralNonBlockingStepExecution in DockerNodeStepExecution Issue Type: Task Assignee: Nicolas De Loof Components: docker-plugin Created: 2018-12-06 21:04 Priority: Minor Reporter: Jesse Glick The API introduced in JENKINS-49337 would improve the behavior of the dockerNode step, particularly in laggy installations. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-43276) CoreWrapperStep should run SimpleBuildWrapper.setUp asynchronously
Title: Message Title Jesse Glick updated JENKINS-43276 Jenkins / JENKINS-43276 CoreWrapperStep should run SimpleBuildWrapper.setUp asynchronously 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-43276) CoreWrapperStep should run SimpleBuildWrapper.setUp asynchronously
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-43276 CoreWrapperStep should run SimpleBuildWrapper.setUp asynchronously Change By: Jesse Glick Assignee: 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-43276) CoreWrapperStep should run SimpleBuildWrapper.setUp asynchronously
Title: Message Title Jesse Glick commented on JENKINS-43276 Re: CoreWrapperStep should run SimpleBuildWrapper.setUp asynchronously Defining the necessary API in JENKINS-49337. 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-43276) CoreWrapperStep should run SimpleBuildWrapper.setUp asynchronously
Title: Message Title Jesse Glick started work on JENKINS-43276 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-55042) email and bitbucket notifications from a non-existent job
Title: Message Title marlene cote commented on JENKINS-55042 Re: email and bitbucket notifications from a non-existent job creating a new job from scratch seemed to fix it, but I just aborted a jenkins build and the Bitbucket notification for a ghost build is back. 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-55042) email and bitbucket notifications from a non-existent job
Title: Message Title marlene cote updated an issue Jenkins / JENKINS-55042 email and bitbucket notifications from a non-existent job Change By: marlene cote Comment: I have created a completely new job for the CI one and the ghost emails and Bitbucket notifications have stopped. I still have the old job around, but disabled if you want to proceed to debug this further. 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-54759) Groovy Parsers - improve help text
Title: Message Title Ulli Hafner updated JENKINS-54759 Jenkins / JENKINS-54759 Groovy Parsers - improve help text Change By: Ulli Hafner 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-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title Devin Nusbaum commented on JENKINS-53305 Re: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; I would be very interested to know if anyone who is experiencing this problem still sees it in after updating to version 2.17 of the Pipeline Step API Plugin, which should be available from the update center in a few hours. 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-55059) pluginmanager shows Update information obtained: N/A ago
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-55059 pluginmanager shows Update information obtained: N/A ago Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-12-06 18:56 Priority: Minor Reporter: Josh Soref Jenkins ver. 2.154 visit /pluginManager/advanced change the update site to https://updates.jenkins.io/experimental/update-center.json Submit change the update site to https://updates.jenkins.io/update-center.json Submit See Update information obtained: N/A ago Expect not to see N/A ago Afaiu, the code starts: https://github.com/jenkinsci/jenkins/blob/7aef24d4542738ce309122ea05a3d194e842c8d8/core/src/main/resources/hudson/PluginManager/check.jelly#L28 https://github.com/jenkinsci/jenkins/blob/22aa2e6e766074d11249893e3f35e0b99e20d3d0/core/src/main/resources/hudson/PluginManager/check.properties#L23
[JIRA] (JENKINS-55058) Show all tasks as separate build stage in Blueocean
Title: Message Title Fabian Grutschus created an issue Jenkins / JENKINS-55058 Show all tasks as separate build stage in Blueocean Issue Type: New Feature Assignee: Jean-Christophe Sirot Components: ansible-plugin Created: 2018-12-06 18:18 Labels: blueocean-ui Priority: Minor Reporter: Fabian Grutschus Hello, could be a nice addition to show all tasks and everything else of an Ansible playbook as separate stage in Blueocean. This could make it easier to see what exact task has failed and click on it just to see the output of the failed task. Add Comment
[JIRA] (JENKINS-46394) active choices reactive parameter cant load shared library
Title: Message Title Ashwin Pai commented on JENKINS-46394 Re: active choices reactive parameter cant load shared library I too would vote in favour of this feature. It would be very useful to have a single shared groovy lib that can be used across. 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-55057) pipeline mail report is giving previous run health report
Title: Message Title Prakash G created an issue Jenkins / JENKINS-55057 pipeline mail report is giving previous run health report Issue Type: Bug Assignee: Unassigned Components: pipeline-view-plugin Created: 2018-12-06 17:47 Priority: Critical Reporter: Prakash G In my pipeline job I use emailext as post mail notifier and email content is $DEFAULT_CONTENT , I am getting mail report perfectly with junit result but the Health report is not correct, am getting previous run health report and it continuous Health Report W Description Score Build stability: 1 out of the last 5 builds failed. 80 Test Result: 1 test failing out of a total of 6 tests. 83
[JIRA] (JENKINS-48283) InterruptedException processing the outputs of Maven builds (processing the logs generated by the pipeline maven spy)
Title: Message Title Vincent Massol commented on JENKINS-48283 Re: InterruptedException processing the outputs of Maven builds (processing the logs generated by the pipeline maven spy) woohoo, thanks Cyrille Le Clerc and 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-49337) InterruptedException - Exception processing the logs
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-49337 Re: InterruptedException - Exception processing the logs FYI https://github.com/jenkinsci/workflow-step-api-plugin/pull/38 successfully tested. We should have a fix "soon" (need first to merge the workflow-step-api-plugin PR and to release it) See https://github.com/jenkinsci/pipeline-maven-plugin/pull/190 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-49337) InterruptedException - Exception processing the logs
Title: Message Title Cyrille Le Clerc commented on JENKINS-49337 Re: InterruptedException - Exception processing the logs FYI https://github.com/jenkinsci/workflow-step-api-plugin/pull/38 successfully tested. We should have a fix "soon" (need first to merge the workflow-step-api-plugin PR and to release it) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48283) InterruptedException processing the outputs of Maven builds (processing the logs generated by the pipeline maven spy)
Title: Message Title Cyrille Le Clerc commented on JENKINS-48283 Re: InterruptedException processing the outputs of Maven builds (processing the logs generated by the pipeline maven spy) FYI https://github.com/jenkinsci/workflow-step-api-plugin/pull/38 successfully tested. We should have a fix "soon" (need first to merge the workflow-step-api-plugin PR and to release it) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48283) InterruptedException processing the outputs of Maven builds (processing the logs generated by the pipeline maven spy)
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-48283 Re: InterruptedException processing the outputs of Maven builds (processing the logs generated by the pipeline maven spy) FYI https://github.com/jenkinsci/workflow-step-api-plugin/pull/38 successfully tested. We should have a fix "soon" (need first to merge the workflow-step-api-plugin PR and to release it) See https://github.com/jenkinsci/pipeline-maven-plugin/pull/190 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-55027) Git plugin requires: Pipeline: SCM Step, Step API
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-55027 Git plugin requires: Pipeline: SCM Step, Step API Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55042) email and bitbucket notifications from a non-existent job
Title: Message Title marlene cote commented on JENKINS-55042 Re: email and bitbucket notifications from a non-existent job I have created a completely new job for the CI one and the ghost emails and Bitbucket notifications have stopped. I still have the old job around, but disabled if you want to proceed to debug this further. 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-55029) Allow target=_blank for links in OWASP Markup Formatter Plugin ("Safe HTML" formatter) under conditions
Title: Message Title
Jarek Rencz commented on JENKINS-55029
Re: Allow target=_blank for links in OWASP Markup Formatter Plugin ("Safe HTML" formatter) under conditions
There's an initiative in WHATWG to make rel="noopener" an implicit default in case target="_blank": https://github.com/whatwg/html/issues/4078 This may simplify this feature to "just allow target="_blank"
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-55029) Allow target=_blank for links in OWASP Markup Formatter Plugin ("Safe HTML" formatter) under conditions
Title: Message Title
Jarek Rencz edited a comment on JENKINS-55029
Re: Allow target=_blank for links in OWASP Markup Formatter Plugin ("Safe HTML" formatter) under conditions
There's an initiative in WHATWG to make {{rel="noopener"}} an implicit default in case {{target="_blank"}}: [https://github.com/whatwg/html/issues/4078]This may simplify this feature to "just allow {{target="_blank"}}
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-55056) Use of net.sf.json.JSONObject can lead to invalid marathon.json generation
Title: Message Title
Jon McKenzie created an issue
Jenkins / JENKINS-55056
Use of net.sf.json.JSONObject can lead to invalid marathon.json generation
Issue Type:
New Feature
Assignee:
Colin
Components:
marathon-plugin
Created:
2018-12-06 16:02
Priority:
Minor
Reporter:
Jon McKenzie
The Marathon plugin uses the net.sf.json.JSONObject class to deserialize the Marathon config. If a user accidentally includes a duplicate key (e.g. in env or labels), this class will combine the values of the duplicate keys into an array in the resulting generated Marathon config (in contrast to most JSON deserialization libraries, which pick the last key), leading to a schema violation when the plugin attempts to PUT the generated config to Marathon (this shows up as an HTTP 422 and no useful error message in Jenkins, due to JENKINS-37287). For example, if you have an env like this:
{
"foo": "bar",
"foo": "baz"
}
The Marathon plugin will generate:
{
"foo": ["bar", "baz"]
}
Values in the 'env' hash are only allowed to be strings, not arrays, so this fails Marathon's JSON schema validation, leading to the HTTP 422.
[JIRA] (JENKINS-54898) ECS Plugin 1.18 cannot launch slaves
Title: Message Title Dominique Rochefort commented on JENKINS-54898 Re: ECS Plugin 1.18 cannot launch slaves Same issue here, reverted to v1.17. Our configuration uses EC2 instances, not Fargate. 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-54898) ECS Plugin 1.18 cannot launch slaves
Title: Message Title Dominique Rochefort updated an issue Jenkins / JENKINS-54898 ECS Plugin 1.18 cannot launch slaves Change By: Dominique Rochefort Attachment: Screen Shot 2018-12-06 at 10.01.35 AM.png Attachment: Screen Shot 2018-12-06 at 10.02.45 AM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49950) Specifying Docker registry credentials should not silently fail if using default URL
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49950 Specifying Docker registry credentials should not silently fail if using default URL Change By: Andrew Bayer Sprint: Declarative backlog 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-52744) Using not existing environment variables in environment GString expression causes strange error message
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-52744 Using not existing environment variables in environment GString _expression_ causes strange error message Change By: Andrew Bayer Sprint: Declarative backlog 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-49280) pipeline docker agent configuration is inconsistent
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49280 pipeline docker agent configuration is inconsistent Change By: Andrew Bayer Sprint: Declarative backlog 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-49142) Be able to customize checkout as "options" in declarative pipeline
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-49142 Be able to customize checkout as "options" in declarative pipeline Change By: Andrew Bayer Sprint: Declarative backlog 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-44491) Step not marked as failure when step could not be found
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-44491 Step not marked as failure when step could not be found Change By: Andrew Bayer Sprint: Declarative - 1.2 , Declarative backlog 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-55055) The dist-fork command hangs when the remote directory contains a FIFO file
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-55055 The dist-fork command hangs when the remote directory contains a FIFO file Likely a core bug at root, though it may be possible for the plugin’s TimestampFilter to work around it. Change By: Jesse Glick Component/s: core 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-54128) Deprecated calls to Run.getLogFile
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-54128 Deprecated calls to Run.getLogFile I removed the component 'warnings' since I fixed it in the beta of the warnings-ng plugin now. Change By: Ulli Hafner Component/s: warnings-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-55051) Support for D-Scanner format
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55051 Support for D-Scanner format Change By: Ulli Hafner Labels: PR help - appreciated wanted newbie-friendly 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-22264) MSBuild parser does not support multi-language output
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-22264 MSBuild parser does not support multi-language output Change By: Ulli Hafner Labels: PR-appreciated 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-22264) MSBuild parser does not support multi-language output
Title: Message Title Ulli Hafner updated JENKINS-22264 Jenkins / JENKINS-22264 MSBuild parser does not support multi-language output Change By: Ulli Hafner 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.
